Problèmes et Dépannage

Pour un support en Anglais, demander de l'aide sur le Discord Nintendo Homebrew.
Si vous appréciez ce guide, nous acceptons les Dons.

This page offers troubleshooting advice for commonly encountered issues. 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.

Table of Contents

Used on multiple pages:

Guide pages:

Issues after installation:

Issues with SafeB9SInstaller

SigHaxed FIRM was not installed! Check lower screen for more info.

SigHaxed FIRM - File not found

You are missing boot9strap.firm and boot9strap.firm.sha from the boot9strap folder, or the boot9strap folder is misnamed. Download the latest release of boot9strap, and place boot9strap.firm and boot9strap.firm.sha in the boot9strap folder.

SigHaxed FIRM - invalid FIRM

There is an issue with your boot9strap.firm and boot9strap.firm.sha files. 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

Join Nintendo Homebrew on Discord for assistance, and describe the message that you see.

Seedminer

Multiple long folder names in Nintendo 3DS folder

This occurs when you use your SD card in multiple 3DS devices and is intended to prevent inadvertently merging data that would not be valid on other devices. 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 device and power on your device
  3. Wait for the device to generate the SD card data
    • Your applications will have disappeared. This is normal and will be resolved shortly
  4. Power off your device and reinsert your SD card into your computer
  5. Naviguez vers le dossier Nintendo 3DS de votre carte 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

The website has already mined your movable.sed using your friend code and ID0 combination. You can use the movable.sed that it provides you.

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

Your friend code was blocked from using the friend code bot because your 3DS did not successfully friend the bot. Ensure your 3DS is properly connected to the Internet, then join Nintendo Homebrew on Discord and ask to be unlocked.

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

The website has determined that your movable.sed cannot be brute-forced. Ensure that you gave the correct ID0 to the website. 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 device in a way that makes this method impossible to perform. Si c’est le cas, rejoignez Nintendo Homebrew sur Discord et demandez de l’aide, en anglais.

DSiWare Management menu displays "No accessible software data."

F00D43D5.bin is missing from Nintendo 3DS -> <ID0> -> <ID1> -> Nintendo DSiWare. Make sure that Nintendo DSiWare is correctly spelled and spaced. Uppercase/lowercase does not matter.

DSiWare Management shows a question mark

There may be an issue with your F00D43D5.bin file (it may be corrupted or intended for the wrong 3DS). Re-create your F00D43D5.bin file with the Bannerbomb3 Injector, ensuring that you use the movable.sed file for your console.

Installing 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. Do not add the .bin extension if you do not already see it.

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

The file SafeB9SInstaller.bin is missing or misplaced. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

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

Error on Fredtool Injector page

Ensure that your movable.sed and DSiWare backup come from the same console. A mismatch will result in an error.

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

There is an issue with your 42383821.bin file (it is incorrect, missing, misplaced, or corrupted). 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! was not copied from your SD card to your system memory.

Black screen when launching DS Connection Settings

Your DS Connection Settings application is broken, and you will need Homebrew Launcher access to fix this issue. Join Nintendo Homebrew on Discord for assistance.

SD card is grayed out in Flipnote

Flipnote may take a long time to index your card if you have a large SD card. Let it sit for a few minutes.

Lenny face does not appear in SD card section

You did not copy the private folder from the Frogminer_save .zip to the root of your SD card.

Flipnote freezes

You may have accidentally touched the touch screen while in the modified Flipnote. Re-enter DS Connection Settings and try again, ensuring that you don’t accidentally use the touchscreen.

Green screen after pasting

The file boot.nds is missing or misplaced. Download the latest release of b9stool and place boot.nds on the root of your SD card, replacing the existing one.

White screen after pasting

There is an issue with your boot.nds file. Re-download the latest release of b9stool and place boot.nds on the root of your SD card, replacing the existing one.

Unable to open Luma3DS configuration menu after running B9STool

Join Nintendo Homebrew on Discord and explain what has happened.

Installing boot9strap (Soundhax)

Red/purple/pink and white screen after running Soundhax

If your device 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 device is not on those firmwares, it likely indicates that you already have custom firmware. You should check for CFW.

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

There is an issue with your otherapp.bin file (it is missing, misplaced, or corrupted). Download the latest release of universal-otherapp and place it on the root of your SD card.

"Could not play"

You have the wrong Soundhax file for your device and region, or your device is incompatible with Soundhax. In the latter case, you should update your device to the latest version and follow Seedminer.

Failed to open SafeB9SInstaller.bin

The file SafeB9SInstaller.bin is missing or misplaced. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

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. You should check for CFW.

"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. Do not add the .bin extension if you do not already see it.

"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. Do not add the .bin extension if you do not already see it.

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 the System Settings application
  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 device 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 device powered off, hold the following buttons: (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A), and while holding these buttons together, power on your device
    • Maintenez les boutons enfoncés jusqu’à ce que la console démarre en mode sans échec (menu “Mise à jour”)
  3. Appuyez sur “OK” pour accepter la mise à jour
  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 device to the latest version and follow Seedminer.

Failed to open SafeB9SInstaller.bin

The file SafeB9SInstaller.bin is missing or misplaced. Download the latest release of SafeB9SInstaller, extract it, and place SafeB9SInstaller.bin on the root of your SD card. Do not add the .bin extension if you do not already see it.

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. Do not add the .bin extension if you do not already see it.

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

