When a 3DS boots to a black screen instead of the HOME Menu, it is usually a bad sign. This page lists common troubleshooting steps to fix this issue.
When a 3DS boots to a black screen instead of the HOME Menu, it is usually a bad sign. This page lists common troubleshooting steps to fix this issue.
The troubleshooting below should always be started at the first section. The troubleshooting will direct you to the next sections if necessary.
First and foremost, you need to check if the console has a custom firmware installed.
__TOC__
__TOC__
==CFW Check==
==CFW Check==
First, we will check if the console has CFW. This will help as it allows access to [[3DS:GodMode9|GodMode9]], a helpful tool for troubleshooting and fixing issues.
Checking if the console has CFW will help as it allows access to [[3DS:GodMode9|GodMode9]], a helpful tool for troubleshooting and fixing issues.
#Power on your console while holding the {{B|SELECT}} button
#Power on your console while holding the {{B|SELECT}} button
Line 17:
Line 17:
#***To make sure of this, hold {{Key press|SELECT|START|X|POWER}} for seven seconds while the console is powered off, then power off again, hold {{B|HOME}}, and then press {{B|POWER}} - if the notification LED [[3DS:boot9strap#LED_Status_Codes|lit up a color]] or the [[3DS:fastboot3DS|fastboot3DS]] menu appears, then you have working CFW but something is interfering with Luma. Join the Nintendo Homebrew Discord for more advanced help
#***To make sure of this, hold {{Key press|SELECT|START|X|POWER}} for seven seconds while the console is powered off, then power off again, hold {{B|HOME}}, and then press {{B|POWER}} - if the notification LED [[3DS:boot9strap#LED_Status_Codes|lit up a color]] or the [[3DS:fastboot3DS|fastboot3DS]] menu appears, then you have working CFW but something is interfering with Luma. Join the Nintendo Homebrew Discord for more advanced help
==CFW troubleshooting==
<tabber>
|-|Yes, I have CFW=
The troubleshooting below should always be started at the first section. The troubleshooting will direct you to the next sections if necessary.
===Section I - Prep Work===
===Section I - Prep Work===
Line 105:
Line 110:
#Follow the instructions on [[3DS:Hardware test|the hardware test page]]
#Follow the instructions on [[3DS:Hardware test|the hardware test page]]
#*If the number of errors from this is zero, continue to the next section
#*If the number of errors from this is zero, continue to the next section
===Section X - Manual CTRTransfer===
===Section X - Manual CTRTransfer===
Line 115:
Line 119:
By this point, you have exhausted all conventional fixes. If your console has not booted to the HOME Menu by now, go to the Nintendo Homebrew Discord and mention that you've tried this page already.
By this point, you have exhausted all conventional fixes. If your console has not booted to the HOME Menu by now, go to the Nintendo Homebrew Discord and mention that you've tried this page already.
==Stock troubleshooting==
|-|No, my console is stock=
Begin with testing if Safe Mode is accessible.
===Section I - Safe Mode===
===Section I - Safe Mode===
Line 131:
Line 137:
#*If the shutdown menu opens (a grey screen with text), you're experiencing <code>f000000b</code> corruption and must install boot9strap with a [[3DS:ntrboot|ntrboot]] compatible flashcart in order to fix the issue
#*If the shutdown menu opens (a grey screen with text), you're experiencing <code>f000000b</code> corruption and must install boot9strap with a [[3DS:ntrboot|ntrboot]] compatible flashcart in order to fix the issue
#*If the screen stays black and the console only powers off if you hold the button for 15 seconds, this may be potentially fixable with [[3DS:ntrboot|ntrboot]] if it is not a hardware issue
#*If the screen stays black and the console only powers off if you hold the button for 15 seconds, this may be potentially fixable with [[3DS:ntrboot|ntrboot]] if it is not a hardware issue
When a 3DS boots to a black screen instead of the HOME Menu, it is usually a bad sign. This page lists common troubleshooting steps to fix this issue.
First and foremost, you need to check if the console has a custom firmware installed.
CFW Check
Checking if the console has CFW will help as it allows access to GodMode9, a helpful tool for troubleshooting and fixing issues.
Power on your console while holding the SELECT button
If your console boots to the Luma3DS configuration menu, press START to save, then continue to the CFW troubleshooting section below
If your console doesn't boot to the Luma3DS configuration menu, do the same without the SD card inserted
If your console does boot to the Luma3DS configuration menu, your SD card wasn't inserted correctly, re-insert it and try again
If your console turns off right away, you have CFW and can continue to the CFW troubleshooting section below
If your console doesn't boot to the Luma3DS configuration menu but black-screens, your console is likely bricked without CFW, and you should continue to the stock troubleshooting section at the bottom of this page
To make sure of this, hold SELECT+START+X+POWER for seven seconds while the console is powered off, then power off again, hold HOME, and then press POWER - if the notification LED lit up a color or the fastboot3DS menu appears, then you have working CFW but something is interfering with Luma. Join the Nintendo Homebrew Discord for more advanced help
The troubleshooting below should always be started at the first section. The troubleshooting will direct you to the next sections if necessary.
Wait ten seconds, then press L+↓+SELECT at the same time
If the Rosalina menu opens, you're likely experiencing 3DS:RTCBug - return by pressing B, wait 15 minutes, remove any inserted cartridge, and the HOME Menu should load on its own. If this doesn't work, continue to the next section
If Rosalina doesn't open, continue to the next section
Section III - Luma3DS configuration reset
Insert the SD card into your computer
Navigate to the folder sd:/luma
Delete config.ini
Reinsert the SD card into your console
Power on your console
If your console doesn't boot to the Luma3DS config, follow SD Clean, then return to section 2
Do not enable anything, just press START to save the default configuration
If your console boots to the HOME Menu, you should look for and delete faulty patches in /luma/sysmodules and /luma/titles on the SD card before turning Enable game patching or Loading external FIRMs and modules back on
If your console doesn't boot to the HOME Menu, continue to the next section
If your console boots to an error, check the Luma exceptions page for how to fix your error, or ask for help in the Nintendo Homebrew Discord if your error isn't listed there
Section IV - SD HOME Menu extdata
Power on your console without the SD card inserted
If it boots to the Luma3DS configuration screen, press START to save
If it doesn't boot to the HOME menu, continue to the next section
If it boots to the HOME Menu, do the following steps:
Insert your SD card into your computer
Navigate to Nintendo 3DS -> ID0 -> ID1 -> extdata -> 00000000
ID0 and ID1 are 32-character long folders
If you have multiple ID0/ID1 folders, do the following for all of them
Delete the corresponding folder for your region:
USA: 0000008f
EUR: 00000098
JPN: 00000082
KOR: 000000A9
Reinsert your SD card into your console
Power on your console
If it still doesn't boot to the HOME Menu, but does without the SD card, you're experiencing a very weird issue and should ask in the Nintendo Homebrew discord for more advanced help
Section V - Safe Mode
Power on your console while holding L+R+↑+A
If your console boots to the Safe Mode menu, perform the update and see if it boots to the HOME Menu
If it doesn't boot to Safe Mode, or doesn't boot to the HOME Menu after a Safe Mode update, continue to the next section
If the console doesn't boot to the HOME Menu after all applicable fixes have been tried, continue to the next section
Section VII - New 3DS camera brick
If you are currently troubleshooting an old model console, ignore this and skip to the next section.
If you are unsure whether your console is new or old, look at its shoulder buttons. A new model has four (ZL+L+R+ZR), and an old model has two (L+R).
Insert your SD card into your computer
Navigate to the /luma/ folder
Look for errdisp.txt
If this file already exists, rename it to _errdisp.txt
If this file doesn't exist, skip to the next section
Reinsert your SD card into the console
Power on the console
Wait 30 seconds without pressing any buttons
Power off the console
Navigate to the /luma/ folder
Look for errdisp.txt
If this file exists, open it in a text editor, and check if the process name is qtm
If the process name is qtm, you need to disconnect your inner camera or replace it
If the process name is something else, your console has a very unusual issue and you should ask in the Nintendo Homebrew Discord for more advanced help
If this file doesn't exist, continue to the next section
When asked whether to restore optional data, press B to deny it
By this point, you have exhausted all conventional fixes. If your console has not booted to the HOME Menu by now, go to the Nintendo Homebrew Discord and mention that you've tried this page already.
Begin with testing if Safe Mode is accessible.
Section I - Safe Mode
Power on your console while holding L+R+↑+A
If your console boots to the Safe Mode menu and is an Old 3DS/XL/2DS model, try Safecerthax, if not, proceed to the next bullet point
If your console boots to the Safe Mode menu and the first bullet point didn't apply to you, perform the update and see if it boots to the HOME Menu
If it doesn't boot to Safe Mode, or doesn't boot to the HOME Menu after a Safe Mode update, continue to the next section
Section II - Shutdown menu
Power on the console
Wait 30 seconds without touching any buttons
Press the POWER button
If the shutdown menu opens (a grey screen with text), you're experiencing f000000b corruption and must install boot9strap with a ntrboot compatible flashcart in order to fix the issue
If the screen stays black and the console only powers off if you hold the button for 15 seconds, this may be potentially fixable with ntrboot if it is not a hardware issue