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: 13.60
Highest unreleased HV: 14.00
*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,
@HS2005 Concerning backports. How are you sure eboot.bin, *.srx or *.sprx hasn't been modified? There is some dumps with versions than needs much higher firmware than stated for that specific version. Yet it comes with 4.xx support without mentioning backports for ex, or it does mention it but there is no other dump to reference. It can't be SDK compatability I reckon. And some backports do modify eboot.bin for ex. Am I missing something? :-)

Edit: What I mean is sometimes there is no other dump to compare to and i'm not sure if the eboot.bin etc been modified at all and need fakelib stuff to work even as a fpkg.
 
Sometimes even stuff that weren't modified are flawed because an old version of dump tool was used—one that wasn't very good and was subsequently patched and improved in various ways... so, ideally, we would create a completely new database :) but unfortunately, no one likely has time for that...
 
  • Like
Reactions: flopsy and ViRGE
Fantastic, but why couldn't the guy just make a pull request lol.
No need for a whole new project (or, is there?)
TheFlow is currently on a hiatus, isn't he? So there is no one to accept pull requests on the original PS5 Linux project; a fork (or other separate project) is all but required at this time.

I don't quite understand this desire to replace all formats with fpkg.
It can't be run from an external USB drive, also installing anything on an internal drive increases the chance of catastrophic kernel panic.
I would like to see fpkg as a main format + some A53 accelerated, Kraken based format that can be run from any drive (ArkSama, I'm counting on you), then everyone should be happy.
fPKG has the best performance and compatibility by far. Not only does it get the benefit of direct access to the system's accelerated I/O pathways and dedicated decoder blocks, but that means games can be run without modification, backports notwithstanding. Everything up until now has been a workaround for the inability to use fPKGs, with the ability to load games over USB being one of the handful of things that actually exceeds what a fPKG can do.

Meanwhile, I would say that the risk for a kernel panic with fPKGs to be overblown. With dumps it's an issue because we're doing all sorts of janky things with UnionFS and other techniques to map games into the file system hierarchy in order to run them. Official games (and fPKGs) are doing something a bit different and safer, and on a much better validated code path.

That said, don't forget that M.2 storage is an option here. With the PS4 we needed external storage because that was the only other option. On the PS5 we can put an M.2 drive in the system and have a storage drive that is distinct from the internal storage while still getting full support from the OS to use the accelerated I/O pathways.

Perhaps one day someone will get fPKGs working off of USB storage. But the bandwidth differential is pretty extreme: it's 1GB/second (at best) versus 7GB/sec for the M.2 slot.

This is the reason I wished for clean dumps, aswell, at the same time modified ones can be released. But right now it's very hard to find clean dumps/knowing they are clean unless you do them on your own, and it's not to easy to make them clean since eboot.bin etc been modified. Sometimes for good reason for ex Pro fix or something game breaking perhaps, but still. For long term archivation and perservation it would be nice with clean dumps as reference atleast.
For long-term preservation we have the Redump project, which is focused on making 1:1 clean dumps of discs. That doesn't cover digital-only releases, of course, but there is some thought being put in to long-term archiving, even if it's not something that's immediately user-accessible.
 
For long-term preservation we have the Redump project, which is focused on making 1:1 clean dumps of discs. That doesn't cover digital-only releases, of course, but there is some thought being put in to long-term archiving, even if it's not something that's immediately user-accessible.
I knew about this, but not something that is playable today for all systems :-) And maybe not in the forseeable future either. But still great for these systems either way.
 
How he didn't realize that? lol
Just a clickbait, I guess, but I'm not sure why he would do that. He usually makes informative videos about things that are happening in PS4 and PS5 hacking scene, no? Thankfully, Modded Warfare does a pretty good job covering those news.
 
1791941672115.png

someone is working on a fakePSN
 
  • Wow
