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.22 (2/11/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.

Spoiler: Addresses to block to avoid updates:

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)

Spoiler: System Update Information

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

Spoiler

https://github.com/astrelsky/libhijacker

https://github.com/illusion0001/libhijacker

https://github.com/TheOfficialFloW/Presentations/blob/master/2022-hardwear-io-bd-jb.pdf

https://github.com/sleirsgoevy/bd-jb

https://github.com/psxdev/bd-jb

https://gbatemp.net/download/remount-system-with-write-permissions.37807/

https://github.com/john-tornblom/ps5-payload-sdk

https://github.com/john-tornblom/bdj-sdk/actions/workflows/bdjb.yml

 

[HS2005]

• keys (for cfw?)
• able to install real (encrypted) pkgs, just need to share the license/keys
  • would need to hack the licensing system (no idea what it involves myself)
  • we could then install real pkg updates straight from sony, not need to wait for them to be dumped
  • gives confidence on "clean" dumps, as the pkgs are untouched
  • backports / homebrew would still exist as fpkg I guess

but you're right, we're in a great position

G00d list.
This / last week we got Linux for 13.60 and Byepervisor Reborn.
So what's left is fpkg for 13.60. And at this stage it's just a nice to have (for me). Not even a must.

 

[regex101]

Most of these hosts they're choosing to use such as viking, akia, data etc... are absolute garbage in my humble opinion.

GoFile is free, fast, reliable.... i feel there are many others too, so why use such sketchy hosts... they're horrendous

Piracy sites choose most annoying file hostings to make people pay for "premium subscriptions". Part of these payments are then given back to uploaders.

They guys are not working for charity or some "stick it to sony" memes, or users convenience, you know. It is dirty business, nothing more.

 

[Inaki]

50K bounty for Jordy! OMG! What have i missed
So this is the Hypervisor bug for upto 13.60? This is epic!
Scene is on fire.... Can it even get any better than this?

Upto 14.00 ( and maybe tecnically upto 14.10 but not possible in practice because some side reason ).

 

[ThePSGuy]

Don't forget to set your DNS to 127.0.0.2 when using Y2JB. YouTube will update very fast if you have internet access.
You can also use https://github.com/Epinorr/y2jb-update-blocker/releases/tag/v1.0.2 when you are on 13.60 and load it as a extra measure.

Also for a back-up I would recommend installing the webkit autoloader: https://github.com/itsPLK/ps5-webkit-autoloader/releases/tag/v0.6.1.
If Y2JB has a breakdown or something else happens, at least you can exploit your system quickly again to make changes needed. I use this as my back-up.

I'm currently using 127.0.0.1, what is the difference? Aren't they both localhost?

Regarding a backup method, now that you mention it, do you know if the WebKit Autoloader uses the same Payload Manager installation as the Y2JB Autoloader? That could potentially answer my question about the BD-JB Autoloader.

Also, I think I won't bother with WebKit and just keep the BD-JB disc somewhere in case something goes wrong with Y2JB.

 

[HS2005]

I'm currently using 127.0.0.1, what is the difference? Aren't they both localhost?

Yes 127.x.x.x is localhost address. Also called a Class A IP address.

Regarding a backup method, now that you mention it, do you know if the WebKit Autoloader uses the same Payload Manager installation as the Y2JB Autoloader? That could potentially answer my question about the BD-JB Autoloader.

Also, I think I won't bother with WebKit and just keep the BD-JB disc somewhere in case something goes wrong with Y2JB.

Webkit autoloader uses the same Payload Manager. Just like Y2JB does.

 

[ThePSGuy]

Yes 127.x.x.x is localhost address. Also called a Class A IP address.


Webkit autoloader uses the same Payload Manager. Just like Y2JB does.

So I can just keep using 127.0.0.1 with Y2JB right?

About the Autoloader, I reckon it should take over fine from BD-JB then but I will report back in a few hours in case someone else is interested.

 

[HS2005]

So I can just keep using 127.0.0.1 with Y2JB right?

About the Autoloader, I reckon it should take over fine from BD-JB then but I will report back in a few hours in case someone else is interested.

I have used both but for example NanoDNS it's better to use 0.2. Also Gezin's advise is to set it to 127.0.0.2.

"Why is Setting DNS to 127.0.0.2 Required?
The DNS configuration is critical for Y2JB to function properly for two technical reasons:

1. Blocking PSN Connections: Setting the DNS to 127.0.0.2 (localhost) prevents the PS5 from reaching PlayStation Network servers. This blocks both the YouTube app and system firmware update prompts that would otherwise interfere with the exploit."

Just try it. If it does not work you are 1 number away to make changes. And indeed report your findings.

 

[Schweino]