Join Nintendo Homebrew on Discord for assistance.

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. You should check for CFW.

Finalizing Setup

Unable to update device

The steps below can be attempted in any order, but are listed from easiest to hardest to perform.

  1. Réglez le paramètre “Obtention automatique d’un DNS” sur “Oui”
  2. Rapprochez-vous de votre point d’accès Wi-Fi
  3. Effectuez une mise à jour depuis le mode sans échec (Safe Mode) en éteignant la console puis en maintenant les boutons (L) + (R) + (Haut sur la croix directionnelle) + (A) pendant le démarrage de la console et suivez les instructions à l’écran
  4. Supprimez votre connexion Wi-Fi, puis connectez-vous à nouveau à votre point d’accès Wi-Fi
  5. Redémarrez votre point d’accès Wi-Fi
  6. Connectez-vous à un point d’accès Wi-Fi différent, comme un point d’accès mobile
  7. Les serveurs de Nintendo sont peut-être en panne ; Réessayez plus tard
  8. Si vous recevez toujours un message d’erreur, suivez CTRTransfer, puis réessayez
  9. For further support (in English), join Nintendo Homebrew on Discord
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

There is an issue with your boot.3dsx file (it is missing, misplaced, or corrupted). 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

You did not copy the gm9 folder from the GodMode9 .zip to the root of your SD card. Download the latest release of GodMode9 and place the gm9 folder on the root of your SD card, merging it with the existing one.

"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 devices with custom firmware

The steps detailed here generally assume that your device 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 device 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 device.

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 device (such as a disconnected backlight cable). You may be able to get your device to boot by holding it at certain angles.

My device gets stuck on a black screen with blue power light staying on

The steps below can be attempted in any order, but are listed from least to most time-consuming.

  1. Power off your device, remove the SD card, re-insert it, then power on your device.
  2. Power off your device, eject the game cartridge if inserted, power on your device, then wait up to ten minutes. If your device boots within ten minutes, the issue has been fixed and is unlikely to reoccur
  3. Rename the Nintendo 3DS folder on your SD card to Nintendo 3DS_BACKUP, then attempt to boot. If your device successfully boots, there is some issue within your Nintendo 3DS folder. Try clearing HOME Menu extdata:
    • Navigate to /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ + Delete the corresponding folder for your 3DS region:
      • Région EUR : 00000098
      • Région JPN : 00000082
      • Région USA : 0000008f
      • Région CHN : 000000A1
      • Région KOR : 000000A9
      • Région TWN : 000000B1
  4. Try booting into recovery mode and updating your system:
    • Éteignez votre console
    • Hold (Left Shoulder) + (Right Shoulder) + (D-Pad Up) + (A)
    • Power on your device
    • If you were successful, the device will boot to an “update your system” screen
  5. Follow the CTRTransfer guide
  6. For further support, ask for help at Nintendo Homebrew on Discord

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 Luma3DS and place boot.firm 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:

  • Éteignez votre console
  • Hold (Select)
  • Power on your device, while still holding (Select)
  • 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 device 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 device, remove the SD card, re-insert it, then power on your device
  2. Power off your device, 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 device, 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 device is likely hard-bricked. You will need to buy an ntrboot flashcart to reinstall boot9strap in order to attempt to fix your device. 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 device 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 devices with custom firmware

DSi / DS functionality is broken or has been replaced with Flipnote Studio
  1. Download the latest release of TWLFix-CFW (the .3dsx file)
  2. Éteignez votre 3DS
  3. Créez un dossier nommé 3ds à la racine de votre carte SD si celui ci n’existe pas
  4. Copiez TWLFix-CFW.3dsx dans le dossier /3ds/ de votre carte SD
  5. Retirez la carte SD de votre ordinateur et réinsérez-là dans votre 3DS
  6. Ouvrez le Homebrew Launcher
  7. Lancez TWLFix-CFW que vous trouverez dans la liste des homebrews
  8. Appuyez sur (A) pour désinstaller les titres TWL corrompus
  9. Appuyez sur (Start) pour redémarrer la console
  10. Effectuez une Mise à jour du Système en vous rendant dans les Paramètres de la console, puis “Autres paramètres”, puis tout à droite sur l’option “Mise à jour du Système”
    • Le processus de mise à jour verra que les titres TWL essentiels ont été désinstallés, et va les re-télécharger et les réinstaller
  11. Une fois la mise à jour terminée, appuyez sur “OK” pour redémarrer la console
GBA Virtual Console and/or Safe Mode functionality is broken

Your device is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow A9LH to B9S to update your device 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 device 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. Éteignez votre 3DS
  2. Insérez votre carte SD dans votre ordinateur
  3. Navigate to the /Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ folder on your SD card
  4. Delete the corresponding folder for your 3DS region:
    • Région EUR : 00000098
    • Région JPN : 00000082
    • Région USA : 0000008f
    • Région CHN : 000000A1
    • Région KOR : 000000A9
    • Région TWN : 000000B1
  5. Retirez la carte SD de votre ordinateur et réinsérez-là dans votre 3DS
Clear HOME Menu theme data
  1. Éteignez votre 3DS
  2. Insérez votre carte SD dans votre ordinateur
  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. Retirez la carte SD de votre ordinateur et réinsérez-là dans votre 3DS
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 device’s settings, you will need to disable it. In order to do this, you need to obtain your device’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