Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


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

6.XX = KEX: PS4/5 backups (KEX+HV+Linux: 6.02 max) (WK/BD/Y2/NF/LUA/YARPE: 6.02 for Linux / 6.50 max)
7.XX = KEX: PS4/5 backups (KEX+HV+Linux: 7.61) (
WK/BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = KEX: PS4/5 backups, no HV (WK/BD/Y2/NF/LUA/YARPE)
10.01-12.70 = KEX: PS4/5 backups, no HV (
WK/BD/Y2/NF/LUA/YARPE)
13.XX = HV+KEX+WK SOON! (WK/BD (13.42)/Y2/LUA/YARPE)
14.XX = No KEX/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: Do not update past 12.00. P2JB can take over an hour to exploit on FW up to 12.70.


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


Kernel (KEX):
Highest released KEX:
12.70 (P2JB)
Highest unreleased KEX: 13.60 (SlopSploit SOON)
UMTX2:
1.00-7.61 (*WK to 5.50 / BDJB to 7.61)
Lapse: 1.00-10.01
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):
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)
Webkit: 1.00-5.50 (PSFREE +UMTX2: 5.50 / SlopKit 7.00-13.60 (P2JB: 12.70) / (Slopsploit: 13.60)
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 - coming soon)

NOTE 1: A userland entry point (UL) chained to kernel exploit (KEX) is required to exploit your console.
NOTE 2: Digital consoles can now use Y2JB+Poops (4.03-12.00) / Y2JB+P2JB (9.00-12.70).
NOTE 3: All consoles will be able to use SlopKit (webkit), SplopSploit (KEX) and SlopVisor (HV) for firmwares up to 13.60 SOON.


Useful Applications:
FPKG: 3.00-12.70 / 13.60 SOON
Kstuff Lite: 3.00-12.70
HERE
Kstuff Toggle: 3.00-12.00 HERE
PS5 App Dumper: 3.00-12.00 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-7.61, Slim: 7.61) 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: 14.00 (16/9/26)
Summarised OFW/Model guide: HERE
1.XX-7.61 compatibility list:
HERE
PS5 SDK Repo: HERE
Legit PKG Updates: HERE or HERE
OFW Updates: HERE (history HERE)

Preparing Your Console:


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


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

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

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

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

21.02-04.03.00.00-00.00.00.0.1

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

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

WARNING:

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

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

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

Select Your Jailbreak:


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


  1. Information:
    Firmware 1.00-5.50 or 7.00-12.70 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-8.60:

    https://soniciso1.github.io/pooP2JB/

    Exploiting 7.00-12.00:

    https://jordyidk.github.io/slopkit/

    https://zecoxao.github.io/slopkit2/

    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.30-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


(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,
The thing is, the third person didn't do anything. Jordy just got it in his head that if someone else found it, more people would, so he cashed out. There was no dialogue or attempt made like TheFlow did to preserve the HV exploit, he just cashed his chips in and thought only of himself.

This is why that fucking bug bounty system was introduced in the first place. Until now, the difficulty level was such that professionalism ruled among the legitimate security experts despite the monetary incentives. Now that these undisciplined people are coming in, the fragile peace has been shattered. Sony bet peoples' selfishness would eventually pay off big time and the tree is now bearing fruit.
Fucking bingo.

Probably unpopular to say this, but Flow, for as godly as he is with his knowledge, is doing entirely too much. He's talking out of both sides of his mouth. He says he's vehemently against dumping and piracy (at least for as long as I've seen him post publicly, even going back to the PS4 days), yet he said he wanted to wait to disclose it so that people could "people would have the opportunity to legally purchase the game and also enjoy Linux"? I don't think that really makes sense. He frames it like it's about Linux, when in reality it is obviously implied that it's about dumping GTA, imo. Obviously, it doesn't literally say that and that's my assumption, though.
What!? It DOES make sense. If someone wants and is purchasing the game, they would have both. Now their choices are keep your console on an older firmware to have access to Linux and buy a new one for GTA 6 OR update your console to play GTA 6 and miss out on Linux. I don't think is that complicated. The real question is, why are you talking about piracy or implying piracy?
 
New update for web file manager https://github.com/owendswang/ps5-web-file-manager/releases
ELF sending support & draging in to upload for PC web browser Latest


@owendswang
owendswang released this yesterday
v1.9
e64fb6f
Change log:

  • Clicking on an ELF file to send it to port 9021 of elfldr.
  • Able to drag and drop files or directories to upload from PC web browser.
  • wfm-7zip-helper.elf got updated with smaller size of ELF file, version 26.03-1.
 
Thank you for saving me time 🤣 I converted it too via 0.6.8 but didn’t install it yet.

If that game + dlc works then everything works lol
To be sure, the version that doesn't ship with DLC works as an FPKG. It's the version that tries to include the DLC that faceplants. (And be sure to remove ampr_emu before packaging it)
 
So maybe THAT is what we are waiting on: for the hypervisor to be patched. So, at least SOME good news that it hasn't been patched on 14.00 which is supposed to be where you need the HV to dump games.
So FW 14.00 will be new "golden FW" that includes HV?

Has anyone tested WebKit on 14.00?

-----------


In any case, it will always depend on a few people whether they perform a dump using their private methods and make it available to the community, which could theoretically create a backport... So, it’s not about when Sony fixes something, but rather whether certain individuals or groups are willing to share result(dump game)

Works without dlc 👍 via older buider
Post automatically merged:

Dead space remake works too 👍
How did you manage to get it working? Using that new tool?

I have a 512GB NVMe drive(speed 2000-3000) in USB enclosure, and I'm wondering whether to keep it there or install it in the console's M.2 slot. I'm a bit concerned about cooling, though I do have the thermal pad that came with usb enclosure (I'm not sure if that will be enough).

PS5 (original model with disc drive), firmware 6.50
 
Last edited by Adam512,
Another update from Drakmor. See changes below:

View attachment 591101

Link: https://gofile.io/d/rPOuYuQR

So FW 14.00 will be new "golden FW" that includes HV?

Has anyone tested WebKit on 14.00?

-----------


In any case, it will always depend on a few people whether they perform a dump using their private methods and make it available to the community, which could theoretically create a backport... So, it’s not about when Sony fixes something, but rather whether certain individuals or groups are willing to share result(dump game)


How did you manage to get it working? Using that new tool?

I have a 512GB NVMe drive in USB enclosure, and I'm wondering whether to keep it there or install it in the console's M.2 slot. I'm a bit concerned about cooling, though I do have the thermal pad that came with the enclosure (I'm not sure if that will be enough).

