Part 5 (arm9loaderhax & Cakes)

Every single step worked fine but when I reach the part when i need to install FBI again the icon of health&care just disappear, so i can't go to Homebrew again and my sysNAND is 10.7.

That happened when i did "Update your CFW SysNAND to the latest version using system settings".

// UPDATE
Forgot "Disable Signature Checks".

First of all, thanks for the guide.

As for the question:
https://github.com/Plailect/Guide/wiki/3DS-Stuck-(2.1.0-Without-Functional-Browser)

It does not appear to be clear how to proceed in the case of versions < 3.0 that already show the browser update nag screen. It says:
"If you downgraded to 2.1.0, on Old 3DS, 2DS, or New 3DS but for some reason you have a nonfunctional browser, this guide is for you."

Then right after, in step 6:
"Open the browser and go to http://www.reboot.ms/3ds/load.html?Launcher.dat"

In this case, what is the definition of "non-functional"? As in, it can't be opened? Nag screen?

Also, what is "a valid NAND backup of some kind"? As I understand, If you don't have gateway mode or a functional browser, and can't exploit MSET, under which conditions if any would you be able to dump NAND?

EDIT: I mean, besides going the 10.7.0-32U -> downgrade route.

Can you add region change guide to your great manual?

Be wary of using this guide. During part 3 of the guide, there is a section where you're first installing ReiNand. According to the guide, only way to check to see if ReiNand is installed correctly is if you boot up to the home screen when launching ReiNand from Homebrewlauncher. The guide does not provide any other way to see if you're on your EmuNAND or your SysNAND. Then the guide tells you to update your system, which can basically result in your 3DS being updated to the latest firmware so that you can no longer install any homebrew on it. I would suggest using one of the guides on gbatemp or finding another more, clearly written guide,

After I fully change my 3DS region from Japan to USA,
I launch the downgrade check.

Besides title that does not match the expected versions,
I still have Extra title and Missing title
And the desktop have alot of duplicated apps
After I use FBI to delete those title that does not match the expected versions,
My console gets brick when I try to update it.
Then I have to restore the a9lh NAND again from the decrypt9

what did I do wrong?

Heres the check

Title ID 0x0004003020008802
Extra title

Title ID 0x000400300000c302
Extra title

Title ID 0x000400300000c602
Extra title

Title ID 0x0004003000008202
Extra title

Title ID 0x000400300000bc02
Extra title

Title ID 0x000400300000c102
Extra title

Title ID 0x000400102002c800
Extra title

Title ID 0x0004001020020300
Extra title

Title ID 0x000400100002bf00
Extra title

Title ID 0x0004001000020a00
Extra title

Title ID 0x0004001000020000
Extra title

Title ID 0x0004001000020900
Extra title

Title ID 0x0004009b00012202
Extra title

Title ID 0x000400db00017202
Extra title

Title ID 0x000400db20016202
Extra title

Title ID 0x0004009b00015202
Extra title

Title ID 0x0004009b00013202
Extra title

Title ID 0x0004009b00011902
Extra title

Title ID 0x0004009b00010602
Expected version 0x0002
Installed version 0x0400

Title ID 0x000400302000c003
Extra title

Title ID 0x000400300000c402
Extra title

Title ID 0x000400300000c002
Extra title

Title ID 0x0004003000009502
Extra title

Title ID 0x0004003000008e02
Extra title

Title ID 0x0004003000008d02
Extra title

Title ID 0x0004003000008702
Extra title

Title ID 0x0004003000008602
Extra title

Title ID 0x0004003000008402
Extra title

Title ID 0x0004003000008302
Extra title

Title ID 0x000400102002cb00
Extra title

Title ID 0x000400102002ca00
Extra title

Title ID 0x000400102002c900
Extra title

Title ID 0x0004001020023100
Extra title

Title ID 0x0004001020020d00
Extra title

Title ID 0x0004001000020f00
Extra title

Title ID 0x0004001000020e00
Extra title

Title ID 0x0004001000020b00
Extra title

Title ID 0x0004001000020800
Extra title

Title ID 0x0004001000020700
Extra title

Title ID 0x0004001000020500
Extra title

Title ID 0x0004001000020400
Extra title

Title ID 0x0004001000020200
Extra title

Title ID 0x0004001000020100
Extra title

Title ID 0x0004013000001b02
Expected version 0x0800
Installed version 0x0c01

Title ID 0x0004013000001a02
Expected version 0x1400
Installed version 0x1801

Title ID 0x0004009b00015302
Missing title

Title ID 0x0004009b00011e02
Missing title

Title ID 0x0004009b00011d02
Missing title

Title ID 0x0004009b00011602
Missing title

Title ID 0x0004009b00011402
Missing title

Title ID 0x0004001000021f00
Missing title

Title ID 0x0004001000021e00
Missing title

