I doubt anyone can say that with 100% confidence. No offence to anyone but this isn't Dark Alex providing the protection. There's no reason to assume its always going to be perfectly safe.Wouldn't the same apply in the future?
looks like someone already ported ctrBootManager
I doubt anyone can say that with 100% confidence. No offence to anyone but this isn't Dark Alex providing the protection. There's no reason to assume its always going to be perfectly safe.
The FIRM protection in AuReiNand can't stop someone accidentally restoring a 10.6 emuNAND backup to sysNAND. I'm pretty sure in that case the user would be SOL. So yeah, it's safe-ish but not foolproof. As silly as it may sound it's actually not that hard to make that sort of mistake.I was under the impression that if you updated sysnand while a9lh was installed and firm1/0 are locked it would be fine as long as the cfw supported it. If it didn't then it would black screen like emunand and you'd have to downgrade with decrypt9-anlh.
After all it's a cfw being booted, kind of like emunand. Nintendo never found a way to force installs to sysnand through emunand so shouldn't it be the same with a9lh?
The FIRM protection in AuReiNand can't stop someone accidentally restoring a 10.6 emuNAND backup to sysNAND. I'm pretty sure in that case the user would be SOL. So yeah, it's safe-ish but not foolproof. As silly as it may sound it's actually not that hard to make that sort of mistake.
Yup, but if it's possible someone is bound to do it eventually. In fact, there are probably new ways to screw up that no one has even thought of yet. GBATemp'ers are pioneers in that field.True, but people should store their sys and emunands separately and label them
This is the bit that has me sticking with EmuNAND. I don't want my 3DS to become unusual because I cannot find a NAND backup that I made ages ago.Your NAND will not boot until CFW devs update it to work with the latest FIRM. If you're feeling impatient, flash an older NAND backup, almost the same way you'd do on emuNAND.
Er... ok?This is the bit that has me sticking with EmuNAND. I don't want my 3DS to become unusual because I cannot find a NAND backup that I made ages ago.
That's why you make a backup *today* instead of relying on one you made ages ago.This is the bit that has me sticking with EmuNAND. I don't want my 3DS to become unusual because I cannot find a NAND backup that I made ages ago.
I'm obviously talking about some point in the future.That's why you make a backup *today* instead of relying on one you made ages ago.
arm9loaderhax is unfixable once you dump your OTP its a wrap. Sure nintendo can erase the hack if you update the firmware but you still have the OTP which you can compile the hack again and flash it. Having a nand mod is extremely important if your running arm9loaderhax imo All we need now is bootromhax then we can really see nintendo have a heart attackEmunand, safer and in case of nintendo pull an update who can erease A9LH (i don't know if it's possible)
Install your games normally, just don't forget to install a patch AGB_FIRM first.So yeah, Im looking into using sysnand as my primary NAND mainly for GBA games. What do I actually need to do to run GBA games on my sysnand while using A9LH?