PS5 (original model with disc drive), firmware 6.50
the game without dlc always works fine I can send you a link if you want
 
Here is my humble opinion on firmware versions; naturally, this could change at any time.

FW 1.xx–3.xx: Stay here because of a rumored "keys exploit."

FW 4.xx–11.40: All firmwares in this range can theoretically update to 11.40, as it supports everything—webkit, HV, BD-J, y2jb—and also supports the current fpkg method that doesn't require HV. The only thing it definitely lacks right now is "redis" (which is only up to 7.61 and is supposedly for autobooting... though some people might not consider that essential.

FW 11.60–13.42/13.60: In this range, users could update to 13.42 or 13.60. The difference is that BD-J support currently only goes up to 13.42, so 13.60 doesn't support BD-J userland at the moment. They supposedly have webkit, y2jb, and HV, but still lack redis. Unfortunately, the fpkg method without HV doesn't work here. Of course, not everything has been implemented for 13.xx yet, but it just takes a little time for the developers.

Of course, a keys exploit for FW 1.xx–7.xx could be released tomorrow, so it is always better to stay on the lowest fw version possible.

Do you agree, or do you have a different opinion on the firmware ranges I mentioned? Please share your thoughts.
 
Here is my humble opinion on firmware versions; naturally, this could change at any time.


FW 11.60–13.42/13.60: In this range, users could update to 13.42 or
I would stop at 11.60 and start a new range 11.60-12.20 because they still have access to poopsploit and don't need to fuck with that 45 minute P2JB. Yeah they don't have as many options as the lower one but until a new JB comes out, those 12xxx have to continue to feel the pressure of waiting 45 minutes and don't need to be included among the lower firmware users.

P.S. until something is out for the public, it does not exist. Example GTA6 is a trailer and nothing more right now, it doesn't exist in this reality.

Correction Poopsploit only supported to 12.00 firmware. Thanks ThePSGuy

 
Last edited by solitaire4eva,
I’ve included new kernel exploit in 11.60–13.60 category, since exploit was reportedly patched in version 14.00; unlike with P2JB, this new kernel exploit doesn't require a long wait.

Of course, a new HV exploit hasn't been released yet, so Linux support is currently limited to firmware 7.61... but all indications suggest there’s nothing stopping it from coming to firmware 13.60 in the future.

That range takes near future into account; for now, it is obviously better to avoid P2JB if possible :)
 
  • Love
Reactions: solitaire4eva
Here is my humble opinion on firmware versions; naturally, this could change at any time.

FW 1.xx–3.xx: Stay here because of a rumored "keys exploit."

FW 4.xx–11.40: All firmwares in this range can theoretically update to 11.40, as it supports everything—webkit, HV, BD-J, y2jb—and also supports the current fpkg method that doesn't require HV. The only thing it definitely lacks right now is "redis" (which is only up to 7.61 and is supposedly for autobooting... though some people might not consider that essential.

