System Transfer: Difference between revisions
No edit summary |
|||
Line 5: | Line 5: | ||
With the DSiWare DSi->3DS transfer, savegames are not transferred. | 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. | 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. | |||
== 3DSWare Transfer == | == 3DSWare Transfer == |