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) (BD/Y2/NF/LUA/YARPE: 6.50 max)
7.XX = KEX: PS4/5 backups (KEX+HV+Linux) (
WK/BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = KEX: PS4/5 backups (KEX+HV) (WK/BD/Y2/NF/LUA/YARPE)
10.01-12.70 = KEX: PS4/5 backups (KEX+HV) (
WK/BD/Y2/NF/LUA/YARPE)
13.XX-13.60 = HV+KEX+WK (
WK/BD (13.42)/Y2/LUA/YARPE)
14.XX = No KEX/HV. UL ONLY (LUA/YARPE)

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


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


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

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

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


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

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

Preparing Your Console:


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


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

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

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

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

21.02-04.03.00.00-00.00.00.0.1

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

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

WARNING:

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

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

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

Select Your Jailbreak:


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


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

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

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

    Exploiting 7.00-13.60:

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

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

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

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

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


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

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

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

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

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

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

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

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

    LUA Loader: HERE or HERE

    Auto LUA Loader Fork: HERE

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

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

    Incompatible LUA games:

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

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

  4. Requirements:
    PS5 console must be on 4.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
OFW 13.xx runs PS4 games up to 13.42
OFW 14.xx runs PS4 games up to 14.00


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


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

Warnings:


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

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

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

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

Archived Information


 
Last edited by KiiWii,
IMHO, the best way to go would be to bump it up to 7.61 for now. For someone looking to run Linux that is one of the sweet spots right now since it is the highest version with a hypervisor exploit, and it gets access to all sorts of kernel exploits (along with fPKG for games). FW 6.xx is kind of a no-mans land; the scene seems to be coalescing around 4.03, 7.61, and 9.60 as the "popular" early firmwares.

I'm currently testing on 6.02. Describing as "no mans land" is slight exaggeration. Its only fw that doesn't have WebKit userland but not essential. Backporting games to 6.xx is bit more challenging than other fw but a competent backporter will know what to do.

I was tempted to upgrade to 7.61 but no need until 6.xx become problematic or isolated in Ps5 scene. Only reason I would upgrade is if custom firmware became available and jailbreak was no longer untethered.

I kind of regretted upgrading from 5.50fw to 6.02 and won't do that again. You don't know what future holds...
 
I dont have an m2 installed internally yet, so i its installed in the internal ssd.
If yours is installed in the internal m2 slot, maybe try moving it to internal.
I had problems with gt7 on my legit online console (around fw 10 times i think) while it was installed in the m2 slot ssd. Crashed sometimes too. Moved to internal and problems gone for gt7.

And make sure to use the backport files of hs2005, not the ones on dlps, they threw the same error for me
That was the problem. The game plays perfectly fine now. Rebirth and gran turismo 7 needs to be installed internal for the backport to work for 4.03
 
Anyone got Wolverine to work yet on their pro? If so, what did you do?
The following does not work for me..

1. kstuff-fpkg-1.13-dr-test5
2. ShadowMountPlus 1.7beta4

Edit:

Got it working seems the Pro fic pkg was not being applied through pkg manager. I had to apply in via debug settings... All working from Internal :)
 
Last edited by BobaFett_UK,
Anyone got Wolverine to work yet on their pro? If so, what did you do?
The following does not work for me..

Pro 9.20, Pro fix included in the fpkg by Deckerr97
1. kstuff-fpkg-1.13-dr-test5
2. ShadowMountPlus 1.7beta2 and beta4
Yes. PS5 Pro. 13.60.
.exfat and .ffspsc works. External and internal.
Using kstuff 1.11 (ng also works) and SM+ (latest)
 
I'm currently testing on 6.02. Describing as "no mans land" is slight exaggeration. Its only fw that doesn't have WebKit userland but not essential. Backporting games to 6.xx is bit more challenging than other fw but a competent backporter will know what to do.

I was tempted to upgrade to 7.61 but no need until 6.xx become problematic or isolated in Ps5 scene. Only reason I would upgrade is if custom firmware became available and jailbreak was no longer untethered.

I kind of regretted upgrading from 5.50fw to 6.02 and won't do that again. You don't know what future holds...
Hello friends, I have a OG PS5 currently on FW 6.02 - what's the best path to JB for me? bump to 7.0 to be able to run relapse and/or linux as I wish?

