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,
Yea but it just needs to check everything is valid after it creates the modified sysnand.bin then any bricks that occur from downgrading will be down to that step alone. No user errors...well... less user errors.
yep basically a real 'noob proof' method. you hear us developers make this a thing!
 
  • Like
Reactions: MRDOCA
Not sure the last part of what you're asking. Are you asking how to return from 2.1? It's step 4 of the guide. You should be using Decrypt9 via browser to restore the emu/sys backups you made in step 1.
like, my sysnand is still on 9.2 and i still have menuhax installed. do i just run decrypt9 and restore my emu backup?
i'm just really cautious after all of this bricking :x
 
For the ones that bricked, do you still have your original bricked emunand as well as the processed nand? could you folks check the md5/sha?
My processed emuNAND and bricked emuNAND have different hashes. I don't think it'd be any use for me to provide them because they're unique to my console.
 
This thread in a nut shell

ROA15hA.jpg
 
like, my sysnand is still on 9.2 and i still have menuhax installed. do i just run decrypt9 and restore my emu backup?
i'm just really cautious after all of this bricking :x

Is your current emunand the bricked 2.1? If you just want to back out, you could just run decrypt9 from sysnand and restore your emunand backup.
 
Last edited by ,
I'm at a total loss?? I even tried downgrading my 10.3 emuNAND to 9.2 (before I just cloned my sysNAND instead) and it didn't work either??? now i'm really wishing I had a hardmod
I'm on 9.2 and nada. It won't work. I've basically come to the conclusion that for poor saps like you and me, nothing we can do will help. I'm just hanging out in this thread now. All I can think of is deleting the cia, but no hardmod for me.
 
I'm on 9.2 and nada. It won't work. I've basically come to the conclusion that for poor saps like you and me, nothing we can do will help. I'm just hanging out in this thread now. All I can think of is deleting the cia, but no hardmod for me.

I thought of that too but that's definitely not a good idea probably.
I had my 10.3 emuNAND a few days ago, and then I came across this forum and downgraded it to 2.1 just to see what would happen? It successfully downgraded, but I didn't know it wouldn't load and I'd have to flash it to sysNAND so I just restored my 10.3 emuNAND..............and now I'm kicking myself for doing that. ****
 
I thought of that too but that's definitely not a good idea probably.
I had my 10.3 emuNAND a few days ago, and then I came across this forum and downgraded it to 2.1 just to see what would happen? It successfully downgraded, but I didn't know it wouldn't load and I'd have to flash it to sysNAND so I just restored my 10.3 emuNAND..............and now I'm kicking myself for doing that. ****
Yeah I have a 2.1 emunand backup too, but it was never Timyformated so I'm weary of using it.
 
WAIT WAIT WAIT, hypothetically, could you flash the "processed" emunand.bin back to emunand to make sure its working fine before flashing to sysnand?
 
WAIT WAIT WAIT, hypothetically, could you flash the "processed" emunand.bin back to emunand to make sure its working fine before flashing to sysnand?

That doesn't work on an N3DS (it's bricked for a reason - being the N3DS never supported that FW)
Basically what this process does is write a O3DS header into the beginning region (0x200) of that emunand image. (so it boots up almost pretending its an O3DS.
 

Site & Scene News

Popular threads in this forum