Hacking Transferring all data from one CFW 3DS to another?

DavilosCoyote

Member
OP
Newcomer
Joined
Feb 1, 2020
Messages
8
Trophies
0
Age
19
XP
69
Country
United States
Recently I damaged my CFW 3DS and want to transfer all data to a new 3DS with CFW. The last time I tried to do this via the built in transfer function, all games and apps installed with FBI were lost. Is there any way to clone the system without losing any data, FBI apps, FBI games, or save data?
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
17,741
Trophies
2
XP
17,466
Country
United States
Pirated games and apps will have to be reinstalled manually. Save files should transfer in a System Transfer, but it's a good idea to backup your important save files with JKSM or Checkpoint beforehand.
 

The Real Jdbye

*is birb*
Member
Joined
Mar 17, 2010
Messages
21,899
Trophies
3
Location
Space
XP
11,061
Country
Norway
Is there no way to circumvent having to reinstall such as making a backup with godmode 9?
Sure. You can back up the tickets beforehand (there is an option in GM9 Megascript) and reinstall them on the target console after transfer with FBI. Alternatively you can skip the ticket backup step, and use faketik on the target console to generate any missing tickets, any content on the SD card that was moved over from the old console should then show up.
 

donkeykongoffical

Member
Newcomer
Joined
Aug 8, 2020
Messages
19
Trophies
0
Age
24
XP
85
Country
United States
Pirated games and apps will have to be reinstalled manually. Save files should transfer in a System Transfer, but it's a good idea to backup your important save files with JKSM or Checkpoint beforehand.
couldn't you put the sd card into another console though?
 

slimbizzy

call me watchu want
Member
Joined
Apr 7, 2020
Messages
301
Trophies
1
Location
Calgary
Website
linktr.ee
XP
954
Country
Canada
couldn't you put the sd card into another console though?
not really.

lots of the CFW and OFW for the 3DS is native to its own console.

think of it this way:

my O3DS has a number of 12232.
my N3DS has a number of 12231.

they wont mix. that's the most simple answer you could possible have, probably.

you can use a different systems SD card, but you wont have the same "system-number" making it so you cant have the same games for example.

another thing to know, is that CFW is also built into the SYSTEM. Not just the SD card.

BUT!!! there are other things you can do to make this a reality(i think).
see TurdPooCharger's post right above yours.
 
Last edited by slimbizzy,

slimbizzy

call me watchu want
Member
Joined
Apr 7, 2020
Messages
301
Trophies
1
Location
Calgary
Website
linktr.ee
XP
954
Country
Canada
Can't you change the "system number" through windows explorer
nope. there are some files in the folder that are special, cant edit them from what i'm aware of. although, that might change due to source code leaks.

even then, it is much of a hassle. you might as well just keep a back-up copy of your system key and stuff if you one day maybe lose the official.

it also isn't too much work to just re-pirate titles and hack/mod the DS
 

lone_wolf323

Well-Known Member
Member
Joined
May 27, 2011
Messages
4,755
Trophies
1
XP
3,785
Country
Canada
Can't you change the "system number" through windows explorer
each system encrypts its sd data with its own console unique keys. You have to transfer the console to another to make the console read the data in the next one. doing so will render that previous console inept of reading the new console encryption. There is no way to just insert a sd from one console to another. It simply dont work that way.
 
D

Deleted User

Guest
You could fully clone your 3DS with CTRTransfer Tool. Before you run this tool, copy your movable.sed to your SD Card and then put the movable.sed onto the SysNAND of the target 3DS. Then run the tool, and you should be able to use the same "Nintendo 3DS" folder on the target system, so all of your installed titles should appear on the HOME Menu.
 

Clydefrosch

Well-Known Member
Member
Joined
Jan 2, 2009
Messages
5,911
Trophies
1
XP
4,208
Country
Germany

just follow this. i did this last week and it worked like a charm.
make sure to save your home menu layout before you start and hack the new system before you start the transfer.
then do a system transfer, let it do it's thing until its done. note that unlike in the guide, i wasn't asked how i wanted to transfer my data, it just started doing it in its own way, don't worry.
halfway through, it will have that weird crash reboot moment, when it's done transfering and the old system is factory resetted. just stay calm and let it continue to do its thing on the other system until its ready and boots to home menu..

once it's finally done, just move the sd card over (or in case you need to switch from a large sd to a micro sd, transfer the files with your pc), use faketik and all the installed things will be back. then use cthulu to unwrap them all (or do it by hand) and restore the layout.
 
Last edited by Clydefrosch,
Joined
Jan 1, 2018
Messages
7,292
Trophies
2
XP
5,869
Country
United States
You could fully clone your 3DS with CTRTransfer Tool. Before you run this tool, copy your movable.sed to your SD Card and then put the movable.sed onto the SysNAND of the target 3DS. Then run the tool, and you should be able to use the same "Nintendo 3DS" folder on the target system, so all of your installed titles should appear on the HOME Menu.
Homebrew based System Transfer where the source system's ctrnand partition or nand files are moved or cloned onto a target system is a very terrible idea.

Not only can this permanently overwrite and erase the console unique files of the target system (HWCAL0/1.dat , SecureInfo_A|B , LocalFriendCodeSeed_B , movable.sed , etc ), you run the risk of getting both systems banned by Nintendo when the target system impersonates the source system.

