-
Notifications
You must be signed in to change notification settings - Fork 550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARM11 exception svcBreak in process menu #1503
Comments
I'm facing the same problem. Above message shows when I try to power on my O3DS XL. If I remove my SD card, the blue LED lights up, then goes off -- but I had already done CTRTransfer to NAND. |
Just managed to solve this problem by following the steps in the link below: https://gbatemp.net/threads/black-screen-at-the-start-of-the-3ds.543980/page-3#post-8763629 |
Yo I have the same same problem so I went to fbi then went to titles then deleted the red things in titles cuz they were taking a lot of space on my 2ds then turned it off to take a break then the (Arm11) (core 0) (SvcBreak) |
Why |
For the love of gods do not just go through the title list and delete titles you don't know about |
System model:
Old 3DS
SysNAND version (+emu/redNAND version if applicable):
I cannot check it anymore, but it's the latest American version.
Entrypoint (How/what you're using to boot Luma3DS):
I don't know how can I check it, but I followed the steps in the 3ds.hacks.guide page
Luma3DS version:
v10.2 stable
Luma3DS configuration/options:
Screen brightness: 4(x)
Splash: Off(x)
Splash duration: 1(x) seconds
PIN lock: Off(x)
Enable loading external FIRMs and modules: ( )
Enable game patching: ( )
Show NAND or user string in System Settings: (x)
Show GBA boot screen in patched AGB_FIRM: ( )
Set developer UNITINFO: ( )
Disable Arm11 exception handlers: ( )
Explanation of the issue:
The exception persists even without SD Card.
I've tried a
CTRTransfer (D9)
using the script that comes withGodMode9
. That was my best shoot. After completed I saw a "loading" dialog "Preparing Home Menu" or something like that. After the loading finished I got the same error.Steps to reproduce:
Dump file:
crash_dump_00000000.tar.gz
The text was updated successfully, but these errors were encountered: