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,
Hi everyone, I have a PS5 with a Blu-ray drive, running 7.61 with an internal M2. Y2JB runs really smoothly and without any error messages. I used the Y2JB-upload.zip from thomas-hcb v1.1.0 because of the internal M2. My autoload is set up like this: etaHEN-2.5bin, !4000, Backpork.elf, !1000, Shadowmount.elf, !4000, kill_youtube.elf. It works without KPs; 2 out of 10 times I just have to restart the PS5 if it doesn’t work right away.

Now I’ve also gotten a PS5 Pro with 9.60 without a Blu-ray drive. This one also has an internal M2, and I’ve set it up just like my 7.61. However, after running it, I sometimes get KPs, or if it worked, a system error CE-108262-9 is displayed. I can dismiss the system software errors and then restart normally via itemzflow and etaHEN. I’ve also used the itsPLK v.04 version, but it’s worse with that version. I’ve also tried different autoload sequences and timings, the latest etaHEN and Kstuff Lite—none of that helped. I’ve read that this problem is likely due to the internal M2. Without the internal M2, Y2TB actually works fine. Do you have any ideas on how I can get the PS5 Pro with the internal M2 to run without these system software errors? Is it due to firmware 9.60?

Thank you in advance for your support.
 
My Dear Friends of xp**itati*ns :)
Unfortunately I won't come further with J*jb a PS5 FW11.60. Tried the Backup Restore v1.3 and then wanted to send a Pl getting the elf-Loader running. Listening on port 50000 and local IP-address is fine... But sending the Pl is refused at the PS5...
Might it be that this doesn't work because of the FW and I need to go with N-H* or what I am missing here? :)
Hope someone is so kind and give me a hint what I can try.
Best wishes, Leo
 
Do you have any ideas on how I can get the PS5 Pro with the internal M2 to run without these system software errors? Is it due to firmware 9.60?

Thank you in advance for your support.
What I am missing here? :)
Hope someone is so kind and give me a hint what I can try.
Best wishes, Leo
there are several options.

The first and easiest is to improve Y2JB (github), as we all know Gezine gave up on Y2JB and now he only focuses on star wars.you can try writing to him to improve it or to other devs

The second method is that you ask theFlow to send you CFW in which HV is disabled and then you install this FW. This FW also has an older version of webkit from FW 5.xx

The third option is that you create this CFW yourself but no one will tell you how to do it, you have to figure it out yourself.
 
  • Like
Reactions: django090
Thanks for clarifying David6 :)
psdevwiki.com/ps5/Serial_Number_guide
pointed until 12.00, but first post of this thread states until 10.01. Then I am w8tin' :)
only digital, wo drive
Best wishes, Leo
 
You mean even if the drive is paired I could not play burned Blu-ray games ?
blue ray discs contain protection that cannot be copied by regular blue ray burning, so you cannot play burned games. But you can buy an original disc or search the internet for keys leak for ps5
 
  • Like
Reactions: Derherrbios
Sine you've put it down in writing like that it's definetly msde me think twice if not three or four times and i've not even had a single malt tonight either.... Just a stella ;):)
Yeah didn't mean to put you off mate, I just know it can be a nightmare at times, especially with our glorious rules and whatnot. Best be safe and all that. I've had to start recording myself opening any package because people send me broken shit or stuff that isn't remotely what I paid for or what was advertised, then accused me of damage etc. I had to buy a damn phone mount and everything cos I've only got 2 hands innit, bloody rip off!

I'd also just finished watching a GamersNexus video when I saw your message, it was about some guy getting in shit from Sega for buying parts from a scrapyard, and he got arrested and all kinds of shit. Should check it out if you're interested.

It would be a nice thing to do but yeah, for many reasons we can't have nice things in our wonderful little land...shame... (insert Hot Fuzz meme here, I can't cos Imgur is fucking blocked!!!)
 

SNESC0RE​

SNESC0RE is based on the EMUC0RE NES emulator by EGYDEVTEAM / egycnq, and its usage is basically identical. I'm very happy to be able to contribute in some way to the scene, and I truly hope you enjoy it :) I'm also open to bug reports, feedback, and possible improvements.

Requirements​

  • PS5 console (any firmware, tested up to 13.00)
  • LuaC0re set up and working
  • Star Wars Racer Revenge - US (CUSA03474) or EU (CUSA03492)
  • If you're on latest FW you can grab the digital version from the PS Store
  • Python 3 on your PC
  • PC and PS5 on the same network

Link: https://github.com/BrinooTk/SnesC0re/releases/tag/SnesC0re
 
