Hacks Guide Wiki - User contributions [en]

3DS:Alternate Exploits/Preparing menuhax67 (kartdlphax)

2025-09-30T03:45:38Z

ShinyTillDawn: USM is no longer on the main guide.

==Required Reading==
[https://github.com/PabloMK7/kartdlphax kartdlphax] is an exploit for the game "[[3DS:Mario Kart 7|Mario Kart 7]]", compatible with System Versions 1.0.0 through 11.17.0 for USA/EUR/JPN region consoles primarily made made by [https://github.com/PabloMK7 PabloMK7]. It was used to launch [https://github.com/TuxSH/universal-otherapp universal-otherapp] in the past, that got patched with the latest version, so this exploit can be used now to prepare the secondary exploits [https://github.com/zoogie/unSAFE_MODE unSAFE_MODE](you can find this on [[hacksguidewiki:3DS:Alternate_Exploits/Installing_boot9strap_(HBL-USM)|this page]]) or [https://github.com/zoogie/menuhax67 menuhax67] on 11.16.0+. Credits go to [https://github.com/zoogie zoogie] for both of these exploits. If you're on an older version(<=11.15.0-47X), you can use universal-otherapp instead. This page covers preparing menuhax67 to access the Homebrew Launcher since accessing the Homebrew Launcher from kartdlphax directly not possible currently. On the next page you will find out how to access the Homebrew Launcher with menuhax67 set up. To use these exploits, kartdlphax includes the [https://github.com/PabloMK7/3dsropxploitinjector 3DS ROP xPloit Injector]

To use this exploit, you need:

*A second 3DS with [[custom firmware]] (the '''source 3DS''') that is the same region as the 3DS you are trying to modify (the '''target 3DS''')
*A physical or digital copy of Mario Kart 7 that is the same region as both consoles
*An SD card for both devices

==What you need==
*The latest release of [https://github.com/PabloMK7/kartdlphax/releases/latest kartdlphax] (<code>plugin.3gx</code>)
*The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file)
*The latest release of [https://github.com/zoogie/menuhax67/releases/latest menuhax67] (the menuhax67 <code>.zip</code> file)

==Instructions==

===Section I - Prep Work===
On the '''source 3DS''' (the 3DS with custom firmware):

#Insert the SD card of your '''source 3DS''' in your computer
#Copy everything to the root of your SD card
#*The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
#Copy kartdlphax’s <code>plugin.3gx</code> to the following directory on the '''source 3DS'''’s SD card, depending on the '''region of your copy of Mario Kart 7''':
#*USA: <code>luma/plugins/0004000000030800</code>
#*EUR: <code>luma/plugins/0004000000030700</code>
#*JPN: <code>luma/plugins/0004000000030600</code>
#*Create the <code>plugins</code> and <code>00040000...</code> folders if they do not already exist
#Eject the SD card and put it in the '''source 3DS'''

On the '''target 3DS''' (the 3DS that you are trying to launch the Homebrew Launcher on):

#Insert the SD card of your '''target 3DS''' in your computer
#Copy everything from the Luma3DS <code>.zip</code> to the root of your SD card
#Copy the <code>Launcher.dat</code> for your region/version from the menuhax67 <code>.zip</code> to the root of your SD card

===Section II - kartdlphax===

#Power on the '''source 3DS'''
#*If you are prompted to set up Luma3DS, just press START to save the configuration
#Once in the HOME Menu, press (Left Shoulder) + (Down D-Pad) + (Select) to bring up the Rosalina menu
#Select “Enable plugin loader”
#Press (B) to exit the Rosalina menu
#Launch Mario Kart 7
#*Ensure that wireless connectivity is enabled
#Navigate to <code>Local Multiplayer</code>. A menu should pop up
#*If the screen freezes, hold the power button for fifteen seconds to force power off your device, then try again
#*If you have launched kartdlphax previously, the last selected settings will be loaded. If they are correct, select <code>Use settings</code> and skip the next 3 steps. If they are incorrect, select <code>Change settings</code> and proceed.
#Select your '''target 3DS''' device type (Old 3DS family or New 3DS family)
#Select the exploit type <code>3DS ROP xPloit Injector</code>
#A confirmation menu will show up. If the settings shown on the top screen are correct, select <code>Use settings</code>
#*If the settings are not correct, press <code>Change settings</code> and modify them accordingly
#Select <code>Create Group</code>
#*If the source 3DS freezes at this point and you are using a cartridge, try installing the cartridge to the system
#Power on the '''target 3DS'''
#*Ensure that wireless connectivity is enabled
#On the '''target 3DS''', open the Download Play application (), then select “Nintendo 3DS”
#Join the group created by the '''source 3DS'''
#Select “Start” on the '''source 3DS''' once it has detected the '''target 3DS'''
#Once multiplayer has loaded, navigate to <code>Grand Prix</code> -> <code>50cc</code> -> (any driver) -> <code>Mushroom Cup</code> -> <code>OK</code>
#Wait a while (a percentage should be displayed on the '''source 3DS''')
#If the exploit was successful, the '''target 3DS''' will have booted into the 3DS ROP xPloit Injector
#*If the exploit was not successful, power off the '''source 3DS''' and '''target 3DS''' and start again from the beginning of <code>Section II - kartdlphax</code>
#Press (Y) to install menuhax67
#The '''target 3DS''' will automatically power off
{{Info|text=You will not need to use your source 3DS to complete any further steps on this guide. Any further steps should only be completed on the target 3DS.}}

-----

<span style="font-size:200%;">Continue to [[3DS:Alternate_Exploits/menuhax67#Using_menuhax67 | Using menuhax67]]</span>

[[Category:Nintendo 3DS guides]]

3DS:Alternate Exploits/Installing boot9strap (SSLoth-Browser)

2025-08-24T01:45:21Z

ShinyTillDawn: Updated the PrepareArm9ForTwl error solution to closely match that of 3ds.hacks.guide.

==Technical Details==
In order to exploit the Browser application, we need to bypass the browser version check, which is designed to disallow the use of the browser without updating to the latest system version.

A public proxy server is available, which, with the help of the SSLoth exploit, can bypass this check.

Once the bypass is active, an exploit webpage will be accessible which will do the rest of the job.

For technical details on the exploits that you will be using on this page, see [https://github.com/MrNbaYoh/3ds-ssloth here] (SSLoth) and [https://github.com/TuxSH/universal-otherapp here] (universal-otherapp).

==Compatibility Notes==
SSLoth allows users on version 11.13.0 and below to bypass the browser version check, allowing the use of new-browserhax or old-browserhax (compatible with versions 11.4.0 through 11.13.0 in all regions), which can then be used in conjunction with universal-otherapp.

==What You Need==

*The latest release of [https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip SafeB9SInstaller] (direct download)
*The latest release of [https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip boot9strap] (direct download)
*The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file)
*The latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp] (<code>otherapp.bin</code>)

==Instructions==

====Section I - Prep Work====

#Power off your console
#Insert your SD card into your computer
#Copy <code>otherapp.bin</code> to the root of your SD card and rename it to <code>arm11code.bin</code>
#*The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
#*If you do not see the <code>.bin</code> extension, do not add it to the end of the filename
#Copy everything from the Luma3DS <code>.zip</code> to the root of your SD card
#Create a folder named <code>boot9strap</code> on the root of your SD card
#Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> from the boot9strap <code>.zip</code> to the <code>/boot9strap/</code> folder on your SD card
#Copy <code>SafeB9SInstaller.bin</code> from the SafeB9SInstaller <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your console
#Power on your console

====Section II - SSLoth====

#Launch the System Settings application
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “Yes”, then click <code>Detailed Setup</code>
#Set the Proxy Server to <code>ssloth.nintendohomebrew.com</code>, and the Port to <code>8080</code>
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Click “OK” to continue
#Press “Back” twice, then “Close” to go back to the HOME Menu

====Section III - Launching SafeB9SInstaller====

#On the HOME Menu, press the Left and Right shoulder buttons at the same time to open the camera
#*If you are unable to open the camera, open the Internet Browser and manually type the URL instead (<code><nowiki>https://zoogie.github.io/web/nbhax/</nowiki></code>)
#Tap the QR code button and scan this QR code<br>{{qrlite|content=https://zoogie.github.io/web/nbhax/|format=png|size=5|margin=5}}
#*If you get a crash or an error code, follow the troubleshooting guide at the bottom of the page
#*If you get a security certificate warning, press (A) to allow the connection
#Tap the “PROCEED TO HAXX” button
#If the exploit was successful, you will have booted into SafeB9SInstaller
#*If you get an error, follow the troubleshooting guide at the bottom of the page

====Section IV - Installing boot9strap====

#When prompted, input the key combo given on the top screen to install boot9strap
#*If a step on the lower screen has red-colored text, and you are not prompted to input a key combo, [[3dsguide:troubleshooting#issues-with-safeb9sinstaller|follow this troubleshooting guide]]
#Once it is complete, press (A) to reboot your console
#Your console should have booted into the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, '''leave these options on the default settings''' (do not check or uncheck anything)
#*If your console shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

====Section V - Restoring default proxy====

#Launch the System Settings application
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “No”
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Power off your console

At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.

-----

<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

==Troubleshooting==

===Red/purple/pink and white screen after running Browserhax===
This likely indicates that you already have custom firmware. You should [[3dsguide:checking-for-cfw|check for CFW]].

==="An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text)===
The file <code>arm11code.bin</code> is missing or misplaced. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

==="An error has occurred, forcing the software to close..." (white message box)===
There may be an issue with your <code>arm11code.bin</code> file. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

You can also try resetting your browser save data:

#Launch the browser, then launch the browser settings
#Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
#Return to Section III

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

#Launch the browser, then launch the browser settings
#Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
#Return to Section III

===System Update prompt when opening browser===
The SSLoth proxy was incorrectly configured. Re-do Section II on this page.

===Error 032-0420 when opening browser===
Follow these steps in order:

#Launch System Settings on your console
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “No”
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Click “OK” to continue
#Press “Back” twice, then “Close” to go back to the HOME Menu
#Open the Internet Browser once
#If prompted about a system update, press OK
#*This won’t actually update the system
#Start again from Section II

===Frozen on "Doing agbhax..."===
There may be an issue with your <code>arm11code.bin</code> file. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

==="PrepareArm9ForTwl returned error c8804631!"===
DS Internet Settings is inaccessible from the console. Follow [[3DS:Alternate Exploits|a different exploit]] instead.

===Failed to mount the SD card!===
Back up your data and [[Formatting an SD card|reformat your SD card as FAT32]] with the recommended tool depending on your operating system. 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.
[[Category:Nintendo 3DS guides]]

3DS:Dsu

2025-08-15T21:32:43Z

ShinyTillDawn: Create a redirect to the DS mode unbrick page.

#REDIRECT [[3DS:DS mode unbrick]]

3DS:Error screens/Luma3DS exception screen

2025-08-12T17:50:01Z

ShinyTillDawn: Capitalized a word.

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

==Reading a Luma3DS exception screen==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
*'''Processor:''' What part of the system is causing the exception. The two processors are:
**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
*'''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
**'''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
**'''fs''': The filesystem, i.e. either the SD card or the NAND.
**'''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.
**'''nwm''': Networking services, almost always Wi-Fi.
**'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
*'''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
**If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
**If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.
*'''Stack dump''': A list of code running in memory at the time of the crash. While normally not that useful it will sometimes contain a Title ID of the process that crashed in little-endian, which can help narrow down the issue if "Current process" doesn't have one listed.

==Known Errors==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the {{ml|Get support|Nintendo Homebrew Discord}} for further assistance.}}
----

===<big>Arm9</big>===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
*Files on the SD are corrupted.
**To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
*A system save located on the NAND in <code>[1:]/data</code> has a problem.
*System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
*The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
**To fix, create this folder.
*System titles have been deleted.
**To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
*The console likely has a hardware issue.

<h5>prefetch abort (svcBreak)</h5>
*The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
**To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
*<code>SYSNAND CTRNAND</code> has bad CMACs.
**To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>undefined instruction</h5>
*The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
*Files on the SD are corrupted.
**If only 1 app crashes, delete the app from <code>System Settings</code> -> <code>Data Management</code>, then reinstall.
**If multiple apps crash, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

===<big>Arm11</big>===

All Arm11 errors are sorted by their '''current process''', except for entries that can apply to multiple processes; these always appear first in the list for simplicity.
<br>If an error appears in the <code>Error At Any Time</code> section, do not look for it in the other two sections.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>gsp/i2c/mcu/pxi/spi</h5>
*The console has a serious hardware issue that is likely not easily fixable.
**Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join {{ml|Get support|the Nintendo Homebrew Discord}} and ask, in English, for help.

<h5>act</h5>
*Your NNID(s)' stored data is misconfigured or being interfered with.
**To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].
***If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
*<h6>Outdated firmware (11.16 or older):</h6>
**The current firmware version may be too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
***If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]
*<h6>Latest firmware (11.17):</h6>
**An outdated installation of NetPass is likely interfering with your console. To check this, do the following steps:
**#Hold {{B|SELECT}} while powering on the console
**#Within the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]], disable <code>Enable loading external FIRMs and modules</code>
**#Either press {{B|START}} or press {{B|A}} on the <code>Save and exit</code> option to save changes and exit the configuration menu
**If the issue stops after this, update Netpass via [[3DS:Universal-Updater|Universal-Updater]] (recommended) or go to the [https://netpass.cafe/install.html NetPass Website] and follow the instructions there. Then, boot NetPass to update the patches.
**If this does not help, join the {{ml|Get support|Nintendo Homebrew Discord}} or the [https://netpass.cafe/discord NetPass Discord] and ask, in english, for help.

<h5>camera</h5>
*Potential hardware issues, or an instance of ShutTheCamUp is crashing.
**Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
***If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
***If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the {{ml|Get support|Nintendo Homebrew Discord}} and ask, in English, for help.

<h5>cfg</h5>
*Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
**To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
***If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
*Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
**[[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
*Either an instance of rehid is crashing, or your console may have hardware damage.
**First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
***If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
***If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>loader</h5>
*<h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>menu</h5>
*<h6>data abort</h6>
**The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
***To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**:USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
**The HOME Menu's extra data is corrupted.
***To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**:USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
**An installed application is corrupted or otherwise broken.
***To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
*<h6>prefetch abort</h6>
**An installation of Menuhax is conflicting with the custom firmware.
***To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
*<h6>prefetch abort (svcBreak)</h6>
**If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
***To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>mset</h5>
*System Settings is broken in some way - this may indicate that the console has a hardware issue.
**To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
***If neither of these work, the console has a serious issue. Join the {{ml|Get support|Nintendo Homebrew Discord}} and ask, in English, for help.

<h5>ns</h5>
*The [[3DS:Luma3DS/Configuration|Luma3DS configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
**To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
*The WiFi chipset's hardware is damaged or dead.
**To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
***If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
*The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
**To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>app/CtrApp/IbizaCit/Joker/Kirby3DS/Kujira/niji_loc/etc.</h5>
*The app you most recently opened is attempting to load corrupt code, instructions, or patches. As this type of error can happen to nearly anything on the console, if your listed '''current process''' does not show up anywhere else under Arm11, it may help to follow these instructions anyway.
**First, turn off all game mods, cheat codes, plugins, and both the settings <code>Game patching</code> and <code>loading external FIRMs and modules</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]] to stop all external interference.<br>If this fixes the issue, redownload all of those types of patches that you had enabled for the game(s) before turning them back on. If it does not fix the issue, check whether the game is the same region as the console and [[3DS:SGL|activate locale emulation]] if it is not.
***If the error continues after trying all of the above, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>cam/qtm</h5>
*The camera's hardware is damaged or dead.
**To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>3dsx_app</h5>
*The <code>.3dsx</code> file that was most recently opened is corrupted.
**To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**:If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>fs</h5>
*Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
**[[w:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>GARDEN</h5>
*Animal Crossing's game data or savedata is having issues.
**To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
***If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>loader</h5>

*<h6>undefined instruction</h6>
**The app most recently opened is trying to load invalid, missing, or corrupt data. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. A large number of such error codes can be found at [[3DS:ERRDISP|this page]], but here are the most common values seen in this error:
***<code>D9004587</code>: When trying to open a game: The game is corrupted, or its seed is not imported.
****To fix: Follow [[3DS:FCG|the corrupted games guide]]
***<code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
****To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
***<code>C88044AB</code>: If trying to open the Homebrew Launcher: Your SD card either is not properly inserted, or cannot be read by the console.
****To fix: Try to reinsert the SD more firmly, and check whether its data can be read on boot. If it can't, then [[Formatting an SD card|reformat the SD]].
***<code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
****To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
***Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
*<h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
*'''If not occurring in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
**To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
***If neither of these work, the console has a serious issue. Join the {{ml|Get support|Nintendo Homebrew Discord}} and ask, in English, for help.
*'''If occurring in Nintendo DS Profile:''' Your NVRAM either is corrupted or is suffering from hardware damage. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
*The WiFi chipset's hardware is damaged or dead.
**To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
***If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
*The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>pxi</h5>
*Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>swkbd</h5>
*The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
**To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
***If neither of these work, the console has a serious issue. Join the {{ml|Get support|Nintendo Homebrew Discord}} and ask, in English, for help.

[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]
{{Short description|Guide to the CFW error handler}}

3DS:DS games

2025-08-07T05:45:12Z

ShinyTillDawn: Typo fixes

{{shortcut|3DS:DS}}
The 3DS can run Nintendo DS games natively by simply inserting the cartridge on the slot, but, alternatively, if you don't want to carry your cartridges around, or if you'd like to use homebrew designed for the DS, you can use a [[3DS:Dump titles and game cartridges|dump]] from your Nintendo DS cartridge to run your game from the SD card.

=What You Need=
*The latest version of [[3DS:Universal-Updater|Universal-Updater]]
*A [[3DS:Dump titles and game cartridges|dump]] from your Nintendo DS cartridge ''or'' NDS homebrew in <code>.nds</code> format

=Instructions=
==TWiLight Menu++==
TWiLight Menu++ is an open-source DSi Menu upgrade/replacement for the Nintendo 3DS and Nintendo DS flashcards. It allows you to have multiple save files and have a menu to choose your games from.

#Open Universal-Updater from your HOME Menu.
#Search for '''TWiLight Menu++''', then press {{B|A}} over its icon to install it.
#*If you have to choose between a Nightly and Stable version, choose the Stable version.
#Wait for the download to complete.
#Close Universal-Updater.
{{success|You have successfully set up TWiLight Menu++! You can now navigate to your game's folder in the app and play.}}

==Forwarders==
Forwarders are shortcuts for games that you can install to your HOME Menu. You can load DS games from the SD card or from a compatible flashcard.

#Open Universal-Updater from your HOME Menu.
#Search for '''ndsForwarder''', then press {{B|A}} over its icon to install it.
#*If you have to choose between a Nightly and Stable version, choose the Stable version.
#Wait for the download to complete.
#Close Universal-Updater.
#Open the Homebrew Launcher.
#In the Homebrew Launcher, open '''NDS Forwarder Generator'''.
#Navigate to your game's folder and press {{B|A}}.
#Confirm you wish to install by selecting '''Yes'''.
{{success|You have successfully set up your forwarder!}}

[[Category:Nintendo 3DS guides]]

Wii U:Wii games

2025-08-03T23:10:25Z

ShinyTillDawn: Fixed a typo.

''All these methods assume you have modded your vWii. If have you not, follow this guide [[wiiguide:get-started|here]].''

{{Info|text=While of course simply loading your Wii disc from the Home Menu allows you to play Wii games, there are multiple ways to load backups of your Wii discs on your Wii U. You first must dump your Wii discs to get started.}}

===Dumping Wii games===
To dump your Wii games from your modded vWii follow this guide [https://wiki.hacks.guide/wiki/Wii_U:Dump_Wii_Games here].
==Method I: USB Loaders==
{{Info|text=USB Loaders allow you to load backups of your Wii discs from an external drive via your Wii U's USB ports or SD card.}}
===Instructions===
The process for setting up USB loaders on vWii is identical to that of the Wii's. Please follow the Wii Hacks Guide linked below.

===Continue to the USB loaders usage guide [[wiiguide:wii-loaders|here]].===

==Method II: Virtual Console Injections==
{{Info|text=UWUVCI allows you to inject any Wii backup into a preexisting Virtual Console title, and install it to your Wii U's internal storage, or an external drive connected via the Wii U's USB ports.}}
===Instructions===

====What you need====
*A PC/Mac
**UWUVCI is a WPF app so it's native to Windows, but can be ran with the use of tools like WINE for Mac/Linux
*The latest release of [https://github.com/stuff-by-3-random-dudes/UWUVCI-AIO-WPF/releases/latest UWUVCI AIO].
**This is a dependency, but the UWUVCI installer should install it for you:
***[https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer .net Framework 4.8] .
*Sigpatches on your Wii U.
**Download <code>01_sigpatches.rpx</code> from the github [https://github.com/marco-calautti/SigpatchesModuleWiiU/releases/latest here].
**Copy this file to your <code>sd:/wiiu/environments/[Aroma or Tiramisu]/modules/setup</code> folder.
*The backup of the Wii game you wish to inject.

===Continue to UWUVCI's Wii game guide [https://uwuvci-prime.github.io/UWUVCI-Resources/wii/wii.html here].===

3DS:Keyboard Unbrick

2025-01-05T19:54:52Z

ShinyTillDawn: Clarified that super-skaterhax can only be used on New 3DS models.

{{shortcut|3DS:KBU}}
If a custom keyboard is installed and custom firmware is removed from the console, System Settings will be inaccessible and you will not be able to launch the keyboard. This is obviously detrimental to the overall functioning of your 3DS and should be fixed as soon as possible.

=Unbricking a 3DS with a custom keyboard installed =
{{info|text=If Internet access isn't currently set up, you can set up an Internet connection from Safe Mode as the keyboard will still work there (hold {{Key press|L|R|Up|A}} on boot, then follow its prompts).}}

==Methods that require additional hardware==
The following methods require extra hardware but is the recommended way of recovering from this as they should work 100% of the time regardless of system version:
*[[3dsguide:ntrboot|ntrboot]] (Requires a compatible flashcard)
*[[3DS:Alternate Exploits/Preparing menuhax67 (kartdlphax)|kartdlphax]] (Requires a second console and a copy of Mario Kart 7, both the same region as your console)
*[[3DS:Alternate Exploits/3dsropxploitinjector (basehaxx)|basehaxx]] (Requires a second console and a copy of Pokémon Omega Ruby or Pokémon Alpha Sapphire, on cartridge.)

==Methods that don't require seedminer==
The following methods do not require seedminer and can be followed like normal:
*[[3dsguide:installing-boot9strap-(super-skaterhax).html|super-skaterhax]] (Your console date needs to be correct, and you must have a New 3DS. (A new 3DS has a C-Stick on top of the X button.) Otherwise, there is no reason to follow super-skaterhax.)

==Methods that require seedminer==
{{info|text=If you have a copy of any of the following:
* Your NAND backup (e.g. <code>220101_AA000000000_sysnand_000.bin</code>)
* <code>essentials.exefs</code>
* <code>movable.sed</code>
'''''YOU DO NOT NEED TO MINE YOUR SEED AGAIN.'''''
For instructions on extracting your <code>movable.sed</code> from your NAND backup or from <code>essentials.exefs</code>, see [[3DS:Recover movable.sed|this page]].}}

<div class="center-tabber-tabs">
<tabber>

|-|PicHaxx (Pokémon Picross)=

<span>
==Section I: Installing Pokémon Picross==

{{warning|text=If the eShop requires you to use the keyboard, or you cannot install Pokémon Picross, there's no point following the rest of this guide and you should choose another method.}}

Follow [https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop these] steps to redownload Pokémon Picross if available

==Section II: Mii mining==
{{info|text=If you already have your <code>movable.sed</code>, you can skip this section.}}

Because you can't enter a friend code due to the broken keyboard, you'll need to get your console's encryption key a different way. We can accomplish this by Mii mining.

Follow [[3DS:Seedminer/Mii mining|Mii mining]] to extract the <code>movable.sed</code> from your console, but do not continue onto the main guide as it suggests. Come back to this page once you have the movable.

==Section III: PicHaxx==
Now that you have your <code>movable.sed</code>, continue to [[3DS:Alternate Exploits/Homebrew Launcher (PicHaxx)|Homebrew Launcher (PicHaxx)]].
</span>

|-|Steelhax (Steel Diver: Sub Wars)=

<span>
==Section I: Installing Steel Diver: Sub Wars==

{{warning|text=If the eShop requires you to use the keyboard, or you cannot install Steel Diver: Sub Wars, there's no point following the rest of this guide and you should choose another method.}}

Follow [https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop these] steps to redownload Steel Diver: Sub Wars if available

==Section II: Mii mining==
{{info|text=If you already have your <code>movable.sed</code>, you can skip this section.}}

Because you can't enter a friend code due to the broken keyboard, you'll need to get your console's encryption key a different way. We can accomplish this by Mii mining.

Follow [[3DS:Seedminer/Mii mining|Mii mining]] to extract the <code>movable.sed</code> from your console, but do not continue onto the main guide as it suggests. Come back to this page once you have the movable.

==Section III: Steelhax==
Now that you have your <code>movable.sed</code>, continue to [[3DS:Alternate Exploits/Homebrew Launcher (steelhax)|Homebrew Launcher (steelhax)]].
</span>

|-|Kartminer7 (Mario Kart 7)=

<span>
==Section I: Installing Mario Kart 7==

{{warning|text=If the eShop requires you to use the keyboard, or you cannot install Mario Kart 7 or its 1.2 update, there's no point following the rest of this guide and you should choose another method.}}
{{info|text=If you have a cartridge of Mario Kart 7 and it's the same region as your console, you can skip this section.}}

Follow [https://en-americas-support.nintendo.com/app/answers/detail/a_id/607/~/how-to-download-or-redownload-content-in-nintendo-3ds-eshop these] steps to redownload Mario Kart 7 if available

==Section II: Updating Mario Kart 7==

Follow [https://en-americas-support.nintendo.com/app/answers/detail/a_id/13506/~/how-to-download-software-updates-from-the-home-menu these] steps to update Mario Kart 7

==Section III: Mii mining==
{{info|text=If you already have your <code>movable.sed</code>, you can skip this section.}}

Because you can't enter a friend code due to the broken keyboard, you'll need to get your console's encryption key a different way. We can accomplish this by Mii mining.

Follow [[3DS:Seedminer/Mii mining|Mii mining]] to extract the <code>movable.sed</code> from your console, but do not continue onto the main guide as it suggests. Come back to this page once you have the movable.

==Section IV: Kartminer7==
Now that you have your <code>movable.sed</code>, continue to [[3DS:Alternate Exploits/Preparing menuhax67 (Kartminer7)|preparing menuhax67 (Kartminer7)]].
</span>

</tabber>
</div>

If everything went well, you should end up with boot9strap installed and the keyboard / System Settings should work again.

<center>{{critical|text=Do <big>'''not'''</big> uninstall custom firmware again without guidance. You've now seen first-hand how it can go wrong.}}</center>

[[Category:Unbricking]]
[[Category:Nintendo 3DS guides]]

3DS:File list

2024-12-22T23:31:04Z

ShinyTillDawn: Updated the names of the MSET9 files.

This page lists all files and folders that might be found on a 3DS' SD card, along with their uses.

== Files ==

{| class="wikitable"
|-
!File Name
!Usage
|-
|arm9loaderhax.bin
|The payload chainloaded by arm9loaderhax.
|-
|boot.firm
|The firmware chainloaded by [[3DS:boot9strap|boot9strap]] and [[3DS:fastboot3DS]], usually [[3DS:Luma3DS|Luma3DS]].
|-
|boot.3dsx
|Usually the Homebrew Launcher, which is loaded both by exploits and by Luma3DS' Homebrew Launcher Loader.
|-
|BOOT.NDS/boot.nds
|When all uppercase, a payload for TWiLightMenu++. When all lowercase, usually the B9STool payload that is used in the frogtool/fredtool exploit.
|-
|essentials.exefs
|A backup of all unique system files. Initially created by [[3DS:GodMode9|GodMode9]].
|-
|movable.sed
|The encryption key for all data inside the <code>sd:/Nintendo 3DS</code> folder. Required for various exploits that modify apps/games' savedata.
|-
|safeb9sinstaller.bin
|Boot9strap installer. Identical to the .firm version other than its format.
|-
|}

== Folders ==

{| class="wikitable"
!Folder Name
!Usage
|-
|_nds
|Created automatically by TWiLightMenu++ to store the payloads, data, and config needed for it to play DS games.
|-
|_gba
|Created automatically by TWiLightMenu++ to store the config needed for it to play GBA games.
|-
|3ds
|Contains all <code>.3dsx</code> homebrew applications and their files.
|-
|badges
|Used to install custom badges via [[3DS:GYTB|GYTB]].
|-
|CTGP-7
|Contains all data and config for [[3DS:Mario_Kart_7/CTGP-7|CTGP-7]].
|-
|DCIM
|Contains all photos/videos/screenshots taken by the stock firmware, such as in Nintendo 3DS Camera.
|-
|gm9
|Contains scripts and exported files for GodMode9.
|-
|luma
|Contains configuration for Luma3DS, as well as additional payloads and custom game patches and files.
|-
|Nintendo 3DS
|Contains all digital games/their save files, extra data, DSiWare exports, and the installed theme(s).
|-
|plugin
|Contains all [[3DS:Game plugins/NTR|.plg plugin files]] for use with BootNTR.
|-
|roms
|Optionally created by TWiLightMenu++ to store game ROMs.
|-
|}

== Exploit-Specific Files/Folders ==

{| class="wikitable"
!File/Folder Name
!Usage
|-
|boot9strap
|Contains the boot9strap firm and a hash of it, for use in SafeB9SInstaller.
|-
|browserhax_hblauncher_ropbin_payload.bin
|The payload for super-skaterhax.
|-
|otherapp.bin
|Usually the payload for *hax/universal-otherapp, depending on the specific system version and exploit.
|-
|arm11code.bin
|Usually the payload for browser exploits. Exact contents will depend on the specific system version and exploit.
|-
|Soundhax-<region>-<model>-<version>.m4a
|The exploited sound file for Soundhax. The <region>, <model>, and <version> in the name are replaced with the values matching the specific console.
|-
|mset9-macOS.command
|rowspan="2"|The script file for the mset9 exploit. mset9-macOS.command is for macOS, while mset9-Windows.bat is for Windows.
|-
|mset9-Windows.bat
|-
|}

[[Category:Nintendo 3DS information]]

3DS:Can't Update

2024-11-14T22:16:27Z

ShinyTillDawn: Made a redirect for ''Can't Update'' in title case

#REDIRECT [[3DS:Troubleshooting#Unable_to_update_console]]

3DS:Fcg

2024-10-15T01:01:30Z

ShinyTillDawn: Redirected page to 3DS:Fixing corrupted games

#REDIRECT [[3DS:Fixing corrupted games]]

3DS:Fcg

2024-10-15T00:59:50Z

ShinyTillDawn: Create a redirect to the fixing corrupted games page

<nowiki>#REDIRECT [[3DS:Fixing corrupted games]]</nowiki>