Can no longer boot

[Ondrashek06]

Upon booting, I immediately get "An exception occurred...".

It seems to be related to a process named "act" with Title ID 0004013000003802, how do I get my 3DS to boot again?
The only thing I've done before it started failing was running the NNID removal script because it always threw error 022-5432.

If anyone here is interested in the register values (I doubt it), here are they:

Spoiler: Register Values

R1: 0000001B
R2: 00000001
R3: 00136004
R4: 00128290
R5: 00000001
R6: 001282E4
R7: 00136000
Stack Pointer: 0FFFFF90
Link: 00125114
Program Counter: 001000C68
Current Program Status: 20000030
Fault Address: 00000004
Register R0 and registers R8 to R12 are all set to 00000000.

 

[Hayato213]

0004013000003802 refer to firmware 9.3.0-21-K so what did you do?

 

[Ondrashek06]

0004013000003802 refer to firmware 9.3.0-21-K so what did you do?

9.3? And the KOREAN version too? That firmware version wasn't even on the 3DS during the entire time I owned it, I bought with 11.15.0E flashed and it's an European 3DS...

Edit: The TitleID seems to be the same across regions, but why would my 3DS suddenly attempt to boot an ancient firmware after a NNID removal?

 

[zoogie]

9.3? And the KOREAN version too? That firmware version wasn't even on the 3DS during the entire time I owned it, I bought with 11.15.0E flashed and it's an European 3DS...

Edit: The TitleID seems to be the same across regions, but why would my 3DS suddenly attempt to boot an ancient firmware after a NNID removal?

