Hacking Am exeption occurred for N3DS CFW

  • Thread starter Thread starter lyokohack
  • Start date Start date
  • Views Views 6,862
  • Replies Replies 34

lyokohack

Well-Known Member
Member
Joined
Apr 2, 2018
Messages
323
Reaction score
28
Trophies
0
Age
29
XP
1,193
Country
France
Hi everybody

I just bought a new 3DS LL which hacker under Frimware "11.4.0-37E"

then I meet two problem

1- when I start this game game this game does not start and I have this error

Am exeption occurred


Code:
Processor : ARM11(core1)
Exeption type : prefetch abort (svrBreak)
Current process : loader (0000000000000000)

You can find a dump in the following file:

dumps/arm11/crash_dump_00000008.dmp

press any button to shutdown


the other games work very well but in another game I don't remember its name this game has suffered a crash


2- second problem when I turn off the console I have this happens after playing my unit game after being installed for the first time

Code:
Am exeption occurred
Processor : ARM9
Exeption type : prefetch abort (svcBreak)
You can find a dump in the following file:
dumps/arm9/crash_dump_00000010.dmp

press any button to shutdown

i use as cia conversion plugin for the unit which is called "3DS Simple CIA Converter v5.0"
 
When you boot the system while holding Select, which version of Luma3DS is displayed at the top of the configuration settings page?
 
  • Like
Reactions: Alexander1970
Thanks for your help

but I don't have Luma3DS in my console

I only have FBI that it allows me to install my .cia, because I bought it this console already hacker

this first game is called "minecraft new nintendo 3ds edition" because I forgot to write it
 
Last edited by lyokohack,
TurdPooCharger I'm wondering if you've come across specific games that run into crashes, AiRace: Speed (specifically speed, Xeno never froze on me) crashes a bunch on me. If no, I'm gonna probably run through your classic SD regimen, probably aughta do it anyways

EDIT: for what it's worth, this happens whether I overclock or not
ANOTHER EDIT: I do not wish to take up any of TurdPooCharger's time with this, I beat the game in question already, just wondering.
 
Last edited by yuyuyup,
Thank you for your answers

but when I press (R) and (A) nothing happens

I have restoration options in FBI, but I don't touch anything (because it's the first time I use the 3DS).
 
-snip-
... when I press (R) and (A) nothing happens

I have restoration options in FBI, but I don't touch anything (because it's the first time I use the 3DS).
1. As described in post #4, test the hardware condition of the empty microSD card.
  • [3ds.hacks.guide] H2testw (Windows) {français}
  • Keep the card if it's [GOOD]. Replace the card if it's [BAD].
  • h2testw_menu-png.210567
    h2testw_results-png.210862

2. Turn on the n3DSLL → press and hold (SELECT) button → Luma3DS v#.# configuration.

3. After updating the custom firmware, update the SD setup and 3DS firmware.

4. Try all the listed troubleshooting ideas for games that don't play or launch.

These later steps depends if the above steps 1–4 did not fix your problems.

5. Salvage the games, dlcs, updates, saves, and extdata in the Nintendo 3DS folder like in these examples.

6. Repair the 3DS firmware + custom firmware with CTRTransfer (Type D9) - CTRTransfer. Carefully read and follow the Instructions.
 
Last edited by TurdPooCharger,
  • Like
Reactions: Alexander1970
TurdPooCharger I'm wondering if you've come across specific games that run into crashes, AiRace: Speed (specifically speed, Xeno never froze on me) crashes a bunch on me. If no, I'm gonna probably run through your classic SD regimen, probably aughta do it anyways

EDIT: for what it's worth, this happens whether I overclock or not
ANOTHER EDIT: I do not wish to take up any of TurdPooCharger's time with this, I beat the game in question already, just wondering.
I have certain homebrew apps and games that do this as well. Namely TWiLight Menu ++, JK's Save Manager, Smash 3DS, and just about every single time I use the Rosalina menu. It just does it randomly, too. Open the Rosalina menu? Move fast. You might have 3 seconds or you might have 15 seconds. Usually no more than that. Playing a game with TWiLight? Save often. Might get 10 minutes, might get a few hours. Might not even happen. It doesn't happen on many games, including never happening with Virtual Console injects or on physical cartridges at all.

