Homebrew [RELEASE] OTPHelper - OTP dumping & downgrade helper

[d0k3]

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!

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.

--------------------- MERGED ---------------------------

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

Seconding that.

 

[grubgrub]

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.

--------------------- MERGED ---------------------------


Seconding that.

Yea i made a mistake, I was following a video tutorial on the process that did not have that step as it was made a few weeks ago.

I was also reading the written guide but I realized my error too late to stop the update.

So is my only option left to restart the system and hope it still boots?

 

[d0k3]

Yea i made a mistake, I was following a video tutorial on the process that did not have that step as it was made a few weeks ago.

I was also reading the written guide but I realized my error too late to stop the update.

So is my only option left to restart the system and hope it still boots?

At the moment, yup. But don't worry too much. You know we have that verification only since yesterday, and brick rate was low since v0.71?

 

[grubgrub]

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

I was on 9.0 with i downgraded, but have not restarted to start up 2.1 as i was not sure if it would brick it or not.

But seems like there is nothing else i can do except restart and hope it works.

If it does work i'll complete the process restore my backed up 9.0 sysnand like in the instructions.

--------------------- MERGED ---------------------------

At the moment, yup. But don't worry too much. You know we have that verification only since yesterday, and brick rate was low since v0.71?

Thanks ill do a reset and let you know how it goes!


Edit:
Yay it booted into 2.1, ill continue with the rest of the guide.

 

[d0k3]

I could use (one or more) testers:
(COMING UP, JUST A FEW MINUTES)

This OTPHelper version should fix false alerts for downgrade validation, at least for stage 1 and new stage 0. For stage 2 you at least see that it may be due to fragmented files now. Only downgrade check has to be tested, with an unbricked v2.1 EmuNAND on your SD card.

 

[Darkgilson]

I could use (one or more) testers:
(COMING UP, JUST A FEW MINUTES)

This OTPHelper version should fix false alerts for downgrade validation, at least for stage 1 and new stage 0. For stage 2 you at least see that it may be due to fragmented files now. Only downgrade check has to be tested, with an unbricked v2.1 EmuNAND on your SD card.

Hi d0k3,

I just tried your new build.
I'm using new 3DS with sysnand on 9.2, and emunand downgraded to 2.1 + unbricked (with previous version available).
Only after that I triggered the new build, with the verification step :

Stage 0 : SUCCESS
Stage 1 : FAILED
Stage 2 : FAILED
#TDM success : 0
#TDM not found : 113
#APP success : 0
#App not found : 0
#App fragmented : 0

Shall I maybe restore my emuNAND_formatted.bin then proceed with the downgrade + unbrick with this version ?

 

[d0k3]

Hi d0k3,

I just tried your new build.
I'm using new 3DS with sysnand on 9.2, and emunand downgraded to 2.1 + unbricked (with previous version available).
Only after that I triggered the new build, with the verification step :

Stage 0 : SUCCESS
Stage 1 : FAILED
Stage 2 : FAILED
#TDM success : 0
#TDM not found : 113
#APP success : 0
#App not found : 0
#App fragmented : 0

Shall I maybe restore my emuNAND_formatted.bin then proceed with the downgrade + unbrick with this version ?

Thanks for testing!

If you can, try this:
http://workupload.com/file/5hVM0uTJ

This should work as intended.

 

[Darkgilson]

Thanks for testing!

If you can, try this:
http://workupload.com/file/5hVM0uTJ

This should work as intended.

Stage 0 : SUCCESS
Stage 1 : SUCCESS
Stage 3 : SUCCESS

Validate EmuNAND DOwngrade: succeeded !


I'll complete the arm9loaderhax tutorial. It's the first time I'm doing it, crossing my fingers !

 

[inhumano]

Old 3dsXL

Validation Stage 0: SUCCESS
Validation Stage 1: SUCCESS
Validation Stage 2: SUCCESS

Validate EmuNAND Downgrade: succeeded!

Press B to return, START to reboot.

 

[d0k3]

Old 3dsXL

Validation Stage 0: SUCCESS
Validation Stage 1: SUCCESS
Validation Stage 2: SUCCESS

Validate EmuNAND Downgrade: succeeded!

