Resolución de Problemas

Para soporte en inglés, pide ayuda en el Discord de Nintendo Homebrew.
Si te gustó esta guía, aceptamos Donaciones.

Esta página ofrece consejos de solución de problemas para problemas comunes que puedan surgir. Si no logras resolver tu problema con esta página, por favor únete al Discord de Nintendo Homebrew (en inglés) y describe tu problema, incluyendo lo que ya has intentado hacer previamente.

Table of Contents

Used on multiple pages:

Guide pages:

Issues after installation:

Problemas con SafeB9SInstaller

Before opening SafeB9SInstaller

Failed to open SafeB9SInstaller.bin

Falta el archivo SafeB9SInstaller.bin o está fuera de lugar. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

SigHaxed FIRM was not installed! Revisa la pantalla inferior para más información.

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

Los archivos boot9strap.firm y boot9strap.firm.sha no están en la carpeta boot9strap, o la carpeta boot9strap tiene un nombre equivocado. Download the latest release of boot9strap, and place boot9strap.firm and boot9strap.firm.sha in the boot9strap folder.

SigHaxed FIRM - invalid FIRM

Hay un problema con los archivos boot9strap.firm y boot9strap.firm.sha. 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

Únete al Discord de Nintendo Homebrew (en inglés) para obtener ayuda, y describe el mensaje que veas.

Instalar 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. Deberías ir a Comprobación de CFW antes de continuar.

"An error has occurred, forcing the software to close..." (white message box)

Hay un problema con el archivo otherapp.bin (falta, está mal colocado o está corrupto). Descarga la última versión de universal-otherapp y coloca el archivo en la raíz de tu tarjeta SD.

"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. Únete al Discord de Nintendo Homebrew para obtener ayuda.

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 (MSET9)

Python 3 is not installed

Python is not installed on the computer you are using. Download it from the Python website, double-click the installer, and follow the prompts to install Python. Once Python is installed, try again.

Error 01: Couldn't find Nintendo 3DS folder

You are not running MSET9 from the root of the SD card, or the SD card is missing the Nintendo 3DS folder.

Remember, your SD card should look like this:

MSET9 root layout

If your SD card layout is correct, then your SD card most likely isn’t being read by your console. Re-format it (Windows, Linux, macOS), then start again from the beginning of Section I.

Error 02: Your SD is write protected

Write-protection is enabled on this SD card. 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.

Error 03: Don't change console version

You inputted a different number between different runs of MSET9 (for example, you initially selected option 1 for “Old 3DS, 11.8 - 11.17” and then later selected option 2 for “New 3DS, 11.8 - 11.17”).

If this happened when trying to uninstall MSET9, the script has automatically removed MSET9 for you and you can continue to the next page. Otherwise, start again from the beginning of Section I.

Error 04: No HOME Menu Extdata.

Your SD card is not formatted properly.

Copy everything off the SD Card to your PC, re-format it (Windows, Linux, macOS), copy everything back, then start again from the beginning of Section I.

Error 05: No Mii Maker Data!

Mii Maker data was not found on the SD card. Start again from the beginning of Section I.

Error 06: You need at least 16MB free

Your SD card does not have enough space to trigger MSET9. Free up some space and try again.

At the end of this guide, you will need at least 1.3GB to make a NAND backup, so it’s best to free up at least that much.

Error 07: You don't have 1 ID0, you have (#)!

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. Inserta tu tarjeta SD en tu computadora
  7. Ve a la carpeta Nintendo 3DS en tu tarjeta SD
  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.

Error 08: One or more files are missing or malformed!

One or more files that MSET9 needs to run is missing or corrupted. Re-download the MSET9 Release .zip and extract it to the root of your SD card, replacing all existing files, then try again.

Error 10: Database(s) malformed or missing!

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

  1. If you haven’t already, press Enter to close the MSET9 script
  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
Error 12: You don't have 1 ID1, you have (#)!

