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.

Table of Contents

Used on multiple pages:

Guide pages:

Issues after installation:

Issues with SafeB9SInstaller

Before opening SafeB9SInstaller

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.

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

MicroSD Card - init failed

Your SD card is most likely acting weird. Try reformatting your SD card (Windows, macOS, Linux). If this doesn’t work, try another SD card.

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 consoles and is intended to prevent inadvertently merging data that would not be valid on other consoles. 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 console
  3. Power on your console
  4. Wait for the console to generate the SD card data
    • Your applications will have disappeared. This is normal and will be resolved shortly
  5. Power off your console
  6. Insert your SD card into your computer
  7. Navigate to the Nintendo 3DS folder on your SD card
  8. Copy the 32 character long name of the folder you see
  9. Delete the Nintendo 3DS folder
  10. 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.

If you have a New 3DS / New 3DS XL / New 2DS XL (as indicated by the four shoulder buttons on the back and the C-Stick on the right), you can follow Installing boot9strap (super-skaterhax). Otherwise, you will need to follow a method that requires additional games or hardware.

BannerBomb3

Multiple ID1 folders inside of ID0

This can occur if you’ve used multiple SD cards on a 3DS and then merged the contents of the SD cards together. This is done to prevent conflicting, valid data from being merged together.

To fix this, you will need to determine which folder contains your data. Usually, this will be the larger (or largest) of the folders. Backup and delete the smaller one(s), then create a Nintendo DSiWare folder in the one that remains and move F00D43D5.bin to that location.

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 from the Release .zip to the root of your SD card.

If neither of these solutions fixes this problem, then custom firmware may have been uninstalled on this console in a way that makes this method impossible to perform. If this is the case, join Nintendo Homebrew on Discord and ask, in English, for help.

DSiWare Management menu displays "No accessible software data."

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 (Fredtool-Inject)

Error on DSiHaxInjector page

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

"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.

DSiWare launches normally

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

SD card is grayed out in Flipnote

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 in SD card section

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

Flipnote freezes

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

Join Nintendo Homebrew on Discord and explain what has happened.