Here's someone in the Nintendo Homebrew Discord who had the exact same crash:
https://discord.com/channels/196618637950451712/247557068490276864/1058499497942061096
(you'll have to join to see it - this is the 3ds.guide official discord btw)

tl;dr, is this was fixed, somehow, by running my 2DSaver: https://github.com/zoogie/2DSaver

 

[Ondrashek06]

Here's someone in the Nintendo Homebrew Discord who had the exact same crash:
https://discord.com/channels/196618637950451712/247557068490276864/1058499497942061096
(you'll have to join to see it - this is the 3ds.guide official discord btw)

tl;dr, is this was fixed, somehow, by running my 2DSaver: https://github.com/zoogie/2DSaver

Nope, done exactly what was in the github's readme and it still has the exact same issue.

 

[Kwyjor]

Nope, done exactly what was in the github's readme

So did the app appear?

Does anything different happen if the SD card is removed entirely?

 

[Ondrashek06]

So did the app appear?

Does anything different happen if the SD card is removed entirely?

No, the app did not appear. It first went to the Luma3DS configuration and then to the crash screen. With the SD card removed, it says:

Continuing bootloader...
Firmware not loaded!
Are boot slots properly set up?

EDIT: That seems to have been a mistake of boot slot configuration, I selected "boot.firm.bak" (Luma3DS v10.2.1) and it booted into a completely stock HOME menu (no theme nor software except the defaults). The DSiWare however is still there, I can get into b9sTool (Nope, it just boots into a white screen). In that environment, the firmware says "11.17.0-50E", I have no idea why does it have problems with a 9.3 sysmodule.

I can also get into the homebrew launcher, as it seems to have been injected into H&S. Nope, setting the Rosalina HBL to it triggers an undefined instruction exception with "loader" (TID: 0000000000000000)...

Seriously, so much weird stuff is happening with my 3DS. Is it haunted or something? In the meanwhile, I'm going to play WarioWare Touched DL as it's one of the only things that work...

 

[Kwyjor]

I selected "boot.firm.bak" (Luma3DS v10.2.1) and it booted into a completely stock HOME menu (no theme nor software except the defaults). The DSiWare however is still there

DSiware is stored in the NAND instead of on the SD card. Often if only DSiware is appearing, it means that the SD card is failing. The SD card is unfortunately the most likely component to fail, and SD card failure can cause many mysterious problems.

So, standard procedure: copy everything off (preferably with Roadkil's Unstoppable Copier), format the card, test the empty card with h2testw, and then copy everything back if the test is okay. Sometimes just copying everything off and back again can fix some problems.

Nope, setting the Rosalina HBL to it triggers an undefined instruction exception with "loader" (TID: 0000000000000000)...

Usually that happens if boot.3dsx cannot be loaded. Did you replace boot.3dsx after experimenting with 2DSaver?

 

[Ondrashek06]

DSiware is stored in the NAND instead of on the SD card. Often if only DSiware is appearing, it means that the SD card is failing. The SD card is unfortunately the most likely component to fail, and SD card failure can cause many mysterious problems.

So, standard procedure: copy everything off (preferably with Roadkil's Unstoppable Copier), format the card, test the empty card with h2testw, and then copy everything back if the test is okay. Sometimes just copying everything off and back again can fix some problems.

Usually that happens if boot.3dsx cannot be loaded. Did you replace boot.3dsx after experimenting with 2DSaver?

Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 29.5 MByte/s
Reading speed: 37.6 MByte/s
H2testw v1.4

 

[Kwyjor]

Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 29.5 MByte/s
Reading speed: 37.6 MByte/s
H2testw v1.4

This information isn't very useful on its own. Did you follow the other instructions? Was your card completely empty before you ran h2testw? Did anything different happen when you copied your files back?

 

[Ondrashek06]

This information isn't very useful on its own. Did you follow the other instructions? Was your card completely empty before you ran h2testw? Did anything different happen when you copied your files back?

Yes, the card was completely empty and the files were OK when I copied them back.

There also isn't a boot.3dsx to load, because it loads them from the SD card which I cannot use if I want the 3DS to boot.

 

[Ondrashek06]

The issue still isn't solved, I need help, please

 

[linuxares]

What happens if you try to boot without your sd card inserted?

 

[Ondrashek06]

No, the app did not appear. It first went to the Luma3DS configuration and then to the crash screen. With the SD card removed, it says:

Continuing bootloader...
Firmware not loaded!
Are boot slots properly set up?

EDIT: That seems to have been a mistake of boot slot configuration, I selected "boot.firm.bak" (Luma3DS v10.2.1) and it booted into a completely stock HOME menu (no theme nor software except the defaults). The DSiWare however is still there, I can get into b9sTool (Nope, it just boots into a white screen). In that environment, the firmware says "11.17.0-50E", I have no idea why does it have problems with a 9.3 sysmodule.

I can also get into the homebrew launcher, as it seems to have been injected into H&S. Nope, setting the Rosalina HBL to it triggers an undefined instruction exception with "loader" (TID: 0000000000000000)...

Seriously, so much weird stuff is happening with my 3DS. Is it haunted or something? In the meanwhile, I'm going to play WarioWare Touched DL as it's one of the only things that work...

@linuxares This.

 

[linuxares]

Can you try a new sd card so it isn't faulty then? Seems like you havent installed luma on the nand

 

[Ondrashek06]

Can you try a new sd card so it isn't faulty then? Seems like you havent installed luma on the nand

I tested it with h2testw, there are no problems and no files are corrupted. The SD card isn't the problem.

 

[linuxares]

Then just start Fresh with the card and only put on Lumas files.

 

[Ondrashek06]

Then just start Fresh with the card and only put on Lumas files.

That's exactly what I do not want to do. I have many games installed, and those games have their save data.

 

[linuxares]

Just backup the card and try...

 

[Kwyjor]

Continuing bootloader...
Firmware not loaded!
Are boot slots properly set up?

To be honest, I've never heard of this error before. I don't even know why you would have a "boot.firm.bak" and why your 3DS would prompt you to select it. (Are there other things you can select aside from boot.firm.bak?)

It may indeed be worth trying an empty card with nothing but boot.firm just to see if it does anything different.