PS5 Exploit Guide

HS2005 · Sunday at 12:08 PM

Forgot to post this:

ViRGE · Sunday at 12:29 PM

Alrighty, I have a bit of an account-related head-scratcher on my hands that I am hoping someone can offer some insight with.

Model: PS5 Fat
FW: 9.60

Summary: I deleted a secondary account. Doing so broke most PS5 games on my primary account. Installing a fPKG game somewhat fixed it.

Detailed Description: Because I can never leave well enough alone, this evening I decided to delete a secondary user account that I never used. I initially created it as a backup in case Y2JB or such went wonky, but especially now with the webkit exploit, that is not an issue.

The PS5 deleted the account without issue. And to be safe, I rebooted the console.

After bringing it back up and restoring the jailbreak, much to my surprise I found that many of my PS5 game backups stopped working. Many of them (and seemingly, most requiring backports) would crash shortly after launch. I could still launch some PS5 games (both retail and backups), so I didn't break full game functionality. But deleting that unrelated account broke a lot of them, and I was making no progress on figuring out why.

There is no reason why deleting a secondary account should have had an impact; I didn't even use that account to play games. And to be sure, all of my save files were still intact on the PS5, so it is not as if I had accidentally wiped my save files.

Creating a new secondary account had no impact. The broken PS5 games would not work on that one, either. Even fake activation (using OnionHEN) didn't change anything.

Running out of options, I deleted one of my broken fPKG games and reinstalled it, thinking that maybe deleting the old secondary user somehow nuked part of the game.

Well, it worked. Reinstalling that fPKG game fixed that fPKG game... and everything else. Every broken game has started working again after installing that one fPKG game.

And if that isn't wild enough, here's where things get extra weird: I loaded up the game in question, and it happens to be a game that immediately assigns the account's name to the character's name. The name of the character? It's the name of the account that I originally deleted that started all of this.

At this point I am flummoxed, for so many different reasons. I don't know how deleting an unrelated account broke my PS5 games, I don't know how installing an fPKG game fixed my PS5 games, and I don't know why I now have games saying that my account name is a completely different (and very deleted) account.

To be sure, I've triple-checked and my primary account (which happens to be a legit, PSN-activated account) is showing the correct user name. So it is not as if the account has been renamed. Somehow, the ghost of my old Y2JB backup account has stuck around to haunt me, and will retaliate if I try to remove it.

Has anyone seen anything like this before? Google searches are coming up empty. If I didn't know better, I'd think that my PS5 was writing saves to the wrong location. However I've already confirmed that my save data is all there, intact, which I wouldn't expect to be the case if it was under that deleted secondary user. Even the username.dat file in the ../home/ directory shows the correct user name.

Everything seems to be working just fine again, so I probably shouldn't tempt fate once more. But it would be nice to fix this so that the right user name is showing up in games. Does the PS5 have some undocumented user database that I've somehow damaged?

zebrone · Sunday at 12:38 PM

HS2005 said:
Forgot to post this:

View attachment 596752

Using this i can install linux, on fw 10.01 too?

ViRGE · Sunday at 12:52 PM

lululemon said:
Also: noticed that for some games to run properly, they require loading 'kstuff toggle' in addition to SM+, KStuff, and a53 ppr.
I hope this helps anyone struggling with fpkg on low FW!

Hmm. kstuff toggle should not be necessary. That is an older package that was created to deal with some performance-related issues with kstuff that have since been fixed. Any version of kstuff that is new enough to run fPKG games should not need to toggle. Even on low firmwares, that was a kstuff issue, not a firmware issue.

Schweino said:
Is it possible to use a save file from one region on another region of the same title?

For instance: I have played Astro Bot PPSA21564 – USA and want to continue with Astro Bot PPSA21567 – EUR. When starting the latter the save of the USA version doesn't get recognized (the 2 versions of the games can also be installed next to each other on the PS5 and are seen as 2 different games).

Is it possible to dump the PPSA21564 save with Garlic save manager and reupload it to PPSA21567 so I can continue where I left off?

I have not personally tested this myself. But yes, it is my understanding that Garlic can be used to do that. Most games have identical save data formats.

lululemon · Sunday at 12:55 PM

Kimberly_g said:
i also have a few smaller indie games (unity engine), that crash during startup (Olliolli world, jet cave adventure). tried different payloads and kstuff. I wonder if there are bad dumps out there or we are doing something wrong. did the dumps you have come in rar?

maybe we should have a tool/database that checks the crc of these dumps. i would like to have vanilla/clean dumps and then add patches to them.

