Tutorial More-or-less Catch-All Tutorial

[Sgt. Lulz]

New 3ds XL running sysnand 9.2.0-20U. All appeared to be going well until I tried to figure out the Region and Version for the FBI injection. I keep getting "Missing Health & Safety info".
I tried to load the emuNand from rxTools that I had made before the attempt at injection and I got the error: "Failed to load native firm: 5"

Apparently rxTools doesn't support N3DS FBI injection yet, which means that N3DS users have to use this to inject FBI to emuNAND: https://gbatemp.net/threads/release-inject-any-app-into-health-safety-o3ds-n3ds-cfw-only.402236/
As for the second part, that's not a common error, according to Google.
My first guesses would be to switch to a different nightly and make sure that the firmware9.5.bin file renamed to firmware.bin is in rxTools/sys/.
If that doesn't work, try firmware9.2.bin renamed to firmware.bin instead.
Sorry for taking so many shots in the dark, I don't really have a N3DS of my own to test these methods with, so I have to rely on snippets of information on the internet and oodles of guessiwork.
I'll most likely be able to make this guide more accurate in a few days as soon as I get a N3DS, though.

 

[Katanira]

Apparently rxTools doesn't support N3DS FBI injection yet, which means that N3DS users have to use this to inject FBI to emuNAND: https://gbatemp.net/threads/release-inject-any-app-into-health-safety-o3ds-n3ds-cfw-only.402236/
As for the second part, that's not a common error, according to Google.
My first guesses would be to switch to a different nightly and make sure that the firmware9.5.bin file renamed to firmware.bin is in rxTools/sys/.
If that doesn't work, try firmware9.2.bin renamed to firmware.bin instead.
Sorry for taking so many shots in the dark, I don't really have a N3DS of my own to test these methods with, so I have to rely on snippets of information on the internet and oodles of guessiwork.
I'll most likely be able to make this guide more accurate in a few days as soon as I get a N3DS, though.

Thanks for the reply and the information. I'll probably try the other method in a few hours and post what results I get.

 

[wahts]

hey guys if i follow that tutorial will i be rdy to play on a cfw.
i have a n3ds with firmware 9.4 i did nothing with it so its basicly clean

 

[EthanObi]

Much to my annoyance Browserhax isn't working on my N3DS, 9.1.0.20J, gives 'please hold power button to turn system off' each time, :\

 

[Sgt. Lulz]

Much to my annoyance Browserhax isn't working on my N3DS, 9.1.0.20J, gives 'please hold power button to turn system off' each time, :\

Are you using http://yls8.mtheall.com/browserhax_fright.php?
It should be working, then again boot rates aren't guaranteed to be 100%.
Crappy luck comes to all of us once in a while.

 

[monsterami]