Installing boot9strap (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 HBL otherapps, place the .bin file relevant to your console 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 console 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 HBL otherapps, place the .bin file relevant to your console 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 console 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 console 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 console and region, or your console is incompatible with Soundhax. In the latter case, your course of action will determine on what version your 3DS is currently on. 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.

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 may be 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.

You can also try resetting your browser save data:

  1. Launch the browser, then launch the browser settings
  2. Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
  3. Try the exploit again
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 select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
  3. Try the exploit again
System Update prompt when opening browser

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

Error 032-0420 when opening browser

Follow these steps in order:

  1. Launch System Settings on your console
  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
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.

"PrepareArm9ForTwl returned error c8804631!"

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.

Installing boot9strap (super-skaterhax)

"An error has occurred. Please save your data in any software currently in use, then restart the system."

The date is set incorrectly. To set it correctly, follow these steps:

  1. Select the System Settings icon on the HOME Menu, and tap Open.
  2. Tap Other Settings.
  3. Tap Date & Time.
  4. Tap Today’s date.
  5. Tap Up/Down Arrows to set the correct Day, Month and Year.
  6. Select OK to confirm.

If the problem persists:

  • Ensure that arm11code.bin, browserhax_hblauncher_ropbin_payload.bin, and boot.3dsx are on the root of the SD card (not inside of any folder)
  • Ensure that you selected the correct payload for your region AND system version
  • Ensure that your region settings look like this
  • Try resetting your browser data:
    1. Launch the browser, then launch the browser settings
    2. Scroll to the bottom and select “Reset Save Data” (it may also be called “Initilize Save Data” or “Clear All Save Data”)
    3. Try the exploit again
  • Try changing the system language to something other than the current language
"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. Make sure to copy the files of the latest version of super-skaterhax for your region and version to the root of your SD card (not inside of a folder).

An exception occured or "DLL_HEAP_INFORMATION" when pressing GO! GO!

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

Installing boot9strap (MSET9)

(title/import).db does not exist, create them now?" / invalid database

Full error messages:

  • “Nintendo 3DS/<ID0>/<ID1>/dbs/<import.db and/or title.db> does not exist on SD card! Create them now? (type yes/no)”
  • “Invalid database”

This happens when no valid title database is present, usually because you never installed any titles from eShop on this SD card.

  1. Type “yes”, then press Enter
  2. Insert the SD card into your console
  3. Power on your console
  4. Navigate to System Settings -> Data Management -> Nintendo 3DS -> Software -> Reset (visual instructions)
  5. Power off your console
  6. Insert the SD card into your computer
  7. Return to Section I Step 7
[WinError 5] Access is denied

The SD card may be write-locked. If you are using a full-size SD card, ensure that the lock is flipped in the upright position. Otherwise, try ejecting and reinserting your SD card.

UnboundLocalError: cannot access local variable 'haxid1_path'

This can happen when Option 1 stopped because of an error and there is an incomplete installation.

  1. Close the script window
  2. Execute the mset9.py script on the root of the SD card
    • Windows: Double-click mset9.bat +If this doesn’t work: hold SHIFT and right-click anywhere in the SD card window, then click the option that opens Terminal, PowerShell, or Command Prompt, then type py -3 mset9.py and press Enter
    • Linux: open a Terminal window, cd to the root of your SD card, then type python3 mset9.py and press Enter
    • You should see a window that says “MSET9 … SETUP by zoogie”
  3. Type the number corresponding to your console model and version, then press Enter
  4. Type 4, then press Enter to remove MSET9
  5. Return to the beginning of Section I
Red screen after reinserting SD card (Section II Step 11)

You may be missing SafeB9S.bin from the root of your SD card, or the file may be corrupted. Copy it from the SDMC folder in the MSET9 .zip, replacing any existing files.

Alternatively, your SD card may be improperly formatted or partitioned. Try reformatting your SD card: Windows, Linux (this will wipe your SD card data)

assert(id0_count == 1) AssertionError

You have multiple ID0 folders. To determine the correct folder, follow these instructions:

  1. Rename the Nintendo 3DS folder to BACKUP_Nintendo 3DS
  2. Reinsert your SD card into your console
  3. Power on your console
  4. Wait for the console to generate the SD card data
    • Your applications will have disappeared. This is normal and will be resolved shortly
  5. Power off your console
  6. Insert your SD card into your computer
  7. Navigate to the Nintendo 3DS folder on your SD card
  8. Write down the first few characters of the folder you see
    • This is your true ID0, which we will keep in the real Nintendo 3DS folder
  9. Delete the ID0 from the current Nintendo 3DS folder
  10. Move the true ID0 folder from the BACKUP_Nintendo 3DS folder to the Nintendo 3DS folder
  11. If it exists, move the Private folder from the BACKUP_Nintendo 3DS folder to the Nintendo 3DS folder

Once you’ve done this, continue from Section I Step 7.

assert(mii_ok==1) AssertionError

Your SD card does not have Mii Maker Data, which is necessary for this exploit to run.

  1. Close the script window
  2. Execute the mset9.py script on the root of the SD card
    • Windows: Double-click mset9.bat
      • If this doesn’t work: hold SHIFT and right-click anywhere in the SD card window, then click the option that opens Terminal, PowerShell, or Command Prompt, then type py -3 mset9.py and press Enter
    • Linux: open a Terminal window, cd to the root of your SD card, then type python3 mset9.py and press Enter
    • You should see a window that says “MSET9 … SETUP by zoogie”
  3. Type the number corresponding to your console model and version, then press Enter
  4. Type 4, then press Enter to remove MSET9
  5. Insert the SD card into your console
  6. Power on your console
  7. Launch Mii Maker
  8. Wait for your console to reach the “Welcome to Mii Maker” screen, then exit Mii Maker
  9. Power off your console
  10. Insert the SD card into your computer
  11. Return to Section I Step 7
System Settings loading infinitely after reinserting the SD card

You most likely did something different from the MSET9 instructions, or selected the wrong model or version.

  1. Close the script window
  2. Execute the mset9.py script on the root of the SD card
    • Windows: Double-click mset9.bat
      • If this doesn’t work: hold SHIFT and right-click anywhere in the SD card window, then click the option that opens Terminal, PowerShell, or Command Prompt, then type py -3 mset9.py and press Enter
    • Linux: open a Terminal window, cd to the root of your SD card, then type python3 mset9.py and press Enter
    • You should see a window that says “MSET9 … SETUP by zoogie”
  3. Type the number corresponding to your console model and version, then press Enter
  4. Type 3, then press Enter
  5. Once the window says “Deleting… done.”, insert the SD card into your console
  6. Power on your console
  7. Return to Section II Step 1

If you continue to have this issue and are sure that you did everything correctly, it’s possible that there’s something wrong with your Mii Maker extdata. Follow these instructions to reset it:

  1. Close the script window
  2. Execute the mset9.py script on the root of the SD card
    • Windows: Double-click mset9.bat
      • If this doesn’t work: hold SHIFT and right-click anywhere in the SD card window, then click the option that opens Terminal, PowerShell, or Command Prompt, then type py -3 mset9.py and press Enter
    • Linux: open a Terminal window, cd to the root of your SD card, then type python3 mset9.py and press Enter
    • You should see a window that says “MSET9 … SETUP by zoogie”
  3. Type the number corresponding to your console model and version, then press Enter
  4. Type 4, then press Enter to remove MSET9
  5. Insert the SD card into your console
  6. Power on your console
  7. Launch Mii Maker
  8. Wait for your console to reach the “Welcome to Mii Maker” screen, then exit Mii Maker
  9. Power off your console
  10. Insert the SD card into your computer
  11. Return to Section I Step 7

Finalizing Setup

Unable to update console

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
Error #02: Missing essential.exefs

You said ‘No’ to the “Make essential files backup?” prompt in GodMode9. Power off your console, power it on while holding (Start) to re-enter GodMode9, say ‘Yes’ to the prompt, then try again.

Unable to open GodMode9 or Error #03: Missing files

You did not copy everything from finalize.zip to the root of your SD card. Remember, your SD card should have at least these files:

Error #04: No space

You need at least 1.3GB of free space to perform the NAND backup, which is a part of the script. If you don’t have enough space, follow these steps:

  1. Power off your console
  2. Insert your SD card into your computer
  3. Copy the Nintendo 3DS folder from the root of your SD card to your computer
  4. Delete the Nintendo 3DS folder from the SD card
  5. Reinsert your SD card into your console
  6. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
  7. Press the (Home) button
  8. Select “Scripts…”
  9. Select “finalize”
  10. Press (A) to create a NAND backup
    • This may take around fifteen minutes
  11. Press (A) again
    • The console should automatically power off
  12. Insert your SD card into your computer
  13. Copy the files in /gm9/backups/ on your SD to a safe location on your computer
  14. Delete the <date>_<serialnumber>_sysnand_##.bin and <date>_<serialnumber>_sysnand_##.bin.sha files from the SD card
  15. Copy the Nintendo 3DS folder from your computer to the root of your SD card
  16. Delete the Nintendo 3DS folder from your computer

Now that you have your NAND backup in a safe place:

  1. Reinsert your SD card into your console
  2. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
  3. Press the (Home) button
  4. Select “Scripts…”
  5. Select “finalize”
  6. Continue the script as normal
    • The NAND backup will be automatically skipped
Information #05: No title database

Press (A) to import a title database, unlock SysNAND writing by entering the buttons on-screen, then continue the script as normal.

Error #06 or "Error: Could not open directory" when attempting a NAND backup

Make sure you have at least 1.3GB available in your SD card. If you don’t have enough space, follow these steps:

  1. Power off your console
  2. Insert your SD card into your computer
  3. Copy the Nintendo 3DS folder from the root of your SD card to your computer
  4. Delete the Nintendo 3DS folder from the SD card
  5. Reinsert your SD card into your console
  6. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
  7. Perform a NAND Backup
  8. Copy the files in gm9/out on your SD to a safe location on your computer
  9. Delete the <date>_<serialnumber>_sysnand_##.bin and <date>_<serialnumber>_sysnand_##.bin.sha files from the SD card, keeping essential.exefs in /gm9/out/
  10. Copy the Nintendo 3DS folder from your computer to the root of your SD card
  11. Delete the Nintendo 3DS folder from your computer

If you have enough space on your SD card, your SD might be corrupted or faulty. Check your SD card for any errors by following the guide according to your computer’s operating system: Windows, Linux, macOS.

Error #09: Unsupported GodMode9 version

You are somehow running a version of GodMode9 not packaged with the script. Make sure you copied the contents of finalize.zip to the root of your SD card and that you are holding START while powering on your console.

Error #11: Missing donor database

You did not copy everything from finalize.zip to the root of your SD card. Remember, your SD card should have at least these files:

Error #12: Copy (file).db fail

Ensure that your SD card is not locked. If the SD card is not locked and you continue to get this error, join Nintendo Homebrew on Discord for assistance.

Information #17: Duplicate NAND backup

The script has detected that the Nintendo 3DS folder is missing AND that you have already made a NAND backup before. If you intend to install homebrew applications, you should do the following:

  1. Press (B) to cancel making another NAND backup
  2. Hold (R) and press (Start) at the same time to power off your console
  3. Copy the contents of /gm9/backups/ to a safe location on your computer
  4. Delete /gm9/backups/ from your SD card
  5. If you moved your Nintendo 3DS folder off of your SD card to get to this point, copy it back to your SD card
    • If you do not have a Nintendo 3DS folder, boot into the HOME Menu at least once with the SD card inserted to automatically generate it
  6. Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
  7. Press (Home) to bring up the action menu
  8. Select “Scripts…”
  9. Select “finalize”
  10. Follow the prompts in the script, answering any questions that you are asked

Boot issues on consoles with custom firmware

The steps detailed here generally assume that your console 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.

Power/notification light indicators

My console 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 console.

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 console (such as a disconnected backlight cable). You may be able to get your console to boot by holding it at certain angles.

My console gets stuck on a black screen with blue power light staying on

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

  1. Power off your console, remove the SD card, re-insert it, then power on your console.
  2. Power off your console, eject the game cartridge if inserted, power on your console, then wait up to ten minutes. If your console boots within ten minutes, the issue has been fixed and is unlikely to reoccur
  3. Rename the Nintendo 3DS folder on your SD card to Nintendo 3DS_BACKUP, then attempt to boot. If your console 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
  4. Try booting into recovery mode and updating your system:
    • Power off your console
    • Hold (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A)
    • Power on your console
    • If you were successful, the console will boot to an “update your system” screen
  5. Follow the CTRTransfer guide
  6. For further support, ask for help at Nintendo Homebrew on Discord

Error message on boot

"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.

"Unable to mount CTRNAND or load the CTRNAND FIRM. Please use an external one."

There are a number of reasons as to why this could be happening. In any case, this error can usually be fixed by following the CTRTransfer guide.

"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 console + Hold (Select) + Power on your console, while still holding (Select) + If the “Disable ARM11 exception handlers” box is checked, uncheck it

HOME Menu is missing installed applications

This could be caused by various reasons, but most likely because your SD card is not being read by the system. You can check if your SD is being read by holding SELECT on boot and checking the yellow text on the bottom screen; if it says “Booted from CTRNAND via B9S”, then your console is booting from the internal memory and not from the SD card. If this is the case, attempt the steps below, which are listed from easiest to hardest:

  1. Power off your console, remove the SD card, re-insert it, then power on your console
  2. Power off your console, remove the SD card, insert it on your computer, download the latest release of Luma3DS, extract boot.firm from the Luma3DS.zip and place it on the root of your SD card (replacing any existing file)
  3. Power off your console, remove the SD card, insert it on your computer and reformat your SD card according to your computer’s operating system: Windows, macOS, Linux (this will wipe your SD card data)
  4. Test your SD card for errors by following the guide according to your computer’s operating system: Windows, Linux, macOS. If your SD card is marked as faulty, then you will have to replace your SD card
  5. Your SD card slot may be broken. Join Nintendo Homebrew on Discord for further assistance
Blue "BOOTROM ERROR" screen

Your console is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your console. 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 console powered on, waiting on the blue screen, for five minutes.

Some other error

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

Software issues on consoles with custom firmware

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 console
  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 console
  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 console
  10. Update your console 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 console
GBA Virtual Console and/or Safe Mode functionality is broken

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

Extended memory mode games (Pokemon Sun/Moon, Smash, etc.) don't work

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

Exception screen when booting/loading an application

Look for your exception screen in this page. If you weren’t able to find your error or the instructions didn’t work, join Nintendo Homebrew on Discord for further assistance.

Opening the HOME Menu settings crashes the console or loads the Homebrew Launcher

Your console likely still has menuhax67 installed. To uninstall menuhax67, download the latest release of menuhax67 (the menuhax .zip), then follow the “Uninstall menuhax67” section here.

Other troubleshooting

Clear HOME Menu extdata
  1. Power off your console
  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 console
Clear HOME Menu theme data
  1. Power off your console
  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 console
Manually entering Homebrew Launcher

If you are missing the Homebrew Launcher application from your HOME Menu, you can follow these instructions to manually enter the Homebrew Launcher. (You will need boot.3dsx and boot.firm on the root of your SD card.)

  1. Launch the Download Play application ()
  2. Wait until you see the Nintendo 3DS and Nintendo DS buttons
  3. Press (Left Shoulder) + (D-Pad Down) + (Select) at the same time to open the Rosalina menu
  4. Select “Miscellaneous options”
  5. Select “Switch the hb. title to the current app.”
  6. Press (B) to continue
  7. Press (B) to return to the Rosalina main menu
  8. Press (B) to exit the Rosalina menu
  9. Press (Home) to suspend Download Play
  10. Press the “Close” button on the bottom screen to close Download Play
  11. Re-launch the Download Play application
  12. Your console should load the Homebrew Launcher
    • If your console is stuck on the loading splash screen, you are missing boot.3dsx from the root of your SD card
Turning off Parental Controls

You can disable the Parental Controls feature by going to System Settings -> Parental Controls and inserting the PIN, then pressing “Clear Settings”, then “Delete” to remove it. However, if you do not know the PIN and therefore cannot access the console’s settings, you will need to disable it. In order to do this, you need to obtain your console’s master key (mkey):

  1. Go to this website
  2. Fill the following boxes with the information:
    • Device Type: Select “3DS” (the same applies if you are using a 2DS, New 3DS (XL/LL) or New 2DS (XL/LL))
    • System Date: The day and month your console’s clock is set to
    • Inquiry Number: Can be obtained by pressing “Forgot PIN” then “I Forgot” in the Parental Controls screen
  3. After you have obtained your mkey, press OK on the screen you have obtained your Inquiry Number, then input the master key
  4. Press “Clear Settings”, then “Delete” to remove all Parental Controls data