So to clarify, garlic save manager can allow a higher version game save to work on a lower game version or is it just a conversion between different regions on the same game version, or can it do both?

In my case with Astro Bot: Both. Went from 1.18 US to 1.19 EU

Checked Sony's refurbished ps5, only ps5 slims are available, does anyone here knows which model comes and possible firmware version?

Which slim model is more reliable?

21xx is the best slim version (latest version with the matte top covers and matte middle bar). On the playstation direct site in Europe they state that the refurbished slims are the 21xx model.

I have been using the BD-JB autoloader from the itsPLK GitHub page for the past 5 months now and I'm considering switching to the Y2JB autoloader (from itsPLK aswell).

Is it simply going to take over my existing Payload Manager installation (and autoload sequence) when switching to Y2JB or should I be aware of something else?

yes, it will take over the existing payload manager

 

[HS2005]

EDIT: https://github.com/itsPLK/ps5-payload-manager/releases/tag/v0.6.3 just came out. Hotfix.

v0.6.3​

Changelog​

Bug Fixes​

• Hotfix for v0.6.2: fixed emojis not appearing on PS5.

Full Changelog: v0.6.2...v0.6.3

 

[ayechief]

So I can just keep using 127.0.0.1 with Y2JB right?

About the Autoloader, I reckon it should take over fine from BD-JB then but I will report back in a few hours in case someone else is interested.

I have used both but for example NanoDNS it's better to use 0.2. Also Gezin's advise is to set it to 127.0.0.2.

"Why is Setting DNS to 127.0.0.2 Required?
The DNS configuration is critical for Y2JB to function properly for two technical reasons:

1. Blocking PSN Connections: Setting the DNS to 127.0.0.2 (localhost) prevents the PS5 from reaching PlayStation Network servers. This blocks both the YouTube app and system firmware update prompts that would otherwise interfere with the exploit."

Just try it. If it does not work you are 1 number away to make changes. And indeed report your findings.

I've had issues opening payloads (which were already running) from Media tab and web browser from PC when I was using 127.0.0.2. Also Payload Manager couldn't refresh cloud repo with that DNS.
I patched appinfo.db with 127.0.0.1 address instead and also changed console's DNS to 127.0.0.1 and everything works alright for me since then.

 

[askara]

I'm assuming you haven't done the new jailbreak at all. Change your ip to 45.56.67.85, go back to settings menu select guides and tips, health and safety, other information, user's guide. Run the jailbreak there, and below that you have your payloads. Are you installing game through usb or pc? I install mine through PC using PS5Upload.

Is there a tutorial on running the new jailbreak?

 

[kevin corms]

Is there a tutorial on running the new jailbreak?

Modded warfare on youtube is actually good if thats what you need,

 

[Slegiar]

this is probably a silly question, but I mainly want to be sure. I've got an original disk version ps5, sitting nicely on 13.60, that i've been keeping fully offline to eventually break it when things settle down a bit.....at least the breakneck speed some....

But i figure, if i keep sitting around and waiting, i'm more likely to miss out on some stuff before i get my butt around to actually cracking the thing wide open.

so I just want to be sure, is the list of sony links to block on the home network up to date, and does the 45.56.etc.etc dns still work reliably?

I was debating about waiting till i have a second system as a backup just in case...but i figure i just really shouldn't wait too much longer.

 

[TheStonedModder]

this is probably a silly question, but I mainly want to be sure. I've got an original disk version ps5, sitting nicely on 13.60, that i've been keeping fully offline to eventually break it when things settle down a bit.....at least the breakneck speed some....

But i figure, if i keep sitting around and waiting, i'm more likely to miss out on some stuff before i get my butt around to actually cracking the thing wide open.

so I just want to be sure, is the list of sony links to block on the home network up to date, and does the 45.56.etc.etc dns still work reliably?

I was debating about waiting till i have a second system as a backup just in case...but i figure i just really shouldn't wait too much longer.

Just set ur dns to 127.0.0.1 and call it a day

You won’t have to worry about someone else’s server going down. And will just block it connections for you

The only thing this will cause issue with is if you want to do things like use homebrew that needs outside internet access

 

[kevin corms]

Just set ur dns to 127.0.0.1 and call it a day

You won’t have to worry about someone else’s server going down. And will just block it connections for you

The only thing this will cause issue with is if you want to do things like use homebrew that needs outside internet access

I went with a ESP32 board to service the exploit, dont have to worry at all this way.

 

[playerman]

ps5-payload-manager v0.6.2​

Changelog​

Features & UX Improvements​

