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,
Got it and worked! Don't forget to put arm9haxloader.bin on your root of sd card after installed hax. if you forgot this your 3ds will not boot. you can't turn on your 3ds.

Congrats, now breathe a sigh of relief. :)

but would there be any added benefit (other than emuNAND boot speed) for an o3DS?

Reliability (this will pretty much ALWAYS boot, unlike MenuHax) and eventual brick "immunity" (within reason, if A9LH gets corrupted or removed somehow then you're out of luck if you run into a nasty brick, which would require you to then get a hard mod)
 
Last edited by daxtsu,
but would there be any added benefit (other than emuNAND boot speed) for an o3DS?

How about the ability to be able to update your emunand to the latest firmware versions? Because you can bet that it won't be that long before a9h is the only way to have an up to date CFW.


It's arguably already superior with faster boot rates (for some of us it's as low as 8 seconds to boot emuNAND, not really any slower than sysNAND would ever take), no boot failures, and super stable 3D working out of the box.

It's only really lacking a boot menu to pick what you want to do, but CFWs like AuReiNand are working around that with button combos to boot sysNAND or emuNAND with different settings. I would guess within a month or two at the latest, we'll probably have boot managers ported over to it for a simpler time.

Well, except for that fact that it is still quite risky to do without a hardmod. Any idea when it will be stable enough for CFW to start requiring it because the a9h versions are the only ones still in development?

I think that almost all CFW developers are on it: rxTools, reiNAND (Rei already did a payload for a9lh), CakesFW (MassExplosion213 did the fork for a9lh)

Yes, but how long before CFW requires a9h (and thus OTP dumping) unless you want to be stuck with old, obsolete versions that can't even boot the latest system software.
 
Last edited by nl255,
How about the ability to be able to update your emunand to the latest firmware versions? Because you can bet that it won't be that long before a9h is the only way to have an up to date CFW.
What kind of bullshit is that ? The other entrypoints are still available. MSET entrypoints are still used and updated for newer versions of CFWs even if ninjhax is here now. Stop your bullshit.

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

Yes, but how long before CFW requires a9h (and thus OTP dumping) unless you want to be stuck with old, obsolete versions that can't even boot the latest system software.
See my previous reply.
 
What kind of bullshit is that ? The other entrypoints are still available. MSET entrypoints are still used and updated even if ninjhax is here now. Stop your bullshit.

Except that a9h is different from your standard entry point + kernel exploit otherwise it wouldn't be necessary to create a new fork for the a9h versions. Hopefully it won't be too difficult to maintain both the new a9h code and the old kernel exploit stuff.
 
Except that a9h is different from your standard entry point + kernel exploit otherwise it wouldn't be necessary to create a new fork for the a9h versions. Hopefully it won't be too difficult to maintain both the new a9h code and the old kernel exploit stuff.
It's not so different for a developer, as it is like a Brahma environment. The only reasons that forks have to be done is to remove the screen stuff as it's not done yet and make crash the payload, and to remove the CakeBrah/CakeHax payload (which are the 0x12000 first bytes). Almost everything is the same, and I guess that someone will do something for arm9loaderhax payloads to fix these issues, something like CakeBrah.
 
It's not so different for a developer, as it is like a Brahma environment. The only reasons that forks have to be done is to remove the screen stuff as it's not done yet and make crash the payload, and to remove the CakeBrah/CakeHax payload (which are the 0x12000 first bytes). Almost everything is the same, and I guess that someone will do something for arm9loaderhax payloads to fix these issues, something like CakeBrah.

I could have sworn that one or more developers have said that because of how a9h works would allow access to things that are not currently possible by current methods such as Brahma environments. Were they talking about possible new CFW features or something else?
 
I could have sworn that one or more developers have said that because of how a9h works would allow access to things that are not currently possible by current methods such as Brahma environments. Were they talking about possible new CFW features or something else?
New features: Yes
Letting old entrypoints/*hax users with old versions of their CFWs: no
 
I have right now my OTP and the console in 9.2. Its a OLD3DS and i didnt install it yet. Can i install Cakes,update the console via sysUpdater without NATIVE_FIRM and if i want,use later Gateway? Thanks.
 
  • Like
Reactions: ahezard
I have right now my OTP and the console in 9.2. Its a OLD3DS and i didnt install it yet. Can i install Cakes,update the console via sysUpdater without NATIVE_FIRM and if i want,use later Gateway? Thanks.
No.

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

So if I understand we just need to downgrade emunand to 2.x to get OTP?
No. The steps are to downgrade your sysNAND.
 
New features: Yes
Letting old entrypoints/*hax users with old versions of their CFWs: no

So what new CFW features will likely require a9h to work and will be unavailable to people using existing booting methods? Currently the only possibilities I can think of are DSIware/GBA games in emunand but apparently that is being worked on via patching rather than a9h specific stuff.
 
So what new CFW features will likely require a9h to work and will be unavailable to people using existing booting methods? Currently the only possibilities I can think of are DSIware/GBA games in emunand but apparently that is being worked on via patching rather than a9h specific stuff.
apparently reboot patch is no longer required on o3ds smash bros
 
So what new CFW features will likely require a9h to work and will be unavailable to people using existing booting methods? Currently the only possibilities I can think of are DSIware/GBA games in emunand but apparently that is being worked on via patching rather than a9h specific stuff.
DSiWare and GBA games in emuNAND are already possible without arm9loaderhax. It's just that no one bothered to make the emuNAND patches for these yet.
(and arm9loaderhax doesn't allow that either, or at least not yet.)


(i'm 1337)
 
Last edited by Mrrraou,
Injecting emunand 2.1 in sysnand, 2ds. Fingers crossed...

Edit : worked almost flawlessly. Had to boot withoup the SD inserted.
Now let's get the OTP.

Edit2 : Dumped it 3 times. Same SHA256 everytime. Looks like it's good.
Now time to restore the old sysnand.

Edit4 : Aaaaaaaaaaaaaaaaaaaaaaand done ! Thanx to everyone involded to this guide. It worked perfectly. Now let's wait for more usability of a9lh. Thanx again.
 
Last edited by AkGBA,
:^)
CbqaP9LVIAAVRne.jpg:large
 
  • Like
Reactions: daxtsu

Site & Scene News

Popular threads in this forum