HELP] Can’t get old New 3DS data on new New 3DS - movablemoveover.gm9 runs without error but nothing shows up

todley_fartknocker

Member
Newcomer
Joined
Apr 7, 2026
Messages
17
Reaction score
0
Trophies
0
Age
25
XP
34
Country
United States
Hey everyone, I've been trying to get my old 3DS data onto my new 3DS for hours and I'm completely stuck. I'll try to be as detailed as possible.

MY GOAL:
I want all my games, saves, and data from my old New 3DS to show up on my new New 3DS. The old New 3DS is gone — I only have its 128GB SD card and a NAND backup .bin of it.

MY FULL HISTORY (important context):
- I had an old OLD 3DS, which I transferred data from to an old New 3DS via movable.sed swap a while back. So the old New 3DS had data from two different consoles on it.
- The old New 3DS is now gone. I have its 128GB SD card with all the data on it, and luckily I found a full NAND backup .bin (1.2GB) of it saved on the SD card from when I originally modded it.
- I just got a brand new New 3DS and modded it fresh with CFW.

WHAT I HAVE SAVED:
- Full NAND backup .bin of the old New 3DS (1.2GB) — saved on PC and on the 128GB SD card
- essential.exefs from the old New 3DS's gm9/backups folder
- movable.sed extracted from that essential.exefs
- A full PC backup of everything that was on the 128GB SD card before I wiped it for the fresh mod setup (so nothing is permanently lost)
- The 128GB SD card itself, now freshly modded with CFW on the new New 3DS
- Two ID0 folders from the old New 3DS's Nintendo 3DS folder: 7eb0086c909154ee10e39d8d52b2f3bb (5.18GB) and 25cf78119b6bb9f622966061644867d5 (81.2MB) — both copied back onto the 128GB SD card after the fresh mod

WHAT I'VE TRIED STEP BY STEP:
1. Ran movablemoveover.gm9 script in GodMode9 selecting the essential.exefs — got error: "ID0 of source movable.sed does not match any ID0 on the SD card"
2. Mounted the essential.exefs in GodMode9, extracted the movable.sed from it (1KB file)
3. Ran the script again with the movable.sed instead — same error. Script says detected ID0 is 2fe6ad92eb2ab61d549ddb23206f32de, which doesn't match either of the two ID0 folders on the SD card
4. Created a new folder named 2fe6ad92eb2ab61d549ddb23206f32de inside the Nintendo 3DS folder on the 128GB SD card, hoping the script would populate it
5. Ran the script again — this time no error! But nothing shows up on the home menu when I boot normally
6. Copied contents of both old ID0 folders (7eb and 25c) into the new 2fe6ad folder, skipping conflicts — still nothing shows up on home menu
7. Also tried mounting the full 1.2GB NAND backup .bin in GodMode9 to extract movable.sed directly from it, but when mounted the private folder appears completely empty so I couldn't get anything from it

MY QUESTIONS:
1. Why does the detected ID0 (2fe6ad...) not match either of the two ID0 folders from the old New 3DS's SD card? Where is this ID0 coming from?
2. When the script ran without error after I created the 2fe6ad... folder, did it actually do anything? Should data have appeared?
3. Is there a reliable way to extract the movable.sed directly from the 1.2GB NAND backup .bin? The private folder shows as empty when I mount it in GodMode9.
4. Could the issue be that the essential.exefs I'm using is from a different point in time when the old New 3DS had a different movable.sed (i.e. before or after the old OLD 3DS transfer)?
5. What should my next steps be?

Again I have a full backup of everything on PC so nothing is permanently lost — I just can't get the data to show up on the new console. Any help is massively appreciated! I will also answer any questions if it could help!
 
I want all my games, saves, and data from my old New 3DS to show up on my new New 3DS. The old New 3DS is gone — I only have its 128GB SD card and a NAND backup .bin of it.
Instead of wasting more time on this, I suggest you just decrypt your save data with threeSD, reinstall your games, and then restore the save data with Checkpoint.

1. Why does the detected ID0 (2fe6ad...) not match either of the two ID0 folders from the old New 3DS's SD card? Where is this ID0 coming from?
Presumably that is the new ID0 that the new unit created on its own.

4. Created a new folder named 2fe6ad92eb2ab61d549ddb23206f32de inside the Nintendo 3DS folder on the 128GB SD card, hoping the script would populate it
I'm not familiar with precisely how the script works, but this seems like a terrible idea.

Also tried mounting the full 1.2GB NAND backup .bin in GodMode9 to extract movable.sed directly from it, but when mounted the private folder appears completely empty so I couldn't get anything from it
You can try using ninfs instead. (The file may be called movable.bin when you use ninfs.)
 
Instead of wasting more time on this, I suggest you just decrypt your save data with threeSD, reinstall your games, and then restore the save data with Checkpoint.
Not just game data, but custom themes and DSI ware and whatnot.

