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

 

[Just Passing By]

Installer is now getting stuck on Exploiting arm9...
Even tried rxTools Pasta mode!

Keep trying. You may have to do it 10+ times.

Also pasta mode isn't needed. I feel like it's just a waste of time.

 

[SomeGamer]

Keep trying. You may have to do it 10+ times.

Also pasta mode isn't needed. I feel like it's just a waste of time.

Aaand, third time rxPasta, I'm cold booting into emuNAND now! Thanks to everyone who made this possible!

 

[Naked_Snake]

I ask again is it possible to downgrade my n3ds with safesys updater to 2.1, because this nand replacement in this guide IS NOT working

 

[FenrirWolf]

I ask again is it possible to downgrade my n3ds with safesys updater to 2.1, because this nand replacement in this guide IS NOT working

It is not. The reason you have to do the nand replacement thing is because there is no such thing as an official firmware 2.1 for N3DS. You have to create it manually with your nand dumps and the xorpad dumps and so on. If you were to try a direct downgrade via sysupdater, you would be 100% bricked because you would be installing unpatched O3DS firmware on your N3DS.

 

[MRDOCA]

Bricked. Dunno why. I'm looking over the guide and everything was to a T... oh well hardmod tomorrow and try again

Edit. What was the point of backing up the nand.fat16 stuff? They just sit in the first backup folder...

 

[Plailect]

Bricked. Dunno why. I'm looking over the guide and everything was to a T... oh well hardmod tomorrow and try again

More info please?

 

[Naked_Snake]

It is not. The reason you have to do the nand replacement thing is because there is no such thing as an official firmware 2.1 for N3DS. You have to create it manually with your nand dumps and the xorpad dumps and so on. If you were to try a direct downgrade via sysupdater, you would be 100% bricked because you would be installing unpatched O3DS firmware on your N3DS.

than i dont understand why i am getting an error when i try to downgrade the patched sysNAND created from the python script, its not to small at all it's exactly the same size as my other sysNAND/emuNAND dumps

 

[Plailect]

Edit. What was the point of backing up the nand.fat16 stuff? They just sit in the first backup folder...

Decrypt the NAND at a later point on o3ds, used by the script for n3ds. Try booting without the SD card.

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

than i dont understand why i am getting an error when i try to downgrade the patched sysNAND created from the python script, its not to small at all it's exactly the same size as my other sysNAND/emuNAND dumps

You should be downgrading before the nand is patched...

 

[ThinksAmoral]

Edit. What was the point of backing up the nand.fat16 stuff? They just sit in the first backup folder...

They are required along with the bricked emuNand to create a working sysNand for N3DS.

 

[MRDOCA]

Tryed. That. I figured out what went wrong. The new upload doesn't have a backup folder in section one so the xorpad files weren't where the py file was looking I guess. I didn't make a backup folder till just now. Well that's all I can think off.

 

[SomeGamer]

Tryed. That. I figured out what went wrong. The new upload doesn't have a backup folder in section one so the xorpad files weren't where the py file was looking I guess. I didn't make a backup folder till just now. Well that's all I can think off.

But you're told in the guide to create that.

 

[Naked_Snake]

Decrypt the NAND at a later point on o3ds, used by the script for n3ds. Try booting without the SD card.

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


You should be downgrading before the nand is patched...

In the guide it says put the emuNAND_bricked.bin in the folder than run python script copy over sysNAND.bin it creates and use that to downgrade, this is what im doing and still it's saying the file is to small

 

[Plailect]

Tryed. That. I figured out what went wrong. The new upload doesn't have a backup folder in section one so the xorpad files weren't where the py file was looking I guess. I didn't make a backup folder till just now. Well that's all I can think off.

So you saw the part of the guide where you backup your entire system, and just didn't? I'm struggling to see the logic here...

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

In the guide it says put the emuNAND_bricked.bin in the folder than run python script copy over sysNAND.bin it creates and use that to downgrade, this is what im doing and still it's saying the file is to small

Restart, you messed something up.

 

[MRDOCA]

Nah the old guide files had all the structures I just didn't think to add that myself. It's allgood it'll be fixed tomorrow. Question tho. Can I now move the nand out of the unbricked folder and rename to brickedemunand and rerun the script since it probably didn't do anything anyway? That way I can just restore that tomorrow and start the guide from there.

 

[Plailect]

Nah the old guide files had all the structures I just didn't think to add that myself. It's allgood it'll be fixed tomorrow. Question tho. Can I now move the nand out of the unbricked folder and rename to brickedemunand and rerun the script since it probably didn't do anything anyway? That way I can just restore that tomorrow and start the guide from there.

Yes. You must have the xorpads in the backup folder. Not optional.

 

[Naked_Snake]

So you saw the part of the guide where you backup your entire system, and just didn't? I'm struggling to see the logic here...

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


Restart, you messed something up.

probably this thing doesnt get created so i copied and renamed it
"CTRNAND Padgen 0x4" to nand.fat16.0x4.xorpad

 

[MRDOCA]

I did back up the whole system but didn't put the backup in a backup folder. I put it in "/section_1"

 

[Plailect]

I did back up the whole system but didn't put the backup in a backup folder. I put it in "/section_1"

I guess I'll add giant caps that says it is required.

 

[MRDOCA]

Lol yea maybe
I'm rerunning the script and yea it added the data this time...
So I'll try restore this sysnand to see if I'll be on 2.1 then I'll grab the otp then I'll be allgood.

 

[phil7g]

Hi everyone, I just want to share my bad experience
Yesterday I followed this exellent guide but ended up hard bricking my nand.
I thing the part with the python script windows.py didn't worked as it was supposed to and ended up flashing insted of my bricked emunand instead of the unbricked one. (even though the file sysnand.bin did created, but the process didn't seem normal, didn't see any command line or progess, the script just close as fast as it start.
Anyway it's not as bad as it seem, I will try to restore my nand with a hardmod.(Maybe it's better this way for the future.)
Do you thing that this bad process lock my nand so I will also need a raspberry pi to restore my nand?