Homebrew Random "An Error has ocurred. Please turn off the system and try again" message

[N64]

Well, the first time it occurred I thought it was just something random related to a homebrew, and then I started noticing it more. I finally put it to the test by turning on the 3ds, leaving it on the home screen, and just letting it sit for a bit while I went and ran some errands. Quite similar to the test you're about to do. I checked after an hour - no error. I left again. Checked after another hour - error. That's why I think it was 90 minutes (give or take minutes)

After I noticed the error the first time and rebooted, I could use wifi for a little bit but yes, the error became more frequent when I was actively using wifi (like visiting other towns or trying to play mario kart). It wasn't immediate though. Instead of the 90 minutes, it was probably more like 30-45 when I was actively using wifi.

Since N is not in your country, one other option you have is to buy a 3ds with broken screens or something, and use the parts from it to repair the issue (if it turns out not to be the SD card). for simplicity, I really hope it is the SD card and not something on the system board.

 

[Matezoide]

Well, the first time it occurred I thought it was just something random related to a homebrew, and then I started noticing it more. I finally put it to the test by turning on the 3ds, leaving it on the home screen, and just letting it sit for a bit while I went and ran some errands. Quite similar to the test you're about to do. I checked after an hour - no error. I left again. Checked after another hour - error. That's why I think it was 90 minutes (give or take minutes)

After I noticed the error the first time and rebooted, I could use wifi for a little bit but yes, the error became more frequent when I was actively using wifi (like visiting other towns or trying to play mario kart). It wasn't immediate though. Instead of the 90 minutes, it was probably more like 30-45 when I was actively using wifi.

Since N is not in your country, one other option you have is to buy a 3ds with broken screens or something, and use the parts from it to repair the issue (if it turns out not to be the SD card). for simplicity, I really hope it is the SD card and not something on the system board.

90 minutes or so, eh? My 3DS doesnt last that long even without actively using the Wi-Fi. It is something closer to 20 minutes on my end, which makes me feel safer. I really hope it is just the SD, because getting it fixed around here, while still possible, is going to be a major pain.

 

[Matezoide]

Welp, i inserted the old SD card on my computer and now it can not be open at all.

Tested my old 3DS' card and it opened perfectly. It appears the error, indeed, was showing the SD card was dying. I can not even use it anymore, as even an attempt to format it was met with failure, and the 3DS is incapable of reading it (Despite knowing it is inserted).

However, i just so happened to have made a backup yesterday just in case for this. I have the .bin files for both SysNAND and EmuNAND, as well as an image archieve made from USB Image Tool. It will set me slighty behind in Fire Emblem, but thats hardly a big issue.

I can rest far easier now, if i am to be honest, as this all but confirms the problem was the SD card. I'll leave it one more hour sitting on without any card and see what happens.

EDIT: After testing and no crashes, it should be safe to say the error was on the SD card. It was likely dying and the crashes were a result of that.

First format your new SD with Panasonic SD Formatter. Then using the old SD in the 3DS, get into EmuNand9. Dump your EmuNAND bin. Unmount the SD without leaving EmuNand9 (select). Put your old SD in your computer and copy the contents to someplace there. Put your new SD in the 3DS. Go back to main EmuNand9 menu and do SD Format Options/Format SD (EmuNAND default). Unmount new SD. Put it in the computer and copy the old SD contents over. Put it back in the 3DS. Choose EmuNAND Manager Options. Restore file to EmuNAND. Select your bin file. Voila!

Unfortunately, now that the SD is bused, i can not do this.

However, i still have the .bin files (Both for Emu and SysNAND) and an Image Archieve made from USB Image Tool. Would it still be possible to use these .bin files even without the original SD Card, or should i try to restore this Image into a new SD card through EaseUS Partition Master? If i can use the .bin files, how so?

 

[Quantumcat]

Good work making the backups, I hope others learn from your experience and make frequent backups too :-)

 

[Ricken]

Happens to me whenever I run Sliderhax on a formatted 9.2 first time. it just happens

 

[regnad]

Well, there is a 3dsx version of EmuNand9 that you can run on HBL.

Worst case you can put a new SD in, let the 3DS set up necessary files (make sure to open up the theme menu to set up those files too). Use browserhax to set up menuhax, use HBL to open EmuNand9, then choose SD Format Options/Format SD (EmuNAND default). Unmount SD (select), put it in the computer, but your EmuNAND bin on it, put the SD back in the 3DS, and go back to main Emunand9 menu. Choose EmuNAND Manager Options. Restore file to EmuNAND. Select your bin file.

You will have lost all of your games and all of your saves I believe.

Ideally you can somehow access your old SD.

Does anyone more knowledgable than me know any way to recover the data?

 

[Matezoide]

Well, there is a 3dsx version of EmuNand9 that you can run on HBL.

Worst case you can put a new SD in, let the 3DS set up necessary files (make sure to open up the theme menu to set up those files too). Use browserhax to set up menuhax, use HBL to open EmuNand9, then choose SD Format Options/Format SD (EmuNAND default). Unmount SD (select), put it in the computer, but your EmuNAND bin on it, put the SD back in the 3DS, and go back to main Emunand9 menu. Choose EmuNAND Manager Options. Restore file to EmuNAND. Select your bin file.

You will have lost all of your games and all of your saves I believe.

Ideally you can somehow access your old SD.

Does anyone more knowledgable than me know any way to recover the data?

