Toggle search
Toggle menu
303
299
452
7K
Hacks Guide Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

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

From Hacks Guide Wiki
More actions
mNo edit summary
(condense wikitext, add new error, and revise wording enough to remove one of the two Page WIP clauses)
Line 1: Line 1:
{{Page WIP|notes=
{{Page WIP|notes=
*Add an example exception screen and how to read it.
*Add an example exception screen and how to read it.
*The description of some errors use gm9 drive (x:) notation to describe the location of the problem without directly saying in which partition the problem lies.
}}
}}


This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.
This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.
Note that all numbers such as <code>[1:]</code> are the drive numbers in GodMode9 for those partitions.


==Arm9==
==Arm9==


===On boot ===
===On boot===
 
*Files on the SD are corrupted.
*Files on the SD are corrupted.
* A system save inside <code>1:/data</code> has a problem.
*A system save located on <code>[1]: SYSNAND CTRNAND</code> in <code>/data</code> has a problem.
*Files in <code>1:/rw/sys</code> are missing.
*System-unique files are missing from <code>[1:] SYSNAND CTRNAND</code> in <code>/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.
*<code>1:/private/movable.sed</code> is only 288 bytes, but its flag indicates otherwise.
*<code>[1:] SYSNAND CTRNAND</code> has bad CMACs.
*SYSNAND CTRNAND has bad CMACs.


====Data abort====
====Data abort====
 
*<code>[2:] SYSNAND TWLN</code>'s <code>/shared2</code> folder is missing.
*The <code>2:/shared2</code> folder is missing.
*System titles have been deleted. Perform a Safe Mode update.


===During use===
===During use===
*Files on the SD are corrupted.
*Files on the SD are corrupted.


Line 31: Line 28:
===On boot===
===On boot===


==== boss (0004013000003402), data abort====  
====boss (0004013000003402), data abort====  
 
*Current firmware version is too old for SpotPass to work. Perform a safe mode update.
*Firmware version is too old to handle SpotPass. Perform a safe mode update.


====fs (0000000000000000)====
====fs (0000000000000000)====
 
*Can be anything from SD card problems to hardware issues.
* Can be anything from SD card problems to hardware issues.


====hid (0004013000001D02)====
====hid (0004013000001D02)====
*Potential hardware problems.
*Potential hardware problems.


====menu (000400300000__02), data abort====
====menu (000400300000__02), data abort====
*Broken HOME Menu theme.
*Broken HOME Menu theme.
*Broken HOME Menu extra data.
*Broken HOME Menu extra data.
Line 50: Line 43:


=====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>.
*Broken f000000b folder in CTRNAND.


====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.]]
*Outdated Luma3DS that does not support the current firmware version.


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


[[Category:Unbricking]]
[[Category:Unbricking]]

Revision as of 01:36, 13 October 2022

This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation. Note that all numbers such as [1:] are the drive numbers in GodMode9 for those partitions.

Arm9

On boot

  • Files on the SD are corrupted.
  • A system save located on [1]: SYSNAND CTRNAND in /data has a problem.
  • System-unique files are missing from [1:] SYSNAND CTRNAND in /rw/sys.

Prefetch abort (svcBreak)

  • The [1:] SYSNAND CTRNAND copy of the movable, /private/movable.sed, is 288 bytes but its flag indicates otherwise.
  • [1:] SYSNAND CTRNAND has bad CMACs.

Data abort

  • [2:] SYSNAND TWLN's /shared2 folder is missing.
  • System titles have been deleted. Perform a Safe Mode update.

During use

  • Files on the SD are corrupted.

Arm11

On boot

boss (0004013000003402), data abort

  • Current firmware version is too old for SpotPass to work. Perform a safe mode update.

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.
  • Broken HOME Menu extra data.
  • Broken HOME Menu application.
menu (000400300000__02), prefetch abort (svcBreak)
  • Broken f000000b folder in [1:] SYSNAND CTRNAND, the folder being located at /data/<ID0>/extdata/00048000/f000000b.

pm (0000000000000000), undefined instruction

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

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.

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