Homebrew [RELEASE] OTPHelper - OTP dumping & downgrade helper

[Mister_Keevs]

I can't for the life of me get OTPHelper to boot. I put the arm9.bin and arm11.bin files in root and the OTPHelper folder in 3ds. I've tried it through Browserhax, straight from CtrBootManager and through Ninjhax 1.1b and 2.7. Black screen all the time...
Any ideas?

Edit: Tried the release before latest and it worked on the first try.

Same thing happened to me earlier. Are you by chance using an o3dsXL? Mine refused to boot v0.88 but v0.87 worked like a charm

 

[Shadowfied]

Same thing happened to me. What system you using? I have an o3dsXL and v0.88 refused to boot

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


Same thing happened to me earlier. Are you by chance using an o3dsXL? Mine refused to boot v0.88 but v0.87 worked like a charm

New 3DS XL, European. 9.2 SysNAND.

 

[fitz420]

Same thing happened to me earlier. Are you by chance using an o3dsXL? Mine refused to boot v0.88 but v0.87 worked like a charm

Same result for me. I did another 3ds last night for my daughter and 88 wouldn't boot. Tried like 10x. 87 booted fine. o3ds xl also

 

[d0k3]

I can't for the life of me get OTPHelper to boot. I put the arm9.bin and arm11.bin files in root and the OTPHelper folder in 3ds. I've tried it through Browserhax, straight from CtrBootManager and through Ninjhax 1.1b and 2.7. Black screen all the time...
Any ideas?

Edit: Tried the release before latest and it worked on the first try.

This new release (v0.89) fixes booting on the previously broken entrypoints.

 

[flow349]

Im on 2.1 with a new 3DS, but i was stupid and deleted my original sysnand.bin
Ist there any chance to get it to update?
I have a9lhax installed and can acces the payloads.

 

[d0k3]

Im on 2.1 with a new 3DS, but i was stupid and deleted my original sysnand.bin
Ist there any chance to get it to update?
I have a9lhax installed and can acces the payloads.

Oh well... See here. Best if you would find another NAND dump that you can restore from the current state. Also hold onto the emergency files, the dumped header is important. Maybe contact @slslasher about this, too? He's the first guy who managed to recover from that problem. Also, make sure you don't overwrite your A9LH installation (at least try not to).

 

[flow349]

Oh well... See here. Best if you would find another NAND dump that you can restore from the current state. Also hold onto the emergency files, the dumped header is important. Maybe contact @slslasher about this, too? He's the first guy who managed to recover from that problem. Also, make sure you don't overwrite your A9LH installation (at least try not to).

So far as i understand this, you need an functional nand backup, but i didnt have one.
Only a 2.1 emunand and the emergency files, ican acces decrypt9, hourglass9 and otphelper trough luma payloads.

The guy you named me says a hardmod would be useful(i know this thread) but i cant do it myself!

I have an new 3ds xl can i make an backup from this restore this to emunand and then inject my emergency files and otp (i didnt really know if these are useful)

What would happen if i used the recovery mode? Can i access decrypt9 after that?

I cant acces the homemenu (luma cfw already installed)

 

[EmceeKerser]

Constantly getting an APP fragmentation error on the internet browser title (9D02)

Any way to fix? Ive already tried installing the 10.7 internet browser (to match my FW) but Im still getting the error

 

[d0k3]

Constantly getting an APP fragmentation error on the internet browser title (9D02)

Any way to fix? Ive already tried installing the 10.7 internet browser (to match my FW) but Im still getting the error

Do what Plailect says and use GM9 to confirm the SHA-256 of that. It is all in the guide. Also, you are not running the downgrade checker on an 10.7 NAND, or do you?

 

[Kamihate]

So, i stuck on part 4.