• Autoload Return to Dashboard: Added an optional Return After Autoload setting, disabled by default, to return to the dashboard about 3 seconds after all payloads load successfully. Results stay visible if any payload fails or is skipped (#123).
• Dashboard Icon Setting: Added an option to hide payload icons on the dashboard, leaving more space for text while keeping card sizes unchanged. Icons remain visible in Get Payloads (#131).
• Release Details: Added a collapsible Release details section above the README on payload details pages. Release notes are fetched directly from GitHub for the release tag or version offered by the payload catalog (#133).
• New Languages:
  • Traditional Chinese
  • Romanian

Performance & Bug Fixes​

• Smaller ELF: Replaced bundled emoji artwork with Twemoji images loaded from a version-pinned public CDN, reducing the payload size. Downloaded emoji are cached for offline reuse (#130).
• Mobile Upload Controls: Fixed the upload button appearing outside the visible area in portrait mode. Repository controls now wrap to fit narrow screens, including when search is open (#126).
• Payload Icon Caching: Payload icons and catalog metadata now persist across browser sessions, so cached icons appear immediately when reopening the app instead of waiting for a catalog refresh.

Full Changelog: v0.6.1...v0.6.2

Link: https://github.com/itsPLK/ps5-payload-manager/releases/tag/v0.6.2

Post automatically merged: Oct 19, 2026

Arksama also made a Tweet about it:



Translation:
Fpkg 1st bug: Everything works perfectly with all firmware versions; tested on 12.00, 12.40, and 13.60.
Not yet tested on 14.00 and 14.10, but the bug is still present.

Fpkg with HV only: 40% complete

This is something i dont fully understand. If his fpkg bug is still present on 14.10 how he can check it if there is no kernel exploit for that firmware. Does he have a private one?? I was thinking everything known so far was patched on 14.10. Or maybe he is using dev kit to test that?? Maybe someone can shed some light on that. Thanks

 

[HS2005]

This is something i dont fully understand. If his fpkg bug is still present on 14.10 how he can check it if there is no kernel exploit for that firmware. Does he have a private one?? I was thinking everything known so far was patched on 14.10. Or maybe he is using dev kit to test that?? Maybe someone can shed some light on that. Thanks

Well you can use a devkit and decrypt the 14.10 firmware. Or just decrypt the firmware and check if in that firmware the bug or exploit is still present.

Post automatically merged: Oct 19, 2026

Just set ur dns to 127.0.0.1 and call it a day.

^^ This. Simple and easy. No hassle.

 

[1RickyG]

I just laugh when people use the wrong words for things. like when everybody says "if buying isn't owning then piracy isn't stealing." all the while thinking, you fools. It should be "if buying isn't owning, then downloading isn't piracy." There, fixed it for ya.

 

[HS2005]

Is there a tutorial on running the new jailbreak?

As already mentioned. Check Modded Warfare his YT page. The most up-to-date turorial is this one:



Now have fun!

Post automatically merged: Oct 19, 2026

I've had issues opening payloads (which were already running) from Media tab and web browser from PC when I was using 127.0.0.2. Also Payload Manager couldn't refresh cloud repo with that DNS.
I patched appinfo.db with 127.0.0.1 address instead and also changed console's DNS to 127.0.0.1 and everything works alright for me since then.

Should not matter. In both cases the DNS works for most.
Only with certain .elf files like Nano you need to implement small changes to the DNS. So both 127.0.0.1 and 127.0.0.2 cann be used as I just tested myself on several systems.

Post automatically merged: Oct 19, 2026

I just laugh when people use the wrong words for things. like when everybody says "if buying isn't owning then piracy isn't stealing." all the while thinking, you fools. It should be "if buying isn't owning, then downloading isn't piracy." There, fixed it for ya.

Symantics is not really a debate on this topic. We all get it.
We buy the hardware from Sony and now it's ours to control and actually own the hardware so Sony will no longer be in charge of it. Tough luck for S.

 

[ThePSGuy]

Just try it. If it does not work you are 1 number away to make changes. And indeed report your findings.

yes, it will take over the existing payload manager

I've had issues opening payloads (which were already running) from Media tab and web browser from PC when I was using 127.0.0.2. Also Payload Manager couldn't refresh cloud repo with that DNS.
I patched appinfo.db with 127.0.0.1 address instead and also changed console's DNS to 127.0.0.1 and everything works alright for me since then.

Thanks for the feedback guys, I'm back and can confirm that everything went as smooth as it can be with the DNS set to 127.0.0.1

I just updated my Payload Manager to the latest release (to get the new folder structure) before installing Y2JB and it just picked up my already existing install with all my settings hassle free.

Now I'm wondering, does nanoDNS blocks YouTube updates aswell or are they separate from the regular PlayStation Network? What I mean is, would the app update if I launched it by error when already jailbroken with nanoDNS running?