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

From Hacks Guide Wiki
(condense wikitext, add new error, and revise wording enough to remove one of the two Page WIP clauses)
(add solutions for a large number of the errors & major style fixes)
Line 3: Line 3:
}}
}}


This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
Note that all numbers such as <code>[1:]</code> are the drive numbers in GodMode9 for those partitions.
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==
Line 10: Line 11:
===On boot===
===On boot===
*Files on the SD are corrupted.
*Files on the SD are corrupted.
*A system save located on <code>[1]: SYSNAND CTRNAND</code> in <code>/data</code> has a problem.
**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, format the SD card, and try again.
*System-unique files are missing from <code>[1:] SYSNAND CTRNAND</code> in <code>/rw/sys</code>.
*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)====
====Prefetch abort (svcBreak)====
*The <code>[1:] SYSNAND CTRNAND</code> copy of the movable, <code>/private/movable.sed</code>, is 288 bytes but its flag indicates otherwise.
*The system's movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but its flag indicates otherwise.
*<code>[1:] 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>. Your system will act like it has been formatted after this, and this is intended.


====Data abort====
====Data abort====
*<code>[2:] SYSNAND TWLN</code>'s <code>/shared2</code> folder is missing.
*<code>SYSNAND TWLN</code>'s <code>[2:]/shared2</code> folder is missing.
*System titles have been deleted. Perform a Safe Mode update.
**To fix, create this folder.
*System titles have been deleted.  
**To fix, perform a [[3DS:Safe Mode|Safe Mode update]].


===During use===
===During use===
*Files on the SD are corrupted.
*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, format the SD card, and try again.


==Arm11==
==Arm11==
Line 29: Line 35:


====boss (0004013000003402), data abort====  
====boss (0004013000003402), data abort====  
*Current firmware version is too old for SpotPass to work. Perform a safe mode update.
*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 [[3DS:CTRTransfer|a CTRTransfer.]]


====fs (0000000000000000)====
====fs (0000000000000000)====
Line 39: Line 46:
====menu (000400300000__02), data abort====
====menu (000400300000__02), data abort====
*Broken HOME Menu theme.
*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.
*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.
*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.


=====menu (000400300000__02), prefetch abort (svcBreak)=====
=====menu (000400300000__02), prefetch abort (svcBreak)=====
*Broken f000000b folder in <code>[1:] SYSNAND CTRNAND</code>, the folder being located at <code>/data/<ID0>/extdata/00048000/f000000b</code>.
*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. [[3dsguide:restoring-updating-cfw|Update CFW.]]
*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 in [[3DS:Error_screens/Luma3DS_ErrDisp]].
If the hexadecimal number next to R0 starts with 'C' or 'D', search for it 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]]
[[Category:Unbricking]]

Revision as of 22:48, 16 October 2022

This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues. 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.

OOjs UI icon information-progressive.svg 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.
  • 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 and Fix CMACs for drive. Your system will act like it has been formatted after this, and this is intended.

Data abort

  • SYSNAND TWLN's [2:]/shared2 folder is missing.
    • To fix, create this folder.
  • System titles have been deleted.

During use

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.

menu (000400300000__02), data abort

  • 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
  • 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
  • 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.
menu (000400300000__02), prefetch abort (svcBreak)
  • 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.

pm (0000000000000000), undefined instruction

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


During use

loader (0000000000000000)

If the hexadecimal number next to R0 starts with 'C' or 'D', search for it in 3DS:Error_screens/Luma3DS_ErrDisp.
These errors are usually due to corruption, such as a faulty SD card, dying game cartridge, or dirty cartridge reader.

Retrieved from "https://wiki.hacks.guide/w/index.php?title=3DS:Error_screens/Luma3DS_exception_screen&oldid=2432"