I'm about to throw in the towel and consider this a lost cause, but I wanted to run it past y'all before I do so.
Basically I have a 3DS using Luma and my child wanted a game (in .cia format) on it. I kept trying to install it, but it kept failing. I tried to convert a .3DS of the game and that failed to, so at that point I decided maybe I should try backing up the SD Card and then updating Luma and Godmode9 to the latest versions. At this point I couldn't get the 3DS to boot, it would just blink a blue light for a moment. I could boot it without the SD card, so I figured the console itself was probably fine and so I decided based on the hack guides that I should try reformatting the card and recopying everything back over to it. But much to my chagrin the card failed to format with either guiformat or just Windows and then it wasn't mounting. At 11 years old, I figured the card must have kicked the bucket.
I thought my backup might be okay though because I used Teracopy and its verify feature and it didn't report errors and the card had seemingly been working prior to this whole endeavor (It's a 64GB Sandisk, for what its worth.... I never checked when I got it though if it was counterfeit or not).
So I bought a new card (64GB again) and this time I tested it with h2testw (it passed). I copied my backup back onto it, verified the transfer, and tried it out and found it still wouldn't boot. At this point I don't recall exactly what I did, but I did finally get the 3DS booting with Luma.
And then I found my games weren't showing up (and I didn't have the double directory in the "Nintendo 3DS" directory that I saw resolved this for others) so I tried faketik which resulted in a "Failed to query the external title database" and so I figured I needed to try to rebuild my title database. So then I went through the trouble of trying to find all the files needed to use the rebuild title database python script.
I used ninfs (Nine Inch Nails File System?) to extract movable.sed, but I only had movable.bin but based on some googlling I was under the impression its the same file and so I just renamed it.
So I tried to run the script and I got a whole lot of:
Does this look like my game files are corrupted or was I wrong about thinking I could just change the extension for the movable file?
An annoyance, but its not the end of the world if I have to reinstall my games... but what about the save data? I do have Checkpoint in there, but its been a long time since I used it. There are directories I see for my games under the saves directory... but most are actually empty. So I suppose thats no good either?
So at this point I'm wondering if there are more things to try or if there are enough red flags here that I should just accept my data is FUBAR and I just have to accept loosing everything and starting over (and also doing backups more regularly!)
Thank you for your time.
Basically I have a 3DS using Luma and my child wanted a game (in .cia format) on it. I kept trying to install it, but it kept failing. I tried to convert a .3DS of the game and that failed to, so at that point I decided maybe I should try backing up the SD Card and then updating Luma and Godmode9 to the latest versions. At this point I couldn't get the 3DS to boot, it would just blink a blue light for a moment. I could boot it without the SD card, so I figured the console itself was probably fine and so I decided based on the hack guides that I should try reformatting the card and recopying everything back over to it. But much to my chagrin the card failed to format with either guiformat or just Windows and then it wasn't mounting. At 11 years old, I figured the card must have kicked the bucket.
I thought my backup might be okay though because I used Teracopy and its verify feature and it didn't report errors and the card had seemingly been working prior to this whole endeavor (It's a 64GB Sandisk, for what its worth.... I never checked when I got it though if it was counterfeit or not).
So I bought a new card (64GB again) and this time I tested it with h2testw (it passed). I copied my backup back onto it, verified the transfer, and tried it out and found it still wouldn't boot. At this point I don't recall exactly what I did, but I did finally get the 3DS booting with Luma.
And then I found my games weren't showing up (and I didn't have the double directory in the "Nintendo 3DS" directory that I saw resolved this for others) so I tried faketik which resulted in a "Failed to query the external title database" and so I figured I needed to try to rebuild my title database. So then I went through the trouble of trying to find all the files needed to use the rebuild title database python script.
I used ninfs (Nine Inch Nails File System?) to extract movable.sed, but I only had movable.bin but based on some googlling I was under the impression its the same file and so I just renamed it.
So I tried to run the script and I got a whole lot of:
Code:
Traceback (most recent call last):
File "D:\Users\abailey\Downloads\rebuild-title-database-master\rebuild-title-database.py", line 64, in <module>
tmd = TitleMetadataReader.load(tmd_cfh)
File "C:\Users\abailey\AppData\Roaming\Python\Python314\site-packages\pyctr\type\tmd.py", line 244, in load
raise InvalidSignatureTypeError(sig_type)
pyctr.type.tmd.InvalidSignatureTypeError: 0xeae689a6
Failed to parse tmd at F:\Nintendo 3DS\2ed92e5c5b38047b39252d08cca0d0cb\1a2c00a63010735c30303030001b534d\title\00040000\00054000\content\00000000.tmd
Traceback (most recent call last):
File "C:\Users\abailey\AppData\Roaming\Python\Python314\site-packages\pyctr\type\tmd.py", line 242, in load
sig_size, sig_padding = signature_types[sig_type]Does this look like my game files are corrupted or was I wrong about thinking I could just change the extension for the movable file?
An annoyance, but its not the end of the world if I have to reinstall my games... but what about the save data? I do have Checkpoint in there, but its been a long time since I used it. There are directories I see for my games under the saves directory... but most are actually empty. So I suppose thats no good either?
So at this point I'm wondering if there are more things to try or if there are enough red flags here that I should just accept my data is FUBAR and I just have to accept loosing everything and starting over (and also doing backups more regularly!)
Thank you for your time.
