<li><ahref="#site-nav"class="screen-reader-shortcut">Skip to primary navigation</a></li>
<li><ahref="#main"class="screen-reader-shortcut">Skip to content</a></li>
<li><ahref="#footer"class="screen-reader-shortcut">Skip to footer</a></li>
</ul>
</nav>
<!--[if lt IE 9]>
<divclass="notice--danger align-center"style="margin: 0;">You are using an <strong>outdated</strong> browser. Please <ahref="https://browsehappy.com/">upgrade your browser</a> to improve your experience.</div>
<p>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 <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> and describe your issue, including what you have already tried.</p>
<summary><u>Failed to open SafeB9SInstaller.bin</u></summary>
<p>The file <codeclass="language-plaintext highlighter-rouge">SafeB9SInstaller.bin</code> is missing or misplaced. Download the latest release of <ahref="https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip">SafeB9SInstaller</a>, extract it, and place <codeclass="language-plaintext highlighter-rouge">SafeB9SInstaller.bin</code> on the root of your SD card. Do not add the <codeclass="language-plaintext highlighter-rouge">.bin</code> extension if you do not already see it.</p>
<p>Your SD card is most likely acting weird. Try reformatting your SD card (<ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(mac)">macOS</a>, <ahref="formatting-sd-(linux)">Linux</a>). If this doesn’t work, try another SD card.</p>
<summary><u>SigHaxed FIRM - File not found</u></summary>
<p>You are missing <codeclass="language-plaintext highlighter-rouge">boot9strap.firm</code> and <codeclass="language-plaintext highlighter-rouge">boot9strap.firm.sha</code> from the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder, or the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder is misnamed. Download the latest release of <ahref="https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip">boot9strap</a>, and place <codeclass="language-plaintext highlighter-rouge">boot9strap.firm</code> and <codeclass="language-plaintext highlighter-rouge">boot9strap.firm.sha</code> in the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder.</p>
<p>There is an issue with your <codeclass="language-plaintext highlighter-rouge">boot9strap.firm</code> and <codeclass="language-plaintext highlighter-rouge">boot9strap.firm.sha</code> files. Re-download the latest release of <ahref="https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip">boot9strap</a>, and place <codeclass="language-plaintext highlighter-rouge">boot9strap.firm</code> and <codeclass="language-plaintext highlighter-rouge">boot9strap.firm.sha</code> in the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder.</p>
</details>
<details>
<summary><u>Secret Sector - File not found</u></summary>
<p>You are missing <codeclass="language-plaintext highlighter-rouge">secret_sector.bin</code> from the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder, or the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder is misnamed. Download <ahref="magnet:?xt=urn:btih:15a3c97acf17d67af98ae8657cc66820cc58f655&dn=secret_sector.bin&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.lelux.fi%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.loadbt.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.monitorit4.me%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.ololosh.space%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.pomf.se%3a80%2fannounce&tr=udp%3a%2f%2ftracker.srv00.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.theoks.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.zerobytes.xyz%3a1337%2fannounce&tr=udp%3a%2f%2ftracker1.bt.moack.co.kr%3a80%2fannounce&tr=udp%3a%2f%2fvibe.sleepyinternetfun.xyz%3a1738%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fopenbittorrent.com%3a80%2fannounce">secret_sector.bin</a> using a torrent client, and place it in the <codeclass="language-plaintext highlighter-rouge">boot9strap</code> folder.</p>
</details>
<details>
<summary><u>Something else</u></summary>
<p>Join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for assistance, and describe the message that you see.</p>
<p>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 <ahref="https://github.com/TuxSH/universal-otherapp/releases/latest">here</a>.</p>
<p>If your console is not on those firmwares, it likely indicates that you already have custom firmware. You should <ahref="checking-for-cfw">check for CFW</a>.</p>
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
<p>There is an issue with your <codeclass="language-plaintext highlighter-rouge">otherapp.bin</code> file (it is missing, misplaced, or corrupted). Download the latest release of <ahref="https://github.com/TuxSH/universal-otherapp/releases/latest">universal-otherapp</a> and place it on the root of your SD card.</p>
<p>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. Join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for assistance.</p>
<summary><u>Failed to mount the SD card!</u></summary>
<p>Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system (<ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(mac)">macOS</a>, <ahref="formatting-sd-(linux)">Linux</a>). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.</p>
<p>If this is unsuccessful, try using another SD card.</p>
<summary><u>Python 3 is not installed</u></summary>
<p>Python is not installed on the computer you are using. Download it from the <ahref="https://www.python.org/downloads/">Python website</a>, double-click the installer, and follow the prompts to install Python. Once Python is installed, try again.</p>
</details>
<details>
<summary><u>Error 01: Couldn't find Nintendo 3DS folder</u></summary>
<p>You are not running MSET9 from the root of the SD card, or the SD card is missing the Nintendo 3DS folder.</p>
<p>Remember, your SD card should look like this:</p>
<p>If your SD card layout is correct, then your SD card most likely isn’t being read by your console. Re-format it (<ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(linux)">Linux</a>, <ahref="formatting-sd-(mac)">macOS</a>), then start again from the beginning of <ahref="installing-boot9strap-(mset9-cli)#section-i---prep-work">Section I</a>.</p>
<summary><u>Error 02: Your SD is write protected</u></summary>
<p>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 <ahref="/images/sdlock.png">upright position</a>. Otherwise, try ejecting and reinserting your SD card.</p>
<p>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”).</p>
<p>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 <ahref="installing-boot9strap-(mset9-cli)#section-i---prep-work">Section I</a>.</p>
<p>Copy everything off the SD Card to your PC, re-format it (<ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(linux)">Linux</a>, <ahref="formatting-sd-(mac)">macOS</a>), copy everything back, then start again from the beginning of <ahref="installing-boot9strap-(mset9-cli)#section-i---prep-work">Section I</a>.</p>
<p>Mii Maker data was not found on the SD card. Start again from the beginning of <ahref="installing-boot9strap-(mset9-cli)#section-i---prep-work">Section I</a>.</p>
<p>You have multiple ID0 folders. To determine the correct folder, follow these instructions:</p>
<ol>
<li>Rename the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder to <codeclass="language-plaintext highlighter-rouge">BACKUP_Nintendo 3DS</code></li>
<li>Reinsert your SD card into your console</li>
<li>Power on your console</li>
<li>Wait for the console to generate the SD card data
<ul>
<li>Your applications will have disappeared. This is normal and will be resolved shortly</li>
</ul>
</li>
<li>Power off your console</li>
<li>Insert your SD card into your computer</li>
<li>Navigate to the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder on your SD card</li>
<li>Write down the first few characters of the folder you see
<ul>
<li>This is your true ID0, which we will keep in the real Nintendo 3DS folder</li>
</ul>
</li>
<li>Delete the ID0 from the current <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder</li>
<li>Move the true ID0 folder from the <codeclass="language-plaintext highlighter-rouge">BACKUP_Nintendo 3DS</code> folder to the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder</li>
<li>If it exists, move the <codeclass="language-plaintext highlighter-rouge">Private</code> folder from the <codeclass="language-plaintext highlighter-rouge">BACKUP_Nintendo 3DS</code> folder to the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder</li>
<p>One or more files that MSET9 needs to run is missing or corrupted. Re-download the <ahref="https://github.com/zoogie/MSET9/releases/latest">MSET9 Release <codeclass="language-plaintext highlighter-rouge">.zip</code></a> and extract it to the root of your SD card, replacing all existing files, then try again.</p>
</details>
<details>
<summary><u>Error 10: Database(s) malformed or missing!</u></summary>
<li>Navigate to System Settings -> Data Management -> Nintendo 3DS -> Software -> Reset (<ahref="/images/screenshots/database-reset.jpg">visual instructions</a>)</li>
<p>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.</p>
<p>Now, delete all but one of the folders from your SD card. Generally, you will want to delete the <strong>smallest</strong> 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”:</p>
<p>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.</p>
<p>You may be missing <codeclass="language-plaintext highlighter-rouge">SafeB9S.bin</code> from the root of your SD card, or the file may be corrupted. Copy it from the MSET9 <codeclass="language-plaintext highlighter-rouge">.zip</code>, replacing any existing files.</p>
<p>Alternatively, your SD card may be improperly formatted or partitioned. Try reformatting your SD card: <ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(linux)">Linux</a>, <ahref="formatting-sd-(mac)">macOS</a><em>(this will wipe your SD card data)</em></p>
<li><strong>Linux</strong>: open a Terminal window, <codeclass="language-plaintext highlighter-rouge">cd</code> to the root of your SD card, then type <codeclass="language-plaintext highlighter-rouge">python3 mset9.py</code> and press Enter</li>
<li>You should see a window that says “MSET9 … SETUP by zoogie”</li>
</ul>
</li>
<li>Type the number corresponding to your console model and version, then press Enter</li>
<li>Type <codeclass="language-plaintext highlighter-rouge">3</code>, then press Enter</li>
<p>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:</p>
<li><strong>Linux</strong>: open a Terminal window, <codeclass="language-plaintext highlighter-rouge">cd</code> to the root of your SD card, then type <codeclass="language-plaintext highlighter-rouge">python3 mset9.py</code> and press Enter</li>
<li>You should see a window that says “MSET9 … SETUP by zoogie”</li>
</ul>
</li>
<li>Type the number corresponding to your console model and version, then press Enter</li>
<li>If possible, use a new SD card; otherwise, backup and reformat your existing SD card as FAT32 (<ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(linux)">Linux</a>, <ahref="formatting-sd-(mac)">macOS</a>)</li>
<summary><u>"An error has occurred. Please save your data in any software currently in use, then restart the system."</u></summary>
<p>The date is set incorrectly. To set it correctly, follow these steps:</p>
<ol>
<li>Select the System Settings icon on the HOME Menu, and tap Open.</li>
<li>Tap Other Settings.</li>
<li>Tap Date & Time.</li>
<li>Tap Today’s date.</li>
<li>Tap Up/Down Arrows to set the correct Day, Month and Year.</li>
<li>Select OK to confirm.</li>
</ol>
<p>If the problem persists:</p>
<ul>
<li>Ensure that <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code>, <codeclass="language-plaintext highlighter-rouge">browserhax_hblauncher_ropbin_payload.bin</code>, and <codeclass="language-plaintext highlighter-rouge">boot.3dsx</code> are on the root of the SD card (not inside of any folder)</li>
<li>Ensure that you selected the correct payload for your region AND system version</li>
<li>Ensure that your region settings look <ahref="/images/screenshots/skater_lang.png">like this</a></li>
<li>Try resetting your browser data:
<ol>
<li>Launch the browser, then launch the browser settings</li>
<li>Scroll to the bottom and select “Reset Save Data” (it may also be called “Initilize Save Data” or “Clear All Save Data”)</li>
<li>Try the exploit again</li>
</ol>
</li>
<li>Try changing the system language to something other than the current language</li>
</ul>
</details>
<details>
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
<p>The file <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code> is missing or misplaced. Make sure to copy the files of the <ahref="https://github.com/zoogie/super-skaterhax/releases/latest">latest version of super-skaterhax</a> for your region and version to the root of your SD card (not inside of a folder).</p>
<summary><u>Red/purple/pink and white screen after running Browserhax</u></summary>
<p>This likely indicates that you already have custom firmware. You should <ahref="checking-for-cfw">check for CFW</a>.</p>
</details>
<details>
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)</u></summary>
<p>The file <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code> is missing or misplaced. Download the latest release of <ahref="https://github.com/TuxSH/universal-otherapp/releases/latest">universal-otherapp</a>, place <codeclass="language-plaintext highlighter-rouge">otherapp.bin</code> on the root of your SD card and rename it to <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code>. Do not add the <codeclass="language-plaintext highlighter-rouge">.bin</code> extension if you do not already see it.</p>
</details>
<details>
<summary><u>"An error has occurred, forcing the software to close..." (white message box)</u></summary>
<p>There may be an issue with your <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code> file. Download the latest release of <ahref="https://github.com/TuxSH/universal-otherapp/releases/latest">universal-otherapp</a>, place <codeclass="language-plaintext highlighter-rouge">otherapp.bin</code> on the root of your SD card and rename it to <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code>. Do not add the <codeclass="language-plaintext highlighter-rouge">.bin</code> extension if you do not already see it.</p>
<p>You can also try resetting your browser save data:</p>
<ol>
<li>Launch the browser, then launch the browser settings</li>
<li>Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)</li>
<li>Try the exploit again</li>
</ol>
</details>
<details>
<summary><u>Opening the browserhax QR code or URL crashes</u></summary>
<p>Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.</p>
<ol>
<li>Launch the browser, then launch the browser settings</li>
<li>Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)</li>
<li>Try the exploit again</li>
</ol>
</details>
<details>
<summary><u>System Update prompt when opening browser</u></summary>
<p>The SSLoth proxy was incorrectly configured. Re-do the SSLoth section on the page.</p>
</details>
<details>
<summary><u>Error 032-0420 when opening browser</u></summary>
<p>Follow these steps in order:</p>
<ol>
<li>Launch System Settings on your console</li>
<li>Navigate to <codeclass="language-plaintext highlighter-rouge">Internet Settings</code> -><codeclass="language-plaintext highlighter-rouge">Connection Settings</code></li>
<li>Click on your network connection slot and navigate to <codeclass="language-plaintext highlighter-rouge">Change Settings</code> -><codeclass="language-plaintext highlighter-rouge">Next Page (right arrow)</code> -><codeclass="language-plaintext highlighter-rouge">Proxy Settings</code></li>
<li>Set “Proxy Settings” to “No”</li>
<li>Click OK, then click Save</li>
<li>When prompted, click “Test” to perform the connection test
<ul>
<li>The test should succeed</li>
</ul>
</li>
<li>Click “OK” to continue</li>
<li>Press “Back” twice, then “Close” to go back to the HOME Menu</li>
<li>Open the Internet Browser once</li>
<li>If prompted about a system update, press OK
<ul>
<li>This won’t actually update the system</li>
</ul>
</li>
<li>Start again from <ahref="installing-boot9strap-(ssloth-browser).html#section-ii---ssloth">Section II</a></li>
</ol>
</details>
<details>
<summary><u>Frozen on "Doing agbhax..."</u></summary>
<p>There may be an issue with your <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code> file. Re-download the latest release of <ahref="https://github.com/TuxSH/universal-otherapp/releases/latest">universal-otherapp</a>, place it on the root of your SD card, and rename it to <codeclass="language-plaintext highlighter-rouge">arm11code.bin</code>. Do not add the <codeclass="language-plaintext highlighter-rouge">.bin</code> extension if you do not already see it.</p>
</details>
<details>
<summary><u>"PrepareArm9ForTwl returned error c8804631!"</u></summary>
<p>Join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for assistance.</p>
</details>
<details>
<summary><u>Failed to mount the SD card!</u></summary>
<p>Back up your data and reformat your SD card as FAT32 with the recommended tool depending on your operating system (<ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(mac)">macOS</a>, <ahref="formatting-sd-(linux)">Linux</a>). MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.</p>
<p>If this is unsuccessful, try using another SD card.</p>
<p>The steps below can be attempted in any order, but are listed from easiest to hardest to perform.</p>
<ol>
<li>Set your DNS settings to “Auto”</li>
<li>Move closer to your WiFi router</li>
<li>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</li>
<li>Delete your WiFi connection, then reconnect to your WiFi again</li>
<li>Reboot your WiFi router</li>
<li>Connect to a different WiFi connection, like a mobile hotspot</li>
<li>Nintendo servers may be down; Try again later</li>
<li>If you still get an error, <ahref="ctrtransfer">follow CTRTransfer</a>, then try again</li>
<li>For further support (in English), join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a></li>
<p>The file <codeclass="language-plaintext highlighter-rouge">finalize.romfs</code> is corrupt or unreadable. <ahref="/assets/finalize.romfs">Re-download it</a> and copy it to the root of the SD card, replacing any existing copy, then try again.</p>
<p>The file <codeclass="language-plaintext highlighter-rouge">finalize.romfs</code> 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.</p>
<summary><u>Error #24: SD is write-protected</u></summary>
<p>Ensure that your SD card is not <ahref="/images/sdlock.png">locked</a>. If the SD card is not locked and you continue to get this error, join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for assistance.</p>
<p>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.</p>
<p>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:</p>
<li>The console should automatically power off</li>
</ul>
</li>
<li>Insert your SD card into your computer</li>
<li>Copy the files in <codeclass="language-plaintext highlighter-rouge">/gm9/backups/</code> on your SD to a safe location on your computer</li>
<li>Delete the <codeclass="language-plaintext highlighter-rouge"><date>_<serialnumber>_sysnand_##.bin</code> and <codeclass="language-plaintext highlighter-rouge"><date>_<serialnumber>_sysnand_##.bin.sha</code> files from the SD card</li>
<li>Perform a <ahref="godmode9-usage#creating-a-nand-backup">NAND Backup</a></li>
<li>Copy the files in <codeclass="language-plaintext highlighter-rouge">gm9/out</code> on your SD to a safe location on your computer</li>
<li>Delete the <codeclass="language-plaintext highlighter-rouge"><date>_<serialnumber>_sysnand_##.bin</code> and <codeclass="language-plaintext highlighter-rouge"><date>_<serialnumber>_sysnand_##.bin.sha</code> files from the SD card, keeping essential.exefs in <codeclass="language-plaintext highlighter-rouge">/gm9/out/</code></li>
<li>Copy the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder from your computer to the root of your SD card</li>
<li>Delete the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder from your computer</li>
</ol>
<p>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: <ahref="h2testw-(windows)">Windows</a>, <ahref="f3-(linux)">Linux</a>, <ahref="f3xswift-(mac)">macOS</a>.</p>
<p>Ensure that your SD card is not <ahref="/images/sdlock.png">locked</a>. If the SD card is not locked and you continue to get this error, join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for assistance.</p>
<p>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:</p>
<p>You didn’t remove MSET9 when prompted to. Follow Section IV - Removing MSET9 from the <ahref="installing-boot9strap-(mset9-cli)#section-iv---removing-mset9">Windows/macOS/Linux guide</a> or the <ahref="installing-boot9strap-(mset9-play-store)#section-iv---removing-mset9">Android/ChromeOS guide</a>, then re-run the script.</p>
<pclass="notice--info">The steps detailed here generally assume that your console 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.</p>
<p>There is an issue with your <codeclass="language-plaintext highlighter-rouge">boot.firm</code> file. If you’re running <ahref="https://github.com/SciresM/boot9strap/releases/tag/1.4">boot9strap 1.4</a>, your 3DS notification LED may flash a certain color. This color is used to diagnose issues involving your <codeclass="language-plaintext highlighter-rouge">boot.firm</code> 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.</p>
<li><strong>White</strong>: Your 3DS was not able to find <codeclass="language-plaintext highlighter-rouge">boot.firm</code> on your SD card or on internal memory.</li>
<li><strong>Magenta</strong>: Your 3DS was not able to find <codeclass="language-plaintext highlighter-rouge">boot.firm</code> on your SD card. It was able to find <codeclass="language-plaintext highlighter-rouge">boot.firm</code> on internal memory, but the file is corrupted.</li>
<li><strong>Red</strong>: Your 3DS was able to find <codeclass="language-plaintext highlighter-rouge">boot.firm</code> on both your SD card and on internal memory, but both files are corrupted.</li>
</ul>
<p>You can get a new <codeclass="language-plaintext highlighter-rouge">boot.firm</code> file by downloading the <ahref="https://github.com/LumaTeam/Luma3DS/releases/latest">latest release of Luma3DS</a>, extracting it, and placing <codeclass="language-plaintext highlighter-rouge">boot.firm</code> on the root of your SD card. If your <codeclass="language-plaintext highlighter-rouge">boot.firm</code> file is consistently being detected as corrupted, you may want to check your SD card for errors (<ahref="h2testw-(windows)">Windows</a>, <ahref="f3-(linux)">Linux</a>, or <ahref="f3xswift-(mac)">macOS</a>). Also, note that the 3DS tends to have issues with files extracted using WinRAR.</p>
<p>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.</p>
<li>Power off your console, remove the SD card, re-insert it, then power on your console.</li>
<li>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</li>
<li>Rename the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder on your SD card to <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS_BACKUP</code>, then attempt to boot. If your console successfully boots, there is some issue within your <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> folder. Try clearing HOME Menu extdata:
<li>Follow the <ahref="ctrtransfer">CTRTransfer</a> guide</li>
<li>For further support, ask for help at <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a></li>
</ol>
</details>
<h3id="error-message-on-boot">Error message on boot</h3>
<details>
<summary><u>"An error has occurred: Failed to apply 1 FIRM patch(es)" or "An exception has occurred -- Current process: pm"</u></summary>
<p>Your Luma3DS version is outdated. Download the latest release of <ahref="https://github.com/LumaTeam/Luma3DS/releases/latest">Luma3DS</a> and place <codeclass="language-plaintext highlighter-rouge">boot.firm</code> 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.</p>
</details>
<details>
<summary><u>"Unable to mount CTRNAND or load the CTRNAND FIRM. Please use an external one."</u></summary>
<p>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 <ahref="ctrtransfer">CTRTransfer</a> guide.</p>
</details>
<details>
<summary><u>"An error has occurred. Hold down the POWER button to turn off the power..."</u></summary>
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.
<li>Power off your console, remove the SD card, insert it on your computer, download the latest release of <ahref="https://github.com/LumaTeam/Luma3DS/releases/latest">Luma3DS</a>, extract <codeclass="language-plaintext highlighter-rouge">boot.firm</code> from the <codeclass="language-plaintext highlighter-rouge">Luma3DS.zip</code> and place it on the root of your SD card (replacing any existing file)</li>
<li>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: <ahref="formatting-sd-(windows)">Windows</a>, <ahref="formatting-sd-(mac)">macOS</a>, <ahref="formatting-sd-(linux)">Linux</a><em>(this will wipe your SD card data)</em></li>
<li>Test your SD card for errors by following the guide according to your computer’s operating system: <ahref="h2testw-(windows)">Windows</a>, <ahref="f3-(linux)">Linux</a>, <ahref="f3xswift-(mac)">macOS</a>. If your SD card is marked as faulty, then you will have to replace your SD card</li>
<li>Your SD card slot may be broken. Join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for further assistance</li>
<p>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. In any case, join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for assistance.
+ It is also possible that someone has set a boot-time splash screen that just looks like a brick. Try leaving your console powered on, waiting on the blue screen, for five minutes.</p>
<summary><u>DSi / DS functionality is broken or has been replaced with Flipnote Studio</u></summary>
<ol>
<li>Download the latest release of <ahref="https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/latest">TWLFix-CFW</a> (the <codeclass="language-plaintext highlighter-rouge">.3dsx</code> file)</li>
<li>Create a folder named <codeclass="language-plaintext highlighter-rouge">3ds</code> on the root of your SD card if it does not already exist</li>
<li>Copy <codeclass="language-plaintext highlighter-rouge">TWLFix-CFW.3dsx</code> to the <codeclass="language-plaintext highlighter-rouge">/3ds/</code> folder on your SD card</li>
<p>Your console is running Luma3DS 6.6 or older, likely via arm9loaderhax. You should follow <ahref="a9lh-to-b9s">A9LH to B9S</a> to update your console to a modern custom firmware environment.</p>
<summary><u>Exception screen when booting/loading an application</u></summary>
<p>Look for your exception screen in <ahref="https://wiki.hacks.guide/wiki/3DS:Error_screens/Luma3DS_exception_screen">this page</a>.
If you weren’t able to find your error or the instructions didn’t work, join <ahref="https://discord.gg/MWxPgEp">Nintendo Homebrew on Discord</a> for further assistance.</p>
<summary><u>Opening the HOME Menu settings crashes the console or loads the Homebrew Launcher</u></summary>
<p>Your console likely still has menuhax67 installed. To uninstall menuhax67, download the latest release of <ahref="https://github.com/zoogie/menuhax67/releases/latest">menuhax67</a> (the menuhax <codeclass="language-plaintext highlighter-rouge">.zip</code>), then follow the <ahref="https://wiki.hacks.guide/wiki/3DS:Alternate_Exploits/menuhax67#Uninstall_menuhax67">“Uninstall menuhax67” section</a> here.</p>
<li>Navigate to the <codeclass="language-plaintext highlighter-rouge">/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> folder on your SD card</li>
<li>Delete the corresponding folder for your 3DS region:
<li>Navigate to the <codeclass="language-plaintext highlighter-rouge">/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> folder on your SD card</li>
<li>Delete the corresponding folder for your 3DS region:
<p>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 <ahref="https://github.com/LumaTeam/Luma3DS/releases/latest">boot.3dsx and boot.firm</a> on the root of your SD card.)</p>
<ol>
<li>Launch the Download Play application (<imgsrc="https://3ds.hacks.guide/images/download-play-icon.png"alt=""height="24px"width="24px"/>)</li>
<li>Wait until you see the <codeclass="language-plaintext highlighter-rouge">Nintendo 3DS</code> and <codeclass="language-plaintext highlighter-rouge">Nintendo DS</code> buttons</li>
<li>Press (Left Shoulder) + (D-Pad Down) + (Select) at the same time to open the Rosalina menu</li>
<li>Select “Miscellaneous options”</li>
<li>Select “Switch the hb. title to the current app.”</li>
<li>Press (B) to continue</li>
<li>Press (B) to return to the Rosalina main menu</li>
<li>Press (B) to exit the Rosalina menu</li>
<li>Press (Home) to suspend Download Play</li>
<li>Press the “Close” button on the bottom screen to close Download Play</li>
<li>Re-launch the Download Play application</li>
<li>Your console should load the Homebrew Launcher
<ul>
<li>If your console is stuck on the loading splash screen, you are missing <codeclass="language-plaintext highlighter-rouge">boot.3dsx</code> from the root of your SD card</li>
<summary><u>Turning off Parental Controls</u></summary>
<p>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):</p>
