Pkg Maker Tools

Return to site

Pkg Maker Tools

PS3 TrueAncestor PKG Repacker by JjKkYu 2.45 ATTACH TrueAncestor PKG Repacker by JjKkYu Unpack/Pack pkg files for PSP or PS3 with this tool for PC (Windows). The tool can also be used to.

SISContents is a tool that allows you to unpack, edit and sign Symbian 9 SIS packages (Nokia S60 3rd, 5th Edition and Sony Ericsson UIQ 3. View the PKG script that.
Rapise is a robust, next-generation test automation platform for desktop, mobile, and web applications developed by Inflectra. Using the power of open and extensible architecture, Rapise delivers the most rapid and flexible functional testing tool. Rapise comes with a built-in support for.
Hi, friends, I hope you are doing well. Today on your demand I am going to tell you about the Fake PKG Tool. This tool is really nice because this helps you to convert your disk game into PS4 PKG files. So, after reading this article you will be able to make your favorite game PKG for your PS4 console. PS4 Fake PKG Tool installation and very simple use process, you just need to follow the steps as given in the article and enjoy your favorite game. For doing this process you need to have a Jailbroken PS4 console 5.05 version or below than 5.05 firmware.
My suggestion is for you that if you already updated your console to the latest firmware version then please wait for update jailbreak. Further, you can use any PS4 model FAT, Slim, or Pro. PS4 PKG Tool for PS4 with documentation to generate fake packages that will support homebrew. Before this article, I have already published an article about how to jailbreak PS4 5.05 firmware.
Moreover, PS4 Fake PKG Tool is very useful for those who like to play their favorite game on PS4 like God of War 2018, Detroit Become Human, and so on. Please make sure your PS4 console should be jailbroken and on 5.05 or lower than this. This tool is 100% working and tested, so don't worry about the functioning of it. So let's start.
Steps to convert Disk game to PKG using PS4 Fake PKG Tool
Insert the game disk in your PS4 console which you want to convert
Run game until the full load (Main menu)
Update your game (Do not update your game via the internet)
After the update, reboots your console
Plug your FAT32 formatted USB drive in your PS4 console
Enable dumper and run your game
Wait until the dumping process finish
When dumping process finish then your console will shut down automatically
Leave your console shut down for now
Plug your USB drive in your PC
Copy CUSAXXXXX-app and CUSAXXXXX-patch both folder in your computer
Download and extract FAKE PKG Tool anywhere on your computer.
Run free-ps2-pub-gen
Target CUSAXXXXX-app folder and after finish process save.GP4 (Save .GP4 same folder)
Do same with CUSAXXXXX-patch
Close free-ps2-pub-gen and run Orbis-pub-gen
Target first result.GP4
After the finishing process, build PKG and save anywhere on your computer
Do the same with the 2nd.GP4
Copy-paste both files in your USB root and plug it in your PlayStation 4 console
Simply Enable HAN
Install game PKG, after that install patch PKG
Enjoy your game
 Some commonly asked question answers about PS4 Fake PKG Tool Q: Can I use this process to convert any game into pkg?
A: Yes, you can do the same process with any game. But make sure your game should be updated. Otherwise, it will not work for you. Besides that, some games are converted into pkg but still not working don't panic.
PS3 - Pkg_custom 1.4 | PSX-Place

Q: Can I use this process on the PS4 console which has firmware more than 5.05?
A: No, you can't. As I told you above that, for marking PS4 Fake PKG you need to have a 5.05 firmware. The console should not have the firmware version above 5.05.
Q: Is this process work for me?
A: Sure, this process is 100% tested and working. You just need to follow the article and steps as given. Further, if you forget any step or not fulfill the requirements then only you get the error.
Summary:- Lastly, I assume that you comfortably understand the PS4 Fake PKG Tool. Further, if you need any clarification then write to me. Please like and share my Facebook page and subscribe to push notification for the attest updates.
 -->Note
For UWP guidance on using this tool, see Create an app package with the MakeAppx.exe tool.
App packager (MakeAppx.exe) creates an app package from files on disk or extracts the files from an app package to disk. Starting with Windows 8.1, App packager also creates an app package bundle from app packages on disk or extracts the app packages from an app package bundle to disk. It is included in Microsoft Visual Studio and the Windows Software Development Kit (SDK) for Windows 8 or Windows Software Development Kit (SDK) for Windows 8.1. Visit Downloads for developers to get them.
The MakeAppx.exe tool is typically found at these locations:
On x86: C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
On x64 in two locations:C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
C:Program Files (x86)Windows Kits8.0binx64makeappx.exe or C:Program Files (x86)Windows Kits8.1binx64makeappx.exe
There is no ARM version of the tool.
Using App packagerNote
Relative paths are supported throughout the tool.
To create a package using a directory structurePlace the AppxManifest.xml in the root of a directory containing all of the payload files for your app. An identical directory structure is created for the app package, and will be available when the package is extracted at deployment time.
Place all files in a single directory structure, creating subdirectories as desired.
Create a valid package manifest, AppxManifest.xml, and place it in the root directory.
Run this command:
MakeAppx pack /dinput_directorypath/pfilepath.appx
To create a package using a mapping fileCreate a valid package manifest, AppxManifest.xml.
Create a mapping file. The first line contains the string [Files], and the lines that follow specify the source (disk) and destination (package) paths in quoted strings.
Run this command:
MakeAppx pack /fmapping_filepath/pfilepath.appx
To sign the package using SignToolCreate the certificate. The publisher listed in the manifest must match the publisher subject information of the signing certificate. For more info about creating a signing certificate, see How to create an app package signing certificate.
Run SignTool.exe to sign the package:
SignTool sign /a /v /fdhashAlgorithm/fcertFileNamefilepath.appx
The hashAlgorithm must match the hash algorithm used to create the blockmap when the app was packaged. With the MakeAppx packaging utility, the default Appx blockmap hash algorithm is SHA256. Run SignTool.exe specifying SHA256 as the file digest (/fd) algorithm:
SignTool sign /a /v /fd SHA256 /fcertFileNamefilepath.appx
For more info about how to sign packages, see How to sign an app package using SignTool.
To extract files from a packageRun this command:
MakeAppx unpack /pfile.appx /doutput_directory
The unpacked package has the same structure as the installed package.
To create a package bundle using a directory structureWe use the bundle command to create an app bundle at  by adding all packages from  contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Place all packages in a single directory structure, creating subdirectories as desired.
Run this command:
MakeAppx bundle /dinput_directorypath/pfilepath.appxbundle
To create a package bundle using a mapping fileWe use the bundle command to create an app bundle at  by adding all packages from a list of packages within  contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Create a 
Run this command:
MakeAppx bundle /fmapping_filepath/pfilepath.appxbundle
To extract packages from a bundleRun this command:
MakeAppx unbundle /pbundle_name.appxbundle /doutput_directory
The unpacked bundle has the same structure as the installed package bundle.
To encrypt a package with a key fileCreate a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the key ID and the second string represents the encryption key in hexadecimal form.
Run this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be encrypted into the specified encrypted package using the provided key file.
To encrypt a package with a global test keyRun this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kt
The input package will be encrypted into the specified encrypted package using the global test key.
To decrypt a package with a key fileCreate a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the base64 encoded 32-byte key ID and the second string represents the base64 encoded 32-byte encryption key.
Run this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be decrypted into the specified unencrypted package using the provided key file.
To decrypt a package with a global test keyPS3 - TrueAncestor PKG Repacker - V2.45 By Jjkkyu | PSX-PlaceRun this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kt
The input package will be decrypted into the specified unencrypted package using the global test key.
UsageThe command line argument /p is always required, with either /d, /f, or /ep. Note that /d, /f, and /ep are mutually exclusive.
MakeAppx pack [options]/p/d
MakeAppx pack [options]/p/f
MakeAppx unpack [options]/p/d
MakeAppx bundle [options]/p/d
MakeAppx bundle [options]/p/f
MakeAppx unbundle [options]/p/d
MakeAppx encrypt [options]/p/ep
MakeAppx decrypt [options]/p/ep
Command-line SyntaxHere is the command-line common usage syntax for MakeAppx.
MakeAppx [pack|unpack|bundle|unbundle|encrypt|decrypt] [/h/kf/kt/l/o/no/nv/v/pfn/?]
MakeAppx packs or unpacks the files in a package, bundles or unbundles the packages in a bundle, or encrypts or decrypts the app package or bundle in the specified input directory or mapping file. Here is the list of parameters that apply to MakeAppx pack, MakeAppx unpack, MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, or MakeAppx decrypt.
/l
Ps4 Fake Pkg Maker ToolsThis option is used for localized packages. The default validation trips on localized packages. This option disables only that specific validation, without requiring that all validation be disabled.
/o
Overwrite the output file if it exists. If you don't specify this option or the /no option, the user is asked whether they want to overwrite the file.
You can't use this option with /no.
/no
Prevents an overwrite of the output file if it exists. If you don't specify this option or the /o option, the user is asked whether they want to overwrite the file.
You can't use this option with /o.
/nv
Skip semantic validation. If you don't specify this option, the tool performs a full validation of the package.
/v
Enable verbose logging output to the console.
/?
Display help text.

MakeAppx pack , MakeAppx unpack , MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, and MakeAppx decrypt are mutually exclusive commands. Here are the command-line parameters that apply specifically to each command:
MakeAppx pack [h]
Creates a package.
/halgorithm
Flat_z's Method To Handle PS4 Fake PKGs & SELF / FSELF ..

Specifies the hash algorithm to use when creating the block map. Here are valid values for algorithm:
SHA256 (default)SHA384SHA512You can't use this option with the unpack command.
MakeAppx unpack [pfn]
Extracts all files in the specified package to the specified output directory. The output has the same directory structure as the package.

SISContents is a tool that allows you to unpack, edit and sign Symbian 9 SIS packages (Nokia S60 3rd, 5th Edition and Sony Ericsson UIQ 3. View the PKG script that.
Rapise is a robust, next-generation test automation platform for desktop, mobile, and web applications developed by Inflectra. Using the power of open and extensible architecture, Rapise delivers the most rapid and flexible functional testing tool. Rapise comes with a built-in support for.
Hi, friends, I hope you are doing well. Today on your demand I am going to tell you about the Fake PKG Tool. This tool is really nice because this helps you to convert your disk game into PS4 PKG files. So, after reading this article you will be able to make your favorite game PKG for your PS4 console. PS4 Fake PKG Tool installation and very simple use process, you just need to follow the steps as given in the article and enjoy your favorite game. For doing this process you need to have a Jailbroken PS4 console 5.05 version or below than 5.05 firmware.
My suggestion is for you that if you already updated your console to the latest firmware version then please wait for update jailbreak. Further, you can use any PS4 model FAT, Slim, or Pro. PS4 PKG Tool for PS4 with documentation to generate fake packages that will support homebrew. Before this article, I have already published an article about how to jailbreak PS4 5.05 firmware.
Moreover, PS4 Fake PKG Tool is very useful for those who like to play their favorite game on PS4 like God of War 2018, Detroit Become Human, and so on. Please make sure your PS4 console should be jailbroken and on 5.05 or lower than this. This tool is 100% working and tested, so don't worry about the functioning of it. So let's start.
Steps to convert Disk game to PKG using PS4 Fake PKG Tool
Insert the game disk in your PS4 console which you want to convert
Run game until the full load (Main menu)
Update your game (Do not update your game via the internet)
After the update, reboots your console
Plug your FAT32 formatted USB drive in your PS4 console
Enable dumper and run your game
Wait until the dumping process finish
When dumping process finish then your console will shut down automatically
Leave your console shut down for now
Plug your USB drive in your PC
Copy CUSAXXXXX-app and CUSAXXXXX-patch both folder in your computer
Download and extract FAKE PKG Tool anywhere on your computer.
Run free-ps2-pub-gen
Target CUSAXXXXX-app folder and after finish process save.GP4 (Save .GP4 same folder)
Do same with CUSAXXXXX-patch
Close free-ps2-pub-gen and run Orbis-pub-gen
Target first result.GP4
After the finishing process, build PKG and save anywhere on your computer
Do the same with the 2nd.GP4
Copy-paste both files in your USB root and plug it in your PlayStation 4 console
Simply Enable HAN
Install game PKG, after that install patch PKG
Enjoy your game
 Some commonly asked question answers about PS4 Fake PKG Tool Q: Can I use this process to convert any game into pkg?
A: Yes, you can do the same process with any game. But make sure your game should be updated. Otherwise, it will not work for you. Besides that, some games are converted into pkg but still not working don't panic.
PS3 - Pkg_custom 1.4 | PSX-PlaceQ: Can I use this process on the PS4 console which has firmware more than 5.05?
A: No, you can't. As I told you above that, for marking PS4 Fake PKG you need to have a 5.05 firmware. The console should not have the firmware version above 5.05.
Q: Is this process work for me?
A: Sure, this process is 100% tested and working. You just need to follow the article and steps as given. Further, if you forget any step or not fulfill the requirements then only you get the error.
Summary:- Lastly, I assume that you comfortably understand the PS4 Fake PKG Tool. Further, if you need any clarification then write to me. Please like and share my Facebook page and subscribe to push notification for the attest updates.
 -->Note
For UWP guidance on using this tool, see Create an app package with the MakeAppx.exe tool.
App packager (MakeAppx.exe) creates an app package from files on disk or extracts the files from an app package to disk. Starting with Windows 8.1, App packager also creates an app package bundle from app packages on disk or extracts the app packages from an app package bundle to disk. It is included in Microsoft Visual Studio and the Windows Software Development Kit (SDK) for Windows 8 or Windows Software Development Kit (SDK) for Windows 8.1. Visit Downloads for developers to get them.
The MakeAppx.exe tool is typically found at these locations:
On x86: C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
On x64 in two locations:C:Program Files (x86)Windows Kits8.0binx86makeappx.exe or C:Program Files (x86)Windows Kits8.1binx86makeappx.exe
C:Program Files (x86)Windows Kits8.0binx64makeappx.exe or C:Program Files (x86)Windows Kits8.1binx64makeappx.exe
There is no ARM version of the tool.
Using App packagerNote
Relative paths are supported throughout the tool.
To create a package using a directory structurePlace the AppxManifest.xml in the root of a directory containing all of the payload files for your app. An identical directory structure is created for the app package, and will be available when the package is extracted at deployment time.
Place all files in a single directory structure, creating subdirectories as desired.
Create a valid package manifest, AppxManifest.xml, and place it in the root directory.
Run this command:
MakeAppx pack /dinput_directorypath/pfilepath.appx
To create a package using a mapping fileCreate a valid package manifest, AppxManifest.xml.
Create a mapping file. The first line contains the string [Files], and the lines that follow specify the source (disk) and destination (package) paths in quoted strings.
Run this command:
MakeAppx pack /fmapping_filepath/pfilepath.appx
To sign the package using SignToolCreate the certificate. The publisher listed in the manifest must match the publisher subject information of the signing certificate. For more info about creating a signing certificate, see How to create an app package signing certificate.
Run SignTool.exe to sign the package:
SignTool sign /a /v /fdhashAlgorithm/fcertFileNamefilepath.appx
The hashAlgorithm must match the hash algorithm used to create the blockmap when the app was packaged. With the MakeAppx packaging utility, the default Appx blockmap hash algorithm is SHA256. Run SignTool.exe specifying SHA256 as the file digest (/fd) algorithm:
SignTool sign /a /v /fd SHA256 /fcertFileNamefilepath.appx
For more info about how to sign packages, see How to sign an app package using SignTool.
To extract files from a packageRun this command:
MakeAppx unpack /pfile.appx /doutput_directory
The unpacked package has the same structure as the installed package.
To create a package bundle using a directory structureWe use the bundle command to create an app bundle at  by adding all packages from  contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Place all packages in a single directory structure, creating subdirectories as desired.
Run this command:
MakeAppx bundle /dinput_directorypath/pfilepath.appxbundle
To create a package bundle using a mapping fileWe use the bundle command to create an app bundle at  by adding all packages from a list of packages within  contains a bundle manifest, AppxBundleManifest.xml, it is ignored.
Create a 
Run this command:
MakeAppx bundle /fmapping_filepath/pfilepath.appxbundle
To extract packages from a bundleRun this command:
MakeAppx unbundle /pbundle_name.appxbundle /doutput_directory
The unpacked bundle has the same structure as the installed package bundle.
To encrypt a package with a key fileCreate a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the key ID and the second string represents the encryption key in hexadecimal form.
Run this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be encrypted into the specified encrypted package using the provided key file.
To encrypt a package with a global test keyRun this command:
MakeAppx.exe encrypt /ppackage_name.appx /epencrypted_package_name.eappx /kt
The input package will be encrypted into the specified encrypted package using the global test key.
To decrypt a package with a key fileCreate a key file. Key files must begin with a line containing the string '[Keys]' followed by lines describing the keys to encrypt the package with. Each key is described by a pair of strings in quotation marks, separated by spaces or tabs. The first string represents the base64 encoded 32-byte key ID and the second string represents the base64 encoded 32-byte encryption key.
Run this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kfkeyfile_name.txt
The input package will be decrypted into the specified unencrypted package using the provided key file.
To decrypt a package with a global test keyPS3 - TrueAncestor PKG Repacker - V2.45 By Jjkkyu | PSX-PlaceRun this command:
MakeAppx.exe decrypt /ppackage_name.appx /epunencrypted_package_name.eappx /kt
The input package will be decrypted into the specified unencrypted package using the global test key.
UsageThe command line argument /p is always required, with either /d, /f, or /ep. Note that /d, /f, and /ep are mutually exclusive.
MakeAppx pack [options]/p/d
MakeAppx pack [options]/p/f
MakeAppx unpack [options]/p/d
MakeAppx bundle [options]/p/d
MakeAppx bundle [options]/p/f
MakeAppx unbundle [options]/p/d
MakeAppx encrypt [options]/p/ep
MakeAppx decrypt [options]/p/ep
Command-line SyntaxHere is the command-line common usage syntax for MakeAppx.
MakeAppx [pack|unpack|bundle|unbundle|encrypt|decrypt] [/h/kf/kt/l/o/no/nv/v/pfn/?]
MakeAppx packs or unpacks the files in a package, bundles or unbundles the packages in a bundle, or encrypts or decrypts the app package or bundle in the specified input directory or mapping file. Here is the list of parameters that apply to MakeAppx pack, MakeAppx unpack, MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, or MakeAppx decrypt.
/l
Ps4 Fake Pkg Maker ToolsThis option is used for localized packages. The default validation trips on localized packages. This option disables only that specific validation, without requiring that all validation be disabled.
/o
Overwrite the output file if it exists. If you don't specify this option or the /no option, the user is asked whether they want to overwrite the file.
You can't use this option with /no.
/no
Prevents an overwrite of the output file if it exists. If you don't specify this option or the /o option, the user is asked whether they want to overwrite the file.
You can't use this option with /o.
/nv
Skip semantic validation. If you don't specify this option, the tool performs a full validation of the package.
/v
Enable verbose logging output to the console.
/?
Display help text.
MakeAppx pack , MakeAppx unpack , MakeAppx bundle, MakeAppx unbundle, MakeAppx encrypt, and MakeAppx decrypt are mutually exclusive commands. Here are the command-line parameters that apply specifically to each command:
MakeAppx pack [h]
Creates a package.
/halgorithm
Flat_z's Method To Handle PS4 Fake PKGs & SELF / FSELF ..Specifies the hash algorithm to use when creating the block map. Here are valid values for algorithm:
SHA256 (default)SHA384SHA512You can't use this option with the unpack command.
MakeAppx unpack [pfn]
Extracts all files in the specified package to the specified output directory. The output has the same directory structure as the package.
/pfn
Specifies a directory named with the package full name. This directory is created under the provided output location. You can't use this option with the pack command.
MakeAppx unbundle [pfn]
Unpacks all packages to a subdirectory under the specified output path, named after the bundle full name. The output has the same directory structure as the installed package bundle.
Free PS2 Pub Gen / Fake PKG Tools: PS2 Fake PKG Generator For PS4/pfn
Specifies a directory named with the package bundle full name. This directory is created under the provided output location. You can't use this option with the bundle command.
MakeAppx encrypt [kf, kt]
Creates an encrypted app package from the specified input app package at the specified output package.
/kf
Encrypts the package or bundle using the key from the specified key file. You can't use this option with kt.
/kt
Encrypts the package or bundle using the global test key. You can't use this option with kf.
MakeAppx decrypt [kf, kt]
Creates an unencrypted app package from the specified input app package at the specified output package.
/kf
Decrypts the package or bundle using the key from the specified key file. You can't use this option with kt.
/kt
Decrypts the package or bundle using the global test key. You can't use this option with kf.
Semantic validation performed by MakeAppxMakeAppx performs limited semantic validation that is designed to catch the most common deployment errors and help ensure that the app package is valid.
This validation ensures that:
Ps3 Pkg Maker ToolsAll files referenced in the package manifest are included in the app package.
An application does not have two identical keys.
An application does not register for a forbidden protocol from this list: SMB , FILE, MS-WWA-WEB, MS-WWA.
Ps3 Pkg CreatorThis semantic validation is not complete, and packages built by MakeAppx are not guaranteed to be installable.