Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


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

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

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


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


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

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

NOTE 1: A userland entry point (UL) chained to kernel exploit (KEX) is required to exploit your console at bare minimum.
NOTE 2: Consoles 7.00-13.60 should now use WebKit and RELAPSE (Recommended)


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

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

Preparing Your Console:


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


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

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

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

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

21.02-04.03.00.00-00.00.00.0.1

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

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

WARNING:

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

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

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

Select Your Jailbreak:


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


  1. Information:
    Firmware 1.00-5.50 or 7.00-13.60 is required for the webkit exploit.

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

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

    Exploiting 7.00-13.60:

    https://ntfargo.github.io/Relapse-Exploit/

    https://zecoxao.github.io/bagagwa/

    https://soniciso1.github.io/poopicker/

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

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


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

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

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

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

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

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

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

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

    LUA Loader: HERE or HERE

    Auto LUA Loader Fork: HERE

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

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

    Incompatible LUA games:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    Exploiting:
    coming soon

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

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

    Exploiting:
    coming soon

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


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


    Important:

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

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

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

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

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


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

Additional Information:


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

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

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

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

OFW 11.xx runs PS4 games up to 12.50
OFW 12.xx runs PS4 games up to 13.00
OFW 13.xx runs PS4 games up to 13.52
OFW 14.xx runs PS4 games up to 14.00


(Note: PS4 backported FPKGs also work perfectly on an exploited PS5 with Kstuff)


You can install free/demo PKGS (legit pkgs) via the debug pkg installer, provided you have all the files/json/licences required.
(Astro’s Playroom has no licences and can be installed and played from official pkgs and updated inline with your firmware)

Warnings:


1: Never enable IDU mode.
If you do, you will need to enter staff mode by holding L1 + L2 and tapping this combo: circle, cross, square, triangle, right D-Pad. Release L1 + L2, and you can access settings to exit IDU.

2: Try to stay on the lowest FW possible and wait for hacks on that firmware.

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

4: If you get stuck in a boot loop at the PS logo, the SNVS is corrupted (if the hash check fails on boot, this causes a “soft brick”). It’s not “bricked”. Simply reinstall your current firmware RECOVERY PUP in safe mode from USB: PS5 > UPDATE > PS5UPDATE.PUP.

Archived Information


 
Last edited by KiiWii,
Ok, now i understand. Unfortunately the 1.07 version only works up to 11.40 like fpkgs. So i will just wait until fpkg works for 13.xx, so xplorer gets updated to work with it native. Will do ftp until then. Was just convenient to quickly lookup something or transfer small stuff from usb etc.
Thanks for the help, found the Youtube xx.130 Version too.
Will try later though, have some work on the house to do first
That Youtube app can't be used in 13.40 or above fw. Use the ones I linked for 13.40 and above, use .030 for fw below 13.40.
Post automatically merged:

Thanks for the qzick tutorial and the link to Youtube Apps.
What i dont understand fully is what i exactly need to get Lady explorer to work on 13.42.
On my 4.03 i can use 1.05 without any extra elfs.
For 1.07 there was a link frw pages ago to a native version which works up to 11.6 without any extra elf.
So which version do i use On my 13.42 Pro, 1.05 or 1.07 ?
And preferably without any extra elf when possible.

Edit: @Inaki your linked youtube version shows xx.253 at the end, which i read here makes problems/doesnt work ?
So i need the xx.030 version it seems according to some posts here.
.253 is the one you need for 13.40 or higher. If you are below 13.40 you must use .030.
 
My guess would be a PS3 integration.

That would be great to see.

On a bit of a side note I’ve seen a lot of people criticize Sony for not releasing ps3 emulation on ps5 due to greed. But I remember when Digital Foundry looked at it, plenty of games did run perfectly but there does seem to be quite a lot of complications with SPU cell emulation which can slow things down.

I think certain titles will work great but I personally wouldn’t be hopeful of full backwards compatibility
 
".253 is the one you need for 13.40 or higher. If you are below 13.40 you must use .030."

Not in my experience. I tried using .253 and it didn't work at all. I had to use .30 on a 13.60 device. And it's now all working perfectly with that .030 version (100% success rate without hard lock). I'm working atm so I can't verify the version directly on the dashboard. Will do it in a few hours.
 
  • Like