FW 11.60–13.42/13.60: In this range, users could update to 13.42 or 13.60. The difference is that BD-J support currently only goes up to 13.42, so 13.60 doesn't support BD-J userland at the moment. They supposedly have webkit, y2jb, and HV, but still lack redis. Unfortunately, the fpkg method without HV doesn't work here. Of course, not everything has been implemented for 13.xx yet, but it just takes a little time for the developers.

Of course, a keys exploit for FW 1.xx–7.xx could be released tomorrow, so it is always better to stay on the lowest fw version possible.

Do you agree, or do you have a different opinion on the firmware ranges I mentioned? Please share your thoughts.
Well, I'd extend that to 14.00 ( and potentially 14.0x... ):

The thing is Sonic-Iso says 14.00 hypervisor exploit is still there, not patched. But he also says kernel exploit has been patched... there's some corner case possibilities ( the hypervisor exploit being directly accessible from user mode... veery unlikely ) but very probably this means:

How do they know the hypervisor exploit is still there if the kernel mode exploit is patched ? this would be because they have other entry-point and kernel exploits that allows them to jailbreak 14.00 and test if the hypervisor exploit works. So, they saw that the public kernel exploit doesn't work, but by using other private exploits they have they managed to get in and from there, from the basic jailbreak state, they tested the hypervisor exploit and they found it remains unpatched.