Title ID 0x0004001000021b00
Missing title

Title ID 0x0004001000021800
Missing title

Title ID 0x0004001000021700
Missing title

Title ID 0x0004001000021500
Missing title

Title ID 0x0004001000021200
Missing title

Hello,

I'm trying to install with this tuto Arm9loaderhax on a 2ds. I launch mini pasta. Then i launch SafeA9LHInstaller. I press select and i reboot into emunand. I don't understand why i boot into emunand and not into sysnand. Because before i must press down Dpad to boot into emunand.

If i continue the tuto, i skip the emunand copy data because it's a new fresh 2ds. I delet the emunand and after i can't boot on sysnand i have a black screen and i can't boot into emunand because i have delete it.

I don't understand where is the problem. I have copied all files. I tried the tuto with one 3ds XL one O3DS and one 2DS and i haven't problem.

I completed the guide days ago before you added the uncart to the guide. Is there a way for me to add that in? If so at what point in the guide do I need to start from to add it to my current setup or do I need to start from part 1 and redo the entire process?

When I downgrade everything is fine when I check it in OTPHelper "Checking title 0004013800000102...
TMD not found or corrupt". I have now downgraded and then reset to NAND_emu_formatted.bin 5 time now and it's always the same error and it doesn't show up in godmode9.

Sorry if I have missed an instruction.

Spent about 4 hours on a 9,8.0 2DS got it to 9.2.0. Followed everything correctly slowly and carefully. The sysNAND folder was NOT displayed when I ran the system update at the end of it and I'm positive I was on emuNAND yet with nintendos newest update it still found and over wrote sysnand now my 3DS is ruined and can't be hacked without ocarina of time. This is seriously unfortunate.

When I try to start EmuNAND9(L+R+Y) it goes to the circle pad calibration screen

At "You can remove any extra files from the root of the SD card that are not in the image." section of Part 5 (AuReiNAND), the picture should be updated to latest version since rei folder change to aurei folder, etc.

AuReiNAND now uses a menu similar to cakes in order to select patches rather than flag files. See the latest release.

"Bitoin"

When I used the installer my sysnand didn't look different (I didn't know if it was supposed to) and decrypt9 didn't work.

In part 4 step 22 the guide says the following:
Backup EmuNAND to redNAND_original.bin (you can use Up and Down / Left and Right to change the name)

However, redNAND_original.bin was not a possible option. red* was basically not available. I've been following the guide from the beginning, so I do have redNAND, if that could be the cause.

I assume this won't cause problems, but just wanted to report this!

Flagrama releases weekly builds of the 10.4+ version of Sysupdater at http://larbob.com/build/sysupdater/ every Wednesday. Today, he released a new version that adds better compatibility for 10.7 downgrading (direct download can be found at http://larbob.com/build/sysupdater/working/sysupdater-10-7-3152016442.zip. This version should probably be in the guide for downgrading, perhaps alongside the older March 8 build you already have included, for the sake of 10.7 users.

Decrypt9 can have issues with several RedNAND related functions, an update will be out soon.

Since there are many brand new 3DS hacking noobs out there that are using this guide or are going to in the future, mentioning that the 10.7 update exists and still supports the 10.6 entry points (ninjhax and OoT3Dhax with or without Powersaves) along with the 10.4+ sysupdater application might be helpful for those users.

Now when I hold L+R on boot to start Decrypt9 it doesn't do anything and starts normally

What cheat methods are useable with this guide? NTR, Spider, ect?

In part four of the guide regarding the H&S inject.
You need the Decrypt9 folder in the root of your SD otherwise Decrypt9 won't boot.
Also need to place the "FBI_inject_with_banner.app" file to the Decrypt9 folder in the root, otherwise you can't select that file (it's also where the extracted file is).