Your region is: USA
Checking title 0004001000021000...
Checking title 0004001000021100...
Checking title 0004001000021200...
Checking title 0004001000021300...
Checking title 0004001000021400...
Checking title 0004001000021500...
Checking title 0004001000021700...
Checking title 0004001000021900...
Checking title 0004001000021A00...
Checking title 0004001000021B00...
Checking title 0004001000021D00...
Checking title 0004001000021E00...
Checking title 0004001000021F00...
Checking title 0004001B00010002...
Checking title 0004003000008A02...
Checking title 0004003000008A03...
Checking title 0004003000008F02...
Checking title 0004003000009002...
Checking title 0004003000009202...
Checking title 0004003000009302...
Checking title 0004003000009402...
Checking title 0004003000009602...
Checking title 0004003000009702...
Checking title 000400300000C502...
Checking title 000400300000C503...
Checking title 000400300000C802...
Checking title 000400300000C803...
Checking title 000400300000C902...
Checking title 000400300000CB02...
Checking title 000400300000CC02...
Checking title 0004009B00010202...
Checking title 0004009B00010402...
Checking title 0004009B00010602...
Checking title 0004009B00011402...
Checking title 0004009B00011602...
Checking title 0004009B00011D02...
Checking title 0004009B00011E02...
Checking title 0004009B00012302...
Checking title 0004009B00013302...
Checking title 0004009B00014002...
Checking title 0004009B00014102...
Checking title 0004009B00014202...
Checking title 0004009B00014302...
Checking title 0004009B00015302...
Checking title 000400DB00010302...
Checking title 000400DB00010502...
Checking title 000400DB00016302...
Checking title 000400DB00017302...
Checking title 0004013000001502...
Checking title 0004013000001503...
Checking title 0004013000001602...
Checking title 0004013000001702...
Checking title 0004013000001703...
Checking title 0004013000001802...
Checking title 0004013000001803...
Checking title 0004013000001A02...
Checking title 0004013000001A03...
Checking title 0004013000001B02...
Checking title 0004013000001B03...
Checking title 0004013000001C02...
Checking title 0004013000001C03...
Checking title 0004013000001D02...
Checking title 0004013000001D03...
Checking title 0004013000001E02...
Checking title 0004013000001E03...
Checking title 0004013000001F02...
Checking title 0004013000001F03...
Checking title 0004013000002002...
Checking title 0004013000002102...
Checking title 0004013000002103...
Checking title 0004013000002202...
Checking title 0004013000002203...
Checking title 0004013000002302...
Checking title 0004013000002303...
Checking title 0004013000002402...
Checking title 0004013000002403...
Checking title 0004013000002602...
Checking title 0004013000002702...
Checking title 0004013000002703...
Checking title 0004013000002802...
Checking title 0004013000002902...
Checking title 0004013000002903...
Checking title 0004013000002A02...
Checking title 0004013000002A03...
Checking title 0004013000002B02...
Checking title 0004013000002C02...
Checking title 0004013000002C03...
Checking title 0004013000002D02...
Checking title 0004013000002D03...
Checking title 0004013000002E02...
Checking title 0004013000002E03...
Checking title 0004013000002F02...
Checking title 0004013000002F03...
Checking title 0004013000003102...
Checking title 0004013000003103...
Checking title 0004013000003202...
Checking title 0004013000003203...
Checking title 0004013000003302...
Checking title 0004013000003303...
Checking title 0004013000003402...
Checking title 0004013000003502...
Checking title 0004013000003702...
Checking title 0004013000008002...
Checking title 0004013000008003...
Checking title 0004013800000002...
TMD not found or corrupt
Checking title 0004013800000003...
Checking title 0004013800000102...
Checking title 0004800542383841...
Is a TWL title, skipped
Checking title 00048005484E4441...
Is a TWL title, skipped
Checking title 0004800F484E4841...
Is a TWL title, skipped
Checking title 0004800F484E4C41...
Is a TWL title, skipped

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

WARNING: Validation Stage 1 failed!
!DO NOT RESTORE THIS TO SYSNAND!
Starting from scratch is recommended

Downgrade Validation failed!
You cannot continue here
One Click Setup: failed!

Press B to return, START to reboot.
======================

