Troubleshooting (Finalizing Setup)
This page offers troubleshooting advice for commonly encountered issues with the "Finalizing Setup" page. 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 Finalizing Setup
Unable to update console
The steps below can be attempted in any order, but are listed from easiest to hardest to perform.
- If you are using Pretendo, switch back to Nintendo with Nimbus and try again
- Set your DNS settings to "Auto"
- Move closer to your WiFi router
- 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
- Delete your WiFi connection, then reconnect to your WiFi again
- Reboot your WiFi router
- Connect to a different WiFi connection, like a mobile hotspot
- Nintendo servers may be down; Try again later
- If you still get an error, follow CTRTransfer, then try again
- For further support (in English), join Nintendo Homebrew on Discord
Error #22: finalize.romfs is invalid
The file finalize.romfs
is corrupt or unreadable. Re-download it and copy it to the root of the SD card, replacing any existing copy, then try again.
Information #23: finalize.romfs in wrong location
The file finalize.romfs
was placed in the wrong location instead of root of SD. The script will attempt to resolve this, but requires your permission to do so. Press (A) on the next few prompts to continue.
Error #24: SD is write-protected
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.
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.
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:
- Power off your console
- Insert your SD card into your computer
- Copy the
Nintendo 3DS
folder from the root of your SD card to your computer - Delete the Nintendo 3DS folder from the SD card
- Reinsert your SD card into your console
- Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
- Press the (Home) button
- Select "Scripts..."
- Select "finalize"
- Press (A) to create a NAND backup
- This may take around fifteen minutes
- Press (A) again
- The console should automatically power off
- Insert your SD card into your computer
- Copy the files in
/gm9/backups/
on your SD to a safe location on your computer - Delete the
<date>_<serialnumber>_sysnand_##.bin
and<date>_<serialnumber>_sysnand_##.bin.sha
files from the SD card - Copy the
Nintendo 3DS
folder from your computer to the root of your SD card - Delete the
Nintendo 3DS
folder from your computer
Now that you have your NAND backup in a safe place:
- Reinsert your SD card into your console
- Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
- Press the (Home) button
- Select "Scripts..."
- Select "finalize"
- 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:
- Power off your console
- Insert your SD card into your computer
- Copy the
Nintendo 3DS
folder from the root of your SD card to your computer - Delete the Nintendo 3DS folder from the SD card
- Reinsert your SD card into your console
- Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
- Perform a NAND Backup
- Copy the files in
gm9/out
on your SD to a safe location on your computer - Delete the
<date>_<serialnumber>_sysnand_##.bin
and<date>_<serialnumber>_sysnand_##.bin.sha
files from the SD card, keeping essential.exefs in/gm9/out/
- Copy the
Nintendo 3DS
folder from your computer to the root of your SD card - 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 #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:
- Press (B) to cancel making another NAND backup
- Hold (R) and press (Start) at the same time to power off your console
- Copy the contents of
/gm9/backups/
to a safe location on your computer - Delete
/gm9/backups/
from your SD card - 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
- Press and hold (Start), and while holding (Start), power on your console. This will launch GodMode9
- Press (Home) to bring up the action menu
- Select "Scripts..."
- Select "finalize"
- Follow the prompts in the script, answering any questions that you are asked
Error #18a/18b: MSET9 detected
You didn't remove MSET9 on the previous page. The script will attempt to remove MSET9 for you; follow the instructions given by the script.
Something else
Join Nintendo Homebrew on Discord for assistance, and describe the issue that you see.
TIP
Go back to Finalizing Setup
TIP
Go back to Troubleshooting