Hacking Is there a way to transfer mii Plaza?

[kamesenin888]

Is there a way to transfer the progress of mii Plaza to another system?

 

[motezazer]

You transfer movable.sed and the NAND saves

 

[kamesenin888]

how can i transfer that? i need to decrypt the nand ?

 

[Necrojinsei]

You transfer movable.sed and the NAND saves

Woah, question. How would you go about doing this? I have been attempting to get this for sometime, could you explain the process, or at least link to something that I can use as a guide to beginning the process.

 

[kamesenin888]

i second that

 

[Ichii Giki]

Woah, question. How would you go about doing this? I have been attempting to get this for sometime, could you explain the process, or at least link to something that I can use as a guide to beginning the process.

You can't just transfer the movable.sed file from one system to another. It has system specific values in it that cause a brick if it is simply moved from the NAND of one machine to another. You can move it from EmuNAND/SysNAND on the SAME system for example if your NANDs are linked, but not to a different system.

I have also been looking for a method to modify the movable.sed file as you would in a system transfer to accomplish moving things such as saves for System Titles like Mii Plaza/ARGames/Face Raiders/etc. If this ever happens, it would basically be a pseudo-manual system transfer...

 

[Necrojinsei]

You can't just transfer the movable.sed file from one system to another. It has system specific values in it that cause a brick if it is simply moved from the NAND of one machine to another. You can move it from EmuNAND/SysNAND on the SAME system for example if your NANDs are linked, but not to a different system.

I have also been looking for a method to modify the movable.sed file as you would in a system transfer to accomplish moving things such as saves for System Titles like Mii Plaza/ARGames/Face Raiders/etc. If this ever happens, it would basically be a pseudo-manual system transfer...

That's what I thought. I did look into just transferring the data through different means, but they always creat issues since it's console specific. It's something that remains an issue.

Unless you mean there is another way motezazer.

 

[motezazer]

You can't just transfer the movable.sed file from one system to another. It has system specific values in it that cause a brick if it is simply moved from the NAND of one machine to another. You can move it from EmuNAND/SysNAND on the SAME system for example if your NANDs are linked, but not to a different system.

I have also been looking for a method to modify the movable.sed file as you would in a system transfer to accomplish moving things such as saves for System Titles like Mii Plaza/ARGames/Face Raiders/etc. If this ever happens, it would basically be a pseudo-manual system transfer...

No, you can transfer movable.sed from a system to another.
BUT you must respect these two things :
-you must delete the folder in the data folder
-you need to hex edit the movable.sed
If its size is 0x120, it is good.
If its size is 0x140, you must remove the last 0x20, then you must clear the 4 bytes next to the magic "SEED"
You inject, you recrypt, you launch. You will have the init part, the same you would have after a system format (because it is a system format basically, but with a chosen movable.sed, and not a random one).
Finally, after the initial init, you redump the nand, you decrypt, you inject the saves you want in the nand:/data/<ID0>/sysdata/ folder (for mii plaza you must inject your old 00020228 folder), you recrypt, you inject the NAND, done!

 

[Ichii Giki]

No, you can transfer movable.sed from a system to another.
BUT you must respect these two things :
-you must delete the folder in the data folder
-you need to hex edit the movable.sed
If its size is 0x120, it is good.
If its size is 0x140, you must remove the last 0x20, then you must clear the 4 bytes next to the magic "SEED"
You inject, you recrypt, you launch. You will have the init part, the same you would have after a system format (because it is a system format basically, but with a chosen movable.sed, and not a random one).
Finally, after the initial init, you redump the nand, you decrypt, you inject the saves you want in the nand:/data/<ID0>/sysdata/ folder (for mii plaza you must inject your old 00020228 folder), you recrypt, you inject the NAND, done!

So correct me if I'm wrong, but this means we could do a manual system transfer like this? (Without eShop access on the copied to console of course because the NNID wouldn't be transferred)? If so I may finally be able to use my N3DS and just buy new things on the O3DS and transfer my tickets.db whenever I do so...

 

[veekay]

Would be nice as I already have my NNID transferred to my N3ds, but I screwed up the transfer and didn't get any of the data

 

[motezazer]

So correct me if I'm wrong, but this means we could do a manual system transfer like this? (Without eShop access on the copied to console of course because the NNID wouldn't be transferred)? If so I may finally be able to use my N3DS and just buy new things on the O3DS and transfer my tickets.db whenever I do so...

You can't transfer your ticket.db.
Tickets are tied to the console.
When you do a system transfer, source 3DS send the tickets to eShop, eShop verify signatures, resign for the target 3DS and the target 3DS download them.

 

[Ichii Giki]

No, you can transfer movable.sed from a system to another.
BUT you must respect these two things :
-you must delete the folder in the data folder
-you need to hex edit the movable.sed
If its size is 0x120, it is good.
If its size is 0x140, you must remove the last 0x20, then you must clear the 4 bytes next to the magic "SEED"
You inject, you recrypt, you launch. You will have the init part, the same you would have after a system format (because it is a system format basically, but with a chosen movable.sed, and not a random one).
Finally, after the initial init, you redump the nand, you decrypt, you inject the saves you want in the nand:/data/<ID0>/sysdata/ folder (for mii plaza you must inject your old 00020228 folder), you recrypt, you inject the NAND, done!

