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

 

[grafate]

I think the guide changed a bit here and there in the last 24 hours. I want to give my input as I tested the guide with a hardmodded N3DS XL and initally after using OTPhelper to unbrick the 2.1 emunand I recall the guide saying use decrypt9 after. That was a no go as it will not do a complete inject emunand to sysnand. After restoring I just used OTPhelper for all steps and it did it fine. I meant to give this feedback yesterday but see it is already corrected.

 

[Hyura]

I think the guide changed a bit here and there in the last 24 hours. I want to give my input as I tested the guide with a hardmodded N3DS XL and initally after using OTPhelper to unbrick the 2.1 emunand I recall the guide saying use decrypt9 after. That was a no go as it will not do a complete inject emunand to sysnand. After restoring I just used OTPhelper for all steps and it did it fine. I meant to give this feedback yesterday but see it is already corrected.

Does this apply only for the New 3DS?

 

[Plailect]

So I'm on the last parts of part 4 where you restore your system. The part that confuses me states:

1. Delete the folders from the inside of the Nintendo 3DS folder on your SD card that are not in the Nintendo 3DS folder you copied to your computer in Section I (the Nintendo 3DS folder on your SD card should now look the same as the one from Section I)

Am I basically just copying and pasting the Nintendo 3DS folder I backed-up in the first part under "Prep Work" or do I have to manually go in and delete files that don't match up with the same filesize as the original Nintendo 3DS folder?

In your backup there will be 2 folders in "Nintendo 3DS", in your SD card there will be 3. You can delete the third one that isn't in the backup folder.

 

[uribemaster]

Hey guys so i did everything to a tee but when trying to boot into emundand, i get an infinite bootloop. Idk if it is because emunand has menuhax but how can i remove it if i can't boot into it. I also tried booting into homebrew browser and no dice

 

[boymatkieng]

I had successful get otp from New 3DS XL and I continue to get it in my 2DS but i am stuck in tiny format emunand.
Can a 2DS system downgrade to 2.1 and not stuck in 3d mode active ?

Sorry for my bad language. Thanks.

 

[DjoeN]

2 tries, and always get a bricked N3DS (hardmodded)
doing my 3th run now, but with a full clean sysnand and a clean emunand and a new SD
(New SD, formatted sysnand, created emunand with Gateway menu, updated emunand to 10.6, tinyformatted etc...)
atm, fixing bricked emunand with OTP, hope this time it works out fine.

[EDIT]
- Yes it worked
(still 2 N3DSXL systems to go :/ , but i'll do the extra steps to start from a clean sysnand and clean emunand)

 

[moghedien]

Trying on my N3DS XL and I made it to Part 4, Section II, Step 22/23.
My SysNAND boots but as soon as the home menu icons finish loading I get an error message saying:

An error has occurred.
Hold down the POWER Button to
turn off the power, then turn it on
and try again.

For help, visit support.nintendo.com

Am I boned?

Edit: Seems like it crashes when it's about to display the Health & Safety icon, maybe it's an issue with the injected FBI? Either way, I can't seem to launch anything before it crashes so I guess it's ruined

Edit 2: The recovery was working so I tried updating to 10.6 and now it wont boot at all, just a black screen. Guess I'll have to attempt a hard mod.

 

[uribemaster]

Ok so i restored a nand vackup and removed menuhax on both nands and still get an infinite bootloop. Any help?

 

[DjoeN]

I would say, create a new fresh emunand from sysnand and try again

 

[uribemaster]

Well it seems like the guide has been updated to upgraded sysnand. Did that tutorial and it worked. Thanks !

 

[Ev1l0rd]

So to anyone who is trying out step 5, I would like to note that if you don't want a perma SysNAND hax, but have an guaranteed EmuNAND, you can go into older revisions of the pages to use that guide instead (note that these are pages for when the guides were still separated, so don't choose the wrong one!):

• O3ds(XL)/2ds link
• N3ds(XL) link