Since this guide now uses an updated sysNAND format for A9LH, and this CFW (Mizuki) was just released specifically for this setup, it might be a good addition to have a guide for arm9loaderhax (step 5) with this CFW along with AuReiNAND and CakesFW. The CFW uses arm9 select by FIX94 for loading applications on boot (including itself) and is the first A9LH CFW that supports the 3DS loader replacement by yifanlu (https://github.com/yifanlu/3ds_injector). This loader then adds more features, such as region free loading from home menu and even region changing support. This CFW is minimalist CFW, so only the CFW's arm9loaderhax.bin is included in the download. In order to run, the AuiReiNAND firmware.bin files can be used and must be put in a /mizuki folder on the SD card, along with the custom loader, which must be named injector.cxi. From there, the arm9loaderhax.bin included in the Mizuki download must be renamed to default.bin and saved to the /arm9select folder on the SD card. For loading other applications on boot, the .bin files (such as decrypt9WIP.bin) have to be renamed to the proper button to be held on boot (a.bin, b.bin, etc) and put in the /arm9select folder, like in the AuReiNAND guide.

This CFW is probably the best option for beginners because it's less complicated compared to AuReiNAND and Cakes yet it supports nearly all of their features, including region free and loading apps from boot. For the guide, the hblauncher_loader and the A9LH installer files would still be needed (safeA9LH installer, slotkey bins, payload_input.zip, minipasta, etc.) along with the "on boot" applications (such as Decrypt9WIP and uncart for A9LH). However, other than that, all that would be needed is the most recent release of Mizuki, the 3DS custom loader, arm9select, and the AuReiNAND NTR firmware.bin files for Old and New3DS.

Also, this CFW can be used to switch regions on A9LH with Eshop access due to the custom loader, so that functionality could be utilized in the region changing guide.

Begining translate: https://github.com/mariogamer2/Guide/wiki/Home

I have followed all the steps from part 1-3 without a problem. When I get to step 24 under part 4 "Open TinyFormat" Hb loader freezes. I can't launch any home brew while inside of emuNAND. It works fine in SysNAND. I have tried going over this step for hours with the same result. My emunand is running firmware 10.6.0.30U as step 29 states in part 3 "Update your EmuNAND to the latest version using system settings"

Have you seen this before?

Steps 18 and 24 under Part 4, Section II link to the wrong troubleshooting section. (They link to "Black screen on SysNAND boot after downgrading" though it appears they should link to "OTPHelper fails to verify my NAND" instead)

I am having issues updating my EmuNAND. I've been using my OOT as an entry point, but everytime I try to update it to the latest version, from 9.2, it fails, saying it needs to restart. However, as far as I can tell, I think my emuNAND and sysNAND are unlinked. Any ideas?

When I launch Decrypt9WIP and try to dump Health&Safety app, it gives me this error:

Searching title "Health&Safety (N3DS)"...
Method 1: Search in title.db...
NAND CID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
TWL Customer ID: xxxxxxxxxxxx
0x03 KeyX: xxxxxxxxxxxxxxxxxxxx
0x03 KeyY: xxxxxxxxxxxxxxxx
0x05 KeyY: not set, slot0x05KeyY.bin not found
Method 2: Search in file system...
Failed!
Health&Safety Dump: failed!

Obviously I have slot0x05Key.bin in the root of SD card, but it is not detected anyway.

Nitpicky thing but in the FAQ it states:

Q: Can I do this without a computer (e.g. an Android phone)?
A: You may be able to complete up to part 3 of the guide (getting emuNAND running). However, part 4 as of now requires a computer to inject FBI into Health & Safety.

emuNAND should be replaced with redNAND since part 3 strictly talks about redNAND now.

Despite its being mentioned with BOLD in the tutorial

So I got stuck on Part 5 (arm9loaderhax & AuReiNAND)
I think I installed miniPasta and SafeA9LHInstaller. But, when it said it reboots it just brought me back to the SafeA9LHInstaller. Eventually, I played around with somefiles in the SD card and now it showed the AuReiNAND CONFIGURATION menu and I followed the steps for that and it just rebooted me back to the same menu.
So, now I got fustrated and I just made a backup of my SD card and tried to redo some steps. Then I got to the point where i had to use sliderhax to get into the homebrew on sysNAND and wasn't able to open any apps. The app icons were there, but when i pressed one it would make the screen black, then turn red on the bottom screen, then black again, then red again, and back to the homebrew launcher. But, when I try to load miniPasta and A9LHInstaller from the homebrew launcher it gives me a black screen.(Also I tried to launch OTPHelper and I couldnt launch that either).
If anyone could help me I Thank you.

SafeSysUpdater is finally safe, and will prevent bricks using wrong FW files.

See:
Cpasjuste/SafeSysUpdater@7b13bc4

Should have people download the latest release (1.0) and use it to downgrade/upgrade.

Now that emuNAND9 in its latest release has full redNAND support, it might be better for the guide to give instructions on how to set up and use a redNAND for step 3 and step 4 (with the 2.1.0-4 downgrade) instead of emuNAND. This change might help resolve a few emuNAND specific problems with downgrading, and redNAND is definitely faster, especially on New 3DS. This change will probably require further testing before it is implemented, just to make sure that redNAND doesn't have any specific problems of its own with the current software used for emuNAND.

I think there are 2 additional directories built in "Nintendo 3DS" on the way to emuNAND_formatted.
Are they obsolete and may be deleted in the final cleanup or do they have some function?
I want my SD to be as clean as possible. :-)

I am getting the message "An error has occurred. Please save your data in any software currently in use, and then restart the system" Everytime I click on the slider bar. I have cleared the internet stuff a dozen times, clicked multiple spots on the slider bar.. Seems no matter what I do, I always get that error.

I am on 9.2.0-20U

After I click the slider bar the bottom screen goes yellow and then grey. Then it takes me home and gives me the above error. Any help would be appreciated.