Reactions: SonGoku78
I'm hoping for Switch 2 Emulation on Ps5. Long shot but seems only emulator missing on the console 😂
Well that's not to shabby as well. Can we at least play the upcoming Pokemon gamez :ha:
Post automatically merged:

That would be great to see.

On a bit of a side note I’ve seen a lot of people criticize Sony for not releasing ps3 emulation on ps5 due to greed. But I remember when Digital Foundry looked at it, plenty of games did run perfectly but there does seem to be quite a lot of complications with SPU cell emulation which can slow things down.

I think certain titles will work great but I personally wouldn’t be hopeful of full backwards compatibility
That was indeed the case. The PS3 has a whole different architecture. Now that we are in like a "AI/Code vibing age" things will speed up. For better and worse.
 
Not sure if this is of any help to anyone but there was a game I was only able to find in fpkg format.

So I was able to extract it with https://github.com/thanhsondev/PSVIETHOA-FPKG-Builder/
and build the .exfat file with https://github.com/pearlxcore/PS5PKGTool

Took me a few hours to find out the tool that would extract the fpkg.

PS5 PKG Tool can't extract fpkg files, while it seems to have this feature, it errors out everytime.
This does work but you need to manually insert
ampr_emu.index in the root of your fpkg dump folder
And insert both
LibSceAmpr.sprx
LibScePlayGo.sprx
Into fakelib folder

And use the latest shadowmount as can do game by game check box for fakelib

Wow haven't posted on gbatemp in ages 😘
 
  • Like
Reactions: peteruk and ViRGE
Tailscale update:

v0.6.0​

New​

  • Send files to the console with Taildrop. Send a file from any of your own devices (share menu on a phone, "Send with Tailscale" on a desktop, or tailscale file cp). It lands in /data/tailscale/received, the console shows a notification, and the status page lists it with a download link. Sending files from the console is not implemented.
  • Install updates from the status page. From the next release on, the update notice has an Install button. It downloads the release, checks that it is signed with this project's release key, and starts it; login and settings are kept. Nothing is installed without pressing the button. If your payload manager starts tailscale.elf at boot, put that file's path under Payload file to keep up to date in the settings so the update replaces it too.
  • "Only my own devices." A new setting limits who on the tailnet can reach the console (every forwarded port, Remote Play and the status page) to devices logged in as the same user. Other users' devices and devices shared into your tailnet are turned away. Off by default.
  • Key expiry warning. The page shows when the console's Tailscale key expires and warns two weeks ahead; the console shows a notification as well. To avoid expiry, choose Disable key expiry for the console in the Tailscale admin console.
  • A notification when a newer release exists, once per release, in addition to the notice on the page.
  • Start-up problems leave a trace. If the payload cannot start it now says why in a notification and in /data/tailscale/launcher.log. Until now a payload manager would simply show nothing. If Tailscale does not start on your console, please attach that file to your report.

Changed​

  • Click an address on the status page to copy it.
  • The device list no longer breaks words in the middle on phones.

Upgrading​

Replace tailscale.elf wherever you keep it, or send the new one to the ELF loader (port 9021) while the old one runs. The login and settings are kept. This is the last update that has to be done by hand.

tailscale.elf.sig is the signature the Install button checks; you do not need to download it. Full instructions are in the README.
Unofficial; not affiliated with Tailscale Inc. or Sony.

Link: https://github.com/holdmysocks/ps5-tailscale/releases/tag/v0.6.0
 
Does PS5X2 work with version 13.60? I tried to set it up over the weekend but couldn't. The icon didn't appear on the dashboard, and it didn't create any folders or files on the console.
 
  • Wow
Reactions: cearp
Caludeslop is taking over.
Post automatically merged:

If I dont set my dns to 127.0.0.2 the Y2JB wont work at all.
I made my own version of nanodns for that so that it listens to 127.0.0.1 and 127.0.0.2 so that I dont have switch it up all the time.
My PS5 is firewalled no way im taking it online.
Won't use Y2JB if it can't work offline.

Edit:
set dns 127.0.0.1 primary
set dns 127.0.0.2 secondary

This made Y2JB work again!!
 
Last edited by arson-tux,
  • Like
Reactions: TheStonedModder
Another one with credits stripped

Do yall notice the pattern? It has the same exact bugs and controller support again lol

Just slop ontop of slop

https://github.com/diegobarbosaa/OmniPad-PS5
Haven't tested this one, but the AnyPad does indeed react the same way to your earlier beta I tested on my 6.02 console, only with extra bugs and issues lol.

