Hacking Followed the guide perfectly, "exception occurred error"

[pwnsweet]

Thanks in advance for your time,

Here's the situation:
Been out of the scene for a long time. New3DS on 9.0.0.0-20E sysNAND with a 9.5 emuNAND that was created with Gateway long ago, autobooting into that emuNAND using themehax and reiNAND CFW. Followed the guide over at 3ds.guide exactly every step of the way with the only exception being that I needed to use fasthax instead of udsploit to be able to successfully run safehax. Safehax booted. Safety checks completed, button combo entered, pressed A which rebooted the machine and put me into the Luma3DS configuration menu. I selected "show NAND or user string in System Settings" and pressed Start. I was met with the following:

Now, everytime I boot my n3ds, I get this screen. If I hold Select during boot, I get to the Luma3DS config menu. With no microSD card inserted at all, the machine turns on, screen stays black for 1 sec and turns off again. Can someone please advise on the best way forward? I've helped a lot of people in the past with Wii hacking but I've been so long out of the loop on 3DS stuff that I'm the one needing help now. Is my 3ds dead?

 

[Lacius]

Out of curiosity, what happens when you select the setting to Autoboot emuNAND in the Luma3DS configuration settings?

 

[pwnsweet]

Out of curiosity, what happens when you select the setting to Autoboot emuNAND in the Luma3DS configuration settings?

It takes me to my emuNAND. I guess that's confirmation that my 3DS isn't dead. That's a huge relief. Still, I can't boot into sysNAND at all which is somewhat concerning.

 

[Lacius]

It takes me to (what looks exactly like) my emuNAND

You should be able to fix your problem with booting into sysNAND by clearing your home menu’s extdata. However, instead of doing that, it might be easier to just copy your emuNAND to your sysNAND following this guide, since you don't need to be using emuNAND anymore: https://3ds.guide/move-emunand

 

[pwnsweet]

Ok Lacius I'll give it a shot and report back soon.

 

[pwnsweet]

Everything seems to be OK now. emuNAND is now my sysNAND and I'm in the process of making a NAND backup and updating to 11.5. Thank you so much for your immediate and pertinent help Lacius. Very professional.

 

[DocKlokMan]

Everything seems to be OK now. emuNAND is now my sysNAND and I'm in the process of making a NAND backup and updating to 11.5. Thank you so much for your immediate and pertinent help Lacius. Very professional.

If you want to know why it happened it's because you still had menuhax on your sysNAND. Menuhax causes a purposeful crash to get Homebrew Launcher to load, but after you put Luma on it, it just crashes and produces an error log. Had you removed menuhax or cleared your Home menu ext data then everything would be fine (you could have also booted without your SD card and then re-inserted it after the Home menu loaded).

 

[FateForWindows]

Also, note that udsploit and fasthax both work just the same for loading safehax.

 

[Kazuma77]

If you want to know why it happened it's because you still had menuhax on your sysNAND. Menuhax causes a purposeful crash to get Homebrew Launcher to load, but after you put Luma on it, it just crashes and produces an error log. Had you removed menuhax or cleared your Home menu ext data then everything would be fine (you could have also booted without your SD card and then re-inserted it after the Home menu loaded).

You beat me to it All he needed to do was boot without the card, insert the card, and set a theme, but, as long as he got it fixed. This is why he should have used InScripted instead of the guide. He could have just run Legacy, set a theme, then rebooted into regular Luma. Dirty hack or not, it's still good for fixing issues like this.

 

[Lacius]

You beat me to it All he needed to do was boot without the card, insert the card, and set a theme, but, as long as he got it fixed. This is why he should have used InScripted instead of the guide. He could have just run Legacy, set a theme, then rebooted into regular Luma. Dirty hack or not, it's still good for fixing issues like this.

There was no need for any of this when the guide was clear about transferring one's emuNAND to one's sysNAND.

 

[Greymane]

Simply deleting the folder in nintendo 3ds, also works

• EUR Region: Delete 00000098
• JPN Region: Delete 00000082
• USA Region: Delete 0000008f
• CHN Region: Delete 000000A1
• KOR Region: Delete 000000A9
• TWN Region: Delete 000000B1

 

[Kazuma77]

There was no need for any of this when the guide was clear about transferring one's emuNAND to one's sysNAND.

It's an optional step. Not something that is, nor should be, forced down anyone's throat. I recommend it personally, but, if someone wants to keep their NANDs the way they are, they should be able to.

InScripted does not limit you to one CFW and one app, has GW already setup for those that want it, does not make you click 50 different links and do a bunch of copying and renaming manually, is thoroughly drag and drop, performs the entire installation via a single script, and allows you to alter your chainloader setup in any way imaginable without making a trip to your PC. It has scripts for changing the default payload and chainloader. It has an alternate BootCTR9 configuration that acts like Arm9Select so you can rename payloads in GM9 to change hotkeys (without switching to an inferior chainloader). Plus countless other extra features added by optional scripts. But if you still want to use the guide, that's your call.

 

[Lacius]

It's an optional step. Not something that is, nor should be, forced down anyone's throat. I recommend it personally, but, if someone wants to keep their NANDs the way they are, they should be able to.

InScripted does not limit you to one CFW and one app, has GW already setup for those that want it, does not make you click 50 different links and do a bunch of copying and renaming manually, is thoroughly drag and drop, performs the entire installation via a single script, and allows you to alter your chainloader setup in any way imaginable without making a trip to your PC. It has scripts for changing the default payload and chainloader. It has an alternate BootCTR9 configuration that acts like Arm9Select so you can rename payloads to change hotkeys (without switching to an inferior chainloader). Plus countless other extra features added by optional scripts. But if you still want to use the guide, that's your call.

The guide also says exactly what to do in the case of a black screen on boot after installing B9S.

 

[Baoulettes]

Simply deleting the folder in nintendo 3ds, also works

• EUR Region: Delete 00000098
• JPN Region: Delete 00000082
• USA Region: Delete 0000008f
• CHN Region: Delete 000000A1
• KOR Region: Delete 000000A9
• TWN Region: Delete 000000B1

This, it should be saved somewhere if it is not for these rare person that still use old hack and a day maybe they want to move out

 

[Lacius]

This, it should be saved somewhere if it is not for these rare person that still use old hack and a day maybe they want to move out

It's in the 3ds.guide.

 

[Greymane]

It's in the 3ds.guide.

It is indeed, most basic problems can be solved with the troubleshoot portion of the guide.

 

[Kazuma77]

The guide also says exactly what to do in the case of a black screen on boot after installing B9S.

Well, that's not what this was. It was a crash. But, their problem is solved, so, no point in continuing this. Scripts will end guides, though. The 3DS can't make a mistake following them.

 

[Quantumcat]

Well, that's not what this was. It was a crash. But, their problem is solved, so, no point in continuing this. Scripts will end guides, though. The 3DS can't make a mistake following them.

The person writing the script can make mistakes though (I don't think I would follow one written by you).

 

[Kazuma77]

The person writing the script can make mistakes though (I don't think I would follow one written by you).

They've all been tested thoroughly on multiple systems. Also, I've been writing batch files since DOS 6.0, so, if you can't trust one I've written, then what can you trust? Also, consider your personal attack reported.

 

[Lacius]

They've all been tested thoroughly on multiple systems. Also, I've been writing batch files since DOS 6.0, so, if you can't trust one I've written, then what can you trust? Also, consider your personal attack reported.

That wasn't a personal attack. I don't agree with some of your above views regarding how a 3DS should be hacked, so I don't think I would use one of your scripts either.