6,264
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: − + + + +
→DSi System Transfer
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.
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 the consoleID? The DSi authenticates/associates with some binary SSID. The rest uses cleartext ntr/twl multi-cast communications, most of this is just keep-alive frames and some DSi->3DS command frame.
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 username and serial number to the 3DS, 3DS will send its username/serial# to DSi as well.
The 3DS seems to query the shop server /w SOAP for the list of DSiWare that the DSi owns, as well as titles that are allowed to be transferred? The 3DS sends this title list to the DSi. When the user selects which title to transfer, DSi sends the banner of that title to the 3DS and many frames later the titleID.
== 3DSWare Transfer ==
== 3DSWare Transfer ==