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

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

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.

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 and power on your console
  3. Wait for the console to generate the SD card data
    • Your applications will have disappeared. This is normal and will be resolved shortly
  4. Power off your console and reinsert your SD card into your computer
  5. Ve a la carpeta Nintendo 3DS en tu tarjeta SD
  6. Copy the 32 character long name of the folder you see
  7. Delete the Nintendo 3DS folder
  8. Rename the BACKUP_Nintendo 3DS folder to Nintendo 3DS
Bruteforce Movable skips to step 4

El sitio web ya ha minado tu movable.sed usando tu código de amigo y el ID0. Puedes utilizar el movable.sed que te proporciona.

Important! You have been locked out of the automated part1 dumper system...

Tu código de amigo fue bloqueado del bot de código de amigo porque tu consola no pudo agregar al bot como amigo. Asegúrate de que tu consola esté correctamente conectada a Internet, luego únete al Discord de Nintendo Homebrew y pide que se te desbloquee.

We were unable to successfully complete your bruteforce request. :`(

El sitio web ha determinado que tu movable.sed no puede ser minado. Asegúrate de haber escrito correctamente el ID0 en el sitio web. 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 Homebrew Launcher (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 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. Asegúrate de que Nintendo DSiWare está correctamente escrito y espaciado. Las mayúsculas/minúsculas no importan.

DSiWare Management shows a question mark

Puede haber un problema con el archivo F00D43D5.bin (puede estar corrupto o preparado para otra consola 3DS). Re-create your F00D43D5.bin file with the Bannerbomb3 Injector, ensuring that you use the movable.sed file for your console.

Instalar boot9strap (USM)

Safe Mode system update succeeds instead of giving error 003-1099

unSAFE_MODE is not installed. Follow the instructions to install it.

Red screen after selecting "Detailed Setup"

The file usm.bin is missing or misplaced. Download the latest release of unSAFE_MODE and place usm.bin on the root of your SD card. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

There is also a possibility that the console isn’t reading your SD card. Make sure it is inserted and formatted correctly.

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.

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.

Instalar boot9strap (Fredtool)

Error on Fredtool Injector page

Asegúrate de que tu archivo movable.sed y la copia de seguridad de DSiWare provienen de la misma consola. El error aparece cuando los archivos no coinciden.

Unable to select "Haxxxxxxxxx!" because the BB3 multihax menu appears

You forgot to delete F00D43D5.bin from the SD card. Navigate to Nintendo 3DS -> <ID0> -> <ID1> -> Nintendo DSiWare on your SD card and delete the F00D43D5.bin file.

"Haxxxxxxxxx!" does not appear

Hay un problema con el archivo 42383821.bin (es incorrecto, no está presente, está mal colocado o está corrupto). 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.

DS Connection Settings launches normally

Haxxxxxxxxx! no fue copiado de la tarjeta SD a la memoria de la consola.

Black screen when launching DS Connection Settings

El menú de Conexiones de Nintendo DS no funciona, y necesitarás acceso al Homebrew Launcher para solucionar este problema. Únete al Discord de Nintendo Homebrew para obtener ayuda.

SD card is grayed out in Flipnote

Flipnote puede tomar mucho tiempo en construir un índice de la tarjeta SD si esta es muy grande. Espera unos minutos.

Lenny face does not appear in SD card section

No copiaste la carpeta private del archivo .zip de Frogminer_save a la raíz de la tarjeta SD.

Flipnote freezes

Es posible que hayas tocado la pantalla táctil dentro del Flipnote modificado. Vuelve a entrar al menú de Conexiones de Nintendo DS e intenta de nuevo, asegurándote de no tocar la pantalla táctil por accidente.

Green screen after pasting

Falta el archivo boot.nds o está fuera de lugar. Descarga la última versión de b9stool y coloca el archivo boot.nds en la raíz de la tarjeta SD, sobreescribiendo el existente.

White screen after pasting

Hay un problema con el archivo boot.nds. Vuelve a descargar la última versión de b9stool y coloca el archivo boot.nds en la raíz de la tarjeta SD, sobreescribiendo el existente.

Unable to open Luma3DS configuration menu after running B9STool

Join Nintendo Homebrew on Discord and explain what has happened.

Homebrew Launcher (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 otherapps.zip, place the .bin file relevant to your console to the root of your SD card, and rename it to otherapp.bin. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

"An exception occurred" or Errdisp when opening Picross

Your console already has 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)

There is an issue with your otherapp.bin file. Download otherapps.zip, place the .bin file relevant to your console to the root of your SD card, and rename it to otherapp.bin. No añadas manualmente la extensión .bin al archivo si ves que no la tiene.

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.

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, you should update your console to the latest version and follow Seedminer.

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.

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

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 Initialize Savedata (it also may be called 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
"To use the Internet Browser, please update your system using the System Update option in the System Settings."

First, make sure you entered the correct proxy for the connection you’re using. If not, go back to Section II. If the proxy is correct, then your console has been cart-updated, which means an alternate exploit will need to be used.

Method 1
If the two numbers before the region in the system version string is equal to or less than 36 (e.g. Ver. 11.14.0-36U), you can follow Soundhax. When prompted to select a firmware to generate the sound file, use:

  • 1.x - 2.1 if the number is between 0 and 2
  • 2.1 - 2.2 if the number is between 3 and 4
  • 3.x - 4.x if the number is between 5 and 10
  • 5.x - 11.3 if the number is between 11 and 36

Method 2 (Old 3DS only)
If you have an Old 3DS / Old 3DS XL / 2DS, you can try a Safe Mode update, which will trigger an alternate exploit:

  1. Ensure that the proxy that you used for SSLoth is still actively applied to your internet connection
  2. With your console powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your console
    • Keep holding the buttons until the console boots into Safe Mode (a “system update” menu)
  3. Press “OK” to accept the update
  4. If everything worked correctly, the update will fail and the 3DS will boot into SafeB9SInstaller. If it did, then continue from Section IV.

If these methods didn’t work (or do not apply to you), update your console to the latest version and follow Seedminer.

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.

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.

If you have a Taiwanese unit (with a T in the version string, ie. 11.3.0-##T), you will not be able to follow these instructions, and you will need to update your console and follow Seedminer instead.

If you have a Mainland Chinese unit (with a C in the version string, ie. 11.3.0-##C), join Nintendo Homebrew on Discord for assistance.

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

Homebrew Launcher (super-skaterhax)

"An error has occured. 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 and you have a system version ending in E, and the language set to English, change the language to any other language temporarily. You can revert this change when you reach Finalizing Setup.

An exception occured or ErrDisp when pressing GO! GO!

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

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
Unable to enter Rosalina menu due to broken Left Shoulder / Down D-Pad / Select button(s)

Download this alternate config.ini and place it in /luma/. This will change the Rosalina key combination to (X) + (Y).

"An exception occurred" or infinite "Nintendo 3DS" screen after trying to launch Homebrew Launcher from Download Play

Hay un problema con el archivo boot.3dsx (falta, está mal colocado o está corrupto). Download the latest release of the Homebrew Launcher and place boot.3dsx on the root of your SD card, replacing any existing file.

"Scripts directory not found" in GodMode9

No copiaste la carpeta gm9 del archivo .zip de GodMode9 a la raíz de la tarjeta SD. Descarga la última versión de GodMode9 y coloca la carpeta gm9 en la raíz de la tarjeta SD, combinándola con la ya existente.

"Backup failed" 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. Remove the SD card and insert it 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. Power off your console, hold START and power on still holding START to boot on 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.

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 PC, 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 PC 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. Realiza una Actualización de sistema dirigiéndote a la Configuración de la consola, después a “Otras opciones”, luego ve al último menú de la derecha y pulsa en “Actualización”
    • 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.

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
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:
    • Console 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