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

 

[ihaveahax]

I guess I'll wait for a visual solution then. AuReiNAND has many button combos.

if you put firmware90.bin in the rei folder, hold L to go into sysnand with 9.0 firmlaunch. a visual solution might just cause the 3D bug on New3DS again and other things(?)

 

[Svaethier]

Alright, we have success.
It turned out getting a build environment was pretty easy and worked first try, so I wound up using my own (sorry, Trill Spector).

I was already on ReiNAND so now I'm on A9LH AuReiNAND instead.
Still EmuNAND, naturally, since I do all my stuff in one and I've yet to see a "Move your EmuNAND to SysNAND for A9LH" thread =P

Feels good to be out of the danger zone... at least, until I try the O3DS again.

just use decrypt9, go to emunand settings, partition dump, dump all partitions except firmo and firm1, do the same with sysnand settings, inject your emunand partitions into sysnand and sysnand partitions into emunand. I did this and my sysnand is now emunand and vice versa

 

[dkabot]

just use decrypt9, go to emunand settings, partition dump, dump all partitions except firmo and firm1, do the same with sysnand settings, inject your emunand partitions into sysnand and sysnand partitions into emunand. I did this and my sysnand is now emunand and vice versa

Do they have to match? It'd be quite bad if it did, I would bri- well, I wouldn't brick, but it would still suck.

Edit: Match versions, derp

 

[Svaethier]

Do they have to match? It'd be quite bad if it did, I would bri- well, I wouldn't brick, but it would still suck.

Edit: Match versions, derp

I used 9.2 sysnand partitions for emunand and everything except the CTRNAND was 9.2 from emunand, the emunand CTRNAND was from my 10.5 dump, still worked fine for me so it shouldn't matter. but downgrade your emunand to 9.2 if you want to feel safer.

 

[dkabot]

Actually, I'm a derp. AuReiNAND is patched to not change FIRM1/0 when updating, so thus it would probably work to not downgrade the EmuNAND and just inject everything not firm1/0

Edit: Double derp: Was wondering "What about NATIVE_FIRM from updates?" then remembered AuReiNAND is still providing firmlaunch. I'm not good at thinking today.

 

[Gcentrex]

I have tried to downgrade emuNAND mutiple times and it keeps failing on 0004003000008F02.cia each time, if the file is removed it completes fully

Anyone know if it will work correctly without installing 0004003000008F02.cia (home menu)

This is on on o3ds xl


EDIT: emuNAND version is 9.2 if that makes a difference but seems from a search of this thread im not the only one with this error

 

[Just Passing By]

I have tried to downgrade emuNAND mutiple times and it keeps failing on 0004003000008F02.cia each time, if the file is removed it completes fully

Anyone know if it will work correctly without installing 0004003000008F02.cia (home menu)

This is on on o3ds xl

I'd never remove a file that you're using to downgrade. Luckily I've found a solution that seems to work. What you want to do is update your emunand to anything higher than it's current firmware. 10.3 worked for me and 10.5 worked for someone else, so those two will work. After that make a backup of your emunand just in case and downgrade.

I've had that problem and I had to wait for about 4+ days before someone ran into the same problem as me and I was able to figure out the problem. It seems like a rare group of people have the .....8F02 problem.

 

[Gcentrex]

I'd never remove a file that you're using to downgrade. Luckily I've found a solution that seems to work. What you want to do is update your emunand to anything higher than it's current firmware. 10.3 worked for me and 10.5 worked for someone else, so those two will work. After that make a backup of your emunand just in case and downgrade.

I've had that problem and I had to wait for about 4+ days before someone ran into the same problem as me and I was able to figure out the problem. It seems like a rare group of people have the .....8F02 problem.

At first I just thought it was bad luck but I watched the entire thing and it kept getting stuck each time, so since its only emuNAND thought I would see if it worked with that removed.

I was not going to flash it to sysNAND, I'm currently restoring my backup and will try your suggestion of updating to a higher emuNAND first then try again.

Thanks

 

