No, it will just result in a nice error message, and the console rebootingthing is if there new update needs to modifle firm0/1 it could result in it courrpting arm9loader hax and bricking the 3ds
>666 postsNo, it will just result in a nice error message, and the console rebooting
(I already tried that)
No, it will just result in a nice error message, and the console rebooting
(I already tried that)
No.can nintedo make there new updates not work with cfw and just crash if you try to use a9lh with it
i was just asking this cause im thinking of getting rid of the emunand since you don't need it with arm9loader hax and flashing my emunand to sysnand so i still have all my games etc
You'll be fine, but if you really want to stay on the safe side, when there's a new update released, check Tempi was just asking this cause im thinking of getting rid of the emunand since you don't need it with arm9loader hax and flashing my emunand to sysnand so i still have all my games etc
You can if you use the retain a9lh option.I thought we are not able to flash emaunand to synand. Did that change?
Is there such an option now? I remember I had to manually inject partitions.You can if you use the retain a9lh option.
Decrypt9WIP added that option a while backIs there such an option now? I remember I had to manually inject partitions.
It's simply hard to patch, too low-level exploit.thing is why arent nintedo trying hard to stop it if it allows piracy though
Because by adding the OTP to the chain of trust they royally screwed themselves.thing is why arent nintedo trying hard to stop it if it allows piracy though
Well, when I tried to update my 3DS emuNAND from 9.9 to 10.7 with ReiNAND 3.8 (with FIRM protection), it just gave me an error (something like "The update could not be completed, the system will now restart"), but with Cakes (with FIRM protection disabled), I worked perfectly. Same thing with SysUpdater on my N3DS; when I tried to downgrade the emuNAND to 2.1, it failed to downgrade NATIVE_FIRM, but with Cakes, no problem.Also it should actually update successfully, without touching FIRM0/1
Then I blame ReiNand. Using AuReiNand I updated from 9.2 A9LH to 10.7 keeping A9LH fine using SysNAND.Well, when I tried to update my 3DS emuNAND from 9.9 to 10.7 with ReiNAND 3.8 (with FIRM protection), it just gave me an error (something like "The update could not be completed, the system will now restart"), but with Cakes (with FIRM protection disabled), I worked perfectly. Same thing with SysUpdater on my N3DS; when I tried to downgrade the emuNAND to 2.1, it failed to downgrade NATIVE_FIRM, but with Cakes, no problem.
Well, when I tried to update my 3DS emuNAND from 9.9 to 10.7 with ReiNAND 3.8 (with FIRM protection), it just gave me an error (something like "The update could not be completed, the system will now restart"), but with Cakes (with FIRM protection disabled), I worked perfectly. Same thing with SysUpdater on my N3DS; when I tried to downgrade the emuNAND to 2.1, it failed to downgrade NATIVE_FIRM, but with Cakes, no problem.[/QUOTE]Also it should actually update successfully, without touching FIRM0/1
You can if you use the retain a9lh option.