The weird part is that I setup a New Nintendo 3DS and a New Nintendo 2DS identically after going through TurdPooCharger's instructions above, including a CTRTransfer. I've just come to the conclusion that there is something defective with the 3DS. I bought it used the same time I bought the 2DS new. Both used the guide and both SD cards are identical (from WalMart) and tested good.

Edit to clarify: I bought the 3DS to hack and play injects and mod games offline and the 2DS to stay legit and play online. When the 3DS acted funky, I hacked the 2DS because I just don't care to play online and I prefer the 2DS screens.
 
Last edited by fatsocat,
@fatsocat,
  1. Battery trick.
  2. On another/spare (small sized, 4 GB minimum) SD card that has been checked+passed in H2testw, create a test setup.
    • SD & firmware setup: Luma3DS v10.1.3, GodMode9 v1.9.1, boot9strap v1.3, Sys 11.13.0-45U
    • Refer to the above post #8 in updating these.
    • Don't reuse your previous SD card, or the files from your main setup.
  3. FBI install an example .CIA games that are known to crash on your main setup.
  4. (Conditional) If yours an o3DS or o3DSXL, try playing the game with WiFi turned off.
    • This is to determine if the instability is due to disconnected or unseated WiFi board module.
    • You can also rule this out if visiting Nintendo eShop or Internet Browser works fine.
Does the test setup also crashes?
 
thanks a lot for your help

1- I checked my SD card here is the result



2- I try to stay pressed on the selection button (SELECT) but nothing happens

I think I don't have Luma3DS on my console
 
thanks a lot for your help

1- I checked my SD card here is the result

-snip-

2- I try to stay pressed on the selection button (SELECT) but nothing happens

I think I don't have Luma3DS on my console

That SD card is good. Delete the *.h2w test files.

Make sure the SD card was reformatted in [ FAT32 format | 32 KB cluster size | MBR disk | Primary partition ] as described in the step 2 from post #2 post #4.


Before adding back your files / main setup, check which custom firmware type your n3DSLL has. For step 2 from post #8,

After the n3DSLL has its custom firmware updated or upgraded to boot9strap v1.3, add back your files / main setup. Continue with the rest of post #8's steps 3–6.
 
Last edited by TurdPooCharger,
  • Like
Reactions: Alexander1970
@fatsocat,
  1. Battery Trick.
  2. On another/spare (small sized, 4 GB minimum) SD card that has been checked+passed in H2testw, create a test setup.
    • SD & firmware setup: Luma3DS v10.1.3, GodMode9 v1.9.1, boot9strap v1.3, Sys 11.13.0-45U
    • Refer to the above post #8 updating these.
    • Don't reuse your previous SD card, or the files from your main setup.
  3. FBI install an example .CIA games that are known to crash on your main setup.
  4. (Conditional) If yours an o3DS or o3DSXL, try playing the game with WiFi turned off.
    • This is to determine if the instability is due to disconnected or unseated WiFi board module.
    • You can also rule this out if visiting Nintendo eShop or Internet Browser works fine.
Does the test setup also crashes?
I finally got a chance to try this earlier today. I stopped by WalMart after reading this and picked up a spare 8Gb card. I needed one for my drone anyway.

It tested fine in h2testw but it took forever to verify. It got formatted using the new 3DS after testing the card. Afterwords, I removed the SD card and put it in my PC to transfer files grabbed from the "Finalize Setup" guide page. Luna is 10.1.3, boot9strap is 1.3, GM9 is 1.9.1, and the system is fully updated.

I didn't time it, but about 10 seconds after bringing up the Rosalina menu, it Arm9 crashed. I did not even need to install a CIA using FBI.
 
