Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


FW Ranges:
2.XX = HEN+Kstuff+HV = PS4/5 backups, possible keys exploit (WebKit: 2.50 best / 2.7X max)
3.XX = HEN+Kstuff+HV+Linux = PS4/5 backups, possible keys exploit (WK/BDJB/LUA: 3.20 best / 3.21 max)
4.XX = HEN+Kstuff+HV+Linux = PS4/5 backups (WK/Y2JB/BDJB/LUA: 4.50 best / 4.51 max)
5.XX = HEN+Kstuff+HV+Linux = PS4/5 backups (
WK/Y2JB/BDJB/LUA: 5.50 best + max)

6.XX = HEN+Kstuff = PS4/5 backups, HV+Linux for 6.02 max (Y2JB/BDJB/LUA: 6.50 best + max)
7.XX = HEN+Kstuff = PS4/5 backups, no HV (
Y2JB/BDJB/LUA: 7.61 best + max)
8.XX-10.01 = HEN+ Kstuff = PS4/5 backups, no HV (Y2JB/LUA)
10.20-12.00 = KEX + Kstuff = PS4/5 backups, no HV (
LUA)
12.02-12.70 = KEX (
P2JB/SWRR)
13.XX = No KEX/HEN/Kstuff/HV (LUA)

NOTE: Recommended firmware is subjective. Staying low is always suggested first & foremost. It is not recommended to update too many major versions (e.g., 4.xx to 5.xx or 7.xx to 8.xx) because you should remain low unless all you want is backups.

DO NOT UPDATE OVER 12.00!! P2JB can take over 3 hrs to trigger an exploit.


Hypervisor (HV):
Highest known HV exploit: 6.02
Highest theoretical HV exploit: 7.XX
Highest implemented HV exploit: 1.00-4.51 (Cragson PS5Hen) / 3.00-6.02 (TheFlow)
*unreleased/unimplemented

Kernel (KEX):
Highest public Release:
12.70
Highest known: 12.70 (P2JB)
UMTX2: 1.00-7.61
Lapse: 1.00-10.01
Poopsploit: 4.XX-12.00
P2JB: X.XX-12.70

Userland (UL):
LUA: 2.00-LATEST (LUA game exploit, chain Lapse up to 10.01)
Y2JB: 4.03-12.60 (YouTube exploit, + Lapse up to 10.01)
NFNH: 4.03-12.XX (Netflix exploit, + Lapse up to 10.01)
YARPE: 4.03-12.XX (Ren'Py exploit, + Lapse up to 10.01)
BD-JB: 1.00-7.61 (Blu Ray exploit + UMTX2, 8.00-12.40 via UN BD JB + Poopsploit)
Webkit: 1.00-5.50 (PSFREE +UMTX2) (up to 13.20 coming soon)
Mast1C0re: 1.00-7.61 (PS2 backups)
LuaC0re: 10.20-12.02 (Star Wars RR: + Poopsploit up to 12.00)

NOTE: A userland entry exploit (UL) chained to kernel exploit (KEX) is required at a bare minimum to exploit your console.

NOTE 2: Since 12.60/13.00 Sony has removed the YouTube and Netflix apps and has added 30 day expirations to downloaded software used for LuaC0re/Mast1C0re/RenPy etc.

Digital consoles will now need a new webkit userland to hack their consoles as of 19/04/2026)


Useful Applications:
Elf loader: 8.00/7.61 HERE (use with BD-J)
Kstuff: 3.00-10.01 (3.00-12.70 soon)
HERE
Kstuff Lite: 3.00-12.70 HERE
Kstuff Toggle: 3.00-12.00 HERE
Dumping: Up to 8.00/7.61 (ItemzFlow / self decryptor) latest HERE
PS5 App Dumper: 3.00-12.00 HERE
Dump Runner: 3.00-12.00 HERE
Dump Installer: 3.00-11.60 HERE
Backporting: Possible (backpork / Porkfolio)
PS4/PS5 DLC: Work with kstuff (on retail disc games)
Homebrew Enabler: etaHEN (3.00-10.01) latest HERE
PS5 Backup Loading: Itemzflow HERE Compatibility list: HERE
PS4 Backup Loading: FPKG Enabler 3.XX-9.XX (rest mode & backports work, can crash).
PS5 Debug: Works
HERE
PS5 Remote Play: Works HERE & HERE
PS5 Trainers/Cheats: Work (Built into itemzFlow)