Press B to return, START to reboot.

Great! Thanks a ton! That one is good to go, btw.

--------------------- MERGED ---------------------------

Stage 0 : SUCCESS
Stage 1 : SUCCESS
Stage 3 : SUCCESS

Validate EmuNAND DOwngrade: succeeded !


I'll complete the arm9loaderhax tutorial. It's the first time I'm doing it, crossing my fingers !

Thanks, both of you. Good to go, this one!

 

[d0k3]

I was on 9.0 with i downgraded, but have not restarted to start up 2.1 as i was not sure if it would brick it or not.

But seems like there is nothing else i can do except restart and hope it works.

If it does work i'll complete the process restore my backed up 9.0 sysnand like in the instructions.

--------------------- MERGED ---------------------------



Thanks ill do a reset and let you know how it goes!


Edit:
Yay it booted into 2.1, ill continue with the rest of the guide.

If you have some time at your hands, after finishing this - could you recheck your EmuNAND with the new build I posted above?

 

[grubgrub]

If you have some time at your hands, after finishing this - could you recheck your EmuNAND with the new build I posted above?

Thanks for your help and all the the work you putting into this protect.
I just completed the installation of the A9LH and am using Aureinand from following the video tutorial.

To test this out, do i have to downgrade the emunand to 2.1 again?

 

[Deleted member 373223]

nvm

 

[d0k3]

Thanks for your help and all the the work you putting into this protect.
I just completed the installation of the A9LH and am using Aureinand from following the video tutorial.

To test this out, do i have to downgrade the emunand to 2.1 again?

You just have to restore the v2.1 image to your EmuNAND. But wait for a bit, I need to check some things about that build. More later...

 

[inhumano]

With this build "OTPHelper-20160320-225655.zip"

Checking title 0004013000008002...
TMD not found or corrupt


Validation Stage 0: SUCCESS
Validation Stage 1: FAILED
Validation Stage 2: FAILED
# TMD success       : 112
# TMD not found     :   1
# APP success       : 112
# APP not found     :   0
# APP fragmented    :   0

 

[d0k3]

With this build "OTPHelper-20160320-225655.zip"

Checking title 0004013000008002...
TMD not found or corrupt


Validation Stage 0: SUCCESS
Validation Stage 1: FAILED
Validation Stage 2: FAILED
# TMD success       : 112
# TMD not found     :   1
# APP success       : 112
# APP not found     :   0
# APP fragmented    :   0

This could be an incomplete downgrade, just saying.

Everyone, you can try the downgrade checker in this new test build:
http://workupload.com/file/qI5946yL

Let me know about the results!

 

[inhumano]

@d0k3 with this build "OTPHelper-20160320-225655.zip"


2 successful downgrades and the same error (I already have a9lh on my Old 3ds XL)

 

[d0k3]

@d0k3 with this build "OTPHelper-20160320-225655.zip"


2 successful downgrades and the same error (I already have a9lh on my Old 3ds XL)

We will find out, no worries

Maybe, if you have time, retry with this one?
http://workupload.com/file/qI5946yL

 

[trees2]

We will find out, no worries

Maybe, if you have time, retry with this one?
http://workupload.com/file/qI5946yL

Switching to your new build changed my results...

Old build:

Validation Stage 0: SUCCESS
Validation Stage 1: FAILED
Validation Stage 2: FAILED
# TWL titles        :   4
# TMD success       : 107
# TMD not found     :   1
# APP success       : 107
# APP not found     :   0
# APP fragmented    :   0

New build:

Validation Stage 0: SUCCESS
Validation Stage 1: SUCCESS
Validation Stage 2: SUCCESS
# TWL titles        :   4
# TMD success       : 108
# TMD not found     :   0
# APP success       : 108
# APP not found     :   0
# APP fragmented    :   0

Thanks much for being so responsive to the community <3

 

[Tigrokai]

whenever I try to validate SysNAND downgrade, I get a "FIRM0 hash mismatch" message, saying the downgrade failed. I verified SysNAND itself and it passes, but I'm still afraid to reboot. I can't restore sysnand from a backup (slot0x5 image, you can't inject this) so am I safe to reboot or what are my options?