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.
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...
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!
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...
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!
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?
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?
I FORGOT!!!
You must also transfer this folder (Mii maker should work now) : nand:/data/<ID0>/extdata/00048000/f000000b
How about doing the Activity Log? Would that work the same way?