Tutorial  Updated

OTP Guide

Full Guide Release!

https://plailect.github.io/OTP/

All regions now supported!

If you appreciate this guide and the work I put into maintaining it, I accept donations through both Bitcoin and PayPal.

If you felt like the guide helped you out then I'd really appreciate it! If I get enough I may buy a 2DS for testing hardware stuff so I don't break another N3DS.

If the guide didn't help you out then I'm really sorry about that :(
 
Last edited by Plailect,
Can't wait to do it. But if I understand correctly, 2ds users should wait, right ? But wait for what exactly ?

From what I understand, aside from the 2DS's downgrading issues, O3DS (including 2DS) also has no CFW to actually boot after installing arm9loaderhax, so there's not much of a point aside from getting your OTP for future use.
 
Well then, I'm definitely glad I didn't install on my softmod o3ds.

Even if a Linux-compiled build hadn't bricked you, you would've been left with a temporarily unusable O3DS (unless you had a hardmod), since there are no A9LH CFW payloads that will boot on O3DS yet.
 
Out of interest, what is the reason why you can't just downgrade sysnand to 2.1 directly on n3DS? I have a hard mod if that makes any difference...
 
It could be months until cfws start utilizing the a9lh,not sure how successful this will even turn out considering the end user needs to know how to either compile the a9lh to work or know someone that can do it for them provided they take the huge risk of getting the otp and potentially get a bricked console unless they have a hardmod which most end users do not currently have. What else can a9lh do for the end user besides making sysnand more usable with the ability to install cias on it? Unless someone makes a program that ensures at least 60-100% non bricking downgrade and upgrade process for end users who don't know squat about this stuff I don't see much success becoming of this pretty awesome way to make 3ds/2ds systems even more awesome.
 
Out of interest, what is the reason why you can't just downgrade sysnand to 2.1 directly on n3DS? I have a hard mod if that makes any difference...

I would guess that you probably can if you want, but it's just safer for those of us without a hardmod. Hopefully we'll also see a modded CFW that we can boot to test our work afterwards. That'd probably make it about as safe as it can possibly be without a hardmod.
 
I would guess that you probably can if you want, but it's just safer for those of us without a hardmod. Hopefully we'll also see a modded CFW that we can boot to test our work afterwards. That'd probably make it about as safe as it can possibly be without a hardmod.
I might just try it today and see what happens.
 
Even if a Linux-compiled build hadn't bricked you, you would've been left with a temporarily unusable O3DS (unless you had a hardmod), since there are no A9LH CFW payloads that will boot on O3DS yet.
That was why I hadn't installed.
 
Nope. Unless you have a hardmod to dump your NAND and fix encryption.
Aha! So can I avoid mucking about with emunand with a hardmod like this?
  1. Dump xorpads
  2. Install sysupdater CIA in sysnand using pasta
  3. Update sysnand to 2.1 and let it brick
  4. Read bricked 2.1 sysnand using hard mod
  5. Fix encryption using the method in the OTP tutorial
  6. Rewrite 2.1 sysnand image using hard mod
Would that work?
 
Aha! So can I avoid mucking about with emunand with a hardmod like this?
  1. Dump xorpads
  2. Install sysupdater CIA in sysnand using pasta
  3. Update sysnand to 2.1 and let it brick
  4. Read bricked 2.1 sysnand using hard mod
  5. Fix encryption using the method in the OTP tutorial
  6. Rewrite 2.1 sysnand image using hard mod
Would that work?
And editing the NCSD header, as @capito27 said.
Yes, it should.
 

Site & Scene News

Popular threads in this forum