(Stolen analogy alert)It's sorta like this.
Menuhax is like an old junker car, and a9lh is like a sports car. Everyone can agree that the sports car is better, but the junker car is functional, if not always reliable.
>giving Nintendo ideasTechnically, Nintendo could do something in regards to a9lh, that could lock out those who don't have a nand backup, from their homebrew, without bricking the system. All they would have to do, is embed a plaintext firm update into system menu, along with a custom arm9loaderhax.bin file.
If system menu detects arm9loaderhax.bin or arm9loaderhax_si.bin, it could hash check it, to determine the state of it. if it sees that it is not the hash of the one embedded in system menu, it could then overwrite it, and also write its copy of FIRM.bin to the SD then force a reboot.
Once rebooted, that overwritten arm9loaderhax.bin will then encrypt FIRM.bin with the system specific FIRM0/FIRM1 keys, and overwrite FIRM0/FIRM1, then reboot.
That updated FIRM, could just have ALL of the secret sector keys hard-coded within it, since said secret sector is compromised anyways, and not use secret sector anymore, and thus, this FIRM even if written onto FIRM0/FIRM1 of a new 3DS, could be made to NOT brick even the a9lh hacked systems. Likewise, if someone was to perform said update within gateway, if nintendo was to do this, then they would just lose A9LH.
Therefore, it definitely is suggested to NOT update your system, even with A9LH present, till a few hard-modded users confirm the update is safe.
Even if they did this, we could install Nver and Cver and the Friends list CIAs and pretend nothing ever happenedTechnically, Nintendo could do something in regards to a9lh, that could lock out those who don't have a nand backup, from their homebrew, without bricking the system. All they would have to do, is embed a plaintext firm update into system menu, along with a custom arm9loaderhax.bin file.
If system menu detects arm9loaderhax.bin or arm9loaderhax_si.bin, it could hash check it, to determine the state of it. if it sees that it is not the hash of the one embedded in system menu, it could then overwrite it, and also write its copy of FIRM.bin to the SD then force a reboot.
Once rebooted, that overwritten arm9loaderhax.bin will then encrypt FIRM.bin with the system specific FIRM0/FIRM1 keys, and overwrite FIRM0/FIRM1, then reboot.
That updated FIRM, could just have ALL of the secret sector keys hard-coded within it, since said secret sector is compromised anyways, and not use secret sector anymore, and thus, this FIRM even if written onto FIRM0/FIRM1 of a new 3DS, could be made to NOT brick even the a9lh hacked systems. Likewise, if someone was to perform said update within gateway, if nintendo was to do this, then they would just lose A9LH.
Therefore, it definitely is suggested to NOT update your system, even with A9LH present, till a few hard-modded users confirm the update is safe.
Once installed the hack is impervious..... They may make an update that doesn't play nice with the hack but it can always be patched as needed.Please do not state that as fact. It is possible to stop as devs have pointed out before, its difficult to take down but not impossible.
How does this take away from what I said?Once installed the hack is impervious..... They may make an update that doesn't play nice with the hack but it can always be patched as needed.
Fixing the known-plaintext exploit, meaning we can't write native_firm even with a hardmod.
it was a Comissioned Piece, but thats Off-topic, i dont fully understand how they bricked just remember it was involving regnion changed Wii's with BootMiiNice avatar. Did you make it?
Anyway, so it bricked normal consoles? How?
Your profile is locked so I was just saying it here. Who drew it?it was a Comissioned Piece, but thats Off-topic, i dont fully understand how they bricked just remember it was involving regnion changed Wii's with BootMii