Ah, so the saves and .cias arent inside EmuNAND.bin...no idea why i assumed it was.

However, i still have the Image file from USB Image Tool. If i were to decompress it with the correct tool, wouldnt it give me acess to my original files? I could just do your method, and then drag the files back in, no?

Regardless, there are some programs made to recover files from SD cards. I'll take a look and see what i can find, another back up cant hurt.

 

[regnad]

Ah, so the saves and .cias arent inside EmuNAND.bin...no idea why i assumed it was.

However, i still have the Image file from USB Image Tool. If i were to decompress it with the correct tool, wouldnt it give me acess to my original files? I could just do your method, and then drag the files back in, no?

The saves are encrypted in the Nintendo 3DS folder (unless it's a cart, and then it's on the cart).

I wasn't sure what you meant by the USB image. If that's what is (or was!) on your SD, then you are back in business!

--------------------- MERGED ---------------------------

Maybe you should reinject your SysNAND bin as well since you have everything still.

 

[Matezoide]

The saves are encrypted in the Nintendo 3DS folder (unless it's a cart, and then it's on the cart).

I wasn't sure what you meant by the USB image. If that's what is (or was!) on your SD, then you are back in business!


Maybe you should reinject your SysNAND bin as well since you have everything still.

Ah, good.

I do have to admit my knowledge on USB image is lacking, but based on my research, it does contain everything (As it was used on my SD yesterday and the size matches), since i took that idea from another tutorial on GBAtemp.

https://gbatemp.net/threads/how-to-transfer-emunand-to-another-sd-card-working-on-new3ds.383684/


As to reinjecting SysNAND bin, thats a good idea. However, i didnt actually see a ''Restore'' option...closest thing i saw when i used EmuNAND9 was ''Clone EmuNAND.bin to EmuNAND'', would you know if they are the same thing?

Bleh i really hate when a tutorial i see gives a name to a certain command and i can only find one that sounds similar lol


No luck on getting anything from the dead SD Card, however. EaseUS Data Recovery, just like my computer, does not ''see'' the SD card. Even though i will probably not need this, it could still come in hand, so does anyone know another recovery program for SD Cards?

 

[regnad]

Ah, good.

I do have to admit my knowledge on USB image is lacking, but based on my research, it does contain everything (As it was used on my SD yesterday and the size matches), since i took that idea from another tutorial on GBAtemp.

https://gbatemp.net/threads/how-to-transfer-emunand-to-another-sd-card-working-on-new3ds.383684/


As to reinjecting SysNAND bin, thats a good idea. However, i didnt actually see a ''Restore'' option...closest thing i saw when i used EmuNAND9 was ''Clone EmuNAND.bin to EmuNAND'', would you know if they are the same thing?

Bleh i really hate when a tutorial i see gives a name to a certain command and i can only find one that sounds similar lol


No luck on getting anything from the dead SD Card, however. EaseUS Data Recovery, just like my computer, does not ''see'' the SD card. Even though i will probably not need this, it could still come in hand, so does anyone know another recovery program for SD Cards?

Yes, that's it! Sorry, I didn't have my 3DS with me the check when I wrote that.

Here's a very explicit tutorial that's probably better than what I can tell you!

https://gbatemp.net/threads/tutorial-transferring-working-emunand-to-a-new-sd-card.411342/

 

[Matezoide]

Yes, that's it! Sorry, I didn't have my 3DS with me the check when I wrote that.

Here's a very explicit tutorial that's probably better than what I can tell you!

https://gbatemp.net/threads/tutorial-transferring-working-emunand-to-a-new-sd-card.411342/

Well, i cant really use that tutorial since the old SD isnt working anymore, haha.

But the small guide you described seems to be logical, so it could work nonethless.

 

[N64]

glad to see your problem was solved relatively easily, with very minimal loss of data

 

[regnad]

Well, i cant really use that tutorial since the old SD isnt working anymore, haha.

But the small guide you described seems to be logical, so it could work nonethless.

So did everything work out? Are you back up and running?

 

[Matezoide]

glad to see your problem was solved relatively easily, with very minimal loss of data

So did everything work out? Are you back up and running?

Alright, finally got back home.


Recovering the data itself was a complete sucess. My games and saves are perfectly fine, just the way i left it. Set back almost one entire chapter in Fire Emblem, but whatever.


I can only hope this will be able to solve the issue. I'll play for a bit more and see it crashes again. Should it crash, i'll attempt to play another game to make sure it isnt just Fire Emblem.

If needed, there are alternative places for fixing. It is possible my problem isnt entirely solved and the SD dying was a mere coincidence, but knowing my data is safe, alone, is an extreme relief.

Assuming the problem is somehow physical, it is most likely the Wi-Fi chip, which is fairly easy to resolve as long as i can get someone with the knowledge to open it.


Regardless, many thanks to everyone in this thread for the help. I do have to admit i did not expect all this support that quickly.

 

[regnad]

Surely this solves it!

 

[Matezoide]

Alright, in case anyone is interested or curious...

After playing for several hours, i can confirm there have been absolutely no crashes, so it was, indeed, the SD.


I am still having a fairly hard time believing it though, given how quickly everything happened...it took less than 48 hours for it to go from absolutely perfect to crashing a few times to becoming completely useless! But at this point, it would be nothing but foolish of my part to believe otherwise.

Again, you all have been of extreme help, and i give you my thanks.