Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


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

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


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


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


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

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

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


Useful Applications:
FPKG: 3.00-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-12.70 is required for the webkit exploit.

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

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

    Exploiting 7.00-8.60:

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

    Exploiting 7.00-12.00 (-13.60 SOON):

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

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

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

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


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

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

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

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

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

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

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

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

    LUA Loader: HERE or HERE

    Auto LUA Loader Fork: HERE

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

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

    Incompatible LUA games:

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

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

  4. Requirements:
    PS5 console must be on 4.30-12.70 and previously activated through PSN or fake activated to use the YouTube app, unless you're restoring a backup.
    (Note: restoring a backup will factory reset your console).

    Information:
    If updating and older installation, download the latest download0.dat > use FTP or PS5 Explorer to place it in the user/download/PPSA01650 folder.

    Preparation:
    Download the Y2JB_backup_X.X(4.03) if you're on 4.03-12.40, or the Y2JB_backup_X.X(12.20) if you're on 12.60 or higher from HERE
    On PC: format a USB 3.0 HDD to exFAT, and copy the PS5 folder from the backup to the root, and put the latest nanodnf.efl from nanoDNS to the root too.
    On console: go to [Settings] > [System] > [System Software] > [Back up and Restore] > [Restore] > select the y2JB back up & let it install (the console will reboot when complete).
    (Note: The exploit will now be accessible under the [MEDIA] tab)

    Exploiting:
    Going to [Settings] > [Network] > [Settings] > [Set up Internet Connection] > [Set up Manually] > set up a wireless or LAN connection > change [DNS Settings] to manual > change [Primary DNS] to 127.0.0.1 > click [Done] > open the [YouTube App].
    (Note: Ignore and internet connection issue warnings)

    Firmware up to 10.01 will use Lapse Kernel Exploit. Firmware 10.20-12.70 and above will use P2JB and could take up to an hour.

    You can send payloads using netcat GUI to PS5's IP Address & port 9021.

    You can swap the download0.dat to itzPLK version for auto loading and payload manager in future (payload manager accessible through browser on 127.0.0.1:8084)

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

  5. Requirements:
    PS5 console must be on 4.30-10.01 and previously activated through PSN or fake activated. You will need a 256GB external HDD (minimum).

    Preparation:
    Download balenaEtcher
    Download the latest Extended Storage or M.2 Image (select your m.2's capacity)

    EXTERNAL DRIVE METHOD (Netflix_PS5_EU_Ext.7z):
    1a, On PC: connect your 256GB (min) USB drive to your Windows/Mac/Linux PC > extract the image to your computer > open Etcher > click [Flash From File] & select the extracted image *.zip > click [Select Target] & choose the external drive > Click [Flash!] & allow it to complete.
    (Note: 256GB is the smallest drive you can use)

    2a, On console: click [Settings] > [Storage] > [USB Extended Storage] > [Games and Apps] > press X on [Netflix] > select [NETFLIX] under items to move > select [Move] > move to internal storage & allow it to complete.
    (Note: The exploit will now be accessible under the [MEDIA] tab)

    INTERNAL DRIVE METHOD (Netflix.XXXXGB.7z):
    1b, On PC: connect the M.2 to your Windows/Mac/Linux PC > extract the image to your computer > open Etcher > click [Flash From File] & select the extracted image *.zip > click [Select Target] & choose the external drive > Click [Flash!] & allow it to complete.
    (Note: 4TB will take 80 mins, 2TB 45 mins, 256GB 10 mins)

    2b, On console: Power off the console > insert the M.2 SSD > power on the console > click [Settings] > [Storage] > press X on [Netflix] > select [NETFLIX] under items to move > select [Move] > move to internal storage & allow it to complete.
    (Note: The exploit will now be accessible under the [MEDIA] tab).

    Exploiting:
    1a, for consoles 10.01 and below, on console: go to [Settings] > [Network] > [Settings] > [Set up Internet Connection] > [Set up Manually] > set up a wireless or LAN connection. Go to Proxy > change [Automatic] to [Manual] > enter Address: 172.105.156.37 & port: 42069 > click [Done] > open the [Netflix App].
    (Note: Ignore and internet connection issue warnings)

    1b, for consoles 10.20-12.70, COMING SOON.

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

  6. Important:
    YARPE works from 4.30 to 12.70 (9.00 - 12.07 via P2JB)
    (A compatible PS4 game is required to launch the exploit on PS5. See below)

    Requirements:
    PS5 console must be on 4.30-10.01 to use this exploit.

    Exploiting:
    coming soon

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

  7. Requirements:
    PS5 console must be on 4.30-12.70 to use this exploit. SWRR

    Exploiting:
    coming soon

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


  8. [UPDATED]
    No longer needed if using latest WebKit (to 13.60) or BD-JB (to 13.42)!


    Important:

    This method modifies the BD-J stack to allows BD-JB entry point to be re-enabled on consoles up to 13.60, for convenience only.

    Very Important:
    This method requires your console to be jailbroken by another method first to gain access to alter the files.

    https://github.com/Gezine/BD-UN-JB

    Preparation:
    Burn the ISO to a blank Blu Ray, insert it into the jailbroken console. Send the bdj_unpatch.elf to elfldr using netcat GUI to PS5's IP Address & port 9021 to unpatch BD-J.

    (NOTE: DO NOT REINSTALL/UPDATE FW, IT WILL WIPE THE PATCH AND LOSE BD-JB)


Once jailbroken it is recommended to run KSTUFF LITE and SHADOWMOUNTPLUS at minimum to get you up and running.
(ShadowMountPlus: is an automated background auto-mounter payload for jailbroken PS5 consoles. Detects, mounts, and installs game dumps from internal or external storage, with support for UFS, exFAT, PFS, and nested compressed PFS containers)

Additional Information:


Blocking Updated with nanoDNS:
Set primary DNS manually to 127.0.0.1. Send latest elf to BIN LOADER using netcat GUI to PS5's IP Address & port 9021.

PS4 GAME INFORMATION:
OFW 1.xx cannot run PS4 games.
OFW 2.xx runs PS4 games up to 8.03

OFW 3.xx runs PS4 games up to 8.52
OFW 4.xx runs PS4 games up to 9.04
OFW 5.xx runs PS4 games up to 9.60
OFW 6.xx runs PS4 games up to 10.50

OFW 7.xx runs PS4 games up to 11.00
OFW 8.xx/9.xx runs PS4 games up to 11.50
OFW 10.xx runs PS4 games up to 12.00

OFW 11.xx runs PS4 games up to 12.50
OFW 12.xx runs PS4 games up to 13.00
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,
would anyone be interested in giving the new ghost control and its toolbox a beta test ? It works on my 5.5 console but other firmwares quickly introduce bugs
On firm 10.20 using the previous GC version. Let me know how i can help

Edit: can test with 8bitdo ultimate 2, easysmx x05 and bunch of other controllers.
 
It’s only a “hassle” if they’re just telling Claude how to code and don’t truly understand how things work or what they’re doing. A real dev does and can explain. We see it in the MiSTer community all the time. Devs breaking down how things work and why. Hell, even with systems previous to this when we had actual devs in the scene and not a bunch of vibe coding bounty hunters, we always seen explanations and videos of how things worked and how they got there.

I know kissing ass is the norm here and you people want to normalize this kind of thing, but I’m not doing it.

You wonder WHY legit devs are leaving this scene? Because it’s full of toxic vibe coders who just type a few things into Claude and use their social media pages to gain clout and attention. I been in various scenes since the Dreamcast era and I’ve never seen a scene as toxic and inexcusable as this one.

Both these vibe coders and the people that worship them. I respect people who actually put in the work. I can tell a vibe coder apart from a legit programmer and congratulations.

You failed.
Post automatically merged:


That’s not what I said.

I explained why it’s not possible since none of these supposed “devs” can explain why it’s not possible yet. I gave them a chance to explain, they didn’t. So I did.

I knew the answer, I was waiting for them to explain it.
Another reason information isn’t being shared early in regards to this stuff

Is if someone(a vibe coder) decides to jump the gun and beat someone to the punch (which is fine ofc) is because a lot can go wrong on this level .. by accident or on purpose

For example I bricked 2 consoles and was able to trace it back reliably to make a payload that purposely bricks consoles. Now I would never share this but with information ark and those other devs know

Anyone with a half a brain can read between the lines and recreate it. Give us a pikabrick situation.

Also with how complicated a53 is, any write up ark would give I’m sure would also be not 100% accurate in a week or 2s time either.

I was helping him briefly, it has happened several times. Anything wr thought that we knew. We where sorely mistaken and it was a honey pot. Nothing is being worked on from plaintext. It’s watching logs and throwing the dumps into ghidra and hoping to learn and recreate their flow

It’s not a deep conspiracy there a lot of moving parts and it’s a fickle mistress (a53)

Post automatically merged:

On firm 10.20 using the previous GC version. Let me know how i can help

Edit: can test with 8bitdo ultimate 2, easysmx x05 and bunch of other controllers.
Please message me
 
It’s only a “hassle” if they’re just telling Claude how to code and don’t truly understand how things work or what they’re doing. A real dev does and can explain. We see it in the MiSTer community all the time. Devs breaking down how things work and why. Hell, even with systems previous to this when we had actual devs in the scene and not a bunch of vibe coding bounty hunters, we always seen explanations and videos of how things worked and how they got there.

I know kissing ass is the norm here and you people want to normalize this kind of thing, but I’m not doing it.

You wonder WHY legit devs are leaving this scene? Because it’s full of toxic vibe coders who just type a few things into Claude and use their social media pages to gain clout and attention. I been in various scenes since the Dreamcast era and I’ve never seen a scene as toxic and inexcusable as this one.

Both these vibe coders and the people that worship them. I respect people who actually put in the work. I can tell a vibe coder apart from a legit programmer and congratulations.

You failed.
Post automatically merged:


That’s not what I said.

I explained why it’s not possible since none of these supposed “devs” can explain why it’s not possible yet. I gave them a chance to explain, they didn’t. So I did.

I knew the answer, I was waiting for them to explain it.

We wouldn't have Jordy WebKit We're it not for use of "AI" assistance. I think the tool has it's place like any other. Of course better if dev has background in coding.

I have watched ps5 scene for years and let me tell you, there are all kinds of reasons Devs have left. Sometimes it toxic user, sometimes it's in-fighting and bad behaviour of other Devs e.g ego, stealing code,etc. List goes on....

I just laugh when scene is turned into politics or one group blaming another. To much hypocrisy and blame to go around.

It's mostly a symbiotic relationship. Devs get to do research while receiving some donations & possible Job opportunities while User gets a Jail broken device. I might be wrong but that was my basic interpretation.
 
Last edited by AlphaBravo,
  • Like
Reactions: leorod199
Anyone using onionhen, do you always get the onionhen shortcut in the top right of the xmb like in modded warfares video?
I'm on 6.02 and it seems any payload that tries to put a shortcut up there, fails to do so.
Yeah, i always get the icon on top right. Firm 10.20
 
Another reason information isn’t being shared early in regards to this stuff

Is if someone(a vibe coder) decides to jump the gun and beat someone to the punch (which is fine ofc) is because a lot can go wrong on this level .. by accident or on purpose

For example I bricked 2 consoles and was able to trace it back reliably to make a payload that purposely bricks consoles. Now I would never share this but with information ark and those other devs know

Anyone with a half a brain can read between the lines and recreate it. Give us a pikabrick situation.

Also with how complicated a53 is, any write up ark would give I’m sure would also be not 100% accurate in a week or 2s time either.

I was helping him briefly, it has happened several times. Anything wr thought that we knew. We where sorely mistaken and it was a honey pot. Nothing is being worked on from plaintext. It’s watching logs and throwing the dumps into ghidra and hoping to learn and recreate their flow

It’s not a deep conspiracy there a lot of moving parts and it’s a fickle mistress (a53)

Post automatically merged:


Please message me
I have a LOT of controllers, I have lost the count of them all, lots of NSO ones, maybe near a dozen 8bitdos, a couple of gulikit kingkongs, ps3, ps4, ps5, xbox,... a lot. I am studying a masters degree and also work 8h a day, so my time is on a period by period basis, so to say, but if I can help...

By the way, I envy you, ArkSama and you both; hopefully I'll learn enough do do some small first step apps/payloads and we shall see from that...
 
  • Like
Reactions: bn2soldier
Another reason information isn’t being shared early in regards to this stuff

Is if someone(a vibe coder) decides to jump the gun and beat someone to the punch (which is fine ofc) is because a lot can go wrong on this level .. by accident or on purpose

For example I bricked 2 consoles and was able to trace it back reliably to make a payload that purposely bricks consoles. Now I would never share this but with information ark and those other devs know

Anyone with a half a brain can read between the lines and recreate it. Give us a pikabrick situation.

Also with how complicated a53 is, any write up ark would give I’m sure would also be not 100% accurate in a week or 2s time either.

I was helping him briefly, it has happened several times. Anything wr thought that we knew. We where sorely mistaken and it was a honey pot. Nothing is being worked on from plaintext. It’s watching logs and throwing the dumps into ghidra and hoping to learn and recreate their flow
And that’s sadly part of my point. I’m more wanting explanations to help others so we don’t get hundreds of people wanting free shit. I’m trying to explain why things aren’t possible at the moment and how they work.

But like you explained in this scene, it is hard to explain things because then someone could take that and use it for their own benefit instead of working together as a community. And a big reason of that is all these bounty programs. Sony has literally made a community where we’re all attacking each other instead of working together with what we know. Because the first one to the dance gets the 10 grand or 25 grand, whichever they pay out. I completely get that. Don’t like it, but I completely get it.

Believe it or not, I’m in the middle. I understand the frustration from the average user, but I also know how tiring it is to answer every little thing or comment. I noticed lots of times we’re actually on the same side, but because I’m not one to accept excuses or to be more blunt, it doesn’t seem that way. I hold accountability. I always have.

If Ark would just say, hey, look, it’s not possible right now because the current exploit doesn’t allow us to do that. That’s fine. But he went on his social media talking about GTA VI, and all of a sudden everyone’s confused. So that’s why I asked for the explanation.

But when you just use LLMs instead of actually learning how to code and or understanding how the hardware works, it’s very easy to give misinformation. So that’s a problem too.
 
I have a LOT of controllers, I have lost the count of them all, lots of NSO ones, maybe near a dozen 8bitdos, a couple of gulikit kingkongs, ps3, ps4, ps5, xbox,... a lot. I am studying a masters degree and also work 8h a day, so my time is on a period by period basis, so to say, but if I can help...

By the way, I envy you, ArkSama and you both; hopefully I'll learn enough do do some small first step apps/payloads and we shall see from that...
Hey anything you can offer to help
Would be appreciated! I understand life comes first ofc so anything you can try is much appreciated please PM me


As for the small steps, don’t lose hope. 9 months ago I didn’t know Shit about fuck. SonicISO was spoon feeding me on how to even restore my fw or get backports installed 🤣

We all gotta start somewhere but that is where the community’s power shines ! I’m always happy to help you (or anyone else) however I can

If it wasn’t for the community I wouldn’t have learned a single thing and would have stopped at one console lol
 
By the way, I envy you, ArkSama and you both; hopefully I'll learn enough do do some small first step apps/payloads and we shall see from that...
Here’s a piece of advice: AI is good as a testing tool or an assistant. But the programming and actual work should come from you. Start small and only get more technical when it and when you feel confident enough. You’re gonna fuck up. Probably many times. But keep at it. And if something is frustrating and you hit that brick wall, it’s okay to leave it and come back. The answers always come when you aren’t looking. Like finding a partner in real life.
Post automatically merged:

We wouldn't have Jordy WebKit We're it not for use of "AI" assistance. I think the tool has it's place like any other. Of course better if dev has background in coding.

I have watched ps5 scene for years and let me tell you, there are all kinds of reasons Devs have left. Sometimes it toxic user, sometimes it's in-fighting and bad behaviour of other Devs e.g ego, stealing code,etc. List goes on....

I just laugh when scene is turned into politics or one group blaming another. To much hypocrisy and blame to go around.

It's mostly a symbiotic relationship. Devs get to do research while making some donations & possible Job opportunities while User gets a Jail broken device. I might be wrong but that was my basic interpretation.
Assistance is fine. But when it’s used to completely code because the person doesn’t know what they’re doing, that’s a problem. It’s great to help test a theory, but not to program with.
 

PS5 RetroArch — Alpha 2 🎮​

This release adds PPSSPP, the first core that renders on the PS5's GPU. It runs through PS5_Vulkan with its JIT enabled. RetroArch also now outputs at 120 Hz when your display supports it.

✨ What's new​

  • PPSSPP (PlayStation Portable), hardware-rendered. God of War: Ghost of Sparta and Yu-Gi-Oh! GX Tag Force are tested at 10× internal resolution (4800×2720) with 16× anisotropic filtering. Both run at full speed with correct
    colours.
  • 120 Hz output, with a 60 Hz fallback. Cores that run at 60 FPS keep their normal speed at 120 Hz.
  • Save states and fast-forward work, including in PPSSPP. Loading a PPSSPP save state dropped from about 20 seconds to a fraction of a second, and creating one no longer freezes the game.
  • Closing content and loading another game works reliably, including closing a PSP game and opening it again.
  • Smoother gameplay. Logging and shader work no longer stall frames.
  • The last frame stays on screen while the video driver reinitialises, instead of going black.
  • Fixed a crash when starting Yu-Gi-Oh! GX Tag Force and other games that check free disk space.
Link: https://github.com/mihawk-99/PS5_RetroArch/releases/tag/v0.2.0-alpha.2
 

PS5 RetroArch — Alpha 2 🎮​

This release adds PPSSPP, the first core that renders on the PS5's GPU. It runs through PS5_Vulkan with its JIT enabled. RetroArch also now outputs at 120 Hz when your display supports it.

✨ What's new​

  • PPSSPP (PlayStation Portable), hardware-rendered. God of War: Ghost of Sparta and Yu-Gi-Oh! GX Tag Force are tested at 10× internal resolution (4800×2720) with 16× anisotropic filtering. Both run at full speed with correct
    colours.
  • 120 Hz output, with a 60 Hz fallback. Cores that run at 60 FPS keep their normal speed at 120 Hz.
  • Save states and fast-forward work, including in PPSSPP. Loading a PPSSPP save state dropped from about 20 seconds to a fraction of a second, and creating one no longer freezes the game.
  • Closing content and loading another game works reliably, including closing a PSP game and opening it again.
  • Smoother gameplay. Logging and shader work no longer stall frames.
  • The last frame stays on screen while the video driver reinitialises, instead of going black.
  • Fixed a crash when starting Yu-Gi-Oh! GX Tag Force and other games that check free disk space.
Link: https://github.com/mihawk-99/PS5_RetroArch/releases/tag/v0.2.0-alpha.2
I usually don’t use emulators on console, but seeing PSP in 10x, I gotta give that a shot.
 
Hey anything you can offer to help
Would be appreciated! I understand life comes first ofc so anything you can try is much appreciated please PM me


As for the small steps, don’t lose hope. 9 months ago I didn’t know Shit about fuck. SonicISO was spoon feeding me on how to even restore my fw or get backports installed 🤣

We all gotta start somewhere but that is where the community’s power shines ! I’m always happy to help you (or anyone else) however I can

If it wasn’t for the community I wouldn’t have learned a single thing and would have stopped at one console lol
The thing is I have a lot of x86(-64) experience ( 25+ years ) and I do lowlevel stuff for a living, but I have to get going in the PS5/FreeBSD/... environment O: ) Good to know there's devs in the scene that help others though :)

P.S.: You have a new Patreon member :)
 
The thing is I have a lot of x86(-64) experience ( 25+ years ) and I do lowlevel stuff for a living, but I have to get going in the PS5/FreeBSD/... environment O: ) Good to know there's devs in the scene that help others though :)

P.S.: You have a new Patreon member :)
If/when you begin

I recommend learning from the etahen source code. LM did an amazing job and covered damn near anything you can think of in some aspect.

It’s how I learned the initial XMB patching protocol
 
The thing is I have a lot of x86(-64) experience ( 25+ years ) and I do lowlevel stuff for a living, but I have to get going in the PS5/FreeBSD/... environment O: ) Good to know there's devs in the scene that help others though :)

P.S.: You have a new Patreon member :)
If you have years of low level experience and are comfortable working with Linux and ARM processors, the MiSTer FPGA project is a good place to program too. Also being able to port those cores to things like the Analogue Pocket, Game Bub, and *bleh* M64.
 
Last edited by littlemisskittn,
its fake the exe is a rickroll and the files themselves dont work. Its the same ones that hve been posted several times
1790272825788.png


My response:

1790272874438.png


The amount of people who instantly forked it got me so hard.
 

Site & Scene News