Hacking Ways Nintendo Can Kill A9LH?

[gnmmarechal]

Yeah. My console is already nand modded. It's really really impossible for them to uninstall my CFW. I could just flash a backup to undo all their hardwork then wait till CFW is updated to block what ever they did to brick it.

Or, they can brick it by messing with the leds. Wouldn't be fixable by a NAND restore

Sent from my Nokia 3310 using Tapatalk

 

[gnmmarechal]

Firm is not as well locked, else Gateway's implementation of AL9H wouldn't have "update risks"

It's fucking Gateway. Nothing else to say.

Sent from my Nokia 3310 using Tapatalk

 

[Deleted User]

http://wiibrew.org/wiki/Error_003
Error 003 was a deliberate attempt by Nintendo to brick Korean Wiis that were region changed to any other region. The reason I can say it was deliberate is because, as noted in the wiibrew article, the system attempts to use the Korean key to encrypt some hardcoded bytes. If the result matches what the actual Korean key would produce, it shows error 003. I cannot think of any situation where that could have been accidental.

Haha, whoops. Guess I got it somewhat backwards. Been a while since I read about it.

 

[SnakeOil092]

Nintendo is watching.

 

[runetoonxx2]

That being said,

They could always:

1. secretly modify your arm9loaderhax bin to have firm unprotected,
2. force a restart
3. proceed to update.

edit:
and package it nicely with a prompt

"Your 3DS needs to be restarted before this update, do you agree?"

Hit yes, and they work their evil XD

#not anymore shadownand now provides firm protection straight from the NAND so we can take out our SD cards to update if needed

 

[gnmmarechal]

#not anymore shadownand now provides firm protection straight from the NAND so we can take out our SD cards to update if needed

same with Aurora's A9LH, but many will forget to remove SD, plus you won't know if Nintendo did this until SOMEONE updates.

 

[Jiro2]

It definitely appears they have moved their security team's priorities to the NX which will be the successor to the Wii-U.

I am not convinced of this. The 11.0 update to the 3DS was obviously an attempt to prevent as many hacks as they could to the extent they could, and it's still pretty recent.

 

[vb_encryption_vb]

I am not convinced of this. The 11.0 update to the 3DS was obviously an attempt to prevent as many hacks as they could to the extent they could, and it's still pretty recent.

They still haven't patch hardmod dowgrade...

 

[Arthurgamer07]

They still haven't patch hardmod dowgrade...

I dont think they can patch that

 

[vb_encryption_vb]

I dont think they can patch that

All they have to do is update native firm.

 

[Pokéidiot]

Hardmod downgrade is done by messing with plaintext regions of FIRM partition on a raw NAND backup.
A new hardware revision would be needed to this to be encrypted, and reprogramming bootroms to decrypt it at boot time.

And...
YOU ARE GIVING NINTENDU IDIAZ!
All people that did RE'd 3DS did writeups of their work for this same reason.

 

[PK101]

I think they might forget about a9lh, but then again they could do something about it in the new releases.

 

[CreAtor135]

http://wiibrew.org/wiki/Error_003
Error 003 was a deliberate attempt by Nintendo to brick Korean Wiis that were region changed to any other region. The reason I can say it was deliberate is because, as noted in the wiibrew article, the system attempts to use the Korean key to encrypt some hardcoded bytes. If the result matches what the actual Korean key would produce, it shows error 003. I cannot think of any situation where that could have been accidental.

I don't get how everyone seems to let this fly over their heads, when they say any company that intentionally bricks is absolute tripe and shouldn't be forgiven, nor trusted.

 

[Urbanshadow]

I don't really think they can do much to systems with a9lh already installed. They could go full retard and try to specifically detect a9lh in the contents of the FIRM partitions during firm boot and deliberately crash but that is a ton of work for nintendo, barely reliable, with potential workarounds.

They could add padding to the firms to prevent new a9lh installs. That way the cool jumpy garbaged FIRM1 would write over the a9lh stage2 when booting. Then again a downgrade to a lower FIRM would fix this.

If they change the FIRM major version (to block hardmod firm exchange procedure), update FIRM minimum version system titles list, add padding to FIRM0/1 all in the same update they might be able to hurt those people without CFW FIRM write protection (virtually no one). And that would make a decent strong security update for new bundles that might come with that system version.

Unless someone found a ARM9K level exploit (remember svcBackdoor was gone?). Then it's 9.2 all over again.

 

[Zan']

Don't quote me on this, but I think that'd be illegal.

It's perfectly legal.
You are violating their terms of use by modifying your system in such ways.
Therefore they have the right to remove all their software from the system as long as they don't physically damage your Hardware, which they wouldn't.
(I asked a friend who is studying law about this.)

Also most A9LH Users use it for pirating games etc. So if it comes to it the A9LH user would lose anyway.

However, creating a "brick arm9loaderhax.bin" on the root of the SD card would only affect Users, whi didn't mess around with the path or name of the file.
I personally load it as "launcher.bin". Therefore a brick file arm9loaderhax.bin wouldn't do shit.

And messing with the Arm9 Kernel could affect legit users as well, and is therefore not really an option.

They could surely implement complicated checks and do whatever modifications, but none of that is 100%.

 

[gnmmarechal]

I dont think they can patch that

They can, by changing the encryption of say, 11.1 like they did on 9.6. You can't use 9.6+ titles on 9.5 or lower. They can patch the downgrading by making 11.1 titles incompatible with 10.7 NATIVE_FIRM.

 

[JPnintendo]

Ok, just in case I Will mark my A9LH.bin as read only in my SD. That would prevent a "Nintendo update overwrite"

 

[GerbilSoft]

Ok, just in case I Will mark my A9LH.bin as read only in my SD. That would prevent a "Nintendo update overwrite"

Because that 'read only' attribute on FAT filesystems can't be worked around and is definitely honored by all implementations. :V

That having been said, I'm pretty sure Nintendo generally doesn't mess with user files on the SD card outside of the "Nintendo 3DS" directory unless specifically granted permission, e.g. with the 3DS Camera. (Twilight Hack saves being deleted on Wii only affected the copies in the Wii system memory, not on the SD card.)

 

[Pokéidiot]

Hardmod downgrade is done by messing with plaintext regions of FIRM partition on a raw NAND backup.
A new hardware revision would be needed to this to be encrypted, and reprogramming bootroms to decrypt it at boot time.

And...
YOU ARE GIVING NINTENDU IDIAZ!
All people that did RE'd 3DS did writeups of their work for this same reason.

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

I think that nintendo wouldn't remove a hack that an user installed. That's not respectful. What nintendo is actually doing is, always patching exploits to prevent users to use it.
So, I think that they most likely will patch A9LH with a new hardware revision, since it tricks bootrom.

 

[Temarile]

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

I think that nintendo wouldn't remove a hack that an user installed. That's not respectful. What nintendo is actually doing is, always patching exploits to prevent users to use it.
So, I think that they most likely will patch A9LH with a new hardware revision, since it tricks bootrom.

The chance that nintendo releases a new 3ds device is so so small. The 3ds is at the end of its lifespan. Chances are that the NX will be the next gen for both the wii u and the 3ds.