So it seems like it worked... I was able to boot the EmuNAND with the modified movable.sed and see transferred saves like my notes, but for Friend List/Mii Maker/Mii Plaza it said my Mii/save/update data was corrupted. I bet this stems from the fact that I have DLC street pass games and other stuff that isn't in the default ticket.db file. However, if you just try to inject the ticket.db of an O3DS, it causes a brick on EmuNAND.

Do you know how I would go about merging my O3DS ticket.db and N3DS ticket.db so it would be able to read all the data from my SD Card/saves? I'm pretty sure this will work once we work out the kinks, because I copied my whole Nintendo 3DS folder from my O3DS and it even loaded a cached theme from the SD card extdata, so it was reading data from the O3DS! Also Mii Maker showed the faces of my stored Miis in the carousel before trying to open it and making me create a new Mii because it said the default Mii was corrupted. Furthermore things like Face Raiders also show the saved face from my save in the banner title. Thanks in advance for any assistance you can provide!

P.S. Can you think of anything besides "sysdata" and "extdata" saves in the "data" folder of NAND dump and ticket.db file that would need to be moved over for a "manual" system transfer like this? I would like to make it as seamless as possible copying from O3DS to N3DS.

 

[Ichii Giki]

You can't transfer your ticket.db.
Tickets are tied to the console.
When you do a system transfer, source 3DS send the tickets to eShop, eShop verify signatures, resign for the target 3DS and the target 3DS download them.

Hmm, if that's the case would I just have to install updates as CIAs (like Streetpass DLC) as normal for Gateway and run everything in Gateway mode? This kinda sucks as I normally run Classic/rxTools on my O3DS and I would have to rip all the cart games I want to play, but still if there is a way to get my Mii Plaza data over, I could still finally start using my N3DS! Since things like rxTools can decrypt your title tickets, could we also somehow dump and re-encrypt them to merge back into the ticket.db of the N3DS?

 

[motezazer]

Hmm, if that's the case would I just have to install updates as CIAs (like Streetpass DLC) as normal for Gateway and run everything in Gateway mode? This kinda sucks as I normally run Classic/rxTools on my O3DS and I would have to rip all the cart games I want to play, but still if there is a way to get my Mii Plaza data over, I could still finally start using my N3DS! Since things like rxTools can decrypt your title tickets, could we also somehow dump and re-encrypt them to merge back into the ticket.db of the N3DS?

No, because on N3DS you doesn't have the ticket at all. And if you try to install your old ticket, this won't work : your console ID is specified within. Of course you can't change it, because it is signed.

For Mii Plaza, sorry, I forgot you must transfer also 00000227

EDIT : And you ALSO must copy the Nintendo 3DS folder of your old SD card.

 

[Ichii Giki]

No, because on N3DS you doesn't have the ticket at all. And if you try to install your old ticket, this won't work : your console ID is specified within. Of course you can't change it, because it is signed.

For Mii Plaza, sorry, I forgot you must transfer also 00000227

EDIT : And you ALSO must copy the Nintendo 3DS folder of your old SD card.

I did transfer both of those (although 217 and 218 for me as it's USA), as well as copying the folder from the old SD card, and it was showing my Miis in the carousel so it was reading data, but it said my data was corrupt when trying to enter Mii Maker/Plaza. Plaza specifically said the update data was corrupt, so I assume it's because it couldn't read the Mii Plaza DLC as the ticket for it wasn't in the default ticket.db. Does that make sense?

I also assume that it might work in Gateway mode with the proper DLC CIAs installed. Does that also seem correct?

P.S. When you say Console ID is specified in the ticket, is this something that would have carried over with the SecureInfo_A file of a region change? As it happens, my O3DS and this N3DS share SecureInfo_A files from doing a region change on the N3DS.

 

[motezazer]

I did transfer both of those (although 217 and 218 for me as it's USA), as well as copying the folder from the old SD card, and it was showing my Miis in the carousel so it was reading data, but it said my data was corrupt when trying to enter Mii Maker/Plaza. Plaza specifically said the update data was corrupt, so I assume it's because it couldn't read the Mii Plaza DLC as the ticket for it wasn't in the default ticket.db. Does that make sense?

I also assume that it might work in Gateway mode with the proper DLC CIAs installed. Does that also seem correct?

With the proper UPDATE installed. That matters.

 

[motezazer]

I FORGOT!!!
You must also transfer this folder (Mii maker should work now) : nand:/data/<ID0>/extdata/00048000/f000000b

 

[Ichii Giki]

I FORGOT!!!
You must also transfer this folder (Mii maker should work now) : nand:/data/<ID0>/extdata/00048000/f000000b

It seems to have worked! After I installed CIAs for the updates and got all the data transferred (as suggested), I can definitely see my Miis in Mii Maker and all of my Streetpass Folk in Mii Plaza! Thank you so much! I think I can finally start using my N3DS now (once I get everything else ripped and installed from my O3DS, heh heh heh)...

 

[veekay]

How about doing the Activity Log? Would that work the same way?

 

[motezazer]

How about doing the Activity Log? Would that work the same way?

nand:/data/<ID0>/sysdata/00010022