Hacking SysNAND won't load after updating ARM9LoaderHax

[ArmoredGuns1]

Hello, I'm going to explain my situation here:

- I had the old version of arm9loaderhax with no screen-init, old version of AuReiNAND, 9.2 Sysnand and 10.6 Emunand.

- I wanted to update arm9loaderhax AND make my Emunand be my SysNAND, so I recompiled the installer with the latest Delebile fork, made an Emunand backup with D9, renamed it to NAND.bin and installed Arm9loaderhax.3ds again through SysNAND Homebrew Launcher.

- After that, SysNAND won't load, but Emunand loads fine. I tried updating AuReinand without any luck. Yes, I have both firmware90.bin and firmware.bin in the Rei folder. What could the problem be and how am I able to solve it? Thanks for your advice!

 

[Toiry921]

So you uninstalled A9LH by restoring a 9.2 NAND backup and then loaded a9lh installer and then your SysNAND bricked? But you still have access to emunand and A9LH

 

[ArmoredGuns1]

So you uninstalled A9LH by restoring a 9.2 NAND backup and then loaded a9lh installer and then your SysNAND bricked? But you still have access to emunand and A9LH

No, like I said in my post, I made an Emunand backup with D9, renamed it to NAND.bin, and installed my recompiled A9LH of Delebile's fork. After that SysNAND won't load, but Emunand loads just fine. A9LH still works.

 

[Toiry921]

No, like I said in my post, I made an Emunand backup with D9, renamed it to NAND.bin, and installed my recompiled A9LH of Delebile's fork. After that SysNAND won't load, but Emunand loads just fine. A9LH still works.

did you restore the NAND.bin to sysnand before you reinstalled A9LH? you can always use D9 to restore an older NAND backup and try again.

 

[ArmoredGuns1]

did you restore the NAND.bin to sysnand before you reinstalled A9LH? you can always use D9 to restore an older NAND backup and try again.

I didn't. I will try that, thanks!

 

[ArmoredGuns1]

OK, I just did the following:

1) Restored original 9.2 NAND backup with A9LH version of Decrypt9.
2) Installed Arm9loaderhax.3dsx in SysNAND homebrew launcher.
3) SysNAND boots well with A9LH installed again.
4) Using D9, I dumped my Emunand's CTRNAND Partition
5) I injected Emunand's CTRNAND partition to SysNAND's
6) SysNAND won't boot again, using AuReiNAND 3.8.1.

What could I be doing wrong?

 

[lithium210]

OK, I just did the following:

1) Restored original 9.2 NAND backup with A9LH version of Decrypt9.
2) Installed Arm9loaderhax.3dsx in SysNAND homebrew launcher.
3) SysNAND boots well with A9LH installed again.
4) Using D9, I dumped my Emunand's CTRNAND Partition
5) I injected Emunand's CTRNAND partition to SysNAND's
6) SysNAND won't boot again, using AuReiNAND 3.8.1.

What could I be doing wrong?

Have the proper files (flags) in the rei folder? [updatedsysnand, installeda9lh & usepatchedfw] Updatedsysnand is the most important so sysnand boots.

 

[ArmoredGuns1]

Yeah I have them there. I'm trying to boot SysNAND by pressing the L button, which stays in a black screen.

 

[lithium210]

Yeah I have them there. I'm trying to boot SysNAND by pressing the L button, which stays in a black screen.

If you have the "updatedsysnand" file in the rei folder itll boot directly to sysnand without pressing any buttons. If you hold L or R, should boot to emunand (if you have one).

 

[stl25]

"Updated sysNAND" mode:
- For this, you need A9LH. You can toggle it by creating a "/rei/updatedsysnand" file.
- Normally sysNAND is autobooted.
- If you hold L on boot, emuNAND will be booted with the 9.0 FIRM (firmware90.bin) so you can use exploits (you need to create a 9.0/9.2 emuNAND for this!).
- If you hold R on boot, emuNAND will be booted with the firmware.bin on the SD card.

 

[tivu100]

Dude. You're booting SYSNAND all this time.

You don;t have a EMUNADN 9.0 or 9.2 so by holding L you boot firm9.0 for EMUNAND which of course not working (black screen).

Try hold R and let us know whether you can get on to EMUNAND?

Or you can copy the coNtent of current memory card to a different memory card without EMUNAND. If it boots then your SYSNAND booting just fine.