Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


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

6.XX = KEX: PS4/5 backups (KEX+HV+Linux: 6.02 max) (WK/BD/Y2/NF/LUA/YARPE: 6.02 for Linux / 6.50 max)
7.XX = KEX: PS4/5 backups (KEX+HV+Linux: 7.61) (
WK/BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = KEX: PS4/5 backups, no HV (WK/BD/Y2/NF/LUA/YARPE)
10.01-12.70 = KEX: PS4/5 backups, no HV (
WK/BD/Y2/NF/LUA/YARPE)
13.XX = HV+KEX+WK (
WK/BD (13.42)/Y2/LUA/YARPE)
14.XX = No KEX/UL only (LUA/YARPE)

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


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


Kernel (KEX):
Highest released KEX:
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/Prolapse: 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):
LUA (Artemis): 2.00-LATEST (LUA exploit, + Lapse up to 10.01)
Y2JB: 4.03-13.40 (YouTube exploit, + Lapse: 10.01 / P2JB: 12.70)
NFNH: 4.03-12.XX (Netflix exploit, + Lapse: 10.01)
YARPE: 4.03-12.XX (Ren'Py exploit, + Lapse: 10.01 / P2JB: 12.70)
BD-JB: 1.00-13.42 (BD exploit + UMTX2: 7.61 / BD-JB5 + Poops to 12.00)
Webkit: 1.00-5.50 (PSFREE +UMTX2: 5.50 / 7.00-13.60 (RELAPSE)
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.
NOTE 2: Consoles 7.00-13.60 can use WebKit and RELAPSE (Recommended)


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

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

Preparing Your Console:


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


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

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

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

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

21.02-04.03.00.00-00.00.00.0.1

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

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

WARNING:

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

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

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

Select Your Jailbreak:


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


  1. Information:
    Firmware 1.00-5.50 or 7.00-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,
I will not repeat myself. It's being worked on. End of story.
If you want to follow the updates I would advise to join this specific Discord group: https://discord.gg/6F4PEtcRX
Post automatically merged:

EDIT: Newer update.

Link: https://github.com/mihawk-99/PS5_RetroArch/releases/tag/v0.5.7-alpha.5


Is not compiled or im mistake?
Post automatically merged:

Well in your settings > install location you can decide where to put your data / games

View attachment 593493


If i i try to install on an m2 that contains exfat games,it will erase them before installing?
 
Is not compiled or im mistake?
Define complicated.
Post automatically merged:

13.60 hack comes out; Sony miraculously get QSSR on base model consoles….
Indeed. Just read it today. The irony. It's suddenly "possible".
 
Last edited by HS2005,
People are reporting that illusion's patches for PS4 games are working via manual installation, on 13.20 at least, with the steps given in their repository for the PS5 usage. Haven't seen anything for 13.4x or 13.60. I'm far from my console right know, so no clue if it works for 13.60 yet.

https://github.com/illusionyy/ps-game-patch
Confirmed, the method does not work on 13.40 and 13.60, the .elf does nothing on those firmware versions. It is confirmed that it is working on 13.00 and 13.20.
Post automatically merged:

13.60 hack comes out; Sony miraculously get QSSR on base model consoles….
Suspicious if anything xD
 
Is there a fix for elfdir not working? I updated itsplk's webkit autoloader on 13.4 which solved my inconsistant boot issue, and crashing

Now I just cant send any payloads outside of the initial autoload
Well I actually got my first errors today. I was already waiting for this to happen. :toot:
The Webkit Autoloader did not work anymore. It was not loading the exploit. Getting stuck. Getting a blank page etc.
And as I always do I invested some time to figure some things out. I mean: computers are stupid and i'm in charge.

What I did was I went through all of the discussion threads:
[v0.5.0] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/15
[v0.5.1] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/17
[v0.5.2] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/21

Perhaps a solution for you:

"On firmwares 7.00–13.60 (Relapse / Poops), the autoloader uses a custom version of elfldr that only accepts connections from the PS5 itself (localhost). This improves security by preventing unauthorized devices on your network from sending payloads to your console. On firmwares 1.00–5.50 (umtx2), the stock elfldr is booted.

If you want to use a "normal" ELF Loader that allows sending payloads from any device, you can simply load it through Payload Manager.

Alternatively, if you are using a manual config file (autoload.txt):

Place your custom ELF Loader (e.g. elfldr.elf) in the ps5_autoloader directory.
Add elfldr.elf to your autoload.txt.
Note: If you are loading other payloads right after elfldr.elf in your autoload.txt, add a sleep command immediately after it (like !4000 to sleep for 4 seconds) to give the new ELF Loader time to start up and listen before subsequent payloads are sent."

https://github.com/ntfargo/Relapse-Exploit/blob/main/payloads/elfldr-ps5-1360.elf

And etaHEN:

https://github.com/ntfargo/Relapse-...9ae9e8df214da37271290b13e/payloads/etaHEN.elf

This was not my issue. I revolved my issue this way:

My personal solution
1. Deleted the webkit autoloader application.
2. Cleaned/cleared the cache and deleted the browser cookies
3. Iinstalled v0.5.2 again.
4. After a reboot it worked again.

So I rebooted 4 times and 4 times it worked again. Don't know about the 5th boot and onwards lol... Guess I'll check tomorrow again.
 
Last edited by HS2005,
Well I actually got my first errors today. I was already waiting for this to happen. :toot:
The Webkit Autoloader did not work anymore. It was not loading the exploit. Getting stuck. Getting a blank page etc.
And as I always do I invested some time to figure some things out. I mean: computers are stupid and i'm in charge.

What I did was I went through all of the discussion threads:
[v0.5.0] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/15
[v0.5.1] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/17
[v0.5.2] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/21

Perhaps a solution for you:

"On firmwares 7.00–13.60 (Relapse / Poops), the autoloader uses a custom version of elfldr that only accepts connections from the PS5 itself (localhost). This improves security by preventing unauthorized devices on your network from sending payloads to your console. On firmwares 1.00–5.50 (umtx2), the stock elfldr is booted.

If you want to use a "normal" ELF Loader that allows sending payloads from any device, you can simply load it through Payload Manager.

Alternatively, if you are using a manual config file (autoload.txt):

Place your custom ELF Loader (e.g. elfldr.elf) in the ps5_autoloader directory.
Add elfldr.elf to your autoload.txt.
Note: If you are loading other payloads right after elfldr.elf in your autoload.txt, add a sleep command immediately after it (like !4000 to sleep for 4 seconds) to give the new ELF Loader time to start up and listen before subsequent payloads are sent."

https://github.com/ntfargo/Relapse-Exploit/blob/main/payloads/elfldr-ps5-1360.elf

This was not my issue. I revolved my issue this way:

My personal solution
1. Deleted the webkit autoloader application.
2. Cleaned/cleared the cache and deleted the browser cookies
3. Iinstalled v0.5.2 again.
4. After a reboot it worked again.

So I rebooted 4 times and 4 times it worked again. Don't know about the 5th boot and onwards lol... Guess I'll check tomorrow again.
What you're saying is - 0.5.2 fixed the crashes? I've read the changelog for that version and maybe i'm missing something but i don't see any fixes - unless skipping splash screen/logo is doing the thing.
 
Well I actually got my first errors today. I was already waiting for this to happen. :toot:
The Webkit Autoloader did not work anymore. It was not loading the exploit. Getting stuck. Getting a blank page etc.
And as I always do I invested some time to figure some things out. I mean: computers are stupid and i'm in charge.

What I did was I went through all of the discussion threads:
[v0.5.0] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/15
[v0.5.1] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/17
[v0.5.2] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/21

Perhaps a solution for you:

"On firmwares 7.00–13.60 (Relapse / Poops), the autoloader uses a custom version of elfldr that only accepts connections from the PS5 itself (localhost). This improves security by preventing unauthorized devices on your network from sending payloads to your console. On firmwares 1.00–5.50 (umtx2), the stock elfldr is booted.

If you want to use a "normal" ELF Loader that allows sending payloads from any device, you can simply load it through Payload Manager.

Alternatively, if you are using a manual config file (autoload.txt):

Place your custom ELF Loader (e.g. elfldr.elf) in the ps5_autoloader directory.
Add elfldr.elf to your autoload.txt.
Note: If you are loading other payloads right after elfldr.elf in your autoload.txt, add a sleep command immediately after it (like !4000 to sleep for 4 seconds) to give the new ELF Loader time to start up and listen before subsequent payloads are sent."

https://github.com/ntfargo/Relapse-Exploit/blob/main/payloads/elfldr-ps5-1360.elf

This was not my issue. I revolved my issue this way:

My personal solution
1. Deleted the webkit autoloader application.
2. Cleaned/cleared the cache and deleted the browser cookies
3. Iinstalled v0.5.2 again.
4. After a reboot it worked again.

So I rebooted 4 times and 4 times it worked again. Don't know about the 5th boot and onwards lol... Guess I'll check tomorrow again.
I also had the opportunity to experience strange behavior.
After downgrading the webkit autoloader, I decided to clear data/cache and cookies to make sure the failed exploit attempts weren't caused by some cached junk.
This completely blowed up the ps5-webkit-autoloader. After launching it, it got stuck at 'waiting to start' every single time.
No amount of deleting the shortcut, reinstalling and rebooting helped.
Only after completely clearing the /user/home/<userid>/webkit/shell folder content and reinstalling the autoloader it started working again.
 
Last edited by kam821,
13.60 hack comes out; Sony miraculously get QSSR on base model consoles….
They'll rip it away immediately if there's ever a newer firmware exploit released, it'll be removed as part of the next updates "Stability and optimisation" patches :rofl2:

Lucky for me, they lost Kojimbo, the main reason I didn't mind Sony consoles. Thankfully xbox love releasing games as console exclusive, but not platform exclusive. Never liked many xbox exclusives, but never needed to buy one since the 360 so can't complain lol. PCMR

It's great to be a PS5 andy though if you don't have a pc with all the recent dumps, if you wanna stick your fist up Sony's arse.

Also is it available on pro consoles at earlier fw versions? If so, that means someone might be able to port it over to earlier base consoles maybe?
 
I am got a bit lazy but search command didn't work out.
Does anyone have the complete youtube packages by region and firmware pls.
Thank you.
I do have usa/eu/jp version .003 and .030
 
Last edited by vivastar,
So Relapse needs network connected but doesnt need internet when using webkit installed. Did anyone tried a loopback Ethernet adapter?? If i have Time over the weekend i might try it myself but if someone has a spare one around or want to do it from some spare cable that will help a lot and we will have fully offline solution.

How would that be different from using localhost DNS on your PS5 LAN or WiFi setting?
 
What you're saying is - 0.5.2 fixed the crashes? I've read the changelog for that version and maybe i'm missing something but i don't see any fixes - unless skipping splash screen/logo is doing the thing.
No. Read again ^^
It was the cache and cookies that was part of the issue (at least for me) every FW, system (PRO/SLIM etc.) and situations differs.
Post automatically merged:

Karo set up a host for Relapse, guarantees more reliable launch, without it freezing halfway through or causing the browser to crash, and without black screens or crashes when loading ELF.


Always good to have back-ups and improvements. What Sonic is mentioning is in fact correct. I've also reported prob. the same issues to LM.

EDIT: Forgot to add this. Stay tuned.

1790887918051.png


Post automatically merged:

I also had the opportunity to experience strange behavior.
After downgrading the webkit autoloader, I decided to clear data/cache and cookies to make sure the failed exploit attempts weren't caused by this.
This completely blowed up the ps5-webkit-autoloader. After launching it, it got stuck at 'waiting to start' every single time.
No amount of deleting the shortcut, reinstalling and rebooting helped.
Only after completely clearing the /user/home/<userid>/webkit/shell folder content and reinstalling the autoloader it started working again.
Ah so you had do deal with it the hard way. Mine was a lot easier to deal with (well for now that is). Should I stumble on your issue I can always try that.
Post automatically merged:

The Legend of Zelda: The Wind Waker HD FTW :toot:
 
Last edited by HS2005,
Well I actually got my first errors today. I was already waiting for this to happen. :toot:
The Webkit Autoloader did not work anymore. It was not loading the exploit. Getting stuck. Getting a blank page etc.
And as I always do I invested some time to figure some things out. I mean: computers are stupid and i'm in charge.

What I did was I went through all of the discussion threads:
[v0.5.0] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/15
[v0.5.1] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/17
[v0.5.2] https://github.com/itsPLK/ps5-webkit-autoloader/discussions/21

Perhaps a solution for you:

"On firmwares 7.00–13.60 (Relapse / Poops), the autoloader uses a custom version of elfldr that only accepts connections from the PS5 itself (localhost). This improves security by preventing unauthorized devices on your network from sending payloads to your console. On firmwares 1.00–5.50 (umtx2), the stock elfldr is booted.

If you want to use a "normal" ELF Loader that allows sending payloads from any device, you can simply load it through Payload Manager.

Alternatively, if you are using a manual config file (autoload.txt):

Place your custom ELF Loader (e.g. elfldr.elf) in the ps5_autoloader directory.
Add elfldr.elf to your autoload.txt.
Note: If you are loading other payloads right after elfldr.elf in your autoload.txt, add a sleep command immediately after it (like !4000 to sleep for 4 seconds) to give the new ELF Loader time to start up and listen before subsequent payloads are sent."

https://github.com/ntfargo/Relapse-Exploit/blob/main/payloads/elfldr-ps5-1360.elf

And etaHEN:

https://github.com/ntfargo/Relapse-...9ae9e8df214da37271290b13e/payloads/etaHEN.elf

This was not my issue. I revolved my issue this way:

My personal solution
1. Deleted the webkit autoloader application.
2. Cleaned/cleared the cache and deleted the browser cookies
3. Iinstalled v0.5.2 again.
4. After a reboot it worked again.

So I rebooted 4 times and 4 times it worked again. Don't know about the 5th boot and onwards lol... Guess I'll check tomorrow again.
That was the fix thank you!

What a silly change
 
  • Like
Reactions: flopsy

Site & Scene News

New Hot Discussed User Submitted