I did not know about hydroseed, that's useful, but using the "CTRTransfer Ticket Copy" should work just the same.
Hydroseed is a windows program that takes
seeddb.bin and breaks it apart into individual DAT files for offline seed importing with FBI.
The "CTRTransfer Ticket Copy" found in GM9Megascript mounts the backed up
ticket.bak after doing CTRTransfer and dumps all the legit purchased eShop tickets. Those tickets can't be installed on any other systems. There's a drawback where continually dumping and reinstalling legit eShop tickets causes GodMode9 to no longer acknowledge them; they'll eventually no longer be re-dump-able.
And yeah, I did already mention that NNID transfer isn't possible offline.
The files I didn't mention in detail are just not needed so it wasn't worth explaining for the purposes of manual system transfer.
I wanted to add extra clarification on why many of those NAND files should not be used or manually transferred over to a different system, in case people get any funny ideas..
Looks like some of the files can't be transferred as easily as I thought. I think transferring movable.sed would likely not result in a ban. Not likely that Nintendo is gonna ban anyone on 3DS at this point. What makes you say the eShop will be blocked? It's just encryption keys for SD data, it shouldn't make a difference.
Anytime someone does a
Format System Memory or
System Transfer, a replacement or edited
movable.sed is re-derived from the
LocalFriendCodeSeed_B.
Half of that
KeyY that controls encrypting the
Nintendo 3DS folder happens to also be a part of the
LFCS_B. The second half is derived from the first half with a counter value.
If the 3DS/2DS has a nonvalid
movable.sed where it doesn't contain an entire copy of a real/signed
LFCS_B, you won't be allowed to go in the Nintendo eShop. This includes faking an entire
movable.sed. I also tried this with like a single hex edit in the
LFCS_B portion of my n3DSXL's actual
movable.sed with intact
KeyY. It's all no go.
If you manually clone the entire NAND (ie, full blown [CTR + TWL] Transfer) from one system onto another like-new/old system and try to access eShop, you get blocked and warned with error code
022-2591. I once flashed my niece's n3DS NAND image on my n3DSXL while researching if Decrypt9 CTRTransfer could be made viable on GodMode9 through the
[S:] SYSNAND VIRTUAL. In the middle of checking stuff out, I accidentally launched Nintendo eShop while trying to tap the icon for System Settings... Opps. While neither of them are banned, I wouldn't place my trust in doing that again.
There are some people who think they're smart alecks by,
- backing up the SysNAND *.bin image on their source system
- copying the Nintendo 3DS folder on a separate SD card
- System Transferring their NNID & user profile over to a target system
- restoring the SysNAND on their source system
- sharing the same set of SD titles where both systems' movable.sed files have the exact same KeyY
When the source system tries to access eShop with its original NAND setup, Nintendo sees in their sever record that it should no longer have that
KeyY and NNID. The
movable.sed also has a mysterious 4 bytes (block 0x120-123) that is believed to be server recorded as another security measure when facilitating official System Transfer. When you fail those server checks, Nintendo may come to the conclusion you have custom firmware and performed unauthorized/homebrew System Transfer as an attempt to circumvent their piracy protection, leading to the possible taken action of banning both source and target systems.
Speaking of shared
KeyY, this idea has been tried before with poor outcome.
LocalFriendCodeSeed_B is indeed tied to movable.sed in some way but clearly that doesn't matter too much as people that have unbanned their consoles with LFCS_B are still able to use their consoles online (besides eShop not working but that's for unrelated reasons), it just contains encryption keys after all so as long as that matches the SD encryption there should be no issues.
Yes,
LFCS_B banned from online game play is separate from
movable.sed ban from Nintendo eShop.
However, an issue can arise when replacing
LFCS_B. As was mentioned above, formatting the system memory will replace your
movable.sed with a new one derived from that
LFCS_B. There's a chance Nintendo will notice your system and whichever donor system that lent that
LFCS_B have similar
movable.sed, which brings back the point of whether or not you're in the green if you've done official System Transfer.
Transferring friend code and friend list to a new console is possible. I've seen people do manual system transfers in the past and really the only thing that wasn't transferrable was the NNID, but that was between two consoles of the same region, not that that should matter for friend code but does matter for some other things so you can't just transfer all the system save data and expect things to work. I just don't know if those two files are enough to do it.
Same here. I don't know enough about successfully injecting back the Friends List. The few attempts I've reformatted my n3DSXL with incremental changed
KeyY, launching the imported Friends List would give a corrupted error message and state that it'll be deleted. Perhaps Checkpoint or JKSM is better equipped in backing up + restoring this.
There's always the tried and true method: bust out the pen and paper.
SD transfer is useful, I guess it would be easier to use that (but also a lot slower whereas this is a very quick process).
This "SDTransfer" is a very recent development. People often place too much emphasis on speed versus proper end results. There is a bit of good news about the performance aspect. Since those CMAC hurdles have been mapped out, it's possible for this feature to be implemented on a desktop program.
I did not know the part about not being able to transfer legit purchased tickets but I'm just kinda assuming they have no legit purchased content and in any case any legit content they had won't be legit anymore if they can't transfer their NNID over so does it really matter?
Correct. Their purchased titles would be rendered nonlegit due to the lose of those legit tickets. This would be a concern if
@Tired302 has hard-to-find titles that can't be replaced or redownloaded (no sources from
that ISO title) and does not personally keep CIA backups.
That eShop access after region change thing only works if eShop has never been opened on the console IIRC and for those consoles that came with a demo preinstalled it won't work at all as those have already been "connected" to the eShop in some way. Unless this is a different method.
It's a different method where new series 3DS/2DS that has already accessed their native region Nintendo eShop can have its firmware region changed and then system transferred with borrowed NNID in order to gain access to its adopted region's eShop.
I don't believe this can be adapted in moving the NNID from USA region server to JPN/EUR/etc.