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-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: 14.10 (SlopVisor)
*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.52
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,
Thanks for taking the time out to put this down for everyone that is/was having issues. My file perms are already 777 for the .dat file.

You got me on the folder perms, though, but in my defence EVERYTHING in that folder is set the same (0700) and I didn't want to start pissing about with changing anything more than I needed to seeing as I was trying to move away from the hard lock ups that freaked me the-fuck-out the more they happened. The file system on this box is pretty fragile, in my experience, so less messing the better imo. I was pushing back against the blanket 'just use .253 and you're golden' mentality. It was not as black/white as that. That was my message, with proof.

As you mentioned, everything is working for me so I see zero point in fixing a problem that isn't happening. Again, thank you very much for responding, shining a light on something that might help someone else and, of course, everything you do in this mammoth thread. It's appreciated.
 
Thanks for taking the time out to put this down for everyone that is/was having issues. My file perms are already 777 for the .dat file.

You got me on the folder perms, though, but in my defence EVERYTHING in that folder is set the same (0700) and I didn't want to start pissing about with changing anything more than I needed to seeing as I was trying to move away from the hard lock ups that freaked me the-fuck-out the more they happened. The file system on this box is pretty fragile, in my experience, so less messing the better imo. I was pushing back against the blanket 'just use .253 and you're golden' mentality. It was not as black/white as that. That was my message, with proof.

As you mentioned, everything is working for me so I see zero point in fixing a problem that isn't happening. Again, thank you very much for responding, shining a light on something that might help someone else and, of course, everything you do in this mammoth thread. It's appreciated.
Sure I can understand that. NP.
I see a lot of cases where the write permissions are an issue. Not YT related in general.
As I mentioned: if it works it works. Thought you perhaps want to tinker (like I mostly do) with stuff to learn / improve etc. But it's not a necessity.
 
Sure I can understand that. NP.
I see a lot of cases where the write permissions are an issue. Not YT related in general.
As I mentioned: if it works it works. Thought you perhaps want to tinker (like I mostly do) with stuff to learn / improve etc. But it's not a necessity.
Thanks. I do like to tinker. Being here conversing about this is evidence of that. I also get paid to do it 9-5. I just don't want to do it on a near £1k limited-edition box, with a notoriously fragile file system, that is just one serious KP away from needing a system update to 14.00. That would shit on my cornflakes, quick smart.
 
Last edited by JayPea,
Would love to see a comprehensive guide on building fpkg (settings). So grabbing dump, adding backport, dlc and game update.

But also how to fix a broken release. So fkpg back to dump folder and hopefully fixing issue like backport. Or changing game update to an older or newer one.

I would usually research myself but can't do to much testing on my current pc as old and not much HDD space left.

Maybe guide exists? Or hopefully MW or another youtuber creates one SOON...
 
Yes. :toot: PPSA18194 (v1.004.003) FW 13.60

1791226499740.png

Link:
https://prosperopatches.com/PPSA18194

Post automatically merged:

Would love to see a comprehensive guide on building fpkg (settings). So grabbing dump, adding backport, dlc and game update.

But also how to fix a broken release. So fkpg back to dump folder and hopefully fixing issue like backport. Or changing game update to an older or newer one.

I would usually research myself but can't do to much testing on my current pc as old and not much HDD space left.

Maybe guide exists? Or hopefully MW or another youtuber creates one SOON...
Regarding APR emu and backports you can already use: https://github.com/strongt1me/PS5-Dump-Image-Converter/releases/tag/v1.9.43

This is an auto APR updater: https://github.com/tsuramatsu1/apr-emu-updater/releases/tag/v2.0.6

Handy: A Standalone PS5 payload for compressing, unpacking, validating, repairing, and moving ShadowMountPlus-mounted games from a simple web UI: https://github.com/gcoding97/PS5-Game-Compressor/releases/tag/v1.1.1

And last a Windows app for managing your PS5 dump and image collection, reading PS5 packages, and building or converting images: https://github.com/pearlxcore/PS5PKGTool/releases/tag/v1.2.0
 
Ok, ff7 rebirth finished downloading and installing as fpkg (fw 9+ eu version from dlps). I put the backport files in the ppsaxxxxx folder in /data/homebrew/backports.
Game shows splash screen on start and debug backport message too, so the backport gets indeed recognized by sm+.
But the game crashes with "an error occured" and returns to home screen.
I guess the backport is not interchabgeable between the loose file release and the fpkg release.
But with a matching backport it should work generally to have an installed fpkg and loose backport files.
 
Hey quick question. So I did hear about the new exploit. Checked my PS5 and it is on 13.60. I tried to follow the guide. I blocked the update things, but still get the nag and got to update to do anything? Does that mean I can't do the exploit? The guide says to go unto settings and then user and then open youtube, but I don't have that option. Could someone enlighten me.
 
I put the backport files in the ppsaxxxxx folder in /data/homebrew/backports.
Game shows splash screen on start and debug backport message too, so the backport gets indeed recognized by sm+.
But the game crashes with "an error occured" and returns to home screen.
I guess the backport is not interchabgeable between the loose file release and the fpkg release.
But with a matching backport it should work generally to have an installed fpkg and loose backport files.
The Rebirth I know uses FW 9.xx+

There is a FW 4.xx Backport for PPSA08668_01.080.000. See image below. I have that one.

1791227619120.png


