ROM Hack How can I move saves from EmuNAND to SysNAND?

ReclaimerShawn

Well-Known Member
OP
Member
Joined
Dec 17, 2018
Messages
297
Trophies
0
XP
1,287
Country
United States
So, I'm making an EmuNAND in order to all of my modding. I plan on using EmuNAND for ROM Hacks and Save Editing. I'll be formatting my SysNAND and updating it to 6.2 (my EmuNAND is on 6.2). What I'd like to do is savemod on EmuNAND offline, transfer it to use it on my OFW SysNAND, and then play online. I'm doing this as an added security in hopes I don't have my NAND banned, but I understand there's a risk regardless. Also, my SD Card is 256GB exFAT, just to put that out there. I'm also using SX Pro + SX OS.
 
Last edited by ReclaimerShawn,

username23bob

Well-Known Member
Member
Joined
Mar 15, 2009
Messages
156
Trophies
0
XP
743
Country
United States
Don't make an EmuNAND or don't save mod on SysNAND? I've went online with CFW once or twice without stealth on now and things have played out fine. Just keeping myself offline is a ban in and of itself anyways.

i meant save modding on ofw, but if you went online in cfw without stealth mode (or even the dns yo block nintendo), you’re probably already flagged man.
 

username23bob

Well-Known Member
Member
Joined
Mar 15, 2009
Messages
156
Trophies
0
XP
743
Country
United States
Assuming I'm not flagged, how would I savemod on OFW using EmuNAND CFW?

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.
 

ReclaimerShawn

Well-Known Member
OP
Member
Joined
Dec 17, 2018
Messages
297
Trophies
0
XP
1,287
Country
United States
Alright, thank you for the save transfer tutorial. That'll really help me. I have a NAND Backup from OFW that had 5.1.0 on it. Considering I updated through System Settings, I've burned fuses. If I attempted to run SysNAND on 5.1.0, my console wouldn't boot. After finishing the process of creating an EmuNAND, my EmuNAND and SysNAND are currently the same and both are on 6.2. How would I format my SysNAND so it wasn't hacked? Would I just be able to do it through Initialize Console, or would I need something else? Thanks for being such a help once again. I'm on an SX Pro with SX OS 2.5.

EDIT: My backup was thankfully 6.2.0. I just loaded that via NAND Restore and now I have EmuNAND set up.
 
Last edited by ReclaimerShawn,

ReclaimerShawn

Well-Known Member
OP
Member
Joined
Dec 17, 2018
Messages
297
Trophies
0
XP
1,287
Country
United States
found this on reddit.. literally from this site
Sounds definitely doable after reading this, however it may require more work than you may have previously thought.”

I wanted to comment back to you to say that I got the saves on my SysNAND. I got a few homescreen errors at first and a game launch error, but after getting the hang of it, I got the saves fully functional and working on my SysNAND from my EmuNAND. Thanks for the help! Here's to (however long it is) online play!
 

sergux

Well-Known Member
Member
Joined
Jul 14, 2018
Messages
126
Trophies
0
Age
102
XP
1,072
Country
Afghanistan
is possible to do a backup of splatoon 2 save game from the original firmware without risk of ban?
 

ReclaimerShawn

Well-Known Member
OP
Member
Joined
Dec 17, 2018
Messages
297
Trophies
0
XP
1,287
Country
United States
is possible to do a backup of splatoon 2 save game from the original firmware without risk of ban?
If you're just talking about doing a NAND Dump of OFW and then ripping the save via HacDiskTool, then I highly doubt you'd get banned. Only thing I'd see you getting banned for is going into Hekate/RCM Payload once, but I don't know if they'd ban you for that or not (I doubt it). If you're talking about injecting modded saves into OFW through HacDiskTool, that's a different story. There's a chance of you getting banned there, but I've done that online and so far am fine. However, I could get banned at any time. Wouldn't recommend it unless you're willing to take that risk.
 
  • Like
Reactions: sergux

sergux

