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.

Spoiler: Addresses to block to avoid updates:

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)

Spoiler: System Update Information

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

Spoiler

https://github.com/astrelsky/libhijacker

https://github.com/illusion0001/libhijacker

https://github.com/TheOfficialFloW/Presentations/blob/master/2022-hardwear-io-bd-jb.pdf

https://github.com/sleirsgoevy/bd-jb

https://github.com/psxdev/bd-jb

https://gbatemp.net/download/remount-system-with-write-permissions.37807/

https://github.com/john-tornblom/ps5-payload-sdk

https://github.com/john-tornblom/bdj-sdk/actions/workflows/bdjb.yml

 

[AlphaBravo]

The .xml files that maj0r has incorporated into Cheatrunner still have issues; they experience frame drops and stuttering, and even conflict with the operating system. I assume this is because they’re running through Cheatrunner. On the other hand, the Patch Manager from the Illusion repository, which someone kindly forked to provide support for 13.60, has zero issues. Bloodborne, patched with Cheatrunner, has audio problems when running, and the Shadow of the Colossus remake can’t maintain 60 fps when running in 4K. It’s a different story with the Patch Manager; no game has given me those problems. I had talked to maj0r about the Gravity Rush 2 patch, since it stuttered a lot with Cheatrunner. I sent him all my logs, and he assumed the patch was bugged in 13.60. The day Patch Manager support was added, the first thing I did was test GR2, and I was amazed that there were no problems, no bugs, nothing.

I don't really use cheats so removed cheatrunner and just use patch manager to enable 60fps.

Are you using a ps5 pro or base console? I have had mixed results.

Batman Arkham Asylum (PS4) hits 59-60fps but drops as low as 45fps while gliding through sections of the city, car chases,etc.
Still unplayable for me as sensitive to frame drops. Perhaps Pro ps5 would fix?

Shadow of Mordor (PS4) on the other hand remains locked at 60fps and finally playable!

Once I fix current issue with my ps5, I will checkout Drive Club next....

 

[Blythe93]

Can anyone share their newest autoloader setup with me by chance?

I doubt that my autoloader setup will be useful to you but my Payload Manager is still on 0.5.2 and I'm using kstuff lite 1.11, ShadowMountPlus 1.7beta5-fix1 and nanodns 0.4. So far no KPs whatsoever. My current load order is: nanoDNS, ShadowMountPlus, kstuff lite, with 3s delay between them. Note that I'm yet to try out some games in FPKG format so I can't really say how stable it really is.

 

[TheStonedModder]

Will your overlocking research benefit PS5 Pro?

I don’t own a pro and won’t be able to afford one anytime soon. So I don’t know

 

[Bigoroth]

I don't really use cheats so removed cheatrunner and just use patch manager to enable 60fps.

Are you using a ps5 pro or base console? I have had mixed results.

Batman Arkham Asylum (PS4) bits 59-60fps but drops as low as 45fps while gliding through sections of the city, car chases,etc.
Still unplayable for me as sensitive to frame drops. Perhaps Pro ps5 would fix?

Shadow of Mordor (PS4) on the other hand remains locked at 60fps and finally playable!

Once I fix current issue with my ps5, I will checkout Drive Club next....

I'm on base console, but I haven't tested Batman yet-

From my own testing with Patch Manager:

Bloodborne
Driveclub
The Order 1886
OG FF VII Remake
OG Marvel's Spider-Man
The Evil Within
Gravity Rush 2

All of those running at 60 without problems. I wanna make some free time to test some others. I want to test RDR 2 as well, but I need a lot of time for that one in particular given the game and update file size.

I can give Batman a test in a couple of hours tho.

 

[Eva888]

I don't really use cheats so removed cheatrunner and just use patch manager to enable 60fps.

Are you using a ps5 pro or base console? I have had mixed results.

Batman Arkham Asylum (PS4) bits 59-60fps but drops as low as 45fps while gliding through sections of the city, car chases,etc.
Still unplayable for me as sensitive to frame drops. Perhaps Pro ps5 would fix?

Shadow of Mordor (PS4) on the other hand remains locked at 60fps and finally playable!

Once I fix current issue with my ps5, I will checkout Drive Club next....

Are you sure you didn't do anything differently? For instance, did you try some kind of "HV Reborn"? Try to figure out what you might have done differently—maybe a different exploit, a different payload, etc. You can back up your saves (and your entire profile, just to be safe) and then reset the console, but it’s probably better to try and find a fix for this issue first.

 

[AlphaBravo]

Are you sure you didn't do anything differently? For instance, did you try some kind of "HV Reborn"? Try to figure out what you might have done differently—maybe a different exploit, a different payload, etc. You can back up your saves (and your entire profile, just to be safe) and then reset the console, but it’s probably better to try and find a fix for this issue first.

Nothing different. In fact I made sure to load only a few payloads (Kstuff,SM+,ftpsrv). No etahen, no autoloaders, etc. I do everything manually to rule out conflicts. Everything worked perfectly until I installed "Sword of the Sea" (PS5) Dump with separate backport (not tested for my fw). Converted it to fpkg and after launching all problems began.
Deleting game and backport folder did not fix issue. Even after deleting Shadowmount+ and trying different versions.
Perhaps there are other folders or files in different parts of directory where problem is allowed to continue. Will try more testing tomorrow.

 

