You should not specify too high of a number here, as running multiple threads on a single CPU will result in diminishing returns. On OSX/Windows, it is up to the scheduler to make such decisions. On Linux, each thread tries to run on a separate processor. The -n option specifies the number of threads to run. For example, if I wish to decrypt PS Vita/PGAME/xxxxxxxxxxxxxxxx/NPJH00053/game/game.psvimg then my AID is xxxxxxxxxxxxxxxx. The AID is the 16 hex characters in your CMA backup path. The partials.bin file does not contain any console-unique information but is derived from the provided PSN AID. You can generate partials for other people as well if you know their AID. You should generate a valid partials.bin file using the provided "dump_partials" Vita homebrew that runs on HENkaku enabled consoles. This is a brute-force backup key find tool. Trying to add a backup set with a custom path may result in failure.
Note that CMA does check the paths of the backup sets.
The means a separate directory for each backup set (there may only be one set, in which your input directory will contain one subdirectory) each with a VITA_PATH.TXT file specifying the Vita path and optionally a VITA_DATA.BIN file if the set is a file. The pack input directory should follow the same format as the output of psvimg-extract. For example, if you are repacking license.psvimg, you should specify -n license. psvimg extension) when repacking because CMA does check for a valid name. You should use the same name (the file name without the. psvmd, you should use the -n option and specify the name of the backup. psvmd, you may pass it in with -m and the tool will reuse as many fields as possible (exception: size fields). This repacks extracted files and creates the associated. Extracting this file is not required for repacking and is provided for reverse engineering/debugging purposes.
This contains information such as the firmware version of the system that created the backup and the unique PSID of the system. The contents of which are defined in psvimg.h. In that case, the file VITA_DATA.BIN is created to host the contents of the file. A set can be only a single file (for example ux0:iconlayout.ini). A special file VITA_PATH.TXT is created for each set to remember what the original path was before extraction (this is used for repacking). Each backup set contains zero or more files and directories. The extracted output includes a directory for each backup set (e.g: ur0:appmeta, ux0:iconlayout.ini, and ur0:tmp/registry are three separate sets).
0 kommentar(er)
