Hacking Bricked sysNAND with A9LH

[sora10pls]

Before anybody asks, yes, I have tried multiple NAND backups through Decrypt9 and my hardmod, only to have none of them work.

For a while now I've had A9LH installed on my n3DS. I haven't been using Updated SysNAND Mode, but I figured that I wanted to considering it'd give me more space to work with on my microSD and I'd get a slightly faster boot time.

When I tried to hold L to go into my SysNAND, it came up with an error and a black top screen. Thinking I could fix it, I tried to restore a NAND backup through Decrypt9 on boot, and it restored just fine!
...but I still got the same error when booting into my SysNAND. Hoping nothing got screwed up, I booted regularly and my EmuNAND was still fully functional.

I thought to myself, "Maybe try restoring through my hardmod." So I did just that, and got the exact same result as before.

Case in point, my SysNAND is bricked, yet my A9LH EmuNAND is working totally fine.

Does anybody have any idea why that's the case? I'm just glad that my n3DS is working, but I would still also like to use Updated SysNAND Mode if possible.

 

[Deleted User]

Stupid question time but before you did A9LH, did you use menuhax by chance and you deleted the payload from your SD?

If so, there's a high chance menuhax is triggering and since the payload is missing, will crash the console.

 

[sora10pls]

Stupid question time but before you did A9LH, did you use menuhax by chance and you deleted the payload from your SD?

I did use Menuhax, but I deleted both the payload and extdata once I installed A9LH.

 

[Deleted User]

Assuming you deleted the extdata in the proper Nintendo3DS folder, what's the exact error you get when booting to sysNAND on the bottom screen?

You also didn't mention which FW (assuming AuRei) and you have the firmware90.bin? Also assuming you were on 9.2? IF so, just for shits and giggles, put the payload back.

 

[sora10pls]

Assuming you deleted the extdata in the proper Nintendo3DS folder, what's the exact error you get when booting to sysNAND on the bottom screen?

You also didn't mention which FW (assuming AuRei) and you have the firmware90.bin? Also assuming you were on 9.2? IF so, just for shits and giggles, put the payload back.

Error: "An error has occurred. Hold down the POWER Button to turn off the power, then turn it on and try again. For help, visit support.nintendo.com."
SysNAND 9.2.0-20U.
And yes, I do have firmware90.bin in my /aurei folder.

 

[Deleted User]

Just to check, and assuming you haven't install/deleted any titles.

Go into both folders Nintendo3DS/<Id0><id1>/extdata/000000/0000008f and move the 8f folder for both to your desktop and attempt to boot. Does it still crash? If so, your sysNAND probably has modified titles.

Have you checked your sysNAND backups via OTP Helper to check if they're valid?

edit: If you don't care whats on sysNAND, you can always downgrade emuNAND and flash it to sysNAND.

 

[leonmagnus99]

good that i came up on this thread, i also removed my menuhax files from my mSD except for the ones inside the Nintendo3DS folder,

i never touch those ones.

 

[sora10pls]

Just to check, and assuming you haven't install/deleted any titles.

Go into both folders Nintendo3DS/<Id0><id1>/extdata/000000/0000008f and move the 8f folder for both to your desktop and attempt to boot. Does it still crash? If so, your sysNAND probably has modified titles.

Have you checked your sysNAND backups via OTP Helper to check if they're valid?

I hadn't really thought it through and made the post on my way to work, so sadly I can't do that until after my shift tonight. If you'd be willing to help out around then it'd be very much appreciated.

And no, I haven't actually. What does have me believe that they're valid is the fact that once I restore a non-A9LH backup, I get the error instantly. But after when I restore an A9LH backup through my hardmod, it boots into EmuNAND fine but SysNAND gives an error.

 

[Deleted User]

Probably should be around, but A9LH wouldn't make a difference, when A9 is running there's no OS running, A9 jumps straight to emuNAND. (unlike menuhax where sysNAND is a requirement)

 

[mgrev]

you still have the otp.bin right? try downgrading your emunand to 9.2, then flash it to sysnand, and then install a9lh

 

[sora10pls]

you still have the otp.bin right? try downgrading your emunand to 9.2, then flash it to sysnand, and then install a9lh

I do have the OTP, but I've already tried that. When restoring my EmuNAND to SysNAND with Decrypt9, it says the backup isn't valid.

 

[ricosuave0922]

I think i had something similar to this, when i tried to boot holding L i would get that error. after playing around with some files from my SD backup, when i put the menuhax_padcfg.bin back on the root of my sd card everything works as expected. The system doesn't boot with all the colors and stuff of menuhax it boots right away like A9LH is supposed to. Not sure what that means exactly. I do still use menuhax on my 9.2 sysnand to boot homebrew launcher and gateway mode.

Its weird though, if i set the sue FIRM9.0 by default it works fine, if i switch to updated sysnand mode and try to hold L to boot FIRM9 then it just freezes on a black screen and i have to hard power it off. Any ideas what that means?