Edit: I forgot to thank you for responding, I really appreciate it!
 
Not just game data, but custom themes and DSI ware and whatnot.
Not sure what you mean by "DSI ware". That can be re-installed just as easily as any other game. Also, once installed it's generally stored in the NAND and not on the SD card. And if I'm not mistaken, custom themes aren't encrypted at all.
 
  • Like
Reactions: todley_fartknocker
wait that makes a lot of sense! Ok, I’m going to continue to think about what I might miss besides everything else, but so far this sounds like a perfect plan. A quick question (sorry!), is there a way to see every game I had? I’m not quite sure I remember all of the names, being that I had, like, 50 plus games on it lmao!
 
Hey everyone, I've been trying to get my old 3DS data onto my new 3DS for hours and I'm completely stuck. I'll try to be as detailed as possible.

MY GOAL:
I want all my games, saves, and data from my old New 3DS to show up on my new New 3DS. The old New 3DS is gone — I only have its 128GB SD card and a NAND backup .bin of it.

MY FULL HISTORY (important context):
- I had an old OLD 3DS, which I transferred data from to an old New 3DS via movable.sed swap a while back. So the old New 3DS had data from two different consoles on it.
- The old New 3DS is now gone. I have its 128GB SD card with all the data on it, and luckily I found a full NAND backup .bin (1.2GB) of it saved on the SD card from when I originally modded it.
- I just got a brand new New 3DS and modded it fresh with CFW.

WHAT I HAVE SAVED:
- Full NAND backup .bin of the old New 3DS (1.2GB) — saved on PC and on the 128GB SD card
- essential.exefs from the old New 3DS's gm9/backups folder
- movable.sed extracted from that essential.exefs
- A full PC backup of everything that was on the 128GB SD card before I wiped it for the fresh mod setup (so nothing is permanently lost)
- The 128GB SD card itself, now freshly modded with CFW on the new New 3DS
- Two ID0 folders from the old New 3DS's Nintendo 3DS folder: 7eb0086c909154ee10e39d8d52b2f3bb (5.18GB) and 25cf78119b6bb9f622966061644867d5 (81.2MB) — both copied back onto the 128GB SD card after the fresh mod

WHAT I'VE TRIED STEP BY STEP:
1. Ran movablemoveover.gm9 script in GodMode9 selecting the essential.exefs — got error: "ID0 of source movable.sed does not match any ID0 on the SD card"
2. Mounted the essential.exefs in GodMode9, extracted the movable.sed from it (1KB file)
3. Ran the script again with the movable.sed instead — same error. Script says detected ID0 is 2fe6ad92eb2ab61d549ddb23206f32de, which doesn't match either of the two ID0 folders on the SD card
4. Created a new folder named 2fe6ad92eb2ab61d549ddb23206f32de inside the Nintendo 3DS folder on the 128GB SD card, hoping the script would populate it
5. Ran the script again — this time no error! But nothing shows up on the home menu when I boot normally
6. Copied contents of both old ID0 folders (7eb and 25c) into the new 2fe6ad folder, skipping conflicts — still nothing shows up on home menu
7. Also tried mounting the full 1.2GB NAND backup .bin in GodMode9 to extract movable.sed directly from it, but when mounted the private folder appears completely empty so I couldn't get anything from it

MY QUESTIONS:
1. Why does the detected ID0 (2fe6ad...) not match either of the two ID0 folders from the old New 3DS's SD card? Where is this ID0 coming from?
2. When the script ran without error after I created the 2fe6ad... folder, did it actually do anything? Should data have appeared?
3. Is there a reliable way to extract the movable.sed directly from the 1.2GB NAND backup .bin? The private folder shows as empty when I mount it in GodMode9.
4. Could the issue be that the essential.exefs I'm using is from a different point in time when the old New 3DS had a different movable.sed (i.e. before or after the old OLD 3DS transfer)?
5. What should my next steps be?

Again I have a full backup of everything on PC so nothing is permanently lost — I just can't get the data to show up on the new console. Any help is massively appreciated! I will also answer any questions if it could help!
Of course nothing showed up, the folder it was trying to transfer from was empty (because you created an empty folder)
4. Could the issue be that the essential.exefs I'm using is from a different point in time when the old New 3DS had a different movable.sed (i.e. before or after the old OLD 3DS transfer)?
I think this hunch is probably correct. GM9 only creates the essentials.exefs once when you first launch it, if you make any major changes like doing a system transfer it's up to you to create a NAND backup. System transfer completely replaces the movable.sed with the one from the source console. If you have a NAND backup from the old 3DS, even if it's older, the movable.sed from it could still be usable.
 
  • Like