This occurs when you use multiple SD cards with the same 3DS and then merge the SD card contents together. Both are “valid”, but the 3DS can only read one at a time.

You will need to determine which one contains your data. First of all, back up all of the folders, in case something goes wrong:

Backup ID1

Now, delete all but one of the folders from your SD card. Generally, you will want to delete the smallest one(s), as the one with all your data will probably have more space occupied. You can compare which folder is occupying more space by right-clicking it and clicking “Properties”:

Properties prompt

Which to delete

Your SD card should now look something like this:

Just enough ID1s

Now, put your SD card into your 3DS and turn it on. If your data is still there, you deleted the right folder and have now determined your correct ID1. If everything has disappeared, go back into the backup folder that you made earlier and try the other folder.

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 MSET9 .zip, replacing any existing files.

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

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
    • 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 “Successfully removed MSET9!”, reinsert 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. Run the MSET9 script
    • Windows: Double-click mset9.bat
    • 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 to remove MSET9
  5. If possible, use a new SD card; otherwise, backup and reformat your existing SD card as FAT32 (Windows, Linux, macOS)
  6. Insert the formatted, blank SD card into your console
  7. Return to Section I Step 1

After finishing the MSET9 page, you should switch back to your old SD card before continuing to Finalizing Setup.

An exception occured after triggering MSET9

This likely indicates that you already have custom firmware. Deberías ir a Comprobación de CFW antes de continuar.

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. Deberías ir a Comprobación de CFW antes de continuar.

Installing boot9strap (SSLoth-Browser)

Red/purple/pink and white screen after running Browserhax

This likely indicates that you already have custom firmware. Deberías ir a Comprobación de CFW antes de continuar.

"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. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

"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. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

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. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

"PrepareArm9ForTwl returned error c8804631!"

Únete al Discord de Nintendo Homebrew para obtener ayuda.

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.

Finalizar instalación

Unable to update console

Los pasos siguientes se pueden intentar en cualquier orden, pero están ordenados por orden de dificultad.

  1. Establece la configuración de DNS a “Automático”
  2. Colócate más cerca de tu router de Wi-Fi
  3. Actualiza desde el modo seguro: Apaga la consola, mantén presionados los botones (L), (R), (D-pad Arriba) y (A) mientras la enciendes, y sigue las indicaciones en pantalla
  4. Borra tu configuración de conexión Wi-Fi, y luego vuelve a reconectar
  5. Renicia tu router de Wi-Fi
  6. Conéctate a una conexión Wi-Fi distinta, como desde una red de datos móviles
  7. Puede que los servidores de Nintendo estén caídos. Intenta más tarde
  8. Si aún te sigue dando error, sigue la sección de CTRTransfer y luego intenta actualizar nuevamente
  9. Para más soporte (en inglés), entra al Discord de Nintendo Homebrew
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:

  1. Power off your console
  2. Inserta tu tarjeta SD en tu computadora
  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. Esto abrirá GodMode9
  7. Press the (Home) button
  8. Selecciona “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. Inserta tu tarjeta SD en tu computadora
  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. Esto abrirá GodMode9
  3. Press the (Home) button
  4. Selecciona “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. Inserta tu tarjeta SD en tu computadora
  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. Esto abrirá 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 #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. Esto abrirá GodMode9
  7. Presiona el botón (Home) para abrir el menú de acción
  8. Selecciona “Scripts…”
  9. Select “finalize”
  10. Follow the prompts in the script, answering any questions that you are asked
Error #18: MSET9 detected

You didn’t remove MSET9 when prompted to. Follow Section IV - Removing MSET9 from the Windows/macOS/Linux guide or the Android/ChromeOS guide, then re-run the script.

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). Si tu consola tiene una configuración antigua (por ejemplo, algo basado en arm9loaderhax o menuhax), deberías actualizar dicha configuración antes de seguir estas instrucciones.

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