My dumps came as a single .pkg file . I've tried dumps from a different source that did come as a rar, and those actually worked.
Game source database is a good idea, I hope some implements it soon!

SkiDDeR · Sunday at 1:07 PM

cherryduck said:
Try the Console section, or load your crash dumps into the Crash log tab. It should diagnose the issue and suggest a fix, if not, send me the klog and the log files from the program.

Also, make sure you load as many existing backports into the program as kits as you can reasonably find, the more data it has the better. You may be missing some fakelibs that can be grabbed from existing backports.

I didnt use any kits, i just build it with target 8. Should i get kits to load?

cherryduck · Sunday at 1:12 PM

SkiDDeR said:
I didnt use any kits, i just build it with target 8. Should i get kits to load?

Yes. The tool doesn't come with any fakelibs so you need to load in existing backports (kits), doesn't matter what games they are for. They're used as evidence for recommended fixes, and they provide a library of fakelibs. Without loading in any kits, you'll get binary patches but no matching fakelibs.

ascii_politely · Sunday at 1:21 PM

cherryduck said:
PS5 Backport Toolkit v0.1.0: now on Windows (formerly PS5 Backport Linux)

The tool has a new name and now runs on Windows 10/11 as well as Linux. Same features, same app and command line.

What's new

Windows support: unzip and run ps5bp-gui.exe. No Python or git needed.

Ready-made downloads: a Windows zip and a Linux tarball on the releases page, so you no longer have to build it yourself. The Linux build runs on any distro from 2022 on.

Same results on both systems: a test backport of KINGDOM HEARTS HD 1.5+2.5 came out byte-for-byte identical on Windows and Linux.

New name: PS5 Backport Toolkit. The old GitHub link redirects automatically.

Download: GitHub releases
Source and README: https://github.com/cherryduck/ps5-backport-toolkit

Notes

Windows SmartScreen may warn the first time because the exe isn't code-signed: More info → Run anyway.

Kits and history are kept in %LOCALAPPDATA%\ps5bp on Windows and ~/.local/share/ps5bp on Linux.

The Console tab (live klog and crash dumps) hasn't been tested from Windows against a real PS5 yet, so reports from Windows users are especially welcome.

As before, please include a klog or what the Console tab said with any bug report.

Thanks for this! I finally had some success. My issues boiled down to trying to create backports for 4.xx even though my console is 9.60. I wanted the broadest, most compatible backport files for my collection. However, this would always give me the dreaded PRX_NOT_RESOLVED_FUNCTION error on launch, no matter how many fakelib and other files from various sources were added. The "Diagnosis" tool on your app would say "none of the 5 fakelib/ module(s) in the build folder were loaded"

I fixed this by creating a backport for my actual fw version. I got past that error and encountered new crashes, which were fixed after reading the logs and applying the appropriate Fix Rules. I ended up applying compat-stubs and set3-nonfatal (in addition to the recommended ones), which got me past black screens and missing sound issues. So thanks again.

I do have one issue to report tho: I had issues using the "Also build for" option. When the Target FW is 4.xx and "Also build for" is 5,9 - it seems to use the Target FW for all the binaries in the 5 and 9 backports, rather than the expected additional versions. The param.json files were updated but the binaries are skipped, remaining identical to the primary Target FW files. Changing the Target FW to 9 created the correct binaries and solved my issue, but would be nice to build multiple backports for many versions at once (which appears to be the intent)

HS2005 · Sunday at 1:36 PM

BrivsMekis said:
does anyone have this or older versions? seems the github account has been nuked

https://github.com/theghostonline/PS5VR/releases/tag/v1.3.0

No older versions. But it's continued here: https://theghostonline.dev/theghostonline/PS5VR/releases

Post automatically merged: Sunday at 1:38 PM

zebrone said:
Using this i can install linux, on fw 10.01 too?

For Linux only I would use this payload (.elf) Steam fix.

Comments:

"when Sonic ISO released the 13.60 payload for linux, it booted into ubuntu. But, there was an issue where you couldn't download any large files, including games on steam. This new payload by rmux completely fixes that bug, allowing you to download as much games as you want, with no I/O errors."

cherryduck · Sunday at 2:12 PM

ascii_politely said:
Thanks for this! I finally had some success. My issues boiled down to trying to create backports for 4.xx even though my console is 9.60. I wanted the broadest, most compatible backport files for my collection. However, this would always give me the dreaded PRX_NOT_RESOLVED_FUNCTION error on launch, no matter how many fakelib and other files from various sources were added. The "Diagnosis" tool on your app would say "none of the 5 fakelib/ module(s) in the build folder were loaded"

