Should have come to this forum and ask for help when failing to restore backup instead of upgrading the firmware assuming it will be okay.
If that was a viable option, it would've been mentioned as alternative in the guide.
I have no way to try this, and i won't reccomend it to anyone, but i think you can update to 4.5 via cart. then set up a cfw on sysnand with no firm patch(like rxtools devmode). and then use sysupdater with the N3ds files.But what do you suppose caused you to fail upgrading to begin with? That's the real issue. You wouldn't be where you are now if that hadn't happened. Did you use the newest version of OTPhelper linked to in the Plailect guide?
Wouldn't this have been prevented if he used the sysnand backup validation in otphelper? Not sure if it's in plailects guide, but it should be.
I think you're scaring the guy too much. Now OTPhelper does all the patching for N3ds users, so no need to worry.Yes u can and u must use 2.1 but u know that 2.1 was only for o3ds right? And that why u needed to patch the bricked emunand with 2.1 and if u update form 2.1 on n3ds u will brick and why? because the n3ds never had 2.1 update
Without 2.1 u would never be able to dumb ur otp.bin
You got this man!Currently trying my first A9LH on N3DS
Currently trying my first A9LH on N3DS
The update seemed to work fine. The device did a reset and didn't load. I do see the blue light on.
I have a sysnand backup.
But he BRICKED..!You can not update from 2.1 N3DS, even it updating, it brokes the firms. Your nand backups are probably invalid due to some kind of corruption or fragmentation.
- If you downgraded to 2.1.0 on New 3DS but for some reason have no functional NAND backups(with or without a functional browser), I am working on a possible solution involving EmuNAND + NCSD / Crypto trickery.
https://github.com/Plailect/Guide/wiki/3DS-Stuck-(2.1.0-Without-Functional-Browser)
https://github.com/Plailect/Guide/wiki/NAND-Size
Does SysNAND validation checker on OTPHelper check to make sure the dumped NAND is okay, i.e. the kind of corruption/fragmentation/dumpingerror that probably caused OP's problems? Can this be checked immediately before advancing to the next step?
I've successfully A9LHed my O3DS, but I'm nervous to do my N3DS. If OTPHelper can do this, it would make me a lot less nervous.
But he BRICKED..!
He said he updated his 3DS and now he has a BLACK SCREEN.
Why were you trying to restore sysnand from 2.1 to 9.2, when it should have been emunand that was downgraded to 2.1?
U have to flash Emunand to Sysnand in order to get the OTP
You can't extract the OTP from EmuNAND, in fact, there is no CFW that can load a 2.1 EmuNAND. It's just for safety, to make sure the downgrade process goes smoothly, since it doesn't always and a failed downgrade is a brick.Ok, downgrade emu first just so if it fails it's a whole lot easier to recover from? I thought the idea was so you could extract otp directly from the emunand (which should have the otp as well?)