Hacking Could future updates ever potentially be blocked (or damage) A9LH systems?

[The Catboy]

I think you might have answered my question here actually - so depending on the CFW, it's likely that the CFW will protect the A9LH install. That makes lots of sense. So in theory if Nintendo attempted to remove the modifications the read-only lock in place would halt the upgrade.

--------------------- MERGED ---------------------------



An update running without the protections in place on the CFW - thanks for the good answer.

Basically, the only way Nintendo can remove A9LH, is if you are stupid. But since Luma3DS, SaltFW, and ReiNAND all have it on by default, those are completely noob-proof.
Corbenik and CakesFW do not have it on by default. But since they are Dev/Poweruser driven CFW's, the devs just assume the end user is smart enough to remember to turn on these protections.

 

[yifan_lu]

Like I said, you underestimate the skills of hackers. Putting aside any legal issues, there is no way Nintendo can "slip by" a cfw removing update. First, any ota update must be accepted. If the update deletes your cfw, there would be posts everywhere about it literally minutes after the update comes out. If they were more sneaky, they might release a stage1 update that disables user confirmation on ota updates and push a stage2 ota that deletes your cfw. But even that will be detected by hackers and there will quickly be a Luma3DS update that disables such a "feature".

 

[The Catboy]

Like I said, you underestimate the skills of hackers. Putting aside any legal issues, there is no way Nintendo can "slip by" a cfw removing update. First, any ota update must be accepted. If the update deletes your cfw, there would be posts everywhere about it literally minutes after the update comes out. If they were more sneaky, they might release a stage1 update that disables user confirmation on ota updates and push a stage2 ota that deletes your cfw. But even that will be detected by hackers and there will quickly be a Luma3DS update that disables such a "feature".

Even than, it still all boils down to someone needs to accept it. And people should wait until they have a confirmed safe update before blindly rushing into an update.

 

[chaoskagami]

Look, they could only ever do this with two updates (aside from arm9loaderhax.bin)

The next update would need to change the system updater in some signifcant way to screw our patches, and the next one would be the one to brick us. By then, we would all know and have fixed our patches.

The current method system update uses can't touch us.

 

[cracker]

Nintendo could legally do it if you gave them the go-ahead by blindly accepting the EULA for an update that stated it would remove it. It is a legal grey area but you accepted the terms that you wouldn't modify the system hardware- or software-wise when you opened the box (or first set the 3DS up depending on whom you ask).

 

[Sumea]

Nintendo could legally do it if you gave them the go-ahead by blindly accepting the EULA for an update that stated it would remove it. It is a legal grey area but you accepted the terms that you wouldn't modify the system hardware- or software-wise when you opened the box (or first set the 3DS up depending on whom you ask).

I'd say it is way nebulous to have EULA with a piece of hardware. I think that is illegal even in europe. US I can believe just about anything about but the most would be that agreement to use their update services, online services etc. prohibit modified systems and you relinquish any damage your system may suffer for breaking this agreement.

There has been tons of legal battles over say, jailbreaking iPhone as a legality and I think also modifying game console systems for your own software - it is your device and hardware ultimately. Software and software piracy are other thing entirely.

 

[cracker]

Yeah, in the US companies get away with a lot more shit. Opening a product means accepting the agreement before you even get the opportunity to read it. This has been challenged against MS for it's software but I haven't seen anything else along these lines.

 

[tombi]

For users who still don't trust the protections of modern noob-proof CFW: Just don't update once an update is available. Look at the forums and check if anybody tried an update with A9LH yet. Once an update is available the community will inform everybody very fast about it.

 

[apoptygma]

For users who still don't trust the protections of modern noob-proof CFW: Just don't update once an update is available. Look at the forums and check if anybody tried an update with A9LH yet. Once an update is available the community will inform everybody very fast about it.

Just a minor amendment to your statement there - what (as far as I understand) people should be searching for is if people have attempted an update within the environment of their chosen CFW (ie. Luma3DS) - A9LH doesn't inherently protect it's own modifications to firmware, the CFW provides these mitigations. This was essentially the correct answer to my original question, which several people provided.

 

[tombi]

@apoptygma Thanks! This is right and very important to know.