Hacking Requesting tutorial to system transfer from O3DS 10.5 sysNAND to N3DS emuNAND, please.

[Meteor7]

Could anyone create or link me to a tutorial on how to do a system transfer from my 10.5 O3DS, with no exploits or cfw on it, to my reiNand New3DS's emuNAND? I've seen reports that it is doable, but I've seen many more reports of failure than success. After much searching, I can't seem to find a guide specific enough while still pertaining to the New3DS. The old guides require you to turn off the wifi switch on the target console at a certain point (something the New3DS doesn't have), so I'm feeling very unsure of the process on a New3DS. Many have failed, but I haven't yet found any reliable information as to what caused the failure.

Thanks for any help.

 

[Ronhero]

As long as both consoles are on 10.5 you can do it over the air.

The only time not possible is emu to sys and n3ds to o3ds

 

[Meteor7]

Alrighty, I'll give it a go...

Ok, it seems like it worked. I picked the "PC transfer" option for my DSi Ware because I thought it'd be the safest choice, but now I don't know which files to transfer from my old SD card. The transfer instructions said to just copy everything to my micro SD, but I'm not really sure that's the right option as some folders don't match what's in my emuNAND's folders. Right now I have this in my O3DS SD card after the transfer:

DCIM
>100NIN03 (old pictures)
>101NIN03 (my old videos and screenshots)

Nintendo 3DS
>[a jumbled mess of letters and numbers which MATCHES my emuNAND directory in the same place on my N3DS's micro SD]
>>[a jumbled mess of letters and numbers which DOES NOT MATCH the corresponding folder in my emuNAND directory]
>>>backup
>>>dbs
>>>extdata
>>>Nintendo DSiWare
>>>title

private
>00020400
>>phtcache.bin
>00020500
>>voice (which in turn contains ten other folders labeled 1-10)

So, what do I transfer over? Actually, let me put it this way, what can I mess with WITHOUT BREAKING ANYTHING? Just give me a run down of every file and directory on my reiNand N3DS's micro SD that I should never, ever touch. I know there are some delicate files in the Nintendo 3DS directory, I just need to know which directories I shouldn't add files to. Once I know that, I'll be free to experiment and I'll report back here when I find a solution.

 

[Meteor7]

bumping for the edit.

 

[Ronhero]

When it's done just enjoy

 

[samiam144]

The Nintendo 3DS folder is the only folder you have to transfer to have your games, saves, etc.

 

[Meteor7]

The Nintendo 3DS folder is the only folder you have to transfer to have your games, saves, etc.

But this will create a separate "jumbled numbers" folder inside my first "jumbled" folder inside the Nintendo 3DS folder. Should I copy the contents of the "jumbled" folder into the one which already exists in my N3DS's micro SD/Nintendo 3DS/"jumbled emuNAND"/"jumbled"/ (which is the one which corresponds to the one which doesn't match) or do I just copy the entirety of my Nintendo 3DS folder onto my micro SD, merging the old with the new and creating another directory in my "jumbled" emuNAND folder?

--------------------- MERGED ---------------------------

Actually, just tell me if adding files to my Nintendo 3DS directory on my micro SD would be unsafe in any way. If it's cool, I can figure out the rest for myself.

 

[samiam144]

But this will create a separate "jumbled numbers" folder inside my first "jumbled" folder inside the Nintendo 3DS folder. Should I copy the contents of the "jumbled" folder into the one which already exists in my N3DS's micro SD/Nintendo 3DS/"jumbled emuNAND"/"jumbled"/ (which is the one which corresponds to the one which doesn't match) or do I just copy the entirety of my Nintendo 3DS folder onto my micro SD, merging the old with the new and creating another directory in my "jumbled" emuNAND folder?

--------------------- MERGED ---------------------------

Actually, just tell me if adding files to my Nintendo 3DS directory on my micro SD would be unsafe in any way. If it's cool, I can figure out the rest for myself.

Personally, I would backup the Nintendo 3DS folder on the N3DS microSD and then delete it, and then I would transfer the Nintendo 3DS folder from the O3DS SD card to the N3DS SD card. That way, you can always restore the folder if you have issues.

 

[Meteor7]

Personally, I would backup the Nintendo 3DS folder on the N3DS microSD and then delete it, and then I would transfer the Nintendo 3DS folder from the O3DS SD card to the N3DS SD card. That way, you can always restore the folder if you have issues.

