|
|
| (16 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| {{#approvable_by: users = ItsCrocoSwine}}<!-- this should be removed if moved out of userspace -->
| | =Luma3DS Error Toolkit= |
| =Key information=
| |
|
| |
|
| This page lists possible causes and fixes of Luma3DS exception screens, ErrDisp screens, stock error codes, and bootROM errors. They are not applicable to every situation, but cover most common known issues.
| | On both stock and custom firmware, apps can cause errors if they run into a non-fatal issue. |
|
| |
|
| In the following lists, 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 [[3DS:GodMode9|GodMode9's]] drive numbers. | | This page lists possible causes and fixes of Luma3DS exception screens, ErrDisp screens, and stock error codes. They are not applicable to every situation, but cover most common known issues. |
| | |
| | In the following lists, 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. |
|
| |
|
| 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. | | 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. |
|
| |
| On both stock and custom firmware, apps can cause '''error codes''' if they run into a non-fatal issue.<br>
| |
| In the below tables, error codes are separated into sets by their section (e.g. 007-XXXX) and then sorted within their sets in ascending order by their result code (e.g. XXX-2001).
| |
|
| |
|
| {{info|Not all 3DS error codes are known or understood, and it is unlikely all codes will ever be documented in full due to Nintendo failing to document many of them.}} | | {{info|Not all 3DS error codes are known or understood, and it is unlikely all codes will ever be documented in full due to Nintendo failing to document many of them.}} |
|
| |
|
| {{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] for further assistance.}} | | {{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [[https://discord.gg/nintendohomebrew Nintendo Homebrew Discord]] for further assistance.}} |
|
| |
|
| =Known errors= | | ==Known errors== |
|
| |
|
| ---- | | ---- |
| Line 40: |
Line 38: |
| |- | | |- |
| | System titles have been deleted. | | | System titles have been deleted. |
| :To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. | | :To fix, perform a [[3DS:Safe Mode|Safe Mode update]].<br>If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]]. |
| ::If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].
| |
| |- | | |- |
| | rowspan="3" | prefetch abort (svcBreak) | | | rowspan="2" | prefetch abort (svcBreak) |
| | The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes. | | | 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. | | :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. |
| Line 49: |
Line 46: |
| | <code>SYSNAND CTRNAND</code> has bad CMACs. | | | <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. | | :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 fixes worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].
| |
| |- | | |- |
| | prefetch abort (kernel panic) | | | prefetch abort (kernel panic) |
| Line 66: |
Line 61: |
| | data abort | | | data abort |
| | Files on the SD are corrupted. | | | 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 again. | | :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. |
| |} | | |} |
|
| |
|
| Line 76: |
Line 71: |
| ! style="font-size:125%;" | Exception Type | | ! style="font-size:125%;" | Exception Type |
| ! style="font-size:125%;" | Problem & Solution | | ! style="font-size:125%;" | Problem & Solution |
| |-
| |
| | act || any
| |
| | 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 [[3DS:Luma3DS/Configuration|the Luma 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]].
| |
| |- | | |- |
| | boss || data abort | | | boss || data abort |
| | The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]]. | | | The current firmware version is 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.]] | | :If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]] |
| |-
| |
| | camera || any
| |
| | 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.
| |
| |-
| |
| | cfg || any
| |
| | 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]], 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.
| |
| |- | | |- |
| | fs || any | | | fs || any |
| | Can be anything from SD card problems to hardware issues. | | | Can be anything from SD card problems to hardware issues. |
| : [[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]]. | | : [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]], [[Formatting an SD card|formatting your SD card]], and/or [[Checking SD card integrity|testing your SD for errors]]. |
| |- | | |- |
| | hid || any | | | hid || any |
| | Potential hardware problems, or an instance of rehid is crashing. | | | Potential hardware problems, or an outdated version of Rehid. |
| : 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>. | | : First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. If these dont exist, or you've never downloaded Rehid, it's likely hardware issues. |
| :: 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.
| | :: [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation. |
| :: 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.
| |
| |- | | |- |
| | i2c, gsp, mcu, pxi, spi || any | | | ic2, spi || any |
| | The console has a serious hardware issue that likely is not easily fixable. | | | The console has a serious hardware issue that likely is not easily fixable. |
| :Run [[3DS:Hardware test|3ds_hw_test]]. | | :Join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help. |
| ::If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.
| | |- |
| |- | | |- |
| | mset || any | | | mset || any |
| Line 117: |
Line 95: |
| ::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. | | ::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. |
| |- | | |- |
| | rowspan="6" | menu | | | rowspan="5" | menu |
| | rowspan="3" | data abort | | | rowspan="3" | data abort |
| | Broken HOME Menu theme. | | | Broken HOME Menu theme. |
| Line 131: |
Line 109: |
| |- | | |- |
| | prefetch abort | | | prefetch abort |
| | An installation of Menuhax is conflicting with the custom firmware. | | | An installation of menuhax is conflicting with the custom firmware. |
| :To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]]. | | :To fix, place the <code>menuhax67_installer.3dsx</code> file from [[https://github.com/zoogie/menuhax67/releases/download/v1.1/menuhax67_v1.1.zip this download]] into <code>sd:/3ds</code>, run it through Homebrew Launcher, and choose REMOVE. |
| ::If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma 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.
| |
| |- | | |- |
| | rowspan="2" | prefetch abort (svcBreak)
| | | prefetch abort (svcBreak) |
| | 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>. | | | 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. | | :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, you could try restoring it instead with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]
| |
| |- | | |- |
| | ns || prefetch abort (svcBreak) | | | ns || prefetch abort (svcBreak) |
| | The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist. | | | The [[3DS:Luma3DS/Configuration|Luma configuration]] setting <code>Autoboot Homebrew</code> 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. | | :To fix, disable the option or install an application that matches the title ID set in <code>sd:/luma/config.ini</code>. |
| |- | | |- |
| | nwm || any | | | nwm || any |
| | The WiFi chipset's hardware is damaged or dead. | | | 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. | | :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. | | ::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. |
| |- | | |- |
| | pm || undefined instruction | | | pm || undefined instruction |
| Line 165: |
Line 138: |
| |- | | |- |
| | 3dsx_app || any | | | 3dsx_app || any |
| | The <code>.3dsx</code> file that was most recently opened is corrupted. | | | The <code>.3dsx</code> file you 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>. | | :To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when you open 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.]] | | ::If the error still happens, [[Checking SD card integrity|test your SD for errors.]] |
| |- | | |- |
| | rowspan=2 | app<br>CtrApp
| | | app<br>CtrApp || any |
| | prefetch abort (svcbreak)
| | | The app you last opened is trying to use broken software. |
| | The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.
| |
| |-
| |
| | any other process | |
| | The app most recently opened is trying to use broken software. | |
| :To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. | | :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 is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, 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 still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, 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. |
| Line 185: |
Line 154: |
| | fs || any | | | fs || any |
| | Can be anything from SD card problems to hardware issues. | | | Can be anything from SD card problems to hardware issues. |
| : [[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]]. | | : [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]], [[Formatting an SD card|formatting your SD card]], and/or [[Checking SD card integrity|testing your SD for errors]]. |
| |- | | |- |
| | Kujira<br>Joker<br>niji_loc || any | | | Kujira<br>Joker<br>niji_loc || any |
| | The app most recently opened has an issue of some kind. | | | The app you last opened has an issue of some kind. |
| :To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]] | | :To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|force the game to use the correct region.]] |
| ::If the error yet still happens, 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. | | ::If the error yet still happens, 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. |
| |- | | |- |
| | rowspan="2" | loader | | | loader || undefined instruction |
| | undefined instruction | | | The app you last opened has an issue. If the contents of R0 start with C or D, R0 is an error code.<br> |
| | The app most recently opened has an issue. R0 is (most likely) an error code. Here are some common values for R0: | | :Most of the possible error codes for this are also listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]]. |
| : <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
| |
| :: See: [[3DS:Fixing corrupted games]]
| |
| : <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>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 open the Homebrew Launcher itself, see the error above.
| |
| : Most of the other possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]]. | |
| |-
| |
| | prefetch abort (svcBreak)
| |
| | The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
| |
| : To fix: Re-download 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]].
| |
| |- | | |- |
| | mset || any | | | mset || any |
| | System Settings is broken in some way - this may indicate that the console has a hardware issue. | | | 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. | | :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 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. |
| |- | | |- |
| | nwm || any | | | nwm || any |
| Line 216: |
Line 174: |
| :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. | | :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. | | ::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. |
| |-
| |
| | pxi || any
| |
| | Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.
| |
| |- | | |- |
| | qtm<br>cam || any | | | qtm<br>cam || any |
| | The camera's hardware is damaged or dead. | | | 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. | | :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. |
| |-
| |
| | swkbd || any
| |
| | 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.
| |
| |- | | |- |
| |} | | |} |
| Line 245: |
Line 195: |
| | process: '''kernel''' | | | process: '''kernel''' |
| | Your system software is having a strange issue. | | | 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. | | :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: '''nwm''' | | | process: '''nwm''' |
| Line 265: |
Line 215: |
| | card removed | | | card removed |
| | Your SD card is faulty, or debris is interfering with its connection to the 3DS. | | | 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]]. | | :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]]. |
| |-
| |
| |0xC8A11BEF
| |
| |Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
| |
| |- | | |- |
| | 0xC86044D2 | | | 0xC86044D2 |
| | Your NAND does not have enough free space available. | | | 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. | | :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. |
| |- | | |- |
| | 0xC8804478 | | | 0xC8804478 |
| | The app you tried to open or system software it relies on is missing. | | | 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 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. | | :If this occurs after doing a manual CTRTransfer or Lazarus3DS, 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. |
| |- | | |- |
| | 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A? | | | 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A? |
| Line 296: |
Line 243: |
| | 0xC92044EB<br>0xC92044FA<br>0xC960454? | | | 0xC92044EB<br>0xC92044FA<br>0xC960454? |
| | Your SD card is set to read-only or is faulty. | | | 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. | | :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 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.
| |
| :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 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. |
| |- | | |- |
| Line 317: |
Line 263: |
|
| |
|
| |-|Error codes= | | |-|Error codes= |
| <span style="font-size:175%; display:flex; justify-content:center">Error Codes</span>
| |
| {| class="wikitable" style="margin:auto;" | | {| class="wikitable" style="margin:auto;" |
| |- | | |- |
| Line 447: |
Line 392: |
| |- | | |- |
| |0400 | | |0400 |
| |Your ability to do this is restricted by Parental Controls. | | |Your ability to do s is restricted by Parental Controls. |
| | | | | |
| |- | | |- |
| Line 1,256: |
Line 1,201: |
| |- | | |- |
| |2634 | | |2634 |
| |The NNID is not correctly linked to the system. To fix this, follow these steps, reboot the console, and try to sign into the NNID again. | | |The NNID is not correctly linked to the system. To fix this, follow these steps and afterwards reboot and sign into the NNID again. |
| |[[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|Said Steps]] | | |[[3dsguide:godmode9-usage#removing-an-nnid-without-formatting-your-device)|Said Steps]] |
| |- | | |- |
| |2643 | | |2643 |
| Line 1,379: |
Line 1,324: |
| |The game is permanently banned from Pokémon Global Link for using altered or illegal save data. | | |The game is permanently banned from Pokémon Global Link for using altered or illegal save data. |
| | | | | |
| |}
| |
|
| |
| |-|BootROM=
| |
| <span style="font-size:175%; display:flex; justify-content:center">BootROM</span>
| |
| {| class="wikitable" style="margin: auto"
| |
| ! style="font-size:125%;" | Error
| |
| ! style="font-size:125%;" | Description
| |
| |-
| |
| |00F800FE<br>00000000 00000000<br>00000200 00000000
| |
| |Error when having SD-card reader connected to NAND during boot.
| |
| |-
| |
| |00F800FE<br>00000000 00000000<br>00000400 00000000
| |
| |NAND not found error (?)
| |
| |-
| |
| |00F800FE<br>FFFFFFFF FFFFFFFF<br>00000080 00800000
| |
| |NAND error when DAT1 was used as DAT0.
| |
| |-
| |
| |00F800FE<br>FFFFFFFF FFFFFFFF<br>00000005 00800000
| |
| |NAND error when DAT2 was used as DAT0.
| |
| |-
| |
| |00F800FE<br>FFFFFFFF FFFFFFFF<br>00000005 00000000
| |
| |NAND error when DAT3 was used as DAT0.
| |
| |-
| |
| |00F800FF<br>F8F8FFFF FFFFFFFF<br>00000000 00000000
| |
| |Both the firm0 and firm1 partitions are corrupt (failed signature checks).
| |
| |-
| |
| |00F800FF<br>DEDEFFFF FFFFFFFF<br>00000000 00000000
| |
| |Both the firm0 and firm1 partitions are corrupt (possibly related to certain flags missing?)
| |
| |-
| |
| |00F800FF<br>CFCFFFFF FFFFFFFF<br>00000000 00000000
| |
| |Both the firm0 and firm1 partitions are corrupt
| |
| |-
| |
| |00F800EE<br>FFFFFFFF FFFFFFFF<br>00000000 00000000
| |
| |NCSD header in sector 0 is corrupt (failed signature check).
| |
| |} | | |} |
|
| |
|
| </tabber> | | </tabber> |
|
| |
| =Reading error screens=
| |
|
| |
|
| ==Reading a Luma3DS exception screen== | | ==Reading a Luma3DS exception screen== |
| [[File:Luma3DS_exception.png|right|300px]]A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
| | 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: | | * '''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. | | **'''Arm9:''' The 'security processor' of the system. These exceptions usually result from 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. | | **'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are 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: | | * '''Exception type:''' How the system is causing the exception. These categories are often too broad to be helpful, but three of them are more precise: |
| **'''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. | | **'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken. |
| **'''prefetch abort''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.
| | **'''prefetch abort (svcBreak)''': Oftentimes an issue with data on the NAND, even when Arm11. Can also happen when launching an out-of-region game. |
| **'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in 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''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot). |
| **'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.
| | *'''Fault status:''' Why the system is causing the exception. Normally not helpful except for developers. |
| **'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the 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: | | *'''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. | | **'''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. | | **'''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. | | **'''loader''': The service that opens apps, meaning the app you last tried to open has an issue. |
| **'''nwm''': Networking services, almost always Wi-Fi. | | **'''nwm''': Networking services, almost always WiFi. |
| **'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode. | | **'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode. |
| *'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however: | | *'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however: |
| Line 1,444: |
Line 1,351: |
| ==Reading a Luma3DS ErrDisp== | | ==Reading a Luma3DS ErrDisp== |
|
| |
|
| [[File:Luma3DS ErrDisp.jpg|right|300px]]A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
| | With Luma3DS insa 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. | | * '''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. | | * '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error. |
|
| |
|
| == Reading an error code == | | == Reading an error code == |
| <span>[[File:3DS error code.jpg|right|300px]]An error code has two parts - the code itself, and its official description.<br>
| | An error code has two parts - the code itself, and its official description. |
| For this page, only the code matters</span>
| | [[File:3DS error code.jpg|center]] |
| | | For this page, only the code matters |
| ==Reading boot9strap LED status codes==
| |
| Booting your console while holding {{B|X|START|SELECT}}, or if either FIRM file is corrupt, the notification LED will display a color indicating the status of the FIRMs located at <code>sdmc:/boot.firm</code> and <code>nand:/boot.firm</code>. Refer to the following table for their status:
| |
| {{B9s LED table}}
| |
| In addition, the LED will blink if booting from [[3DS:ntrboot|ntrboot]]<br>
| |
| NOTE: A red LED status can also occur if the NAND firm is missing rather than corrupt.
| |
| | |
| =Sources=
| |
| [[3DS:Error codes]]<br>
| |
| <!-- Up to date as of 22:51, 2 April 2024 id=5587 -->
| |
| [[3DS:Error screens/Luma3DS exception screen]]<br>
| |
| <!-- Up to date as of 14:44, 22 May 2024 id=6047 -->
| |
| [[3DS:Error screens/Luma3DS ErrDisp]]<br>
| |
| <!-- Up to date as of 07:29, 26 March 2024 id=5537 -->
| |
| [[3DS:Boot9strap]]<br>
| |
| {{GitHub|SciresM/boot9strap|boot9strap GitHub}}<br>
| |
| [[3dbrew:Bootloader]]
| |
| | |
| This page is up to date as of 04:08, 12 July 2024 (UTC)
| |
| <!-- ~~~~~ for time format -->
| |