Well-Known Member
Member
Joined
Jul 14, 2018
Messages
126
Trophies
0
Age
102
XP
1,072
Country
Afghanistan
If you're just talking about doing a NAND Dump of OFW and then ripping the save via HacDiskTool, then I highly doubt you'd get banned. Only thing I'd see you getting banned for is going into Hekate/RCM Payload once, but I don't know if they'd ban you for that or not (I doubt it). If you're talking about injecting modded saves into OFW through HacDiskTool, that's a different story. There's a chance of you getting banned there, but I've done that online and so far am fine. However, I could get banned at any time. Wouldn't recommend it unless you're willing to take that risk.
i just want to keep my save safe if i break or lose my console. I hate the decision of nintendo about this game, i want cloud for this game :(
 

Elliander

Well-Known Member
Member
Joined
Sep 16, 2011
Messages
634
Trophies
1
Location
Illinois
Website
elliander.etherealspheres.com
XP
1,449
Country
United States
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.

That is a very interesting approach. I wonder: Is it possible to inject saves save to a sysNAND directly from an emuNAND for the same console with hacdiskmount? If so, then I wouldn't have to risk my online Switch at all. My offline Switch never had CFW on the sysNAND and I even went so far as to backup the sysNAND before creating emuNAND and then restored the sysNAND after just in case. What I am thinking is that if I can transfer from the emuNAND to the sysNAND from and to the same Switch directly, then the sysNAND should be clean of any CFW and then I could do a save transfer from one Switch to another. That way, if the console that did this is banned, it would be the one I keep offline anyway rather than the one I play online.

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

i just want to keep my save safe if i break or lose my console. I hate the decision of nintendo about this game, i want cloud for this game :(

In that case, it why not do what I did:

1.) Backup sysNAND
2.) Use SXPRO Dongle to create an emuNAND from the existing sysNAND onto the SD card
3.) Restore sysNAND from backup created (just in case any evidence is left on the sysNAND)

Saves that were on sysNAND when the emuNAND was created should be on the emuNAND. You can then run checkpoint without ever having any CFW or Homebrew installed onto sysNAND.
 

crimsonnight

Well-Known Member
Member
Joined
Jan 9, 2008
Messages
337
Trophies
1
XP
742
Country
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.

This seems a bit convoluted though no? Could I not just backup my sysnand and emunand, then copy the relevant saves over from the sysnand to the emunand via hacdiskmount and then flash the updated sysnand back to the console?
 

crimsonnight

Well-Known Member
Member
Joined
Jan 9, 2008
Messages
337
Trophies
1
XP
742
Country
This seems a bit convoluted though no? Could I not just backup my sysnand and emunand, then copy the relevant saves over from the sysnand to the emunand via hacdiskmount and then flash the updated sysnand back to the console?

Has anyone tried anything like this? If so, is there a guide anywhere? :)
 

Elliander

Well-Known Member
Member
Joined
Sep 16, 2011
Messages
634
Trophies
1
Location
Illinois
Website
elliander.etherealspheres.com
XP
1,449
Country
United States
Has anyone tried anything like this? If so, is there a guide anywhere? :)

I imagine it could work like this:

1.) Delete WiFi hotspot information, go into airplane mode
1b.) If you use an ethernet adapter, remove Switch from dock to be safe.
3.) backup sysNAND
4.) Use the SX Pro Dongle to boot sysNAND in CFW
5.) Using checkpoint on the microSD card, export the saves
6.) Power off Switch, then restore the sysNAND from the backup made in step 3
7.) Boot into your emuNAND and use checkpoint to restore the saves

If you do this, you shouldn't have to create a new emuNAND entirely, and you will be able to use checkpoint, but if you go online at all between backing up and restoring the sysNAND you absolutely will banned, so don't forget to make the sysNAND backup!

I wish they made it easy to export DLC and updates the same way. It would make a few things quite a bit easier.
 

crimsonnight

Well-Known Member
Member
Joined
Jan 9, 2008
Messages
337
Trophies
1
XP
742
Country
You cannot mount EmuNAND via hacdiskmount.
I imagine it could work like this:

1.) Delete WiFi hotspot information, go into airplane mode
1b.) If you use an ethernet adapter, remove Switch from dock to be safe.
3.) backup sysNAND
4.) Use the SX Pro Dongle to boot sysNAND in CFW
5.) Using checkpoint on the microSD card, export the saves
6.) Power off Switch, then restore the sysNAND from the backup made in step 3
7.) Boot into your emuNAND and use checkpoint to restore the saves

