Hacks Guide Wiki - User contributions [en]

3DS:Missing Titles

2025-06-21T18:47:59Z

AE: grammar, spelling fixes

3DS titles can appear to vanish from the HOME Menu for several different reasons. This page provides recommended solutions based on what appears in System Settings → Data Management → Nintendo 3DS → Software.

{{info|text=This issue does not affect anything
installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.}}

== On the 3DS, Going to System Settings → Data Management → Nintendo 3DS → Software results in...==

==='''Titles with gray X's on them:'''===
Install and run [[3DS:Faketik|Faketik]].

==='''A Popup Reading "The microSD/SD card software management information is corrupted. Reset it now?":'''===
If you have any games or saves you'd like to keep, [[3DS:Rebuild title database|rebuild your Title Database]]. If you do not care about your current data, you can hit "Reset", which will erase the contents of your SD Card, rendering your current games and saves unplayable, and you can reinstall your apps afterwards.

==='''A Popup Reading "There is no available software data" and/or your installed custom theme is gone:'''===
Your SD Card is not being read by your console. Ensure it is properly inserted into the console. If it is, backup the contents of your SD Card to a computer or phone, [[Formatting an SD card|reformat the SD Card]], then [[Checking SD card integrity|test its integrity]].

==='''Question marks or black boxes where game icons should be:'''===
Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Titles Appear Listed Normally, But are Still Missing from Home Menu''':===
==== If this occurred after installing 300+ 3DS titles:====
Delete some games from the <code>Data Management</code> screen until you’re under 300 titles.
====If this occurred and you have less than 300 titles installed:====
Install and run [[3DS:Gm9-title-fixer|Chalenged's gm9 title fixer]].

*If you run into any issues with the above option, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and mention that you've tried to use the title fixer script.

*Alternatively, you can manually generate a file that describes the contents of your SD, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord], and send it in the <code>#bot-cmds</code> channel for further instructions. To generate this file, you will need a Windows computer and a way to access your SD on said computer. Follow the instructions below:

#Insert your 3DS's SD card into your computer
#Navigate to the <code>Nintendo 3DS/<ID0>/<ID1>/title</code> folder on your SD
#*The ID0 and ID1 are long 32-character folders inside your <code>Nintendo 3DS</code> folder. For more help navigating your SD Card's contents, consult the [https://3ds.hacks.guide/key-information.html Key Information] Section of the 3DS Guide.
#Hold Shift and right-click on the empty space of the folder
#Click on Open Command Prompt/Terminal/Powershell, depending on which ones appear
#Type <code>tree /a /f > title.txt</code> into the terminal and then press Enter
#Close the terminal
# Upload <code>title.txt</code> to the <code>#bot-cmds</code> channel of the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and follow its recommendations

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

3DS:Missing Titles

2025-06-07T00:57:45Z

AE: Clarifications and formatting

This page lists multiple examples of 3DS titles disappearing from the 3DS Home Screen and provides recommended solutions.
{{info|text=This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.}}

== On the 3DS, Going to System Settings → Data Management → Nintendo 3DS → Software results in...==

==='''Titles with gray X's on them:'''===
Install and run [[3DS:Faketik|Faketik]].

==='''"The microSD/SD card software management information is corrupted. Reset it now?" message''':===
If you have any games or saves you'd like to keep, [[3DS:Rebuild title database|rebuild your Title Database]]. If you do not care about your current data, you can hit "Reset", which will erase the contents of your SD Card, rendering your current games and saves unplayable, and you can reinstall your apps afterwards.

==='''"There is no available software data" message and/or installed custom theme is gone:'''===
Your SD Card is not being read by your console. Ensure it is properly inserted into the console; if it is, backup the contents of your SD Card to a computer or phone, [[Formatting an SD card|reformat the SD Card]], then [[Checking SD card integrity|test its integrity]].