Many tools (including kstuff) have logic in their internal code where, if firmware version is below 7, they execute a routine—let's call it the "golden chicken"—whereas if it's 7 or higher, they execute a different one—let's call that the "ordinary chicken."

So, it's essentially "golden chicken" versus "ordinary chicken." It involves DMA writes or something similar... Given existence of hypervisor, it probably doesn't matter all that much—but who knows in future?

In any case, FW 6.02 supports "two" hypervisors: the original TMR-based one and the one used from version 6.50 through 7.61 (technically more lower fw might be possible, but no one has implemented them). Personally, I think the 6.50–7.61 version is superior to earlier one because of TMR handling. On version 4.xx, initial hypervisor disabled TMR; while that did allow us to disable hypervisor itself, it came at a terrible cost—a massive slowdown in games, turning experience into a pain rather than a pleasure.

So, ask yourself:
What advantages does FW 7.61 offer me right now?


First, there's WebKit; while WebKit is currently available on 7.xx, it might come to 6.xx in the future... Also, some users aren't happy with WebKit and use the Y2JB autoloader instead; in practice, it just means launching either the red icon or the blue icon.

Linux is available for both 6.xx and 7.xx.

fPKGs work on both 6.xx and 7.xx, and there isn't much difference regarding backports between these two firmware versions either...

So, personally, I can't think of any major difference between these firmware versions right now—except, perhaps, for the official firmware changelog itself.

If anything changes in the future, you can always update to 7.61, but you can't go the other way... Like the person who wrote earlier that they regret updating from 5.50 to 6.02. Firmware 6.xx includes official support for 1440p, which is a HUGE CHANGE. So, in my opinion, there’s nothing to regret.
 
Don't know much about them but they were threatening to release private keys recently. Wonder if this was the person @TheStonedModder was referencing.

Anyway I think they never would. Just using to get attention and leverage. No one in public sphere would do something so stupid 😂
He’s one of the few that stood up for me believe it or not

He’s not a bad guy, but he does get carried away at times (who doesn’t) either way any more info would be hella off topic ha
 
I'm currently testing on 6.02. Describing as "no mans land" is slight exaggeration. Its only fw that doesn't have WebKit userland but not essential. Backporting games to 6.xx is bit more challenging than other fw but a competent backporter will know what to do.

I was tempted to upgrade to 7.61 but no need until 6.xx become problematic or isolated in Ps5 scene. Only reason I would upgrade is if custom firmware became available and jailbreak was no longer untethered.

I kind of regretted upgrading from 5.50fw to 6.02 and won't do that again. You don't know what future holds...
In your opinion what exploit should I use to JB on 6.02? Y2JB?
 
Backporting games to 6.xx is bit more challenging than other fw but a competent backporter will know what to do.
Oh, so it's not just me being a complete idiot then. :rofl2:

So it's easier to backport to 4.xx and 5.xx than 6.xx? Because most the backports I use are for those firmwares.
In your opinion what exploit should I use to JB on 6.02? Y2JB?
I know you didn't ask me, but that's what I'm using on 6.02. Best to have a backup method if something goes wrong, I have itsPLK's autoloader BDJ and a lua game.

Lua is the most stable but I never really use it anymore now that y2jb and bdj are very stable too, and less hassle.

Plus not everyone has an expensive lua game lol
 
  • Haha
Reactions: AlphaBravo
Many tools (including kstuff) have logic in their internal code where, if firmware version is below 7, they execute a routine—let's call it the "golden chicken"—whereas if it's 7 or higher, they execute a different one—let's call that the "ordinary chicken."

So, it's essentially "golden chicken" versus "ordinary chicken." It involves DMA writes or something similar... Given existence of hypervisor, it probably doesn't matter all that much—but who knows in future?

In any case, FW 6.02 supports "two" hypervisors: the original TMR-based one and the one used from version 6.50 through 7.61 (technically more lower fw might be possible, but no one has implemented them). Personally, I think the 6.50–7.61 version is superior to earlier one because of TMR handling. On version 4.xx, initial hypervisor disabled TMR; while that did allow us to disable hypervisor itself, it came at a terrible cost—a massive slowdown in games, turning experience into a pain rather than a pleasure.

So, ask yourself:
What advantages does FW 7.61 offer me right now?


