Hacking N3DS OTP Dumping Tips

[Hyoretsu]

I have already installed a9lh through otp-less mode, but I want to go back to 2.1 to dump my otp. Following all the security tips of this version of Plailect's guide: "https://github.com/Plailect/Guide_RedNAND/wiki/Part-4-(2.1.0-Downgrade)", is there any other things I could do to prevent a brick?

What should I do after dumping my otp.bin? Just restore my 9.2 SysNAND backup? Also, exactly in which step do I actually get my otp.bin?

 

[Quantumcat]

Why do you think you want your otp.bin? There's no use for it. You can update a9lh without it and now we have otp-less installation for N3DS, so if you uninstall a9lh you can install it again without needing your otp.bin.

 

[Hyoretsu]

Why do you think you want your otp.bin? There's no use for it. You can update a9lh without it and now we have otp-less installation for N3DS, so if you uninstall a9lh you can install it again without needing your otp.bin.

For the same reason that I have a9lh+EmuNAND (not exactly, but similar). For me, it's like the SysNAND backup: basically useless (if you have EmuNAND and don't use SysNAND), but good to keep.

 

[nooby89]

SysNAND with arm9loaderhax is best than EmuNAND!

 

[ExByte]

For the same reason that I have a9lh+EmuNAND (not exactly, but similar). For me, it's like the SysNAND backup: basically useless (if you have EmuNAND and don't use SysNAND), but good to keep.

There is no reason to retrieve the otp bin if you have an N3DS, it does not act like a SysNAND backup. If you plan to retrieve it either way then have the utmost caution while doing it.

 

[Hyoretsu]

There is no reason to retrieve the otp bin if you have an N3DS, it does not act like a SysNAND backup. If you plan to retrieve it either way then have the utmost caution while doing it.

Following all the security tips of this version of Plailect's guide: "https://github.com/Plailect/Guide_RedNAND/wiki/Part-4-(2.1.0-Downgrade)", is there any other things I could do to prevent a brick?

I believe that's the purpose of this thread.

What should I do after dumping my otp.bin? Just restore my 9.2 SysNAND backup? Also, exactly in which step do I actually get my otp.bin?

Also this.

 

[ExByte]

I believe that's the purpose of this thread.


Also this.

As far as preventing a brick I recommend that you put your N3DS to version 9.2 and then uninstall a9lh, there might be some complications if you don't uninstall a9lh but that's your call to make I'm only offering the safest way by starting fresh. From there you follow the beginning of the old Plailect guide. You should also have a 9.2 backup that doesn't contain a9lh since this will be your way back from 2.1. So as soon as you retrieve your otp bin, which will be after you downgrade to 2.1, restore your 9.2 backup and re-install a9lh using your otp bin since you'll already have it by then.

 

[Hyoretsu]

As far as preventing a brick I recommend that you put your N3DS to version 9.2 and then uninstall a9lh, there might be some complications if you don't uninstall a9lh but that's your call to make I'm only offering the safest way by starting fresh. From there you follow the beginning of the old Plailect guide. You should also have a 9.2 backup that doesn't contain a9lh since this will be your way back from 2.1. So as soon as you retrieve your otp bin, which will be after you downgrade to 2.1, restore your 9.2 backup and re-install a9lh using your otp bin since you'll already have it by then.

In what step do I actually get the otp.bin? How do I launch homebrew on 2.1?

