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

 

[Sno0t]

Inject FBI into the emunand's H&S app, then use FBI to install the homebrewlauncher-loader cia

Thank you
Is this the easiest way to do this? Or is there another way with which i dont have to inject it into the emuNAND.bin and 'install' it over the existing formatted emuNAND.bin?

 

[FenrirWolf]

Thank you
Is this the easiest way to do this? Or is there another way with which i dont have to inject it into the emuNAND.bin and 'install' it over the existing formatted emuNAND.bin?

This would be much easier https://gbatemp.net/threads/release-inject-any-app-into-health-safety-o3ds-n3ds-cfw-only.402236/

 

[Sno0t]

Damn, Iam stuck again...does any1 know why I get a blackscreen when I try to launch Decrypt9?
( Successfully DGD my emuNAND and want to backup it as emuNAND_bricked)

EDIT:
nvm... 8th try did the trick >.>

EDIT2:
Got my OTP.
Thank you @FenrirWolf four your help

 

[iAqua]

Im gonna attempt this. Good thing I have the ebgames return warranty thing.

 

[pre10c]

is the updates folder in the The all-in-one pack the 2.1 update cia's used to downgrade? or do we need to provide our own and is that updates folder just an example?

 

[pbanj]

is the updates folder in the The all-in-one pack the 2.1 update cia's used to downgrade? or do we need to provide our own and is that updates folder just an example?

It's the files

 

[iAqua]

OTP.BIN succesful! I thought it bricked, but deleting the extdata folder worked perfectly.

 

[naivegirl2411]

Do we ever have to unlink our nands during the process to get our otp? With a9lh do we still have to unlink nands?

 

[Fureshyu]

help! I'm at the step where I used tinyformat on emunand and 1st time it went through, my nands were linked. I did it again, they're unlinked but I can't install cias on it. It says invalid database. So i did some research, remade my database on sysnand, tried on emunand but it didn't recognize, then i copied my dbs folder on emunand and still no recognition. I'm really frustrated, can someone help me?

 

[Tigroid]

help! I'm at the step where I used tinyformat on emunand and 1st time it went through, my nands were linked. I did it again, they're unlinked but I can't install cias on it. It says invalid database. So i did some research, remade my database on sysnand, tried on emunand but it didn't recognize, then i copied my dbs folder on emunand and still no recognition. I'm really frustrated, can someone help me?

I think you need to boot into EmuNand, run *hax, run Pasta CFW from homebrew menu, this will take you back to EmuNand, but with Pasta patches, run *hax again to run FBI and install CIAs. I hope you understand and that this helps.

 

[FenrirWolf]

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

To rebuild your database for your emunand, you need to make a blank title.db and a blank import.db as well. Put them in the dbs folder for your emunand, then go to system settings->data management->Nintendo 3DS->Software. You'll see a message about your database being rebuilt.

 

[Fureshyu]

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

To rebuild your database for your emunand, you need to make a blank title.db and a blank import.db as well. Put them in the dbs folder for your emunand, then go to system settings->data management->Nintendo 3DS->Software. You'll see a message about your database being rebuilt.

I already did that, and it didn't do anything.

 

[FenrirWolf]

I'm guessing you've already injected FBI into H&S on your emunand? Or were you trying to install CIAs from the 3dsx version? You won't be able to do it from the homebrew launcher.

 

[Fureshyu]

Yes it is injected. I am getting the error from there

I'm guessing you've already injected FBI into H&S on your emunand? Or were you trying to install CIAs from the 3dsx version? You won't be able to do it from the homebrew launcher.

 

[FenrirWolf]

I would just clone a new emunand from your sysnand if it's giving you that much trouble. You'll still be able to restore your existing sysnand and emunand backups afterwards.

 

[Fureshyu]

I would just clone a new emunand from your sysnand if it's giving you that much trouble. You'll still be able to restore your existing sysnand and emunand backups afterwards.

Okay, if I do that, should I downgrade straight from my new emunand taken from a sysnand backup or use tiny format again?

 

[FenrirWolf]

You could use tinyformat again if you want to unlink them, but truth be told it isn't necessary to unlink the NANDs in order for this guide to work. Leaving them linked does make it slightly easier to lose track of where you are, but it won't actually be detrimental to anything aside from that.

 

[Fureshyu]

You could use tinyformat again if you want to unlink them, but truth be told it isn't necessary to unlink the NANDs in order for this guide to work. Leaving them linked does make it slightly easier to lose track of where you are, but it won't actually be detrimental to anything aside from that.

I'm on n3ds, so leaving the nands linked would be detrimental if i downgraded.

 

[FenrirWolf]

Not really. I downgraded my N3DS to 2.1 and the NANDs were linked on mine.

"linked nands" just means that they both look in the same folder on the SD card to load games, theme data, and some other things. When you downgrade your emunand to 2.1, it gets bricked. And even when you run the emunand through the unbricker script, you aren't actually able to boot up a 2.1 emunand. Instead, you flash the unbricked emunand image to sysnand and boot it there. Therefore, there never is a time where you can be booting both 9.2 and 2.1 at the same time, which means that the NANDs being linked ultimately doesn't matter apart from the slight organizational confusion that can be involved.

But either way, you can also just run tinyformat to unlink them if you like. Hopefully it won't throw the same kind of errors at you that it did last time.

 

[Fureshyu]

Not really. I downgraded my N3DS to 2.1 and the NANDs were linked on mine.

"linked nands" just means that they both look in the same folder on the SD card to load games, theme data, and some other things. When you downgrade your emunand to 2.1, it gets bricked. And even when you run the emunand through the unbricker script, you aren't actually able to boot up a 2.1 emunand. Instead, you flash the unbricked emunand image to sysnand and boot it there. Therefore, there never is a time where you can be booting both 9.2 and 2.1 at the same time, which means that the NANDs being linked ultimately doesn't matter apart from the slight organizational confusion that can be involved.

Well I just tried flashing the sysnand and it kept looping back to ctrbootmanager :/ I flashed my emunand backup and tried tinyformat and it worked except made my nands linked again. Tried tinyformat once more and it worked as well as unlinking my nands. But now I'm back to square one where FBI injected tells me a database error even after I've tried repairing it.

This is very frustrating, I trust you but I'm not comfortable downgrading with nands linked.