Hardware CFW: Files still on SD card, but system memory is formatted.

[Nommert69]

Hi!

I've bought a new N3DS XL a few days ago. I transferred my old data to the new ds, but I made a mistake in doing so. I only realised my system (and SD card with CFW) would be formatted after I had already done the transfer, so there was no going back. At the time I thought it would be smart to turn the DS simply off after the files have been transferred, but before the SD card would format.

Now my DS has been formatted completely, but not the SD card. All the files are still on de SD card, only they are not showing up on my system.
Do I have to format my Sd card and follow the #DS hacks guide (partially) again? Or is there a way to save me the hassle of downloading 100gb of games again?

Thank you for reading!

 

[ThoD]

Hi!

I've bought a new N3DS XL a few days ago. I transferred my old data to the new ds, but I made a mistake in doing so. I only realised my system (and SD card with CFW) would be formatted after I had already done the transfer, so there was no going back. At the time I thought it would be smart to turn the DS simply off after the files have been transferred, but before the SD card would format.

Now my DS has been formatted completely, but not the SD card. All the files are still on de SD card, only they are not showing up on my system.
Do I have to format my Sd card and follow the #DS hacks guide (partially) again? Or is there a way to save me the hassle of downloading 100gb of games again?

Thank you for reading!

If only the system was formatted, then absolutely nothing happened to the CFW installation, it's still there, reason you aren't seeing your stuff is almost definitely because of missing tickets, as when system is formatted all tickets/keys are deleted, so simply import them back in with FBI.

 

[Nommert69]

If only the system was formatted, then absolutely nothing happened to the CFW installation, it's still there, reason you aren't seeing your stuff is almost definitely because of missing tickets, as when system is formatted all tickets/keys are deleted, so simply import them back in with FBI.

Thank you for your response. I understand all I have to do is re-install FBI and import the tickets?

 

[ThoD]

Thank you for your response. I understand all I have to do is re-install FBI and import the tickets?

Yup, to reinstall it just inject it into H&S using GM9, then install it and un-inject it when done.

 

[TurdPooCharger]

Reinstalling games will overwrite and delete saves.

* How you should have System Transfer with 3DS system(s) that have custom firmware.

• How to perform a System Transfer without losing non-legitimate titles

 

[Nommert69]

Yup, to reinstall it just inject it into H&S using GM9, then install it and un-inject it when done.

I installed FBI and homebrew again using Rosalina. Could you help me with installing the missing tickets using FBI? I don't know how to do this and I can't find it on google either.

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

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

@TurdPooCharger The save games don't matter much. I haven't played in a long time except for 1 game. Thanks for the information, I didn't think the system transfer through.
I was searching on google and I found an older comment of yours;

How to reinstall system tickets without doing CTRTransfer.

1. GodMode9 → 11.5.0-38X_ctrtransfer_x3ds.bin → CTRNAND options... →Mount image to drive.
2. 7:/dbs/ticket.db → Copy to 0:/gm9/out.
3. Press (B) button several times to back out. Hold (R)-shoulder and press (X) on [7:] FAT IMAGE to unmount.
4. [0:] SDCARD ()/gm9/out/ticket.db → Ticket.db options... → Mount image to drive.
5. In the T:/ drive, hold (L)-shoulder and press (RIGHT) d-pad to highlight select yellow: eshop, hidden, system, and unknown.
6. Press (Y) to [CLIPBOARD] selection all four (4) items, or press (SELECT) to reset and try again.
   
