Hacking Removing Boot9Strap and LumaCFW? 3DS Crashes?

[Yandere-chan]

I know this sounds completely stupid but, I want to remove custom firmware from my device. I am on an o3DS 11.5 with boot9strap and luma 8.1. My 3DS has been crashing at times frequently with arm9 crash dumps and making me shut off the system and eShop doesn't work anymore (error 007-2001).

 

[Deleted User]

I know this sounds completely stupid but, I want to remove custom firmware from my device. I am on an o3DS 11.5 with boot9strap and luma 8.1. My 3DS has been crashing at times frequently with arm9 crash dumps and making me shut off the system and eShop doesn't work anymore (error 007-2001).

Do you know by Any chance if you are on b9s 1.2 exactly? If you are try a stable version of luma 8.1,the crashes could be from a nightly or a earlier build.

 

[The Real Jdbye]

I know this sounds completely stupid but, I want to remove custom firmware from my device. I am on an o3DS 11.5 with boot9strap and luma 8.1. My 3DS has been crashing at times frequently with arm9 crash dumps and making me shut off the system and eShop doesn't work anymore (error 007-2001).

Try the legacy build from here: https://astronautlevel2.github.io/Luma3DS/
It should get rid of the crashes.
Removing B9S should be your last resort.

 

[wsquan171]

Have you changed your region? I remember someone saying that re-doing a ctrnand transfer could probably fix the issue to some extent.

 

[dpad_5678]

Removing B9S is just stupid to be honest. B9S doesn't cause crashes like you described. Could be an unstable Luma build or a user error.

 

[The Catboy]

B9S is not the cause of your error and removing it will not fix your error. 98% of the problems happening now are being mistakenly tagged to B9S and that needs to stop.
Your error is being caused by Rosalina (the new experimental feature of Luma3DS.) These crashes are something that have been happening since the launch of the feature.
Try using the Legacy build

 

[Quantumcat]

@Yandere-chan did using the legacy build help you?

 

[ihaveahax]

don't forget to also try the latest release (v8.1.1) to see if the same crashes occur. if they do, an issue can be created on the tracker: https://github.com/AuroraWright/Luma3DS/issues

 

[Deleted-351540]

B9S is not the cause of your error and removing it will not fix your error. 98% of the problems happening now are being mistakenly tagged to B9S and that needs to stop.
Your error is being caused by Rosalina (the new experimental feature of Luma3DS.) These crashes are something that have been happening since the launch of the feature.
Try using the Legacy build

This can't be true. I was on the legacy build for a few weeks and still saw crashes. Mainly in Retroarch, NTRSelector, TWLoader, and a few games. (Mario Sports Superstars, Ridge Racer 3D, and a nifty indie I've been playing called Polara)

I'm more inclined to believe it has to do with game patching because even without Rosalina I still have the crashes. Enabling exception vectors only automatically reboots the 3DS, which is a bit quicker than having to push a button to shut down and then holding the power button until it boots back up but still not a fix.

I keep seeing "Use the legacy build" thrown around as a workaround and it doesn't fix anything for me. It simply isn't viable.

For what it's worth, B9S users can roll back to A9LH/Luma 7.1 IF you have a NAND backup from that setup. I do, so that's where I now sit. Severely outdated but stable.

 

[ihaveahax]

This can't be true. I was on the legacy build for a few weeks and still saw crashes. Mainly in Retroarch, NTRSelector, TWLoader, and a few games. (Mario Sports Superstars, Ridge Racer 3D, and a nifty indie I've been playing called Polara)

I'm more inclined to believe it has to do with game patching because even without Rosalina I still have the crashes. Enabling exception vectors only automatically reboots the 3DS, which is a bit quicker than having to push a button to shut down and then holding the power button until it boots back up but still not a fix.

I keep seeing "Use the legacy build" thrown around as a workaround and it doesn't fix anything for me. It simply isn't viable.

For what it's worth, B9S users can roll back to A9LH/Luma 7.1 IF you have a NAND backup from that setup. I do, so that's where I now sit. Severely outdated but stable.

if your same issues still occur on 8.1.1 (released today) please file an issue so it can be fixed in the next release: https://github.com/AuroraWright/Luma3DS/issues

it's hard to follow the forums for issues, having it all in one place makes everything easier and faster.

 

[Deleted-351540]

if your same issues still occur on 8.1.1 (released today) please file an issue so it can be fixed in the next release: https://github.com/AuroraWright/Luma3DS/issues

I will update just as soon as I can. Astronautlevel and I went at it troubleshooting a few weeks back and determined that it was safe to downgrade back to A9LH. We had me do all kinds of testing and in each case I had crashes. So I downgraded. If I find the thread, I'll link it here later. But basically, the legacy build didn't help at all.

I'll update back to B9S tonight, update to Luma 8.1.1 and let you know. Crashes are random, but mostly when starting an application.

Except Retroarch with any core. That damn thing crashes on exit every time, no matter what.

Edit: link to testing thread.
https://gbatemp.net/threads/13-different-games-crashing-boot-on-b9s-luma.474595/