Homebrew Doing a system transfer, im a bit paranoid.

[holographic_joe]

I can't find a single straight answer on how to handle system transfers when CFW is involved. So I'm going to detail my plan here and you can all tell me what I'm doing wrong!

1. Perform normal "PC based" system transfer, just straight up copy the whole SD card over to the new system.
-all my stuff will be invisible (but still present) due to illegitimate tickets.

2. install CFW on the new system.

3. use faketik or restore a ticket.db to make all my apps appear again.

I have a feeling it really isn't that easy. Would this plan work or am I a moron?

 

[TurdPooCharger]

- If your source 3DS system has custom firmware, you backup all the saves + extdata with Checkpoint or JKSM.
- GBA VC saves will need to be backed up with tedious process using GodMode9.
- All your pirated games, DLCs, and updates not bought from Nintendo eShop will need to be dumped into *.cia files with GodMode9.
- The NNID will be System Transfer over to your target 3DS system. Pirated titles do not cross over.
- If your target 3DS system does not have custom firmware, you install it with Frogminer.
- Once the target system has CFW, you reinstall all pirated titles and restore the saves + extdata.

• CFW to CFW system transfer
• 3DS system transfer today- Whats the best way?

 

[Namesnipe]

- If your source 3DS system has custom firmware, you backup all the saves + extdata with Checkpoint or JKSM.
- GBA VC saves will need to be backed up with tedious process using GodMode9.
- All your pirated games, DLCs, and updates not bought from Nintendo eShop will need to be dumped into *.cia files with GodMode9.
- The NNID will be System Transfer over to your target 3DS system. Pirated titles do not cross over.
- If your target 3DS system does not have custom firmware, you install it with Frogminer.
- Once the target system has CFW, you reinstall all pirated titles and restore the saves + extdata.

• CFW to CFW system transfer
• 3DS system transfer today- Whats the best way?

This actually isn't the case. He can dump his ticket.db, extract the .tiks and reinstall them. If I'm correct, you install the tickets from the eshop and hidden folder. I'm not so sure about the hidden folder.

 

[TurdPooCharger]

This actually isn't the case. He can dump his ticket.db, extract the .tiks and reinstall them. If I'm correct, you install the tickets from the eshop and hidden folder. I'm not so sure about the hidden folder.

I know that fake or spoofed tickets do not cross over but am not sure if pirated titles get deleted off the SD card while it is in the source 3DS when the System Transfer occurs.

I also know from prior NAND experiments that System Transfer changes the CMAC values for certain files like the movable.sed, [certs / import / ticket / title / tmp_i / tmp_t] *.db found on NAND and possibly the [import / title] *.db found on SD card in the Nintendo 3DS folder. If the CMAC hashes for these are not correct, the 3DS will fail to recognize the contents on HOME Menu. This is why I don't believe one can simply make a copy of the Nintendo 3DS folder before the System Transfer and then reuse that folder on the target 3DS after doing it.

While (I think) it's possible to back up the ticket.db from source 3DS SysNAND, re-inject it into the target 3DS SysNAND, and have GodMode9 fix the CMAC, you can still end up with the 3DS refusing to recognize titles on HOME Menu. This is if the import.db and title.db files in Nintendo 3DS folder were edited to de-list pirated titles during System Transfer.

Oh, if you think you can keep copies of the import and title *.db and use GodMode9 recalculate their CMAC, I have to warn anyone who attempts this that it can end badly. My entire collection of games, DLCs, updates, saves + extdata was once permanently deleted with no hope of recovery, not even when scanning for them with data recovery programs like EaseUS. As for why this happened, I can't say. I suppose you can try this if you have a backup copy of that folder on your computer.

***

I personally recommend the minimum task is to back up the saves + extdata with a save manager for all your games before going through with System Transfer. You can recollect lost titles from places like those [...] sites or even GodMode9 redump them into *.cia files from the target system so long as there's a retained copy of the Nintendo 3DS folder prior to System Transfer.

Game progresses are too important not to back up if and when things go wrong.

 

[Namesnipe]

I know that fake or spoofed tickets do not cross over but am not sure if pirated titles get deleted off the SD card while it is in the source 3DS when the System Transfer occurs.

I also know from prior NAND experiments that System Transfer changes the CMAC values for certain files like the movable.sed, [certs / import / ticket / title / tmp_i / tmp_t] *.db found on NAND and possibly the [import / title] *.db found on SD card in the Nintendo 3DS folder. If the CMAC hashes for these are not correct, the 3DS will fail to recognize the contents on HOME Menu. This is why I don't believe one can simply make a copy of the Nintendo 3DS folder before the System Transfer and then reuse that folder on the target 3DS after doing it.

While (I think) it's possible to back up the ticket.db from source 3DS SysNAND, re-inject it into the target 3DS SysNAND, and have GodMode9 fix the CMAC, you can still end up with the 3DS refusing to recognize titles on HOME Menu. This is if the import.db and title.db files in Nintendo 3DS folder were edited to de-list pirated titles during System Transfer.

Oh, if you think you can keep copies of the import and title *.db and use GodMode9 recalculate their CMAC, I have to warn anyone who attempts this that it can end badly. My entire collection of games, DLCs, updates, saves + extdata was once permanently deleted with no hope of recovery, not even when scanning for them with data recovery programs like EaseUS. As for why this happened, I can't say. I suppose you can try this if you have a backup copy of that folder on your computer.

***

I personally recommend the minimum task is to back up the saves + extdata with a save manager for all your games before going through with System Transfer. You can recollect lost titles from places like those [...] sites or even GodMode9 redump them into *.cia files from the target system so long as there's a retained copy of the Nintendo 3DS folder prior to System Transfer.

Game progresses are too important not to back up if and when things go wrong.

Pirated titles do not get deleted from the SD card, and I said to extract the contents of the ticket.db and install the tickets from those, as just swapping the ticket.db will cause your 3DS to stop booting.

 

[TurdPooCharger]

Pirated titles do not get deleted from the SD card, and I said to extract the contents of the ticket.db and install the tickets from those, as just swapping the ticket.db will cause your 3DS to stop booting.

Swap it and use the Calculate CMAC option. This should avoid the whole ticket extract and reinstall.

 

[Namesnipe]

Swap it and use the Calculate CMAC option. This should avoid the whole ticket extract and reinstall.

Oh wow. I reinstalled my tickets last time. Thanks.

 

[TurdPooCharger]

Oh wow. I reinstalled my tickets last time. Thanks.

Thanks back in mentioning the *.tik files with ticket.db. I never knew they can be reinstalled individually. One of the burning questions I have is whether the ticket.db is commutable or shareable between different systems with different movable.sed or not involved in System Transfer. Check back this post for later edit update.

Edit - I took the ticket.db from my niece's n3DS which has most of the games I have minus several DSiWare titles, swapped it into my n3DSXL, and used the calculate CMAC. It does indeed works!