3DS:Error screens/Luma3DS exception screen: Difference between revisions

Line 1:

~~{{Page WIP~~|~~notes=~~

This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

*~~Add~~ an ~~example~~ exception ~~screen and how~~ to ~~read it~~.

==Reading a Luma3DS exception screen==

}}

A Luma3DS exception has at least four different parts to it that must be interpreted to find the cause of an error, 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 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 are often too broad of categories to be helpful, but three types 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 <code>boot.firm</code> (if on boot).

*'''Fault status:''' Why the system is causing the exception. Normally not helpful for end-users.

*'''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:

**'''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, <code>boot.firm</code> is too outdated to work.

**'''loader''': The app you last tried to run has an error.

**'''qtm''': Your camera has a hardware issue.

*'''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 <code>E0E01BF5</code>, <code>boot.firm</code> is too outdated to work.

~~This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.~~

==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/nintendohomebrew Nintendo Homebrew Discord]] for further assistance.}}

===Arm9===

=~~=Arm9==~~

====On boot====

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

Line 15:

Line 32:

*System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

====Prefetch abort (svcBreak)====

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

=====Data abort=====

*<code>SYSNAND TWLN</code>'s <code>[2:]/shared2</code> folder is missing.

**To fix, create this folder.

Line 26:

Line 43:

**To fix, perform a [[3DS:Safe Mode|Safe Mode update]].

===During use===

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

==Arm11==

===Arm11===

===On boot===

====On boot====

====boss (0004013000003402), data abort====

=====boss (0004013000003402), data abort=====

*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)====

=====fs (0000000000000000)=====

*Can be anything from SD card problems to hardware issues.

====hid (0004013000001D02)====

=====hid (0004013000001D02)=====

*Potential hardware problems.

====menu (000400300000__02), data abort====

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

Line 61:

Line 78:

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

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

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

=====pm (0000000000000000), undefined instruction=====

*The installed version of Luma3DS does not support the current firmware version.

**To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

===During use===

====During use====

====loader (0000000000000000)====

=====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 SD card, dying game cartridge, or dirty cartridge reader.

[[Category:Unbricking]]

@@ Line 1: / Line 1: @@
-{{Page WIP|notes=
+This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
-*Add an example exception screen and how to read it.
+==Reading a Luma3DS exception screen==
-}}
+A Luma3DS exception has at least four different parts to it that must be interpreted to find the cause of an error, 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 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 are often too broad of categories to be helpful, but three types 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 <code>boot.firm</code> (if on boot).
+*'''Fault status:''' Why the system is causing the exception. Normally not helpful for end-users.
+*'''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:
+**'''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, <code>boot.firm</code> is too outdated to work.
+**'''loader''': The app you last tried to run has an error.
+**'''qtm''': Your camera has a hardware issue.
+*'''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 <code>E0E01BF5</code>, <code>boot.firm</code> is too outdated to work.
-This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
+==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/nintendohomebrew Nintendo Homebrew Discord]] for further assistance.}}
+===Arm9===
-==Arm9==
+====On boot====
-===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.
@@ Line 15: / Line 32: @@
 *System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.
-====Prefetch abort (svcBreak)====
+=====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====
+=====Data abort=====
 *<code>SYSNAND TWLN</code>'s <code>[2:]/shared2</code> folder is missing.
 **To fix, create this folder.
@@ Line 26: / Line 43: @@
 **To fix, perform a [[3DS:Safe Mode|Safe Mode update]].
-===During use===
+====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.
-==Arm11==
+===Arm11===
-===On boot===
+====On boot====
-====boss (0004013000003402), data abort====
+=====boss (0004013000003402), data abort=====
 *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)====
+=====fs (0000000000000000)=====
 *Can be anything from SD card problems to hardware issues.
-====hid (0004013000001D02)====
+=====hid (0004013000001D02)=====
 *Potential hardware problems.
-====menu (000400300000__02), data abort====
+=====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:
@@ Line 61: / Line 78: @@
 **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=====
+======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)=====
+======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, 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====
+=====pm (0000000000000000), undefined instruction=====
 *The installed version of Luma3DS does not support the current firmware version.
 **To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]
-===During use===
+====During use====
-====loader (0000000000000000)====
+=====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 SD card, dying game cartridge, or dirty cartridge reader.
 [[Category:Unbricking]]