Homebrew Luma3Ds Old Exception Error

AaronBrokeHisOld3DS

Member
Newcomer
Joined
Dec 20, 2018
Messages
5
Reaction score
0
Trophies
0
Age
21
XP
83
Country
United States
So I had installed Homebrew for 11.9 on an OLD Nintendo 3ds running 11.9 and Lumas CFW, FBI, G9 and all the typical stuff you download but the problem came in when I downloaded FreEshop (yes ik it’s bad but I have my reasons) and at first it worked until I need to put the Key URLs in because FreEshop is kind of dead. So I took the SD card out just to check something and when I put it back in and turned on the power I got “an exception occurred
Processor: ARM11 (core 1)
Exception type: prefetch abort (svcBreak)
Fault status: Debug event
Current process: pm

I am still able to access the Luma Menu and God Mode menu but I can’t turn the actual 3ds on any help to fix this?
 
So I had installed Homebrew for 11.9 on an OLD Nintendo 3ds running 11.9 and Lumas CFW, FBI, G9 and all the typical stuff you download but the problem came in when I downloaded FreEshop (yes ik it’s bad but I have my reasons) and at first it worked until I need to put the Key URLs in because FreEshop is kind of dead. So I took the SD card out just to check something and when I put it back in and turned on the power I got “an exception occurred
Processor: ARM11 (core 1)
Exception type: prefetch abort (svcBreak)
Fault status: Debug event
Current process: pm

I am still able to access the Luma Menu and God Mode menu but I can’t turn the actual 3ds on any help to fix this?
Freeshop is dead for good 2 weeks after 11.8 dropped
 
That is the point of Freeshop
I think you have not read the original post correctly the exception error is not happening when the op loads freeshop the exception error happens when he simply switches on his 3ds.
 
  • Like
Reactions: AaronBrokeHisOld3DS
Remove the battery, press and hold the (Power) button for 30 seconds, press several more times, reinsert the battery, and then turn on the o3DS without the SD card and without a game cart.

Try booting Recovery Mode, GodMode9, Luma3DS configuration, and HOME Menu.
Yes I quoted myself. If you can't boot at all without the card, you probably don't have Luma3DS on the CTRNAND. Try it again with the card.
 
Yes I quoted myself. If you can't boot at all without the card, you probably don't have Luma3DS on the CTRNAND. Try it again with the card.
Yeah I’m unable to boot it without and SD card

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

Yes I quoted myself. If you can't boot at all without the card, you probably don't have Luma3DS on the CTRNAND. Try it again with the card.
Also why would I need to take the battery out?
 
Yeah I’m unable to boot it without and SD card
So you can't boot the 3DS without the SD card? Am I reading this correctly?
  1. Take a spare SD card, copy everything off it onto a computer, and reformat it as FAT32 + 32 KB cluster size with Windows File Explorer or guiformat.
  2. Full Write + Verify the empty card with H2testw. This is to check for hardware defects and prevent bricking your 3DS. Do not skip this step.
  3. If the card passes, delete the *.h2w test files. However, replace the card if an error was reported.
    • Go back to step 1 if that spare card is a dud or faulty.
  4. Make a test CFW setup. You may use the starter kit found here. Hold off from using files from your main setup for the moment.
  5. Follow through the Updating B9S guide to update to boot9strap v1.3. Section VI will put Luma3DS v9.1and GodMode9 on the CTRNAND.
    • Browsing in GodMode9, you can delete any payload *.firm you do not wish keep by pressing (X). These can be found at:
      • 0:/luma/payloads (SD card)
      • 1:/rw/luma/payloads (SysNAND CTRNAND) * Be careful in this directory.
    • Or, rerun the Setup Luma3DS to CTRNAND gm9 script after figuring out which *.firm you don't want on the SD card to copy over to CTRNAND.
    • It's highly recommended you at least keep GodMode9.
  6. Update the 3DS firmware in System Settings and make a SysNAND backup *.bin image to keep safely on your computer or external drive.