Los pasos siguientes se pueden intentar en cualquier orden, pero están ordenados por cantidad de tiempo que toma realizar.

  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. Cambia el nombre de la carpeta Nintendo 3DS de tu tarjeta SD a Nintendo 3DS_BACKUP, luego intenta encenderla. If your console successfully boots, there is some issue within your Nintendo 3DS folder. Try clearing HOME Menu extdata:
    • Ve a /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/
    • Delete the corresponding folder for your 3DS region:
      • Región EUR: 00000098
      • Región JPN: 00000082
      • Región USA: 0000008f
      • Región CHN: 000000A1
      • Región KOR: 000000A9
      • Región TWN: 000000B1
  4. Intenta iniciar en modo de recuperación y actualizar tu consola:
    • Power off your console
    • Mantén presionado (L) + (R) + (D-Pad Arriba) + (A)
    • Power on your console
    • If you were successful, the console will boot to an “update your system” screen
  5. Sigue la guía de CTRTransfer
  6. Para más ayuda, puedes pedir ayuda (en inglés) en el Discord de Nintendo Homebrew

Error message on boot

"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"

Tu versión de Luma3DS está desactualizada. Descarga la última versión de Luma3DS y coloca boot.firm en la raíz de tu tarjeta SD, reemplazando cualquier archivo existente. Asegúrate de extraer el archivo ZIP con cualquier herramienta que no sea WinRAR, ya que se sabe que causa problemas con los archivos relacionados con 3DS.

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

Tienes activada la opción “Disable ARM11 exception handlers”, o directamente no tienes custom firmware instalado. Intenta activar las excepciones de ARM11: + Power off your console + Mantén presionado (Select) + Power on your console, while still holding (Select) + Si la opción “Disable ARM11 exception handlers” está marcada, desmárcala

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. En este caso, entra al Discord de Nintendo Homebrew para obtener ayuda (en inglés). + También es posible que alguien haya configurado una pantalla de inicio que luce tal y como un brickeo. Try leaving your console powered on, waiting on the blue screen, for five minutes.

Some other error

Por favor saca una foto del error y entra al Discord de Nintendo Homebrew y pide ayuda (en inglés).

Software issues on consoles with custom firmware

DSi / DS functionality is broken or has been replaced with Flipnote Studio
  1. Descarga la última versión de TWLFix-CFW (el archivo .3dsx)
  2. Power off your console
  3. Crea una carpeta llamada 3ds en la raíz de tu tarjeta SD, si aún no existe
  4. Copia TWLFix-CFW.3dsx a la carpeta /3ds/ en tu tarjeta SD
  5. Reinsert your SD card into your console
  6. Abre el Homebrew Launcher
  7. Inicia TWLFix-CFW desde la lista de homebrew
  8. Presiona (A) para desinstalar los títulos TWL dañados
  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”
    • La actualización verá que los títulos TWL esenciales han sido desinstalados, y los volverá a descargar e instalar
  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

Esto puede ocurrir después de un CTRTransfer o al cambiar de región en 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. Inserta tu tarjeta SD en tu computadora
  3. Navigate to the /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ folder on your SD card
  4. Delete the corresponding folder for your 3DS region:
    • Región EUR: 00000098
    • Región JPN: 00000082
    • Región USA: 0000008f
    • Región CHN: 000000A1
    • Región KOR: 000000A9
    • Región TWN: 000000B1
  5. Reinsert your SD card into your console
Clear HOME Menu theme data
  1. Power off your console
  2. Inserta tu tarjeta SD en tu computadora
  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. Ejecuta la aplicación Modo Descarga ()
  2. Espera hasta ver las opciones que dicen Nintendo 3DS y Nintendo DS
  3. Presiona (Left Shoulder) + (Abajo) + (Select) a la vez para abrir el menú de Rosalina
  4. Selecciona “Miscellaneous options”
  5. Selecciona “Switch the hb. title to the current app.”
  6. Presiona (B) para continuar
  7. Presiona (B) para regresar al menú principal de Rosalina
  8. Presiona (B) para salir del menú de Rosalina
  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