Got my Sky3DS and sucessfully transferred all my Card1 saves (over two dozens). Only need to have an original CardID and correct EEPROM ID size (may differ for several titles in the Sky3DS template). Save converter attached.
I ran the perl script on my save file (EEPROM) dumped via launcher.dat. However, it was not recognized still. I used a template file with my own private headers and IDs so I thought it would work. Are there any missing pieces that might be preventing it from working? The two carts I tried were Mario Kart 7 and Crosswords Plus - both failed.
Sharpzz - you'll need a perl interpreter to be able to run the script, they are freely available for download for various OSes. Once you have it installed rename it to skysave.pl and do:
perl skysave.pl <template file name> <save file / EEPROM> <cart code (e.g. AMKE for MK7)>
For Mario Kart there is two versions - 1.0 and 1.1 win integrated patch, saves are not compatible between them, so just try with the right rom.
For Crosswords Plus, check the EEPROM dump size, I suppose it is 128K, but template is for 512k saves and this matters!
Change C2 22 13 with C2 22 11, rewrite ROM to micro SD, restore save and try once again.
Duke - I don't think the issue is with the Mario Kart version. I opened the result of your perl script (amke.sav) in a hex editor and after the initial header (which was correct) it was all 0xFF the rest of the way. For some reason it is not copying the original info from my sav file (which I viewed in the hex editor so I know it exists). Any idea why that might happen? Same deal with Crosswords, all 0xFF after the header (even after changing to C2 22 11).
For Mario Kart there is two versions - 1.0 and 1.1 win integrated patch, saves are not compatible between them, so just try with the right rom.
So it's better to use ROM 1.1 to avoid having to download the update and leaving more free space on the 3DS?
That's nice to know.Yes, unless you have to transfer save data from your retail card with 1.0 rom.
That's nice to know.
Just checked my ROM, it says CTR-P-AMKP so it should be v. 1.1.
Check firmware version, they are both AMKP, but 1.1 is fw 4+
If you played on the sky with the default template, only the repeat CTR fail encoded saves can be converted back because you can't change card Id of the retail card while save is cyphered with the key derived from it. Skip 88 bytes header in sky save and trim to the original 128 or 512 KB and you have the EEPROM dump.One final question - more a curiosity than anything. How difficult would it be to convert from the Sky3DS save back to the version that could be copied back to the retail cart via launcher.dat browser exploit? I know a little perl but haven't programmed in it for quite a while.
If you played on the sky with the default template, only the repeat CTR fail encoded saves can be converted back because you can't change card Id of the retail card while save is cyphered with the key derived from it. Skip 88 bytes header in sky save and trim to the original 128 or 512 KB and you have the EEPROM dump.
Just did it successfully. Chopped off first 88 bytes, then removed all the 0xFF at the end to bring it to the correct size. Then used launcher.dat exploit to restore to the original cartridge. It worked!! I now have a safe method of going back to the cartridge if needed, it looks like. Thanks again for the help, we might want to make this info a sticky / FAQ since it's the only way I've found so far to use original saves on Sky3DS (and vice-versa).
Wait, so does this allow you to backup and restore save files to a 3DS game cartidge, even if it's not the same copy that you used for the Gateway 3DS?
For example, if I have 5 copies of a 3DS game, all brand new and sealed, this would allow me to write a gamesave to all copies of that game?
I ask this because I know before you were not able to do this, and now it seems like you can.
Saves with 1.0/repeat CTR fail encryption are compatible with any card of the title, while newer save encryptions based on the CardID unique for each physical game card, so save transfer is not possible.Wait, so does this allow you to backup and restore save files to a 3DS game cartidge, even if it's not the same copy that you used for the Gateway 3DS?
For example, if I have 5 copies of a 3DS game, all brand new and sealed, this would allow me to write a gamesave to all copies of that game?
I ask this because I know before you were not able to do this, and now it seems like you can.
Thanks!
Saves with 1.0/repeat CTR fail encryption are compatible with any card of the title, while newer save encryptions based on the CardID unique for each physical game card, so save transfer is not possible.