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

 

[FenrirWolf]

That's fine, if you aren't comfortable with linked nands there shouldn't be harm in unlinking them. I don't get why the databases are giving you so much trouble though.

Maybe you should try installing something (something harmless like the hblauncher-loader cia) on your sysnand to see if things are working properly there, then re-clone the sysnand to emunand again.

 

[Tigroid]

Pretty sure that pasta is exclusively a sysnand thing. It'll reboot the console and apply patches to sysnand, not your emunand.

Pasta will boot to EmuNand unless Menuhax is being used. As long as either Menuhax isn't being used or you're pushing the button/ not pushing the button to use it, Pasta will take you back to the ***Nand the homebrw menu was booted from when you selected Pasta.

Source:https: https://gbatemp.net/threads/tutoria...luding-emunand-coldboot-cia-installer.405589/ Th "Setting Up EmuNand" sections explains using Pasta to install CIAs in EmuNand. Not that this really matters anymore, seeing as how the problems seems to have been solved...

 

[Sniffynose]

I got it to work the second attempt after bricking the first lols, I still don't know what went wrong but I ended up hardmodding my n3ds and using my original nand backup (thank god) to restore without a hassle. I followed everything from scratch again and it worked out. 50/50 chance ftw lol!

Sigh now for the next step doing something with this OTP >.>

 

[baked potato]

So, question. Section 2 step says I need to use tiny format on my emunand. I tried this a week ago but it seemed to have failed and relinked my nands. I had already unlinked my nands earlier during the cfw process, so im not sure if this step should have been skipped if I already unlinked them.

 

[Sniffynose]

So, question. Section 2 step says I need to use tiny format on my emunand. I tried this a week ago but it seemed to have failed and relinked my nands. I had already unlinked my nands earlier during the cfw process, so im not sure if this step should have been skipped if I already unlinked them.

If they are unlinked (test by changing your emunand theme then seeing if it switched the sysnand too) you don't need to bother doing it again.

 

[baked potato]

If they are unlinked (test by changing your emunand theme then seeing if it switched the sysnand too) you don't need to bother doing it again.

Ive known they where unlinked for awhile now. Great, thanks bro. Ive been putting off this guide because of step

Edit: Actually, one other thing I forgot to ask. The guide specifically says to back up sys and emunand to sysnand.bin and emunand.bin, but the option given when using decrypt 9 is nand.bin and nandemu.bin. Thiw isnt a problem right? Im assuming they mean the same thign just under a different filename

 

[Cuphat]

When I did it, I just ran TinyFormat twice. The first time it will relink, the second time it should unlink again. I don't know that it is necessary but might as well get it as clean as possible I guess.

 

[WindyRain0212]

When I did it, I just ran TinyFormat twice. The first time it will relink, the second time it should unlink again. I don't know that it is necessary but might as well get it as clean as possible I guess.

How did you ran it again though? I'm about to downgrade my N3DS, installed the tinyformat .cia to my emuNAND and ran it, pressed Y, finished, rebooted (menuhax failed first, so rebooted again), and then it apparently went to sysNAND.
I'm kinda lost. (step 9./sectionII is where I am stuck at right now.)
Also I apparently lost my menuHax entry on sysNAND. Which confuses me more. The guide said that it'll format emuNAND and not sysNAND.

EDIT: NVM - figured it out!

 

[pkmz]

Any idea why i run the windows bat for bricked emunand it says coild not find nand16.xorpad or what ever. Both files are there. 04 and regular.

 

[Ryft]

I just wanted to say this is one of the best written and organized guides I have ever seen. I love how the folders are split up into different steps. I followed this last night and had absolutely no hiccups (except decrypt9 not wanting to load a couple times). I am now running aureinand flawlessly and it is amazing. Thanks for your hard work @Plailect and everyone else who put this stuff together.

 

[Hyura]

OK, I have read the guide and I think I understood it.

The only brick risk is the downgrade to 2.1, right? And the majority of people do it without a problem.

After getting the OTP the a9lhax setup is fairly safe too, isn't it?

 

[WindyRain0212]

OK, I have read the guide and I think I understood it.

The only brick risk is the downgrade to 2.1, right? And the majority of people do it without a problem.

After getting the OTP the a9lhax setup is fairly safe too, isn't it?

Yeah, pretty much. I'm currently at the last steps, restoring the NAND's and then installing A9LH.
Just be sure that the downgrade of the emuNAND and its "unbrick"-compiling went flawlessly, then you should be fine.

 

[Plailect]

OK, I have read the guide and I think I understood it.

The only brick risk is the downgrade to 2.1, right? And the majority of people do it without a problem.

After getting the OTP the a9lhax setup is fairly safe too, isn't it?

If you'd like to wait until later today, I will probably have the OTPHelper update out by then, which greatly simplifies the process.

 

[Hyura]

If you'd like to wait until later today, I will probably have the OTPHelper update out by then, which greatly simplifies the process.

This is really interesting. I might wait for it (:

Thanks!

 

[uddevallare]

My second O3DSXL went well aslo, but don't forget a nand file on the root of the sd card when you run the arm9loaderhax.3dsx file. I did, toke some extra time due to the nand file being restored to the systemnand.

 

[baked potato]

So in the second section, once more i ran into a problem. Well, not really a problem but it asks for me to make a second emunand back up which i imagine the reason is because inbetween we would normally have used tiny format.

If youre going to update the guide topay guy, i suggest you also consider those who already used tiny format before using this guide.

 

[Plailect]

So in the second section, once more i ran into a problem. Well, not really a problem but it asks for me to make a second emunand back up which i imagine the reason is because inbetween we would normally have used tiny format.

If youre going to update the guide topay guy, i suggest you also consider those who already used tiny format before using this guide.

The second emunand backup is to reset it to just after we've set everything up but just before the downgrade, so if something goes wrong you can restore from that point.

 

[baked potato]

The second emunand backup is to reset it to just after we've set everything up but just before the downgrade, so if something goes wrong you can restore from that point.

Right, but the only thing that happened in between section 1 and section 2 #14 was the use of tiny format. For those who already used tiny format i dont see a reason for the second back up, unless im missing something

 

[Deleted member 117573]

@Plailect, Thank you for your OTP Guide. By following your guide I was able to successfully dump OTP.bin from 2 N3DS and 1 O3DS. I should have thanked you much earlier but I got caught up in all the arm9loaderhax hype and dropped the ball. Keep up the great work.

 

[TheGlow]

I hate to be that guy but its already up to page 106. On a N3DSXL so the only risky bit is flashing the Sysnand with the 2.1 build?
If it fails then I need to hardmod?

Side note I find emuNANDTool_1.0.1.exe and emuNANDTool_1.0.3.exe better for emunand dumping and restoring. Via pc its much faster.