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

 

[OrGoN3]

Hmm they might have changed the method of downgrading (highly unlikely), but from what I remember, you downgrade emuNAND, use D9 to extract emuNAND, do a little magic, and inject the downgraded emuNAND to sysNAND, and then you get your OTP. You say that you just downgrade emuNAND and get your OTP which would be unbelievable, but I'm pretty sure you can't.

No magic. After emunand downgrade, reboot into sysnand, run D9, backup emunand. My fault in that I wasn't being specific. Also, no idea why the site showed me an early post as the first new post. Sorry.

 

[Sukid]

I'm also having the issue in Step III where the browser just goes to "loading arm11.bin" and freezes, no flashing or anything. I haven't happened to stumble upon how to directly address this problem. x_x I know the firmware downgraded successfully, and I've also cleared history and cookies and initialized save data on the browser and so far no dice. Even used a different SD card with nothing but the arm11.bin on the root and that's it.

Using o3DS spider download. I notice in the cubic version there are more files than just the arm11.bin. Were those supposed to be in the spider version as well?

 

[pbanj]

I'm also having the issue in Step III where the browser just goes to "loading arm11.bin" and freezes, no flashing or anything. I haven't happened to stumble upon how to directly address this problem. x_x I know the firmware downgraded successfully, and I've also cleared history and cookies and initialized save data on the browser and so far no dice. Even used a different SD card with nothing but the arm11.bin on the root and that's it.

Using o3DS spider download. I notice in the cubic version there are more files than just the arm11.bin. Were those supposed to be in the spider version as well?

U should have 2 bins, iirc when I did mine it had an arm11 and an arm9 bin

 

[FenrirWolf]

Decrypt9 has two bins at least. I think there was only one for the OTP dumper.

 

[Sukid]

Yeah, the section III folder only has the arm11.bin and yeah as far as I've read the arm9.bin in section IV is only for decrypt9. :/

 

[Sev501]

For the life of me... I don't get it why the hashes don't match even tho it was already updated and fixed... I'm downloading the U pack for No Cubic ninja and this is my 4th download hahah....

And I always end up with that file checksum 42c......

Hmm?

 

[Just Passing By]

Then it's fine. Go for the downgrade.

 

[Sev501]

Then it's fine. Go for the downgrade.

Here we go.. Backing up SD card haha... And generating the files take time... Crossing my fingers for the downgrade. Praying everything goes smoothly...

 

[leerz]

For the life of me... I don't get it why the hashes don't match even tho it was already updated and fixed... I'm downloading the U pack for No Cubic ninja and this is my 4th download hahah....

And I always end up with that file checksum 42c......

Hmm?

3rd attempt, hashes are different from all 3! lol, bricking 3x

 

[N64]

just finished doing this on a n3ds

 

[Sukid]

welp I guess I screwed up massively. From everything I've read the problem of the browser freezing was due to an improper downgrade so I tried to find a game card I had that had a firmware update on it and in my infinite wisdom/panic(because this is a friend's 3ds) I picked Smash. Now I'm on 9.9 and sysupdater is either saying it can't check the cia files or just flat out freezing on me.

I downgraded it to 9.2 just fine before from 10.3 but it seems like 9.9 wants to put up a fight.

 

[FenrirWolf]

That's just sysupdater being sysupdater. Good luck with the fight.

 

[Sukid]

Well, finally downgraded. Not sure if it made much of a difference but I changed to the sysupdater download provided in the guide and that worked after a couple tries, for whatever reason.

So... preventing the issue of the browser not properly downgrading. Does that have anything to do with fully updating emunand before the downgrade? I had emunand on 9.2 before I downgraded it to 2.1.

Although one lesson learned: Use your own 3DS to learn to do a new hack before you try doing it on a friend's 3DS.

 

[leerz]

i keep bricking when moving 2.1 emunand to sysnand. 4th attempt, this time my .zip files were correct hash.

am I bricking because of the injected fbi on the h&s app?

 

[Sukid]

No, if that was the case I would have bricked as well. It seems like H&S just goes back to normal when you flash to sysnand. That said, if you think it might be, try injecting the vanilla h&s once you've done all you need to do with fbi. (I'll try that myself, never know. >.>)

 

[leerz]

I'm retrying with my 9.2 fresh emunand from virgin 9.2, the first 4 attempts were 10.5

 

[piratesephiroth]

i keep bricking when moving 2.1 emunand to sysnand. 4th attempt, this time my .zip files were correct hash.