[PopperTop]

Is it too late to buy a retail PS5? Will they be running newer firmware versions? If I go to buy one tomorrow, what should I look for on the box in the UK to make sure it’s compatible with the jailbreak?

 

[Blythe93]

Is it too late to buy a retail PS5? Will they be running newer firmware versions? If I go to buy one tomorrow, what should I look for on the box in the UK to make sure it’s compatible with the jailbreak?

They should be on a jailbreakable firmware as long as they weren't opened i.e. new, factory-sealed. The only serial number guide that I know of is this one: https://www.psdevwiki.com/ps5/Serial_Number_guide
Good luck!

 

[Rasa39]

Can anyone share their newest autoloader setup with me by chance? Kstuff and shadowmount and whatever else yall are using changes so quickly with what works and what doesn’t work

My current setup always says PPR failed

Still rocking the older UI version of elf-arsenal, I installed Drakmor's kstuff from his discord and SM+, which all get loaded automatically by elf-arsenal.

Keeping this older GUI version for now because it has an easy way to monitor temps and everything through the web UI. I'm honestly amazed how it's just working still.

Oh and I fixed the demons in my console, did a full reset because I was using one of master_s9's backups which I think was causing my troubles. (I can now see the ghost controller and onionhen settings bubbles for example)

 

[Bigoroth]

Which is the best save backup manager nowadays? I just beat Demon's Souls Remake for the first time and I wanna do a backup and put it on a USB drive

 

[ThePSGuy]

I see. I've found this image on Reddit:
View attachment 596006

I still have my Astro Bot FFPKG file as well as the original game dump in folders and files. Is there a tool that you guys use to convert those dumps into FPKGs? Some games require backports as well. On console, I've seen that AMPR emulator is required for some games as well. Will that work on my PS5 5.00? For example, Ghost of Yotei I've seen that it has a backport that works up to 4.03 or something and that there's a ampr_emu.index file with the fix for the loading splash screen. How to even run AMPR emu?

Still new to FPKGs so I'd like to get as much info as possible before I start converting my game dumps.

Hi, I didn't see anyone answering you so might aswell go ahead.