That sounds super dangerous. Doesn't the Nintendo 3DS hold important sys and emuNAND files? Or maybe I'm overestimating the volatility of this folder?

 

[samiam144]

That sounds super dangerous. Doesn't the Nintendo 3DS hold important sys and emuNAND files? Or maybe I'm overestimating the volatility of this folder?

But, you will have a backup on your PC lol. It does hold all your data, which is why you can back it up and restore it if anything goes wrong.
Anyways, all the data that you need to transfer to your new 3ds lies within that folder on your o3ds SD card, so placing it on your N3DS microSD card (not merging it with the existing one) is what you want to do.

 

[Meteor7]

But, you will have a backup on your PC lol. It does hold all your data, which is why you can back it up and restore it if anything goes wrong.
Anyways, all the data that you need to transfer to your new 3ds lies within that folder on your o3ds SD card, so placing it on your N3DS microSD card (not merging it with the existing one) is what you want to do.

But that will only leave one jumbled directory in my Nintendo 3DS folder. Remember, this N3DS has an emuNAND and runs reiNand. I remember, back when I set up an emuNAND, the way I could tell that the emuNAND and sysNAND were unlinked was that two jumbled folders appeared in the Nintendo 3DS folder, representing sys and emu NAND. It feels like my emuNAND will mess up if I just get rid of the directory and who knows what'll happen to the sysNAND.

...oof, I think I might be acting overly cautious. I'm temped to just start adding files and see what comes out. (after an SD backup, that is)

 

[samiam144]

But that will only leave one jumbled directory in my Nintendo 3DS folder. Remember, this N3DS has an emuNAND and runs reiNand. I remember, back when I set up an emuNAND, the way I could tell that the emuNAND and sysNAND were unlinked was that two jumbled folders appeared in the Nintendo 3DS folder, representing sys and emu NAND. It feels like my emuNAND will mess up if I just get rid of the directory and who knows what'll happen to the sysNAND.

...oof, I think I might be acting overly cautious. I'm temped to just start adding files and see what comes out. (after an SD backup, that is)

You're right. But remember, you did a System Transfer to your EmuNAND, so one of the jumbled folders that belongs to your sysnand is actually the single one you have on your O3DS SD Card, because the "jumbled" letters and numbers is actually the ID of the nand. Since your O3DS Sysnand is now in your N3DS EmuNAND, you need to transfer that one jumbled folder from your O3DS SD Card to your N3DS microSD so that the ID folder matches your "new" EmuNAND ID. But I was wrong before; the jumbled/ID folder that belongs to your N3DS SysNAND should stay on the microSD card. So basically:

O3DS SD Card
-Nintendo 3DS Folder
---jumbled folder, i.e. the ID folder that belonged to your O3DS SysNAND before the system transfer

N3DS MicroSD Card
-Nintendo 3DS Folder
---ID folder belonging to your N3DS SysNAND
---ID folder that belonged to your EmuNAND before doing the system transfer (this is now obsolete after doing the system transfer, and you can probably delete it now)
---ID folder that belongs to your EmuNAND after doing the system transfer; this is because your EmuNAND now has the same ID as your O3DS Sysnand. This should be the exact same folder as the one on the O3DS SD Card mentioned above.

 

[Meteor7]

WELL THEN! Not only was that very explicit and concise, but it worked perfectly. Thanks muchly, samiam144! Every game and save is right there.

So, for those who were wondering how to do something like this, it's almost identical to a normal system transfer, except for that one scary moment.

