< 3DS:Error screens
Revision as of 01:36, 13 October 2022 by StarlitSkies (talk | contribs) (condense wikitext, add new error, and revise wording enough to remove one of the two Page WIP clauses)
 | This page is a work in progress. Notes:
|
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 CTRNANDin/datahas a problem. - System-unique files are missing from
[1:] SYSNAND CTRNANDin/rw/sys.
Prefetch abort (svcBreak)
- The
[1:] SYSNAND CTRNANDcopy of the movable,/private/movable.sed, is 288 bytes but its flag indicates otherwise. [1:] SYSNAND CTRNANDhas bad CMACs.
Data abort
[2:] SYSNAND TWLN's/shared2folder 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.
- Broken HOME Menu theme.
- Broken HOME Menu extra data.
- Broken HOME Menu application.
- 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.