So, just downgrade to 2.1 (Already on 9.2 with a pre-a9lh backup. Should I also make a backup of my EmuNAND and my microSD?), get my otp.bin with OTPHelper, restore pre-a9lh 9.2 backup, install a9lh through otp method (Using the a9lh version for O3DS, right?) and restore my 9.2 backup through Hourglass9 (If the answer for the first question was yes, I should presume that I have to restore my EmuNAND and microSD's backups as well?)?

 

[ExByte]

In what step do I actually get the otp.bin? How do I launch homebrew on 2.1?

So, just downgrade to 2.1 (Already on 9.2 with a pre-a9lh backup. Should I also make a backup of my EmuNAND and my microSD?), get my otp.bin with OTPHelper, restore pre-a9lh 9.2 backup, install a9lh through otp method (Using the a9lh version for O3DS, right?) and restore my 9.2 backup through Hourglass9 (If the answer for the first question was yes, I should presume that I have to restore my EmuNAND and microSD's backups as well?)?

You get your otp.bin in Part 5, Section 2, Step 3, right after you select full install. You don't technically launch homebrew normally in 2.1, the guide will give you a link to go to which opens up a program that will install a9lh right there. From that point foward you'll be on 2.1 a9lh with your otp.bin in a folder called "a9lh". You then use the payload system from Luma to launch hourglass9 and restore your nand backup while keeping a9lh. You will then be on 9.2 SysNAND with a9lh installed and have your otp.bin. (Sorry for earlier, I was talking about an older version of plailect's guide and got it mixed up with this one. I also recommend backing up everything you have just in case, including sd card contents.)

 

[annson24]

If you're already on a9lh-less 9.2 I suggest starting here

https://plailect.github.io/Guide/decrypt9-(browser)

Sent from my SM-G935F using Tapatalk

 

[trinhno]

Do a CTRNand transfer to 2.1 and dump the OTP using OTPhelper.

 

[Hyoretsu]

Do a CTRNand transfer to 2.1 and dump the OTP using OTPhelper.

So, just make backups of EmuNAND, microSD and SysNAND (already have a9lh), downgrade to 2.1, get my otp.bin with OTPHelper, restore SysNAND backup keeping a9lh?

Also, how do you launch homebrew while on 2.1?

 

[Quantumcat]

So, just make backups of EmuNAND, microSD and SysNAND (already have a9lh), downgrade to 2.1, get my otp.bin with OTPHelper, restore SysNAND backup keeping a9lh?

Also, how do you launch homebrew while on 2.1?

You don't launch homebrew on 2.1. You just run SafeArm9Installer.

 

[Hyoretsu]

So delete a9lh, have pre-a9lh 9.2 SysNAND, 11.2 EmuNAND and microSD backups and follow Plailect's from part 4 like it was my first time?

 

[gkoelho]

So delete a9lh, have pre-a9lh 9.2 SysNAND, 11.2 EmuNAND and microSD backups and follow Plailect's from part 4 like it was my first time?

Like WHY will you do this? You have made the riskier process to install al9h and now you are going to delete everything just to grab a useless file? This doesnt make sense at all.

 

[Hyoretsu]

Like WHY will you do this? You have made the riskier process to install al9h and now you are going to delete everything just to grab a useless file? This doesnt make sense at all.

For the same reason that I have a9lh+EmuNAND (not exactly, but similar). For me, it's like the SysNAND backup: basically useless (if you have EmuNAND and don't use SysNAND), but good to keep.

Sometimes, I think that people just don't read the entire thread (that's super small).

If you know the steps to get it without uninstalling a9lh, please tell me (Seriously, I'd love to hear it).

 

[Ryccardo]

If you know the steps to get it without uninstalling a9lh, please tell me (Seriously, I would love to hear it).

There aren't any, because running a 3.0+ kernel causes the OTP to be locked until the console is hard rebooted...

...A9LH itself is called that way because it's an exploit in Arm9Loader; Arm9Loader is part of the N3DS kernel (yes A9LH means you're installing one even on O3DS), and there are no 1.x or 2.x N3DS kernels

(Even if they existed in a parallel universe, they might not even have used Arm9Loader)

 

[Urbanshadow]

Sometimes, I think that people just don't read the entire thread (that's super small).

If you know the steps to get it without uninstalling a9lh, please tell me (Seriously, I'd love to hear it).

I am more curious about why would you want your otp. If you are up to something, it's fine if you don't tell, but either: a) You are tampering in uncharted waters or b) arm9loader already has/provides what are you looking for.

 

[Hyoretsu]

I am more curious about why would you want your otp. If you are up to something, it's fine if you don't tell, but either: a) You are tampering in uncharted waters or b) arm9loader already has/provides what are you looking for.

I just want to keep a backup of it, because silly reasons (Literally silly reasons, the same reason that makes me install EmuNAND on a9lh).

 

[gkoelho]

I just want to keep a backup of it, because silly reasons (Literally silly reasons, the same reason that makes me install EmuNAND on a9lh).

On other words, for no reason.

Well, do what you feel is best, there is no shortcut anyway. Go to a vanilla 9.2 backup, making sure you are not keeping al9h AND is on 9.2 and then do al9h normal process. Very much wasted time.