==='''Question marks or black boxes where game icons should be:'''===
Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Titles Appear Listed Normally, But are Still Missing from Home Menu''':===
==== If this occurred after installing 300+ 3DS titles:====
Delete some games from the <code>Data Management</code> screen until you’re under 300 titles.
====If this occurred and you have less than 300 titles installed:====
Install and run [https://github.com/chalenged/gm9-title-fixer Chalenged's gm9 title fixer] per [[3DS:Gm9-title-fixer|their guide]].

*If you run into any issues with the above option, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and mention that you've tried to use the title fixer script.

*Alternatively, you can manually generate a file that describes the contents of your SD, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord], and send it in the <code>#bot-cmds</code> channel for further instructions. To generate the file, you will need a Windows computer, and a way to access your SD on said computer. Follow the instructions below:

#Insert your 3DS's SD card into your computer
#Navigate to the <code>Nintendo 3DS/<ID0>/<ID1>/title</code> folder on your SD
#*The ID0 and ID1 are long 32-character folders inside your <code>Nintendo 3DS</code> folder. For more help navigating your SD Card's contents, consult the [https://3ds.hacks.guide/key-information.html Key Information] Section of the 3DS Guide.
#Hold Shift and right click on the empty space of the folder
#Click on Open Command Prompt/Terminal/Powershell, depending on which ones appear
#Type <code>tree /a /f > title.txt</code> into the terminal and then press Enter
#Close the terminal
# Upload the title.txt file into <code>#bot-cmds</code> channel of the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and follow its recommendations.

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

3DS:Missing Titles

2025-06-03T05:15:51Z

AE: Updated GM9 Title Fixer link. Formatting fixes.

=3DS Titles Disappeared From Home Menu=

This page lists multiple examples of 3DS titles disappearing from the 3DS Home Screen and provides recommended solutions.
{{info|text=This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.}}

==On the 3DS, Going to System Settings → Data Management → Nintendo 3DS → Software results in...==

==='''Titles with gray X's on them:'''===
Install and run [[3DS:Faketik|Faketik]].

==='''"The microSD/SD card software management information is corrupted. Reset it now?" message''':===
If you have any games or saves you'd like to keep, [[3DS:Rebuild title database|rebuild your Title Database]]. If you do not care about your current data, you can hit "Reset", which will erase the contents of your SD Card, rendering your current games and saves unplayable, and you can reinstall your apps afterwards.

==='''"There is no available software data" message and/or installed custom theme is gone:'''===
Your SD Card is not being read by your console. Ensure it is properly inserted into the console; if it is, backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Question marks or black boxes where game icons should be:'''===
Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Titles Appear Listed Normally, But are Still Missing from Home Menu''':===
====If this occurred after installing 300+ 3DS titles:====
Delete some games from the <code>Data Management</code> screen until you’re under 300 titles.
====If this occurred and you have less than 300 titles installed:====
Install and run [https://github.com/chalenged/gm9-title-fixer Chalenged's gm9 title fixer] per [[3DS:Gm9-title-fixer|their guide]].

*If you run into any issues with the above option, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and mention that you've tried to use the title fixer script.

*Alternatively, you can manually generate a file that describes the contents of your SD, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord], and send it in the <code>#bot-cmds</code> channel for further instructions. To generate the file, you will need a Windows computer, and a way to access your SD on said computer. Follow the instructions below:

##Insert your 3DS's SD card into your computer
##Open the <code>Nintendo 3DS</code> folder on your SD
##Open the folder with a long name (32 characters)
##Open the second folder with a long name (also 32 characters)
##Open the <code>title</code> folder
##Hold Shift and right click on the empty space of the folder
##Click on Open Command Prompt/Terminal/Powershell, depending on which ones appear
##Type <code>tree /a /f > title.txt</code> into the terminal and then press Enter
##Close the terminal
##Upload the title.txt file into <code>#bot-cmds</code> channel of the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and follow its recommendations.

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

3DS:Missing Titles

2025-06-03T00:46:06Z

AE: Migrated everything from user page. eliminated reference to being able to use Mac/Linux. included steps for Windows bot command usage.

=3DS Titles Disappeared From Home Menu=

This page lists multiple examples of 3DS titles disappearing from the 3DS Home Screen and provides recommended solutions.
{{info|text=This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.}}

==On the 3DS, Going to System Settings → Data Management → Nintendo 3DS → Software results in...==

==='''Titles with gray X's on them:'''===
Install and run [[3DS:Faketik|Faketik]].