Also does voidshell have a timed license like the etahen beta builds?

I've just tried launching my alternate payloads, including voidshell, and I get a debug error saying license invalid or tampered with. I switch backed to standard etahen2.5B just in case it was the beta build from that, but it's still happening.

etahen works, but voidshell doesn't. I'm using the same elf as I've always used from the 2.0 beta.

Ed: It's definitely voidshell, just ran it again on it's own and it says "license invalid or system tampered"
 
  • Like
Reactions: solitaire4eva
Also does voidshell have a timed license like the etahen beta builds?

I've just tried launching my alternate payloads, including voidshell, and I get a debug error saying license invalid or tampered with. I switch backed to standard etahen2.5B just in case it was the beta build from that, but it's still happening.

etahen works, but voidshell doesn't. I'm using the same elf as I've always used from the 2.0 beta.

Ed: It's definitely voidshell, just ran it again on it's own and it says "license invalid or system tampered"

Voidwhisper updated VoidShell 2.0 to work until 30th April 2026, meanwhile he is working on VoidShell 3.0.
Support him if you want. I did: https://ko-fi.com/s/99aac5c463
 
Please think again, he is modifying a console to bypass security measures.
And i mentioned copied games right?
Which is absolutely illegal to sell!
And even if he installs from disk, modifying the ps5 will make the User able to even use that installed game even if he has no licence or disk!
I wouldnt risk that, lawyers are like blood hounds.
And selling my legit unhacked ps5, Profile removed, but game files still installed is surely no problem, because buyer will have no access to the games aka i didnt make it possible to do so. This is total different story and cant be compared to preparing a console for Bypass security measures. Thats the point that matters.
And why even install swrr, this is bdj unlock service, so the User can use bdj exploit.
If User had the swrr disk, wouldn't even send it in.
Also just google what happened to many switch modders that sold modified consoles.
Different countrys will have different copyright laws.
Just be careful, read into it for uk and dont install unnecessary stuff which can be trouble. Thats what i wanted to say, nothing more, nothing less.
You're thinking too much, bud.

My point is, there is nothing wrong with leaving the game installed whether is intentionally and unintentionally. There is nothing unlawful about it. lol

The patched .jar file must be left in the console otherwise there is no service to be done, the game files and save games, are worthless without the original disc.

The shellcode in the savegame, the patch and the use of the game is a more nuanced than just "bypass security measures", I don't think none of us are equipped to argue the legality of it.
Post automatically merged:

Astro Bot has the latest update 1.018... other games have some updates too

----

@BobaFett_UK
How about renting the game SWRR? That would be easier with the transfer.. Of course, the buyer would have to sign a contract remotely that in case of not returning it within a certain period, the deposit will not be refunded or something like that...

Example: You rent a game for 200 euros for 7 days, the period will start counting from the day of collection at the post office and if it is not sent back after 7 days, the fees will be deducted from the prepaid deposit... The deposit will be, for example, 2000 euros, which the buyer must pay in advance along with the price of the loan (i.e. 2000+200). For every single day of delay, there will be a minus of 100 euros.

Simple, right? There are definitely people who would pay this amount and you also have insurance in case they don't want to return the game. If the customer returns the game on time, you will send them back the full deposit (2000) and you will only keep the rental price, which in this theoretical case is only 200 euros.
I thought on something like that, but there is always the concern of someone maliciously keeping the game, while lets say 200 euros is too high of a price for the game, someone may keep it, re-sell it or even offer paid services with it.
 
  • Like
Reactions: schatzi24
What i mean is not copy the original but burn a dump from like duplex to the disc , would that work?
Now that's a lot of wear and tear on your PS5 laser! Also largest blank disc is around 128GB. You ain't playing no Astrobot from no burnt disc!
 
Last edited by solitaire4eva,
  • Haha
Reactions: iguanoPT
For those who want or are using Linux:

PS4 Linux Loader v24b​

Whats new​

Fixed small bug that detects the firmware version for sub 10.71

The rest from v24:​

  • No more per firmware payloads. Its all in one, aka firmware agnostic Linux payload. Thanks to @rmuxnet
  • Introducing runtime Southbridge and PS4 PRO detection, no more separate PRO or Baikal payloads.
  • Completed PS4 7.xx and 8.xx support.
  • scans for the files in /user/system/boot/ if they weren't found in the default path /data/linux/boot/
  • low vram payloads. great for repurposing the PS4 as a server. lowest supported payload is 32mb.

Supported firmware list​