Reactions: Blythe93
HyperHEN - An all-in-one HEN and Toolbox for PlayStation 5
https://github.com/Michele-M-Media/HYPERHEN
I like the energy. But I think we're still a bit early for an all-in-one HEN.

There are still too many things going on and changing in the PS5 jailbreak ecosystem right now. It would be better to wait a few months for everything to settle down and all of the necessary payloads for 13.60 get released, refined, and tested, before going on and bundling that all together as a single package.

etaHen bundled kstuff, and that aged like milk. Never mind all the problems with Elf Arsenal.

Is it possible to downgrade the payload manager back to 0.5.2? The new one crashes on the 6th and 7th payload no matter what order i set the paylopads in.
It should be possible to just install the 0.5.2 ELF over the current one. Worst case scenario, I should think you'd be able to delete the ELF, which would cause the version installed with your jailbreak application to load instead.
 
i do what he did exacly with ps5 fpkg on 13.60 and didint work. cant believe crump did that.
Coming up next: PS5 13.60 Console Reboot test. :D Yeah, I don't know why he did that either other than for clickbaiting people into checking it out.
 
Yes sideloading is fine with that sm+ directory. I prefer that method to installing backports via .PKG. Very handy because sometimes backport needs a fix and who wants to deal with the whole process again from scratch.

Guys, I'm sorry to be bumping my own thread but just want to confirm that info again.
What we have:
4.50 console with webkit 0.5.2 autoloader with latest kstuff from drakmor and latest shadowmount. Mortal Kombat 1 in fpkg format (PPSA07571) with preinstalled (baked-in) backport for 7.xx systems. Trying to start this game "as is" gives CE-100099-9 error which is "App has higher firmware than your console"
What was done:
Downloaded backport for 4.xx systems for PPSA07570 (its actually universal for both US and EU releases) and all files put in data/homebrew/backports/PPSA07571/
Result:
Shadowmount sees actual executables in backport location and overrides those, that are baked-in fpkg file. You dont have to redownload/repack/reinstall fpkg. Game works perfectly as if native pkg format.

Nothing new probably but maybe this info may help anyone who will face that error code (CE-100099-99).
 
If you watch the video. Hes installing a ps4 game xD
Wait Wut? :rofl2: I only saw like the beginning with kfstuff NG and Byepervisor and then CUSA on PS5... lol
HV isnt needed for PS4 PKG
Indeed it is not. Or he messed up the video himself or he was not thinking straight.

Just a clickbait, I guess, but I'm not sure why he would do that. He usually makes informative videos about things that are happening in PS4 and PS5 hacking scene, no? Thankfully, Modded Warfare does a pretty good job covering those news.

Indeed. I also find his videos informative, next to Modded. What Modded covers sometimes Michael does not cover and it's the other way around. This is just a huge screwup on his part.

@HS2005 Concerning backports. How are you sure eboot.bin, *.srx or *.sprx hasn't been modified? There is some dumps with versions than needs much higher firmware than stated for that specific version. Yet it comes with 4.xx support without mentioning backports for ex, or it does mention it but there is no other dump to reference. It can't be SDK compatability I reckon. And some backports do modify eboot.bin for ex. Am I missing something? :-)

Edit: What I mean is sometimes there is no other dump to compare to and i'm not sure if the eboot.bin etc been modified at all and need fakelib stuff to work even as a fpkg.
True. That's why I advise using a clean folder. If that's not possible use https://github.com/strongt1me/PS5-Dump-Image-Converter/releases/tag/v1.9.75 and recompile it. This program will mention if there are any errors in your build and you can also remove APR-EMU and select a backport version or not if you want.

In other news, for those of you who are making emulators:

MihawkGen v1.0.0: the network​

Download mihawkgen-network-v1.0.0.fgw (1.7 MB, 432,308 parameters). It is the network the generator loads with fg_context_load_network; it pairs with the shaders and code of this tag.

SHA-256 31ecc7d69af1e9de… (full sum in SHA256SUMS).

What it does​

