m (typo on loader undefined instr) |
StarlitSkies (talk | contribs) (add a couple more processes plus other misc. info // Edit via Wikitext Extension for VSCode) |
||
(34 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues. | 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== | ==Reading a Luma3DS exception screen== | ||
Line 5: | Line 4: | ||
[[File:Luma3DS_exception.png|center]] | [[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 | **'''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. | ||
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are | **'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are often related to broken software or user data. | ||
* '''Exception type:''' | * '''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''': | **'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken. | ||
**'''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)''': | **'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot). | ||
*'''Fault status:''' Why the system is causing the exception. Normally not helpful except for developers. | |||
**'''undefined instruction''': | *'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Common or unique processes are as follows: | ||
*'''Fault status:''' | **'''fs''': Files on your SD card or NAND are having issues. | ||
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. | **'''hid''': Potential hardware problems. | ||
**'''fs''': | **'''menu''': Some of the data/extdata that's either associated with the HOME Menu or loaded at the same time is broken. | ||
**'''menu''': | **'''pm''': Almost always, <code>boot.firm</code> is too outdated to work. | ||
**'''loader''': The | **'''loader''': The app you last tried to run has an error. | ||
**''' | **'''qtm'''/'''cam''': Your camera has a hardware issue. | ||
**''' | **'''nwm''': Your WiFi chip is damaged, dying, or entirely dead. This always means you must disable WiFi to stop the errors. | ||
*'''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: | ||
**'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue. | **'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue. | ||
**'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work. | **'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work. | ||
== Known Errors == | ==Known Errors== | ||
Note that the prefixes on file paths refer to the starting location. <code>sdmc:/</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/ | {{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.}} | ||
===Arm9=== | |||
=== < | ====On boot==== | ||
*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 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>. | |||
< | =====Prefetch abort (svcBreak)===== | ||
*The system's movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but its flag indicates otherwise. | |||
*<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>. Your system will act like it has been formatted after this, and this is intended. | |||
< | =====Data abort===== | ||
* | *<code>SYSNAND TWLN</code>'s <code>[2:]/shared2</code> folder is missing. | ||
** To fix, [[ | **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]]. | |||
====During use==== | |||
* | *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. | |||
** To fix, | |||
===Arm11=== | |||
====On boot==== | |||
=====boss (0004013000003402), data abort===== | |||
* The | *The current firmware version is too old for SpotPass to work. | ||
**To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]] | |||
=====fs (0000000000000000)===== | |||
*Can be anything from SD card problems to hardware issues. | |||
=====hid (0004013000001D02)===== | |||
* | *Potential hardware problems. | ||
=== < | =====menu (000400300000__02), data abort===== | ||
*Broken HOME Menu theme. | |||
**To fix, go into the folder <code>sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following: | |||
***USA: <code>000002cd</code> | |||
***EUR: <code>000002ce</code> | |||
***JPN: <code>000002cc</code> | |||
*Broken HOME Menu extra data. | |||
**To fix, go into the folder <code>sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following: | |||
***USA: <code>0000008f</code> | |||
***EUR: <code>00000098</code> | |||
***JPN: <code>00000082</code> | |||
***KOR: <code>000000A9</code> | |||
*Broken HOME Menu application. | |||
**To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. | |||
**If this does not fix it, attempt to enter System Settings before the crash occurs and find the broken application in Data Management, if possible. | |||
**If ''this'' does not fix it, you may try to enter GodMode9 and use its title list to find the broken application - this is risky, however, and should not be attempted without guidance unless you know exactly what you are doing. For guidance, join the [[https://discord.gg/nintendohomebrew Nintendo Homebrew Discord]]. | |||
< | ======menu (000400300000__02), prefetch abort====== | ||
*An installation of menuhax is conflicting with your custom firmware. | |||
**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>sdmc:/3ds</code>, run it through Homebrew Launcher, and choose REMOVE. | |||
< | ======menu (000400300000__02), prefetch abort (svcBreak)====== | ||
*The f000000b folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>. | |||
** To fix, | **To fix, backup that folder by pressing R+A while highlighting it, then select <code>Copy to 0:/gm9/out</code>. Once backed up, delete the folder. If this does not fix the issue, copy the folder back where it was. | ||
=====pm (0000000000000000), undefined instruction===== | |||
* The current firmware version | *The installed version of Luma3DS does not support the current firmware version. | ||
** | **To fix, [[3dsguide:restoring-updating-cfw|update CFW.]] | ||
====During use==== | |||
=====loader (0000000000000000)===== | |||
If the hexadecimal number next to R0 starts with 'C' or 'D', search for it as an error code or in [[3DS:Error_screens/Luma3DS_ErrDisp]].<br> | |||
These errors are usually due to corruption, such as a faulty/dirty SD card or game cartridge. | |||
[[Category:Unbricking]] | [[Category:Unbricking]] | ||
Revision as of 21:52, 22 January 2023
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:
- Processor: What part of the system is causing the exception. The two processors are:
- 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.
- Arm11: The 'userland' of the system. These exceptions have numerous causes but are often related to broken software or user data.
- 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: Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken.
- prefetch abort (svcBreak): Oftentimes an issue with data on the NAND, even when Arm11. Can also happen when launching an out-of-region game.
- undefined instruction: Usually either a broken piece of software (if not on boot) or outdated
boot.firm
(if on boot).
- Fault status: Why the system is causing the exception. Normally not helpful except for developers.
- Current process: Where the error is coming from in the system. Often the most helpful part of the exception. Common or unique processes are as follows:
- fs: Files on your SD card or NAND are having issues.
- hid: Potential hardware problems.
- menu: Some of the data/extdata that's either associated with the HOME Menu or loaded at the same time is broken.
- pm: Almost always,
boot.firm
is too outdated to work. - loader: The app you last tried to run has an error.
- qtm/cam: Your camera has a hardware issue.
- nwm: Your WiFi chip is damaged, dying, or entirely dead. This always means you must disable WiFi to stop the errors.
- R0: Usually just internal data that's not worth reading. There are two notable exceptions, however:
- Arm11 loader exception: If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue.
- Arm11 pm exception: If R0's contents are
E0E01BF5
,boot.firm
is guaranteed to be too outdated to work.
Known Errors
Note that the prefixes on file paths refer to the starting location. sdmc:/
refers to the SD card, and numbers in the format of [X:]
refer to GodMode9's drive numbers.
If the below fixes do not solve your issue or you are unsure of what to do, join the [Nintendo Homebrew Discord] for further assistance. |
Arm9
On boot
- Files on the SD are corrupted.
- To fix, verify that your card is not faulty. If it is verified working, make a backup of all intact files, format the SD card, and try booting again.
- A system save located on the NAND in
[1:]/data
has a problem. - System-unique files are missing from the NAND in
[1:]/rw/sys
.
Prefetch abort (svcBreak)
- The system's movable,
[1:]/private/movable.sed
, is 288 bytes but its flag indicates otherwise. SYSNAND CTRNAND
has bad CMACs.- To fix, press R+A on the
SYSNAND CTRNAND
drive andFix CMACs for drive
. Your system will act like it has been formatted after this, and this is intended.
- To fix, press R+A on the
Data abort
SYSNAND TWLN
's[2:]/shared2
folder is missing.- To fix, create this folder.
- System titles have been deleted.
- To fix, perform a Safe Mode update. If this does not work, perform a CTRTransfer.
During use
- Files on the SD are corrupted.
- To fix, verify that your card is not faulty. If it is verified working, make a backup of all intact files, format the SD card, and try again.
Arm11
On boot
boss (0004013000003402), data abort
- The current firmware version is too old for SpotPass to work.
- To fix, perform a Safe Mode update. If this does not work, you may require a CTRTransfer.
fs (0000000000000000)
- Can be anything from SD card problems to hardware issues.
hid (0004013000001D02)
- Potential hardware problems.
- Broken HOME Menu theme.
- To fix, go into the folder
sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/
and delete the folder matching your region, one of the following:- USA:
000002cd
- EUR:
000002ce
- JPN:
000002cc
- USA:
- To fix, go into the folder
- Broken HOME Menu extra data.
- To fix, go into the folder
sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/
and delete the folder matching your region, one of the following:- USA:
0000008f
- EUR:
00000098
- JPN:
00000082
- KOR:
000000A9
- USA:
- To fix, go into the folder
- Broken HOME Menu application.
- To fix, perform a Safe Mode update.
- If this does not fix it, attempt to enter System Settings before the crash occurs and find the broken application in Data Management, if possible.
- If this does not fix it, you may try to enter GodMode9 and use its title list to find the broken application - this is risky, however, and should not be attempted without guidance unless you know exactly what you are doing. For guidance, join the [Nintendo Homebrew Discord].
- An installation of menuhax is conflicting with your custom firmware.
- To fix, place the
menuhax67_installer.3dsx
file from [this download] intosdmc:/3ds
, run it through Homebrew Launcher, and choose REMOVE.
- To fix, place the
- The f000000b folder in
SYSNAND CTRNAND
is broken, its exact location being at[1:]/data/<ID0>/extdata/00048000/f000000b
.- To fix, backup that folder by pressing R+A while highlighting it, then select
Copy to 0:/gm9/out
. Once backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
- To fix, backup that folder by pressing R+A while highlighting it, then select
pm (0000000000000000), undefined instruction
- The installed version of Luma3DS does not support the current firmware version.
- To fix, update CFW.
During use
loader (0000000000000000)
If the hexadecimal number next to R0 starts with 'C' or 'D', search for it as an error code or in 3DS:Error_screens/Luma3DS_ErrDisp.
These errors are usually due to corruption, such as a faulty/dirty SD card or game cartridge.