It is strange that it needs you to make secondary account per controller though, some kind of workaround to your code the ai they used couldn't figure out how to "improve" on?

Keep it up though dude, looking forward to seeing how you cook. I imagine these alts might get lucky and work properly on their own, but what's the chances that updates only come after yours do :rofl2:
My PS5 is firewalled no way im taking it online.
Won't use Y2JB if it can't work offline.
You could always self host, usually with one of the many types of esp32 boards that create a fake wifi connection. I used to do that on ps4 for the webkit. That way it's never actually connected to the internet, but it thinks it is.

NanoDNS on the other hand, hasn't failed me yet, so I've never had to worry with my ps5, even on wifi. I just set the dns to 127.0.0.1 on first setup.

I'm using that in place of my PiHole, since the console will never go online until nanoDNS activates and blocks all the psn servers. Much safer than it was on ps4 back in the day, plus nanoDNS is on ps4 too.
 
Last edited by Rasa39,
Haven't tested this one, but the AnyPad does indeed react the same way to your earlier beta I tested on my 6.02 console, only with extra bugs and issues lol.

It is strange that it needs you to make secondary account per controller though, some kind of workaround to your code the ai they used couldn't figure out how to "improve" on?

Keep it up though dude, looking forward to seeing how you cook. I imagine these alts might get lucky and work properly on their own, but what's the chances that updates only come after yours do :rofl2:
Zero considering I’m not open sourcing again for this exact issue lol

I’m trying to cool for yall I want this to be the ultimate solution. Again I’m not trying to be a dictator on this specific homebrew

If they where doing proper forks, giving proper credit and actually fixing and innovating I wouldn’t be annoyed at all

But to summarize why the wait will be worth it

But it will have, all built into a native appp

ALL xinput and dinput controllers supported

Configuration wizard for setting up controllers and generating profiles or rebinding (shareable) if a controller appears as unknown

3d interactactable ds5 to show your gyro and inputs in real time during that.

Macros

Light pad toys for playing with the color and making animations

Rumble motor controls to spice up the night

Macros

Bluetooth audio

Bluetooth controllers

And my favorite network contorllers. Meaning we use a pc or esp32 or pi anything to remotely control or trigger macros

I plan to use that last one for my 10k twitch account for twitch plays Astro bot :)
 
That Youtube app can't be used in 13.40 or above fw. Use the ones I linked for 13.40 and above, use .030 for fw below 13.40.
Post automatically merged:


.253 is the one you need for 13.40 or higher. If you are below 13.40 you must use .030.

".253 is the one you need for 13.40 or higher. If you are below 13.40 you must use .030."

Not in my experience. I tried using .253 and it didn't work at all. I had to use .30 on a 13.60 device. And it's now all working perfectly with that .030 version (100% success rate without hard lock). I'm working atm so I can't verify the version directly on the dashboard. Will do it in a few hours.

Yes, i read that on different places that .253 doesnt work for everyone and .030 seems a sure bet for 13.60.
Will try soon and report back
 
I wanted shared some more info / knowledge.

Problem:
So what I have enountered is when booting Resident Evil 9 Requiem (PPSA31246) and Pragmata (PPSA02530) when loading a backport. So when backport_fakelib=1 = active. 1 = true 0 = false you get error CE-107098-5. You then have to reconfigure your settings over and over. Bloody annoying.

Setting backport_fakelib=0 works for those games, but the ones who have a backport / make use of the fakelib2 folder won't run/boot anymore. Getting stuck. Freezes etc. etc. So below is the solution to get both scenario's working.

Solution:
Code:
backport_fakelib=1
fakelib_exclude=PPSA31246
fakelib_exclude=PPSA02530

Place the games directly under there. Apprently placing it at other positions will result in the same error.
The config.ini can be found in: /data/shadowmount/

This is the whole block:

Code:
# Sandbox fakelib support:
# 1/true/yes/on  -> mount fakelib2 when present, otherwise fakelib, into common/lib
# Installed PKGs use only their own app0/fakelib2 or app0/fakelib; external
# backport directories are not overlaid on app0 and are not used as sources.
# 0/false/no/off -> disable fakelib overlays
# Default: 1
backport_fakelib=1
fakelib_exclude=PPSA31246
fakelib_exclude=PPSA02530

Hope this helps.
 

Site & Scene News

New Hot Discussed User Submitted