Closed cgrs closed 3 years ago
I got the same problem, thankx for posting this issue
It's being worked on
It's being worked on
Thank you for the response but so far, my console is then completley bricked. Can anyone give me pointers to still acces my 3ds without the CFW? I have a crash dump but I can only open the 3ds tommorow to get the sd card out.
Same here just gonna have to wait for the next luma update
On Mon, Nov 16, 2020, 7:09 PM Joerie Judong notifications@github.com wrote:
It's being worked on
Thank you for the response but so far, my console is then completley bricked. Can anyone give me pointers to still acces my 3ds without the CFW? I have a crash dump but I can only open the 3ds tommorow to get the sd card out.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LumaTeam/Luma3DS/issues/1519#issuecomment-728591266, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZSAR44X2WUUDFVUBBA7ETSQHEK5ANCNFSM4TX4435Q .
WEW LADS, I thought I was the only one. its crashing for me with AND without SD card in, New 2DS Xl as well. crash_dump_0000000.dmp is here https://files.catbox.moe/wn531k.dmp
Out of pure curiosity, what does commit 94b5113b17a54d8595a0d2195f06b27bfd73ee79 actually change in terms of the generated code? To me, the source code change would seem like a no-op!
Notice how svcKernelSetState() takes a variable number of args? If you pass args with the wrong types that's not gonna work very nicely when the kernel expects something else.
System model:
New 2DS XL
SysNAND version (+emu/redNAND version if applicable):
11.14.0-46E
Entrypoint (How/what you're using to boot Luma3DS):
Boot9Strap
Luma3DS version:
v10.2 Luma3DS configuration/options:
Default EmuNAND: (Off )
Screen brightness: (1 )
Splash: (Before )
Splash duration: (1s )
PIN lock: (Off )
New 3DS CPU: (Off )
--
Autoboot EmuNAND: (Off )
Use EmuNAND FIRM if booting with R: (Off )
Enable loading external FIRMs and modules: ( Off)
Enable game patching: (Off )
Show NAND or user string in System Settings: (On )
Show GBA boot screen in patched AGB_FIRM: ( Off)
Set developer UNITINFO: ( Off)
Disable Arm11 exception handlers: (Off )
Enable Rosalina on SAFE_FIRM: ( Off )
--
Explanation of the issue:
Afer updating to latest 3DS Firmware (11.14.0-46) and rebooting the console, an ARM11 exception appears. Everytime the console boots Luma loads but the exception reappears. It is possible to access payloads previously installed (I used this to boot into Godmode9 and boot NATIVE_FIRM. This made the console as if it was untouched, because after that I couldn't access Luma configuration screen and payloads).
Steps to reproduce:
1.Update to latest FW.
Dump file:
(Unfortunately I didn't get a dump. I'll try to reproduce it again and upload the dump in this issue).