I'll try that right now thank you.
Just FYI this was the final stage of what I did:
Part 5 (arm9loaderhax)
Plailect edited this page on 1 Oct ·
145 revisions
Pages 28
Home
FAQ
Troubleshooting
Get Started
OTP Info
NAND Size
Device Info
Part 1 - Homebrew
Part 2 - 9.2.0 Downgrade
Part 3 - RedNAND
Part 4 - 2.1.0 Downgrade
Part 5 - arm9loaderhax
9.2.0 Update
Region Changing
Firmware Downgrade
Updating arm9loaderhax
Donations
Credits
Clone this wiki locally
You cannot use another console's OTP or you will brick GUARANTEED.
The final step of this guide is to install arm9loaderhax and setup Luma3DS to run just milliseconds into the boot. This is accomplished by using SafeA9LHInstaller by
AuroraWright.
This will install
AuroraWright's Fork of arm9loaderhax.
This guide uses "Updated SysNAND" mode, in which we copy our RedNAND to SysNAND (to keep games and such) and install arm9loaderhax to have permanent SysNAND hax with no RedNAND required at all.
We will also setup the ability to launch payloads from arm9loaderhax, giving us the ability to unbrick our SysNAND from situations that would normally brick us by restoring from backup.
Overview of steps
In this section, we will go through the process that all the other steps have led up to: actually installing arm9loaderhax.
This is nearly the best possible kind of device exploit because it is permanantly installable into the NAND firm partitions, and runs before most of the OS loads, allowing it to not only work on
allversions once installed, but also protect itself and recover from most situations that would brick a non-a9lhax 3DS such as a nonfunctional home menu or bad title install.
The file arm9loaderhax.bin is what is launched by arm9loaderhax itself after it finishes loading off of NAND, and can be any valid arm9 payload. This file can be replaced at any time, although Luma3DS allows for the launch of other arm9 payloads by holding buttons on boot.
In this case, we use Luma3DS by
AuroraWright to boot a patched SysNAND directly, allowing us to completely bypass the need for any kind of RedNAND, vastly simplifying the usage of a hacked 3DS in addition to saving SD card space.
Once arm9loaderhax is installed and Luma3DS is setup with the correct options, we then backup our SD card and format it using EmuNAND9 to remove the now obsolete RedNAND and reclaim the SD card space it previously used.
During this process, we also setup programs such as FBI
(installs CIA formatted games and applications), Luma3DS Updater
(updates our CFW installation easily), Decrypt9
(NAND + decryption tool which can also convert physical cartridge games to digital CIA files), Hourglass9
(allows us to restore NANDs and such before boot to recover from bricks and do many other miscellaneous functions), and EmuNAND9
(manages RedNAND installations in addition to several miscellaneous features).
Screeninit arm9loaderhax payloads turn on the screen before handing control over to arm9loaderhax.bin (making sure it works with all arm9loaderhax.bin files), while noscreeninit arm9loaderhax payloads do not (allowing arm9loaderhax.bin to control things like brightness during boot). You can choose to use either (the guide used to only have screeninit payloads).
What you need
Instructions
Section I - Preparatory work
- Copy emergency_SecureInfo_A, emergency_movable.sed, emergency_title.db, emergency_ticket.db, NCSD_header_[o/n]3ds.bin, and firm0firm1.xorpad from the root of your SD card to a safe location on your computer and back them up to multiple locations (such as online file storage); they do not replace NAND backups, but in the event of lost backups could save you from total data loss (after further research and development is completed)
- Delete emergency_SecureInfo_A, emergency_movable.sed, emergency_title.db, emergency_ticket.db, NCSD_header_[o/n]3ds.bin, and firm0firm1.xorpad from the root of your SD card
- Delete the EmuNAND9 folder from the root of your SD card if you have one
- Delete the 3ds folder from the root of your SD card
- Copy the contents of the starter folder in starter.zip to the root of your SD card
- (this will reset homebrew launcher apps to default, you don't need the others from before)
- Copy the a9lh folder from data_input_v2.zip to the root of your SD Card
- Copy payload_stage1.bin and payload_stage2.bin from the arm9loaderhax zip to a9lh folder on your SD card
- Copy arm11.bin and arm9.bin from the SafeA9LHInstaller zip to the root of your SD card
- Copy hblauncher_loader.cia from the hblauncher_loader zip to the root of your SD card
- Copy lumaupdater.cia from the Luma3DS Updater zip to the root of your SD card
- Copy FBI.cia from the FBI zip to the root of your SD card
- Copy arm9loaderhax.bin and the luma folder from the Luma3DS zip to the root of your SD card
- Copy Hourglass9.bin from the Hourglass9 zip to the /luma/payloads/ folder on your SD card and rename Hourglass9.bin to start_Hourglass9.bin
- Copy EmuNAND9.bin from the EmuNAND9 zip to the /luma/payloads/ folder on your SD card and rename EmuNAND9.bin to y_EmuNAND9.bin
- Copy Decrypt9WIP.bin to the /luma/payloads/ folder on your SD card and rename Decrypt9WIP.bin to x_Decrypt9WIP.bin
- Copy aeskeydb.bin to the root of your SD card
- Copy DspDump.3dsx to the /3ds/ folder on your SD card
- Copy emuNAND_original.bin and emuNAND_original.bin.sha from Section II of Part 4 to the root of your SD card
Section II - Installing arm9loaderhax
- Reinsert your SD card into your 2.1.0 3DS
- Go to http://dukesrg.github.io/2xrsa.html?arm11.bin on your 3DS
- Select Full Install
- The installer will now install arm9loaderhax on your device (this is very fast)
- Following this, booting to a black screen is normal (Luma3DS cannot boot a 2.1.0 NAND).
- Copy your console specific OTP.bin from the /a9lh/ folder on your SD card to a safe location on your computer and back it up to multiple locations (such as online file storage)
Section III - Configuring Luma3DS
- Hold select on boot to enter the Luma3DS menu.
- Use the A button and the D-Pad to turn on the following:
- "Autoboot SysNAND"
- "SysNAND is updated"
- "Force A9LH detection"
- "Show current NAND in System Settings"
- "Show GBA boot screen in patched AGB_FIRM"
- If you are using a New 3DS, you should also enable the following:
- Toggle "New 3DS CPU" to "Clock+L2(x)" for improved game performance
- Press Start to save and reboot
- Following this, booting to a black screen is normal (Luma3DS cannot boot a 2.1.0 NAND).
Section IV - Copying RedNAND data to SysNAND
- Open Hourglass9 from arm9loaderhax by holding Start on boot
- Go to "SysNAND Backup/Restore..."
- Select "SysNAND Restore"
- Confirm and restore from emuNAND_original.bin
- Your device should now be able to boot properly once more.
Section V - Removing RedNAND from your SD
- Press Select on the main menu to eject your SD card
- Delete emuNAND_original.bin and emuNAND_original.bin.sha from the root of your SD card
- Backup every file on your SD card to a folder on your computer, all files will be deleted in the next step
(if you followed Part 3 of this guide, you can delete the SD card backup from that - this will replace it)
- Reinsert your SD card into your 3DS.
- Hold Y on boot to launch EmuNAND9
- Go to "SD Format Options", then "Format SD..."
- Select the "Format SD (No EmuNAND)" option
- Press Select on the main menu to eject your SD card
- Put your SD card in your computer, then copy all your files back into it
Section VI - Finalizing setup
- Reinsert your SD card into your 3DS
- Still from EmuNAND9, go to EmuNAND Manager Options and make a backup of SysNAND to sysNAND.bin
- Press Select on the main menu to eject your SD card, then put it in your computer
- Rename sysNAND.bin to sysNAND-A9LHAX.bin and sysNAND.bin.sha to sysNAND-A9LHAX.bin.sha
- Copy both to a safe location on your computer; this is a SysNAND backup containing arm9loaderhax (Your backup should match one of the sizes on this page; if it does not, you should delete it and make a new one!)
- Delete sysNAND-A9LHAX.bin and sysNAND-A9LHAX.bin.sha from your SD card
- Reinsert your SD card into your 3DS then press Start to reboot
- Update your CFW SysNAND to the latest version using system settings (if it is not already)
- Open Health and Safety (which is now FBI)
- Select "SD"
- Navigate to FBI.cia and press A to install
- Navigate to hblauncher_loader.cia and press A to install
- Navigate to lumaupdater.cia and press A to install
- Exit with the home button
- Launch the Homebrew Launcher from the home menu
- Select "DSP Dump"
- Press Start when prompted to exit
- Reboot while holding Start to launch Hourglass9
- Go to SysNAND Backup/Restore, then select Health&Safety Inject
- Select hs.app (the original one from Part 4), then press A and confirm to inject
- Press Start on the main menu to reboot!
If everything has gone according to plan, arm9loaderhax will be installed to your device, your RedNAND will have been copied to your SysNAND, you will no longer need RedNAND, you will have a CIA installer, and you'll be able to launch the Homebrew Launcher from an icon on your home menu. Your device will now automatically launch into CFW SysNAND.
You can now use Luma3DS Updater to update your Luma3DS to the latest version just by opening it and pressing A.
(This is not the same thing as a System Update; it just downloads and extracts the newest Luma3DS files)
You will no longer be able to boot without the SD card in, that is normal.
You will now boot a Custom Firmware based SysNAND by default.
You can now hold Select on boot to launch the Luma3DS configuration menu.
You can now hold Start on boot to launch Hourglass9, an arm9loaderhax safe NAND tool.
You can now hold Y on boot to launch EmuNAND9, a full featured RedNAND and SD management tool.
You can now hold X on boot to launch Decrypt9, a full featured NAND + decryption tool which can also be used to
convert a physical game cart to an installable file.
You can update your arm9loaderhax installation in the future by following the instructions on the
Updating arm9loaderhax page.
To use
NTR CFW, get ntr.bin from the appropriate zip on
this page and copy it to the root of your SD card, then install BootNTR.cia from
this page.
You can remove any extra files from the root of the SD card that are not in the image