Hacking Am exeption occurred for N3DS CFW

[TurdPooCharger]

That's freaking cool I guess. I can absolutely verify that it not only failed eMMC Status checks, but failed it twice. GodMode9 did crash midrun, however it booted back up as if it were a completely newly formatted 3DS. All of my games and saves were gone, but I expected that. I can reinstall the tickets and stuff later.

Rosalina menu still crashes, which means I'm still in the same boat. I will definitely look into setting up emuNAND on the system as a quick and easy way to keep it alive. I suppose I better make that now before the NAND gets worse? As for DSiWare games, I'm not entirely sure what those are. I know that using VC injects for GBA, SNES, and NES won't cause a crash. I also know that using my Acekard 2 doesn't cause a crash, and since TWiLight Menu++ does crash, it is my current preferred way to play DS games on the New Nintendo 3DS. If I can use TWiLight Menu++ on emuNAND without having to install the game on NAND, that would be great. I only play about 15-20 DS games and about 5-6 homebrews and all of them are supported in TM++.

Pick a charity, good internet stranger. I'll gladly donate in your name. Or, if you prefer, I can setup six months of GBATemp Patreon for you. We'd just have to talk to a mod to ensure you're getting it and not me. I've never done Patreon, and I'm fairly new to GBATemp so I'm not sure how that'd work. But I'm sure we can do it! I scoped out your profile, and my god... The amount of support you hand out! You deserve it.

Did the eMMC Status Checker ever logged and dumped the results? If so, where did the failure occur?

• sdmc:/gm9/out/eMMC_text_report.txt

In case of write and test pass run failures, the script is supposed to automatically go straight to restoring the backed up sysnand *.bin image.

• sdmc:/gm9/out/nand_minsize.bin

A true midrun crash would be where GodMode9 freezes or errors out with a QR code like this. If that was to happen, the 3DS system would be super softbricked where the 3DS firmware + custom firmware is fully overwritten or in a wiped state of garbage mess. It would boot with Blue Screens of Death or bootrom 8046 like this. The only way to recover from that would be to ntrboot GodMode9 using a compatible DS flashcart and restoring the sysnand with that auto-preprepped dumped nand_minsize.bin image.

The missing HOME Menu games could be explained by how the 3DS firmware handles creating another <ID1> sudfolder found in the Nintendo 3DS folder when moving the game library between different SD cards. Check if your Nintendo 3DS folder has two <ID1> subfolders.