I fixed this by creating a backport for my actual fw version. I got past that error and encountered new crashes, which were fixed after reading the logs and applying the appropriate Fix Rules. I ended up applying compat-stubs and set3-nonfatal (in addition to the recommended ones), which got me past black screens and missing sound issues. So thanks again.

I do have one issue to report tho: I had issues using the "Also build for" option. When the Target FW is 4.xx and "Also build for" is 5,9 - it seems to use the Target FW for all the binaries in the 5 and 9 backports, rather than the expected additional versions. The param.json files were updated but the binaries are skipped, remaining identical to the primary Target FW files. Changing the Target FW to 9 created the correct binaries and solved my issue, but would be nice to build multiple backports for many versions at once (which appears to be the intent)

Glad to hear it's working for you and the analysis tools proved useful! I'm working on your bug report and will update you when the new release is up.

Wojtek1997 · Sunday at 2:14 PM

@TheStonedModder how's the progress with the AIO Ghostcontroller going? I have been waiting on since i first tried ghostcontroller and tbh all the replicas are not worth the risk

TheStonedModder · Sunday at 2:18 PM

Wojtek1997 said:
@TheStonedModder how's the progress with the AIO Ghostcontroller going? I have been waiting on since i first tried ghostcontroller and tbh all the replicas are not worth the risk

App is done, my API for others to use isnt quite, especially with this silly nonsense of us having to escape sandbox to send our own payloads to elfdir (I loathe whoever chose that design choice) I had to rewrite this 4 times so far

Options show as "Unavailable" if my API elf is not running.

alexiw · Sunday at 2:30 PM

Schweino said:
Is it possible to use a save file from one region on another region of the same title?

For instance: I have played Astro Bot PPSA21564 – USA and want to continue with Astro Bot PPSA21567 – EUR. When starting the latter the save of the USA version doesn't get recognized (the 2 versions of the games can also be installed next to each other on the PS5 and are seen as 2 different games).

Is it possible to dump the PPSA21564 save with Garlic save manager and reupload it to PPSA21567 so I can continue where I left off?

I just dealt with this with TLOU2.
Dump a decrypted copy of the saves with Garlic. For each save, edit sce_sys\param.sfo and rename the title ID to the correct one - or else it'll be ignored. A simple string replacement works here for this purpose, the file stays valid. Finally, rename the folder containing each save to the correct title ID.
Then, reupload with Garlic - on the last version, I could only upload each save file in a separate zip and couldn't upload multiple more at once or batch them unfortunately. Notice that other tools for uploading save backups may expect an already encrypted save file, so they won't work either.
That worked for me.

cherryduck · Sunday at 2:40 PM

ascii_politely said:
Thanks for this! I finally had some success. My issues boiled down to trying to create backports for 4.xx even though my console is 9.60. I wanted the broadest, most compatible backport files for my collection. However, this would always give me the dreaded PRX_NOT_RESOLVED_FUNCTION error on launch, no matter how many fakelib and other files from various sources were added. The "Diagnosis" tool on your app would say "none of the 5 fakelib/ module(s) in the build folder were loaded"

I fixed this by creating a backport for my actual fw version. I got past that error and encountered new crashes, which were fixed after reading the logs and applying the appropriate Fix Rules. I ended up applying compat-stubs and set3-nonfatal (in addition to the recommended ones), which got me past black screens and missing sound issues. So thanks again.

I do have one issue to report tho: I had issues using the "Also build for" option. When the Target FW is 4.xx and "Also build for" is 5,9 - it seems to use the Target FW for all the binaries in the 5 and 9 backports, rather than the expected additional versions. The param.json files were updated but the binaries are skipped, remaining identical to the primary Target FW files. Changing the Target FW to 9 created the correct binaries and solved my issue, but would be nice to build multiple backports for many versions at once (which appears to be the intent)

New release is up which fixes the "also build for" bug, thanks for the report!

Schweino · Sunday at 2:48 PM

alexiw said:
I just dealt with this with TLOU2.
Dump a decrypted copy of the saves with Garlic. For each save, edit sce_sys\param.sfo and rename the title ID to the correct one - or else it'll be ignored. A simple string replacement works here for this purpose, the file stays valid. Finally, rename the folder containing each save to the correct title ID.
Then, reupload with Garlic - on the last version, I could only upload each save file in a separate zip and couldn't upload multiple more at once or batch them unfortunately. Notice that other tools for uploading save backups may expect an already encrypted save file, so they won't work either.
That worked for me.

I managed to swap them out too. A bit easier than above: I extracted the memory.dat file from the US Astro Bot decrypted zip file and dragged and dropped that one into the EU save image mounted in Garlic manager. It asked me if I wanted to overwrite the existing memory.dat and I confirmed. After that I dismounted the save image in Garlic Manager.