If you do this, you shouldn't have to create a new emuNAND entirely, and you will be able to use checkpoint, but if you go online at all between backing up and restoring the sysNAND you absolutely will banned, so don't forget to make the sysNAND backup!

I wish they made it easy to export DLC and updates the same way. It would make a few things quite a bit easier.

Cheers but that's transferring saves from sysNAND to emuNAND when I'm asking about the other way around lol. It seems a bit convoluted, but I guess the steps outlined by username23bob is the way to go. My only other question then is as I don't want to go through the process again, should I transfer all my saves or will that raise a flag? Would only transferring a few be safer?
 

Elliander

Well-Known Member
Member
Joined
Sep 16, 2011
Messages
634
Trophies
1
Location
Illinois
Website
elliander.etherealspheres.com
XP
1,449
Country
United States
ahh, right. Those steps are quite a bit much though which is why I probably won't be doing that myself. It seems to me that there should be a way for a homebrew within an emuNAND to write to the sysNAND directly and inject saves that way. Why should we have to overwrite the entire NAND, when a year old version of SXOS could write itself inside the sysNAND without being detected by Nintendo at all? Obviously though, even checkpoint needs a save file to actually exist before it can overwrite it, but still.

If that were possible, these would be the steps:

1.) Make sure the game has been played at least once and saved on sysNAND.
2.) Go into emuNAND.
3.) Use checkpoint to export your saves.
4.) Open the currently non-existent app which would solve all our problems
5.) See the list of games that have been played on sysNAND. select one, and click to inject from either checkpoint file or emuNAND save.
6.) Done.

As long as the saved game doesn't depend on DLC you didn't pay for, and wasn't created before the release date of the game, and doesn't have any mods for things that you shouldn't be able to get, it would be undetectable by Nintendo and allow you to safely inject any save you want whenever you want, and I see no reason why this magical homebrew can't exist.

Of course, as already mentioned, Nintendo could potentially counter this by keeping a log file of the date and time that the Switch was turned off and turned on and compare that with when the file was last edited, but this possibility would easily be circumvented by reading the date and time of the legitimate save within the sysNAND before overwriting, and then after overwriting to change the date and time of the new save to match the old one.

Similarly, I see no reason why SXOS can't import saves, updates, and DLC directly from the sysNAND at any time.
 

crimsonnight

Well-Known Member
Member
Joined
Jan 9, 2008
Messages
337
Trophies
1
XP
742
Country
ahh, right. Those steps are quite a bit much though which is why I probably won't be doing that myself. It seems to me that there should be a way for a homebrew within an emuNAND to write to the sysNAND directly and inject saves that way. Why should we have to overwrite the entire NAND, when a year old version of SXOS could write itself inside the sysNAND without being detected by Nintendo at all? Obviously though, even checkpoint needs a save file to actually exist before it can overwrite it, but still.

If that were possible, these would be the steps:

1.) Make sure the game has been played at least once and saved on sysNAND.
2.) Go into emuNAND.
3.) Use checkpoint to export your saves.
4.) Open the currently non-existent app which would solve all our problems
5.) See the list of games that have been played on sysNAND. select one, and click to inject from either checkpoint file or emuNAND save.
6.) Done.

As long as the saved game doesn't depend on DLC you didn't pay for, and wasn't created before the release date of the game, and doesn't have any mods for things that you shouldn't be able to get, it would be undetectable by Nintendo and allow you to safely inject any save you want whenever you want, and I see no reason why this magical homebrew can't exist.

Of course, as already mentioned, Nintendo could potentially counter this by keeping a log file of the date and time that the Switch was turned off and turned on and compare that with when the file was last edited, but this possibility would easily be circumvented by reading the date and time of the legitimate save within the sysNAND before overwriting, and then after overwriting to change the date and time of the new save to match the old one.

Similarly, I see no reason why SXOS can't import saves, updates, and DLC directly from the sysNAND at any time.

Fair, although that being said, if I boot into SX OS on the sysNAND (purely to restore saves with checkpoint) and then immediately shut down the system, would that be detected/flagged? :unsure:
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: "Now I know why he took his own life"