it says i don't have
title 0004013800000002...
What should i do?

 

[GerbilSoft]

it says i don't have
title 0004013800000002...
What should i do?

That's NATIVE_FIRM, which is rather important. You should restart from the beginning of this section; that is, restore EmuNAND to its previous state, then run the downgrade again.

 

[Kamihate]

So, i just messed everyfucking thing and now my o3ds XL power on but screens stay black. I've tried pull out sd, pull out bateries, and etc.
I can't enter on recovery mode, it just stay in that black screen FOR EVER

 

[GerbilSoft]

So, i just messed everyfucking thing and now my o3ds XL power on but screens stay black. I've tried pull out sd, pull out bateries, and etc.
I can't enter on recovery mode, it just stay in that black screen FOR EVER

...did you actually continue with the downgrade even though it said FAILED, rather than starting over by restoring EmuNAND?

 

[retrofan_k]

So, i just messed everyfucking thing and now my o3ds XL power on but screens stay black. I've tried pull out sd, pull out bateries, and etc.
I can't enter on recovery mode, it just stay in that black screen FOR EVER

Did you follow this below, if not you may have bricked it. Hard mod only to recover, if so.

"Validation Stage 1: FAILED" and "Validation Stage 2: FAILED"
THIS APPLIES ONLY TO .TMD RELATED ERRORS, NOT .APP RELATED ERRORS
If you got a .app related error, you should restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9..

1. Check otphelper.log to see which titles the TMD hash mismatches on
2. Download the latest release of GodMode9
3. Copy the GodMode9 folder from the GodMode9 zip to the /3ds/ folder on the root of your SD card
4. Get into the Homebrew Launcher on SysNAND through the entrypoint of your choice
5. Open GodMode9 (Be VERY careful with this tool, it can brick you if you delete something important with it)
6. Select (on bottom screen) emuNAND CTRNAND
7. Select title
8. Select the folder which has the same 8 characters as the beginning of the title that mismatched (for example, if you mismatched after Checking title 0004013000003202... then you would select the 00040130 folder)
9. Select the folder which has the same 8 characters as the end of the title that mismatched (for example, if you mismatched after Checking title 0004013000003202... then you would select the 00003202 folder)
10. Select content

The latest release of OTPHelper rarely shows false positives, but if you want to you can check manually just to be sure. To do this, press A on each .tmd and select "Calculate SHA-256" to manually compare to see if at least one of the .tmd files in each folder match a Sha256Sum tothis list.

If, in each folder, at least one of the .tmd files matches a hash on the list, this was a a false positive and you can use the following steps. If it is a New 3DS you should unbrick EmuNAND first. Go to "NAND Backup & Restore" -> "Clone RedNAND to SysNAND" then use "NAND Validation Options" -> "Validate SysNAND Downgrade" and confirm your SysNAND only has the same error as EmuNAND. If you get a NEW error after cloning RedNAND to SysNAND, restore SysNAND from SysNAND_original.bin, restore RedNAND from emuNAND_formatted.binand retry from Part 4 - Section II - Step 9. If you do not get a NEW error, continue with the guide, ignoring the error.

If, in any folder, none of the .tmd files match, then this was a legitimate downgrade error and you have been saved from a brick; you should restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9.

Check all of the titles that mismatch with this same method.

 

[Kamihate]

...did you actually continue with the downgrade even though it said FAILED, rather than restarting over by restoring EmuNAND?

No, i restarted. At first it booted on my sysnand, then i powered off and entered at homebrew channel, i read at the troubleshoot that i needed a firm.bin and inject it at emuNAND but i think i injected it in my sysNAND. So i downgrade my emunand to 2.1 and tried oneclick setup. It failed and i restarted to open my sysnand. For my surprise i got these dual black screens and can't go anyware

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

Did you follow this below, if not you may have bricked it. Hard mod only to recover, if so.

