Difference between revisions of "System Transfer"
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. | ||
+ | |||
+ | === Title record from DSi === | ||
+ | |||
+ | Total record size is 0x128 bytes. | ||
+ | {| class="wikitable" border="1" | ||
+ | |- | ||
+ | ! Offset | ||
+ | ! Length | ||
+ | ! Notes | ||
+ | |- | ||
+ | | 0x0 | ||
+ | | 0x8 | ||
+ | | TitleID | ||
+ | |- | ||
+ | | 0x8 | ||
+ | | 0x8 | ||
+ | | Little-endian ticketID | ||
+ | |- | ||
+ | | 0x10 | ||
+ | | 0x4 | ||
+ | | Usually zero? | ||
+ | |- | ||
+ | | 0x14 | ||
+ | | 0x4 | ||
+ | | Usually one? | ||
+ | |- | ||
+ | | 0x18 | ||
+ | | 0x4 | ||
+ | | Some ID? | ||
+ | |- | ||
+ | | 0x1c | ||
+ | | 0x4 | ||
+ | | Usually zero? | ||
+ | |- | ||
+ | | 0x20 | ||
+ | | ? | ||
+ | | Sometimes the title name is stored here? | ||
+ | |} | ||
== 3DSWare Transfer == | == 3DSWare Transfer == |
Revision as of 05:40, 8 June 2011
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
With the DSiWare DSi->3DS transfer, savegames are not transferred. When transferring DSiWare, the DSi system transfer title will send a SOAP request to the DSi Shop server, this transfers the DSiWare license/ticket to the 3DS shop account. The DSi title will then delete the ticket from NAND. The 3DS will then download the ticket, tmd, and content immediately from shop/CDN.
The 3DS broadcasts beacons with Nintendo tag vendor 0009bf. This includes the 3DS user-name, and possibly some consoleID? The DSi authenticates/associates with some binary SSID. The rest uses cleartext ntr/twl multi-cast communications, a lot of keep-alive frames are sent.
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
Total record size is 0x128 bytes.
Offset | Length | Notes |
---|---|---|
0x0 | 0x8 | TitleID |
0x8 | 0x8 | Little-endian ticketID |
0x10 | 0x4 | Usually zero? |
0x14 | 0x4 | Usually one? |
0x18 | 0x4 | Some ID? |
0x1c | 0x4 | Usually zero? |
0x20 | ? | Sometimes the title name is stored here? |
3DSWare Transfer
3DSWare transfer isn't available yet, would be implemented in another future system update.
See also
Nintendo of Japan System Transfer page.