I am not responsible if these guides brick your 3ds, shoot your wife or burn your house down.

If this guide bricks your wife, shoots your house and burns your 3ds, you are doing it right.

 

[DjoeN]

Well i like to say, for those on a NON modded N3DS(XL)
It doesn't hurt to do the extra steps of running your bricked emunand through the old script to fix it,
then compare it with your emunand that OTPHelper fixed before flashing it to sysnand.
Would i have done this the first time, i didn't had to do everything 3 times (luckily hardmodded)

So it would be a good thing that the unbrick script from the old guide was still available on the guide.

 

[pbanj]

ill prob catch hell for this but i think it was a bad idea to have the guide make people use the sysnand from the get go. i think it should have stuck with the emunand and then shown them the guide for swapping nands if they want. more and more people seem to be having issue with the new guide using the sysnand

 

[calebsw]

Right this did not seem to work. Now I am out of ideass.


Anyone have an idea on how I can solve this? I'd rather not loose my streetpass data and such.

Did you ever figure out what was going on here? I want to upgrade to a9lh, but I don't want to switch to sysnand cfw if it means sacrificing all the streetpass data I've been accumulating.

 

[Kenchansyd]

Part 5:
42. Reboot, then open Decrypt9 from arm9loaderhax by holding X on boot, then go to "SysNAND File Options", then select the "Dump Health & Safety" option

Seaching title "Health&Safety (N3DS)"...
Method 1: Search in title.db
Method 2: Search in file system...
Failed!
Health&Safety Dump: Failed!

Press B to return, START to reboot.

Any Ideas guys???

 

[Cuphat]

Make sure you have the key files (slot0x05KeyY.bin, slot0x11key96.bin, slot0x25keyX.bin) in the root of your SD card. They are required for Decrypt9 to actually decrypt things.

 

[Cuphat]

While dumping another OTP, I was lamenting not having the OTP 0x108 on my personal 3DS. I decided to take a look at the extra 8 bytes that are new from the regular OTP dump. Is it really this simple?

 

[Hat_Man]

Went through and successfully completed this.

There's a weird side-issue that I thought I'd mention though: None of the tools recognise emuNAND or sysNAND dumps that have been set to read only by Windows/OSX unless you set them back to read/write. I was setting all my dumps to be backed up as read-only for obvious reasons.

 

[TBreaker]

1. How do I know my EmuNand was downgraded succesfully when I can't even boot it with CFW?
I don't want it to somehow beeing bricked without knowing that. I'm on O3DS 9.2.0 btw.
2. Should I restore my SysNand directly from 2.1.0 or can I do a cart update to 7.1.0 first?
3.

27. Open the eShop at least once to allow it to initialize databases
28. Launch the Health and Safety Application (which is now FBI) on EmuNAND
29. Navigate to TinyFormat.cia and press A to install
30. Press home to exit FBI, then launch TinyFormat using the home menu icon
31. Press Y to format EmuNAND
32. Reboot back into EmuNAND and complete initial setup without signing into your Nintendo Network ID
33. Repeat steps 27 through 32, this is not optional (in other words, you must TinyFormat your EmuNAND twice - if you do not, your device may brick when you downgrade)

So, if I repeat each step from 27 - 32 I end up having an EmuNand without initialized dbs, because last step is formating, right? Or should I initialize though?

 

[jefffisher]

1. How do I know my EmuNand was downgraded succesfully when I can't even boot it with CFW?
I don't want it to somehow beeing bricked without knowing that. I'm on O3DS 9.2.0 btw.
2. Should I restore my SysNand directly from 2.1.0 or can I do a cart update to 7.1.0 first?
3.

So, if I repeat each step from 27 - 32 I end up having an EmuNand without initialized dbs, because last step is formating, right? Or should I initialize though?

1 unfortunately you don't
2 restore sysnand directly from 2.1 you do it in otp helper which you will already have open.
3 yes you should initialize again