Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


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

6.XX = PS4/5 backups (KEX+HV+Linux) (BD/Y2/NF/LUA/YARPE: 6.50 max)
7.XX = PS4/5 backups (KEX+HV+Linux) (
WK/BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = PS4/5 backups (KEX+HV+Linux) (WK/BD/Y2/NF/LUA/YARPE)
10.01-12.70 = PS4/5 backups (KEX+HV+Linux) (
WK/BD/Y2/NF/LUA/YARPE)
13.XX-13.60 = PS4/5 backups (KEX+HV+Linux) (
WK/BD(13.42)/Y2/LUA/YARPE)
14.XX = No public KEX, HV/A53 patched in 14.20, 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: 13.60
Highest unreleased HV: 14.00
*unreleased/unimplemented


Kernel (KEX):
Highest released KEX:
13.60 (ReLapse)
Highest unreleased KEX: 14.10 (Gezine)
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) (14.XX SOON)
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-13.60) HERE
Kldload (wip): 3.00-6.50 HERE
PSN access: NEVER
Latest OFW: 14.20 (21/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.42
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,
1793259248534.png


kstuff1.13-fpkg-dr-test7-restmode.elf
 
Was rest mode not working up, until now?
Well not for the regular (exfcat etc.) formats. Rest mode works. This only affects fpkg.
Post automatically merged:

So you saying I don't need that ESp32 thingy?
You can use it, but it's not needed. Y2JB is a all-in-one solution. Make sure to also use https://github.com/Epinorr/y2jb-update-blocker/releases/tag/v1.0.2

Setting a local host address (class A) so 127.0.0.1 or 127.0.0.2 is pretty much enough.
Never has any casses where something accidently updated like a game updayte, PS5 system update or homebrew update.

I don't use or make use of a ESP32 device due to having the settings above ^^.

Post automatically merged:

EDIT: Nvm. These have already been answered. B-)
 
Last edited by HS2005,
Nope; no external hardware is needed. Y2JB is completely self-contained.
How come?? You still need a network connection. Even without internet. ESP is doing just that. Allowing you to jailbreak without real internet. Its 100% sure that you wouldnt update with it. Using DNS or blocking your console on the router its working but there is a small chance that will update. ESP is 100% offline solution. Or maybe i read it wrong but Removed network log server check its just making it faster not disabling need of network.
 
Can i ask the brains trust, if i am not too fussed about linux, would i be mad to use my 13.6 Pro as my JB machine, and update my 7.61 original disc to use online with family/friends?
 
I'm on 5.5 and use the offline psviethoa webkit autoloader, which somebody recommended here, plus payload manager.

In comparison with the webkit on my ps4 pro (9.00), it's rock solid. From 50 attempts, i only have 2-3 fails.

But if there is better webkit autoloader, please tell me :)

Because the autoloader is offline by now, I attach the file.

I would like to see a evaluation of all different jailbreak ways and which one is the most stable one, for the different entrypoints :)


I’ve been using Jordy’s auto jailbreak. Which automatically jailbreaks the console, it has only failed to run maybe 1 or 2 times in about 100 attempts so it is insanely stable. And also since the console is set to log in automatically I just turn the PS5 on and everything is handled itself. Makes it much easier if for example my gf wants to play :D
 
  • Like
Reactions: _iggyman_
Well not for the regular (exfcat etc.) formats. Rest mode works. This only affects fpkg.
Post automatically merged:


You can use it, but it's not needed. Y2JB is a all-in-one solution. Make sure to also use https://github.com/Epinorr/y2jb-update-blocker/releases/tag/v1.0.2

Setting a local host address (class A) so 127.0.0.1 or 127.0.0.2 is pretty much enough.
Never has any casses where something accidently updated like a game updayte, PS5 system update or homebrew update.

I don't use or make use of a ESP32 device due to having the settings above ^^.

Post automatically merged:

EDIT: Nvm. These have already been answered. B-)
Is that update blocker actually needed ? In my experience with this:

- At first I had the YouTube app updated every now and then and had to use webkit to redo the download0.dat in /user/downloads/PPSA0165x/. I was installing without using y2jb_update.zip, I just overwrote the download0.zip.

- After some of these I learned how to mod appinfo.db and the .json files and did that and that was a solution, weeks without losing y2jb or without YouTube app updates.

- Then I saw comments where the theory was doing not only the appinfo.db and json files but also de app.db file, so I changed that too ( using the proper sql lite db editor and using the sql sentences described and so on, I even read the state after the sentences executed and made sure all was good )... BUT, the YouTube app soon updated after this "change all things", so it was theoretically thorough but it happened that somehow, maybe changing the app.db or whatever, somehow triggered a renewal or... the fact is the thorough change version led to a YouTube app update soon after. And I redid the whole reinstall + editions again and again and I always got it working fine but soon after the YouTube app updated.

- I even wrote a payload called iwY2JBs - as in I Want You 2 Just Be Still, lol - ( I still have it, mixed coding, me + Claude, it does actually work fine to do the theoretical changes on any combination of PPSA0165x apps, their json and db files, if anyone is interested... ) but I didn't publish it because of what I say, if I do the thorough changes YouTube app will update soon after. Again, many complete cycles of reinstall, use the payload to have all edited, have Y2JB working fine and like... even as short as minutes after, boom, YouTube app updated again :O.

