Troubleshooting

For support in English, ask for help at Nintendo Homebrew on Discord.
If you appreciate this guide, we accept Donations.

This page offers troubleshooting advice for commonly encountered issues. If you are unable to solve your issue with the advice on this page, please join Nintendo Homebrew on Discord and describe your issue, including what you have already tried.

Issues with SafeB9SInstaller

SigHaxed FIRM was not installed! Check lower screen for more info.

SigHaxed FIRM - File not found

You are missing boot9strap.firm and boot9strap.firm.sha from the boot9strap folder, or the boot9strap folder is misnamed. Download the latest release of boot9strap, and place boot9strap.firm and boot9strap.firm.sha in the boot9strap folder.

SigHaxed FIRM - invalid FIRM

There is an issue with your boot9strap.firm and boot9strap.firm.sha files. Re-download the latest release of boot9strap, and place boot9strap.firm and boot9strap.firm.sha in the boot9strap folder.

Secret Sector - File not found

You are missing secret_sector.bin from the boot9strap folder, or the boot9strap folder is misnamed. Download secret_sector.bin using a torrent client, and place it in the boot9strap folder.

Something else

Join Nintendo Homebrew on Discord for assistance, and describe the message that you see.

Seedminer

Multiple long folder names in Nintendo 3DS folder

This occurs when you use your SD card in multiple 3DS devices and is intended to prevent inadvertently merging data that would not be valid on other devices. To figure out which long folder name is correct for your 3DS, follow these instructions:

  1. Rename the Nintendo 3DS folder to BACKUP_Nintendo 3DS
  2. Reinsert your SD card into your device and power on your device
  3. Wait for the device to generate the SD card data
    • Your applications will have disappeared. This is normal and will be resolved shortly
  4. Power off your device and reinsert your SD card into your computer
  5. Navigate to the Nintendo 3DS folder on your SD card
  6. Copy the 32 character long name of the folder you see
  7. Delete the Nintendo 3DS folder
  8. Rename the BACKUP_Nintendo 3DS folder to Nintendo 3DS

Bruteforce Movable skips to step 4

The website has already mined your movable.sed using your friend code and ID0 combination. You can use the movable.sed that it provides you.

Important! You have been locked out of the automated part1 dumper system…

Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join Nintendo Homebrew on Discord and ask to be unlocked.

