Hacking Is there a way to transfer mii Plaza?

[Arkansaw]

this discussion is only relevant if you are trying to transfer mii plaza data without system transfer, right?

 

[veekay]

this discussion is only relevant if you are trying to transfer mii plaza data without system transfer, right?

That is all I need to do. Mii plaza data and activity log. From o3ds to n3ds

 

[Apache Thunder]

Oh wow I'd thought transferring the movable.sed would be more complicated then this. It's exciting to see that there is finally a way. As for the tickets, I'm not to concerned about that. I would bet I could just keep my current tickets and they would work with the content of the old SD card from my bricked 3DS. I'd just have to reinstall titles my old 3DS didn't have. Though would be a challenge redownloading things from eShop seeing that Gateway STILL has not come out with a fix for 9.6+ emunand on old 3DS.

If I transfer the movable.sed in this way, I assume this would restore my old FC and friends list? Some questions:

1. The 4 bytes after magic seed. Is this 2 or 4 characters in the hexeditor. This part has me a bit confused. I forgot exactly how much data 4 bytes constitutes.
2. When you said if the file is 0x140 to remove the last 0x20, do I just zero that out maintaining the file size or actually remove that from the file so that the file shrinks?

 

[daxtsu]

1. The 4 bytes after magic seed. Is this 2 or 4 characters in the hexeditor. This part has me a bit confused. I forgot exactly how much data 4 bytes constitutes.

It would be eight characters. Every group of two hexadecimal characters (e.g. 00 AA BB CC) represents one byte. Using that same example, 00, AA, BB, CC, that would equate to four bytes.

 

[Ichii Giki]

Oh wow I'd thought transferring the movable.sed would be more complicated than this. It's exciting to see that there is finally a way. As for the tickets, I'm not to concerned about that. I would bet I could just keep my current tickets and they would work with the content of the old SD card from my bricked 3DS. I'd just have to reinstall titles my old 3DS didn't have. Though would be a challenge redownloading things from eShop seeing that Gateway STILL has not come out with a fix for 9.6+ emunand on old 3DS.

If I transfer the movable.sed in this way, I assume this would restore my old FC and friends list? Some questions:

1. The 4 bytes after magic seed. Is this 2 or 4 characters in the hexeditor. This part has me a bit confused. I forgot exactly how much data 4 bytes constitutes.
2. When you said if the file is 0x140 to remove the last 0x20, do I just zero that out maintaining the file size or actually remove that from the file so that the file shrinks?

You remove the last 0x20 completely, shrinking the file size, at least that's what worked for me. However, when I transferred my movable.sed like this, I got Mii Maker/Plaza to show all my old data, but in the Friend List app, it just show me with a ????-????-???? value for friend code. There may be other files in the old NAND that I also need to manually extract and inject into the N3DS NAND. I'm going to try wholesale extraction/import of saves from O3DS EmuNAND to N3DS EmuNAND next and see what does/doesn't properly come over instead of just picking a few applet saves to transfer from the old NAND.

Also in regards to the tickets, they are kind of important. If you want the easiest access that is. I imagine saves from applications with their tickets installed from generic CIAs will show up, but of course you could only run those in Gateway mode. Without importing the associated tickets, when I copied my complete SD card contents from O3DS to N3DS, only system app data seemed to be accessible. I haven't tried installing a generic CIA for an eShop game I have the data for on the SD card yet. If we can properly import the old tickets, then SD content should also work in Classic/SysNAND I think, which I would love. Pretty much a complete manual system transfer (without NNID of course since that is a server-side switch).

It looks like this utility might do the trick with tickets individually extracted from the O3DS (with something like FunkyCIA?):
https://github.com/yifanlu/3DSSystemTools/tree/master/3DSInstallTickets
It compiles to a .3dsx though, so might only be able to do the import through SysNAND with Ninjhax at the moment.

 

[Apache Thunder]

I'm planning on downgrading emunand to 9.2 and once movable.sed is done I will transfer the entire contents of the data folder. My bricked 3DS was on 9.2 at the time, so I will just make emunand be on the same version as well. This will remove any possible compatibility issues with the system save data.

Also I assume I only have to let the console boot up and get to the initialize settings screen? I don't actually have to complete the initial setup and it's already ready? I can just power down and inject the data folder?

 

[Ichii Giki]

I'm planning on downgrading emunand to 9.2 and once movable.sed is done I will transfer the entire contents of the data folder. My bricked 3DS was on 9.2 at the time, so I will just make emunand be on the same version as well. This will remove any possible compatibility issues with the system save data.

Also I assume I only have to let the console boot up and get to the initialize settings screen? I don't actually have to complete the initial setup and it's already ready? I can just power down and inject the data folder?

Not sure about the setup, I just went through it and then injected my data.

In regards to downgrading an existing EmuNAND, what's the easiest way to do so? I may need to do that for some steps on my O3DS that has 9.6/7 EmuNAND with rxTools. Do you manually remove and reinstall titles with something like FBI or is there are more automatic method that I am unaware of?

 

[Apache Thunder]

I just have an older emunand that is a clone of my sysnand basically. I wouldn't exactly call it downgrading now that I think about it.

 

[Ichii Giki]

