Hacking Problems with my N3DS

  • Thread starter Thread starter Deleted User
  • Start date Start date
  • Views Views 3,863
  • Replies Replies 20
D

Deleted User

Guest
Could somebody help me here please?

My N3DS no longer boots after installing the homebrew launcher cia.
Black Screen after boot. I turn the 3DS off and get this Error Message:

An exception occurred

Processor: ARM 11 (core 1)
Exception type: prefetch abort (kernel panic)
Current process: ptm (0004013000002202)

I can still go into the Luma3DS chainloader.
 
I get the same Error Message.
Determine if your n3DS has something informally known as a "gamecoin-type" softbrick.
  1. Reinsert the microSD card back into the n3DS.
  2. Go to GodMode9 → [1:] SYSNAND CTRNAND → hold (R)-shoulder and press (X) on data folder → rename this to data2.
    • :!: Be careful that you don't press only the (X) button as this brings up delete option!
  3. Press (START) to exit GodMode9. If successful, the n3DS will ask you to make a new user profile setup.
Does the n3DS still throws the ARM11 error?
 
Determine if your n3DS has something informally known as a "gamecoin-type" softbrick.
  1. Reinsert the microSD card back into the n3DS.
  2. Go to GodMode9 → [1:] SYSNAND CTRNAND → hold (R)-shoulder and press (X) on data folder → rename this to data2.
    • :!: Be careful that you don't press only the (X) button as this brings up delete option!
  3. Press (START) to exit GodMode9. If successful, the n3DS will ask you to make a new user profile setup.
Does the n3DS still throws the ARM11 error?
I renamed data file to data2 and still get the ARM11 error.
 
I renamed data file to data2 and still get the ARM11 error.
4. Go back to GodMode9 → [1:] SYSNAND CTRNAND. Press (X) to delete the (dummy) data folder. Hold (R)-shoulder and press (X) to rename the (real) data2 back to data.
5. Repair the 3DS firmware + custom firmware with CTRTransfer (Type D9) - CTRTransfer. See the page's Instructions. If you have a spare (preferably) 4 GB microSD card, perform this alternative CTRTransfer on this second card over your main card. The smaller card will be faster to hardware test in H2testw.
Edit - Sorry, I accidentally linked to the standard CTRTransfer. Meant to say use the one from that gm9 script.
 
Last edited by TurdPooCharger,
4. Go back to GodMode9 → [1:] SYSNAND CTRNAND. Press (X) to delete the (dummy) data folder. Hold (R)-shoulder and press (X) to rename the (real) data2 back to data.
5. Repair the 3DS firmware + custom firmware with CTRTransfer (Type D9) - CTRTransfer. See the page's Instructions. If you have a spare (preferably) 4 GB microSD card, perform this alternative CTRTransfer on this second card over your main card. The smaller card will be faster to hardware test in H2testw.
Edit - Sorry, I accidentally linked to the standard CTRTransfer. Meant to say use the one from that gm9 script.
Thank you for your help so far. I will report back after the next steps are completed!
 
I have a O3DS somewhere. I still have the NAND backup for my N3DS. Can I use it to restore the 3DS?
I'm not sure if restoring that n3DS previously backed up SysNAND *.bin image will work. That CTRTransfer (Type D9) you ran works very similar to a SysNAND Restore at the most fundamental level.

If that ARM11 error is still present despite the CTRTransfer (Type D9), adjusted settings in Luma3DS v#.# configuration, battery trick, and gamecoin-type softbrick check, this points to a serious hardware failure.

The prime suspect of that failure would be the eMMC (NAND chip). There is a way to diagnosis this condition with that script, but there's a chance of "super (soft)bricking" if the test run goes wrong.

Edit - That's why the question if you happen to have an ntrboot flashcart.
 
Last edited by TurdPooCharger,
I'm not sure if restoring that n3DS previously backed up SysNAND *.bin image will work. That CTRTransfer (Type D9) you ran works very similar to a SysNAND Restore at the most fundamental level.

If that ARM11 error is still present despite the CTRTransfer (Type D9), adjusted settings in Luma3DS v#.# configuration, battery trick, and gamecoin-type softbrick check, this points to a serious hardware failure.

The prime suspect of that failure would be the eMMC (NAND chip). There is a way to diagnosis this condition with that script, but there's a chance of "super (soft)bricking" if the test run goes wrong.

Edit - That's why the question if you happen to have an ntrboot flashcart.
Good News! I restored the NAND with my backup NAND and everything is working again!!:)
I don´t know why, but it worked. Thank you for your time and patience.
 
  • Like
Reactions: TurdPooCharger
Good News! I restored the NAND with my backup NAND and everything is working again!!:)
I don´t know why, but it worked. Thank you for your time and patience.
Hmm, I have so many questions... Hey, if your restored sysnand is from an older firmware, can you report what's the n3DS stability after system updating back it to 11.13E?
 
My Firmware status is now Sys 11.5.0-38E. That´s pretty much all I can say.
 
Last edited by ,
Is this something I have to do with Luma or Godmode9?
  • System Settings → Other Settings → System Update
***

If you wish to manually restore your user profile settings, (Type D9) pulled copies of the data (user profile), dbs (for the tickets in ticket.db), and private (contains movable.sed with encryption KeyY tied to a specific sdmc:/Nintendo 3DS/<ID0> library of games/dlcs/updates) folders out of the [1:] SYSNAND CTRNAND.
  • sdmc:/gm9/out/<date>_<serial>_sysnand ctrnand_000
Also, any DSiWare games & saves you have were backed up at:
  • sdmc:/gm9/out/<date>_<serial>_dsiware_000
 
Last edited by TurdPooCharger,
  • Like
Reactions: Deleted User

Site & Scene News

Popular threads in this forum