7. Press (B) button to back out. Go to [0:] SDCARD ()/gm9/out directory.
8. Hold (R)-shoulder and press (Y) → Create a folder. Rename it from newdir → tickets.
9. Go into the tickets folder. Press (Y) → Paste 4 paths here? <A> yes.
10. On desktop computer (or GodMode9 if you're familiar enough with the controls), combine and move all TIK files in the root of tickets.
11. Keep all tickets that are in this format [delete tickets that don't have the eight (8) zeros].
    • ################.00000000.tik
12. Rosalina menu inject Homebrew Launcher to Nintendo 3DS Camera using the gm9 script, <ink> - Inject HBL to Camera.
    • Ignore the CTRTransfer part. This is just one of the several functions it does.
13. HOME Menu → Press (L) + (R) → Camera applet → Nintendo 3DS Camera → Homebrew Launcher → FBI → SD/gm9/out/tickets → <current directory> → Install and delete all tickets.
14. System Settings → Other Settings → System Update or <link> to fix the rest of the 3DS firmware.
15. For pirated games, DLCs, and updates that are missing tickets, use <link> (DO NOT USE THIS TO RESTORE SYSTEM TITLES).

Will this inject my missing tickets? I'm not sure what the difference is between system and game tickets.

 

[TurdPooCharger]

I installed FBI and homebrew again using Rosalina. Could you help me with installing the missing tickets using FBI? I don't know how to do this and I can't find it on google either.

@TurdPooCharger The save games don't matter much. I haven't played in a long time except for 1 game. Thanks for the information, I didn't think the system transfer through.
I was searching on google and I found an older comment of yours;

Will this inject my missing tickets? I'm not sure what the difference is between system and game tickets.

That was written specifically for someone who delete ALL their tickets, including both system and game titles. It was geared towards repairing the 3DS firmware while avoiding having to do CTRTransfer. A 3DS firmware that is missing legit tickets or has fake tickets for its system titles cause problems with system updates and bricking if custom firmware is ever removed.

Game titles are typical your library set found on the SD card. They're separate from system titles found on the 3DS internal NAND memory. However, all tickets for both system and game titles are installed to the ticket.db found on CTRNAND.

Unless you bought or downloaded games, DLCs, and updates from the Nintendo eShop and wish to keep their personal legit tickets, you can restored or spoof back fake tickets for pirated CIAs using faketik app.

 

[Nommert69]

That was written specifically for someone who delete ALL their tickets, including both system and game titles. It was geared towards repairing the 3DS firmware while avoiding having to do CTRTransfer. A 3DS firmware that is missing legit tickets or has fake tickets for its system titles cause problems with system updates and bricking if custom firmware is ever removed.

Game titles are typical your library set found on the SD card. They're separate from system titles found on the 3DS internal NAND memory. However, all tickets for both system and game titles are installed to the ticket.db found on CTRNAND.

Unless you bought or downloaded games, DLCs, and updates from the Nintendo eShop and wish to keep their personal legit tickets, you can restored or spoof back fake tickets for pirated CIAs using faketik app.

Ah alright, thanks for the info. Now I know what the difference is. I already ran the faketik app using homebrew, but it says there are no missing tickets. There are however a lot of red tickets in the FBI tickets folder. Do you know what this could mean?

 

[TurdPooCharger]

Ah alright, thanks for the info. Now I know what the difference is. I already ran the faketik app using homebrew, but it says there are no missing tickets. There are however a lot of red tickets in the FBI tickets folder. Do you know what this could mean?

Other than missing tickets, there are two other causes for unrecognized games.

(1) The 3DS has damaged database. All titles have been delisted from the SD card's title.db and import.db.

• Signs of damaged database (ie, only GodMode9 Search for titles sees them).
  
• To fix the database, you'll need to use CTRTransfer (Type D9) - Rebuild 3DS Database.

(2) The 3DS system you're using does not have matching encryption between its NAND's movable.sed KeyY and Nintendo 3DS/<ID0> subfolder.

• You would need to figure out whether the source or target system has the (mostly) intact KeyY.
  
• You can try to correct this by using CTRTransfer (Type D9) - Fix movable.sed KeyY.
• In case the script fails to find the exact KeyY, you'll need to resort to dumping Friend Code info with seedstarter, taking the 1st half of a given KeyY, and recreating the 2nd half with a dummy movable.sed though bruteforcemovable.com, and then decrypting/backing up contents with ninfs. This data recovery route is super messy and ugly.