- Then, after seeing people saying they didn't do anything for the anti-update, seeing they just installed the Y2JB as described and never got it updated, I thought: hmmm, you always install via download0.dat overwrite only, what if the y2jb_update.zip cycle is needed ? what if the initial download0.dat carries the exploit thing, of course, but can't actually be the final version of file contents/descriptions/permissions/... and the y2jb_update.zip cycle is needed so that in the first update, it can now change those contents/descriptions/permissions/... and let them in a state that is protected against updates ? Well, I started updating my Y2JB by doing the download0.dat overwrite PLUS the y2jb_update.zip in /data/ and first update cycle, as described. Result ? well, it's been a couple of weeks with no YouTube app updates.

So... all this is empirical and not extensive enough, but until I see some contraexample... the thing is that a lot of people who installed the Y2JB via the described means and did the y2jb_update.zip update cycle have said they still have their YouTube app intact, no need for any editing or protective payloads... Also, itsPLK and others don't say anything about protecting those...

Anyway, we shall see, but there's some bits more we don't completely know that would explain these quirks, for sure...
 
Last edited by Inaki,
Is that update blocker actually needed ? In my experience with this:
Not needed. Just an option as I mentioned. I did it because I sometimes switch the full internet access and local domain. This tool prevented the YT being updated. When I click on the YT app when having full internet access it won't update so that helps. It's an easy tool to use. Just for convenience...
Post automatically merged:

How come?? You still need a network connection. Even without internet. ESP is doing just that. Allowing you to jailbreak without real internet. Its 100% sure that you wouldnt update with it. Using DNS or blocking your console on the router its working but there is a small chance that will update. ESP is 100% offline solution. Or maybe i read it wrong but Removed network log server check its just making it faster not disabling need of network.
Yeah I just tested that.
Hitting the switch that allowed no connection at all and run Y2JB. It will give a message that no kernel exploit has been loaded. So that's not going to work. Though I would try looking at the recent updates / developments. Well seems still sticking to the old formula is the way to go.
 
Last edited by HS2005,
  • Like
Reactions: _iggyman_ and Inaki
Not needed. Just an option as I mentioned. I did it because I sometimes switch the full internet access and local domain. This tool prevented the YT being updated. When I click on the YT app when having full internet access it won't update so that helps. It's an easy tool to use. Just for convenience...
Post automatically merged:


Yeah I just tested that.
Hitting the switch that allowed no connection at all and run Y2JB. It will give a message that no kernel exploit has been loaded. So that's not going to work. Though I would try looking at the recent updates / developments. Well seems still sticking to the old formula is the way to go.
Why cant NanoDNS block YT automatically? Nice feature would be to select what services to block (if now some dont want to block YT)
I have the ytblocker installed and i added the yt block lines manually in NanoDNS just for this.
 
Why cant NanoDNS block YT automatically? Nice feature would be to select what services to block (if now some dont want to block YT)
Why not report it as a feature. Mentioning improvements here won't help the cause.
I would suggest to submit your feature here: https://github.com/drakmor/nanoDNS/issues

I have the ytblocker installed and i added the yt block lines manually in NanoDNS just for this.

Yes you need to add IP addresses manually in the .ini file > /data/nanodns/nanodns.ini
For example for those who want to know:

Code:
[overrides]
*.playstation.com=0.0.0.0
*.playstation.com.*=0.0.0.0
playstation.com=0.0.0.0
*.playstation.net=0.0.0.0
*.playstation.net.*=0.0.0.0
*.psndl.net=0.0.0.0
playstation.net=0.0.0.0
psndl.net=0.0.0.0
# *.example.com=192.168.0.10
# exact.host.local=10.0.0.42

[exceptions]
feature.api.playstation.com
*.stun.playstation.net
stun.*.playstation.net
ena.net.playstation.net
post.net.playstation.net
gst.prod.dl.playstation.net
# auth.api.playstation.net
# *.allowed.playstation.net
Post automatically merged:

They released an update yesterday: https://github.com/premohq/PS5-ECAM/releases/tag/v5.1.0
Looking foreward into playing Switch games as well. I'm running Nintendo 3DS, Nintendo DS and Wii U games via this. Still use ProsperoEden for the Switch games.
 
I'm having a problem with the YouTube jailbreak. So I watched the modded warfare video a few days ago so I can move to the YouTube jailbreak, downloaded the update for 12.60+ and replaced download0.dat. I have 2 YouTubes on my system now.

Rebooted the console and opening YouTube. It glitches between the exploit foir a split second, then it just opens normal YouTube. And it does everytime when I try to open it. So I'm still stuck on this unstable webkit :(

My PS5 is on 13.00, I decided to stay on that since I had success and it's in rest mode now. But if a crash occurs, I'd like to use YouTube jailbreak from now on, which isn't possible for me since I don't know what went wrong.

I have another question though. By setting IP to 127.0.0.1 as seen for the YouTube jailbreak, can I still use Prospero Store and RetroAchievements hardcore mode for emulation? Otherwise this is also a no go.

Thanks.
 
Last edited by thekarter104,

Site & Scene News

New Hot Discussed User Submitted