"Validation Stage 1: FAILED" and "Validation Stage 2: FAILED"
THIS APPLIES ONLY TO .TMD RELATED ERRORS, NOT .APP RELATED ERRORS
If you got a .app related error, you should restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9..

1. Check otphelper.log to see which titles the TMD hash mismatches on
2. Download the latest release of GodMode9
3. Copy the GodMode9 folder from the GodMode9 zip to the /3ds/ folder on the root of your SD card
4. Get into the Homebrew Launcher on SysNAND through the entrypoint of your choice
5. Open GodMode9 (Be VERY careful with this tool, it can brick you if you delete something important with it)
6. Select (on bottom screen) emuNAND CTRNAND
7. Select title
8. Select the folder which has the same 8 characters as the beginning of the title that mismatched (for example, if you mismatched after Checking title 0004013000003202... then you would select the 00040130 folder)
9. Select the folder which has the same 8 characters as the end of the title that mismatched (for example, if you mismatched after Checking title 0004013000003202... then you would select the 00003202 folder)
10. Select content

The latest release of OTPHelper rarely shows false positives, but if you want to you can check manually just to be sure. To do this, press A on each .tmd and select "Calculate SHA-256" to manually compare to see if at least one of the .tmd files in each folder match a Sha256Sum tothis list.

If, in each folder, at least one of the .tmd files matches a hash on the list, this was a a false positive and you can use the following steps. If it is a New 3DS you should unbrick EmuNAND first. Go to "NAND Backup & Restore" -> "Clone RedNAND to SysNAND" then use "NAND Validation Options" -> "Validate SysNAND Downgrade" and confirm your SysNAND only has the same error as EmuNAND. If you get a NEW error after cloning RedNAND to SysNAND, restore SysNAND from SysNAND_original.bin, restore RedNAND from emuNAND_formatted.binand retry from Part 4 - Section II - Step 9. If you do not get a NEW error, continue with the guide, ignoring the error.

If, in any folder, none of the .tmd files match, then this was a legitimate downgrade error and you have been saved from a brick; you should restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9.

Check all of the titles that mismatch with this same method.

Yes, i tried it many times re-downgrade and i mande step 9- about 30 times, with the same errors

 

[TheCyberQuake]

So, i just messed everyfucking thing and now my o3ds XL power on but screens stay black. I've tried pull out sd, pull out bateries, and etc.
I can't enter on recovery mode, it just stay in that black screen FOR EVER

Sounds like a brick to me, and only solution now would be to hardmod and flash one of your sysNAND dumps back onto it.

 

[d0k3]

No, i restarted. At first it booted on my sysnand, then i powered off and entered at homebrew channel, i read at the troubleshoot that i needed a firm.bin and inject it at emuNAND but i think i injected it in my sysNAND. So i downgrade my emunand to 2.1 and tried oneclick setup. It failed and i restarted to open my sysnand. For my surprise i got these dual black screens and can't go anyware

Yeah, that's a guaranteed brick. You injected it to the SysNAND, despite the warning. You should not have injected it at all, the FIRM partition (which is different from the NATIVE_FIRM app) was fine.

 

[Kamihate]

Sounds like a brick to me, and only solution now would be to hardmod and flash one of your sysNAND dumps back onto it.

Yeah, that's a guaranteed brick. You injected it to the SysNAND, despite the warning. You should not have injected it at all, the FIRM partition (which is different from the NATIVE_FIRM app) was fine.

I don't have a dump from hard mod, only a sysnand backup. So i must just leave my 3ds somewhere and let it R.I.P?

 

[d0k3]

I don't have a dump from hard mod, only a sysnand backup. So i must just leave my 3ds somewhere and let it R.I.P?

You can restore the SysNAND backup via hardmod, that's how it works. You should take your time reading the guide next time doing this, this brick could have been prevented.

 

[Kamihate]

You can restore the SysNAND backup via hardmod, that's how it works. You should take your time reading the guide next time doing this, this brick could have been prevented.

I read the guide, i just confused a little. i'll try hard mode with my sysnand backup from OTP. Thanks!