There are many tools available for converting folder dumps to FPKGs (this one for example: https://github.com/pearlxcore/PS5PkgTool) but I would advise using drakmor's fpkg-gui which is regularly updated (and because who knows FPKG better than drakmor?).

You can find it on his Discord channel in the room called "fpkg-payloads": https://discord.gg/UDB9UEtWVT

FPKGs don't bypass the need for a higher firmware so you still need ShadowMountPlus to mount your backports if needed.

On the contrary, ampr-emu is obsolete if you run FPKGs because they can make use of the A53 and get the full intended feature set of the PS5 without the need for emulators.

If you don't plan on using FPKGs and would rather stay with older formats (why would you even do that?) then you can use ampr-emu by creating a fakelib folder inside your folder dump and put the libSceAmpr.prx library in it: https://github.com/drakmor/ampr_emu

Also, in order to use the ampr-emu, you need to build an index for your game dump otherwise it won't work. To do that, you have to run a python script that can be found in drakmor's Discord channel.

Hope that answers all your questions, if you have more, feel free to ask them.

 

[ViRGE]

Can anyone share their newest autoloader setup with me by chance? Kstuff and shadowmount and whatever else yall are using changes so quickly with what works and what doesn’t work

My current setup always says PPR failed

For FW 9.60, I have:

NanoDNS 0.4
kstuff-1.13-fpkg-dr-test6

And if I need it, OnionHEN v0.0.13.

And that's it. I have SM+ installed just in case I need it, but I never do since I'm using fPKGs for everything.

That is very strange that you are getting a PPR failed message. What firmware are you trying this on?

 

[TheStonedModder]

For FW 9.60, I have:

NanoDNS 0.4
kstuff-1.13-fpkg-dr-test6

And if I need it, OnionHEN v0.0.13.

And that's it. I have SM+ installed just in case I need it, but I never do since I'm using fPKGs for everything.

That is very strange that you are getting a PPR failed message. What firmware are you trying this on?

Of course now that I asked for help, it’s working

But this is 3.0 5.50 and 13.6 that is all doing this to me randomly

Maybe I just have excessively bad luck

 

[ViRGE]

Of course now that I asked for help, it’s working

But this is 3.0 5.50 and 13.6 that is all doing this to me randomly

Maybe I just have excessively bad luck

If you're on FW 13.60, then it's my understanding that the PPR patch should fail. That's the A53 patch, which only works on firmwares up to 11.60.

 

[Bigoroth]

Can anyone share their newest autoloader setup with me by chance? Kstuff and shadowmount and whatever else yall are using changes so quickly with what works and what doesn’t work

My current setup always says PPR failed

For mine I have

nanodns, kstuff-lite, an onionHEN build, and shadowmountplus 1.7betafix1 with a 5 second delay between each one

 

[cvskid]

Don't know how useful this is for anyone since i have not heard anyone talk about it but this suposedly disables ps5 system updates besides using the dns 127.0.0.1 with nanodns elf method.

https://github.com/logic-68/Enable-Disable-UPD-PS5

 

[Skirttles]

Can anyone share their newest autoloader setup with me by chance? Kstuff and shadowmount and whatever else yall are using changes so quickly with what works and what doesn’t work

My current setup always says PPR failed

FW 7.61
Using y2jb to jailbreak, loading payload manager:

Kstuff drakmor 1.13 beta6
8 sec delay
Shadowmount 1.17 beta5fix1
3 sec delay
Nanodns 0.4

 

[ayechief]

Can anyone share their newest autoloader setup with me by chance? Kstuff and shadowmount and whatever else yall are using changes so quickly with what works and what doesn’t work

My current setup always says PPR failed

Launching just the kstuff (i'm using 1.13-DR-TEST6) instantly gives an error PPR failed.

 

[HS2005]

Can anyone share their newest autoloader setup with me by chance? Kstuff and shadowmount and whatever else yall are using changes so quickly with what works and what doesn’t work

My current setup always says PPR failed

I can reproduce PPR failures with kstuff-1.13-fpkg-dr-test6. Just tested it. So I switched back to kstuff-lite.

I wanted to update to ps5-payload-manager v0.6.0. But It messed up the whole folder structure and autoloader. I always have backup. So now i'm on ps5-payload-manager v0.6.1. This is my build below:

Post automatically merged: Oct 15, 2026

Some updates:

ps5-payload-manager v0.6.1​

Changelog​

Backend & Bug Fixes​

• Restored automatic Disc Player termination on startup for BD-JB users, which was removed in v0.6.0.
  This is still useful for users on older BD-JB autoloader builds (lower than v1.4.0).

Full Changelog: v0.6.0...v0.6.1

---

How to update​

You do not need to manually download or replace your original pldmgr.elf file.
Simply install the update directly within the Payload Manager app (from the repository).
The updated version will automatically launch on every subsequent startup, regardless of whether you load the old or new .elf file initially.

Link: https://github.com/itsPLK/ps5-payload-manager/releases/tag/v0.6.1

Post automatically merged: Oct 15, 2026

Y2JB update:

ps5-y2jb-autoloader v1.0.2​

Changelog:​

• Relapse:
  • fixed fw 7.xx support
  • droped the one-run-per-boot fail marker

Full Changelog (since last stable release): v1.0.1-0866fb4...v1.0.2-254c85f

Link: https://github.com/itsPLK/ps5-y2jb-autoloader/releases/tag/v1.0.2-254c85f

 

[Eva888]

I can reproduce PPR failures with kstuff-1.13-fpkg-dr-test6. Just tested it. So I switched back to kstuff-lite.

I wanted to update to ps5-payload-manager v0.6.0. But It messed up the whole folder structure and autoloader. I always have backup. So now i'm on ps5-payload-manager v0.6.1. This is my build below:

View attachment 596127

Post automatically merged: Oct 15, 2026

Some updates:

ps5-payload-manager v0.6.1​

Changelog​

Backend & Bug Fixes​

• Restored automatic Disc Player termination on startup for BD-JB users, which was removed in v0.6.0.
  This is still useful for users on older BD-JB autoloader builds (lower than v1.4.0).

Full Changelog: v0.6.0...v0.6.1

---

How to update​

You do not need to manually download or replace your original pldmgr.elf file.
Simply install the update directly within the Payload Manager app (from the repository).
The updated version will automatically launch on every subsequent startup, regardless of whether you load the old or new .elf file initially.

Link: https://github.com/itsPLK/ps5-payload-manager/releases/tag/v0.6.1

Post automatically merged: Oct 15, 2026

Y2JB update:

ps5-y2jb-autoloader v1.0.2​

Changelog:​

• Relapse:
  • fixed fw 7.xx support
  • droped the one-run-per-boot fail marker

Full Changelog (since last stable release): v1.0.1-0866fb4...v1.0.2-254c85f

Link: https://github.com/itsPLK/ps5-y2jb-autoloader/releases/tag/v1.0.2-254c85f

Is there any reason why garlic is there? I thought that was used when someone needs to edit a save file.

Nothing different. In fact I made sure to load only a few payloads (Kstuff,SM+,ftpsrv). No etahen, no autoloaders, etc. I do everything manually to rule out conflicts. Everything worked perfectly until I installed "Sword of the Sea" (PS5) Dump with separate backport (not tested for my fw). Converted it to fpkg and after launching all problems began.
Deleting game and backport folder did not fix issue. Even after deleting Shadowmount+ and trying different versions.
Perhaps there are other folders or files in different parts of directory where problem is allowed to continue. Will try more testing tomorrow.

Could you please try creating a new profile and checking if things work fine with it? I also recommend inspecting the last two PKG files you downloaded—use a PKG viewer to look at the actual files inside. It’s possible that the "backport" was actually just an official patch, which might have caused some confusion in the database, or perhaps it was a virus specifically designed to corrupt the profile database.