==='''"The microSD/SD card software management information is corrupted. Reset it now?" message''':===
If you have any games or saves you'd like to keep, [[3DS:Rebuild title database|rebuild your Title Database]]. If you do not care about your current data, you can hit "Reset", which will erase the contents of your SD Card, rendering your current games and saves unplayable, and you can reinstall your apps afterwards.

==='''"There is no available software data" message and/or installed custom theme is gone:'''===
Your SD Card is not being read by your console. Ensure it is properly inserted into the console; if it is, backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Question marks or black boxes where game icons should be:'''===
Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Titles Appear Listed Normally, But are Still Missing from Home Menu''':===
====If this occurred after installing 300+ 3DS titles:====
Delete some games from the <code>Data Management</code> screen until you’re under 300 titles.
====If this occurred and you have less than 300 titles installed:====
Install and run [https://github.com/chalenged/gm9-title-fixer Chalenged's gm9 title fixer] per [[User:Chalenged/sandbox|their guide]].

*If you run into any issues with the above option, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and mention that you've tried to use the title fixer script.

*Alternatively, you can manually generate a file that describes the contents of your SD, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord], and send it in the <code>#bot-cmds</code> channel for further instructions. To generate the file, you will need a Windows computer, and a way to access your SD on said computer. Follow the instructions below:

#Insert your SD card into your computer
#Open the Nintendo 3DS folder on your SD
#Open the folder with a long name (32 characters)
#Open the second folder with a long name (also 32 characters)
#Open the title folder
#Hold Shift and right click on the empty space of the folder
#Click on Open Command Prompt/Terminal/Powershell, depending on which ones appear
#Type <code>tree /a /f > title.txt</code> into the terminal and then press Enter
#Close the terminal
#Upload the title.txt file into #bot-cmds channel of the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and follow its recommendations.

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

User:AE/MissingTitles

2025-05-30T05:32:31Z

AE: Reorganized to provide more coherent flow with the discord bot command as the last option. cleaned up text.

=3DS Titles Disappeared From Home Menu=

This page lists multiple examples of 3DS titles dissappearing from the 3DS Home Screen and provides recommended solutions.
{{info|text=This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.}}

==On the 3DS, Going to System Settings → Data Management → Nintendo 3DS → Software results in...==

==='''Titles with gray X's on them:''' ===
Install and run [[3DS:Faketik|Faketik]].

==='''"The microSD/SD card software management information is corrupted. Reset it now?" message''':===
If you have any games or saves you'd like to keep, [[3DS:Rebuild title database|rebuild your Title Database]]. If you do not care about your current data, you can hit "Reset", which will erase the contents of your SD Card, rendering your current games and saves unplayable, and you can reinstall your apps afterwards.