Also why would I need to take the battery out?
Sometimes, the 3DS can hang in booting either from a failed wake up out of sleep mode or improper shut off / crashing. Battery removal and reinsertion can fix this by resetting or removing lingering RAM memory causing a boot hold up.
 
Last edited by TurdPooCharger,
Alright I went through those steps and it did not work. :/
Oh boy, here's where it's going to suck and get tricky.

First, make a backup of your current SysNAND. This is for the scenario your game progress & collection recovery proves quirky.
***

Whenever a 3DS system fails to boot HOME Menu, one would have to resort to restoring with a previously backed up, known working SysNAND *.bin image (not the one instructed above).

If a backed up NAND image was never made, you resort to:
If CTRTransfer does not work with GodMode9, you would attempt this again with Decrypt9WIP.

***

The problem with any of these recovery methods is that you'll lose tickets that cause the 3DS to semi-acknowledge the games; they won't appear on HOME Menu but will in:
  • System Settings → Data Management → Nintendo 3DS → Software

If after performing SysNAND Restore or CTRTransfer, check if your games are marked with X's. If they are, you'll need to follow the guide found in this thread to recovery the saves + extdata and lost tickets for games / DLCs / updates.

***

When it becomes quirky.

:!: If you do NOT see X's in the System Settings ... Software, you might have previously performed a Format System Memory or System Transfer. The encryption key in your movable.sed would have changed. This rendered your entire library unrecognizable.

Restore your SysNAND with the messed up *.bin image, follow through with CTRTransfer, and then check again for the X's.
  • If X's aren't seen, try following through with the guide from the "I made a NAND backup..." thread.
  • For further verification that your movable.sed matches with the Nintendo 3DS folder, we're going to have to take a look at your keyY.
 
Last edited by TurdPooCharger,
Oh boy, here's where it's going to suck and get tricky.

First, make a backup of your current SysNAND. This is for the scenario your game progress & collection recovery proves quirky.
***

Whenever a 3DS system fails to boot HOME Menu, one would have to resort to restoring with a previously backed up, known working SysNAND *.bin image (not the one instructed above).

If a backed up NAND image was never made, you resort to:
If CTRTransfer does not work with GodMode9, you would attempt this again with Decrypt9WIP.

***

The problem with any of these recovery methods is that you'll lose tickets that cause the 3DS to semi-acknowledge the games; they won't appear on HOME Menu but will in:
  • System Settings → Data Management → Nintendo 3DS → Software

If after performing SysNAND Restore or CTRTransfer, check if your games are marked with X's. If they are, you'll need to follow the guide found in this thread to recovery the saves + extdata and lost tickets for games / DLCs / updates.

***

When it becomes quirky.

:!: If you do NOT see X's in the System Settings ... Software, you might have previously performed a Format System Memory or System Transfer. The encryption key in your movable.sed would have changed. This rendered your entire library unrecognizable.

Restore your SysNAND with the messed up *.bin image, follow through with CTRTransfer, and then check again for the X's.
  • If X's aren't seen, try following through with the guide from the "I made a NAND backup..." thread.
  • For further verification that your movable.sed matches with the Nintendo 3DS folder, we're going to have to take a look at your keyY.
On this topic, I had to deal with missing tickets after a ctrtransfer myself.
ctrtransfer these days automatically backs up tickets that can be reinstalled afterwards with FBI, you should probably mention that when you are helping out people related to ctrtransfer.

But, in my case, a couple of games were still missing as well as all my homebrew. Not sure why, I must have messed up at some point and overwritten the ticket.db with the wrong one when I tried to do what is essentially a manual ctrtransfer in order to fix a brick. Anyway, what I ended up doing was going through a whole ordeal with editing config files on my router in order to add hosts entries for the title key site, so that tikShop would work on my 3DS. Which did get those two games back, and I ran tikSweep after.

But that made me think, this could be made so much easier. What if there was a tool that would simply reinstall missing tickets if a match is found on the title key database? And without requiring messing with a custom DNS just to get the site working?

