ROM Hack Transfer saves from EMUNAND to SYSNAND

  • Thread starter Thread starter elhefegaming
  • Start date Start date
  • Views Views 9,018
  • Replies Replies 14
  • Likes Likes 2

elhefegaming

Active Member
Newcomer
Joined
Jul 9, 2018
Messages
28
Reaction score
5
Trophies
0
Age
76
XP
133
Country
United States
Is there a way to do this safely?

The idea would be to start playing a game on emunand as soon as it leaks and then when you purchase the original one be able to continue playing with your saved file but through official SYSNAND, going online etc.

I'd guess using hacdiskmount maybe?
 
Is there a way to do this safely?

The idea would be to start playing a game on emunand as soon as it leaks and then when you purchase the original one be able to continue playing with your saved file but through official SYSNAND, going online etc.

I'd guess using hacdiskmount maybe?
I'm interested in knowing more about this too. Maybe a guide on subject if anyone knows where to find a good one
 
All you have to do is run hekate to launch CFW Stock, then use Edizon or any save manager to import your save files.

This will get you banned if you go online though.
 
All you have to do is run hekate to launch CFW Stock, then use Edizon or any save manager to import your save files.

This will get you banned if you go online though.
even if you're not using cfw when you go online and only doing so just to transfer the save?
 
even if you're not using cfw when you go online and only doing so just to transfer the save?
Yes, merely running CFW once is said to get your NAND dirty and getting exposed to a ban. Though no one really knows what is Nintendo checking to get someone banned.

Anyway, I found this on an old post, and it makes sense, a lot of sense:

found this on reddit.. literally from this site

“From a gbatemp post:

"I did it this way:

Backed up save from hacked console with Checkpoint

Put legit console in flight mode

Take NAND backup

Boot into CFW and restore save(s) with Checkpoint

Take another NAND backup

Open the save-injected NAND backup with hacdiskmount

Copy the specific (console signed) save files for the games I want (I didn't copy them all)

Open the original NAND backup with hacdiskmount

Overwrite the existing saves with the new ones

Restore the original NAND backup, which is essentially the same, except for the 1 or 2 save files you've replaced.

There should be no evidence that CFW was ever run, as it never was under the original NAND backup.

No files should have changed except for the save files you replaced, which are properly signed by your console/Horizon.

Unless Nintendo stores some kind of metadata to detect that the save file(s) have been modified since the last shutdown and current boot-up (which they may), it should be pretty safe (and if they don't already do that they'll know after reading this...). It's the safest way I can think to do it, however it's certainly not ban proof.

LibHac is also able to sign saves, I also did it successfully for a modified save, it requires a bucketload of C# knowledge though currently."

Sounds definitely doable after reading this, however it may require more work than you may have previously thought.”

since you’re using emunand, you probably don’t need to restore as many times.
 
Last edited by Zkajavier,
Does anyone know if the save data between sword and shield are interchangeable?

--------------------- MERGED ---------------------------

I don't understand. Are you guys looking for Checkpoint? If so, check out https://github.com/FlagBrew/Checkpoint/releases
we weren't looking for checkpoint. We were talking about transfering save data from Emunand to Sysnand without being detected using homebrew
 
Does anyone know if the save data between sword and shield are interchangeable?

--------------------- MERGED ---------------------------


we weren't looking for checkpoint. We were talking about transfering save data from Emunand to Sysnand without being detected using homebrew

Minor homebrew applications like checkpoint are rarely detected by Nintendo. If you are attempting to edit the SysNAND directly and importing EmuNAND values, it will probably be much less safe than an .nro app.
I do hope you find what you are looking for :)
 
  • Like
Reactions: Blaze Uchiha
So what's the veredict?
I played a lot and I really want to buy the game to play online, but I don't want to get banned :P

Yes, merely running CFW once is said to get your NAND dirty and getting exposed to a ban. Though no one really knows what is Nintendo checking to get someone banned.

Anyway, I found this on an old post, and it makes sense, a lot of sense:
Link?

My idea was to do this.
Copy my saves with hacdiskmount from emu to clean sys.
Run the game, do something and save.
Backup those sysnand save files
Restore clean nand backup.
Copy from the backup sysnand files to the new clean nand. then going online

it sounds pretty safe doesn't it?
unless of course they do some sort of historical save information or something on the save files. otherwise, it feels like the save will be clean as it would've ben saved by a CLEAN nand.
 
Last edited by elhefegaming,
Yes, merely running CFW once is said to get your NAND dirty and getting exposed to a ban. Though no one really knows what is Nintendo checking to get someone banned.

Anyway, I found this on an old post, and it makes sense, a lot of sense:

Nintendo is checking your installed games against games you currently own in the eShop. It's how many people get banned, by having titles on your console you don't actually own along with running any cheats while playing online. It doesn't matter what kind of cheats either.
 
So what's the veredict?
I played a lot and I really want to buy the game to play online, but I don't want to get banned :P


Link?

My idea was to do this.
Copy my saves with hacdiskmount from emu to clean sys.
Run the game, do something and save.
Backup those sysnand save files
Restore clean nand backup.
Copy from the backup sysnand files to the new clean nand. then going online

it sounds pretty safe doesn't it?
unless of course they do some sort of historical save information or something on the save files. otherwise, it feels like the save will be clean as it would've ben saved by a CLEAN nand.


Did you tried it? Searching for such informations for hours.
 
So what's the veredict?
I played a lot and I really want to buy the game to play online, but I don't want to get banned :P


Link?

My idea was to do this.
Copy my saves with hacdiskmount from emu to clean sys.
Run the game, do something and save.
Backup those sysnand save files
Restore clean nand backup.
Copy from the backup sysnand files to the new clean nand. then going online

it sounds pretty safe doesn't it?
unless of course they do some sort of historical save information or something on the save files. otherwise, it feels like the save will be clean as it would've ben saved by a CLEAN nand.

This was my idea exactly. I tested it with emuNAND first and when I checked the saves after they wasn't there. I think I might have needed the game installed first.
I did try with JKSV testing in emuNAND but when I checked the USER partition of said emuNAND in NxNandManager the USERID was different.
So looked like JKSV copied the USERID incorrectly but on the switch it showed correct. Not sure what was going on.

So it looks like there is multiple ways of doing this.

  • [1] CFW (emuNAND / sysNAND) backup with Checkpoint / JKSV
    • CFW sysNAND restore with Checkpoint / JKSV
      • STOCK sysNAND play / upload / transfer on from there
  • [2] CFW (emuNAND / sysNAND) mount USER partition on PC with HacDiskMount or NxNandManager
    • Extract save data, decrypt, copy in save required, re-encrypt (sign) using hactoolnet
      • Inject newly encrypted / signed saves to USER partition with HacDiskMount or NxNandManager
I was looking at doing step 2 after launching the games first and creating a save on my STOCK firmware.

What do you think is "safer"? This is assuming that the saves are un-modified, from the same user and the same device.
 
Last edited by Shady0808,

Site & Scene News

Popular threads in this forum