Two colour frames in, the picture between them out. 30 or 60 fps to 120 fps on a base PS5: one generated picture between two real frames at 60 fps, three at 30 fps. Compute shaders, about 2.2 ms of the PS5's GPU at 3840×2160; no engine data and no motion vectors.

Benchmarks (never-trained games, middle picture, PSNR in dB)​

Method
MihawkGen
plain average of the two frames
FSR 3.1 frame interpolation (no engine data)
BiM-VFI (6.9 M parameters)
SGM-VFI (20.9 M)
GIMM-VFI-R (19.8 M)

SSIM and LPIPS tables, the x4 results and the 70 controlled situations are in the README and train/.

Use it​

framegen/tests/run.sh # tests, seconds
tools/lab.sh pixels # the pixel-art motion pass
tools/lab.sh host # FrameGen Lab on this PC

The file is plain weights: a short header (FGW1, the block sizes) and float tensors. Licence: GPL-3.0-or-later, like the generator.

Link: https://github.com/mihawk-99/PS5_MihawkGen/releases/tag/v1.0.0
 
Last edited by HS2005,
Report it to ItsPLK - not here. It not a page of ALL the payloads that are out there.
Post automatically merged:


Well it's not that complicated thankfully. I'll explain you some methods.

1. You can either unpack a .exfat or other format to folder and then remove the backport files.
2. Download a folder format first and then remove the backport files. Then rebuild to your desired format.

Result: No backport loading message.

Typical backport folder structure

Code:
Game/
├── eboot.bin
├── sce_sys/
│   └── param.json
├── sce_module/
│   └── *.prx
├── sce_modules/
│   └── *.sprx
├── fakelib/
│   └── patched system libraries
└── backport/
    └── optional metadata or patch files

What files do​

File or directoryPurpose
eboot.binMain game executable; may be modified to adjust its SDK requirement or compatibility.
sce_sys/param.jsonContains application metadata, including the title ID and title name.
sce_module/ or sce_modules/May contain game-specific modules and system libraries, depending on the dump.
fakelib/Can hold patched compatibility libraries used by particular backport methods.
.bps filesBinary patch files that describe changes to apply to a target file.
.bak or backup foldersPreserve original files before modification.
Readme or metadata filesDocument the target firmware, patch version, or installation instructions.

Where backports are stored with ShadowMountPlus​

The location matters because a backport overlay does not necessarily belong inside the original game folder.

Code:
/data/
├── homebrew/
│   ├── PPSA12345/
│   │   └── sce_sys/
│   │       └── param.json
│   └── backports/
│       └── PPSA12345/
│           └── [backport files]
└── etaHEN/
    └── games/
        └── [other game folders]

I'm a big fan of using option 2.It's the easiest part / method. Good luck and have fun.
Post automatically merged:

EDIT: Should you still have issues. Just download a full folder 13.60 game and seperate backport. Check the files from the backport folder to see what you can remove and how the layout and files are used.
Thanks but yet I got a question because it sounds kinda unclear to me:
With the first method - do i delete just what's in /backport/ folder or also eboot.bin, param.json, *.prx, *.srpx and /fakelib/ catalog? I think the game wouldn't run if i deleted all of those.
And about the second method - i don't see /backports/ folder in /data/ at all 🤔

I've seen info about mounting a backport to a game previously but don't have it anymore with any (of little just 3 titles).
Although it says now for each game: 'Mounting emulators' - I believe this is just about fakelibs, right?

What would be the cases (in ShadowMountPlus) to change `Mount fakelibs` feature from Default (Full) to 'Just emulators' or to 'Off'?

Also - when payloads load (I am a simple man and run just kstuff and ShadowMount+) it says launching PPR and then PPR installation failed - should i be concerned?

And last two questions I have - what even is that PPR? And also I've seen a different times (in here and not only) something called 'a53' - I've only found that it's some exploit like HV but for lower fw's?
 
Last edited by ayechief,

Site & Scene News

New Hot Discussed User Submitted