So, this would mean 14.00 is compromised to the same extent as 13.60, except the user and kernel exploits are private for now, while the hypervisor exploit is the same for both 13.60 and 14.00. Good news, I suppose, but be careful not to jump to conclusions: GTA6 might require the absolute latest firmware when it launches. Since it's digital and requires PSN, they could release GTA6 requiring, say, 14.0x ( where x > 0 ) and, days before GTA6, release a firmware update to that 14.0x, a firmware that patches the hypervisor exploit we have... *However*, as long as those private user and kernel exploits -not the ones we have for 13.60, but the private ones the devs have- remain unknown to the public, those devs would still have a basic jailbreak when GTA6 and that 14.0x firmware arrive. The question is whether they'll be able to dump GTA6 using that basic jailbreak without hypervisor access. It seems Sony has made changes to prevent games from being dumped without hypervisor access ( I can imagine methods like encrypted code snippets sent to the hypervisor to be decrypted and executed there, code that does vital things for the game's logic... ).

My guess: using those basic jailbreak exploits -without the hypervisor exploit and access- they might manage to dump GTA6... but this time I’m leaning toward something more extreme, looking at teams like DUPLEX or others and maybe using new means of dumping ( and decrypting ) games... don't forget/underestimate those teams...
 
Here is my humble opinion on firmware versions; naturally, this could change at any time.

FW 1.xx–3.xx: Stay here because of a rumored "keys exploit."

FW 4.xx–11.40: All firmwares in this range can theoretically update to 11.40, as it supports everything—webkit, HV, BD-J, y2jb—and also supports the current fpkg method that doesn't require HV. The only thing it definitely lacks right now is "redis" (which is only up to 7.61 and is supposedly for autobooting... though some people might not consider that essential.

FW 11.60–13.42/13.60: In this range, users could update to 13.42 or 13.60. The difference is that BD-J support currently only goes up to 13.42, so 13.60 doesn't support BD-J userland at the moment. They supposedly have webkit, y2jb, and HV, but still lack redis. Unfortunately, the fpkg method without HV doesn't work here. Of course, not everything has been implemented for 13.xx yet, but it just takes a little time for the developers.

Of course, a keys exploit for FW 1.xx–7.xx could be released tomorrow, so it is always better to stay on the lowest fw version possible.

Do you agree, or do you have a different opinion on the firmware ranges I mentioned? Please share your thoughts.

I'm currently sitting on 4.50 casually playing in old games which came as fpkg for ps4. When 12.0 dropped my initial thought was to jump to 12.0 right away, even though redis looks cool but too few people are tested it so it has some problems and nobody seems to working on then atm. Then fpkg dropped and for whatever reason its not working past 11.40 smh. I would kick myself in the nuts if I've jumped to 12.0 already, so basically it's chill on 4.50 for me indefinitely until either community comes to an agreement for golden fw or when I would really have a reason to update to play something like gta6 on 13.60 with backport. But I've already skipped many major ps5 titles like that and won't be surprised if even gta6 wouldn't budge me into updating my good ol' fatty on 4.50
 
  • Like
Reactions: solitaire4eva
I would stop at 11.60 and start a new range 11.60-12.20 because they still have access to poopsploit and don't need to fuck with that 45 minute P2JB. Yeah they don't have as many options as the lower one but until a new JB comes out, those 12xxx have to continue to feel the pressure of waiting 45 minutes and don't need to be included among the lower firmware users.

P.S. until something is out for the public, it does not exist. Example GTA6 is a trailer and nothing more right now, it doesn't exist in this reality.
This, except the small mistake you made about 12.20 which doesn't support poopsploit (12.00 max). :)

But all and all, I would say there is no magic sheet to know what firmware you need to be on as the scene have been evolving rapidly these past weeks.

For example, 11.40 wasn't considered as "better" than 12.00 until a few days ago when FPKG finally got released.

The golden rule everyone should follow is just to stay where they are unless they absolutely need to upgrade for whatever reason (which in most case doesn't even exist to begin with).
 
  • Like
Reactions: solitaire4eva
Well, I'd extend that to 14.00 ( and potentially 14.0x... ):

The thing is Sonic-Iso says 14.00 hypervisor exploit is still there, not patched. But he also says kernel exploit has been patched... there's some corner case possibilities ( the hypervisor exploit being directly accessible from user mode... veery unlikely ) but very probably this means:

How do they know the hypervisor exploit is still there if the kernel mode exploit is patched ? this would be because they have other entry-point and kernel exploits that allows them to jailbreak 14.00 and test if the hypervisor exploit works. So, they saw that the public kernel exploit doesn't work, but by using other private exploits they have they managed to get in and from there, from the basic jailbreak state, they tested the hypervisor exploit and they found it remains unpatched.

So, this would mean 14.00 is compromised to the same extent as 13.60, except the user and kernel exploits are private for now, while the hypervisor exploit is the same for both 13.60 and 14.00. Good news, I suppose, but be careful not to jump to conclusions: GTA6 might require the absolute latest firmware when it launches. Since it's digital and requires PSN, they could release GTA6 requiring, say, 14.0x ( where x > 0 ) and, days before GTA6, release a firmware update to that 14.0x, a firmware that patches the hypervisor exploit we have... *However*, as long as those private user and kernel exploits -not the ones we have for 13.60, but the private ones the devs have- remain unknown to the public, those devs would still have a basic jailbreak when GTA6 and that 14.0x firmware arrive. The question is whether they'll be able to dump GTA6 using that basic jailbreak without hypervisor access. It seems Sony has made changes to prevent games from being dumped without hypervisor access ( I can imagine methods like encrypted code snippets sent to the hypervisor to be decrypted and executed there, code that does vital things for the game's logic... ).
Video game reviews
Video Games
Download Video Games


My guess: using those basic jailbreak exploits -without the hypervisor exploit and access- they might manage to dump GTA6... but this time I’m leaning toward something more extreme, looking at teams like DUPLEX or others and maybe using new means of dumping ( and decrypting ) games... don't forget/underestimate those teams...
Play PC Games
Video Games
Download Video Games
It’s amazing that HV exploit reportedly still works on 14.00, even though one kernel exploit was apparently patched. I have no doubt another kernel exploit will surface eventually, but I’m not sure when—it could be a long time off.

That’s why it’s better to stay on 13.60 for now, as a new exploit might be just around the corner (something other developers have also suggested).

We’ve gotten used to seeing a lot of new kernel exploits lately, but let’s not forget that hasn’t always been the case.

This, except the small mistake you made about 12.20 which doesn't support poopsploit (12.00 max). :)

But all and all, I would say there is no magic sheet to know what firmware you need to be on as the scene have been evolving rapidly these past weeks.

For example, 11.40 wasn't considered as "better" than 12.00 until a few days ago when FPKG finally got released.

The golden rule everyone should follow is just to stay where they are unless they absolutely need to upgrade for whatever reason (which in most case doesn't even exist to begin with).
It’s true that everything can change overnight... an fpkg method involving HV hasn't been created yet, so—unexpectedly—the method that doesn't require HV only works up to version 11.40.

I also used to think it was better to be on 12.00, but then that method for 11.40 came along... anyway, it would be great if HV made it possible to install fpkgs on firmware 13.60 as well.
 
  • Like
Reactions: solitaire4eva
This, except the small mistake you made about 12.20 which doesn't support poopsploit (12.00 max). :)

But all and all, I would say there is no magic sheet to know what firmware you need to be on as the scene have been evolving rapidly these past weeks.

For example, 11.40 wasn't considered as "better" than 12.00 until a few days ago when FPKG finally got released.

The golden rule everyone should follow is just to stay where they are unless they absolutely need to upgrade for whatever reason (which in most case doesn't even exist to begin with).
Good catch!
 
So in a nutshell, HV upto 14.00, GTA VI can still be dumped with Keys and Game will likely be backported. Whole incident Seems like bit of a nothing Burger except to portray Claude & Jordy as next antichrist 🤔
I think the worst thing is that theflow left the scene because he was working on adding linux support for ps5 pro - and now he's not.

I don't care about gta etc, I wanted a really nice ps5 pro linux release that I'm sure would have been delivered.
Hopefully someone else can do the magic.
 

Site & Scene News

Popular threads in this forum