3DS:Troubleshooting

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  file. If you're running, your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your  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  on your SD card or on internal memory.
 * Magenta: Your 3DS was not able to find  on your SD card. It was able to find   on internal memory, but the file is corrupted.
 * Red: Your 3DS was able to find  on both your SD card and on internal memory, but both files are corrupted.

You can get a new  file by downloading the latest release of, extracting it, and placing   on the root of your SD card. If your  file is consistently being detected as corrupted, you may want to check your SD card for errors. 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
Follow the black screen unbrick guide

=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 and place   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:
 * 1) Power off your console
 * 2) Hold (Select)
 * 3) Power on your console, while still holding (Select)
 * 4) 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, extract   from the   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  (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: Checking SD card integrity. 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  (the   file)
 * 2) Power off your console
 * 3) Create a folder named   on the root of your SD card if it does not already exist
 * 4) Copy   to the   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  to uninstall the broken TWL titles
 * 9) Press  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"
 * 11) * The update will see that the essential TWL titles have been uninstalled, and will redownload and reinstall them
 * 12) 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 follow removing menuhax67

=Other troubleshooting=

Clear HOME Menu extdata

 * 1) Power off your console
 * 2) Insert your SD card into your computer
 * 3) Navigate to the   folder on your SD card
 * 4) Delete the corresponding folder for your 3DS region:
 * 5) * EUR Region:
 * 6) * JPN Region:
 * 7) * USA Region:
 * 8) * CHN Region:
 * 9) * KOR Region:
 * 10) * TWN Region:
 * 11) 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   folder on your SD card
 * 4) Delete the corresponding folder for your 3DS region:
 * 5) * EUR Region:
 * 6) * JPN Region:
 * 7) * USA Region:
 * 8) Reinsert your SD card into your console

Manually entering Homebrew Launcher
Follow manually entering homebrew launcher

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:
 * 3) * Device Type: Select "3DS" (the same applies if you are using a 2DS, New 3DS (XL/LL) or New 2DS (XL/LL))
 * 4) * System Date: The day and month your console's clock is set to
 * 5) * Inquiry Number: Can be obtained by pressing "Forgot PIN" then "I Forgot" in the Parental Controls screen
 * 6) After you have obtained your mkey, press OK on the screen you have obtained your Inquiry Number, then input the master key
 * 7) Press "Clear Settings", then "Delete" to remove all Parental Controls data