I just have an older emunand that is a clone of my sysnand basically. I wouldn't exactly call it downgrading now that I think about it.

Aha, well I guess if I do need to actually downgrade, I'll just manually transfer my NAND-based saves/data from my 9.6/7 EmuNAND to my 9.2 EmuNAND backup. Who needs automation!

 

[Apache Thunder]

Alright injected the modified movable.sed...It worked! Didn't get a bricked emunand. So that's a good sign. It already recreated the data folder, so I'm guessing you don't have to go through the initial settings screen at all. Once you get to the language select screen, you can just force power it off and restore the old data folder.

 

[Apache Thunder]

IT *****KING WORKED! Got my old FC and friend list back! Even the custom theme I had installed back then is back! This is kickass!

I also injected the ticket.db from my current 9.5 emunand into my new 9.2 emunand. As expected all the stuff I had installed on the bricked 3DS still shows up. Though some things like savedatafiler and stuff I didn't install from eShop will probably vanish when I visit Data Management. But no big deal, I can just reinstall those.

 

[Ichii Giki]

IT *****KING WORKED! Got my old FC and friend list back! Even the custom theme I installed is back! This is kickass!

Very nice! Did you have to restore any special/specific files to get the friend code/friend list to show up properly? Did it show up properly even with your WIFI off (I had mine disabled at the time I checked it on my N3DS)? I assume your friend code/friend list showed up without doing any NNID shenanigans? Does the console have an NNID linked now (I don't assume the friend code/list has any connection to NNID). I hope none of my issues were because of going from O3DS to N3DS, but not a huge deal if so.

 

[Apache Thunder]

Very nice! Did you have to restore any special/specific files to get the friend code/friend list to show up properly? Did it show up properly even with your WIFI off (I had mine disabled at the time I checked it on my N3DS)? I assume your friend code/friend list showed up without doing any NNID shenanigans? Does the console have an NNID linked now (I don't assume the friend code/list has any connection to NNID). I hope none of my issues were because of going from O3DS to N3DS, but not a huge deal if so.

Friend list operated correctly as far as I can tell. Even one of the friends I had registered shows up as online. Even Nappy's FC/Mii appeared. (though he no longer has me on his system so he'll always appear as offline for me)

I didn't restore anything specific. I just restored the entire data folder from my 9.2 backup from my bricked 3DS.

Note I'm not working with a n3DS like you so you might have to exclude certain files. I'm not sure on that.

My bricked 3DS was linked to my NNID at the time it bricked. I called Nintendo shortly after I got my 3DS XL to manually unlink and move my NNID to the XL. I forgot the password at the time when I was trying to relink the NNID to my XL. I might have issues with that now I got the old stuff restored. I assume I can just revist NNID menu in system settings and change the stored password to the correct one. The NNID account itself though is valid, so I shouldn't have issues using NNID once the password is fixed.

I won't know if NNID works correctly until I run a copy of the new emunand in rxTools on latest firmware as I can't use eShop on 9.2 right now. (that NIM patch floating around only works on NTR CFW)

 

[veekay]

How exactly do you extract files from the actual nand?

 

[Ichii Giki]

How exactly do you extract files from the actual nand?

The same way you would from EmuNAND, make a NAND backup (for example with a hardmod or Gateway menu) of SysNAND, extract the FAT16 ctrNAND partition, then decrypt it with xorpad and mount the xorpadded image with something like WinImage. From there you can extract/edit/inject files as you wish. Afteward you would reverse the process and reflash the edited NAND backup to the system. BE CAREFUL WHEN DOING SYSNAND MODIFICATIONS, ESPECIALLY WIHTOUT A HARDMOD!!! ALWAYS TAKE A BACKUP FIRST SO YOU CAN RECOVER SOMEHOW!!!

 

[Jiro2]

Could someone please write a guide that covers the entire thing? I can try to figure it out from the posts here and the later corrections, but this can get complicated.

 

[veekay]

I'm guessing this would also work if I updated both consoles to 9.7 and did a legit transfer and then just extracted the correct files and moved them back to the 9.5 backups? Hard modded of course.

 

[Ichii Giki]

I'm guessing this would also work if I updated both consoles to 9.7 and did a legit transfer and then just extracted the correct files and moved them back to the 9.5 backups? Hard modded of course.

No reason why not, you're just doing a normal system transfer at that point then decrypting/extracting/injecting the data into an older EmuNAND. This method is more for people with region-changed N3DS consoles that can't do a legit system transfer.

 

[veekay]

It is the decrypting/extracting/injecting that gets me right now. I was able to pull everything, but as far as putting it back into an emunand file and having that work I'm more lost on.

 

[Ichii Giki]

It is the decrypting/extracting/injecting that gets me right now. I was able to pull everything, but as far as putting it back into an emunand file and having that work I'm more lost on.

If you have pulled your saves/movable.sed from a 9.7 NAND dump, putting them back in a 9.5 EmuNAND dump from the same console (pre-system transfer) is mostly the same process, you extract your CTRnand FAT16 partition, decrypt the EmuNAND (as I assume you did with your NAND dump to pull the files) with xorpad, then mount the xorpadded-dump in something like WinImage and replace all the files. Then you reverse this process to pack it back up and inject the modified EmuNAND back onto the SD card.