Homebrew based System Transfer differs from Nintendo's officially sanctioned System Transfer is that the source system's personal user account (NNID, Friend Code, eShop account/credit card info, etc.) hasn't been notified and recorded to the CDN server as being given to that target system.
 
D

Deleted User

Guest
Homebrew based System Transfer where the source system's ctrnand partition or nand files are moved or cloned onto a target system is a very terrible idea.

Not only can this permanently overwrite and erase the console unique files of the target system (HWCAL0/1.dat , SecureInfo_A|B , LocalFriendCodeSeed_B , movable.sed , etc ), you run the risk of getting both systems banned by Nintendo when the target system impersonates the source system.

Homebrew based System Transfer differs from Nintendo's officially sanctioned System Transfer is that the source system's personal user account (NNID, Friend Code, eShop account/credit card info, etc.) hasn't been notified and recorded to the CDN server as being given to that target system.
The whole point of CTRTransfer is that it DOESN'T copy console specific files or account information. That is why it doesn't cause bans.
 
Joined
Jan 1, 2018
Messages
7,292
Trophies
2
XP
5,869
Country
United States
The whole point of CTRTransfer is that it DOESN'T copy console specific files or account information. That is why it doesn't cause bans.

I'm quoting your post from the other thread as this relevant to this discussion.
This software could have been so much simpler to make... I made a 1 KB GM9 script that does everything that this software does, but my script also implements a movable.sed and dbs folder swap option, so you can use the Nintendo 3DS folder from another 3DS.
Oh dear...

The first thing we have to establish is that are several varieties of CTRTransfer. While it's true that those like [3ds.hacks.guide] Standard CTRTransfer and [3ds.eiphax.tech] Manual Transfer {when used as instructed} does not copy console unique files outside of their intended or original 2DS/3DS system from where they were sourced, the CTRTransfer Tool you were referring in post #11 is not one of them.

This form of CTRTransfer does erase the target system's unique files by supplementing or replacing them with those from a target system. In fact, reflashing the entire CTRNAND with a donor's ctrnand *.bin image is actually one of the key aspects to Lazarus3DS (aka, last ditch nuclear option meant to repair worst case firmware softbrick where the NAND is fully trashed and no SysNAND *.bin image backup exists).

***

While your idea of selectively restoring the movable.sed and nand *.dbs does work in terms of being able to play another/source system's library (Nintendo 3DS folder), the movable.sed contains console unique information such as a copy of the LocalFriendCodeSeed_B (responsible for online play access), access rights to the Nintendo eShop (eShop account) and who's NNID + DeviceID that movable.sed is supposed to be registered per their CDN server records. The same goes for your private legit eShop tickets found in ticket.db. Those have signatures specifically to the device that bought the titles.

It'll be pretty stupid to broadcast your presence, such as your Friend Code, from two places at once. Taking that target system to play or shop online with the cloned setup is asking for Nintendo to ban both. Extra negative points if you give a reason for Nintendo to suspect stolen identity or fraud (ie, credit card info linked to eShop) and to hyperban them both.

***

Also, it's not a good idea to transfer only the nand's title.db & import.db to a different system as these two database are intricate to what's installed or listed in the title folder. You can softbrick the 3DS firmware due to differences in firmware versions and ContentIDs names for the APP files.
 
  • Like
Reactions: KleinesSinchen
D

Deleted User

Guest
I'm quoting your post from the other thread as this relevant to this discussion.

Oh dear...

The first thing we have to establish is that are several varieties of CTRTransfer. While it's true that those like [3ds.hacks.guide] Standard CTRTransfer and [3ds.eiphax.tech] Manual Transfer {when used as instructed} does not copy console unique files outside of their intended or original 2DS/3DS system from where they were sourced, the CTRTransfer Tool you were referring in post #11 is not one of them.

This form of CTRTransfer does erase the target system's unique files by supplementing or replacing them with those from a target system. In fact, reflashing the entire CTRNAND with a donor's ctrnand *.bin image is actually one of the key aspects to Lazarus3DS (aka, last ditch nuclear option meant to repair worst case firmware softbrick where the NAND is fully trashed and no SysNAND *.bin image backup exists).

***

While your idea of selectively restoring the movable.sed and nand *.dbs does work in terms of being able to play another/source system's library (Nintendo 3DS folder), the movable.sed contains console unique information such as a copy of the LocalFriendCodeSeed_B (responsible for online play access), access rights to the Nintendo eShop (eShop account) and who's NNID + DeviceID that movable.sed is supposed to be registered per their CDN server records. The same goes for your private legit eShop tickets found in ticket.db. Those have signatures specifically to the device that bought the titles.

It'll be pretty stupid to broadcast your presence, such as your Friend Code, from two places at once. Taking that target system to play or shop online with the cloned setup is asking for Nintendo to ban both. Extra negative points if you give a reason for Nintendo to suspect stolen identity or fraud (ie, credit card info linked to eShop) and to hyperban them both.

***

Also, it's not a good idea to transfer only the nand's title.db & import.db to a different system as these two database are intricate to what's installed or listed in the title folder. You can softbrick the 3DS firmware due to differences in firmware versions and ContentIDs names for the APP files.
Oh, I thought I had read somewhere that importing /r#/sys console specific files would cause a softbrick.
Also, I was not intending to refer to any one CTRTransfer method, that term was intended to be vague.
 
Last edited by ,
General chit-chat
Help Users
    Psionic Roshambo @ Psionic Roshambo: Lol