We were unable to successfully complete your bruteforce request. :`(

The website has determined that your movable.sed cannot be brute-forced. Ensure that you gave the correct ID0 to the website. If your ID0 is correct, then you will be unable to use Seedminer and you will have to use an alternate method that will require additional games or hardware.

Homebrew Launcher (PicHaxx)

“An error has occurred. Hold down the POWER button to turn off the power…” (black screen with text)

Your 00000001.sav and/or otherapp.bin files may be misplaced. Ensure that 00000001.sav is in Nintendo 3DS -> <ID0> -> <ID1> -> title -> 00040000 -> 0017c100 -> data and that otherapp.bin is on the root of your SD card.

If your files are in the correct locations, re-create the save using the PicHaxx Save Tool, then place it in Nintendo 3DS -> <ID0> -> <ID1> -> title -> 00040000 -> 0017c100 -> data. Ensure that the file is named exactly 00000001.sav and that you used your console’s movable.sed to create it. Re-download the latest release of unSAFE_MODE, place the .bin file relevant to your console from the otherapps_with_CfgS folder to the root of your SD card, and rename it to otherapp.bin. Do not add the .bin extension if you do not already see it.

“An exception occurred” or Errdisp when opening Picross

Your device already has custom firmware. You should check for CFW.

“An error has occurred, forcing the software to close…” (white message box)

There is an issue with your otherapp.bin file. Download the latest release of unSAFE_MODE, place the .bin file relevant to your console from the otherapps_with_CfgS folder to the root of your SD card, and rename it to otherapp.bin. Do not add the .bin extension if you do not already see it.

Game starts normally

Your modified 00000001.sav file may be misplaced, or you may have used the wrong movable.sed when creating it. Re-generate your movable.sed from Bruteforce Movable, then re-create the save using the PicHaxx Save Tool and place the resulting file (00000001.sav) in Nintendo 3DS -> <ID0> -> <ID1> -> title -> 00040000 -> 0017c100 -> data.

Installing boot9strap (Soundhax)

Red/purple/pink and white screen after running Soundhax

If your device is on system version 9.4.0, 9.5.0, or 9.6.0, you may be encountering a bug with an old version of universal-otherapp. Download the latest version from here.

If your device is not on those firmwares, it likely indicates that you already have custom firmware. You should check for CFW.

“An error has occurred, forcing the software to close…” (white message box)

There is an issue with your otherapp.bin file (it is missing, misplaced, or corrupted). Download the latest release of universal-otherapp and place it on the root of your SD card.

“Could not play”

You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow Seedminer.

Failed to open SafeB9SInstaller.bin

The file SafeB9SInstaller.bin is missing or misplaced. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

Failed to mount the SD card!

Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system (Windows, macOS, Linux). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.

If this is unsuccessful, try using another SD card.

Installing boot9strap (SSLoth-Browser)

Red/purple/pink and white screen after running browserhax

This likely indicates that you already have custom firmware. You should check for CFW.

“An error has occurred. Hold down the POWER button to turn off the power…” (black screen with text)

The file arm11code.bin is missing or misplaced. Download the latest release of universal-otherapp, place otherapp.bin on the root of your SD card and rename it to arm11code.bin. Do not add the .bin extension if you do not already see it.

“An error has occurred, forcing the software to close…” (white message box)

There is an issue with your arm11code.bin file. Download the latest release of universal-otherapp, place otherapp.bin on the root of your SD card and rename it to arm11code.bin. Do not add the .bin extension if you do not already see it.

Opening the browserhax QR code or URL crashes

Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.

  1. Launch the browser, then launch the browser settings
  2. Scroll to the bottom and Initialize Savedata (it also may be called Clear All Save Data)
  3. Try the exploit again

Opening the browser prompts for a system update instead

The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.

Error 032-0420 when trying to open the browser

Follow these steps in order:

  1. Launch the System Settings application
  2. Navigate to Internet Settings -> Connection Settings
  3. Click on your network connection slot and navigate to Change Settings -> Next Page (right arrow) -> Proxy Settings
  4. Set “Proxy Settings” to “No”
  5. Click OK, then click Save
  6. When prompted, click “Test” to perform the connection test
    • The test should succeed
  7. Click “OK” to continue
  8. Press “Back” twice, then “Close” to go back to the HOME Menu
  9. Open the Internet Browser once
  10. If prompted about a system update, press OK
    • This won’t actually update the system
  11. Start again from Section II

Failed to open SafeB9SInstaller.bin

The file SafeB9SInstaller.bin is missing or misplaced. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

Frozen on “Doing agbhax…”

There may be an issue with your arm11code.bin file. Re-download the latest release of universal-otherapp, place it on the root of your SD card, and rename it to arm11code.bin. Do not add the .bin extension if you do not already see it.

If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow Seedminer instead.

If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join Nintendo Homebrew on Discord for assistance.

“PrepareArm9ForTwl returned error c8804631!”

You will need to follow an alternate method. Join Nintendo Homebrew on Discord for assistance.

Failed to mount the SD card!

Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system (Windows, macOS, Linux). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.

If this is unsuccessful, try using another SD card.

BannerBomb3

DSiWare Management menu crashes without showing BB3 multihax menu

Ensure that F00D43D5.bin is the only file in Nintendo 3DS -> <ID0> -> <ID1> -> Nintendo DSiWare. If it is, then re-create it with the Bannerbomb3 Injector.

Also, ensure that bb3.bin is on the root of the SD card. If it is missing, then download the latest release of Bannerbomb3 (direct download), and copy the bb3.bin file to the root of your SD card.

If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this device in a way that makes this method impossible to perform. If this is the case and Safe Mode works, you will need to follow an alternate branch of Seedminer. If Safe Mode doesn’t work or you need assistance with this matter, join Nintendo Homebrew on Discord and ask, in English, for help.

DSiWare Management menu does not crash

F00D43D5.bin is missing from Nintendo 3DS -> <ID0> -> <ID1> -> Nintendo DSiWare. Make sure that Nintendo DSiWare is correctly spelled and spaced. Uppercase/lowercase does not matter.

DSiWare Management shows a question mark

There may be an issue with your F00D43D5.bin file (it may be corrupted or intended for the wrong 3DS). Re-create your F00D43D5.bin file with the Bannerbomb3 Injector, ensuring that you use the movable.sed file for your console.

Installing boot9strap (USM)

Update doesn’t fail with error code 003-1099

unSAFE_MODE is not installed. Follow the instructions on your page to install unSAFE_MODE again.

Red screen when selecting detailed setup

The file usm.bin is missing or misplaced. Download the latest release of unSAFE_MODE and place usm.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

There is also a possibility that the console isn’t reading your SD card. Make sure it is inserted and formatted correctly.

Failed to open SafeB9SInstaller.bin

The file SafeB9SInstaller.bin is missing or misplaced. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

Failed to mount the SD card!

Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system (Windows, macOS, Linux). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.

If this is unsuccessful, try using another SD card.

Installing boot9strap (Fredtool)

Error on Fredtool Injector page

Ensure that your movable.sed and DSiWare backup come from the same console. A mismatch will result in an error.

Unable to select the “Haxxxxxxxxx!” title because of the BB3 multihax menu

You forgot to delete F00D43D5.bin from the SD card. Navigate to Nintendo 3DS -> <ID0> -> <ID1> -> Nintendo DSiWare on your SD card and delete the F00D43D5.bin file.

“Haxxxxxxxxx!” does not appear

There is an issue with your 42383821.bin file (it is incorrect, missing, misplaced, or corrupted). Re-create your files with the DSIHaxInjector_new website and ensure that you place the 42383821.bin file from output.zip -> hax in Nintendo 3DS -> <ID0> -> <ID1> -> Nintendo DSiWare.

DS Connection Settings launches normally

Haxxxxxxxxx! was not copied from your SD card to your system memory.

Black screen when launching DS Connection Settings

Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join Nintendo Homebrew on Discord for assistance.

SD card is grayed out

Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.

Lenny face does not appear

You did not copy the private folder from the Frogminer_save .zip to the root of your SD card.

Flipnote is frozen

You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don’t accidentally use the touchscreen.

Green screen after pasting

The file boot.nds is missing or misplaced. Download the latest release of b9stool and place boot.nds on the root of your SD card, replacing the existing one.

White screen after pasting

There is an issue with your boot.nds file. Re-download the latest release of b9stool and place boot.nds on the root of your SD card, replacing the existing one.

Unable to open Luma3DS configuration menu after running b9stool

It is possible that boot9strap was not successfully installed. Follow section B of this page.

Finalizing Setup

Unable to update device

The steps below can be attempted in any order, but are listed from easiest to hardest to perform.

  1. Set your DNS settings to “Auto”
  2. Move closer to your WiFi router
  3. Update from Safe Mode by turning off the console, holding (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A) on boot, and following the on-screen prompts
  4. Delete your WiFi connection, then reconnect to your WiFi again
  5. Reboot your WiFi router
  6. Connect to a different WiFi connection, like a mobile hotspot
  7. Nintendo servers may be down; Try again later
  8. If you still get an error, follow CTRTransfer, then try again
  9. For further support (in English), join Nintendo Homebrew on Discord

Unable to enter Rosalina due to broken button(s)

Download this alternate config.ini and place it in /luma/. This will change the Rosalina key combination to (X) + (Y).

“An exception occurred” after trying to launch Homebrew Launcher via Download Play

There is an issue with your boot.3dsx file (it is missing, misplaced, or corrupted). Download the latest release of the Homebrew Launcher and place boot.3dsx on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.

“Scripts directory not found” in GodMode9

You did not copy the gm9 folder from the GodMode9 .zip to the root of your SD card. Download the latest release of GodMode9 and place the gm9 folder on the root of your SD card, merging it with the existing one.

essentials.exefs missing from /gm9/out/

Your device had custom firmware in the past, so you were not automatically prompted to make a backup. Make a backup manually:

  1. Reinsert your SD card into your device
  2. Press and hold (Start), and while holding (Start), power on your device. This will launch GodMode9
  3. Navigate to [S:] SYSNAND VIRTUAL
  4. Select essentials.exefs, then Copy to 0:/gm9/out/
  5. You should now have essentials.exefs in /gm9/out/

The steps detailed here generally assume that your device has a modern custom firmware setup (boot9strap + Luma3DS 8.0 or greater). If your console is running an older homebrew setup (for example, something based on arm9loaderhax or menuhax), you should update your setup before trying these instructions.

My device powers off when I try to turn it on, and/or the notification LED shows a color on boot

There is an issue with your boot.firm file. If you’re running boot9strap 1.4, your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your boot.firm file on SD card or internal memory. On older versions of boot9strap, the blue light will power off almost immediately when trying to turn on the device.

If the notification LED flashes:

  • White: Your 3DS was not able to find boot.firm on your SD card or on internal memory.
  • Magenta: Your 3DS was not able to find boot.firm on your SD card. It was able to find boot.firm on internal memory, but the file is corrupted.
  • Red: Your 3DS was able to find boot.firm on both your SD card and on internal memory, but both files are corrupted.

You can get a new boot.firm file by downloading the latest release of Luma3DS, extracting it, and placing boot.firm on the root of your SD card. If your boot.firm file is consistently being detected as corrupted, you may want to check your SD card for errors (Windows, Linux, or macOS). Also, note that the 3DS tends to have issues with files extracted using WinRAR.

If you hear a “popping sound”, potentially accompanied with the backlight turning on for a split second, there is a hardware issue with your device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.

My device gets stuck on a black screen, with a static blue light

The steps below can be attempted in any order, but are listed from least to most time-consuming.

  1. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
  2. Rename the Nintendo 3DS folder on your SD card to Nintendo 3DS_BACKUP, then attempt to boot. If your device successfully boots, there is some issue within your Nintendo 3DS folder. Try clearing HOME Menu extdata:
    • Navigate to /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ + Delete the corresponding folder for your 3DS region:
      • EUR Region: 00000098
      • JPN Region: 00000082
      • USA Region: 0000008f
      • CHN Region: 000000A1
      • KOR Region: 000000A9
      • TWN Region: 000000B1
  3. Try booting into recovery mode and updating your system:
    • Power off your device
    • Hold (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A)
    • Power on your device
    • If you were successful, the device will boot to an “update your system” screen
  4. Follow the CTRTransfer guide
  5. For further support, ask for help at Nintendo Homebrew on Discord

My device boots to an error screen

“An error has occurred: Failed to apply 1 FIRM patch(es)” or “An exception has occurred – Current process: pm”

Your Luma3DS version is outdated. Download the latest release of Luma3DS and place boot.firm on the root of your SD card, replacing any existing file. Make sure you are extracting the ZIP file with any tool other than WinRAR, as it is known to cause issues with 3DS-related files.

“An error has occurred. Hold down the POWER button to turn off the power…”

ARM11 exception handlers are disabled, or custom firmware is not installed. Try enabling ARM11 exception handlers:

  • Power off your device
  • Hold (Select)
  • Power on your device, while still holding (Select)
  • If the “Disable ARM11 exception handlers” box is checked, uncheck it

Some other error

Please take a photo of the error and join Nintendo Homebrew on Discord for assistance.

Blue “Bootrom Error” screen

Your device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. This may also indicate a hardware issue that cannot be fixed. In any case, join Nintendo Homebrew on Discord for assistance.

  • It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your device powered on, waiting on the blue screen, for five minutes.

DSi / DS functionality is broken or has been replaced with Flipnote Studio

  1. Download the latest release of TWLFix-CFW (the .3dsx file)
  2. Power off your device
  3. Create a folder named 3ds on the root of your SD card if it does not already exist
  4. Copy TWLFix-CFW.3dsx to the /3ds/ folder on your SD card
  5. Reinsert your SD card into your device
  6. Open the Homebrew Launcher
  7. Launch TWLFix-CFW from the list of homebrew
  8. Press (A) to uninstall the broken TWL titles
  9. Press (Start) to reboot the device
  10. Perform a System Update by going to System Settings, then “Other Settings”, then going all the way to the right and using “System Update”
    • The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
  11. Once the update is complete, tap “OK” to reboot the device

GBA Virtual Console and/or Safe Mode functionality is broken

Your device is running Luma3DS/AuReiNand 6.6 or older, likely via arm9loaderhax. You should follow A9LH to B9S to update your device to a modern custom firmware environment.

Extended memory mode games are broken

This can occur after a CTRTransfer or region change on Old 3DS / 2DS. You will need to system format your device to fix this issue.

Other troubleshooting

Clear HOME Menu extdata

  1. Power off your device
  2. Insert your SD card into your computer
  3. Navigate to the /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ folder on your SD card
  4. Delete the corresponding folder for your 3DS region:
    • EUR Region: 00000098
    • JPN Region: 00000082
    • USA Region: 0000008f
    • CHN Region: 000000A1
    • KOR Region: 000000A9
    • TWN Region: 000000B1
  5. Reinsert your SD card into your device

Clear HOME Menu theme data

  1. Power off your device
  2. Insert your SD card into your computer
  3. Navigate to the /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ folder on your SD card
  4. Delete the corresponding folder for your 3DS region:
    • EUR Region: 000002ce
    • JPN Region: 000002cc
    • USA Region: 000002cd
  5. Reinsert your SD card into your device