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

From Hacks Guide Wiki
(experienced that issue, and helpees had it too, removing the folder fixes it, so i guess its related to that)
mNo edit summary
Line 1: Line 1:
{{Page WIP|notes=
*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.


== 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 inside <code>1:/data</code> has a problem.
* Files in <code>1:/rw/sys</code> are missing.
*Files in <code>1:/rw/sys</code> are missing.


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


* <code>1:/private/movable.sed</code> is only 288 bytes, but its flag indicates otherwise.
*<code>1:/private/movable.sed</code> is only 288 bytes, but its flag indicates otherwise.
* SYSNAND CTRNAND has bad CMACs.
*SYSNAND CTRNAND has bad CMACs.


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


* The <code>2:/shared2</code> folder is missing.
*The <code>2:/shared2</code> folder is missing.


=== During use ===
===During use===


* Files on the SD are corrupted.
*Files on the SD are corrupted.


== Arm11 ==
==Arm11==


=== On boot ===
===On boot===


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


* Firmware version is too old to handle SpotPass. 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.
* Broken HOME Menu application.
*Broken HOME Menu application.


===== menu (000400300000__02), prefetch abort (svcBreak) =====
=====menu (000400300000__02), prefetch abort (svcBreak)=====


* Broken f000000b folder in CTRNAND.
*Broken f000000b folder in CTRNAND.


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


* Outdated Luma3DS that does not support the current firmware version.
*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 00:42, 26 September 2022

This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.

Arm9

On boot

  • Files on the SD are corrupted.
  • A system save inside 1:/data has a problem.
  • Files in 1:/rw/sys are missing.

Prefetch abort (svcBreak)

  • 1:/private/movable.sed is only 288 bytes, but its flag indicates otherwise.
  • SYSNAND CTRNAND has bad CMACs.

Data abort

  • The 2:/shared2 folder is missing.

During use

  • Files on the SD are corrupted.

Arm11

On boot

boss (0004013000003402), data abort

  • Firmware version is too old to handle SpotPass. 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 CTRNAND.

pm (0000000000000000), undefined instruction

  • Outdated Luma3DS that 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.