Anti Savegame Restore - Revision history

TimmSkiller: Changed redirect target from Filesystem Services#Anti Savegame Restore to Filesystem services#Anti Savegame Restore

2025-07-01T13:21:30Z

Changed redirect target from Filesystem Services#Anti Savegame Restore to Filesystem services#Anti Savegame Restore

← Older revision		Revision as of 17:21, 1 July 2025
Line 1:		Line 1:
	#REDIRECT [[~~Filesystem_Services~~#Anti_Savegame_Restore]]		#REDIRECT [[Filesystem_services#Anti_Savegame_Restore]]

TimmSkiller: Redirected page to Filesystem Services#Anti Savegame Restore

2025-07-01T13:21:22Z

Redirected page to Filesystem Services#Anti Savegame Restore

← Older revision		Revision as of 17:21, 1 July 2025
Line 1:		Line 1:
	~~=Summary=~~		#REDIRECT [[Filesystem_Services#Anti_Savegame_Restore]]
	Anti Savegame Restore (internally referred to as ''Save Data Rollback Prevention'') is a feature originally implemented in [[Filesystem_services\|FS]] module with [[4.0.0-7]], which prevents the user from restoring previous versions of a savegame image. This feature is not used for gamecard games. When an old version of the save is detected, the application will display an error regarding old savegame version, then delete+recreate the save(similar to when the savegame is corrupted).

	~~=Implementation=~~
	When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services\|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in the FS module [[System_SaveData]].

	Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.

	~~=Remove the secure value=~~
	~~It is possible to remove the secure value easily by using [[FS:ControlSecureSave\|ControlSecureSave]], from the [[Filesystem_services~~#~~Filesystem_service_.22fs:USER.22\|fs:USER]] service, with the~~ [[~~FS:ControlSecureSave~~#~~Action\|SECURESAVE_ACTION_DELETE~~]] ~~action.~~

	~~=Applications using this feature=~~
	* Animal Crossing: New Leaf
	* Pokemon X & Y
	* Pokemon Omega Ruby & Alpha Sapphire
	* Pokemon Omega Ruby & Alpha Sapphire Demo
	* Pokemon Shuffle
	* Super Smash Bros
	* Pokemon Red,Blue and Yellow (GB(C) VC)
	* Rusty's Real Deal Baseball
	* Megami Meguri

Cooolgamer: /* Applications using this feature */

2022-02-19T18:58:08Z

Applications using this feature

← Older revision		Revision as of 21:58, 19 February 2022
Line 18:		Line 18:
	* Super Smash Bros		* Super Smash Bros
	* Pokemon Red,Blue and Yellow (GB(C) VC)		* Pokemon Red,Blue and Yellow (GB(C) VC)
			* Rusty's Real Deal Baseball
			* Megami Meguri

Ground: /* Applications using this feature */

2016-08-23T00:03:07Z

Applications using this feature

← Older revision		Revision as of 04:03, 23 August 2016
Line 17:		Line 17:
	* Pokemon Shuffle		* Pokemon Shuffle
	* Super Smash Bros		* Super Smash Bros
			* Pokemon Red,Blue and Yellow (GB(C) VC)

Gocario at 09:21, 1 February 2016

2016-02-01T08:21:13Z

← Older revision		Revision as of 11:21, 1 February 2016
Line 6:		Line 6:

	Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.		Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.

			=Remove the secure value=
			It is possible to remove the secure value easily by using [[FS:ControlSecureSave\|ControlSecureSave]], from the [[Filesystem_services#Filesystem_service_.22fs:USER.22\|fs:USER]] service, with the [[FS:ControlSecureSave#Action\|SECURESAVE_ACTION_DELETE]] action.

	=Applications using this feature=		=Applications using this feature=

Daesoph: /* Applications using this feature */

2015-10-04T17:22:43Z

Applications using this feature

← Older revision		Revision as of 21:22, 4 October 2015
Line 10:		Line 10:
	* Animal Crossing: New Leaf		* Animal Crossing: New Leaf
	* Pokemon X & Y		* Pokemon X & Y
	* Pokemon Omega ~~ruby~~ & Alpha Sapphire		* Pokemon Omega Ruby & Alpha Sapphire
	* Pokemon ~~ORAS~~ Demo		* Pokemon Omega Ruby & Alpha Sapphire Demo
	* Pokemon Shuffle		* Pokemon Shuffle
	* Super Smash Bros		* Super Smash Bros

MassExplosion213: Fixed typo. Sorry for double edit.

2015-10-04T17:20:28Z

Fixed typo. Sorry for double edit.

← Older revision		Revision as of 21:20, 4 October 2015
Line 10:		Line 10:
	* Animal Crossing: New Leaf		* Animal Crossing: New Leaf
	* Pokemon X & Y		* Pokemon X & Y
	* Pokemon Omega ruby & Alpha ~~Saphire~~		* Pokemon Omega ruby & Alpha Sapphire
	* Pokemon ORAS Demo		* Pokemon ORAS Demo
	* Pokemon Shuffle		* Pokemon Shuffle
	* Super Smash Bros		* Super Smash Bros

MassExplosion213: ORAS Demo is e-shop only.

2015-10-04T17:20:01Z

ORAS Demo is e-shop only.

← Older revision		Revision as of 21:20, 4 October 2015
Line 14:		Line 14:
	* Pokemon Shuffle		* Pokemon Shuffle
	* Super Smash Bros		* Super Smash Bros

	~~It's currently unknown whether there's any eShop-only titles that use this.~~

Hartie95: Added some more games using the secure Value

2015-10-01T06:09:42Z

Added some more games using the secure Value

← Older revision		Revision as of 10:09, 1 October 2015
Line 10:		Line 10:
	* Animal Crossing: New Leaf		* Animal Crossing: New Leaf
	* Pokemon X & Y		* Pokemon X & Y
			* Pokemon Omega ruby & Alpha Saphire
			* Pokemon ORAS Demo
			* Pokemon Shuffle
	* Super Smash Bros		* Super Smash Bros

	It's currently unknown whether there's any eShop-only titles that use this.		It's currently unknown whether there's any eShop-only titles that use this.

Yellows8: /* Implementation */

2014-09-14T18:33:55Z

Implementation

← Older revision		Revision as of 22:33, 14 September 2014
Line 3:		Line 3:

	=Implementation=		=Implementation=
	When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services\|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in ~~a NAND savegame~~.		When creating the SD savedata, the application generates a random u64 value, then stores it in an arbitary savefile in the savegame FS. The application then uses the anti-savegame-restore [[Filesystem_services\|FS]] commands to verify the stored u64(with the u64 loaded by FS module), and to update the u64 used by FS module. The u64 used by FS module is stored in the FS module [[System_SaveData]].

	Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.		Each time the application writes to the savegame, the u64 value stored in the savefile should be updated(and the command for updating the NAND u64 value should be used as well). Usually applications update this value by incrementing it, however generating a new random-number or other methods of updating it can be used as well.