So. I'm having the black screen issue if I try to boot into rxtools emunand after injecting FBI the first time. My SD is a GB smaller. I've tried multiple SD cards. I've tried multiple entry-points to both hax and rxtools (ninjhax, menuhax, ctrbootmanager etc.). The MD5 of both my firmware (a9dcd99a360e8629810f8ed08403d746) and my downgrade (879f437d7c78f09ae565f79f5aa9c421) match what I should have/be using for an O3DS. Is it safe to assume that there's a problem with my downgrade and that I should go back to 10.3 and wait for a more stable release? (I already have my NAND backed up, but I don't know if I trust it at this point)

 

[Domukuro Wolfield]

You'll have to delete a couple .db files in your "Nintendo 3DS" folder iirc. I don't remember exactly which, just that one is title .db (or .dbs i'm not sure) and that the other is in the same folder.

My sdcard don't have these files And the app send me the same error. Is possible install with another tool tinyformat?

 

[Sgt. Lulz]

My sdcard don't have these files And the app send me the same error. Is possible install with another tool tinyformat?

Right in the 'Final touches to CFW' section:

3. You can solve 'No Database' errors in FBI by opening the eShop and closing it in EmuNAND.

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

So. I'm having the black screen issue if I try to boot into rxtools emunand after injecting FBI the first time. My SD is a GB smaller. I've tried multiple SD cards. I've tried multiple entry-points to both hax and rxtools (ninjhax, menuhax, ctrbootmanager etc.). The MD5 of both my firmware (a9dcd99a360e8629810f8ed08403d746) and my downgrade (879f437d7c78f09ae565f79f5aa9c421) match what I should have/be using for an O3DS. Is it safe to assume that there's a problem with my downgrade and that I should go back to 10.3 and wait for a more stable release? (I already have my NAND backed up, but I don't know if I trust it at this point)

No, it's probably okay.
I feel like I should point this out to the rxTools blackscreeners:
If you could create the emuNAND at all through emuNAND9, that means your downgrade went fine.
rxTools blackscreening seems to be caused by something I can't quite pinpoint yet. Sometimes it happens, sometimes it doesn't.
I don't have nearly enough information to solve this issue on my own, sadly, but I know that it shouldn't be happening and in fact isn't happening to most people I know.
If anyone knows anything else about this bug, do tell what's up.

 

[monsterami]

No, it's probably okay.
I feel like I should point this out to the rxTools blackscreeners:
If you could create the emuNAND at all through emuNAND9, that means your downgrade went fine.
rxTools blackscreening seems to be caused by something I can't quite pinpoint yet. Sometimes it happens, sometimes it doesn't.
I don't have nearly enough information to solve this issue on my own, sadly, but I know that it shouldn't be happening and in fact isn't happening to most people I know.
If anyone knows anything else about this bug, do tell what's up.

Understood. Well, if it helps narrow it down, I'm using the latest nightly of rxTools (5th of december) and the FBI I injected is USA v2051.

 

[Sgt. Lulz]

Understood. Well, if it helps narrow it down, I'm using the latest nightly of rxTools (5th of december) and the FBI I injected is USA v2051.

Something I should ask: Did emuNAND work at all before injecting FBI?
I think I might be onto something, but it seems kind of asinine.

 

[Phil Shroyer]

Something I should ask: Did emuNAND work at all before injecting FBI?
I think I might be onto something, but it seems kind of asinine.

That I never thought to try, I will though as soon as I'm home from work, you think FBI is the issue?

 

[Domukuro Wolfield]

Oh man, this is work BUT, when i launch the tinyformat and press Y, the system reboot and now i can't get access to HBL, this is normal? I don't know if the 3DS are in the emuNAND or sysNAND, are a way to know it?

And i can get out the NAND.bin from the SD now?

 

[monsterami]

Something I should ask: Did emuNAND work at all before injecting FBI?
I think I might be onto something, but it seems kind of asinine.

I didn't try this, but like the poster above I will when I am home later today!

 

[Sgt. Lulz]

Oh man, this is work BUT, when i launch the tinyformat and press Y, the system reboot and now i can't get access to HBL, this is normal? I don't know if the 3DS are in the emuNAND or sysNAND, are a way to know it?

And i can get out the NAND.bin from the SD now?

No, that doesn't seem normal.
TinyFormat simply reinitializes the system firmware (on emuNAND in this guide's case) so it generates a new unique ID and forces you to perform the first-time setup all over again without formatting the SD card.
If you've changed your theme on sysNAND through the home menu, that will have uninstalled Menuhax, so reinstall it.
There's no strict way of telling whether you're on sysNAND or emuNAND: Once unlinked, the two can have different themes and effectively behave as two different systems. emuNAND is the one that opens after you boot rxTools and sysNAND is the one that opens when you turn on the console like normal.
Yes, the NAND.bin file is merely meant for hardmod purposes, so you can take it out of the SD card, as it's not much more than just dead space for now.

 

[esker]

Something I should ask: Did emuNAND work at all before injecting FBI?
I think I might be onto something, but it seems kind of asinine.

I just tried this myself (went right back to the creating a new EmuNAND step) and am still getting the black screen even without having injected FBI.

 

[Sgt. Lulz]

I just tried this myself (went right back to the creating a new EmuNAND step) and am still getting the black screen even without having injected FBI.

Yeah, still haven't got a clue, then.
It's in some manner possible that some step may have failed, perhaps the emuNAND setup part.
One way to check if emuNAND is at all there is opening Disk Management on Windows (Start menu > Search "disk management" > first result; "Create and format hard disk partitions") and seeing if there's a ~1GB-2GB partition of unallocated space on the SD card.

Considering how this has been happening to O3DS and N3DS users alike, I don't think it's a firmware.bin problem,
The problem could be anywhere between Menuhax/Browserhax, CTRBootManager, emuNAND9 and rxTools itself.
Reports are sort of a mixed bag with some people getting success with Ironhax and Browserhax and Menuhax, etc., so I genuinely have no clue what's up.

 

[Phil Shroyer]

Yeah, still haven't got a clue, then.
It's in some manner possible that some step may have failed, perhaps the emuNAND setup part.
One way to check if emuNAND is at all there is opening Disk Management on Windows (Start menu > Search "disk management" > first result; "Create and format hard disk partitions") and seeing if there's a ~1GB-2GB partition of unallocated space on the SD card.

Considering how this has been happening to O3DS and N3DS users alike, I don't think it's a firmware.bin problem,
The problem could be anywhere between Menuhax/Browserhax, CTRBootManager, emuNAND9 and rxTools itself.
Reports are sort of a mixed bag with some people getting success with Ironhax and Browserhax and Menuhax, etc., so I genuinely have no clue what's up.

Well like I said if I run rxtools using the browser as an entrypoint it does load, verified as emunand as it does show rxtools on the system settings page

 

[Sgt. Lulz]

Well like I said if I run rxtools using the browser as an entrypoint it does load, verified as emunand as it does show rxtools on the system settings page

Yeah, everyone here seems to have way different symptoms of what can only be narrowed down to 'It blackscreens'.
I don't know what to tell you all to fix the issue, so I'm gonna wait on a word from a developer for now.
These reports of CFW blackscreening are awfully common at the moment, following my tutorial or otherwise, so I can only imagine they've been heard plenty enough now.

 

[Sapphirexe]

When booting emunand with this tutorial, I got a black screen every time. Did al the steps of the 9.2 tutorial except the 0004013820000002.bin copy-thing because I can´t find it anywhere.

 

[esker]

I've just had success using an older version of rxTools I pulled from some random Reddit thread: https://mega.nz/#!KQ1HVDLZ!TJhiM4zQlknFSqdkDDf8oGMHaNod6-WbR_ggznC8b3c

I guess give that a go if you're also having black screen issues?