Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


FW Ranges:
2.XX = HEN+Kstuff+HV = PS4/5 backups, possible keys exploit (WebKit: 2.50 best / 2.7X max)
3.XX = HEN+Kstuff+HV+Linux = PS4/5 backups, possible keys exploit (WK/BDJB/LUA: 3.20 best / 3.21 max)
4.XX = HEN+Kstuff+HV+Linux = PS4/5 backups (WK/Y2JB/BDJB/LUA: 4.50 best / 4.51 max)
5.XX = HEN+Kstuff+HV+Linux = PS4/5 backups (
WK/Y2JB/BDJB/LUA: 5.50 best + max)

6.XX = HEN+Kstuff = PS4/5 backups, HV+Linux for 6.02 max (Y2JB/BDJB/LUA: 6.50 best + max)
7.XX = HEN+Kstuff = PS4/5 backups, no HV (
Y2JB/BDJB/LUA: 7.61 best + max)
8.XX-10.01 = HEN+ Kstuff = PS4/5 backups, no HV (Y2JB/LUA)
10.20-12.00 = KEX + Kstuff = PS4/5 backups, no HV (
LUA)
12.02-12.70 = KEX (
P2JB/SWRR)
13.XX = No KEX/HEN/Kstuff/HV (LUA)

NOTE: Recommended firmware is subjective. Staying low is always suggested first & foremost. It is not recommended to update too many major versions (e.g., 4.xx to 5.xx or 7.xx to 8.xx) because you should remain low unless all you want is backups.

DO NOT UPDATE OVER 12.00!! P2JB can take over 3 hrs to trigger an exploit.


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

Kernel (KEX):
Highest public Release:
12.70
Highest known: 12.70 (P2JB)
UMTX2: 1.00-7.61
Lapse: 1.00-10.01
Poopsploit: 4.XX-12.00
P2JB: X.XX-12.70

Userland (UL):
LUA: 2.00-LATEST (LUA game exploit, chain Lapse up to 10.01)
Y2JB: 4.03-12.60 (YouTube exploit, + Lapse up to 10.01)
NFNH: 4.03-12.XX (Netflix exploit, + Lapse up to 10.01)
YARPE: 4.03-12.XX (Ren'Py exploit, + Lapse up to 10.01)
BD-JB: 1.00-7.61 (Blu Ray exploit + UMTX2, 8.00-12.40 via UN BD JB + Poopsploit)
Webkit: 1.00-5.50 (PSFREE +UMTX2) (up to 13.20 coming soon)
Mast1C0re: 1.00-7.61 (PS2 backups)
LuaC0re: 10.20-12.02 (Star Wars RR: + Poopsploit up to 12.00)

NOTE: A userland entry exploit (UL) chained to kernel exploit (KEX) is required at a bare minimum to exploit your console.

NOTE 2: Since 12.60/13.00 Sony has removed the YouTube and Netflix apps and has added 30 day expirations to downloaded software used for LuaC0re/Mast1C0re/RenPy etc.

Digital consoles will now need a new webkit userland to hack their consoles as of 19/04/2026)


Useful Applications:
Elf loader: 8.00/7.61 HERE (use with BD-J)
Kstuff: 3.00-10.01 (3.00-12.70 soon)
HERE
Kstuff Lite: 3.00-12.70 HERE
Kstuff Toggle: 3.00-12.00 HERE
Dumping: Up to 8.00/7.61 (ItemzFlow / self decryptor) latest HERE
PS5 App Dumper: 3.00-12.00 HERE
Dump Runner: 3.00-12.00 HERE
Dump Installer: 3.00-11.60 HERE
Backporting: Possible (backpork / Porkfolio)
PS4/PS5 DLC: Work with kstuff (on retail disc games)
Homebrew Enabler: etaHEN (3.00-10.01) latest HERE
PS5 Backup Loading: Itemzflow HERE Compatibility list: HERE
PS4 Backup Loading: FPKG Enabler 3.XX-9.XX (rest mode & backports work, can crash).
PS5 Debug: Works
HERE
PS5 Remote Play: Works HERE & HERE
PS5 Trainers/Cheats: Work (Built into itemzFlow)

UART:
HERE
Linux: (3.00-6.02) HERE
Kldload (wip): 3.00-6.50 HERE
Full chain exploit: 1.00-4.51 (byepervisor) HERE (also built into etaHEN up to 2.7X)
PSN access: NEVER
Latest OFW: 13.40 (04/06/26)
Summarised OFW/Model guide: HERE
1.XX-7.61 compatibility list:
HERE
PS5 SDK Repo: HERE
Legit PKG Updates: HERE or HERE
OFW Updates: HERE (history HERE)

Preparing Your Console:


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


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

Alternative DNS IP:
DNS 1: 172.245.146.114
(Leave DNS 2 blank)

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

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

21.02-04.03.00.00-00.00.00.0.1

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

Current Examples:

2.00 could be updated to 2.50 maximum to retain Webkit/BD-JB/LUA HV + KEX + HEN.
4.00 could be updated to 4.51 maximum for WebKit/BD-JB/LUA + KEX + HEN + potential HV exploits.
5.00 could be updated to 5.50 maximum for WebKit/BD-JB/LUA + KEX + HEN.
6.XX-7.XX could be updated to 7.61 maximum for HEN using only BD-JB or LUA.
Digital/Pro users on 6.XX-LATEST cannot use BDJB or LUA without an activated console. Wekbit does not go beyond 5.50 for now.
Digital/Pro users or Disc console users on 8.XX-LATEST should consider waiting or selling/swapping consoles to get a lower firmware.
(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

SYSTEM UPDATES:

12.00 SYS MD5: 79d3171ec4ef38ca27f8ff36a9940847 (Exploited - No HEN yet)

10.01 SYS MD5: 68a31944c1867bf9643798fd1c14998e (Exploited + HEN)
9.00 SYS MD5: e74ddccd3360941ca24475c13195e031 (Exploited + HEN)
8.00 SYS MD5: 7616128c57581d5e49b42d1b3f308232 (Exploited + HEN)
7.61 SYS MD5: d5eca8b171a8d7df7ba225167f77e645 (Exploited + HEN)

6.50 SYS MD5: 98db854ba47a75dff0cb09355bca9025 (Exploited + HEN)
5.50 SYS MD5: edb3513ec531b2bd28f3a0b52a82a54f Exploited + HEN)
4.51 SYS MD5: 1330b7bf63bf5c93d809b1eb1f4e1f01 (Exploited + HEN)
4.03 SYS MD5: 3716e4e6e0d223cd94cd4a8e5bd4fb94 (Exploited + HEN)

RECOVERY UPDATES (wipes HDD):
12.00 REC MD5: f993e4c35ed6659b516346941980de4b (Exploited - no HEN yet)

10.01 REC MD5: 5202be086fc726d881f722d46e4486c6 (Exploited + HEN)
9.00 REC MD5: 6fbbda82c325bb5d6ec0717c2223b5c0 (Exploited + HEN)
8.00 REC MD5: 6cbb7a2fa2ace926202bd6e71304fb06 (Exploited + HEN)
7.61 REC MD5: 932f24e934723050fe49561b67e95226 (Exploited + HEN)
6.50 REC MD5: 4305223c12bd6dda9b944c0ee49c94c0 (Exploited + HEN)
5.50 REC MD5: c939ac8b37e07bbc129816a61002d30a (Exploited + HEN)
4.51 REC MD5: da78ca268da90a963d89b0f45db0f061 (Exploited + HEN)
4.03 REC MD5: e6dcc800d8d1dcada4f2bcd6e7ff162c (Exploited + HEN)

PS5 factory mode PUP installation path:

/usb/PROSPERO/UPDATE/PROSPEROUPDATE.PUP

Select Your Jailbreak:


WEBKIT (1.00-5.50):BD-JB 1.00-7.61:LUA (2.00-LATEST):Mast1c0re (2.00-7.61):Y2JB (4.03-10.01):NFNH (4.03-10.01):YARPE (4.03-10.01):LuaC0re (12.00 REQUIRES SWRR):BD UN JB (REQUIRES JB'D CONSOLE):


  1. PSFREE 1.XX-5.XX: https://github.com/kmeps4/PSFree
    Recommended host: https://zecoxao.github.io/luasauce/ (UMTX2 + Webkit for 1.XX-5.XX)

    Recommended WebKit hosts:
    https://zecoxao.github.io/luasauce/
    (UTMX2 with Lua and WebKit for 1.xx-5.xx)
    https://zecoxao.github.io/umtx/ or https://es7in1.site/
    (UMTX 2 exploit works on 3.00-5.50 with PSFREE WebKit)

    Alternative hosts:
    https://zecoxao.github.io/ps5jb/

    https://ps5jb.pages.dev/
    https://sleirsgoevy.github.io/ps4jb2/ps5-403/index.html

  2. You will need a BD dive paired to your Slim/Pro console, or an OG Phat model on 1.00-7.61 to run this exploit.

    Viktorious AIO Auto BD-JB ISO for 4.XX-7.61: https://github.com/Viktorious-x/ps5-bdjb-modified-ISOs/releases
    (Alternative: UMTX Kernel exploit 7.61 JAR loader by Hammer83: https://github.com/hammer-83/ps5-jar-loader/releases)

    Burn ISO to a blank BD-R or BD-RE, put it into your console, and click on the [DISC PLAYER] icon.
    Highlight [PIPELINE RUNNER] then click option 2 [Normaljailbreak-etaHEN-UMTX1.pipe] to auto load etaHEN ready for ItemzFlow.
    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].
    ELF Loader will be running on your PS5 IP: port 9021


  3. Important:
    Up to 10.01 has a kernel exploit + HEN
    11.XX-12.70 has a kernel exploit but no HEN yet.
    LUA entry point works on the latest OFW, but there is no kernel or HEN 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)

  4. PS2 Classics > Userland via CTurt:
    (Implementation by McCaulay)
    Note: this is currently limited to swapping the loaded PS2 iso, or loading PS2 elf homebrew on PS5 (or PS4) for emulators or basic PS2 brew.

    Mast1c0re PS2 exploit for PS2 homebrew:
    https://cturt.github.io/mast1c0re.html

    Mast1c0re part 2:
    https://cturt.github.io/mast1c0re-2.html

    Mast1c0re payload framework:
    https://github.com/McCaulay/mast1c0re

    Okrager save game exploit generator for Okage:
    https://github.com/McCaulay/okrager

    Mast1c0re payloader TCP Client GUI for PS5 6.50:
    https://github.com/Master-s/PS4-PS5-Mast1c0re-Payloader/releases

    TCP network ISO loader:
    https://github.com/McCaulay/mast1c0re-ps2-network-elf-loader/releases

    ExFat USB ISO loader:
    https://github.com/McCaulay/mast1c0re-ps2-usb-game-loader/releases

  5. coming soon

  6. coming soon

  7. coming soon

  8. coming soon

  9. This method modifies the BD-J stack to allows BDJB to be re-enabled on your higher firmware console up to 12.40.

    This requires your console to be hacked via another method first to gain access to alter the files.
    (For example 12.00 needs SWRR disc to hack it first)

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

    DO NOT REINSTALL FW, IT WILL WIPE THE PATCH AND LOSE BD-JB


Additional Information:


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

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

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

OFW 11.xx runs PS4 games up to 12.50
OFW 12.xx runs PS4 games up to 13.00


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


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

Warnings:


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

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

3: PS5 FPKGs do not work. A hack for the A53 processor does not publicly exist to enable installing PS5 content as FPKG/PKG.

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

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

Archived Information


 
Last edited by KiiWii,
Further steps towards the holy grail...

Screenshot 2026-03-20 at 23.44.12.png
 
Iui
Have you verified that output? If not, you could just as well flip a coin for the same amount of accuracy. I am currently researching the limitations of LLMs and I cannot stress this enough: If you work with slop machines, do NOT believe them until you can confirm they generated a correct answer.
Yep I was wrong! Damn You AI! Factory recovery returns the file to it's original. But!!! Restoring from a backup does not touch that system file...
 
  • Like
Reactions: iguanoPT
Voidshell works great for this, much faster transfers. I've just started using it but it's brilliant. You can't edit any files like in PS5xplorer, but you can have both folders open you want to copy/paste into and can delete files, or upload them directly from your pc if you using the web host.

I found that using the move function causes my ps5 to crash, but the copy function works great, and you can just delete the original after. I also think cut and paste on PS5xplorer crashed my system too, so I don't think the apps can be blamed for that one, might just be my console.

It's much more responsive using the web host, but you can follow the guide and install it locally now, it's just the ps5 webbrowser version runs slower, graphically I mean.

Cos of all a that cake boi! DAYUM!!!
thanks I'll have to check out Voidshell also. I'm still busy copying games to the external drive. 15 games on it so far. pretty good.

do you think I should just keep my 2TB in the internal NVME slot and have the 4TB in external? that's how it is right now. I'm guessing according to you guys games can be played from the internal NVME just fine? thanks
 
Last edited by realtimesave,
  • Like
Reactions: schatzi24
Iui
Yep I was wrong! Damn You AI! Factory recovery returns the file to it's original. But!!! Restoring from a backup does not touch that system file...
Thanks for clarifying. That basically means we finally got a method to carry over a jailbreak from a public backup to our own private backup? Neat. :)
 
Thanks for clarifying. That basically means we finally got a method to carry over a jailbreak from a public backup to our own private backup? Neat. :)
Just imagine if someone with a lower firmware released an offline backup to the public. Hell we can barely get people to share a prepatched LUA save individually. Gotta use an entire system backup if you can't get it done manually LOL
 
Just imagine if someone with a lower firmware released an offline backup to the public. Hell we can barely get people to share a prepatched LUA save individually. Gotta use an entire system backup if you can't get it done manually LOL
This is the dilemma we face with digital consoles... either you jailbreak it manually following all the steps in various videos or you use a backup like I did from Gezine... In my case that was not an issue as i had a vanialla console at the time...

For a newcome to jailbreaking, following the manaul steps can be daunting as it only takes one mistake to gert yourself into a pickle... and if you only have say a Macbook then things kinda get a little more interesting when sending payloads to the console... At least there is a filezilla app for the Mac which makes life easier :)

Post automatically merged:

Edit..

So the Blu-Ray userland is now out for 10.20 to 12.00.... Roll on the next piece of the puzzle...


1774097303527.png


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

BD-UN-JB is RemoteJarLoader that can be used on already jailbroken PS5 upto 12.00 firmware.
It supports on-screen logging and network logging.


Send bdj_unpatch.elf to elfldr to unpatch BD-J.
bdj_unpatch.elf will backup existing bdjstack.jar to bdjstack.jar.bak just in case.


Then burn BD-UN-JB iso and run.


DO NOT REINSTALL FW, IT WILL WIPE THE PATCH AND LOSE BD-JB
 
Last edited by BobaFett_UK,
Crimson Desert graphics mode for consoles
CDCS.jpg


Anyone believe the 'quality' final part of PS5 Pro as fake ? For me is very clear, it's a lie. A BIG ONE!
Just check all previous graphics modes where several of them are about 1440p UPSCALED. And now Sony, or the game developers, or who knows, want to say us that the quality mode is able to run at native 4K. SERIOUSLY ?
To be honest all about video games in the last 2 or 3 years, smells shit.

CD640.jpg
 
do you think I should just keep my 2TB in the internal NVME slot and have the 4TB in external? that's how it is right now. I'm guessing according to you guys games can be played from the internal NVME just fine? thanks
It's entirely up to you. If you're already copying files then you could keep it external, since you'd need to format it again to use it as an internal.

But you can still keep the 2TB internal one, and any games you know you'll play often, just copy them into that one from your external.

For me, my internal drive is mounted under ext1 and not ext0 like I thought it would be, weird that there's two mounts there but only one internal slot. It says ext1, but it's for the internal, which is external as far as the console is concerned, whereas your actual external will show up under one of the usb mounts.

Or swap the drives around if you don't mind copying the games again, you could use ftp directly to the internal nvme if you don't mind the slower speeds, it would save you some ssd durability on the other drive this way too if you're copying a load of files.

If you're terrified like I was, you can just backup your database files after you've installed all your games. People report that a database rebuild actually deletes the game files, but I've only had one rebuild that deleted the shortcuts like it does on ps4 (after I messed with it for the y2jb).

Lucky I had a backup so after restoring it, all my games where actually still there, ps4 and ps5 ones. I had many database rebuilds that did absolutely nothing, not even wiping the homebrew apps installed directly to the console.

Maybe I just got lucky, but it seems to not be anywhere near as serious as people kept making it out to be. I was shitting bricks when I had my first crash after installing everything and seeing a database rebuild, expecting everything to be yeeted but, nope, it was all good. Just ftp in and backup the database every now and then after you've added/deleted any games if you wanna be cautious.
 
Guys, does anybody have experience with the Data Transfer feature of the PS5 that can move savegames from one console to another? Is it possible to use that feature with an unactivated donor console that is on a lower firmware? The recipient console is on 13.00. I'm trying to figure out how to move savegames to my new console but I wanna keep the old one on a jailbreakable firmware. Got through one Internet check on the recipient console and it was listing my donor console, but error E2-80D79B60 gets in the way when I try to move forward with the data transfer process.
 
This is the dilemma we face with digital consoles... either you jailbreak it manually following all the steps in various videos or you use a backup like I did from Gezine... In my case that was not an issue as i had a vanialla console at the time...

For a newcome to jailbreaking, following the manaul steps can be daunting as it only takes one mistake to gert yourself into a pickle... and if you only have say a Macbook then things kinda get a little more interesting when sending payloads to the console... At least there is a filezilla app for the Mac which makes life easier :)

Post automatically merged:

Edit..

So the Blu-Ray userland is now out for 10.20 to 12.00.... Roll on the next piece of the puzzle...


View attachment 563497

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

BD-UN-JB is RemoteJarLoader that can be used on already jailbroken PS5 upto 12.00 firmware.
It supports on-screen logging and network logging.


Send bdj_unpatch.elf to elfldr to unpatch BD-J.
bdj_unpatch.elf will backup existing bdjstack.jar to bdjstack.jar.bak just in case.


Then burn BD-UN-JB iso and run.


DO NOT REINSTALL FW, IT WILL WIPE THE PATCH AND LOSE BD-JB
So what can you do in this case? I'm mean if you already run a JB console you can do stuff. I'f you want to upgrade to 12.00 you can't do anything because you don't have a JB anymore.

So let's say for example you have the SWRR game as a PKG and the save. You load up SWRR and you will get the loader message. If you update to 12.00 you won't have that anymore, because your SWRR game was a fpkg. Your fpkg is not going to load on a 12.00. Or am I missing something here.
 
  • Like
Reactions: schatzi24
Guys, does anybody have experience with the Data Transfer feature of the PS5 that can move savegames from one console to another? Is it possible to use that feature with an unactivated donor console that is on a lower firmware? The recipient console is on 13.00. I'm trying to figure out how to move savegames to my new console but I wanna keep the old one on a jailbreakable firmware. Got through one Internet check on the recipient console and it was listing my donor console, but error E2-80D79B60 gets in the way when I try to move forward with the data transfer process.
Are you trying to transfer the data from the higher firmware console to the lower firmware or the lower to the higher?
Post automatically merged:

So what can you do in this case? I'm mean if you already run a JB console you can do stuff. I'f you want to upgrade to 12.00 you can't do anything because you don't have a JB anymore.

So let's say for example you have the SWRR game as a PKG and the save. You load up SWRR and you will get the loader message. If you update to 12.00 you won't have that anymore, because your SWRR game was a fpkg. Your fpkg is not going to load on a 12.00. Or am I missing something here.
Jailbreak for 12.00 has happened, just waiting for an the other stuff to get ported. The lua userland exploits work in all firmwares we just don't have kernel exploits for anything above 12 yet. Unless of course someone can make an elf loader that doesn't require kernel privileges.
 
Are you trying to transfer the data from the higher firmware console to the lower firmware or the lower to the higher?

Lower to higher. First I thought restoring a backup of the low fw console on the high fw console would do the trick, but then I found out it didn't restore the saves. Those can only be restored on the console that created the backup, because the account that has the saves is a local one. I thought I might still be able to get the saves over without losing the lower fw on my older console using the data transfer, but so far I've hit a roadblock.
 
  • Like
Reactions: schatzi24
Lower to higher. First I thought restoring a backup of the low fw console on the high fw console would do the trick, but then I found out it didn't restore the saves. Those can only be restored on the console that created the backup, because the account that has the saves is a local one. I thought I might still be able to get the saves over without losing the lower fw on my older console using the data transfer, but so far I've hit a roadblock.
Does it work if you load it up on an internal nvme, then just move it over to the other console? Assuming they are on the same account ID of course. Are both consoles exploitable?

I tried it myself but from higher to lower, I didn't expect it to work but I figured I might as well try it.
Obviously it didn't, but lower to higher shouldn't be a problem I think. So you could try loading it all up on an internal nvme and just moving the drive between consoles.

On another note, I put my OG plates back on, I literally never used them but I gave my purple plates to a friend after I ordered some speed hole plates (not dbrand). I've just noticed a slight difference in the plate pins that connect it to the console.
1000006728.jpg
1000006759.jpg
I know it might be irrelevant, but I bring it up because after just swapping the plates back to white, I noticed a 2-3c drop despite making no other changes, the console was already clean etc. So I wonder if the new design somehow helps airflow somehow.

Like maybe the older plates flex once the console is laying horizontally, whereas the newer reinforced once keep the plate at the right distance, allowing for slightly more airflow overall. (you can see slightly on the purple one where the metal fan grill must have been hitting against the plate, I'm using the original stand too.)

Both are made by Foxconn, which I thought only made the fans but I guess not. The white is the OG from my 1200 model, but the coloured plate was bought directly from Sony, and it looks like it was made in early 2021 whereas the white plate is mid 2023.

Also it looks so weird seeing a white and black ps5 after having it be purple from the moment I bought it lol.
 
Last edited by Rasa39,
Does it work if you load it up on an internal nvme, then just move it over to the other console? Assuming they are on the same account ID of course. Are both consoles exploitable?

I tried it myself but from higher to lower, I didn't expect it to work but I figured I might as well try it.
Obviously it didn't, but lower to higher shouldn't be a problem I think. So you could try loading it all up on an internal nvme and just moving the drive between consoles.

On another note, I put my OG plates back on, I literally never used them but I gave my purple plates to a friend after I ordered some speed hole plates (not dbrand). I've just noticed a slight difference in the plate pins that connect it to the console.
I know it might be irrelevant, but I bring it up because after just swapping the plates back to white, I noticed a 2-3c drop despite making no other changes, the console was already clean etc. So I wonder if the new design somehow helps airflow somehow.

Like maybe the older plates flex once the console is laying horizontally, whereas the newer reinforced once keep the plate at the right distance, allowing for slightly more airflow overall. (you can see slightly on the purple one where the metal fan grill must have been hitting against the plate, I'm using the original stand too.)

Both are made by Foxconn, which I thought only made the fans but I guess not. The white is the OG from my 1200 model, but the coloured plate was bought directly from Sony, and it looks like it was made in early 2021 whereas the white plate is mid 2023.

Also it looks so weird seeing a white and black ps5 after having it be purple from the moment I bought it lol.
This is actually really interesting to see great timing..I am in the process of making box plates for our consoles with magnetic tops (for customization) and have been trying to wrap my head around these "hooks" those are the last thing I have to do

Are those the only variations you have noticed? I ask because my understanding was that the console was very picky with the shape/design of these hooks to securely hold the plates
 
This is actually really interesting to see great timing..I am in the process of making box plates for our consoles with magnetic tops (for customization) and have been trying to wrap my head around these "hooks" those are the last thing I have to do

Are those the only variations you have noticed? I ask because my understanding was that the console was very picky with the shape/design of these hooks to securely hold the plates
Yeah I didn't see much on any other difference really. Everything else seemed identical, right down to the molding lines and stuff, which does make sense given that it's the same manufacturer.

You can see the square areas where the hooks must be plastic welded on, so maybe the actual plate is made first, then the process for the hooks was changed, which wouldn't matter because those are added later.

I guess there is some extra plastic inside of the circles that cover the area the PS logo is, the one pictured is the disc drive side hence no logo cutout.

Interestingly though both top plates have wobble in them, it moves up and down at the corner near the power button. Only slightly though so I wonder if it's just a tolerance issue. Since mine are both Foxconn, I wonder if anyone else has a different manufacture of their plates. It's stamped on the disc drive side on both of my sets of plates.

I do have my new black plates with fan cutouts and those hooks/pins mimic the purple plate design. But getting them on, it was a much tighter fit, I had to spank the disc drive side like it was naughty to get it on fully though. And this one has no wobble, so I think it's probably by design on the official ones to make them easier to remove and replace.

Currently testing this new plate so we'll see, seems good so far though, no change in temps outside margin of error, but it does seem like the fan is quieter, and it's still pulling in plenty of air through the original front grills despite also pulling air through the new fan grills, so my nvme should be totally okay.
 
Last edited by Rasa39,
  • Like
Reactions: iguanoPT

Site & Scene News

Popular threads in this forum