I think this could be done as simply as merging tikShop and tikSweep into one, and simply replacing the DNS lookup with the hardcoded IP of the title key site (since the domain is expired), and it would achieve what I spent probably a few hours trying to do in a better way before finally giving up and spending an hour figuring out how to add hosts entries on my router, and in just a few minutes without any hassle. That would be the easy way to do it since it would essentially just be copy pasting some code (which I could do easily even not having much knowledge about 3DS homebrew development specifically), but the proper way to do it would be to check the SD card for data that has missing tickets, and only install those tickets, negating the need for deleting unused tickets afterwards and making the whole process much faster. That, I'm not sure how to do though.

I've seen several posts recently with people having missing tickets (and "X" in data management), so it seems there is a use for something like this.
 
Last edited by The Real Jdbye,
On this topic, I had to deal with missing tickets after a ctrtransfer myself.
ctrtransfer these days automatically backs up tickets that can be reinstalled afterwards with FBI, you should probably mention that when you are helping out people related to ctrtransfer.
I don't trust CTRTransfer enough to not lose tickets. I see CTRTransfer like a universal SysNAND restore. In fact, I myself have once lost tickets using it. It should be viewed and treated as a region changing and firmware recovery tool with caveats to look out for. As for dropping a mention that it'll keep tickets, good luck telling someone that when their tickets are not kept. Eh...

But, in my case, a couple of games were still missing as well as all my homebrew. Not sure why, I must have messed up at some point and overwritten the ticket.db with the wrong one when I tried to do what is essentially a manual ctrtransfer in order to fix a brick. Anyway, what I ended up doing was going through a whole ordeal with editing config files on my router in order to add hosts entries for the title key site, so that tikShop would work on my 3DS. Which did get those two games back, and I ran tikSweep after.
tikSweep sucks at its purpose. Use FBI to delete unused tickets.

Your mentioning of reconfiguring the router to make TIKdevil work does pique my interest. :creep:
However, I consider this approach very messy in ticket restoration for the lay person who isn't technical enough to setup their router.
Also, TIKdevil will miss restoring tickets for games released after the CDN server block, custom Virtual Console injections, and *.3ds rom cart rips converted to *.cia files.

Oh yah, there are two (2) other *.db files to look out for found at:
  • sdmc:/Nintendo 3DS/<ID0>/<ID1>/dbs/
    • import.db
    • title.db
If you tamper with these or they become corrupt when using the:
  • System Settings → Data Management → ... → Delete
, all your titles will disappears in HOME Menu.

Because of that, I suggest deleting titles only with FBI because of the number of times other users reported this happening to them.

But that made me think, this could be made so much easier. What if there was a tool that would simply reinstall missing tickets if a match is found on the title key database? And without requiring messing with a custom DNS just to get the site working?
No tool such as that exists as far as I could search for. Maybe some day if somehow decides to rework developing TIKdevil. :/

I think this could be done as simply as merging tikShop and tikSweep into one, and simply replacing the DNS lookup with the hardcoded IP of the title key site (since the domain is expired), and it would achieve what I spent probably a few hours trying to do in a better way before finally giving up and spending an hour figuring out how to add hosts entries on my router, and in just a few minutes without any hassle. That would be the easy way to do it since it would essentially just be copy pasting some code (which I could do easily even not having much knowledge about 3DS homebrew development specifically), but the proper way to do it would be to check the SD card for data that has missing tickets, and only install those tickets, negating the need for deleting unused tickets afterwards and making the whole process much faster. That, I'm not sure how to do though.

I've seen several posts recently with people having missing tickets (and "X" in data management), so it seems there is a use for something like this.
Tell me about it. For the time being, I annoyingly tell everyone I've come across to backup their game saves + extdata, dump their games into *.cia, and keep safe a copy of their SysNAND *.bin image. Basically, try to avoid finding themselves in the scenario having to jump through hoops to get their stuff working again. Preventative measures, folks!

