Hacking Transferring to New Emunand

[Uncle_Iroh]

So I've recently had to transfer to a new Emunand on a new SD card. Since I hadn't unlinked my Sysnand, it is essentially the same Emunand on a different SD (albeit at a higher software version). How can I get back the CIAs from the previous setup? Just Copy Pasting the contents of the previous SD to the new SD doesn't seem to work.

If that is the case, I am prepared to install the CIAs on the new EMunand again. But then how do get back just the save files from the old SD? The contents of the SD appear to be about 12 GB, which is clearly CIA content + saves. Which files are the save files, and how do I recognize them?

 

[Uncle_Iroh]

Bump.

 

[Uncle_Iroh]

Another bump.

 

[DjoeN]

You sure it's the same emunand???

If i'm correct, setting up a new emunand and formatting it to unlink your sysnand and emunand, makes it as a new and you get a new folder in your 3DS folder on your 3DS SD. (It makes a new ID)
Look on your 3DS SD cart en see if it has more then 1 folder under the 3DS folder, if it does, it's another emunand (if you format your 3DS (or make a new emunand and format the emunand, you really have a clean setup to start from, meaning, reinstalling the cia's you had and modifying the saves with savedatafiller 1 by 1 to get them back working.

 

[Uncle_Iroh]

You sure it's the same emunand???

If i'm correct, setting up a new emunand and formatting it to unlink your sysnand and emunand, makes it as a new and you get a new folder in your 3DS folder on your 3DS SD. (It makes a new ID)
Look on your 3DS SD cart en see if it has more then 1 folder under the 3DS folder, if it does, it's another emunand (if you format your 3DS (or make a new emunand and format the emunand, you really have a clean setup to start from, meaning, reinstalling the cia's you had and modifying the saves with savedatafiller 1 by 1 to get them back working.

Well I had never done any unlinking at any point of time, and I still haven't. Even though the current Emunand isn't an actual copy of the previous emunand, it's build from the same sysnand as the previous one.

In this case, what should I do?

 

[DjoeN]

I don't know if it will solve the problem, but get ticket.db from your previous emunand (extract it using rxTools) and inject it back into your new emunand (use rxTools for that to)

As far as i know in basic terms, everything you install gets stored in ticket.db on your NAND (Emunand in this case) so it knows what you have installed and what to look for on your SD

Before you start, make a backup of your SD (copy to pc) and emunand (with emunandtool v1.3) (or make an image with win32diskimager) so you can always revert back to your original state.

 

[Rafael_ZW]

.