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) (BD/Y2/NF/LUA/YARPE: 6.02 for Linux / 6.50 max)
7.XX = KEX: PS4/5 backups, no HV (
BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = KEX: PS4/5 backups, no HV (Y2/NF/LUA/YARPE)
10.01-12.70 = KEX: PS4/5 backups, no HV (
Y2/NF/LUA/YARPE)
13.XX = No KEX/UL only (Y2/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: Do not update past 12.00. P2JB can take over an hour to exploit on FW up to 12.70.


Hypervisor (HV):
Highest known HV exploit: 6.02
Highest theoretical HV exploit: 7.XX
Highest HV exploit: 1.00-4.51 (Cragson/Jordy) / 3.00-6.02 (TheFlow)
*unreleased/unimplemented

Kernel (KEX):
Highest public Release:
12.70
Highest known: 12.70 (P2JB)
UMTX2:
1.00-7.61 (*WK to 5.50 / BDJB to 7.61)
Lapse: 1.00-10.01
Poopsploit: 4.03-12.00
P2JB: 9.00-12.70 (*Use Lapse up to 10.01)

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-7.61 (Blu-Ray exploit + UMTX2, *8.00-13.20 via UN BD-JB + Poops to 12.00)
Webkit: 1.00-5.50 (PSFREE +UMTX2) (*up to 13.XX coming soon)
Mast1C0re: 1.00-7.61 (Depreciated for LuaC0re)
LuaC0re: 1.00-12.70 (Poops: 4.03-12.00/P2JB: 9.00-12.70)

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).


Useful Applications:
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: (3.00-6.02) HERE
Kldload (wip): 3.00-6.50 HERE
Full chain exploit: 1.00-4.51 (byepervisor) HERE (also built into etaHEN up to 2.7X)
PSN access: NEVER
Latest OFW: 13.40 (04/06/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:
DNS 1: 172.245.146.114
(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)

KEY SYSTEM UPDATES:

12.70 SYS MD5: 707B15B07085500EB90205565751ECC3 (Exploited + KEX)
10.01 SYS MD5: 68A31944C1867BF9643798FD1C14998E (Exploited + KEX)
7.61 SYS MD5: D5ECA8B171A8D7DF7BA225167F77E645 (Exploited + KEX)
6.02 SYS MD5: 17b271DE081EB6EB25DBF70CB73EF9E8 (Exploited + KEX/HV/Linux)
5.50 SYS MD5: EDB3513EC531B2BD28F3A0B52A82A54F (Exploited + KEX/HV/Linux)
4.51 SYS MD5: 1330B7BF63BF5C93D809B1EB1F4E1F01 (Exploited + KEX/HV/Linux)
4.03 SYS MD5: 3716E4E6E0D223CD94CD4A8E5BD4FB94 (Exploited + KEX/HV/Linux)
3.20 SYS MD5: (F62F0D595D3F00C213D674D4DB2A7E44 (Exploited + KEX/HV/Linux)

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 is required for 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:
    Enter https://zecoxao.github.io/luasauce/ or https://github.com/kmeps4/PSFree into google > "Click Jailbreak" or wait for it to complete.

    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-7.61 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. Important:
    This method modifies the BD-J stack to allows BD-JB entry point to be re-enabled on consoles up to 13.40, for conveninece 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


(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: PS5 FPKGs do not work. A hack for the A53 processor does not publicly exist to enable installing PS5 content as FPKG/PKG.

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

5: 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,
Ah, I see. In that case, do let me know and when the tool is out. ^^ Good luck figuring out where all your stuff is. :D
Would you (or anyone else reading this?) Mind giving this pull request a stress test? He added a lot of controllers!

https://github.com/StonedModder/Ghostcontrol-PS5-USB-Controller-Patcher/pull/5

Expands DS4-compatible coverage. Sony (0x054C) and HORI (0x0F0D) VIDs continue to match unconditionally; adds an explicit VID/PID table for 42 well-known third-party PS4-protocol devices in controller_ds4.c.

== Complete supported controller list (after this PR) ==

Sony:

  • DualShock 4 v1 (0x054C:0x05C4)
  • DualShock 4 v2 / Slim (0x054C:0x09CC)
  • DualShock 4 Wireless adapter (0x054C:0x0BA0)
  • STRIKEPAD PS4 Grip add-on (0x054C:0x05C5)
HORI (PS4-licensed):

  • HORIPAD 4 / 4 FPS / 4 FPS Plus
  • HORIPAD mini 4
  • HORI Fighting Commander 4 / Commander PS4 / Commander OCTA
  • HORI Fighting Stick mini 4 / Stick α / Real Arcade Pro 4
  • HORI TAC PRO / TAC4 mouse-keyboard adapters
  • Hori mini wired
  • HORI Wireless Controller Light
Mouse + keyboard adapters (enumerate as DS4 / HORIPAD):

  • XIM4 (enumerates as HORIPAD FPS Plus 4)
  • Cronus Zen in DS4 mode
Mad Catz: FightPad Pro PS4, FightStick TE S+ / TE 2 / TE 2+ PS4 Razer: Panthera / Panthera Evo, Raiju / Raiju 2 Ultimate (USB+BT) /
Raiju 2 Tournament (USB+BT), RAION Fightpad
Nacon: Revolution Pro Controller v1 / v2 / v3, Revolution Infinite /
Unlimited (+ wireless dongle), Revolution 5 Pro (PS4 mode,
wired + dongle), Daija Fight Stick, Asymmetric Controller
Brook / ZEROPLUS / Hitbox / EMIO: Brook Mars, Hitbox Arcade Stick,
EMIO PS4 Elite, ZEROPLUS P4 Wired variants, Armor 3 Pad PS4,
Game:Pad 4, generic P4 clones
Qanba: Drone / Obsidian / Dragon
Victrix: Pro FS / Pro FS V2 / Pro FS PS4-PS5
PowerA Fusion Fight Pad
Thrustmaster Eswap Pro
Astro C40
Armor 3 / Level Up Cobra
Venom Arcade Stick
"PS4 Fun Controller"

Xbox One / Series:

  • ALL Xbox One/Series controllers regardless of PID (detected by GIP interface descriptor SubClass 0x47 / Protocol 0xD0; covers official Microsoft pads, Series X/S, and Xbox-licensed third parties).
Nintendo / 8BitDo:

  • Nintendo Switch Pro Controller (0x057E:0x2009)
  • 8BitDo Pro 2 / Pro / etc. in Switch mode (matches VID 0x057E)
  • 8BitDo Native protocol (0x2DC8:0x310B)
Generic HID DInput:

  • Logitech RumblePad 2 (0x046D:0xC218)
XInput-mode PS4-style pads (Nacon Compact, Hori Fighting Stick mini 4 kai, Qanba arcade joysticks, Astro C40 in Xbox mode) route through the Xbox path - same physical hardware, different USB protocol.

== Tested on hardware ==

  • DualShock 4 v1 + v2
  • XIM4
  • Cronus Zen
  • Xbox Series X/S
  • Logitech RumblePad 2 (ancient, added for smoke)
 

Attachments

So.....you people are not going to believe this absolute fucking shit.....all the issues i was having getting the ffpfsc games working? It's because I forgot to put the elfs in the ps5_autoloader folder.......I was doing this for a long time and didn't realize it until I needed to actually update. So it was using the elfs off the actual DISC and not the ones on the USB. So, tried Astro Bot, MGS Delta, and Pragmata and all work fine so far. I wanted to get them working on the slim before trying the Pro because most of the APR titles dumped, I have already in legit form on my Pro and set for offline play. Me getting those to work wasn't a high priority like getting the ffpfsc to work. Because if the APR games had problems (like Spider-Man does giving me the offline error every time it tries to autosave and stutters galore), it's not an issue as most likely it's on my Pro legitimately if I want to play them. I can always swap out the APR emu if there's a new version I assume.

But yeah, double check your shit and don't be like me spending three days trying to make working files when they were fine all along, it's just that my fuck up caused the incorrect elf files to load.....

I feel like such a fucking idiot right now.....

BTW, kudos to the dude who linked me to the batch file because that wasn't working either, until I used Gemini to find there was an "updater" file on my computer causing the command prompt to close unless it was in admin mode, so I also had to fix my PC as well. Now, the batch file is working PERFECT and without needing to use my internal drive neither (as I only have 200GB out of 512GB and most of it claims to be program files, but that's another story I intend to find out).
 
It is seemingly impossible to beat Ratchet & Clank Rift Apart with an ampr_emu backup.

There's a mandatory section about halfway through the campaign that relies heavily on Insomniac's party trick of rapidity switching between environments by pulling data off the SSD. Unfortunately, backups have slightly longer load times, which makes this transition literally impossible to get past. You will begin falling while the game is loading and die every time.



This is running from a folder dump on an M.2 SSD. I also tried .exfat, but the load times for that are even worse. I don't know if there's a fix for this or if one is even possible, but I wanted to document this before someone else runs headlong into the same issue.
 
View attachment 577270

I already saw many posts on the internet thinking that they can run 1.6 on 13.00 ~ 13.40, BUT also thinking it's a KEX.
Imagine the disappointment when they get a port 50000 screen and have no clue how to handle it :rofl:

Anyway, I finished my little easy-peasy tutorial for the newest Y2JB.
I am using system backups since day one to jailbreak ps5 lol I didn't hack it manually lol .... but it as good practice specially that I have a pc next to my hacked ps5 lol
Post automatically merged:

I hope we get something else other than p2jb for y2jb 1.6
Post automatically merged:

The ps5 hacking scene right now: 🤣

 
Last edited by MohammedQ8,
It is seemingly impossible to beat Ratchet & Clank Rift Apart with an ampr_emu backup.

There's a mandatory section about halfway through the campaign that relies heavily on Insomniac's party trick of rapidity switching between environments by pulling data off the SSD. Unfortunately, backups have slightly longer load times, which makes this transition literally impossible to get past. You will begin falling while the game is loading and die every time.

View attachment 577308

This is running from a folder dump on an M.2 SSD. I also tried .exfat, but the load times for that are even worse. I don't know if there's a fix for this or if one is even possible, but I wanted to document this before someone else runs headlong into the same issue.
Oh, that is bad.. I have a similar issue with Spider.-man 2 on my M.2 SSD, but on USB is working more or less fine..
You can do 2 different test to resolve this issues:

1º Yes, .exfat is slow, but we have the new format ffpfsc (or something similar) so you can convert your .exfat dump to the new format where the image is compressed and the people said that is more faster reading because is less data to be read (because is compressed) than .exfat
2º Copy the files on USB and try there. I know, USB is slow, but on spider-man 2 even is more slow than m.2 it resolve the issues.
3º Wait for a new compress format that right now are in development (kraken)

Btw, How I can test this on my PRO? which mission is that?
 
  • Like
Reactions: _iggyman_
Good lord, i wake up and there is like a million posts! I srtill need my coffee to read this lot :D

Good to see that a dev version of the itsPLK autoloader V0.8 is out... i'll let the dust settle and try it when it's officially released....

@HS2005 you are right DEVS DON"T SLEEP :D (it's so underated lol)

@bn2soldier You made me realise I haven't backed up my 9.20 console which has a lot of saved game data on it... better make a back up of all the save data in case it throws a tantrum and a reset is needed....
 
OK, so I have zero issues on 12.70 using .ffpfsc. My setup (in order):

View attachment 577174

So I mainly convert from a .exfat to .ffpfsc. So I already got a proper / existing .exfat.
From I just drag and drop the file (.exfat or .ffpkg) into this script and wait: https://gofile.io/d/URLSAq

USB setup:
  • Place the files into a external device and place them into homebrew/. If you login to the FTP I would look like this: /mnt/usb0/homebrew/ (NVME speeds needed for loading times. SSD/HDD causes issues)
  • Give the files short names with no spaces. So game1.ffpfsc or game1.Ultimate.Edition.exfat (spaces and long names can give conflicts)
  • If you have over 15 games in a folder give SM+ some times for indexing
  • If you have previous installtions of a game. Always delete them first before installing a new game.
Github links:
ftpsrv: https://github.com/ps5-payload-dev/ftpsrv/releases/tag/v0.20
Garlic SaveMgr: https://git.etawen.dev/earthonion/garlic-savemgr/releases/tag/v1.82b
SM+: https://github.com/drakmor/ShadowMountPlus/releases/tag/1.6test15-fix2
kstuff: https://github.com/drakmor/kstuff-lite/releases/tag/1.2-dr-test1

PHU like the ftp server and Garlic are additional.

I'm pretty sure phu overlay isn't needed anymore since that version of kstuff lite includes trophy support (unless you're using phu overlay for something else...)
Post automatically merged:

question how much performance we lose if we kept kstaff on during gameplay? because some arp games requires always on kstaff
Which ones require that?
 
  • Like
Reactions: _iggyman_
Ah, ok. I see that now:

"We recommend not pausing kstuff on this title. 1st game start can take a while as apr emu is building its index."

I'm not sure how to keep kstuff unpaused short of just using the regular version as a standalone payload. Maybe launching from itemzflow instead of using shadowmount?

I have been dying to play Nioh 3, but so far there's no backport (although I suspect that maybe someone could create one from Wo Long's backport [or maybe Fatal Frame's backport whenever it comes out] considering they use the same engine). I'm on 9.60.
I am on 10.01 and want to update to 12.00 hack it first via p2jb and then via bdjb autoloader ... I mean even y2jb lapes fails few times it is not perfect.

also saros backport patch maybe caused sound issues when I play it from internal ssd
 
I am on 10.01 and want to update to 12.00 hack it first via p2jb and then via bdjb autoloader ... I mean even y2jb lapes fails few times it is not perfect.

also saros backport patch maybe caused sound issues when I play it from internal ssd
I would not do that. Updating is never a good idea. What happens if a hypervisor exploit that affects up to firmware 10 happens and you miss out on that? I would just wait for a backport of whatever game you want to play.

I'm also confused as to why you asked about Nioh 3 if you can't even play it lol
 
It is seemingly impossible to beat Ratchet & Clank Rift Apart with an ampr_emu backup.

There's a mandatory section about halfway through the campaign that relies heavily on Insomniac's party trick of rapidity switching between environments by pulling data off the SSD. Unfortunately, backups have slightly longer load times, which makes this transition literally impossible to get past. You will begin falling while the game is loading and die every time.

View attachment 577308

This is running from a folder dump on an M.2 SSD. I also tried .exfat, but the load times for that are even worse. I don't know if there's a fix for this or if one is even possible, but I wanted to document this before someone else runs headlong into the same issue.
What about test game in internal ssd ?
 
Stick with external, whats your autoloader saying also is it internal /data/autoloader or usb?
Only load...
pldmgr.elf (from USB)
then id suggest loading an ftp payload or etaHEN then checking your internal autoloader, pldmgr/payloads, and elf-arsenals config
if in doubt remove elf-arsenal completely (ftp) and restart ps5
autoload pldmgr (as above)
#1 - nanodns
#2 - backpork
#3 - shadowmountplus
#4 - +5 secs
#5 - etaHEN

or
autoload pldmgr
#1 - elf-arsenal

configure what you want in the settings eg (replace kstuff & smp in default locations) autoload backpork & nanodns

Finally your PS5 will more than likely crash and turn off 1/2/3 times before successfully jb and load your NEW config - It has a little temper tantrum but you should notice progression each time then should stabilize (speaking from my experience)

Remove your backup games ssd's and delete all the install game titles on your ps5 then replug ssd so when smp re-installs them they should work
For elf-arsenal I just had that in the autoload, otherwise I have it almost exactly as your example, just without backpork loaded separately.

I tried using just the payloadmanager to set things up with etahen, but it still reacts the same way.

I tried the ssd thing too, deleting all of them and let remount, but again even via webman in etahen they don't work. I'm wondering if SM+ has some temp folders somewhere too. I'm gonna go through with ftp like you said, but I'm gonna just start deleting any homebrew generated folders I find.
I have the same issue PS5 games stopped working out of no ware PS4 games and DLC still works all homebrew works this sucks. Are you using kstuff lite i am?
Yeah using latest kstuff lite 1.07, but I tried using the one built into etahen which I think was kstuff 1.04 but still the same issue where I could use it just fine before so I don't think it's kstuff related.

This is such a bizzare issue, I literally changed nothing and suddenly it just starts doing this. The only thing is that elf-arsenal forcefully updates itself so I'm wondering if that has fucked me up somehow.

Also to whomever it was (forgot the name sorry) asking about using gen 3 drives as the ps5 nvme, this video might be interesting to you. Turns out I was kinda correct, you can bypass the check using a backup.
 
I've been trying to figure out a new elf stack since I've not started up the PS5 for a few weeks.

Ultimately, whatever one that I try seems to have me coming back to just using etaHEN 2.6B (with latest kstuff lite), then autoloading ShadowMountPlus afterward via etaHEN/payloads. It really just works and allows me to have a native PKG installer for PS4 games or homebrew. Also, etaHEN's payload launcher is pretty easy to use in the etaHEN toolbox.

The only downside is that autoloading the etaHEN toolbox is kinda iffy sometimes. I think that there is a way to have it not autoload and just create a shortcut on the homescreen to load it as needed, is that true? I know that there is an Itemzflow button to do it, but I forget if it's possible with a shortcut on the homescreen.
 
It is seemingly impossible to beat Ratchet & Clank Rift Apart with an ampr_emu backup.

There's a mandatory section about halfway through the campaign that relies heavily on Insomniac's party trick of rapidity switching between environments by pulling data off the SSD. Unfortunately, backups have slightly longer load times, which makes this transition literally impossible to get past. You will begin falling while the game is loading and die every time.

View attachment 577308

This is running from a folder dump on an M.2 SSD. I also tried .exfat, but the load times for that are even worse. I don't know if there's a fix for this or if one is even possible, but I wanted to document this before someone else runs headlong into the same issue.
Let us know if you find solution to this
 
Oh, that is bad.. I have a similar issue with Spider.-man 2 on my M.2 SSD, but on USB is working more or less fine..
You can do 2 different test to resolve this issues:

1º Yes, .exfat is slow, but we have the new format ffpfsc (or something similar) so you can convert your .exfat dump to the new format where the image is compressed and the people said that is more faster reading because is less data to be read (because is compressed) than .exfat
2º Copy the files on USB and try there. I know, USB is slow, but on spider-man 2 even is more slow than m.2 it resolve the issues.
3º Wait for a new compress format that right now are in development (kraken)

Btw, How I can test this on my PRO? which mission is that?

I first tried moving the folder dump to USB. That loaded significantly slower, which resulted in this happening


Next I tried compressing the exfat image to ffpfsc and putting on the M.2 drive. That was even slower, resulting in the same problem occurring much earlier in the sequence.



These results are pretty much what I expected TBH.
 

Site & Scene News

Popular threads in this forum