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

 

[Xenon Hacks]

You're the first person I've seen report the same issue as me. I have a hardmod, so I could recover and try again, but I only got the same result

When you copy the first 200 offset from the O3DS header and paste into your 2.1 emunand are you clicking paste write? Also are you flashing that modified emunand to your sysnand?

 

[daxtsu]

This is almost certainly a stupid question but: Could you get your OTP from Emunand version 2.x? For instance, use menuhax to cold boot into emunand and downgrade that then floow the guide, etc?

No, because by the time your CFW boots, the OTP was already locked by the 9.x system that ran before your CFW. When you boot a CFW as it is now, it doesn't do a full reboot, which would unlock the OTP.

 

[hisagishi]

No, because by the time your CFW boots, the OTP was already locked by the 9.x system that ran before your CFW. When you boot a CFW as it is now, it doesn't do a full reboot, which would unlock the OTP.

Nope, Its already been thought of a million times

Right, sorry about bringing it up for the umpteenth time

Thanks for taking the time to explain it.

 

[Plailect]

Revision 2 has released!

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

 

[runetoonxx2]

working on it

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

Lets whip out that old 8 gb sd so i dont need to reinstall every cia

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

AND YES DOWNLOADED STARTING TO FOLLOW GUIDE

 

[hisagishi]

Currently using a gateway card + emunand.

Sysnand = 4.2 Emunand = 9.2

Was thinking of going with a menuhax coldboot RXtools but should I wait for this? I don't really have a reason to change my current gateway setup except to make playing DS games a bit more convenient. Would this be worth the wait? What types of things can you potentially be able to do with this?

 

[Kirino]

wait will this work with a 128 gig microsd? i have 16gig micro sd but i dont to set up emunand again

 

[runetoonxx2]

Revision 2 has released!

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

one question the sha 256 is that for the otp or no?

 

[JacksonS]

Revision 2 has released!

Thank you, kind soul.

 

[Just Passing By]

one question the sha 256 is that for the otp or no?

The sha 256 is for the downgrade packs.

 

[daxtsu]

Revision 2 has released!

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

I suggest eventually adding a FAQ to it for things like what can be done with it and such, since those sorts of questions are starting to be asked more often.

Currently using a gateway card + emunand.

Sysnand = 4.2 Emunand = 9.2

Was thinking of going with a menuhax coldboot RXtools but should I wait for this? I don't really have a reason to change my current gateway setup except to make playing DS games a bit more convenient. Would this be worth the wait? What types of things can you potentially be able to do with this?

Benefits right now:

1. 100% boot rate, nothing can get in its way of failing (unlike MenuHax, where it can fail in two places: on boot (white screen/yellow screen), and when launching your CFW)
2. ~8-10 second boot time versus 20+ (this varies based on your SD card size though)
3. Super stable 3D works out of the box on N3DS

it has risks though. You can brick in three places: during the downgrade, during the restoration of 9.2, and when installing A9LH itself. The new guide should dramatically lower the risks, however.

Possible future benefits:

1. Bootmii-like solutions, where you can basically be immune to most bricks without a hardmod
2. Boot manager menus can eventually be ported over to boot sysNAND, emuNAND, or whatever, once we have graphics output
3. Boot other operating systems such as Linux or maybe BSD (no, not Windows)
4. No more need for emuNAND once things like NATIVE_FIRM update blocking is done (but you can still use emuNAND if you want to).

Basically, with A9LH you own the ARM9 CPU from the very beginning, so you can do just about whatever you want.

 

[runetoonxx2]

kk ty jpb

 

[Plailect]

one question the sha 256 is that for the otp or no?

It's for the region packs. All of the required software is bundled into one download now for convenience.

 

[runetoonxx2]

The sha 256 is for the downgrade packs.

thank god they match

 

[Just Passing By]

thank god they match

Lol I mean if they don't then just redownload the packs...

 

[runetoonxx2]

welp time to start by setting up a fresh new emunand and a fresh new system

 

[Just Passing By]

Does the sd card still matter? Or can we use SDXC?

 

[Kirino]

Does the sd card still matter? Or can we use SDXC?

i second this

 

[Plailect]

Does the sd card still matter? Or can we use SDXC?

This does not change what SD cards can be used. SDXC support wasn't added until after 2.1.

 

[SirByte]

Currently using a gateway card + emunand.

Sysnand = 4.2 Emunand = 9.2

I am in the same boat as you are (SysNAND 4.1 and plenty of EmuNAND backups, including 9.2). I wonder if in R2 the xorpad generation is going to be an issue as our sysnand differs from our emunand.

Is there going to be an issue to temporarily flash GW 9.2 emunand to sysnand and start from there?