There is a Homebrew app called Checkpoint that allows you to backup game save data.
Have you backed up your NAND yet? You can also backup games + their save data (and important system data) with a RAW NAND dump. This would kill 2 birds with one stone - backing up all of your games + saves, and protecting your system data in case you ever get bricked.
Risk of avoiding ban = close to 0
Ideally you want to back up your NAND in a fresh state wjth nothing installed, no game played so your eMMC is blank. Now you can play games and make saves backup with Checkpoint which will make a backup of your saves o your sd card so you can restore them later.
Ideally you want to back up your NAND in a fresh state wjth nothing installed, no game played so your eMMC is blank. Now you can play games and make saves backup with Checkpoint which will make a backup of your saves o your sd card so you can restore them later.
Yeah just create the NAND backup with Hekate, and use Checkpoint whenever you want to make a new backup of game saves in the future.
There are a couple good videos on YouTube and some really good posts here about backing up NAND. Just be sure to back up at LEAST: BOOT0, BOOT1, and eMMc SYS to have what you need to recover from a brick.
To back up your games and saves you’ll need to do a RAW dump. I believe the RAW dump includes the BOOT0, BOOT1 and eMMC SYS files.
Last edited by mranonymous,
As far as I know, there is only one way to backup save games in a way that has minimal chance of a ban. This is only for backing up, no editing. No tools exist to edit these yet as far as I am aware.
- Get TegraRCMSmashGUI. Unpack to a folder somewhere. Call it something convenient, like Tegra.
- Go here and download biskeydump, memloader, and HacDiskMount.
- Unpack biskeydump.bin, and memloader.bin. Put in the Tegra folder.
- In memloader.zip, there is a folder called sample. Unpack the contents to your SD card.
- Turn off your Switch, get jiggy, and go into RCM mode.
- Launch TegraRcmGUI. It should say "RCM OK" in the bottom left of the UI. Select "biskeydump.bin" as the payload, and click Inject Payload.
- Note down everything manually or take a shot of the QR code, then save it somewhere.
- Press the power button to turn off your Switch, get jiggy, and go into RCM mode.
- Go back to TegraRcmGUI. It should say "RCM OK" in the bottom left of the UI. Select "memloader.bin" as the payload, and click Inject Payload.
- In the resulting screen, select "ums_emmc.ini". If this option is not present, you didn't do step 4 correctly. Turn off your switch, and go do it. Continue from step 8.
- Once selected, press power once.
- Launch HacDiskMount, run as Administrator. Go to File-Open physical drive.
- You should see "Linux UMS disk 0 (21.121 GiB)" or something very similar. Select this then click OK.
- Now you should see a list of items starting with PRODINFO and ending with USER. Double click USER.
- A window called "Operations on USER" should have appeared. At the top it should say "BIS Key 3", along with two text boxes for Crypto and Tweak.
- Go to the keys you noted from biskeydump. Copy the correct keys from this to the appropriate text boxes. Click Test. If the result is green with OK! Entropy, continue. Otherwise double check your keys.
- Below the keys section there is Virtual Drive. Click install, if it hasn't been done already after previously following a different tutorial.
- Select an empty/unused drive letter. Click Read Only (for safety). Click Mount.
- Open Explorer, navigate to the newly mounted drive. If nothing appears or Windows says it needs to be formatted, abort and check your keys.
- In the mounted drive, you will see five folders (Album, Contents, save, saveMeta, temp) and one file (PRF2SAFE.RCV). Copy save and saveMeta somewhere safe, and good luck identifying which one is which.
- Click Unmount in HacDiskTool. You can now turn off your Switch, hold down Power for 13 seconds.
You can decrypt them after with one of the bis key (either SYSTEM or USER). Does a tool exist for that? Idk.
Also restoring save in aclean nand might be risky, playlog has 0 data and you still have a save...
That might be fixed by simply going into the game a certain period of time.
There might be other logs of game tho...
In fact, the switch currently can't detect cfw (not including piracy).
Last edited by mariogamer,
Not worth the money if you join only for that.
Worth the risk if you use the partition method.
SciresM said he used custom exceptions so anything that uses Atmosphere code will be detectable by Nintendo since the logs are sent to them.
No. Those are custom crash logs. and sciresM creport never actually report the crash (normal behaviour)
lemme explain myself, the crash report included with atmo saves crashes to the sd card. Normal one saves them to the nand and report them. This make it even more safe than deleting them on 5.x!
This is why nx-dreport is deprecated/was removed from sdfiles and creport added.
Last edited by mariogamer,
It was taken from this. But that's a few weeks old so I guess things may have changed since.ReSwitched said:
still Imo unsafe unless atmosphere sends fake reports sending no reports has possibly flag you for a ban in the future I'm sure Nintendo thought of that
No not crash reporr. If you don't send any that means no fatal error, which is a normal behaviour.
Interesting, but in which context did he say that? I think it's about layered fs only.
So I did an experiment last night. I attempted to transfer my Zelda BOTW save from my legit Switch (5.1.0) to my hacked one (4.1.0). Both switches had identical installs - Zelda original release physical game cart, plus current update plus DLCs (5.1.0 legit, 4.1.0 less so).
4.1.0 savegame:
save\0000000000000020 [64 Mb]
saveMeta\0000000000000020\00000001.meta [256 Kb]
5.1.0 savegame:
save\000000000000003a [64.1 Mb]
saveMeta\000000000000003a\00000001.meta [256 Kb]
5.1.0 save -> 4.1.0 FAIL, "Save game corrupted"
5.1.0 save + saveMeta -> 4.1.0 FAIL, "Save game corrupted"
I suspect there are differences in the way the two OS versions handle save data - the different sizes alone indicate this. I can't test going the other way (4.1.0 -> 5.1.0), but I suspect that might actually work.
The save data itself (000000000000003a) isn't further encrypted once copied via HacDiskMount. I can look at individual save data using a hex editor (see attached pic for Salt & Sanctuary save, which is 20.2 Mb - the highlighted "02" is the number of skill points for upgrading your character). It seems to be a virtual drive of some sort that gets mounted by the operating system as the game starts.
4.1.0 savegame:
save\0000000000000020 [64 Mb]
saveMeta\0000000000000020\00000001.meta [256 Kb]
5.1.0 savegame:
save\000000000000003a [64.1 Mb]
saveMeta\000000000000003a\00000001.meta [256 Kb]
5.1.0 save -> 4.1.0 FAIL, "Save game corrupted"
5.1.0 save + saveMeta -> 4.1.0 FAIL, "Save game corrupted"
I suspect there are differences in the way the two OS versions handle save data - the different sizes alone indicate this. I can't test going the other way (4.1.0 -> 5.1.0), but I suspect that might actually work.
The save data itself (000000000000003a) isn't further encrypted once copied via HacDiskMount. I can look at individual save data using a hex editor (see attached pic for Salt & Sanctuary save, which is 20.2 Mb - the highlighted "02" is the number of skill points for upgrading your character). It seems to be a virtual drive of some sort that gets mounted by the operating system as the game starts.
Attachments
-
-
-
-
-
@
RedColoredStars:
Never even seen a tiger crust pizza in any stores around here. Walmart, Cub, or otherwise. -
-
-
@
RedColoredStars:
Last thing I told her is how much I love her, and that Im not leaving her there forever and I promise to come back and take her back home with me.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