I finally got a chance to try this earlier today. I stopped by WalMart after reading this and picked up a spare 8Gb card. I needed one for my drone anyway.

It tested fine in h2testw but it took forever to verify. It got formatted using the new 3DS after testing the card. Afterwords, I removed the SD card and put it in my PC to transfer files grabbed from the "Finalize Setup" guide page. Luna is 10.1.3, boot9strap is 1.3, GM9 is 1.9.1, and the system is fully updated.

I didn't time it, but about 10 seconds after bringing up the Rosalina menu, it Arm9 crashed. I did not even need to install a CIA using FBI.
:(

When you tried CTRTransfer, was it the official standard CTRTransfer or the alternative CTRTransfer (Type D9)?


If standard CTRTransfer was done, the 3DS firmware might be slightly softbricked with a damaged file system for the [1:] SYSNAND CTRNAND. A damaged file system is kinda like a cabinet containing folders where some are misplaced or sorted in the wrong order. See if the (Type D9) variety helps.

If alternative CTRTransfer (Type D9) was instead done with no improvements, your o3DS is likely to have a hardware fault for the NAND chip (eMMC) or RAM memory. That CTRTransfer (Type D9) gm9 script has an feature called eMMC Status Checker if you wish to test whether the motherboard is going bad; it's basically H2testw for the NAND. If the o3DS passes the checker, it's likely faulty RAM.
 
  • Like
Reactions: Alexander1970
thanks a lot for your help

Make sure the SD card was reformatted in [ FAT32 format | 32 KB cluster size | MBR disk | Primary partition ] as described in the step 2 from post #2 post #4.

if i look in the windows format settings of my carte sd

i have

Code:
32 bytes


if i install boot9strap

my console
don't brick ?

I'm on firmware

11.4.0-37E
 
Last edited by lyokohack,
:(

When you tried CTRTransfer, was it the official standard CTRTransfer or the alternative CTRTransfer (Type D9)?


If standard CTRTransfer was done, the 3DS firmware might be slightly softbricked with a damaged file system for the [1:] SYSNAND CTRNAND. A damaged file system is kinda like a cabinet containing folders where some are misplaced or sorted in the wrong order. See if the (Type D9) variety helps.

If alternative CTRTransfer (Type D9) was instead done with no improvements, your o3DS is likely to have a hardware fault for the NAND chip (eMMC) or RAM memory. That CTRTransfer (Type D9) gm9 script has an feature called eMMC Status Checker if you wish to test whether the motherboard is going bad; it's basically H2testw for the NAND. If the o3DS passes the checker, it's likely faulty RAM.
It was definitely the standard CTRTransfer and not the D9 Type. I was unaware the Type D9 existed. The console is actually a New Nintendo 3DS, not an original one. I'll run through a CTRTransfer (Type D9) and see if that helps. I'm not too worried if it doesn't, but it would be nice to either have it as a backup console or keep one legit, albeit now modified. Will update when I'm done.
 
thanks a lot for your help

if i look in the windows format settings of my carte sd

i have

Code:
32 bytes

if i install boot9strap

my console
don't brick ?

I'm on firmware

11.4.0-37E
This website might help translating English → French.

***

The SD card has to be in those exact settings, or the 3DS won't be able to read & write to it. See close-up the provided image of quadruple reformat.
  • quadruple-reformat-png.174262

If not correctly formatted, the n3DSLL power indicator light (blue LED) will turn on and off. This happens because the custom firmware (boot9strap or arm9loaderhax) can't find or launch the FIRM or BIN payload off of the SD card or CTRNAND (internal memory drive).


***

(A) Updating B9S v1.0–1.2
-or-​
(B) Upgrading from A9LH

to​

B9S v1.3

will not brick your 3DS system.


You'll eventually want these updated on the n3DSLL.
  • boot9strap v1.3 - FIRM0 + FIRM1 partitions
  • SD card Luma3DS v10.1.3 - sdmc:/boot.firm
  • CTRNAND Luma3DS v10.1.3 - [1:] SYSNAND CTRNAND/boot.firm
  • SD card GodMode9 v1.9.1 - sdmc:/luma/payloads/GodMode9.firm
  • CTRNAND GodMode9 v1.9.1 (OPTIONAL) - [1:] SYSNAND CTRNAND/rw/luma/payloads/GodMode9.firm
  • Homebrew Launcher v2.1.1 - sdmc:/boot.3dsx
  • 3DS firmware Sys 11.13.0-45[J/U/E/C/K/T]
  • Various CIA and/or 3DSX homebrew apps of your preference and choice.

***

After everything has been updated, go back to the step 4 in post #8 when figuring out which games are crashing at launch or in-game play.
 
  • Like
Reactions: Alexander1970
@TurdPooCharger

My New Nintendo 3DS did not pass eMMC verification. I ran through the CTRTransfer twice just to be certain. Both times it failed eMMC Status Checks.

This was my initial assumption, so it is nice to have that verified. Since I also have a New Nintendo 2DS, I don't think I'll be trying to salvage this one and keep using it how I already am: for playing cartridges because it seems to work fine for that.

Thanks for the help! Is there any way I can donate for your excellent support?
 
@TurdPooCharger

My New Nintendo 3DS did not pass eMMC verification. I ran through the CTRTransfer twice just to be certain. Both times it failed eMMC Status Checks.

This was my initial assumption, so it is nice to have that verified. Since I also have a New Nintendo 2DS, I don't think I'll be trying to salvage this one and keep using it how I already am: for playing cartridges because it seems to work fine for that.
Oh wow!

You're the first recorded instance of someone who officially has a verifiable bad but somewhat working NAND chip. I wasn't sure how GodMode9 would react if it couldn't write to dead nand cells. My biggest fear would be that the feature crashing midrun and super softbricking an otherwise perfectly fine n3DS. I would absolutely hate for that to happen to anyone!!!

You can get around the problem of having a broken SysNAND by switching over to an EmuNAND setup.
  • [RELEASE] 3DS Multi EmuNAND Creator
  • GodMode9 → (HOME) button → More...SD format menuRedNAND size (min)Auto → etc.
    • Create the EmuNAND on an empty SD card.
    • Instead of Auto, select 32KB Clusters if the card is 4–64 GB. Select 64KB Cluster if its 128GB or bigger.
Due to the higher wear rate on the SD card where having an emulated NAND vastly increases reading & writing, I don't recommend EmuNAND on bigger cards. Basically, it's the too many eggs in a single basket problem, although this point might be moot as flash memory is getting cheaper over time. 128 GB microSD these days go for $15-20 online retail price.
32 GB is probably the sweet spot without shortening the flash memory life span too fast if your library of games is just a handful.

Special note is that DSiWare games won't work on EmuNAND if a copy of that game isn't installed on SysNAND.

If you do switch to an EmuNAND and ever mention having that in the general 3DS homebrew community, you might run into people who'll question you along the lines of "why? emunand is no longer useful or outdated.", be sure to tell them early on that your n3DS sysnand chip is physically busted. This will (or should) avoid unnecessary confrontation.

***

This is something to consider down the road for long term ownership or restoration. It's possible to replace the NAND chip.

Thanks for the help! Is there any way I can donate for your excellent support?
I'm flattered by your gratitude. Taking donations is something I have no vested interest in. Also, I am probably not the person who could accept that after having shared knowledge of the more questionable and dirtier aspects of 3DS custom firmware and homebrew. Those pursuits came at an ideological cost... It would be extremely hypocritical were I to accept anyone's money or payment.

My only (non-binding, totally up to you) request to anyone is that they visit the gbatemp threads of the 3ds homebrew apps they found interesting and to give likes to their pages. Small gestures lets the respective dev or creator knows their project/work is appreciated.

IF you still wish to donate money, it should go to a legitimate charity, foundation, or the patreon of another reputable dev around here who does good work. Whichever cause or project that is worthy to you.
 
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.
 

Site & Scene News

Popular threads in this forum