Basically, once you transfer from your sysNAND of the original 3DS to the emuNAND of the target 3DS with the normal system transfer process, the target 3DS will restart. Now, I tried to force it to boot into menuhax the way you can do when you exit the settings menu, but no such luck. It booted straight into the settings menu of the sysNAND while giving the message "trying to connect to the internet to verify the transfer." (I'm paraphrasing the message).

This is the point at which I freaked right the f*** out. You can't exit to the home menu or do anything during this, but DO NOT WORRY AND DON'T FORCE A SHUTDOWN. Your 3DS will not update, you will just get an error message and be kicked back to the home screen of your sysNAND (It's fine, you'll still be on your original sysNAND firmware.) If you try and boot into your emuNAND from here, you'll be taken immediately to the settings menu where it will try and finalize the transfer, which it will always fail.

Basically, what you need to do after that is boot into your sysNAND (which will allow you access to your home screen) and turn wifi off. Boot back to emuNAND and the transfer finalization process will give you a new error message which will allow you to cancel the transfer. Do it and you should get a message basically saying that your NNID has been transferred and some other words were there, I dunno, it's not important. If you chose the PC transfer option, you need to do exactly as samiam144 instructed. If you didn't, then those files probably came over during the transfer just fine, or something.

After all that's been done, go into the eShop on your emuNAND to start a 5 minute long verification process where -I think- Nintendo's servers basically register that your NNID and your game licences have transferred to a new system. After that, everything you had before should show up like magic.

The only difference between the method described above and the process described here: http://hackinformer.com/forum/thread-336.html is that, in order to disable the wifi and "interrupt" the transfer process (in quotes, because the transfer is essentially finished at that point), you need to boot to your sysNAND and use the menu options instead of using the switch on O3DSs. Other than that, same story. If there's one thing to remember, it's that when it boots into sysNAND and connects to the internet, don't freak out and turn off your console. I don't know what that would do, mind you, but it's unnecessary.

 

[Quantumcat]

WELL THEN! Not only was that very explicit and concise, but it worked perfectly. Thanks muchly, samiam144! Every game and save is right there.

So, for those who were wondering how to do something like this, it's almost identical to a normal system transfer, except for that one scary moment.

Basically, once you transfer from your sysNAND of the original 3DS to the emuNAND of the target 3DS with the normal system transfer process, the target 3DS will restart. Now, I tried to force it to boot into menuhax the way you can do when you exit the settings menu, but no such luck. It booted straight into the settings menu of the sysNAND while giving the message "trying to connect to the internet to verify the transfer." (I'm paraphrasing the message).

This is the point at which I freaked right the f*** out. You can't exit to the home menu or do anything during this, but DO NOT WORRY AND DON'T FORCE A SHUTDOWN. Your 3DS will not update, you will just get an error message and be kicked back to the home screen of your sysNAND (It's fine, you'll still be on your original sysNAND firmware.) If you try and boot into your emuNAND from here, you'll be taken immediately to the settings menu where it will try and finalize the transfer, which it will always fail.

Basically, what you need to do after that is boot into your sysNAND (which will allow you access to your home screen) and turn wifi off. Boot back to emuNAND and the transfer finalization process will give you a new error message which will allow you to cancel the transfer. Do it and you should get a message basically saying that your NNID has been transferred and some other words were there, I dunno, it's not important. If you chose the PC transfer option, you need to do exactly as samiam144 instructed. If you didn't, then those files probably came over during the transfer just fine, or something.

After all that's been done, go into the eShop on your emuNAND to start a 5 minute long verification process where -I think- Nintendo's servers basically register that your NNID and your game licences have transferred to a new system. After that, everything you had before should show up like magic.

The only difference between the method described above and the process described here: http://hackinformer.com/forum/thread-336.html is that, in order to disable the wifi and "interrupt" the transfer process (in quotes, because the transfer is essentially finished at that point), you need to boot to your sysNAND and use the menu options instead of using the switch on O3DSs. Other than that, same story. If there's one thing to remember, it's that when it boots into sysNAND and connects to the internet, don't freak out and turn off your console. I don't know what that would do, mind you, but it's unnecessary.

I'm surprised you didn't find anything when you searched this forum, over the last year or so I have replied to like ten people asking how to do a system transfer with clear step-by-steps including the solution for when the transfer seems stuck.

 

[Meteor7]

I'm surprised you didn't find anything when you searched this forum, over the last year or so I have replied to like ten people asking how to do a system transfer with clear step-by-steps including the solution for when the transfer seems stuck.

I had found 2 on this site, but they seemed to only pertain to the O3DS. I wasn't sure if I would have the opportunity to turn off wifi and interrupt the process on a N3DS without that wifi switch, so I was hesitant to begin an irreversible process without knowing exactly what would happen.

 

[fireguy85]

Any chance you had Pokemon Shuffleand/or Rumble World? Were you able to retain save data? These are the only two that aren't working for me..

 

[Meteor7]

Any chance you had Pokemon Shuffleand/or Rumble World? Were you able to retain save data? These are the only two that aren't working for me..

I have neither, sorry. Pokemon savedata had been tricky to work with in the past, so maybe look up a tutorial dealing specifically with that. I know those aren't main-series titles, but that's all the advice I can give. Good luck.