I've recently hardmodded my Old 3DS in order to restore A9LH on it, after I have foolishly lost it after updating my firmware without FIRM protection. Eventually, I got it to work an restored my NAND backup on Linux using the dd command:
All went well, my 3DS is now back with A9LH, but for some reason, I can't restore my NAND backup with Decrypt9 / Hourglass9, both give me an error "SysNAND write error. File too small or SD failure". My SD Card is working and the backup itself is valid (I've used it before). So here are my questions
1.Could hardmodding my 3DS somehow affected the NAND, so that I can no longer restore my pre-hardmod backups? Can this be fixed?
2.Can I brick my 3DS by using "NAND Restore (forced)" option? Or lose A9LH again (backup was made with A9LH)?
3.How can I check if all of the files in my NAND are valid and if there are no corrupted blocks?
Thanks in advance for help.
All went well, my 3DS is now back with A9LH, but for some reason, I can't restore my NAND backup with Decrypt9 / Hourglass9, both give me an error "SysNAND write error. File too small or SD failure". My SD Card is working and the backup itself is valid (I've used it before). So here are my questions
1.Could hardmodding my 3DS somehow affected the NAND, so that I can no longer restore my pre-hardmod backups? Can this be fixed?
2.Can I brick my 3DS by using "NAND Restore (forced)" option? Or lose A9LH again (backup was made with A9LH)?
3.How can I check if all of the files in my NAND are valid and if there are no corrupted blocks?
Thanks in advance for help.
Last edited by Wojton,