First, there's WebKit; while WebKit is currently available on 7.xx, it might come to 6.xx in the future... Also, some users aren't happy with WebKit and use the Y2JB autoloader instead; in practice, it just means launching either the red icon or the blue icon.

Linux is available for both 6.xx and 7.xx.

fPKGs work on both 6.xx and 7.xx, and there isn't much difference regarding backports between these two firmware versions either...

So, personally, I can't think of any major difference between these firmware versions right now—except, perhaps, for the official firmware changelog itself.

If anything changes in the future, you can always update to 7.61, but you can't go the other way... Like the person who wrote earlier that they regret updating from 5.50 to 6.02. Firmware 6.xx includes official support for 1440p, which is a HUGE CHANGE. So, in my opinion, there’s nothing to regret.

Great write up. I will forever refer to my 6.02 as "Golden Chicken" 😂

Did you research this for your "friend" as well? Beginning to wonder if they are bit imaginary. It's ok to be super nerd 💪

I regretted upgrading to 6.02 in early days of JB scene because it took a long time get userland and Kex exploits between 4.xx and 5.xx. And then 5.xx got WebKit userland not to long after.

Today I don't mind so much. Fpkg support is a massive advantage of any fw above 11.60.
BUT as soon as 12-13.xx get fpkg support I will jump ship. Perhaps use 6.02 as test machine or useful that it has 500gb of unused storage space 😉

Main advantage for ps5 pro aside from more powerful GPU is in the emulation scene. They just run better with higher res and FPS.
 
Has anyone tried the ps5x360 emulator? for me crashes when launching any game does not matter where (internal/external) or format (folder, god or iso) it crashes after a second of starting any game (in some games i see an initial loading or logo) but then it crashes and saying that the crash happens before kstuff paused then it goes back to home. any advice?

I used to have this also with 3ds games but latest version of ps5cemu-har 3.5.0 works for me all of the sudden.

other than that the rest of the emulators works great (baring the odd slowdown here and there), very impressive stuff and great to progress daily.
 
Last edited by AceLighting,
Halo Campaign Evolved. “eliminate all hostiles surrounding the three UNSC lifeboat crash sites to safely extract the survivors”

This is level 2. Immediately after completing this, the game crashes. Does this happen for anyone else?
 
Oh, so it's not just me being a complete idiot then. :rofl2:

So it's easier to backport to 4.xx and 5.xx than 6.xx? Because most the backports I use are for those firmwares.

Nope. But I have yet to test a game that hasn't worked on 6.02. Returnal was one but that was due to the "date bug". I am currently fixing it myself as can't be bothered to change my calendar every time I want to play it 😂

Bestpig backport project states that 6.xx patches need more work in some instances. Not always though.

You could always message me and ask me to test a game with you but it would have to be one that we both kind of like. I refuse any testing on Wolverine :p
 
  • Haha
Reactions: Rasa39
I know it's 8TB. Also looking at Sony functionalities. I have 2 system with 8TB. Dunno if you even have a 16TB M2.

Sony website:
The M.2 expansion slot of the Sony PlayStation 5 supports M.2 NVMe SSDs with capacities ranging from 250 GB up to 8 TB.
Key drive specifications required:

  • Interface: PCIe Gen4x4 M.2 NVMe SSD (Key M)
  • Capacity: 250 GB to 8 TB
  • Recommended Read Speed: 5,500 MB/s or faster
  • Form Factor: 2230, 2242, 2260, 2280, or 22110
  • Dimensions (including heatsink): Width up to 25 mm, length up to 110 mm, and thickness up to 11.25 mm

I assumed he was referring to a 16TB external HDD since it will be used to store roms for emulation

I’d be interested to know if anyone has tried this method:
Update to latest 7.00 beta (there are a few 7.00 beta versions), then enjoy and test WebKit jailbreak for long time. If CFW for versions 1.xx–6.xx becomes available, one can downgrade without any issues.

What makes you think you can downgrade firmware on a PS5?
 
What makes you think you can downgrade firmware on a PS5?
Beta users can roll back one version if we're talking about BETA firmware...
That’s basic knowledge—like knowing that 1+1=2...

If the beta turns out to be bad, people can revert to previous firmware version—for example from 7.00 to 6.50, and so on.

Of course, I don't know how offsets work on "beta" version—whether they're identical to the official firmware or different.
 

Site & Scene News

New Hot Discussed User Submitted