Separate names with a comma.
Discussion in '3DS - Homebrew Development and Emulators' started by I_AM_L_FORCE, Mar 8, 2016.
Yeah. I bricked sysnand but I still have a9lh installed and can still boot my emunand. Help?
If you could boot a bin file of otphelper through the a9lh, you could restore the sysnand I guess.
By any chance have you made a backup of sysnand with a9lh installed?
There's also an a9lh-bootable version of Decrypt9 that could be used for the same purpose.
No, I have a normal sysnand backup though. Can I flash that then reinstall it?
yeah, it will be fine.
Yeah it will be fine, but keep in mind you'll lose any changes to sysnand and a9lh. As you say, you will have to reinstall a9lh. If I were you I would search a way to do an unbricked CTRNAND backup with D9 or something (CTRNAND != full nand). That way you could recover from bricks without touching a9lh.
How would I make this CTRNAND backup?
Download the Decrypt9WIP all-in-one, you will find a decrypt9wip.bin inside of it, rename it "arm9loaderhax.bin" and boom, decrypt9 at boot0.
Idk, you are on your own there. Perhaps decrypt9 has a CTRNAND partition dump/restore option but I could be wrong.
But yeah, you will lose your arm9loaderhax.
Oh the wii times. 3ds has no boot0/1/2, just bootrom.
It's firm0 and firm1 afaik
Bootrom starts first. Someone has to decrypt the firm partitions before booting them
Also, like boot0 in the wii, is a rom (hece the boot-rom name).
This is also named by ninty this way, as in hardmod systems you can see bootrom errors
with the blue screen saying "BOOTROM" and the error code.
BOOTROM checks FIRM0 and loads it if it passes a signature check, otherwise BOOTROM loads FIRM1.
If FIRM1 doesn't pass a signature check, it's a blue bootrom screen.
FIRM0 and FIRM1 are basically the same. FIRM1 is just there as a backup in case FIRM0 gets corrupted somehow.