Linkz:
https://gofile.io/d/F7vV0aEU
https://vikingfile.com/f/uH0HIqvBKe
https://akirabox.to/LK0G1bAXjm91/file

So you can do it 2 ways:

1. Unpack the fpkg to a folder dump and put the files in there > repack to fpkg.
2. Download the original folder (353GB) > put the files in there > repack to fpkg.

I have uploaded the cheats here: https://hencheats.vercel.app/game/PPSA08668/01.080.000/
Here is also the latest build of SM+: ShadowMountPlus_1.7beta4-6-g4cde42.zip
 
Is there a tutorial for offline account activation? Trying to play Halo.
Thanks!!!
I'm also interested, I thought I had an activated account but it turns out I didn't (even though I have the login options at boot).

I am aware about offact and NP Fake Signin but I have heard that doing so on an existing account will make all existing savegames unusable because of the ID changing.

TLDR: I want to fake activate my existing account without losing all my saves, how can I do that?
 
PS5 Relapse Exploit Offline Host got updated today with support for a lot of ESP boards !!!

https://github.com/0x1iii1ii/PS5-Server/releases/tag/0.6

Auto-load Payload Manager after jailbreak.

Supported boards:

ESP8266
ESP32 / ESP32 Dongle
ESP32-S2 / ESP32-S2 Dongle
ESP32-S3 / LILYGO T-Dongle-S3

Supports PS5 FW from 7.XX - 13.XX.

Many many thanks to _iggyman_ for the tip !!!

:bow:

PS:

Massive thanks to 0x1iii1ii for creating the PS5 Relapse Exploit Offline Host !!!

:bow:
 
  • Like
Reactions: peteruk
Is there any progress on BD-J for firmware 13.60? (Theory is that WebKit-based exploit applies an unbdJb patch to enable BD-J entry point on 13.60 as well
 
I'm also interested, I thought I had an activated account but it turns out I didn't (even though I have the login options at boot).

I am aware about offact and NP Fake Signin but I have heard that doing so on an existing account will make all existing savegames unusable because of the ID changing.

TLDR: I want to fake activate my existing account without losing all my saves, how can I do that?
You can use this to fake sign in and activate. Games will think your signed in and won't ask you. Then reboot to apply:
ps5-account-tools

etaHEN already activates the console but doesn't do fake sign in.
 
You can use this to fake sign in and activate games will think your signed in and won't ask you then reboot to apply:
ps5-account-tools

etaHEN already activates the console but doesn't do fake sign in.
Thanks, that looks interesting but what about my savegames? Am I gonna lose them if I fake activate my main account using this payload?
 
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)

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



PS4 GAME INFORMATION:
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.52
OFW 14.xx runs PS4 games up to 14.00
6.02 max, 6.02 for Linux...
Then new JB 6.50-7.61 was released, so Linux is available for 6.50 as well.


Highest unreleased HV: 14.10
14.10 or 14.00 or 13.60 ? Maybe safe option 13.60 or "13.42/13.60 or 14.00"

OFW 13.xx runs PS4 games up to 13.52
I think that’s incorrect; a PS5 on version 13.00 definitely can't run PS4 version 13.52 because at that time, no such thing existed. ... you also need to look at the firmware release dates. I believe support for PS4 13.52 arrived with PS5 13.42, based on the build release dates. It would be good to verify those last few details mentioned above.


I'm also interested, I thought I had an activated account but it turns out I didn't (even though I have the login options at boot).

I am aware about offact and NP Fake Signin but I have heard that doing so on an existing account will make all existing savegames unusable because of the ID changing.

TLDR: I want to fake activate my existing account without losing all my saves, how can I do that?
You can use this to fake sign in and activate. Games will think your signed in and won't ask you. Then reboot to apply:
ps5-account-tools

etaHEN already activates the console but doesn't do fake sign in.
If we restore profile backup from Y2JB, is profile already activated—meaning there’s no need to perform those activations using *etahen* or *np_fake_sign*? A friend of mine wouldn't want to start playing games only to lose his save data later on. That’s why it’s better to get everything ready beforehand.
 
Last edited by Eva888,
Thanks, that looks interesting but what about my savegames? Am I gonna lose them if I fake activate my main account using this payload?

6.02 max, 6.02 for Linux...
Then new JB 6.50-7.61 was released, so Linux is available for 6.50 as well.


Highest unreleased HV: 14.10
14.10 or 14.00 or 13.60 ? Maybe safe option 13.60 or "13.42/13.60 or 14.00"

OFW 13.xx runs PS4 games up to 13.52
I think that’s incorrect; a PS5 on version 13.00 definitely can't run PS4 version 13.52 because at that time, no such thing existed. ... you also need to look at the firmware release dates. I believe support for PS4 13.52 arrived with PS5 13.42, based on the build release dates. It would be good to verify those last few details mentioned above.




If we restore profile backup from Y2JB, is profile already activated—meaning there’s no need to perform those activations using *etahen* or *np_fake_sign*? A friend of mine wouldn't want to start playing games only to lose his save data later on. That’s why it’s better to get everything ready beforehand.
Regarding fake sign in you don't lose your saves.

Regarding activation not sure what does the activation first etaHEN or Y2JB if you check remote play options in etaHEN settings it will say if it's activated or not.

Your best bet is to backup saves to a pc using ftp and activate just to be safe.
 

Site & Scene News

New Hot Discussed User Submitted