Changes

Jump to navigation Jump to search
1,633 bytes added ,  18:44, 18 December 2021
m
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.
   −
=== Title record from DSi ===
+
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.
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Length
 +
! Notes
 +
|-
 +
| 0x0
 +
| 0x4
 +
| Always zero?
 +
|-
 +
| 0x0
 +
| 0x4
 +
| ?
 +
|-
 +
| 0x8
 +
| 0x4
 +
| Total titles?
 +
|-
 +
| 0xc
 +
| 0x1
 +
| Filler
 +
|-
 +
| 0xd
 +
| 0x48
 +
| All 0xFF bytes.
 +
|}
 +
 
 +
3DS title list header:
 +
{| class="wikitable" border="1"
 +
|-
 +
! Offset
 +
! Length
 +
! Notes
 +
|-
 +
| 0x0
 +
| 0x4
 +
| ?
 +
|-
 +
| 0x4
 +
| 0x4
 +
| Usually zero?
 +
|-
 +
| 0x8
 +
| 0x4
 +
| ?
 +
|-
 +
| 0xc
 +
| 0x4
 +
| Total titles?
 +
|-
 +
| 0x10
 +
| 0x4
 +
| ?
 +
|-
 +
| 0x14
 +
| 0x4
 +
| ?
 +
|-
 +
| 0x18
 +
| 0xf
 +
| 3DS serial number
 +
|-
 +
| 0x27
 +
| 0x11
 +
| Bytes alternates between 0xbd and 0xf7: first byte is 0xbd, second is 0xf7, third is 0xbd etc.
 +
|-
 +
| 0x28
 +
| 0x8
 +
| Unknown, ASCII 3DS ticket consoleID used with DSi Shop SOAPs for the DeviceId?(Unconfirmed)
 +
|-
 +
| 0x30
 +
| 0x18
 +
| Always zero?
 +
|}
 +
 
 +
=== Title record from DSi and 3DS ===
    
Total record size is 0x128 bytes.
 
Total record size is 0x128 bytes.
Line 51: 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.
 +
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].
22

edits

Navigation menu