[dkabot]

I'd never remove a file that you're using to downgrade. Luckily I've found a solution that seems to work. What you want to do is update your emunand to anything higher than it's current firmware. 10.3 worked for me and 10.5 worked for someone else, so those two will work. After that make a backup of your emunand just in case and downgrade.

I've had that problem and I had to wait for about 4+ days before someone ran into the same problem as me and I was able to figure out the problem. It seems like a rare group of people have the .....8F02 problem.

Thanks for that, posted a few pages back about it and it's nice to see a solution.

 

[Svaethier]

Actually, I'm a derp. AuReiNAND is patched to not change FIRM1/0 when updating, so thus it would probably work to not downgrade the EmuNAND and just inject everything not firm1/0

Edit: Double derp: Was wondering "What about NATIVE_FIRM from updates?" then remembered AuReiNAND is still providing firmlaunch. I'm not good at thinking today.

i downgraded my emunand to 9.2 before doing this. only thing that I injected that was from 10.5 emu was my ctrnand but that didn't affect anything so I was safe I guess.

 

[dkabot]

i downgraded my emunand to 9.2 before doing this. only thing that I injected that was from 10.5 emu was my ctrnand but that didn't affect anything so I was safe I guess.

I saw that you said you downgraded, just attempted to apply some thought (which I'm not great at atm) and if it's not updating FIRM0/1 then you probably could inject verbatim.
IIRC the issue with say, SysUpdater on Firmlaunch SysNAND was that FIRM didn't change, but in this case it's not changing regardless and is being compensated for by A9LH Firmlaunch.

At least, that's how I recall hearing it.

 

[Svaethier]

I saw that you said you downgraded, just attempted to apply some thought (which I'm not great at atm) and if it's not updating FIRM0/1 then you probably could inject verbatim.
IIRC the issue with say, SysUpdater on Firmlaunch SysNAND was that FIRM didn't change, but in this case it's not changing regardless and is being compensated for by A9LH Firmlaunch.

At least, that's how I recall hearing it.

when I tried to inject 9.2 partitions into 10.5 emu my emu stopped working so I had to restore from a backup I made two days ago so I think it's safer to downgrade emu to 9.2 so partition versions match atleast.

 

[dkabot]

when I tried to inject 9.2 partitions into 10.5 emu my emu stopped working so I had to restore from a backup I made two days ago so I think it's safer to downgrade emu to 9.2 so partition versions match atleast.

Yeah, prolly doing that for safety, trying something on O3DS first though.

 

[Svaethier]

Yeah, prolly doing that for safety, trying something on O3DS first though.

worked on my 2DS just fine, just make back ups of your sysnand and emunand just in case though.

 

[dkabot]

worked on my 2DS just fine, just make back ups of your sysnand and emunand just in case though.

My "something" is the 8F02 problem, and I followed the guide verbatim so I've got backups.

 

[Just Passing By]

Thanks for that, posted a few pages back about it and it's nice to see a solution.

Oh thanks for the nice words! ^^ I'm sorry I never saw your post. I usually read all of them so yours must have slipped by. It seems like you've basically solved it the way I've found to work, so I'm glad that's another person that can vouch for this method. And it wasn't just me, without @templeofhylia, I'd probably still be here complaining like a baby about how I don't know what the problem is.

 

[Svaethier]

My "something" is the 8F02 problem, and I followed the guide verbatim so I've got backups.

ah, makes sense.

 

[Nikolay]

Another success story here Successfully got my OTP file and have restored back both my NANDs. Thanks to everyone who made this possible, and especially for the well written and concise guide.

 

[Naked_Snake]

Alright started from scratch again no downgrading sysNAND on my n3ds and about to dump OTP if all goes well, aprt from decryption/encryption what else can we do with OTP

 

[daxtsu]

Alright started from scratch again no downgrading sysNAND on my n3ds and about to dump OTP if all goes well, aprt from decryption/encryption what else can we do with OTP

https://gbatemp.net/threads/otp-guide.415140/page-43#post-6088526