***

Oh btw, your previous suggestion from this post about using pasteboard.co didn't work out for me. There was a day I tried dragging and dropping images, and the site didn't accept them. It works perfectly fine now, so it was probably during one of their down times.

I researched imgbb.com, and they're no longer blocked by malwarebytes. They were at one point due to hosting malware masquerading as *.png images, but this was due to users bypassing the image format check the site didn't have before.

Here is VirusTotal recent report of imgbb:
 
Last edited by TurdPooCharger,
I don't trust CTRTransfer enough to not lose tickets. I see CTRTransfer like a universal SysNAND restore. In fact, I myself have once lost tickets using it. It should be viewed and treated as a region changing and firmware recovery tool with caveats to look out for. As for dropping a mention that it'll keep tickets, good luck telling someone that when their tickets are not kept. Eh...


tikSweep sucks at its purpose. Use FBI to delete unused tickets.

Your mentioning of reconfiguring the router to make TIKdevil work does pique my interest. :creep:
However, I consider this approach very messy in ticket restoration for the lay person who isn't technical enough to setup their router.
Also, TIKdevil will miss restoring tickets for games released after the CDN server block, custom Virtual Console injections, and *.3ds rom cart rips converted to *.cia files.

Oh yah, there are two (2) other *.db files to look out for found at:
  • sdmc:/Nintendo 3DS/<ID0>/<ID1>/dbs/
    • import.db
    • title.db
If you tamper with these or they become corrupt when using the:
  • System Settings → Data Management → ... → Delete
, all your titles will disappears in HOME Menu.

Because of that, I suggest deleting titles only with FBI because of the number of times other users reported this happening to them.


No tool such as that exists as far as I could search for. Maybe some day if somehow decides to rework developing TIKdevil. :/


Tell me about it. For the time being, I annoyingly tell everyone I've come across to backup their game saves + extdata, dump their games into *.cia, and keep safe a copy of their SysNAND *.bin image. Basically, try to avoid finding themselves in the scenario having to jump through hoops to get their stuff working again. Preventative measures, folks!

***

Oh btw, your previous suggestion from this post about using pasteboard.co didn't work out for me. There was a day I tried dragging and dropping images, and the site didn't accept them. It works perfectly fine now, so it was probably during one of their down times.

I researched imgbb.com, and they're no longer blocked by malwarebytes. They were at one point due to hosting malware masquerading as *.png images, but this was due to users bypassing the image format check the site didn't have before.

Here is VirusTotal recent report of imgbb:
It's still important to mention the ticket thing, because they do need to actually manually reinstall those tickets and it could save them a lot of hassle.
What's wrong with tikSweep though? Seems to work fine.
As for pasteboard.co, I notice that if I'm too quick it won't accept my images. It needs to load fully and then it'll accept drag & drop.
 
Last edited by The Real Jdbye,
Not sure if anyone said this already, but you could try to copy the latest version of Luma (boot.firm) to the CTRNAND and try to boot without the SD card. (Use GodMode9)
 
It's still important to mention the ticket thing, because they do need to actually manually reinstall those tickets and it could save them a lot of hassle.
I'll have to in-depth test this before reconsidering CTRTransfer as an option over SysNAND restore. I'll try doing a dummy install of several games [cart converts + (fre)eShop + VC custom injects], deleting titles files on my CTRNAND in GodMode9, and then CTRTransfer to see if the games consistently stick around.
What's wrong with tikSweep though? Seems to work fine.
I've noticed tikSweep is not thorough in deleting unused tickets. This once happened to me when I was downloading updates straight from Nintendo eShop post CDN server side block. You can read about that here and onwards.
As for pasteboard.co, I notice that if I'm too quick it won't accept my images. It needs to load fully and then it'll accept drag & drop.
Edit - Eh, I'll pass pasteboard, unless they never delete your pictures.
 
Last edited by TurdPooCharger,

Site & Scene News

Popular threads in this forum