According @Mrrraou , SafeSysUpdater is more unstable (as it is bigger,or I don't know why....).

If the normal can be used....

Part 3 (EmuNAND), after step 10:
When [A] is pressed to ignore starter.bin, another prompt appears:
"You may now switch the SD card
The inserted SD card will be formatted
All data on it will be lost!
If you wish to proceed, enter:
[Down], [Up], [Left], [Right], [A]
[B to cancel]"

I just entered the combination, it seems it was the correct choice. Others may be confused on this part because it is telling to switch SD cards and the thought of formatting might be scary...

I have tried many times to update, but get hung up on the health and safety dump(step 11. Go to SysNAND File Options, then select the Dump Health & Safety option to dump Health & Safety to hs.app) . Here is the error log.

Searching title "Health&Safety"...
Method 1: Search in title.db...
System version 4.x
Found title 0004001000021300
TMD0 found at 15BD8000, size 2868b
APP0 not found or fragmented!
Health&Safety Dump: failed!

During Part 4, Section IV, restoring the sysNAND_Original.bin is failing on an o3ds running with redNAND. Same section succeeded on an o3ds running emuNAND.

I believe the latest OTPHelper is creating mangled sysNAND backups when you're running redNAND instead of emuNAND.

After I fully change my 3DS region from Japan to USA,
I launch the downgrade check.

Besides title that does not match the expected versions,
I still have Extra title and Missing title
And the desktop have alot of duplicated apps
After I use FBI to delete those title that does not match the expected versions,
My console gets brick when I try to update it.
Then I have to restore the a9lh NAND again from the decrypt9

what did I do wrong?

check log attached
check.zip

part 5, aureiNAND, on Finalising setup step number 5 i reboot and i get nothing but a black screen. I can press L+R to get to decrypt9 and LRY for emunand9 but other than that nothing. I do the Black screen on SysNAND boot after injecting CTRNAND troubleshoot since that seems to be my issue but then i get an error: aurei/firmware(90).bin doesnt match this console, or its encrypted. im at an impasse at what to do.

I've been following the tutorial the best I can, and I haven't bricked my system yet, but I've tried a lot of the troubleshooting doesn't really fix this error. (Probably because I'm the only person who's gotten it lol)

I've double checked the steps I took, redid the formatting steps, etc etc, and still get the following error.

Checking title 0004001000024000... TMD not found or corrupt

Could someone help me with this? Thanks in advance!

I have everything working up to the last step. Every time i tried to install hblauncher_loader i get the following error:
Install failed!
hblauncher_loader.cia
source:SOURCE_FSFILE_WRITE (OX1c)
module: MODULE_NN_FS (0x11)
level: LEVEL_PERMANENT (0x1b)
Summary: SUMMARY_WRONG_ARGUMENT (0X8)
description: DESCRIPTION_AES_VERIFICATION_FAILED (0X1)
Did i miss a step?

I followed your guide but when I downgrade it fails the file check and I have tried multiple times.

MD5 -> id: 0004013000001f02 - ver: 02048 -> GOOD
Can't get cia information (hax didn't succeed)

Now that a Kernel11 exploit is implemented for 10.4 NATIVE_FIRM, it is no longer necessary to do hardware modifications to downgrade on 10.4/10.5/10.6

I have downgraded my o3ds and now on 9.2. I followed part 3 with the installation of emuNAND until where it says to reinstall menuhax again for sysNAND. i have tried everything, replacing the files, changing themes, moving the files. This the screen i get every time. Sorry if this issues has been solved before and thank you for the help.

You link to an uncart binary in your guide. Not only is this not an upstream build - it lacks source code. I can't find any forks on github for it, which means it came from elsewhere. Look, hate to be THAT guy, but...

Uncart is GPL. I'm not saying to pull it - I'm not even a dev of uncart, but it is a license violation.

Not to mention I find trimming undesirable, and would like to disable it. Can't do so without source.

Upon reaching this step my system has the arm9loaderhax and no longer booting to sysNAND, but the new CFW sysNAND. The next step mentions removing emuNAND but entry is from sysNAND to HBL to emuNAND9. Does it matter that I'm not on sysNAND? I followed the previous revision on another N3dsxl yesterday successfully. I tried on another N3dsReg(AC happy home edition) and noticed step 5 has gone through some revision. The removing emuNAND step is almost unchanged but with the introduction of safea9lhinstaller step sysNAND has become CFWsysNAND. Should I treat the sysNAND part of removing emuNAND as the new CFW sysNAND and boot emuNAND9 through coldboot (L+R+Y) to delete emuNAND off SD?

Hi there,

on this wiki page you have "If you are already on 9.2.0-20U, skip to step 18.". I would like to suggest you change this so that it is agnostic of the region of a system.

Best regards,
Cu3PO42