am I bricking because of the injected fbi on the h&s app?

Is your emunand up to date? I downgrade fine with mine from 10.5 and it had DevMenu injected into H&S.

Also make sure there are no previous "updates" folder in the SD card, from previous 9.2 downgrades.

 

[leerz]

Is your emunand up to date? I downgrade fine with mine from 10.5 and it had DevMenu injected into H&S.

Also make sure there are no previous "updates" folder in the SD card, from previous 9.2 downgrades.

thanks for the reply

I'm retrying with my 9.2 fresh emunand from virgin 9.2, the first 4 attempts were 10.5

yes, even the CFW files were virgin, only ctrboot, rx, hb (with decrypt9) is there.

additional note: first attempts using emunand formatted through emunand9, -i'm retrying with a gw formatted emunand //reason for thinking this may be the culprit? well, gw formatted emunand work fine with emunand pc backup tools, whilst emunand9 formatted cards just crash and corrupt my emunand.
will hit back after the backups are done (makes it easier for me to retry )



--edit--

brick wall, still black screen,

I will try again with FILES only from the package. ,

I'm maybe using a different version of decrypt9/sysupdater/tinyformat from my current setup.


---question again--
before I re-do everything as stated only by the guide.

does it matter that I changed how this part was performed?

1. Following the options on the main menu, backup your emuNAND to emuNAND.bin.
2. Press (Select) on the main menu to eject your SD card, then rename emuNAND.bin to sysNAND.bin on the root of your SD card from your computer.
3. Reinsert your SD card into your 3DS and press (B).
4. Following the options on the main menu, restore your sysNAND from sysNAND.bin.

I skipped the rename part, after I backup the 2.1 emunand, I restored it directly via decrypt9 to sysnand

so my steps were

cfw setup (hb/rx etc)
unlink nands (tinyformat)
h&s injection, sysupdater
sysupdater dg to 2.1
decrypt9, backup emunand - emunand.bin
decrypt9, restore nand - emunand bin

I'm guessing the rename option part is just for safety?

 

[pbanj]

thanks for the reply

yes, even the CFW files were virgin, only ctrboot, rx, hb (with decrypt9) is there.

additional note: first attempts using emunand formatted through emunand9, -i'm retrying with a gw formatted emunand //reason for thinking this may be the culprit? well, gw formatted emunand work fine with emunand pc backup tools, whilst emunand9 formatted cards just crash and corrupt my emunand.
will hit back after the backups are done (makes it easier for me to retry )



--edit--

brick wall, still black screen,

I will try again with FILES only from the package. ,

I'm maybe using a different version of decrypt9/sysupdater/tinyformat from my current setup.


---question again--
before I re-do everything as stated only by the guide.

does it matter that I changed how this part was performed?



I skipped the rename part, after I backup the 2.1 emunand, I restored it directly via decrypt9 to sysnand

so my steps were

cfw setup (hb/rx etc)
unlink nands (tinyformat)
h&s injection, sysupdater
sysupdater dg to 2.1
decrypt9, backup emunand - emunand.bin
decrypt9, restore nand - emunand bin

I'm guessing the rename option part is just for safety?

It needs to be renamed -_-

 

[piratesephiroth]

thanks for the reply

yes, even the CFW files were virgin, only ctrboot, rx, hb (with decrypt9) is there.

additional note: first attempts using emunand formatted through emunand9, -i'm retrying with a gw formatted emunand //reason for thinking this may be the culprit? well, gw formatted emunand work fine with emunand pc backup tools, whilst emunand9 formatted cards just crash and corrupt my emunand.
will hit back after the backups are done (makes it easier for me to retry )



--edit--

brick wall, still black screen,

I will try again with FILES only from the package. ,

I'm maybe using a different version of decrypt9/sysupdater/tinyformat from my current setup.

After


---question again--
before I re-do everything as stated only by the guide.

does it matter that I changed how this part was performed?



I skipped the rename part, after I backup the 2.1 emunand, I restored it directly via decrypt9 to sysnand

so my steps were

cfw setup (hb/rx etc)
unlink nands (tinyformat)
h&s injection, sysupdater
sysupdater dg to 2.1
decrypt9, backup emunand - emunand.bin
decrypt9, restore nand - emunand bin

I'm guessing the rename option part is just for safety?

You don't need to rename anything. The NAND injection works with any name.
The only thing that considers the name is the sysNAND restore option, that automatically picks a NAND.bin file if it exists (no idea why).