=== '''"There is no available software data" message and/or installed custom theme is gone:'''===
Your SD Card is not being read by your console. Ensure it is properly inserted into the console; if it is, backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Question marks or black boxes where game icons should be:'''===
Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

==='''Titles Appear Listed Normally, But are Still Missing from Home Menu''': ===
====If this occurred after installing 300+ 3DS titles:====
Delete some games from the <code>Data Management</code> screen until you’re under 300 titles.
====If this occurred and you have less than 300 titles installed:====
Install and run [https://github.com/chalenged/gm9-title-fixer Chalenged's gm9 title fixer] per [[User:Chalenged/sandbox|their guide]].

*If you run into any issues with the above option, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and mention that you've tried to use the title fixer script.

* Alternatively, you can manually generate a file that describes the contents of your SD, join the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord], and send it in the #bot-cmds channel for further instructions. To generate the file, you will need a Windows/Linux/Mac computer, and a way to access your SD on said computer. If you wish to follow this route, choose your operating system below. (WIP){{OS selector|w=1|l=1|m=1}}
{{info|text=When the 3DS finds missing or corrupted data in the titles folder, it refuses to load the whole folder. The gm9 script and discord command serve to identify the corrupted or missing data. The file the bot asks you to upload, 'title.txt', is a list of all the files and folders in the titles folder. The bot looks for any folders that are missing files so the user may delete them, which should bring everything back. However, the title in question is inaccessible and needs to be reinstalled.}}

3DS:Error screens/Luma3DS ErrDisp

2025-05-28T00:03:54Z

AE: re-added previous edit from 2025-05-25

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
|process: '''gsp'''
|Your system software is having a strange issue
:If the error code is <code>0xf8a02bfe</code>, your console is a "New" model, and it only appears when waking from sleep mode, to fix, perform a hard reset. Hold down {{B|ABXY}} and {{B|Up}} on the D-pad while powering on the device.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Some piece(s) of hardware related to power or the battery is damaged.
:First, check if your console's charging LED (the orange one) repeatedly turns on and off on its own while a cable is inserted. If it does, this is a sign of a faulty charger port, which may be contributing to the errors and should be fixed before any other troubleshooting.
:Once the charger port is verified intact, any other causes are likely deeper within the motherboard. Dissassembling and carefully analyzing the console will likely be necessary to find these issues, and even then, they may not be practical to fix.
|-
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 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 may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>[A:] SYSNAND SD/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, 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.
|-
|0xD963F99C
|Displayed after selecting <code>UPDATE</code> in [[3DS:FBI|FBI]].
:To fix, follow [[3DS:FBI|FBI]] to update
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

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

User talk:Gruetzig

2025-05-27T19:31:09Z

AE: Created page with "Hello. I saw you reverted one of my changes. I was hoping to get some constructive feedback so I can be better at editing in the future. ~~~~"

Hello. I saw you [[Special:MobileDiff/7580|reverted]] one of my changes. I was hoping to get some constructive feedback so I can be better at editing in the future. [[User:AE|AE]] ([[User talk:AE|talk]]) 19:31, 27 May 2025 (UTC)

3DS:Emulators

2025-05-25T19:24:29Z

AE: /* Emulating the 3DS itself */ added Azahar

{{hatnote|3DS:EMU redirects here. For EmuNAND, see [[3DS:EmuNAND and RedNAND]].}}

An '''emulator''' is a piece of software that uses computing power to simulate another device, such as a video game console or a personal computer. As a general guideline, the original Nintendo 3DS is capable of emulating most popular home consoles up to around the {{iw|wikipedia|fourth generation of video game consoles}} (the SNES/Genesis era), while the New Nintendo 3DS series is (just barely) capable of emulating some of the {{iw|wikipedia|fifth generation of video game consoles|fifth generation}} (the N64/PS1 era).
<br>This is because emulation requires significantly more computing power than running the console natively - though even if it could run emulated games as efficiently as native playback, even a new model 3DS would still only be able to emulate the {{iw|wikipedia|sixth generation of video game consoles|sixth generation}} (the Xbox/PS2/Dreamcast era) and possibly the Wii.

The Nintendo 3DS has hardware that allows for native backwards compatibility with the Nintendo DS and Game Boy Advance, meaning such software can run at full speed as they would on the original hardware. While this is not actually emulation, methods that use this hardware will be included here due to the ubiquity of the term.

== Handheld video game consoles ==

=== Nintendo DS ===
{{Main|3DS:DS games}}

Nintendo DS software can be played natively using nds-bootstrap, a tool that allows NDS backups to be run from the SD card. In most cases, you will use either TWiLight Menu++ or NDS forwarders to launch the ROM, after which nds-bootstrap will do the hard work of getting it to run.

In the past, Nintendo DS flashcarts were a popular way to run Nintendo DS software. Because of nds-bootstrap's development over the years, they have become less and less necessary, but can still offer useful features like being able to use the flashcart on unmodded 3DS-family and DS-family consoles (depending on the cartridge).

=== Game Boy Advance ===
{{Main|3DS:GBA games}}

Game Boy Advance software can be played natively by leveraging AGB_FIRM, something built into every 3DS that allows for native playback of Game Boy Advance software. AGB_FIRM was only ever used officially as part of the Ambassador Program for early purchasers of the original Nintendo 3DS before its price was cut.

The current recommended way to run GBA software is [[3DS:open_agb_firm|open_agb_firm]] due to its drag-and-drop functionality and ease of save file access. open_agb_firm runs as a payload (similar to GodMode9), meaning it is not directly accessible from HOME Menu (requiring a reboot to enter/exit) unless an alternate bootloader such as [[3DS:fastboot3DS|fastboot3DS]] is combined with [https://gbatemp.net/download/open-agb-launcher.36828/ Open AGB Launcher].<br>
If you want to use another method but still want icons directly on your HOME Menu, you can [[3DS:Virtual Console/Creation|create Virtual Console injects]] on a Windows device.

GBA games can also be emulated, the recommended emulator being [[udb:3ds/mgba|mGBA]]. This is the best option if you wish to use cheats and save-states, but performance will rarely be full-speed on old models and some games will not work correctly.

GBARunner2 is a middle ground between native playback and emulation, similar to Nintendont on the Wii - this means it has none of the emulator features and the reduced compatibility of an emulator.<br>
It is included with TWiLightMenu++ (which you may already be using for NDS software), but because of the other options available, it isn't recommended.

=== Game Boy Color / Game Boy ===
The Game Boy Color and Game Boy are old enough that all models of the 3DS (and even the DS) can run them at full speed. The historically popular GB(C) emulator has been [[udb:3ds/gameyob-3ds|GameYob]], but due to 3DS-specific issues the [[udb:ds/gameyob|DS version]] is preferred (ran through TWiLight Menu++).<br>
You can also [[3DS:Virtual Console/Creation|create Virtual Console injects]] for GB/GBC games if you prefer to play your games from the HOME Menu.

The multi-platform GB(C) emulator [https://github.com/RossMeikleham/PlutoBoy/actions PlutoBoy] is currently under active development. A GitHub account is required to download the automated builds.

=== Virtual Boy ===
Possible with [[udb:3ds/red-viper|Red Viper]].

=== WonderSwan ===
Possible through the Mednafen (WonderSwan) core on [[3DS:RetroArch|RetroArch]]. Performance has been reported to be slow on Old 3DS units.

== Home video game consoles ==

=== PlayStation 1 ===
Possible through the PCSX ReARMed core on [[3DS:RetroArch|RetroArch]], with playable speeds on '''New 3DS only'''. A partial compatibility list can be found [https://docs.google.com/spreadsheets/d/1pl2bTkzTe736EOaQjk8FBWY9ixfgoNSYSitbm5Gnyqs/edit#gid=0 here], and optimal configuration can be found [https://www.reddit.com/r/3dshacks/comments/jvkotb/full_speed_psx_finally_here_on_new_3ds_new_2ds_xl/ here].

=== Nintendo 64 ===
''Barely'' possible on '''New 3DS only''' through [[udb:3ds/daedalusx64-3ds|DaedalusX64-3DS]]. A partial compatibility list can be found [https://wiki.gbatemp.net/wiki/DaedalusX64_3DS_Compatibility_List here]; most games are incompatible or run very slowly.

=== Super NES ===
Possible on both Old and New 3DS using [[udb:3ds/snes9x|Snes9x]], which is optimized so that many SNES games can run well on an Old 3DS. There is also an {{GitHub|matbo87/snes9x_3ds/releases/latest|updated Snes9x fork}} that has extra features such as custom game borders, the ability to play on either screen, an improved cheat menu and more. Additionally, New 3DS users can create [[3DS:Virtual_Console/Creation|Virtual Console injects]] that use Nintendo's official SNES emulator.
===TurboGrafx-16 (PC Engine)===
Possible through [[udb:3ds/temperpce|TemperPCE]], as well as being possible through [[3DS:Virtual Console/Creation|Virtual Console injects]].

=== NES / Famicom Disk System ===
The NES is old enough that all models of the 3DS can run it at full speed. The recommended emulator is [[udb:3ds/virtuanes|VirtuaNES]].<br>
you can also [[3DS:Virtual Console/Creation|create Virtual Console injects]] if you prefer to play your games from the home menu.

=== Sega Genesis / CD / 32X / Master System ===
Possible through [[udb:3ds/picodrive|PicoDrive]], covering the Genesis / Mega Drive and its add-ons (the Sega CD and 32X) as well as the Sega Master System. It is apparently reasonably well-optimized for Old 3DS.

== Arcade cabinets ==
WIP

== Home computers ==

=== DOS / Win9x ===
Possible through {{GitHub|MrHuu/dosbox-3ds/releases/latest|DOSBox-3DS}}. Tested mostly on New 3DS. Windows 3.1 and 95 technically ''work'', albeit extremely slowly; this emulator is much more practical for older DOS games.

=== Commodore 64 ===
Possible through [[udb:3ds/vice3ds|Vice3DS]].

=== Amiga 500 ===
Possible through [[udb:3ds/uae3ds|uae3DS]].

== Other ==

=== Calculators ===
''Omega'', a custom firmware for the Numworks graphing calculator, has a simulator available for the Nintendo 3DS. The latest available version (as of 2022/08/09) is available {{GitHub|Omega-Numworks/Omega/releases/download/O1.23.0-E15/simulator.3dsx|here}}.

[https://gbatemp.net/download/wabbitds.7859/ WabbitDS] is a TI-83 Plus emulator for the Nintendo DS. It ''might'' work on the 3DS under TWiLight Menu++ or through a DS flashcart.

== Overview chart ==
WIP

== Emulators that don't exist ==

These are consoles or devices that will not work on the 3DS, usually due to computing power requirements.

* GameCube/Wii/Wii U/Switch
* PlayStation 2 and newer
* PlayStation Portable and Vita
* All Xbox consoles
* Dreamcast
* Windows NT (XP/Vista/7/etc)

== Emulating the 3DS itself ==

To emulate the 3DS on another platform, Citra is the recommended option.<ref group=Note name=Note01>Citra's website and github repos have been taken down by the owners due to legal action against Yuzu (owned by the same entity) by Nintendo.</ref> Other options include [https://azahar-emu.org Azahar], [https://mikage.app Mikage], and [https://github.com/wheremyfoodat/Panda3DS Panda3DS].

== Notes ==
<references group="Note"/>

[[Category:Nintendo 3DS information]]

3DS:Error screens/Luma3DS ErrDisp

2025-05-25T18:41:13Z

AE: Added 0xD963F99C for failure to update FBI.

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Some piece(s) of hardware related to power or the battery is damaged.
:First, check if your console's charging LED (the orange one) repeatedly turns on and off on its own while a cable is inserted. If it does, this is a sign of a faulty charger port, which may be contributing to the errors and should be fixed before any other troubleshooting.
:Once the charger port is verified intact, any other causes are likely deeper within the motherboard. Dissassembling and carefully analyzing the console will likely be necessary to find these issues, and even then, they may not be practical to fix.
|-
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 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 may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>[A:] SYSNAND SD/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, 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.
|-
|0xD963F99C
|Displayed after selecting <code>UPDATE</code> in [[3DS:FBI|FBI]].
:To fix, follow [[3DS:FBI|FBI]] to update
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

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

3DS:Error screens/Luma3DS ErrDisp

2025-05-25T18:27:33Z

AE: Added error and solution for the `gsp` error with code `0xf8a02bfe` only appears in "New" model consoles, and only when waking up from sleep mode. Perform a hard reset using a button combo: hold down ABXY + Up while Powering the device. Source: https://www.reddit.com/r/3dspiracy/s/XRyyyMvs7g

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
|process: gsp
|Your system software is having a strange issue
:If the error code is <code>0xf8a02bfe</code>, your console is a "New" model, and it only appears when waking from sleep mode, to fix, perform a hard reset. Hold down {{B|ABXY}} and {{B|Up}} on the D-pad while powering on the device.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Some piece(s) of hardware related to power or the battery is damaged.
:First, check if your console's charging LED (the orange one) repeatedly turns on and off on its own while a cable is inserted. If it does, this is a sign of a faulty charger port, which may be contributing to the errors and should be fixed before any other troubleshooting.
:Once the charger port is verified intact, any other causes are likely deeper within the motherboard. Dissassembling and carefully analyzing the console will likely be necessary to find these issues, and even then, they may not be practical to fix.
|-
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 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 may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>[A:] SYSNAND SD/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, 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.
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

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

3DS:Error screens/Luma3DS exception screen

2025-05-25T18:06:04Z

AE: Added alternative suggestion for: Update `Arm9→Error during use→data abort` to also say that if it’s just 1 app that causes the crash, the app probably corrupted and to delete and reinstall it.

{{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 [https://discord.gg/C29hYvh 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>
* If just 1 app causes the crash, it is likely corrupted. Delete the app in the 3DS's <code>System Settings</code> → <code>Data Management</code>, then reinstall.
* If multiple apps crash, files on the SD are corrupted.
** To fix, [[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 [https://discord.gg/C29hYvh 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 [https://discord.gg/C29hYvh Nintendo Homebrew Discord] or the [https://discord.gg/CAuZuqZRTw 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 [https://discord.gg/nintendohomebrew 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 [https://discord.gg/C29hYvh 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.
** [[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 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 [https://discord.gg/nintendohomebrew 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 [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

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

User:AE/MissingTitles

2025-05-25T16:25:59Z

AE: reformatting

User:AE/MissingTitles

2025-05-24T22:00:11Z

AE: reformatted, added info for 300+titles

=3DS Titles disappeared from Home Menu=
This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.

=== On the 3DS, Going to System Settings → Data Management results in... ===

==== '''Titles with gray X's on them:''' ====
*install and run [[3DS:Faketik|Faketik]].