• sdmc:/Nintendo 3DS/<ID0>/<ID1>
• Have all the data from previous 3ds cfw sd card, want to transfer to a new SDcard. [post #9]

About creating the EmuNAND, you might need to rerun standard CTRTransfer on the EmuNAND to fix it as it'll adopt any data corruption or imperfection copied over from the SysNAND. Standard CTRTransfer might not work depending on the extent of damage to the file system.

Unfortunately, CTRTransfer (Type D9) wasn't coded to handle EmuNAND in mind as the general homebrew scene consensus was to move away from its usage. [Emu/Red]NAND had a much larger purpose in the haydays of 3DS custom firmware. Reworking the (Type D9) script to include handling EmuNAND might prove difficult due to running out of free space. GodMode9 restricts scripts from launching if they're bigger than 1.00 MB size. A separate recoded version might be needed for this ocassion.

***

@fatsocat, you don't owe anything to me or anyone. People have different reasons why they take up homebrewing whether as a user or as a dev. I'm just glad my lofty script could be of some help here. To me, that in itself is a small awarding rewarding experience knowing something I wrote works as intended.

I can't think of or recommend any charity, foundation, or patreon in particular. In this day and age, everything is highly politically charged and scrutinized. Choosing a cause means making a statement where one has to defend their stance or face against the onslaught of Karens and SJWs who have a bone to pick with why something you like is wrong in their eyes...

For a pretend scenario, I could suggest "please send money to the Glasses for Cats organization, thanks", and there will be those out there who'll argue, "NO! That donation should go to Felines LASIK Institute. They do better work than that hackjob group!"

 

[fatsocat]

@TurdPooCharger

It simply shut off. GM9 did this twice, both in the same spot. If you would like, I could do it again and record what happens. I'm inclined to believe that it is in fact restoring the NAND before it shuts off because it did say restoring some .bin file before it shuts off. I definitely never saw a blue screen or a QR code. Checking: sdmc:/gm9/out/ verified that it restored the bin image located in sdmc:/gm9/out/. I don't think this was a midrun crash and is intentional. I now also have a copy of the bin file from gm9/out, which I think would work as a way to create an emuNAND? (Nope, I reread your post. I'll have to do a standard CTRTransfer. Thats fine. Done it before.)

And see, I'm an idiot. All of my games are gone because I'm doing this on an 8Gb SD card and not my original. Duh. I'll bet that if I power off and reinsert my original SD card all of my games and saves come back like magic. Not that there are many.

Pre-post update: Yes. Reinserting my original SD card brought my games back. I'm now going to make an emuNAND and then CTRTransfer the emuNAND to fix it. Then see if it fixes my issues. Will update when I'm done.

 

[fatsocat]

@TurdPooCharger

Holy hell it works. I figured I might as well start over because I hadnt really played the games that were on there and was mainly using it as a glorified Nintendo DS with a flash cart and I thought it would just make things simpler. So I formatted the console using system settings with a bit of trepidation. It worked though. After that, I ran through the setup process.

I ran through the NAND backup process in GodMode9, then used that backup to create an emuNAND in GodMode9. Afterwords, I booted emuNAND to confirm it works. It did and it had the same problem as NAND: using Rosalina menu would force an error exception. So I booted back to emuNAND and followed this (I can't post links) 3ds.hacks.guide/ctrtransfer, except I specified doing it to emuNAND when asked. It booted back to emuNAND on version 11.5. I know I probably should have continued the guide, but I wanted to know if I was wasting my time. While on 11.5 emuNAND, I opened Rosalina menu and waited. And waited. And waited. 5 minutes later, Rosalina menu is still open and my console had not had an error! So I updated the console.

Is there a way to force boot emuNAND and not have to boot holding "Start" to open the chainloater menu?

 

[TurdPooCharger]

@TurdPooCharger

Holy hell it works. I figured I might as well start over because I hadnt really played the games that were on there and was mainly using it as a glorified Nintendo DS with a flash cart and I thought it would just make things simpler. So I formatted the console using system settings with a bit of trepidation. It worked though. After that, I ran through the setup process.

I ran through the NAND backup process in GodMode9, then used that backup to create an emuNAND in GodMode9. Afterwords, I booted emuNAND to confirm it works. It did and it had the same problem as NAND: using Rosalina menu would force an error exception. So I booted back to emuNAND and followed this (I can't post links) 3ds.hacks.guide/ctrtransfer, except I specified doing it to emuNAND when asked. It booted back to emuNAND on version 11.5. I know I probably should have continued the guide, but I wanted to know if I was wasting my time. While on 11.5 emuNAND, I opened Rosalina menu and waited. And waited. And waited. 5 minutes later, Rosalina menu is still open and my console had not had an error! So I updated the console.

Is there a way to force boot emuNAND and not have to boot holding "Start" to open the chainloater menu?

Right after turning on the n3DS, hold the (SELECT) button to access Luma3DS v10.1.3 configuration. If there is an EmuNAND installed on the SD card, this option should be present in the config list. Have these two options check marked. Press (START) to save, exit, and boot to HOME Menu.

• (x) Autoboot EmuNAND
• (x) Show NAND or user string in System Settings

To verify that the n3DS is booting to or running in EmuNAND, go to System Settings and look for Emu 11.13.0-45U.

Edit 1 - Format System Memory might not have been necessarily.

If the SysNAND still has the original setup (prior to format) or there's a backed up sysnand *.bin image,

• sdmc:/gm9/scripts/NANDManager.gm9 (this comes with the GodMode9 official github download)
• GodMode9 → (HOME) button → Scripts... → NANDManager →
  • <RIGHT> Transfer Sys to Emu (if the sysnand wasn't system formatted)
  • <Y> Restore EmuNAND (with that backed up [sys/emu]nand *.bin image)

1. (Re)-migrate and keep your original sysnand setup on the emunand.
2. Run the ctrtransfer on emunand to repair the damage.
3. Restore missing tickets with faketik app to repopulate missing games on HOME Menu.
4. If there are lots of games, mass unwrap gift icons using Cthulhu.
   
5. System update to Emu 11.13U.

Edit 2 - The above restoration of your old setup can be skipped. It's up to you on keeping what's been made or starting over. Whatever works in getting that n3DS working again with fully functional 3DS mode.

 

[fatsocat]

Right after turning on the n3DS, hold the (SELECT) button to access Luma3DS v10.1.3 configuration. If there is an EmuNAND installed on the SD card, this option should be present in the config list. Have these two options check marked. Press (START) to save, exit, and boot to HOME Menu.

• (x) Autoboot EmuNAND
• (x) Show NAND or user string in System Settings

To verify that the n3DS is booting to or running in EmuNAND, go to System Settings and look for Emu 11.13.0-45U.

Edit 1 - Format System Memory might not have been necessarily.

If the SysNAND still has the original setup (prior to format) or there's a backed up sysnand *.bin image,

• sdmc:/gm9/scripts/NANDManager.gm9 (this comes with the GodMode9 official github download)
• GodMode9 → (HOME) button → Scripts... → NANDManager →
  • <RIGHT> Transfer Sys to Emu (if the sysnand wasn't system formatted)
  • <Y> Restore EmuNAND (with that backed up [sys/emu]nand *.bin image)

1. (Re)-migrate and keep your original sysnand setup on the emunand.
2. Run the ctrtransfer on emunand to repair the damage.
3. Restore missing tickets with faketik app to repopulate missing games on HOME Menu.
4. If there are lots of games, mass unwrap gift icons using Cthulhu.
   
5. System update to Emu 11.13U.

Edit 2 - The above restoration of your old setup can be skipped. It's up to you on keeping what's been made or starting over. Whatever works in getting that n3DS working again with fully functional 3DS mode.

Yes, the option to show NAND or user string in System Settings and the option to Autoboot EmuNAND are both present and are now enabled. It does indeed boot to emuNAND and confirmed in system settings. Awesome!

I do have a NAND backup from just after I installed B9S to it. It would have some of my saves but they would be outdated. I do have the GM9 backup of the NAND used for creation of emuNAND, but I formatted the (barely) used system before so it is empty. My SD card backup does have saves and my Nintendo folder, but I'm not too worried about it. Most of my main 3DS game saves are on my New Nintendo 2DS XL.

I've installed one of the few homebrew softwares that would almost always cause a producible error exception and tried it. JK's Save Manager. I've had it open for about 15 minutes now and it hasn't crashed. This is promising because it never did that before. I am now considering the New Nintendo 3DS fixed for my needs. I've noticed that it does in fact boot slower which makes me think that more installed games and software will continue to slow the system down. As I really only wanted this for a portable emulation setup and Retroarch/standalone emulators caused an error exception, I will now setup the machine with all the standalone emulators instead of a boatload of virtual console injects.

Thanks again, friend. You've been a massive help getting my console back in working order. Hell, I didn't even know there was a problem. I just assumed error exceptions were a thing on New Nintendo 3DS's but not on New Nintendo 2DS XL's.

 

[lyokohack]

thank you very much for your help


I write this message with https://www.deepl.com/translator

how did you know I was translating my message?

1- I just tried the formatting (quadruple) but when I use "guiformat" it refuses to format my card with this parameter 32768

guiformat automatically suggests 16384 and it formatted it with

the other stages of the quadruple work perfectly



2- and quad I tried to update to boot9strap-1.3, I can't find a Luma3DS folder in my sd card to continue the copy of the update method,

Here's what's on my SD card for my hack.

 

[TurdPooCharger]

thank you very much for your help


I write this message with https://www.deepl.com/translator

how did you know I was translating my message?

1- I just tried the formatting (quadruple) but when I use "guiformat" it refuses to format my card with this parameter 32768

guiformat automatically suggests 16384 and it formatted it with

the other stages of the quadruple work perfectly



2- and quad I tried to update to boot9strap-1.3, I can't find a Luma3DS folder in my sd card to continue the copy of the update method,

Here's what's on my SD card for my hack.

-snip-

@lyokohack, download and rename these two versions of SafeB9SInstaller v0.0.7.

• SafeB9SInstaller.firm → boot.firm
• SafeB9SInstaller.bin → arm9loaderhax.bin

Here is where to download boot9strap v1.3.

***

When following these guides,

• Updating B9S (Mettre à jour B9S)
• A9LH to B9S (Mise à jour vers boot9strap) *

, place the files on the SD card like this.

• sdmc:/boot9strap/boot9strap.firm
• sdmc:/boot9strap/boot9strap.firm.sha
• sdmc:/boot9strap/secret_sector.bin (New 3DS series only) *
  
• sdmc:/arm9loaderhax.bin (BIN version of SafeB9SInstaller)
  
• sdmc:/boot.firm (FIRM version of SafeB9SInstaller)

***

After upgrading or updating to B9S v1.3, delete those above five (5) files.


Download and add Luma3DS v10.1.3 to the SD card.

• sdmc:/boot.firm (Luma3DS)

Follow this guide.

• Finalizing Setup (Finalisation de l’installation)

To make this slightly easier, here is a CFW starter kit. The following will need to be completed.

1. System update the 3DS firmware to Sys 11.13.0-45E.
2. Install homebrew apps onto the HOME Menu (*.cia versions) and/or Homebrew Launcher (*.3dsx versions).
3. Install CTRNAND Luma3DS. This is to allow the 3DS system to boot without an SD card.
4. Make a backup copy of the SysNAND *.bin image. Keep this file safe on computer or external drive.

 

[lyokohack]

thank you very much for your help

I realized what you told me...

but I didn't use this file "secret_sector.bin" (I have a doubt for my console (I have a new 3DS LL ? ))
and under firmware 11.4.0-37E

so should I put it on or not ?


when I switch to the Download play Nintendo app and I realize and then " I quit the app to go to the "Homebrew Launcher" step.

when I switch to the Nintendo Download play application and then select "“Switch the hb. title to the current app." "Homebrew Launcher" step and run Nintendo Download play

I have the problem of

 Am exeption occurred

Processor : ARM11(core1)
Exeption type : prefetch abort (svrBreak)

 

[TurdPooCharger]

but I didn't use this file "secret_sector.bin" (I have a doubt for my console (I have a new 3DS LL ? ))
and under firmware 11.4.0-37E

so should I put it on or not ?

All New 3DS series [ New 3DS | New 3DS XL | New 3DS LL | New 2DS XL | New 2DS LL ] from any region [ JPN | USA | EUR | KOR ] has this file.

The secret_sector.bin is also known by this other name.

• [S:] SYSNAND VIRTUAL/sector0x96.bin

If your n3DSLL has the older A9LH custom firmware, secret_sector.bin is required to upgrade A9LH → B9S.


If your n3DSLL has the newer B9S custom firmware but an outdated version, having this file there or missing at:

• sdmc:/boot9strap/secret_sector.bin

, the SafeB9SInstaller (FIRM version) will still update B9S v1.0 → B9S v1.3.

when I switch to the Download play Nintendo app and I realize and then " I quit the app to go to the "Homebrew Launcher" step.

when I switch to the Nintendo Download play application and then select "“Switch the hb. title to the current app." "Homebrew Launcher" step and run Nintendo Download play

I have the problem of

 Am exeption occurred

Processor : ARM11(core1)
Exeption type : prefetch abort (svrBreak)

Can you take clear picture of this crash, and upload/post the picture here? Your error is not expected.

This is the common error new users usually encounter with Homebrew Launcher.

An exception has occurred
Processor: ARM11 (core 1)
Exception type: undefined instruction
Current process: loader (0000000000000000)

This problem is due to missing new-hbmenu.

• sdmc:/boot.3dsx

 

[lyokohack]

thank you very much for your help

I'm trying to download this file.



but the website doesn't give me access to download this file.

 

[Lacius]

thank you very much for your help

I'm trying to download this file.



but the website doesn't give me access to download this file.

You need a bittorrent client installed, such as qBittorrent.

 

[TurdPooCharger]

thank you very much for your help

I'm trying to download this file.
-snip-
but the website doesn't give me access to download this file.

I forgot to add this bit of info. You might also need to put aeskeydb.bin in there if you get the “OTP Crypto Fail” error. That one requires a bittorrent to download, too.

• sdmc:/boot9strap/aeskeydb.bin (A9LH to B9S, Section II - Installation de boot9strap)
• sdmc:/boot9strap/boot9strap.firm
• sdmc:/boot9strap/boot9strap.firm.sha
• sdmc:/boot9strap/secret_sector.bin (New 3DS series only) *
  
• sdmc:/arm9loaderhax.bin (BIN version of SafeB9SInstaller)
  
• sdmc:/boot.firm (FIRM version of SafeB9SInstaller)

 

[lyokohack]

thanks a lot for your help

after installing of the bittorrent i have access to download files
so thank you both

after adding the files the files you told me

when I insert my SD card into my 3DS

I find myself under the SafeB9SInstaller installation screen and I realize the combination keys, and that the installation ends i was not find myself in the configuration of luma3DS

the console reboots to launch the installation menu of SafeB9SInstaller

(it looks like the installation is looping)

I think this is the cause of my problem

 

[TurdPooCharger]

@lyokohack, late reply. After you run the SafeB9SInstaller, delete the six (6) files and folders mentioned in post #32.

Revisit post #27 about reinstall Luma3DS v10.1.3 and the Finalizing Setup. If you don't know what to add to the microSD card, here's a CFW starter kit. Make sure you

• Install CTRNAND Luma3DS so the n3DSXL knows how to turn on without the microSD card.
  
• System update to 11.13.0-45E.
• Backup the SysNAND *.bin image.
• Know how to Rosalina menu inject Homebrew Launcher.

 

[lyokohack]

I am very sorry for my very answer ervry late reply.

I was too tired at that time, I was able to take it all back after all that time.

I ask you not to take me for one who forgets the help of his teachers, I'm really sorry.

Fortunately, I was able to solve this problem, thanks to you, by taking your excellent CFW kit.

it saved me several frustration attempts

thank you very much for your famous help

Congratulations dear you have solved this problem of "Am exeption occurred" of this topic.