UART:
HERE
Linux: (3.00-6.02) HERE
Kldload (wip): 3.00-6.50 HERE
Full chain exploit: 1.00-4.51 (byepervisor) HERE (also built into etaHEN up to 2.7X)
PSN access: NEVER
Latest OFW: 13.20 (23/04/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:
DNS 1: 172.245.146.114
(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.

Current Examples:

2.00 could be updated to 2.50 maximum to retain Webkit/BD-JB/LUA HV + KEX + HEN.
4.00 could be updated to 4.51 maximum for WebKit/BD-JB/LUA + KEX + HEN + potential HV exploits.
5.00 could be updated to 5.50 maximum for WebKit/BD-JB/LUA + KEX + HEN.
6.XX-7.XX could be updated to 7.61 maximum for HEN using only BD-JB or LUA.
Digital/Pro users on 6.XX-LATEST cannot use BDJB or LUA without an activated console. Wekbit does not go beyond 5.50 for now.
Digital/Pro users or Disc console users on 8.XX-LATEST should consider waiting or selling/swapping consoles to get a lower firmware.
(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

SYSTEM UPDATES:

12.00 SYS MD5: 79d3171ec4ef38ca27f8ff36a9940847 (Exploited - No HEN yet)

10.01 SYS MD5: 68a31944c1867bf9643798fd1c14998e (Exploited + HEN)
9.00 SYS MD5: e74ddccd3360941ca24475c13195e031 (Exploited + HEN)
8.00 SYS MD5: 7616128c57581d5e49b42d1b3f308232 (Exploited + HEN)
7.61 SYS MD5: d5eca8b171a8d7df7ba225167f77e645 (Exploited + HEN)

6.50 SYS MD5: 98db854ba47a75dff0cb09355bca9025 (Exploited + HEN)
5.50 SYS MD5: edb3513ec531b2bd28f3a0b52a82a54f Exploited + HEN)
4.51 SYS MD5: 1330b7bf63bf5c93d809b1eb1f4e1f01 (Exploited + HEN)
4.03 SYS MD5: 3716e4e6e0d223cd94cd4a8e5bd4fb94 (Exploited + HEN)

RECOVERY UPDATES (wipes HDD):
12.00 REC MD5: f993e4c35ed6659b516346941980de4b (Exploited - no HEN yet)

10.01 REC MD5: 5202be086fc726d881f722d46e4486c6 (Exploited + HEN)
9.00 REC MD5: 6fbbda82c325bb5d6ec0717c2223b5c0 (Exploited + HEN)
8.00 REC MD5: 6cbb7a2fa2ace926202bd6e71304fb06 (Exploited + HEN)
7.61 REC MD5: 932f24e934723050fe49561b67e95226 (Exploited + HEN)
6.50 REC MD5: 4305223c12bd6dda9b944c0ee49c94c0 (Exploited + HEN)
5.50 REC MD5: c939ac8b37e07bbc129816a61002d30a (Exploited + HEN)
4.51 REC MD5: da78ca268da90a963d89b0f45db0f061 (Exploited + HEN)
4.03 REC MD5: e6dcc800d8d1dcada4f2bcd6e7ff162c (Exploited + HEN)

PS5 factory mode PUP installation path:

/usb/PROSPERO/UPDATE/PROSPEROUPDATE.PUP

Select Your Jailbreak:


WEBKIT (1.00-5.50):BD-JB 1.00-7.61:LUA (2.00-LATEST):Mast1c0re (2.00-7.61):Y2JB (4.03-10.01):NFNH (4.03-10.01):YARPE (4.03-10.01):LuaC0re (12.00 REQUIRES SWRR):BD UN JB (REQUIRES JB'D CONSOLE):


  1. PSFREE 1.XX-5.XX: https://github.com/kmeps4/PSFree
    Recommended host: https://zecoxao.github.io/luasauce/ (UMTX2 + Webkit for 1.XX-5.XX)

    Recommended WebKit hosts:
    https://zecoxao.github.io/luasauce/
    (UTMX2 with Lua and WebKit for 1.xx-5.xx)
    https://zecoxao.github.io/umtx/ or https://es7in1.site/
    (UMTX 2 exploit works on 3.00-5.50 with PSFREE WebKit)

    Alternative hosts:
    https://zecoxao.github.io/ps5jb/

    https://ps5jb.pages.dev/
    https://sleirsgoevy.github.io/ps4jb2/ps5-403/index.html

  2. You will need a BD dive paired to your Slim/Pro console, or an OG Phat model on 1.00-7.61 to run this exploit.

    Viktorious AIO Auto BD-JB ISO for 4.XX-7.61: https://github.com/Viktorious-x/ps5-bdjb-modified-ISOs/releases
    (Alternative: UMTX Kernel exploit 7.61 JAR loader by Hammer83: https://github.com/hammer-83/ps5-jar-loader/releases)

    Burn ISO to a blank BD-R or BD-RE, put it into your console, and click on the [DISC PLAYER] icon.
    Highlight [PIPELINE RUNNER] then click option 2 [Normaljailbreak-etaHEN-UMTX1.pipe] to auto load etaHEN ready for ItemzFlow.
    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].
    ELF Loader will be running on your PS5 IP: port 9021


  3. Important:
    Up to 10.01 has a kernel exploit + HEN
    11.XX-12.70 has a kernel exploit but no HEN yet.
    LUA entry point works on the latest OFW, but there is no kernel or HEN 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)

  4. PS2 Classics > Userland via CTurt:
    (Implementation by McCaulay)
    Note: this is currently limited to swapping the loaded PS2 iso, or loading PS2 elf homebrew on PS5 (or PS4) for emulators or basic PS2 brew.

    Mast1c0re PS2 exploit for PS2 homebrew:
    https://cturt.github.io/mast1c0re.html

    Mast1c0re part 2:
    https://cturt.github.io/mast1c0re-2.html

    Mast1c0re payload framework:
    https://github.com/McCaulay/mast1c0re

    Okrager save game exploit generator for Okage:
    https://github.com/McCaulay/okrager

    Mast1c0re payloader TCP Client GUI for PS5 6.50:
    https://github.com/Master-s/PS4-PS5-Mast1c0re-Payloader/releases

    TCP network ISO loader:
    https://github.com/McCaulay/mast1c0re-ps2-network-elf-loader/releases

    ExFat USB ISO loader:
    https://github.com/McCaulay/mast1c0re-ps2-usb-game-loader/releases

  5. coming soon

  6. coming soon

  7. coming soon

  8. coming soon

  9. This method modifies the BD-J stack to allows BDJB to be re-enabled on your higher firmware console up to 12.40.

    This requires your console to be hacked via another method first to gain access to alter the files.
    (For example 12.00 needs SWRR disc to hack it first)

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

    DO NOT REINSTALL FW, IT WILL WIPE THE PATCH AND LOSE BD-JB


Additional Information:


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


(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: PS5 FPKGs do not work. A hack for the A53 processor does not publicly exist to enable installing PS5 content as FPKG/PKG.

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

5: 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,
I hope I'm wrong, but I've been hearing about ps5 fpkgs "soon" since a year ago, when ze coxao tweeted that he was releasing fpkg games.
dpkg and fpkg are two different things... dpkg is a debug package and works on testkit/devkit only... fpkg should work on normal consoles too.

It's also normal that developers promise something and then nothing comes of it. It's also normal that they collect money from people for a testkit so they can have development, after a few months they sell the testkit (they keep the money) and then after some time they collect money again for a testkit/devkit so it can be development...and then it goes on and on again
Post automatically merged:

NO stay on 6.50. Flow said it would be supported for Linux. I was just pointing out it had less options then the lower firmware.
ok, I'll stay on 6.50. FW 6.xx brings native 1440p support, and 6.xx is also the last FW where it's not necessary to use dma writes. Of course it's good not to have to use backports, but we'll see how it goes in future... Worst case scenario, I can update later. Some alleged HV to 1-7.xx is supposedly on the table, but that's maybe fake info.
 
Last edited by Adam512,
I hope I'm wrong, but I've been hearing about ps5 fpkgs "soon" since a year ago, when ze coxao tweeted that he was releasing fpkg games.
This has been something quite long in the making for now, there's more reference to that than that ( all ever since A53/MP4 was compromised and dumped, or even before that, more than a year now ). Zecoxao has been in contact with the devs and maybe even helped directly or indirectly, so he probably said that when some advancement happened and, yeah, as excited as we all are, I don't see anything wrong with that and I wouldn't blame him. There has probably been "a few" difficulties to overcome and they have decided to work on it before some of those difficulties have been taken care of... it may even be the case some of the issues could put the PS5 at risk ( probably fixable by factory resets or database rebuilding and such, but still a potential fuckup of losing save games and so on ).

https://github.com/cragson/a53-code-exec


EDIT: It may as well be that, having compromised A53 and having dumps of the fw part running in A53 until a given PS5 fw version, they were looking for a way to have future A53 access ( on future PS5 fw versions ), otherwise they could be bringing us FPKG support that would only support FPKGs up until some PS5 fw version. I don't know, it just seems very plausible to me...
 
Last edited by Inaki,
For me what's important is the speed of loading games and to make sure there is no stuttering in game play. Black Myth is shocking for in game stuttering transitions.. I would rather keep a large game dump than have a compressed one with long loading times and the afore mentioned stuttering...
 
I hope I'm wrong, but I've been hearing about ps5 fpkgs "soon" since a year ago, when ze coxao tweeted that he was releasing fpkg games.
I think he got it wrong. DPKG only work on devkit/testkit.

The new announce is by someone else, Jordy, who is trust worthy and was responsible in part for the recent HV releases.
 
For me what's important is the speed of loading games and to make sure there is no stuttering in game play. Black Myth is shocking for in game stuttering transitions.. I would rather keep a large game dump than have a compressed one with long loading times and the afore mentioned stuttering...
I have not converted Wukong (yet). The Deluxe edition is around 170GB.

I have tested 7 .ffpfsc games now and they are working the same as my .exfat games. No extra loading times, no freezes and / or stutters. The average framerate - measured via PHU - is around 50~60fps. It might on the game itself and what you are loading it with.

I will convert more today and test them to see if I notice any differences.
 
Bugfixes

ps5debug-NG v1.2.7​

  • 🐛 Fixed a critical bug - console crash (KP) when rescanning with "between".

Notes​

  • No other changes from v1.2.6 revision1 (which added the FW 8.40+ poke/breakpoint fix).
Link: https://github.com/OpenSourcereR-dev/ps5debug-NG/releases/tag/1.2.7
Hey, are you the author of that tool ? I am quite a bit into debuggers myself and have an ongoing project ( ) for a modern day SoftICE-like debugger ( for UEFI and Windows for now, you debug the machine using the display and keyboard+mouse on the same machine itself, you freeze and enter de debugger via a key combo or when a breakpoint occurs and so on ) and I have been thinking on the possibility of reusing some of my code for PS5... maybe... btw, I also use Zydis on my debugger. I have been thinking on maybe starting with an "all time running" module, not necessarily a debugger, but a tool that would have a raw display UI and you would be able to view&edit stuff on the fly on the PS5 itself ( either via a keyboard or the controller... ).
 
Hey, are you the author of that tool?
No I am not. I'm mainly a tester not a dev. I've talked to Pharaoh2k in this case.
Post automatically merged:

I have been thinking on maybe starting with an "all time running" module, not necessarily a debugger, but a tool that would have a raw display UI and you would be able to view&edit stuff on the fly on the PS5 itself ( either via a keyboard or the controller... ).
Well if you want to kickstart something or do a collaboration you can always check the authors that created that debug tool.
The credits are always displayed on the Github page.
 
Last edited by HS2005,
  • Like
Reactions: schatzi24 and Inaki
Hi guys,
maybe someone can help me with my problem.
My PS5 pro with drive works like a charm on fw 12.0 with BDUB Disc. I shutdown the console yesterday and when i start some minutes ago, i get this error message.

I have already tried to clear the cache, rebuild database and reinstall same 12.0 official firmware. Error occurs again.

If i reset my console, the pairing of my drive and console will lose, right? I can still select all points in the safe mode.

Any hint here?

Thanks in advance
Chris
I've been seeing reports for a while now of people having to factory reset their Slim and Pro PS5s, and honestly I've been worried about ending up in the same situation with my Slim on 11.40. Mine is factory-paired (which is supposedly less prone to losing BD drive pairing), but after jailbreaking it I backed up pairing keys and decided not to jailbreak it again until there's a way to restore pairing, especially since I already have other jailbroken PS5s.

In your case, I think you have two equally valid options:

1. Factory reset your Pro and keep it digital on 12.00

Pros:

  • A public jailbreak is already available (P2JB + Y2JB), even though it takes ~50 min. No need to wait for a new jailbreak.
  • You keep access to the YouTube (Y2JB) and Netflix-n-hack userland exploits when restoring backups.
  • If a less restrictive kernel exploit gets released in a couple of months, it'll likely be compatible with Y2JB.
  • Peace of mind knowing you won't have to worry about losing BD pairing again.
Cons:


2. Factory reset and update to 13.20 to pair the disc drive again

Pros:

  • You get access to your disc drive back.
  • If the rumors are true and you do it before a new firmware is released you'll already be on a firmware that's compatible with the currently private kernel exploit and the WIP Webkit exploit if and when they become public.
Cons:
  • You essentially lose access to the YouTube and Netflix userland exploits (up to fw 12.40 without licenses).
  • You won't be able to jailbreak your PS5 Pro until a new exploit chain is released for 13.20.
  • You're relying on those private exploits being viable and eventually getting released.
  • There's always a chance you could lose disc drive pairing again if something similar happens in the future.
 
Last edited by madbrainx,
  • Like
Reactions: schatzi24
Hi guys,
maybe someone can help me with my problem.
My PS5 pro with drive works like a charm on fw 12.0 with BDUB Disc. I shutdown the console yesterday and when i start some minutes ago, i get this error message.

I have already tried to clear the cache, rebuild database and reinstall same 12.0 official firmware. Error occurs again.

If i reset my console, the pairing of my drive and console will lose, right? I can still select all points in the safe mode.

Any hint here?

Thanks in advance
Chris
Edit:
I've read it all now, you don't have the option to create a new profile and you only have the options in the menu that you tried... as the person above wrote, you have advantages and disadvantages here, but I think it's good to be on 12.00 because you can always install Y2JB in any case... after webkit appears, you can turn on poop on 12.00(fast exploit, so no need bdj) I would stay on 12.00.

on the other hand ps5 fw13 has some improvements for ps5 pro and in the future they might wake up new improvementsw... you will wait a long time but you will definitely get the kernel exploit for 13.20 and you will also have a paired bd. you can even install swrr which has JIT

What did you do to get into this state?
 
Last edited by Adam512,
Hi guys,
maybe someone can help me with my problem.
My PS5 pro with drive works like a charm on fw 12.0 with BDUB Disc. I shutdown the console yesterday and when i start some minutes ago, i get this error message.

I have already tried to clear the cache, rebuild database and reinstall same 12.0 official firmware. Error occurs again.

If i reset my console, the pairing of my drive and console will lose, right? I can still select all points in the safe mode.

Any hint here?

Thanks in advance
Chris
stay at 12.00 and use as a digital ps5 pro

Then buy another PS5 Pro without a drive, put the old drive in the new console and update + paire drive. It's easy
 
about this: https://github.com/Rufidj/Nativehbl

I was messing around and the information is not clear.
For example, how to run again the UI?

The idea of that payload is very good, but other than the required information, it needs more things to do.

About other solutions around, like Elf arsenal and similar stuff. For me all that is horrible. I don't want to have EVERYTHING running in the background.
 
Ive got many Elf in data id likes to clean to bring PS5 without kp or restart could can delete all folder and file Inside data.

Id likes 1 autoloader any advise on the MOST complete if possibile Easy.
Im on 11.20 db patched
Thanks
 
So I made some progress regarding various .exfat conversions.

All games are working properly.

I made some screenshots for you to see what you can achieve in regards to decreasing the file size.

The First Berserker: Khazan

khazan.jpg


Wuchang Fallen Feathers

Wuchang-1.jpg


Dragon Ball: Sparking! Zero

dbz.jpg


Clair Obscur: Expedition 33

33.jpg


Resident Evil 9: Requiem

re9.jpg


Pragmata

Pragmata.jpg


Crimson Desert

Crimson Desert.jpg


Black Myth: Wukong

Wukong.jpg


MGS Delta

MGS Delta.jpg


Post automatically merged:

Autoloader: P2JB v2.6 (Obsession with version number)​

Pre-release

Unnecessary Update:
I was gonna explain why it's unnecessary. But I guess you guys who ask for p2jb v2.6 wouldn't read anyway. So here's what the original owner of p2jb.js said.

ScreenShot_2026-05-29_092546_167

And for those who read this, I suggest to choose last release. Because there's no useless functions for compatibilities in it. You might get worse experience with this release version for p2jb v2.6.

But in the end, choose the stable one for you. If it's already stable for what you have been using, no need to switch to another. It's not worth wasting 50 minutes for unknown results.

Changelog:
P2JB.js upgraded to v2.6.

(Warning: restoring a backup would purge all user data.)

Thanks to all the creators of these masterpieces. Credits

Disclaimer:
This tool is provided as-is for research and development purposes only.
Use at your own risk.
The developers are not responsible for any damage, data loss, or other consequences resulting from the use of this software

Link: https://github.com/owendswang/Y2JB-P2JB-bdj_unpatch/releases/tag/v1.3d-autoloader
 
Last edited by HS2005,
I hope I'm wrong, but I've been hearing about ps5 fpkgs "soon" since a year ago, when ze coxao tweeted that he was releasing fpkg games.
Exactly what I posted previously:
Is this "Jordy" a reliable source? Anyways, still not keeping my hopes up.
Just like how Zeco teased flatz's HEN and that was like a year ago, and.......nothing.
Post automatically merged:

if the fpkg is really near, that apr emu will be obsolete before to born...
Plottwist: apr emu was secretly fpkg all along!
emojis.png
 
So I made some progress regarding various .exfat conversions.

All games are working properly.

I made some screenshots for you to see what you can achieve in regards to decreasing the file size.

The First Berserker: Khazan

View attachment 576353

Wuchang Fallen Feathers

View attachment 576355

Dragon Ball: Sparking! Zero

View attachment 576356

Clair Obscur: Expedition 33

View attachment 576359

Resident Evil 9: Requiem

View attachment 576360

Pragmata

View attachment 576361

Crimson Desert

View attachment 576362

Black Myth: Wukong

View attachment 576363

MGS Delta

View attachment 576368

Post automatically merged:

Autoloader: P2JB v2.6 (Obsession with version number)​

Pre-release

Unnecessary Update:
I was gonna explain why it's unnecessary. But I guess you guys who ask for p2jb v2.6 wouldn't read anyway. So here's what the original owner of p2jb.js said.

ScreenShot_2026-05-29_092546_167

And for those who read this, I suggest to choose last release. Because there's no useless functions for compatibilities in it. You might get worse experience with this release version for p2jb v2.6.

But in the end, choose the stable one for you. If it's already stable for what you have been using, no need to switch to another. It's not worth wasting 50 minutes for unknown results.

Changelog:
P2JB.js upgraded to v2.6.

(Warning: restoring a backup would purge all user data.)

Thanks to all the creators of these masterpieces. Credits

Disclaimer:
This tool is provided as-is for research and development purposes only.
Use at your own risk.
The developers are not responsible for any damage, data loss, or other consequences resulting from the use of this software

Link: https://github.com/owendswang/Y2JB-P2JB-bdj_unpatch/releases/tag/v1.3d-autoloader
Did you convert first to ffpfs and THEN compress or did you go straight to compression from exfat?
 
Exactly what I posted previously:

Post automatically merged:


Plottwist: apr emu was secretly fpkg all along! View attachment 576366
Fpkg installing with debug menu to internal / m2 or usb, right?

I hope fpkg won't be a joke like CFW on PS4... which then turned out to be mira

I heard before that fpkg would come later with PS6, so why did they decide to rush it? I think there are a lot of games on the scene and trophies are also working now.
 
  • Haha
Reactions: FateNightroad

Site & Scene News

Popular threads in this forum