Ok, now where do I put the .see?There's a tutorial of sorts for fuse-3DS over here:
https://gbatemp.net/threads/tutoria...backups-and-sd-contents-with-fuse-3ds.499994/
After this what do I do?"It didn't work" is rarely a useful phrase. Can you be more specific?
If you have essential.exefs open in fuse-3DS, then you need to copy movable.bin to somewhere else on your hard drive. (And then rename it, if you like.)
Afterwards you will need to mount your old SD card (or preferably a backup of your old SD card) in fuse-3DS, while specifying the location of the movable.sed.
Yeah but what I don't understand is, why do I need to do this? And what exactly I'm doing?Did you understand the tutorial? Did you try running fuse-3ds? Click the buttons and see what they do.
This is only a little bit complicated, but you don't have to worry about permanently messing anything up like you would on the 3DS.
You want to use the save data that was stored on your old 3DS. This save data is encrypted, and the encryption key is stored in movable.sed. To decrypt the data, you need to mount your SD card backup in fuse-3DS, and then copy the save data files to somewhere else on your hard drive.Yeah but what I don't understand is, why do I need to do this?
So I have to do this manually for every game and download the CIA again for each one?You want to use the save data that was stored on your old 3DS. This save data is encrypted, and the encryption key is stored in movable.sed. To decrypt the data, you need to mount your SD card backup in fuse-3DS, and then copy the save data files to somewhere else on your hard drive.
After that, you need to unpack the decrypted data using 3ds-save-tool , and that will give you files that you can use on your new 3DS with Checkpoint or JKSM.
I should add that In order to find the save data for a game in your SD card backup, you'll need the title ID number from https://hax0kartik.github.io/3dsdb/ .
Pretty much, yes.So I have to do this manually for every game and download the CIA again for each one?
Ok that was a lot to take in and I don't know if I can do thisYou can GM9 dump your titles back into CIA. @Pluritato, you have a lot to cover: movable.sed, 0x10 bytes keyY and <ID0> (in case you did Format System Memory), tickets, and the importance of order of reinstalling a game versus overwriting/deleting the save data.
Read all of these:
shouldnt that be a movable.sed not a .see file that you have?Does anyone know why my .see doesn't work. It says
0:/gm9/out
No usable entries found
Yeah sorry autocorrectorshouldnt that be a movable.sed not a .see file that you have?
I'm skipping a step or it's just impossible?shouldnt that be a movable.sed not a .see file that you have?
Is there a video tutorial or something like that? Is really hard for me to understand everything on those posts it's too complicated and English is not my first languageYou can GM9 dump your titles back into CIA. @Pluritato, you have a lot to cover: movable.sed, 0x10 bytes keyY and <ID0> (in case you did Format System Memory), tickets, and the importance of order of reinstalling a game versus overwriting/deleting the save data.
Read all of these:
Video guides are not recommended because they're often outdated, missing details, might not explain things adequately, and are sometimes outright wrong. Also, there are no video tutorials of this kind of 3DS data recovery because this is a complicated subject with many different components. Those who run into these problems may follow similiar procedures but can end up having one or several different steps where these can make the difference between success and failure.Is there a video tutorial or something like that? Is really hard for me to understand everything on those posts it's too complicated and English is not my first language
Ok, thank you so much for your help I'll wait and try with an emunand that should work for the time beingVideo guides are not recommended because they're often outdated, missing details, might not explain things adequately, and are sometimes outright wrong. Also, there are no video tutorials of this kind of 3DS data recovery because this is a complicated subject with many different components. Those who run into these problems may follow similiar procedures but can end up having one or several different steps where these can make the difference between success and failure.
Your problem can be approached from several angles:
- fuse-3ds with movable.sed to mount the Nintendo 3DS folder and extract + decrypt the 00000001.sav files. Requires downloading replacement CIAs.
- Temporarily use your previous 3DS NAND image on your replacement system to dump the CIAs and back up the saves.
- Temporarily inject only the movable.sed and restore the tickets, so you can dump the CIAs and back up the saves.
I would help you out 1-on-1, but I'm mentally burnt at this moment. The others here will have to fill you in. For the time being, you should leave your 3DS alone and read/research enough to know what you'll need to do.
- You do not want to use a foreign movable.sed (and other personal files) on a permanent basis if it wasn't involved in an officially Nintendo sanctioned System Transfer.
- There are a bunch of other precautions and warnings. Doing any one thing wrong can corrupt or fail to recover the data, like reinstalling a game will overwrite and delete your previous save data.
- Making backups of your SysNAND and SD card files setup would be super useful from making permanent boo-boos.