- #Powersaves 3ds install
- #Powersaves 3ds windows
Rename your backup save to a different filename. Copy the saveimage you selected from the saveimages_powersaves directory in the release-archive as described above, to this Powersaves3DS directory. #Powersaves 3ds windows
In Windows Explorer, goto "C:\Users\YourUsername\Powersaves3DS". Backup your gamecard savedata with Powersaves, even if you don't want to keep that savedata. Instructions for using with Datel Powersaves: The saveimage files under those region directories have the same filename as the payload contained in the savedata, you can use the filename from this to determine which saveimage filename to use: īefore using the "saveimages" directory, you should verify that your savedata backup filesize matches the filesize from the files from that directory. These directories then contain sub-directories for each game region. If you don't know what the cardids for your gamecard are(these are included with what are commonly called "gamecard-unique headers"), just try either directory until one of them works without the game triggering a savedata-corruption error at boot. Those directories contain two sub-directories, each for a different cardid set. The "saveimages" directory is for raw 0x20000-byte saveimages, while "saveimages_powersaves" is for Datel Powersaves. Raw save-images which can be written to the gamecard savedata flash are contained in the oot3dhax release-archive. #Powersaves 3ds install
Hence, you have to use sploit_installer to install oot3dhax for those regions(but currently there's no hosted *hax payloads available for the CHNTWN regions, as of July 29, 2016).
The release-archive saveimages doesn't include KOR and CHNTWN because newer save crypto is used with those regions' gamecard. The recommended way to install oot3dhax is with either sploit_installer( ), which is included with the homebrew starter-kit( ), or by writing save-images with a gamecard save dongle for example. Note that any EXECHAX type using arm9hax will fail to build the KOR + CHNTWN savefiles, you can ignore this if you aren't using the KOR or CHNTWN savefiles. The arm9-code loads a payload from SD card, see source.
3 for arm9hax with AM(fixed with v5.0). 1 for arm11code-loading via reading the savefile with fsuser directly to. The built romfs data for sploit_installer is located at "finaloutput_romfs/". The built savefiles should be used with sploit_installer, but other savefile-writing tools could be used too. Without moving Link, press A for triggering dialog handling.ġ1.0.0.33 is supported with the June 26, 2016, oot3dhax release builds. This savegame haxx is the same one referred to here: įor details on the vuln/etc, see source and here: Haxx usage The Nintendo Selects versions of this game are supported. KOR and CHNTWN support is currently broken somehow. Since the gamecard(there's only one "version" of the main CXI used for the gamecard) and eShop versions of the game are basically identical, the exploit can be used with both(if one can get the exploit savedata written to the savedata used by the target game version of course). The following regions are supported: JPN, USA, EUR, KOR, and CHNTWN(CHN and TWN have the exact same title). Hence the datetime displayed for the save-slot, this haxx has existed since October 2012. This is a 3DS savedata exploit for "The Legend of Zelda: Ocarina of Time 3D".
0 kommentar(er)