Now I have my progress from US Astro Bot in the EU Astro Bot version!

seany1990 · Sunday at 3:32 PM

I have found a repo for games, it is saying almost all of them require 4.x firmware or higher. If I only care about piracy then do I need to update from 3.20

smoere · Sunday at 4:05 PM

I am just playing GT7 pippo BP version and it seems that I can play and save but some things are not working correctly. I should see more tracks but am not getting them.

Can anyone point me to a description of what i need to get this working correctly?

HS2005 · Sunday at 4:46 PM

PS5_RetroArch-v3.0.0-beta-3

In this release

Game Forwarder · SwanStation · melonDS DS · Frame Generation · RetroAchievements · Your library

Played on a Base PS5 · Upgrading · Source and credits

Make a home screen tile for any game in your library, right from the WebUI. Each tile is a small title of its own: open it and RetroArch starts straight into that game, with the core you chose.

Open Game Forwarder in the WebUI and choose New tile.
Choose the system, each listed with its console, then the game.
Set the name the home screen shows and the core; the game's own core is chosen for you.
Choose the picture: box art, 3D box, logo, cartridge or disc, screenshot, title screen or fan art. Fill the square or fit the picture inside it, and add the system's icon in the bottom right corner if you like.
Choose Create tile, then close RetroArch. Your tile appears on the home screen.

Close RetroArch when the game ends, or carry on in your frontend afterwards: each tile keeps your choice.
Edit or delete a tile at any time. A new name or picture, and a deleted tile, reach the home screen a few seconds after RetroArch closes.
Games in your content folder or on a USB or extended storage drive can have a tile.
Tiles need ShadowMountPlus 1.7 or later, with its API on (its default). The page says so when ShadowMountPlus does not answer.

Forwarders made with other tools work too: they start PS5 RetroArch with --rom <file>, --core <core> and --exit-after-game, as the README describes.

Changes since v2.0.0-beta-2. Release source; component source links and exact revisions are included in licenses/components.json. SwanStation and melonDS DS are built from their own repositories at pinned revisions, under the GPL-3.0.

Snes9x, FinalBurn Neo, Genesis Plus GX, PicoDrive, Opera, and the Alekfull NX theme carry non-commercial restrictions. This distribution may not be sold, and this release carries no donation link. The package's licenses/ directory records component licences and exact source revisions. RPCS3 is not included.

Thank you to AngelXex, whose SwanStationPS5 the SwanStation port's platform work is adapted from; to drakmor for ShadowMountPlus, which puts Game Forwarder's tiles on the home screen; to the SwanStation, melonDS and melonDS DS developers; to the tester whose v2.0.0-beta-2 logs found the 60 Hz slowdown; and to the RetroArch/libretro community, emulator and ES-DE developers, PS5 homebrew contributors, and everyone testing and reporting issues. Interface icons come from Microsoft Fluent Color; system artwork from the Linear ES-DE theme.

Ready to get started? Available releases · Installation guide · Source and credits

Link: https://github.com/mihawk-99/PS5_RetroArch/releases/tag/v3.0.0-beta-3

SkiDDeR · Sunday at 7:07 PM

cherryduck said:
Yes. The tool doesn't come with any fakelibs so you need to load in existing backports (kits), doesn't matter what games they are for. They're used as evidence for recommended fixes, and they provide a library of fakelibs. Without loading in any kits, you'll get binary patches but no matching fakelibs.

Where can i find backports (kits)?

Wojtek1997 · Sunday at 7:13 PM

TheStonedModder said:
App is done, my API for others to use isnt quite, especially with this silly nonsense of us having to escape sandbox to send our own payloads to elfdir (I loathe whoever chose that design choice) I had to rewrite this 4 times so far

Options show as "Unavailable" if my API elf is not running.

View attachment 596783 View attachment 596782View attachment 596781

@TheStonedModder NGL, this looks amazing! Keep up the good work! Cannot wait to try it out

Definitely worth waiting for an AIO solution like this instead of the replicas.

PS5 Hack Status:

Preparing Your Console:

Select Your Jailbreak:

Additional Information:

Warnings:

Archived Information

The destroyer of worlds

Attachments

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

The destroyer of worlds

Attachments

Well-Known Member

Member

Developer

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

The destroyer of worlds

PS5_RetroArch-v3.0.0-beta-3​

In this release​

Well-Known Member

Member

Similar threads

Popular threads in this forum

PS5_RetroArch-v3.0.0-beta-3

In this release