Download Apollo Save Tool v2.4.0
Download the official Apollo Save Tool v2.4.0 builds for PS4, PS3 and PS Vita — plus the separate PSP and PS2 editions — from the developer bucanero’s GitHub releases. Every package below lists its official size and SHA-256 checksum so you can verify your file before installing it.
More Platforms: PSP & PS2 Editions
Apollo also ships as a native homebrew for the PlayStation Portable and the PlayStation 2. Both are official builds from the same developer.
🎮 PlayStation Portable — v2.3.2
File: apollo-psp.zip · 7,362,152 bytes · Released May 12, 2026
Install to ms0:/PSP/GAME/APOLLO on a PSP running custom firmware.
SHA-256: 3ed0ccf9b5eb2d5b10af014630d6ff57070f63d5e8d6a725b3a5619da5e71d41
🕹️ PlayStation 2 — v1.0.2
File: apollo-ps2.zip (contains APOLLO.ELF) · 1,532,552 bytes · Released December 24, 2024
Run the ELF from a homebrew launcher (e.g. Free McBoot). No hash is published by the developer for this build.
Console Deployment & Installation Manual
After validating the SHA-256 hashes of your downloaded asset binaries, follow the platform-specific workflows below to properly initialize Apollo Save Tool inside your system shell environment.
Package Installer Method
- Format an external USB storage device or external hard drive to exFAT or FAT32 file-system standards.
- Copy the downloaded
apollo-ps4.pkgbinary file directly into the root directory (/) of the flash drive. - Connect the drive to your console, run your kernel exploit configuration (GoldHEN), and navigate to Settings → GoldHEN → Package Installer.
- Select the package from the onscreen prompt layout to trigger full automated setup execution.
XMB Package Deployment
- Prepare an external thumb storage layout formatted strictly to FAT32 specifications.
- Place
apollo-ps3.pkginto the storage root partition directory. - Power on the machine, trigger your Enable HEN icon tag (if running standard hybrid models), and scroll to the Game section.
- Enter Package Manager → Install Package Files → Standard, select the file target block, and confirm installation onto internal storage.
VitaShell VPK Extraction
- Establish a secure connection with your console via USB data transfer or local FTP configuration using VitaShell.
- Transfer the downloaded
apollo-vita.vpkfile onto your primary active storage partition path (typicallyux0:data/). - Navigate inside the target directory path using the VitaShell UI file browser list, highlight the asset, and tap the Cross [X] button.
- Authorize the internal operational extended permission request prompts to successfully register the homebrew app onto your LiveArea dashboard.
Post-Download Troubleshooting & Error Fixes
Encountering an issue after downloading? Console operating systems can occasionally trigger specific system errors when parsing homebrew binaries. Review the verified technical patches below.
Application Crash on Startup
Root Cause: This standard error code highlights a corrupted installation or an unprivileged payload environment.
Fix: Completely delete the corrupted application placeholder from your XMB dashboard. Hard reboot your system console, re-inject your GoldHEN payload environment via your host cache, and reinstall the verified apollo-ps4.pkg binary file.
Installation Corrupt Failure Error
Root Cause: The system firmware failed to authenticate the package configuration cryptographic signatures, usually due to an un-elevated system shell.
Fix: Ensure that the Enable HEN toggle switch has been actively engaged prior to entering the package manager. If using a standard CFW layout, verify that the download package wasn’t truncated during your USB drive migration by matching the official SHA-256 hash list.
Fatal Heap Allocation / Crash on Boot
Root Cause: Memory conflict issues generated by unstable background kernel system extensions (plugins) running in the background.
Fix: Use VitaShell to open your main configuration text layout located at ur0:tai/config.txt. Temporarily disable any aggressive experimental performance overlay modules. Ensure your VitaShell deployment properties have “Unsafe Homebrew” fully authorized inside the system configurations.
Save Editing & Risk: Read This First
Apollo Save Tool edits save files stored on your own console. The developer has never published any "anti-ban" protocol or safety guarantee — and neither can this site. Modifying saves is done entirely at your own risk.
💾 Before You Edit
Always export an untouched backup of the original save to USB first (Apollo: Export Save to USB). Downloaded saves from the Online Database must be re-signed to your account in Apollo before any game will load them.
🌐 Online Use
Taking a modified save into online play or syncing artificially unlocked trophies can violate a game’s or network’s terms of service and can put your account at risk. There is no technique that removes that risk — the only fully safe option is to keep modified saves offline.
Post-Download Internal Storage Mapping
Once Apollo Save Tool is active, it utilizes specific hardware directories to dump, backup, and read encrypted save file sectors. Refer to this physical path grid when managing files via FTP or desktop explorers.
00000001) to locate precise encryption keys.