System Transfer - Revision history

TimmSkiller: /* System Save Data Transfer */

2025-05-23T14:15:53Z

System Save Data Transfer

← Older revision		Revision as of 18:15, 23 May 2025
Line 134:		Line 134:
	See also [http://www.nintendo.com/consumer/systems/3ds/en_na/gi_index.jsp?menu=transfer&submenu=ctr-gi-apps-transfer-what-data 3DS System transfer ]		See also [http://www.nintendo.com/consumer/systems/3ds/en_na/gi_index.jsp?menu=transfer&submenu=ctr-gi-apps-transfer-what-data 3DS System transfer ]

	==System Save Data Transfer==		==System Save Data / Shared Extdata Transfer==
	During a system transfer, the source system transfers raw ([[DISA_and_DIFF\|DISA]]) [[System_SaveData\|System Save Data]] images (AES-128-CTR encrypted) to the destination system.		During a system transfer, the source system transfers raw ([[DISA_and_DIFF\|DISA/DIFF]]) [[System_SaveData\|System Save Data]] and possible [[Extdata#NAND_Shared_Extdata\|Shared NAND Extdata]] images (AES-128-CTR encrypted) to the destination system.

	It appears that both the save data for the [[NIM_Services\|nim]] sysmodule and the [[Config_Savegame\|Configuration Savegame]] are skipped during this process.		It appears that both the save data for the [[NIM_Services\|nim]] sysmodule and the [[Config_Savegame\|Configuration Savegame]] are skipped during this process.
Line 143:		Line 143:
	It then uses [[FS:EnumerateSystemSaveData]] to obtain a list of system save data IDs.		It then uses [[FS:EnumerateSystemSaveData]] to obtain a list of system save data IDs.

	The source system then creates the encrypted, raw system save data dumps using [[Filesystem_services#~~0x12345681_Archive_Path_Data_Format~~\|~~archive ID 0x12345681~~]].		The source system then creates the encrypted, raw system save data / extdata dumps using [[Filesystem_services#SystemSaveData\|System Savedata Transfer]] / [[Filesystem_services#Filesystem_services#Extdata_/_Shared_Extdata\|Extdata Transfer / Shared Extdata Transfer]].

	The following encryption is used for these dumps:		The following encryption is used for these dumps:
Line 151:		Line 151:
	- For the CTR, first, the random 16 bytes from the [[Filesystem_services#DeviceMoveContext\|Device Move Context]] are hashed with SHA256.		- For the CTR, first, the random 16 bytes from the [[Filesystem_services#DeviceMoveContext\|Device Move Context]] are hashed with SHA256.

	- The SHA256 hash is updated using the UTF-16 path for the save data file (relative to <code>nand:/data/<ID0></code>), beginning with a </code>/</code> (and including a two-byte NULL termination). Therefore the path would be UTF-16 <code>/sysdata/<lowercase, 8 character hex system save id>/00000000</code> and two additional NULL bytes.		- The SHA256 hash is updated using the UTF-16 path for the save data file (relative to <code>nand:/data/<ID0></code>), beginning with a </code>/</code> (and including a two-byte NULL termination).

			Therefore the path would be UTF-16 <code>/sysdata/<lowercase, 8 character hex system save id>/00000000</code> and two additional NULL bytes.

			For Shared Extdata, the path would similarly be <code>/extdata/<shared ext id low>/<shared ext id high>/<file path></code> and two additional NULL bytes.

	- The CTR is generated as follows: <code>ctr[i] = hash[i] ^ hash[i + 16]</code> for i from 0 to 16.		- The CTR is generated as follows: <code>ctr[i] = hash[i] ^ hash[i + 16]</code> for i from 0 to 16.
Line 159:		Line 163:
	On the destination system, [[FS:StartDeviceMoveAsDestination]] is called using the [[Filesystem_services#DeviceMoveContext\|Device Move Context]] from the source console.		On the destination system, [[FS:StartDeviceMoveAsDestination]] is called using the [[Filesystem_services#DeviceMoveContext\|Device Move Context]] from the source console.

	Similarly, [[Filesystem_services#~~0x12345681_Archive_Path_Data_Format~~\|~~archive ID 0x12345681~~]] is used to import the raw save images, though on the destination system, in ~~write~~ mode.		Similarly, [[Filesystem_services#SystemSaveData\|System Savedata Transfer]] / [[Filesystem_services#Filesystem_services#Extdata_/_Shared_Extdata\|Extdata Transfer / Shared Extdata Transfer]] is used to import the raw save images, though on the destination system, in the destination mode.

	The encrypted save images are written directly to the destination system using the FS interface (and decrypted on the fly).		The encrypted save images are written directly to the destination system using the FS interface (and decrypted on the fly).


	= See also =		= See also =
	Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].		Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].

TimmSkiller at 12:31, 22 December 2024

2024-12-22T11:31:28Z

@@ Line 1: / Line 1: @@
 '''System Transfer''' is functionality that was added with the [[2.0.0-2]] June 6/7 2011 system update, which allows you to transfer DSiWare, recorded audio from the Nintendo DSi Sound title, "internal memory" pictures, WFC configuration, from DSi to 3DS. On DSi this is done with the "Nintendo 3DS Transfer Tool" that is downloaded from DSi Shop, while on 3DS System Transfer is accessible in the [[System Settings]]. System Transfer can also be used to transfer 3DSWare to other 3DS systems.
-== DSi System Transfer ==
+= DSi System Transfer =
 With the DSiWare DSi->3DS transfer, savegames are not transferred.
@@ Line 127: / Line 127: @@
 |}
-== 3DSWare Transfer ==
+= 3DS System Transfer =
-DSWare transfer is now available 3.0.0-5.
 It seems to unlock out of region eShop on the source 3DS (tested on old, not tested on new).
 See also [http://www.nintendo.com/consumer/systems/3ds/en_na/gi_index.jsp?menu=transfer&submenu=ctr-gi-apps-transfer-what-data 3DS System transfer ]
-== See also ==
+==System Save Data Transfer==
 Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].

Cooolgamer: /* 3DSWare Transfer */

2021-12-18T15:44:12Z

3DSWare Transfer

← Older revision		Revision as of 18:44, 18 December 2021
Line 130:		Line 130:

	3DSWare transfer is now available 3.0.0-5.		3DSWare transfer is now available 3.0.0-5.
	See also[http://www.nintendo.com/consumer/systems/3ds/en_na/gi_index.jsp?menu=transfer&submenu=ctr-gi-apps-transfer-what-data 3DS System transfer ]		It seems to unlock out of region eShop on the source 3DS (tested on old, not tested on new).
			See also [http://www.nintendo.com/consumer/systems/3ds/en_na/gi_index.jsp?menu=transfer&submenu=ctr-gi-apps-transfer-what-data 3DS System transfer ]

	== See also ==		== See also ==
	Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].		Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].

Matyapiro31: /* 3DSWare Transfer */

2011-12-10T07:14:19Z

3DSWare Transfer

← Older revision		Revision as of 10:14, 10 December 2011
Line 129:		Line 129:
	== 3DSWare Transfer ==		== 3DSWare Transfer ==

	3DSWare transfer ~~isn't~~ available ~~yet, would be implemented in another future system update~~.		3DSWare transfer is now available 3.0.0-5.
			See also[http://www.nintendo.com/consumer/systems/3ds/en_na/gi_index.jsp?menu=transfer&submenu=ctr-gi-apps-transfer-what-data 3DS System transfer ]

	== See also ==		== See also ==
	Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].		Nintendo of Japan System Transfer [http://www.nintendo.co.jp/3ds/support/transfer/index.html page].

Yellows8: /* DSi System Transfer */

2011-06-17T01:07:44Z

DSi System Transfer

← Older revision		Revision as of 05:07, 17 June 2011
Line 11:		Line 11:
	The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.		The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.

	When the DSi transfer tool and 3DS transfer tool startup, the DSi sends HTTPS SOAP requests to ecs.t.nintendowifi.net, ias.t.nintendowifi.net, and cas.t.nintendowifi.net. The 3DS sends HTTPS (mostly SOAP, unknown why the first one is used) requests to nus.c.nintendowifi.net, ecs.c.nintendowifi.net, and cas.c.nintendowifi.net. When entering the transfer DSiWare list menu, DSi requests from ecs* and cas*, 3DS does likewise.		When the DSi transfer tool and 3DS transfer tool startup, the DSi sends HTTPS SOAP requests to ecs.t.nintendowifi.net, ias.t.nintendowifi.net, and cas.t.nintendowifi.net. The 3DS sends HTTPS (mostly SOAP, unknown why the first one is used) requests to nus.c.nintendowifi.net, ecs.c.nintendowifi.net, and cas.c.nintendowifi.net. When entering the transfer DSiWare list menu, DSi requests from ecs* and cas*, 3DS does likewise. The 3DS system transfer will not allow you(likely server-side or so) to transfer etc at all unless you have the latest system update.

	When DSi sends the title list, after the first 6 bytes of the 802.11 data payload, is the below header. Following the header is the list of titles.		When DSi sends the title list, after the first 6 bytes of the 802.11 data payload, is the below header. Following the header is the list of titles.

Yellows8: /* DSi System Transfer */

2011-06-16T15:01:10Z

DSi System Transfer

← Older revision		Revision as of 19:01, 16 June 2011
Line 82:		Line 82:
	\| 0x28		\| 0x28
	\| 0x8		\| 0x8
	\| ~~Some~~ ASCII ~~numbers~~?		\| Unknown, ASCII 3DS ticket consoleID used with DSi Shop SOAPs for the DeviceId?(Unconfirmed)
	\|-		\|-
	\| 0x30		\| 0x30

Yellows8: /* DSi System Transfer */

2011-06-14T23:44:13Z

DSi System Transfer

← Older revision		Revision as of 03:44, 15 June 2011
Line 10:		Line 10:
	The DSi will then send its country code, username, and serial number to the 3DS, 3DS will send its country-code/username/serial# to DSi as well.		The DSi will then send its country code, username, and serial number to the 3DS, 3DS will send its country-code/username/serial# to DSi as well.
	The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.		The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.

			When the DSi transfer tool and 3DS transfer tool startup, the DSi sends HTTPS SOAP requests to ecs.t.nintendowifi.net, ias.t.nintendowifi.net, and cas.t.nintendowifi.net. The 3DS sends HTTPS (mostly SOAP, unknown why the first one is used) requests to nus.c.nintendowifi.net, ecs.c.nintendowifi.net, and cas.c.nintendowifi.net. When entering the transfer DSiWare list menu, DSi requests from ecs* and cas*, 3DS does likewise.

	When DSi sends the title list, after the first 6 bytes of the 802.11 data payload, is the below header. Following the header is the list of titles.		When DSi sends the title list, after the first 6 bytes of the 802.11 data payload, is the below header. Following the header is the list of titles.

Yellows8: add 3ds title list header.

2011-06-08T04:29:38Z

add 3ds title list header.

@@ Line 37: / Line 37: @@
 | 0x48
 | All 0xFF bytes.
 |}

Yellows8: dsi/3ds use same title record format.

2011-06-08T03:31:03Z

dsi/3ds use same title record format.

← Older revision		Revision as of 07:31, 8 June 2011
Line 39:		Line 39:
	\|}		\|}

	=== Title record from DSi ===		=== Title record from DSi and 3DS ===

	Total record size is 0x128 bytes.		Total record size is 0x128 bytes.

Yellows8 at 05:06, 8 June 2011

2011-06-08T03:06:31Z

@@ Line 10: / Line 10: @@
 The DSi will then send its country code, username, and serial number to the 3DS, 3DS will send its country-code/username/serial# to DSi as well.
 The DSi sends a list of owned titles to the 3DS. The 3DS then seems to query the shop server via SOAP to check which titles may be transferred, it then replies to the DSi with a list of titles(of the titles which were sent to it) that can be transferred. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.
 === Title record from DSi ===