Reactions: todley_fartknocker
Of course nothing showed up, the folder it was trying to transfer from was empty (because you created an empty folder)
4. Could the issue be that the essential.exefs I'm using is from a different point in time when the old New 3DS had a different movable.sed (i.e. before or after the old OLD 3DS transfer)?
I think this hunch is probably correct. GM9 only creates the essentials.exefs once when you first launch it, if you make any major changes like doing a system transfer it's up to you to create a NAND backup. System transfer completely replaces the movable.sed with the one from the source console. If you have a NAND backup from the old 3DS, even if it's older, the movable.sed from it could still be usable.
I see, though my goal is to get all the data back, not just the old o3ds’s. Thank you for helping me understand deeper though!
Post automatically merged:

data with threeSD
Is it possible you could link the website? Also, will I be able to see the full list of games I had so I know which ones to re-download? Sorry for question-bombing again, you are very helpful and I could use all the help I could get!
 
I see, though my goal is to get all the data back, not just the old o3ds’s. Thank you for helping me understand deeper though!
Post automatically merged:


Is it possible you could link the website? Also, will I be able to see the full list of games I had so I know which ones to re-download? Sorry for question-bombing again, you are very helpful and I could use all the help I could get!
That's the neat part. An old movable.sed can still decrypt new content since AFAIK the keys only change when you format, or get replaced by a system transfer.
 
Oh fr! Just to confirm, that movable.sed will have the data from both the old o3ds AND the old n3ds??

Edit: sorry if I’m being redundant
The data is on the SD. The movable.sed just contains an encryption key, the same key is used for all SD data. That's literally all it does.
 
Is it possible you could link the website?
Is it possible for you to search for it..? https://gbatemp.net/threads/restore-save-data-from-dead-3ds-2ds.606907/

Be sure to read the first couple of posts in the thread.

will I be able to see the full list of games I had so I know which ones to re-download?
It is easiest just to look up the title IDs one by one on https://hax0kartik.github.io/3dsdb/ .

Oh fr! Just to confirm, that movable.sed will have the data from both the old o3ds AND the old n3ds??
You seem to be deeply confused as to what exactly the movable.sed is.

So the old New 3DS had data from two different consoles on it.
A 3DS NAND cannot store "data from two different consoles".
 
Is it possible for you to search for it..?
Sorry! I should’ve, I was just scared I’d click the wrong thing
Post automatically merged:

The data is on the SD. The movable.sed just contains an encryption key, the same key is used for all SD data. That's literally all it does.
ohhhh!!! i didn’t know that, thanks so much. Sorry again for being redundant, but now that I know this, what should I do? Should I like, change any folders? Or just run the script? Thank you so so much again
 
Last edited by todley_fartknocker,
Sorry! I should’ve, I was just scared I’d click the wrong thing
Post automatically merged:


ohhhh!!! i didn’t know that, thanks so much. Sorry again for being redundant, but now that I know this, what should I do? Should I like, change any folders? Or just run the script? Thank you so so much again
If you have a movable.sed from the old 3DS from before the transfer (or it won't have the right ID0), try the script with it.
 
If you have a movable.sed from the old 3DS from before the transfer (or it won't have the right ID0), try the script with it.
Ok, will do
Post automatically merged:

If you have a movable.sed from the old 3DS from before the transfer (or it won't have the right ID0), try the script with it.
I tried this, and the home menu showed nothing there. even the pre-installed modded apps (fbi, anemone, universal updater, etc) werent there. Is there something i did wrong?
 
Last edited by todley_fartknocker,
I understand and it’s probably what I will do, I’m just scared there’s more that will be left out like extdata or dlc
There are ways to transfer extdata. DLC can either be downloaded from the eShop again or otherwise re-installed however you installed it in the first place.

If you insist on spending even more hours trying to get this script to work, I suggest you follow all the instructions at https://wiki.hacks.guide/wiki/3DS:Movable_Moveover , because I have no idea what you're trying to do at the moment.
 
thanks so much for all of your help, I am going to take a break from this for a bit. it's very confusing, but your guys's help has allowed me to (sorta) understand it better.
 
Instead of wasting more time on this, I suggest you just decrypt your save data with threeSD, reinstall your games, and then restore the save data with Checkpoint.
Hi, I'm back and planning on doing this now, I was just wondering before I do if I will be able to find out which games I had installed via QR codes I got on r/3dsqrcodes (not “real” games; Roms or homebrew for example) I don’t have a clear list of everything I had.
 
I will be able to find out which games I had installed via QR codes I got on r/3dsqrcodes (not “real” games; Roms or homebrew for example) I don’t have a clear list of everything I had.
Perhaps if there's a game you have no intention of playing ever again, you should just refrain from installing it..?

If you insist, you can probably inject the movable.sed as described in https://gbatemp.net/threads/restore-save-data-from-dead-3ds-2ds.606907/ and read out the titles using godmode9.
 

Site & Scene News

Popular threads in this forum