==== '''Titles appear listed normally, but still missing from Home Menu''': ====
*If this occurred after installing 300+ titles, delete some games form the <code>Data Management</code> screen until you’re under 300 titles.
*If this occurred and you have less than 300 titles installed, use [https://github.com/chalenged/gm9-title-fixer Chalanged's gm9 title fixer] per [[User:Chalenged/sandbox|their guide]] or go to the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and use the <code>.tag missingtitles</code> command. Follow along as instructed.
When the 3DS finds missing or corrupted data in the titles folder, it refuses to load the whole folder. the easy solution is to remove said missing or corrupted data. the hard part is finding the data. The gm9 script and the discord command do just that. The file the bot asks you to upload, 'title.txt', is a list of all the files and folders in the titles folder. this allows the bot to look for any folders that are missing files so you may delete them, which usually brings everything back. However, the title in question is presumably inaccessible and needs to be reinstalled.

==== '''Error Message asking to reset''': ====
*[[3DS:Rebuild title database|rebuild your Title Database]].

==== '''A bunch of question marks or black boxes, or data management is empty and your theme is gone''': ====
*Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [[3ds-guide:formatting-sd-(windows)|reformat the SD Card]], then [[3ds-guide:h2testw-(windows).html|test its integrity]].

User:AE/MissingTitles

2025-05-24T20:19:26Z

AE: Added link to chalenge’s gm9 wiki page and minor fixes

=3DS Titles disappeared from Home Menu=
<blockquote>Note: This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.</blockquote>
==On the 3DS, Go to `System Settings → Data Management` results in...==
*'''Titles with gray X's on them:''' install and run [[3DS:Faketik|Faketik]]
*'''Titles appear listed normally, but still missing from Home Menu''': use [https://github.com/chalenged/gm9-title-fixer Chalanged's gm9 title fixer] per [[User:Chalenged/sandbox|their guide]] or go to the [https://discord.gg/MWxPgEp Nintendo Homebrew Discord] and use the `.tag missingtitles` command. Follow along as instructed.<blockquote>Note: When the 3DS finds missing or corrupted data in the titles folder, it refuses to load the whole folder. the easy solution is to remove said missing or corrupted data. the hard part is finding the data. The gm9 script and the discord command do just that. The file the bot asks you to upload, 'title.txt', is a list of all the files and folders in the titles folder. this allows the bot to look for any folders that are missing files so you may delete them, which usually brings everything back. However, the title in question is presumably inaccessible and needs to be reinstalled.</blockquote>
*'''Error Message asking to reset''': [[3DS:Rebuild title database|rebuild your Title Database]].
*'''A bunch of question marks or black boxes, or data management is empty and your theme is gone''': Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [https://3ds.hacks.guide/formatting-sd-(windows) reformat the SD Card], then [https://3ds.hacks.guide/h2testw-(windows).html test its integrity].

User:AE/sandbox

2025-05-24T19:57:36Z

AE: Moved everything to https://wiki.hacks.guide/wiki/User:AE/MissingTitles

null

User:AE/MissingTitles

2025-05-24T19:52:00Z

AE: Pulled from user sandbox

=3DS Titles disappeared from Home Menu=
<blockquote>Note: This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.</blockquote>
==On the 3DS, Go to `System Settings → Data Management` results in...==
*Titles with gray X's on them, install and run [[3DS:Faketik|Faketik]]
*Titles appear listed normally, but still missing from Home Menu: use [https://github.com/chalenged/gm9-title-fixer Chalanged's gm9 title fixer] or go to the [https://discord.gg/MWxPgEp Official Nintendo Homebrew Discord] and use the `.tag missingtitles` command. Follow along as instructed.<blockquote>Note: When the 3DS finds missing or corrupted data in the titles folder, it refuses to load the whole folder. the easy solution is to remove said missing or corrupted data. the hard part is finding the data. The gm9 script and the discord command do just that. The `title.txt` looks for any folders that are missing files and tells the user to delete them, which usually brings everything back. However, the title in question is presumably inaccessible and needs to be reinstalled.</blockquote>
*Error Message asking to reset: [[3DS:Rebuild title database|rebuild your Title Database]].
*A bunch of question marks or black boxes, or data management is empty and your theme is gone: Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [https://3ds.hacks.guide/formatting-sd-(windows) reformat the SD Card], then [https://3ds.hacks.guide/h2testw-(windows).html test its integrity].

User:AE/sandbox

2025-05-24T19:37:35Z

AE: fixing formatting

=3DS Titles disappeared from Home Menu=
<blockquote>Note: This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.</blockquote>
==On the 3DS, Go to `System Settings → Data Management` results in...==
*Titles with gray X's on them, install and run [[3DS:Faketik|Faketik]]
*Titles appear listed normally, but still missing from Home Menu: use [https://github.com/chalenged/gm9-title-fixer Chalanged's gm9 title fixer] or go to the [https://discord.gg/MWxPgEp Official Nintendo Homebrew Discord] and use the `.tag missingtitles` command. Follow along as instructed.<blockquote>Note: When the 3DS finds missing or corrupted data in the titles folder, it refuses to load the whole folder. the easy solution is to remove said missing or corrupted data. the hard part is finding the data. The gm9 script and the discord command do just that. The `title.txt` looks for any folders that are missing files and tells the user to delete them, which usually brings everything back. However, the title in question is presumably inaccessible and needs to be reinstalled.</blockquote>
*Error Message asking to reset: [[3DS:Rebuild title database|rebuild your Title Database]].
*A bunch of question marks or black boxes, or data management is empty and your theme is gone: Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, [https://3ds.hacks.guide/formatting-sd-(windows) reformat the SD Card], then [https://3ds.hacks.guide/h2testw-(windows).html test its integrity].

User:AE/sandbox

2025-05-24T19:24:56Z

AE: first draft of "3DS Titles Disappeared from Home Menu"

=3DS Titles disappeared from Home Menu=
<blockquote>Note: This issue does not affect anything installed as DSiWare, including TwilightMenu++ and games forwarded via nds-forwarder.</blockquote>
==On the 3DS, Go to `System Settings → Data Management` results in...==
*Titles with gray X's on them, install and run #REDIRECT [[3DS:Faketik|Faketik]]
*Titles appear listed normally, but still missing from Home Menu: use Chalanged's gm9 title fixer https://github.com/chalenged/gm9-title-fixer or go to the Official Nintendo Discord https://discord.gg/MWxPgEp and use the `.tag missingtitles` command. Follow along as instructed.<blockquote>Note: When the 3DS finds missing or corrupted data in the titles folder, it refuses to load the whole folder. the easy solution is to remove said missing or corrupted data. the hard part is finding the data. The gm9 script and the discord command do just that. The `title.txt` looks for any folders that are missing files and tells the user to delete them, which usually brings everything back. However, the title in question is presumably inaccessible and needs to be reinstalled.</blockquote>
*Error Message asking to reset: rebuild your Title Database according to this guide https://wiki.hacks.guide/wiki/3DS:Rebuild_Title_Database.
*A bunch of question marks or black boxes, or data management is empty and your theme is gone: Your SD Card is likely corrupted. Backup the contents of your SD Card to a computer or phone, reformat https://3ds.hacks.guide/formatting-sd-(windows) the SD Card, then test its integrity with h2testw https://3ds.hacks.guide/h2testw-(windows).html)

*

User:AE/sandbox

2025-05-24T19:01:05Z

AE: Page creation

Test 2

User:AE

2025-05-24T18:58:15Z

AE: Created page with "test"

test