Homebrew [RELEASE] OTPHelper - OTP dumping & downgrade helper

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 156,373
  • Replies Replies 801
  • Likes Likes 61
Curious question! Why did you change name to RedNAND than emuNAND? I know it's the same thing but just curious.
 
What is the use of otp0x108? It doesn't seem to be used by anything atm.
https://github.com/Plailect/Guide/issues/1

0x108 includes the TWL ID, which isn't currently used for anything but may be in the future

@d0k3, how does ExpandOtp work? I've digging through the src at moment. Can any version exploited 9.x firm get it? What about those on 10.x Al9h installed, will it be valid or do they need to restore back to 9.x?

Oh I see, it checks you have otp.bin and amends it into new file.
 
Last edited by Glix,
https://github.com/Plailect/Guide/issues/1



@d0k3, how does ExpandOtp work? I've digging through the src at moment. Can any version exploited 9.x firm get it? What about those on 10.x Al9h installed, will it be valid or do they need to restore back to 9.x?

Oh I see, it checks you have otp.bin and amends it into new file.
The expanded OTP should be valid as long as you have ARM9 access (which is always if you are able to run OTPHelper.
 
  • Like
Reactions: Conn0r
Here's a small v0.82 update, fulfilling some users wishes, this is new:
  • Minimum size RedNANDs (as created by EmuNAND9) are now handled by this
  • You can't shutdown / reboot while the SD is out anymore
  • Regular shutdown requires [START + RIGHT]
Just thought I'd say hi. This is actually my first post here on GBATemp but my brother and I were able to get the OTP files for 2 N3DS, 1 O3DSXL and 2 O3DS (one of which I somehow managed to do with a top screen that does not work) with this program and the OTP guide. Awesome job with this program and the others you've made so far. It was cool to see the progression of the program and how it became better with more feedback. I didn't have any issues with it but I like that you added the Decrypt9 functions to it as well. I'm currently trying to learn more about the coding itself but there is a lot of information regarding that and I am not too sure where exactly to start. I'm also trying to see how to find checksums as well for save files, such as the Mii Plaza save, although I know there is now an editor for that. But just wanted to say thank you for that program. It was and still is useful for me.
 
Just thought I'd say hi. This is actually my first post here on GBATemp but my brother and I were able to get the OTP files for 2 N3DS, 1 O3DSXL and 2 O3DS (one of which I somehow managed to do with a top screen that does not work) with this program and the OTP guide. Awesome job with this program and the others you've made so far. It was cool to see the progression of the program and how it became better with more feedback. I didn't have any issues with it but I like that you added the Decrypt9 functions to it as well. I'm currently trying to learn more about the coding itself but there is a lot of information regarding that and I am not too sure where exactly to start. I'm also trying to see how to find checksums as well for save files, such as the Mii Plaza save, although I know there is now an editor for that. But just wanted to say thank you for that program. It was and still is useful for me.
If you want to get a start, check for the easier projects (like HelloEntryPoint in my GitHub repo), then work from there.

Everyone, there's again, a small update, OTPHelper v0.83. This is new:
  • Fixed minimum size RedNAND restore & backup (restore to it would cause problems on the SD in some cases earlier)
  • Display current version on top of menu instead of build date
No April fools, promised, but if you're already traumatized following my other cruel joke, you can also wait until tomorrow with downloading this (there is no prank in here, though). Also, today might be a bad day to update your tools and get the OTP, cause basically everyone and their momma is out to prank you now :P.
 
Hi, I'm using the latest OTPHelper, and so far followed most of the guide from Plailect, except one minor part. For the sysNAND backup, I made the backup using EMUNAND9 instead of OTPHelper (since the backup size matches, I thought it would be fine).

The redNAND setup seems to be producing a minimum size redNAND by default, so the redNAND backup is smaller. I thought it is normal.

I managed to boot into 2.1 and dumped otp.bin, but whenever I'm trying to restore my original sysNAND now, it says:

Small EmuNAND, using minimum size...
No usable file found
SysNAND Restore: failed!​


My NAND is Toshiba, so it is 1.8GB NAND backup. Is there anything wrong here?

EDIT: looking at the changelog, it seems that the small redNAND support is the one causing the issue; now I'm using 0.81 to restore.
 
Last edited by pscytheology,
I'm on step 4, section IV of the guide, on O3DS XL. Everything went down successfully up until now, all of my backups match the sizes stated in the wiki (my original backup size matches Samsung's, the updates I downloaded from the guide match Toshiba's).

After dumping my OTP I'm now trying to restore my sysnand_original.bin (988,807,168 bytes). Getting this error (from the log):

"Small EmuNAND, using minimum size... Use arrow keys and <A> to choose a file sysNAND_original.bin Opening sysNAND_original.bin ... NAND backup has the wrong size! SysNAND Restore: failed!

Press B to return, START to reboot."

Please tell me what's the best course of action from this point. I tried, as the guide said, to redownload and replace the OTPHelper files (v0.83), and verify the integrity of my SD card.
 
Hi, I'm using the latest OTPHelper, and so far followed most of the guide from Plailect, except one minor part. For the sysNAND backup, I made the backup using EMUNAND9 instead of OTPHelper (since the backup size matches, I thought it would be fine).

The redNAND setup seems to be producing a minimum size redNAND by default, so the redNAND backup is smaller. I thought it is normal.

I managed to boot into 2.1 and dumped otp.bin, but whenever I'm trying to restore my original sysNAND now, it says:

Small EmuNAND, using minimum size...
No usable file found
SysNAND Restore: failed!​


My NAND is Toshiba, so it is 1.8GB NAND backup. Is there anything wrong here?

EDIT: looking at the changelog, it seems that the small redNAND support is the one causing the issue; now I'm using 0.81 to restore.
I'm on step 4, section IV of the guide, on O3DS XL. Everything went down successfully up until now, all of my backups match the sizes stated in the wiki (my original backup size matches Samsung's, the updates I downloaded from the guide match Toshiba's).

After dumping my OTP I'm now trying to restore my sysnand_original.bin (988,807,168 bytes). Getting this error (from the log):

"Small EmuNAND, using minimum size... Use arrow keys and <A> to choose a file sysNAND_original.bin Opening sysNAND_original.bin ... NAND backup has the wrong size! SysNAND Restore: failed!

Press B to return, START to reboot."

Please tell me what's the best course of action from this point. I tried, as the guide said, to redownload and replace the OTPHelper files (v0.83), and verify the integrity of my SD card.

The last release introduced some (non-critical!) trouble with RedNANDs. Get OTPHelper v0.84 from here.
 
  • Like
Reactions: pscytheology

Site & Scene News

Popular threads in this forum