I'll fix that in the next version, I just wonder why you haven't checked your EmuNAND before transfering it to SysNAND. Normally, what you have there is a false positive (caused by multiple TMDs in your app directories), but you need to proceed on your own risk there.Hey,
I have a EU N3ds:
I have used this version of the OTP helper "OTPHelper-20160319-125601"
The opt helper wont let me restore sysnand.
Im currently in the otp helper menu and want to restore the previous sysnand as the downgraded 2.1 sysnand currently fails the validation checks.
I only remembered to do a validation check of the downgraded emuanand just as a pressed the button to flash the sysnand.
I waited for the sysnand to finish the flash and did the validation checks, which failed.
The message i got was:
TMD success: 110
TMD not found: 0
TMD hash mismatch: 3
APP success: 110
APP fragmented:
APP hash mismatch: 0
I decided to flash the sysnand with backup that was made at the start of the process but am receiving the same error that Sukamon has:
"This is a slot0x5 (N3DS) type NAND image!Sorry, you can't inject that, and if I saved your 3DS, you owe me a beer.
SysNAND Restore: failed!"
I also just read that the 0.71 version does not have this bug, but I cant change the version of otp helper that im on without restarting the console.
So right now im stuck in the OTP helper, not sure if I should just take the chance and restart the system and hope for the best even though there are some TMD hash mismatches!
Please help!
--------------------- MERGED ---------------------------
Seconding that.Depending from where you try to install a nand, it offers/allows install or not.
OTPHelper (3dsx) sysNAND 9.2 > emuNAND_unbricked.bin (2.1) to sysNAND
OTPHelper (arm11/9.bin) Firmware 2.1 > sysNAND_original.bin to sysNAND