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.
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.