Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


FW Ranges:
2.XX = PS4/5 backups (KEX+HV+Linux) + keys exploit (WK: 2.50 best / 2.7X max)
3.XX = PS4/5 backups (KEX+HV+Linux) + keys exploit (WK/BD/LUA: 3.20 best / 3.21 max)
4.XX = PS4/5 backups (KEX+HV+Linux) + keys exploit (WK/BD/LUA (Y2/NF/YARPE 4.03+): 4.50 best / 4.51 max)
5.XX = PS4/5 backups (KEX+HV+Linux) + keys exploit (
WK/BD/Y2/NF/LUA/YARPE: 5.50 best + max)

6.XX = PS4/5 backups (KEX+HV+Linux) (BD/Y2/NF/LUA/YARPE: 6.50 max)
7.XX = PS4/5 backups (KEX+HV+Linux) (
WK/BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = PS4/5 backups (KEX+HV+Linux) (WK/BD/Y2/NF/LUA/YARPE)
10.01-12.70 = PS4/5 backups (KEX+HV+Linux) (
WK/BD/Y2/NF/LUA/YARPE)
13.XX-13.60 = PS4/5 backups (KEX+HV+Linux) (
WK/BD(13.42)/Y2/LUA/YARPE)
14.XX = No public KEX, HV/A53 patched in 14.20, UL ONLY (LUA/YARPE)

NOTE 1: Recommended firmware is subjective. Staying low is always recommended.
NOTE 2: Do not update too many major versions (e.g., 4.xx to 5.xx or 7.xx to 8.xx). Remain low unless all you want is backups.
NOTE 3: P2JB can take over an hour to exploit on FW up to 12.70.


Hypervisor (HV):
Highest released HV: 13.60
Highest unreleased HV: 14.00
*unreleased/unimplemented


Kernel (KEX):
Highest released KEX:
13.60 (ReLapse)
Highest unreleased KEX: 14.10 (Gezine)
UMTX2:
1.00-7.61 (*WK to 5.50 / BDJB to 7.61)
Lapse: 1.00-10.01
Relapse: 7.00-13.60
Poopsploit:
4.03-12.00 (*BD to 12.00)
P2JB: 9.00-12.70 (*WK: Lapse to 10.01 / P2JB to 12.70)

Userland (UL):
Webkit: 1.00-5.50 (PSFREE +UMTX2) / 7.00-13.60 (RELAPSE) (Recommended)
LUA (Artemis): 2.00-LATEST (LUA exploit, + Lapse up to 10.01)
Y2JB: 4.03-13.40 (YouTube exploit, + Lapse: 10.01 / P2JB: 12.70)
NFNH: 4.03-12.XX (Netflix exploit, + Lapse: 10.01)
YARPE: 4.03-12.XX (Ren'Py exploit, + Lapse: 10.01 / P2JB: 12.70)
BD-JB: 1.00-13.42 (BD exploit + UMTX2: 7.61 / BD-JB5 + Poops to 12.00) (14.XX SOON)
Mast1C0re: 1.00-7.61 (Depreciated for LuaC0re)
LuaC0re: 1.00-12.70 (Poops: 4.03-12.00/P2JB: 9.00-12.70)
REDIS: 1.00-5.50 (Jordy's untethered JB on boot)

NOTE 1: A userland entry point (UL) chained to kernel exploit (KEX) is required to exploit your console at bare minimum.
NOTE 2: Consoles 7.00-13.60 should now use WebKit and RELAPSE (Recommended)


Useful Applications:
FPKG: 3.00-11.60 (KStuff Lite) / 12.XX-13.60 (KStuff-NG SOON)
Kstuff Lite: 3.00-12.70
HERE
Kstuff Toggle: 3.00-12.00 HERE
PS5 App Dumper: 3.00-13.60 HERE
Dump Runner: 3.00-12.00 HERE
Dump Installer: 3.00-12.00 HERE
Backporting: Possible (backpork / Porkfolio)
PS4/PS5 DLC: Work with Kstuff Lite
Trophies: Work with Kstuff Lite
Compression: Works with Kstuff Lite
Homebrew Enabler: etaHEN (3.00-10.01) latest HERE
PS5 Backup manager: ItemzFlow Compatibility list: HERE
PS4 Backup Loading: Works (rest mode & backports work, can crash).
PS5 Debug NG: 3.XX-13.XX
HERE
PS5 Remote Play: Works HERE & HERE
PS5 Trainers/Cheats: Work

UART:
HERE
Linux: (OG: 3.00-13.60) HERE
Kldload (wip): 3.00-6.50 HERE
PSN access: NEVER
Latest OFW: 14.22 (2/11/26)
Summarised OFW/Model guide: HERE
1.XX-7.61 compatibility list:
HERE
PS5 SDK Repo: HERE
Legit PKG Updates: HERE or HERE
OFW Updates: HERE (history HERE)

Preparing Your Console:


It is recommended to either self-host offline or block these addresses in your router to avoid accidental updates or getting an update nag. Using the DNS method is no longer failsafe, as these are not guaranteed to be running 24/7.


dau01.ps5.update.playstation.net
dbr01.ps5.update.playstation.net
dcn01.ps5.update.playstation.net
deu01.ps5.update.playstation.net
dhk01.ps5.update.playstation.net
djp01.ps5.update.playstation.net
dkr01.ps5.update.playstation.net
dmx01.ps5.update.playstation.net
dru01.ps5.update.playstation.net
dsa01.ps5.update.playstation.net
dtw01.ps5.update.playstation.net
duk01.ps5.update.playstation.net
dus01.ps5.update.playstation.net
fau01.ps5.update.playstation.net
fbr01.ps5.update.playstation.net
fcn01.ps5.update.playstation.net
feu01.ps5.update.playstation.net
fhk01.ps5.update.playstation.net
fjp01.ps5.update.playstation.net
fkr01.ps5.update.playstation.net
fmx01.ps5.update.playstation.net
fru01.ps5.update.playstation.net
fsa01.ps5.update.playstation.net
ftw01.ps5.update.playstation.net
fuk01.ps5.update.playstation.net
fus01.ps5.update.playstation.net
hau01.ps5.update.playstation.net
hbr01.ps5.update.playstation.net
hcn01.ps5.update.playstation.net
heu01.ps5.update.playstation.net
hhk01.ps5.update.playstation.net
hjp01.ps5.update.playstation.net
hkr01.ps5.update.playstation.net
hmx01.ps5.update.playstation.net
hru01.ps5.update.playstation.net
hsa01.ps5.update.playstation.net
htw01.ps5.update.playstation.net
huk01.ps5.update.playstation.net
hus01.ps5.update.playstation.net
sgst.prod.dl.playstation.net
gs2.ww.prod.dl.playstation.net

Alternative DNS IP:
62.210.38.117 - User Guide = ES7in1
or
45.56.67.85
(Leave DNS 2 blank)

To determine your OFW version:
Go to settings > system > console information.

Version string info:
Year.Half (1st/2nd half of the year)-Major Version No.Minor Version No.Extended info-Further Info.Retail/Debug

21.02-04.03.00.00-00.00.00.0.1

It is recommended to keep your console as low as possible to have access to better jailbreak stability and features. Stay as low as possible within the "Golden" firmware brackets that apply to your current firmware, see the top of this page.

(No jailbreak is ever guaranteed. No developer is obliged to release anything publicly)

WARNING:

Only update OFW manually via USB by getting the firmware file from HERE and installing from <USB>:/PS5/UPDATE/PS5UPDATE.PUP
(Updating with RECOVERY PUP will perform a factory format and will wipe your internal HDD)

PS5 factory mode PUP installation path:
/usb/PROSPERO/UPDATE/PROSPEROUPDATE.PUP

NOTE: Make a system back up before attempting any modifications.
On console: go to [Settings] > [System] > [System Software] > [Back Up and Restore] > [Back Up Your PS5]

Select Your Jailbreak:


WEBKIT:BD-JB:LUA:Y2JB:NFNH:YARPE:LuaC0re:BD-UN-JB:


  1. Information:
    Firmware 1.00-5.50 or 7.00-13.60 is required for the webkit exploit.

    Enabling web browser:
    Open [Settings] > select [Users & Accounts] > select [YouTube] > click "Link" > click "use browser" > click "terms" (bottom right) > click google apps icon (top right) > select Google Search.

    Exploiting 1.00-5.50:
    Enter https://zecoxao.github.io/luasauce/ or https://github.com/kmeps4/PSFree into google > click “Jailbreak" or wait for it to complete.

    Exploiting 7.00-13.60:

    https://ntfargo.github.io/Relapse-Exploit/

    https://zecoxao.github.io/bagagwa/

    https://soniciso1.github.io/poopicker/

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  2. Important:
    You will need a BD dive paired to your Slim/Pro console or an OG Phat model . Consoles must be on 1.00-13.42 to run this exploit.


    Recommended ISO: Viktorious AIO Auto BD-JB ISO for 4.XX-7.61

    Exploiting: 1, Burn ISO to a blank BD-R or BD-RE > Insert into console > click on the [DISC PLAYER] icon.

    2, Highlight [PIPELINE RUNNER] > click option 2 [Normaljailbreak-etaHEN-UMTX1.pipe] to auto load etaHEN ready for ItemzFlow.

    ELF Loader uses PS5 IP: port 9021 / BIN loader uses 9020 / Jar loader uses port 9025

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  3. Important:
    LUA entry point works from 2.00 to the latest OFW, but there is no KEX above 12.70 yet.
    (A compatible PS4 game is required to launch the exploit on PS5. See below)

    Your PS5 console must be activated to use save copying for PS4 games.
    1. Insert your game disc and, as soon as possible, make a save file within it.
    2. Copy the save files to USB, go to [SETTINGS] > [STORAGE] > [CONSOLE STORAGE] > [SAVE DATA] > [PS4 GAMES] > select the game save and copy to a USB drive.
    3. On PC, using a Google Drive account, make a new folder with the GAME ID of your game, and upload the savedata & savedata.bin files to that folder.
    4. Share the folder, set it to editor mode, share with anyone, and click "copy the link".
    5. Join the HTOS Discord group: HERE type "/decrypt", select "FALSE" for including SCE_SYS, paste or type in the Google Drive link, and press enter. The bot should begin mounting your save. (If it doesn't, paste in the link again.)
    6. Click "ENCRYPTED" to remove the Sony PFS layer. Download the generated files and extract the folder to your desktop (you should have 4 files in there and be named dec_savedata_CUSA[GAME ID]).
    7. Using REMOTE LUA LOADER, open the savedata folder, copy the 20 files within into your encrypted save folder on your desktop.
    8. Upload the encrypted save folder (now with 24 files in) to your Google Drive. It should be named "dec_savedata_CUSA[GAME ID]" where GAME ID is your games 5 digit number, and set it to editor mode, share with anyone, and then click "copy the link".
    9. Go back to the HTOS discord server, and type "/encrypt", hit "FALSE" for uploading individually, and "FALSE" to include SCE_SYS. Finally, hit shared_gd_link and paste in your link to the original save (4 files) folder. (If it doesn't, paste in the link again.)
    10. When this is done, paste the link to the decrypted save (24 files) folder, and the bot will encrypt the files.
    11. Resign the files by typing "/resign" followed by your account name on the console, or PSN ID associated with that account if using the latest OFW.
    12. Download the resigned files, extract the files to your USB drive and overwrite them into the savedata folder on your USB or external drive.
    13. Copy the saves back to your console [SETTINGS] > [SAVE DATA AND GAME/APP SETTINGS] > [SAVE DATA PS4] > [COPY OR DELETE FROM USB] > [COPY TO CONSOLE STORAGE] > select your game save folder from the USB drive and copy/overwrite old save data.
    14. Load LUA game again, and you should see the LUA LOADER screen.
    15. You can use "SEND_LUA.PY" to send the UMTX files to the loader.
    (NOTE: Some games require manual loading of save game)

    On firmware up to 7.61, you can now load UMTX/2 followed by etaHEN by sending the files to your console IP on PORT 9026.
    On firmware 8.00-LATEST, you can connect with the REMOTE LUA LOADER APP to send debug notifications or FTP on port 1337.

    LUA Loader: HERE or HERE

    Auto LUA Loader Fork: HERE

    Compatible LUA games:
    Aerial Life (CUSA17122)
    Aibeya (CUSA17068)
    Aikagi 2 (CUSA19556)
    Aikagi Kimi to Issho ni Pack (CUSA16229)
    Aikano Yukizora no Triangle (CUSA19370)
    Boku to Nurse no Kenshuu Nisshi (CUSA12049)
    Boku to Joi no Shinsatsu Nisshi (CUSA18107)
    Fuyu Kiss (CUSA29745)
    Hamidashi Creative (CUSA27389)
    Hamidashi Creative Demo (CUSA27390 requires the latest OFW to download from PSN)
    Haruoto Alice (CUSA14324)
    IxSHE Tell (CUSA17112)
    IxSHE Tell Demo (CUSA17126)
    Jinki Resurrection (CUSA25179)
    Jinki Resurrection Demo (CUSA25180 requires the latest OFW to download from PSN)
    Maid-san no Iru Kurashi (CUSA18106)
    Nora Princess and Stray Cat Heart HD (CUSA13303: Rename save9999.dat into nora_01.dat)
    Nora Princess and Strat Cat Heart 2 (CUSA13586)
    Raspberry Cube (CUSA16074)
    Winter Guest (CUSA11977)

    WARNING: using demos is free but can become corrupt, and you cannot upgrade your internal HDD either. If you lose the demo you can no longer use the exploit. Disc recommended.

    Incompatible LUA games:

    Dokyusei Remake Csver (CUSA47117)
    Dōkyūsei: Bangin' Summer - Home Edition Demo (CUSA47132)
    Kiss Trilogy (CUSA19341)
    Love Clear Demo (CUSA18109)
    Mikagami Sumika no Seifuku Katsudou (CUSA11481)
    Sen no Hatou, Arazone no Hime (CUSA09647)
    Tonari ni Kanojo no Iru Shiawase: Two Farce (CUSA09825)
    Tonari ni Kanojo no Iru Shiawase Summer Surprise (CUSA18998)

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  4. Requirements:
    PS5 console must be on 4.03-12.70 and previously activated through PSN or fake activated to use the YouTube app, unless you're restoring a backup.
    (Note: restoring a backup will factory reset your console).

    Information:
    If updating and older installation, download the latest download0.dat > use FTP or PS5 Explorer to place it in the user/download/PPSA01650 folder.

    Preparation:
    Download the Y2JB_backup_X.X(4.03) if you're on 4.03-12.40, or the Y2JB_backup_X.X(12.20) if you're on 12.60 or higher from HERE
    On PC: format a USB 3.0 HDD to exFAT, and copy the PS5 folder from the backup to the root, and put the latest nanodnf.efl from nanoDNS to the root too.
    On console: go to [Settings] > [System] > [System Software] > [Back up and Restore] > [Restore] > select the y2JB back up & let it install (the console will reboot when complete).
    (Note: The exploit will now be accessible under the [MEDIA] tab)

    Exploiting:
    Going to [Settings] > [Network] > [Settings] > [Set up Internet Connection] > [Set up Manually] > set up a wireless or LAN connection > change [DNS Settings] to manual > change [Primary DNS] to 127.0.0.1 > click [Done] > open the [YouTube App].
    (Note: Ignore and internet connection issue warnings)

    Firmware up to 10.01 will use Lapse Kernel Exploit. Firmware 10.20-12.70 and above will use P2JB and could take up to an hour.

    You can send payloads using netcat GUI to PS5's IP Address & port 9021.

    You can swap the download0.dat to itzPLK version for auto loading and payload manager in future (payload manager accessible through browser on 127.0.0.1:8084)

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  5. Requirements:
    PS5 console must be on 4.30-10.01 and previously activated through PSN or fake activated. You will need a 256GB external HDD (minimum).

    Preparation:
    Download balenaEtcher
    Download the latest Extended Storage or M.2 Image (select your m.2's capacity)

    EXTERNAL DRIVE METHOD (Netflix_PS5_EU_Ext.7z):
    1a, On PC: connect your 256GB (min) USB drive to your Windows/Mac/Linux PC > extract the image to your computer > open Etcher > click [Flash From File] & select the extracted image *.zip > click [Select Target] & choose the external drive > Click [Flash!] & allow it to complete.
    (Note: 256GB is the smallest drive you can use)

    2a, On console: click [Settings] > [Storage] > [USB Extended Storage] > [Games and Apps] > press X on [Netflix] > select [NETFLIX] under items to move > select [Move] > move to internal storage & allow it to complete.
    (Note: The exploit will now be accessible under the [MEDIA] tab)

    INTERNAL DRIVE METHOD (Netflix.XXXXGB.7z):
    1b, On PC: connect the M.2 to your Windows/Mac/Linux PC > extract the image to your computer > open Etcher > click [Flash From File] & select the extracted image *.zip > click [Select Target] & choose the external drive > Click [Flash!] & allow it to complete.
    (Note: 4TB will take 80 mins, 2TB 45 mins, 256GB 10 mins)

    2b, On console: Power off the console > insert the M.2 SSD > power on the console > click [Settings] > [Storage] > press X on [Netflix] > select [NETFLIX] under items to move > select [Move] > move to internal storage & allow it to complete.
    (Note: The exploit will now be accessible under the [MEDIA] tab).

    Exploiting:
    1a, for consoles 10.01 and below, on console: go to [Settings] > [Network] > [Settings] > [Set up Internet Connection] > [Set up Manually] > set up a wireless or LAN connection. Go to Proxy > change [Automatic] to [Manual] > enter Address: 172.105.156.37 & port: 42069 > click [Done] > open the [Netflix App].
    (Note: Ignore and internet connection issue warnings)

    1b, for consoles 10.20-12.70, COMING SOON.

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  6. Important:
    YARPE works from 4.30 to 12.70 (9.00 - 12.07 via P2JB)
    (A compatible PS4 game is required to launch the exploit on PS5. See below)

    Requirements:
    PS5 console must be on 4.30-10.01 to use this exploit.

    Exploiting:
    coming soon

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  7. Requirements:
    PS5 console must be on 4.30-12.70 to use this exploit. SWRR

    Exploiting:
    coming soon

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].


  8. [UPDATED]
    No longer needed if using latest WebKit (to 13.60) or BD-JB (to 13.42)!


    Important:

    This method modifies the BD-J stack to allows BD-JB entry point to be re-enabled on consoles up to 13.60, for convenience only.

    Very Important:
    This method requires your console to be jailbroken by another method first to gain access to alter the files.

    https://github.com/Gezine/BD-UN-JB

    Preparation:
    Burn the ISO to a blank Blu Ray, insert it into the jailbroken console. Send the bdj_unpatch.elf to elfldr using netcat GUI to PS5's IP Address & port 9021 to unpatch BD-J.

    (NOTE: DO NOT REINSTALL/UPDATE FW, IT WILL WIPE THE PATCH AND LOSE BD-JB)


Once jailbroken it is recommended to run KSTUFF LITE and SHADOWMOUNTPLUS at minimum to get you up and running.
(ShadowMountPlus: is an automated background auto-mounter payload for jailbroken PS5 consoles. Detects, mounts, and installs game dumps from internal or external storage, with support for UFS, exFAT, PFS, and nested compressed PFS containers)

Additional Information:


Blocking Updated with nanoDNS:
Set primary DNS manually to 127.0.0.1. Send latest elf to BIN LOADER using netcat GUI to PS5's IP Address & port 9021.

PS4 GAME INFORMATION:
OFW 1.xx cannot run PS4 games.
OFW 2.xx runs PS4 games up to 8.03

OFW 3.xx runs PS4 games up to 8.52
OFW 4.xx runs PS4 games up to 9.04
OFW 5.xx runs PS4 games up to 9.60
OFW 6.xx runs PS4 games up to 10.50

OFW 7.xx runs PS4 games up to 11.00
OFW 8.xx/9.xx runs PS4 games up to 11.50
OFW 10.xx runs PS4 games up to 12.00

OFW 11.xx runs PS4 games up to 12.50
OFW 12.xx runs PS4 games up to 13.00
OFW 13.xx runs PS4 games up to 13.42
OFW 14.xx runs PS4 games up to 14.00


(Note: PS4 backported FPKGs also work perfectly on an exploited PS5 with Kstuff)


You can install free/demo PKGS (legit pkgs) via the debug pkg installer, provided you have all the files/json/licences required.
(Astro’s Playroom has no licences and can be installed and played from official pkgs and updated inline with your firmware)

Warnings:


1: Never enable IDU mode.
If you do, you will need to enter staff mode by holding L1 + L2 and tapping this combo: circle, cross, square, triangle, right D-Pad. Release L1 + L2, and you can access settings to exit IDU.

2: Try to stay on the lowest FW possible and wait for hacks on that firmware.

3: Installing legit game PKGs you do not own will never work, even if spoofed.

4: If you get stuck in a boot loop at the PS logo, the SNVS is corrupted (if the hash check fails on boot, this causes a “soft brick”). It’s not “bricked”. Simply reinstall your current firmware RECOVERY PUP in safe mode from USB: PS5 > UPDATE > PS5UPDATE.PUP.

Archived Information


 
Last edited by KiiWii,
Perhaps if you play games 24/7. I thought modern SSD don't have this problem. It is a bit concerning that the ps5 internal SSD is fused to the motherboard. If worried, you can always install to m2 drive.
I guess when Ark Sama releases his PHU format, that won't be a problem anymore...
Even with exFAT, background recording is still active, isn't it? This recording feature is hardcoded into the kernel; Sony likely did this on purpose so the console would "die" sooner, forcing people to buy a new one. So, to disable it, you’d probably need a hypervisor (which we have). For redirecting the output to an M2 drive, you might not even need a hypervisor—you’d just need to ensure the drive doesn't disconnect unexpectedly, which could cause issues. With an M2 drive, that’s simple, since it doesn't disconnect; it stays connected all the time, just like the internal drive.

24/7... I can easily imagine someone running Linux for several hours a day—using it like a PC. I suspect that in this scenario, Sony is also "recording" in the background, which wears out the internal drive.

By the way, what ever happened with that fpkg issue of yours? Did you find the reason why not everything would launch?
Post automatically merged:

------
By the way, folks, I saw a comment on Reddit regarding today's question about firmware 14.10... Apparently, Gezine mentioned that a hypervisor (HV) exploit is now required even for older games—something to the effect that a userland + kernel exploit alone will no longer suffice. I’m not entirely sure, though, so I’d recommend verifying that.


In any case, it’s clear that developers already have a userland + kernel exploit plus a hypervisor exploit for firmware 14.20—though they’re keeping it private. Whether they’ll actually dump games like "GTA VI" or "Phantom Blade Zero" for lower firmware versions remains uncertain(talking about near future)
 
With these sorts of posts, it is helpful to list some basic information and trouble-shooting steps.
  • PS5 model
  • Firmware version
  • Game format (I see you have a FFPKG)
  • What versions of kstuff and SM+ you are using
  • If the game requires a backport, whose backport you are using
  • Where you are trying to run the game from (Internal, M.2, or External)
  • And if it's not a fPKG, have you tried running it from another location?

Common reasons stuff doesn't work.
  • It just straight-up doesn't run from your storage location
  • You're running a PS5 Pro and it needs additional fixes
  • Depending on the package type, file name capitalization
  • Directory permissions
Meanwhile, this one is a very much an opinion, but if you're going to use an uncompressed container-based format, exFAT seems to get a lot more traction than FFPKG.


Someone else already mentioned this, but I'd second the vote for switching to Y2JB with Relapse if your setup allows it. Relapse is proving to be an extremely stable jailbreak, especially when activated via YouTube.

KPs do suck, though. I hope you didn't lose anything.🤞


Short answer: no. param.json almost always needs modification as well. And if it's a backport, then any included library files (system fakelibs aside) also need backported.

For reference, here is a list of backported files from a recent SDK 11 game release for its FW 4.xx backport.

Code:
Il2cppUserAssemblies.prx
PS5Util.prx
CommonDialog.prx
PSN.prx
SaveData.prx
lib_burst_generated.prx
libfmod.prx
libfmod_haptics.prx
libfmodstudio.prx
libresonanceaudio.prx
eboot.bin
libSceAgc.sprx
libSceAgcDriver.sprx
libScePsml.sprx
libSceNpCppWebApi.prx
libc.prx
right.sprx
Good evening

So, in order ⬇️

I'm using a PS5 Slim.
_____

My firmware is 12.20
_____

I tried to import it as I usually do via PS5Upload via .ffpfsc / .ffpkg / .exFAT and other various methods as shown in the attached photo below
_____

My version of Kstuff-lite is 1.11 and ShadowMount+ is also 1.7beta7

_____

The game requires firmware 13.60, and I downloaded the game with the 4.xx backport included.

_____

I'm running the game via the internal SSD

_____

In another location? What do you mean? The site originally offered the option to download the game as either an FPKG or an exFAT file. The uploader claims that FPKG files can only run on Android 11.60 or later.
And for firmware versions higher than 11.60, you need to download the game in exFAT format.
So I downloaded it in exFAT format and converted it using PS5Upload.

Thanks in advance! 👍🏻
 

Attachments

  • Snapchat-336811352.mp4
    602.2 KB
  • IMG_20261024_210028_1.jpg
    IMG_20261024_210028_1.jpg
    1.1 MB · Views: 3
  • Snapchat-337510314.mp4
    787.4 KB
  • Like
Reactions: AlphaBravo
Does someone know which firmware has Phantom Blade Zero?
I’m not sure; apparently, there won’t be a physical disc at launch, though there might be one later (supposedly next year)...

People have actually been playing this game for a while now—it might even work on version 13.xx... but I suspect we’ll likely get a version from 14.10 (by time game is officially released, firmware 14.10 should still have access to PSN, allowing for download of game+updates). People probably won’t know how to create thread for this game on "Prospero" scene... so, best bet is likely downloading it on 14.10 and then keeping it offline.

That said, I think we’ll probably get to play it sooner via "PC payload," given that this game is also coming to PC
 
The game requires firmware 13.60, and I downloaded the game with the 4.xx backport included.
No it doesn't, it requires firmware 12.xx or higher.

We already explained to you the difference between firmware requirement (for dumping) and SDK requirement (for running the backup) on this thread a few pages back so just get rid of your backport and try again.
 
Can someone explain to me what would be needed to allow fpkg games survive rest mode? Currently kstuff closes them when coming out of sleep. Would HV exploit improve this?I'm on 11.60
 
  • Like
Reactions: cloudfe
In another location? What do you mean?
Game dumps can be placed in one of three locations:
  • On your console's internal storage
  • On an M.2 drive installed in your console
  • On an external drive hooked up to your console via USB
Depending on the game, it may work in all locations or it may work in none of them. Often, games may fail on internal storage and work on external storage.

So I downloaded it in exFAT format and converted it using PS5Upload.
For what it's worth, you didn't need to convert it. FFPKG is just another uncompressed container like exFAT. If anything, that the game is being distributed in an exFAT container means that one is the better tested version.

And as mentioned by @ThePSGuy, this is a game that doesn't require a backport on your system. So you can get rid of that. When they are not needed, backports add another layer of potential issues.
 
Someone else already mentioned this, but I'd second the vote for switching to Y2JB with Relapse if your setup allows it. Relapse is proving to be an extremely stable jailbreak, especially when activated via YouTube.
3rd vote for Y2JB relapse. Works flawlessly everytime and seems to be a lot quicker to load as well. Good thing about using the YT app is that you can install up to 3 different versions so that you can have either a different setup or something like that. The only thing I found confusing to start with was having 2 of the same icon on the homescreen so I decided to find out how to change them to my liking, and now they show up as YT UK & YT US so I know which is which.
 
No it doesn't, it requires firmware 12.xx or higher.

We already explained to you the difference between firmware requirement (for dumping) and SDK requirement (for running the backup) on this thread a few pages back so just get rid of your backport and try again.
Yes, indeed, and I did read your message, but I don't understand. I can be a bit dense sometimes...

Game dumps can be placed in one of three locations:
  • On your console's internal storage
  • On an M.2 drive installed in your console
  • On an external drive hooked up to your console via USB
Depending on the game, it may work in all locations or it may work in none of them. Often, games may fail on internal storage and work on external storage.


For what it's worth, you didn't need to convert it. FFPKG is just another uncompressed container like exFAT. If anything, that the game is being distributed in an exFAT container means that one is the better tested version.

And as mentioned by @ThePSGuy, this is a game that doesn't require a backport on your system. So you can get rid of that. When they are not needed, backports add another layer of potential issues.
Ah! The problem is that where I download games, the backport is included in the file. Whether it's exFAT or fpkg, it doesn't matter, it is... 🫤
 
  • Like
Reactions: AlphaBravo
not sure how out dated the info this is, but i remember FW past 7.61 need like 1 hour to JB, is this still the case? if not whats the max FW for "instant" JB?
 
You understand that English isn’t everyone’s first language, right ?
I don't think language is relevant here.

He (supposedly) disabled fps cap in IO interactive game,, then wrote long ass rage post. About sony. Where is the logic? It is the same as blaming valve for theses stupid 60fps-locked games on steam, or lack of proper ultrawide support in majority of releases.

And you know what is missing in this long post? Link to actual patch. Why am I not even surprised?
 
Last edited by regex101,
  • Like
Reactions: ViRGE
I don't think language is relevant here.

He (supposedly) disabled fps cap in IO interactive game,, then wrote long ass rage post. About sony. Where is the logic? It is like blaming valve for theses stupid 60fps-locked games on steam, or lack of ultrawide support in majority of releases.

And you know what is missing in this long post? Link to actual patch.

Why am I not even surprised?
Zero is known for sharing these

I’ve also tested this specific one myself
 
  • Like
Reactions: iguanoPT
I don't want to badmouth the dev, especially as I am far too lazy to write any homebrew of my own. But this one legitimately has me scratching my head.

MPC-HC is a fantastic application that I use daily. But the strength of the program is that it is an old-school Win32-styled media player that can hook in to Windows' extensive array of media APIs and decode filters.

None of that is applicable to running it on the PS5. And as far as UI matters go, the platform doesn't even have a mouse.

This is a situation where you would want to port over a player that has been designed with a "big screen" UI from the start. Generally something FFMPEG-based, since you have to bring a complete media decoder environment to kick things off (and then work out how to pass things off to the system's hardware decoders as you refine the app).

The base isn't even the current version of MPC-HC (2.8.4). 1.7.13 is the old branch whose development went dormant almost a decade ago.

With that said, kudos to the developer for getting it done. Though this seems like a project where they did it because they can, rather than because it's something that anyone is going to use.
Yes, indeed, and I did read your message, but I don't understand. I can be a bit dense sometimes...


Ah! The problem is that where I download games, the backport is included in the file. Whether it's exFAT or fpkg, it doesn't matter, it is... 🫤
If a backport is done well, it shouldn't cause any issues. But as a troubleshooting step, you may need to download a folder dump version of the game that doesn't include the backport, and then pack that into an exFAT container yourself.
not sure how out dated the info this is, but i remember FW past 7.61 need like 1 hour to JB, is this still the case? if not whats the max FW for "instant" JB?
13.60 for an instant jailbreak. But you shouldn't update past 11.60 if you are going to be updating at all. 11.60 is the highest firmware that can currently run fPKG games.
I swear to Hades that PS5Upload goes through version updates more frequently than some members here change their underwear. I'm glad to see it is receiving active development, but there is something to be said for releasing software in two week sprints! :rofl2:

I don't think language is relevant here.

He (supposedly) disabled fps cap in IO interactive game,, then wrote long ass rage post. About sony. Where is the logic? It is the same as blaming valve for theses stupid 60fps-locked games on steam, or lack of proper ultrawide support in majority of releases.

And you know what is missing in this long post? Link to actual patch. Why am I not even surprised?
FWIW, I agree with you here.

That whole rant seems to be purposely obtuse to how game development works, and how developers decide when (and how) to cap their framerates. I am not surprised to hear that the game can hit 60fps in parts. But I will bet you dollars to donuts that it is not a stable 60fps.

There is something to be said for allowing a floating frame rate for those users who have a variable refresh display. But the PS5's VRR support is still glitchy due to a lack of built-in low framerate compensation. So I can see why a developer would choose to cap the game at 30fps, as, broadly speaking, most players seem to prefer that to a floating frame rate on a 60Hz display.

And none of this has to do with Sony. Those are all decisions the developer gets to make.
 

Site & Scene News

New Hot Discussed User Submitted