Code:
FW 5.05 ✅
FW 6.72 ✅
FW 7.00 / 7.01 / 7.02 ✅
FW 7.50 / 7.51 / 7.55 ✅
FW 8.00 / 8.01 / 8.03 ✅
FW 8.50 / 8.52 ✅
FW 9.00 ✅
FW 9.03 / 9.04 ✅
FW 9.50 / 9.51 / 9.60 ✅
FW 10.00 / 10.01 ✅
FW 10.50 / 10.70 / 10.71 ✅
FW 11.00 ✅
FW 11.02 ✅
FW 11.50 / 11.52 ✅
FW 12.00 / 12.02 ✅
FW 12.50 / 12.52 ✅
FW 13.00 ✅
FW 13.02(?)

What's Changed​

  • feat: unified AIO payload architecture and kexec deduplication by @rmuxnet in #4
Full Changelog: v23...v24b

Link: https://github.com/ArabPixel/ps4-linux-payloads/releases/tag/v24b

My heart almost stopped looking at this firmware list. Turns out it's PS4 not PS5. Dunno why it's posted.
 
My heart almost stopped looking at this firmware list. Turns out it's PS5
Yeah I opened the wrong thread. Asked the staff to move my post. I was busy writing 2 posts at the same time.
Post automatically merged:

Regarding my previous post: https://gbatemp.net/threads/ps5-exploit-guide.613891/post-10841106

Holding everything

PS5 MIGHT BOOT INTO SAFE MODE AFTER KERNEL PANIC.** Use at your own risk!!!
I'm seeing multiple guys got system corruption after kernel panic at different moment after jailbreak, not only from BD-UN-JB. You'll have to reinstall firmware when PS5 can only boot into safe mode. It would lose the bdj-unpatch. It would lose disc drive pairing for Slim and Pro models.

It feels everything is still in early stage. So I'm putting everything as pre-releases. I'll put it to general release when I don't see safe mode after kernel panic. I suggest to wait for etaHEN release for now. And I won't update this ISO image until then.

Changelog:
Code:
!5000
ftpsrv-ps5-0.18.3.elf
!1000
shadowmountplus-1.6test7-fix2.elf
!3000
kstuff-lite-1.03.elf

'ps5_autoloader' folder loading priority:
/data/ps5_autoloader -> /mnt/USB?/ps5_autoloader -> /mnt/disc/ps5_autoloader.

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/BD-UN-JB-Poops-Autoloader/releases

I did a couple of tests and had no issues / kp's etc. The disc loads faster than Y2JB in my case. Your situation may differ.
 
Last edited by HS2005,
Yeah I opened the wrong thread. Asked the staff to move my post. I was busy writing 2 posts at the same time.
Post automatically merged:

Regarding my previous post: https://gbatemp.net/threads/ps5-exploit-guide.613891/post-10841106

Holding everything

PS5 MIGHT BOOT INTO SAFE MODE AFTER KERNEL PANIC.** Use at your own risk!!!
I'm seeing multiple guys got system corruption after kernel panic at different moment after jailbreak, not only from BD-UN-JB. You'll have to reinstall firmware when PS5 can only boot into safe mode. It would lose the bdj-unpatch. It would lose disc drive pairing for Slim and Pro models.

It feels everything is still in early stage. So I'm putting everything as pre-releases. I'll put it to general release when I don't see safe mode after kernel panic. I suggest to wait for etaHEN release for now. And I won't update this ISO image until then.

Changelog:
Code:
!5000
ftpsrv-ps5-0.18.3.elf
!1000
shadowmountplus-1.6test7-fix2.elf
!3000
kstuff-lite-1.03.elf

'ps5_autoloader' folder loading priority:
/data/ps5_autoloader -> /mnt/USB?/ps5_autoloader -> /mnt/disc/ps5_autoloader.

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/BD-UN-JB-Poops-Autoloader/releases

I did a couple of tests and had no issues / kp's etc. The disc loads faster than Y2JB in my case. Your situation may differ.
If i am understanding correctly this seems like is caused by the autoloader via BR JB disc rather than the POOPS exploit itself.
Post automatically merged:

Although it days "not only from BD-UN-JB" so it may originate from the BR-JB .jar patching?
 
If i am understanding correctly this seems like is caused by the autoloader via BR JB disc rather than the POOPS exploit itself.
Post automatically merged:

Although it days "not only from BD-UN-JB" so it may originate from the BR-JB .jar patching?
I have faith that it'll be sorted. It seems like they know what the problem is, it's just a matter of testing it and making sure it's working.
 

Site & Scene News

Popular threads in this forum