PS5 Exploit Guide

yonasz · 2026-09-30T05:55:42+0100

ManuscriptReplica said:
Trying https://zecoxao.github.io/bagagwa/ on 13.40 and everything goes fine until etaHEN then I get a failed to load into error for that and the toolbox. Not sure what I'm missing. Sorry first time fucking with the PS5. Thanks for any help.

Try not to use etahen just kstuff+ shadomount + FTP if you need it. Just load payload manger and choose payloads
https://github.com/itsPLK/ps5-payload-manager

Dondraper · 2026-09-30T06:46:36+0100

schatzi24 said:

If we have fpkg, backport is still necessary correct?

ThePSGuy · 2026-09-30T07:03:42+0100

Are we still not able to convert dump folders to the new LZ4 format? I can't use FPKG and would like to convert dumps myself without having to wait for scene groups repacks but can't find any tool online.

bamboocappucino · 2026-09-30T07:21:29+0100

Can anyone confirm, once you have done the initial JB and installed the payloads, you can stay offline and thereafter launch the jb without a network connection?

ViRGE · 2026-09-30T07:47:19+0100

Dondraper said:
If we have fpkg, backport is still necessary correct?

Correct. fPKGs get you the native game execution environment. But you still need backports if a game is looking for newer firmware versions and libraries than your current firmware.

bamboocappucino said:
Can anyone confirm, once you have done the initial JB and installed the payloads, you can stay offline and thereafter launch the jb without a network connection?

For the autoloaders, correct. The web autoloaders cache all of the files locally.

However, the Relapse kernel exploit (the new one just released) only works if you have a working network connection, even though it doesn't load any files over the network. This is because the nature of the kernel exploit requires an active network connection with a valid address in order to trigger the bug that results in the kernel exploit. It's attacking the network interface stack, which is only up if there's an active network connection.

arson-tux · 2026-09-30T07:50:07+0100

PS5 webkit autoloader debug menu is broken keeps saying Something went wrong when opening CE-100154-1 and it's missing a lot of options that were available with original ntfargo exploit.

thekarter104 · 2026-09-30T08:16:39+0100

Am I the only one on a perfectly 00 firmware?

I'm on 13.00, I can confirm ETAHEN fully working.

HS2005 · 2026-09-30T08:29:33+0100

Modded made a how-to turorial for those who are new and want to setup the JB with the autoloader.

Links used in the video:
WebKit Autoloader: https://github.com/itsPLK/ps5-webkit-autoloader/releases
NanoDNS: https://github.com/drakmor/nanoDNS/releases
SM+: https://github.com/drakmor/ShadowMountPlus/releases
onionHEN: https://github.com/aydencharles/onionHEN

ThePSGuy · 2026-09-30T08:29:40+0100

enomao94 said:
how a folder like this should be installed?

Have you got your answer? I am encountering the same thing (the game folder with two additional ones) on a newer game I totally dumped myself.

TheStonedModder · 2026-09-30T08:35:12+0100

Can anyone share their 13.x auto loader setup ?

Either this is buggy, or my console has a demon and needs to be factory reset

HS2005 · 2026-09-30T08:40:33+0100

TheStonedModder said:
Can anyone share their 13.x auto loader setup ?

Either this is buggy, or my console has a demon and needs to be factory reset

Yeah sure. I have 2 setups working for 13.60.

1. When booting up the console. I run the Webkit Autoloader. It loads the JB. I have internet and the DNS 45.56.67.85 in place.
2. When Running the Webkit autoloader it loads the payload manager. See image below.

Running this setup with 6 seconds delay between each payload. Somewhere between 5 and 8 seconds is the sweet spot. At least for this setup and on these machines.

I've run this setup over 10 times now. It never failed once. It failed before when I was moving payloads. Like for example putting etaHEN first etc. EtaHEN still gives some error messages at the and about 9020 and 9021 ports but everything works fine.

EDIT: Here is the full pldmgr folder containing the setup and all the payloads. https://gofile.io/d/6qQb6iXP

The .zip file contains:

- kstuff.elf (version 1.11)
- ShadowMountPlus_1.7beta2.elf > Latest: https://github.com/drakmor/ShadowMountPlus/actions/runs/35903594428
- garlic-savemgr_v1.13.1.elf
- etaHEN.elf (one from the repo)

qamartheone · 2026-09-30T08:44:04+0100

thekarter104 said:
Am I the only one on a perfectly 00 firmware?

I'm on 13.00, I can confirm ETAHEN fully working.

can you link to exact etahen version ur using

bamboocappucino · 2026-09-30T08:51:03+0100

thekarter104 said:
Am I the only one on a perfectly 00 firmware?

I'm on 13.00, I can confirm ETAHEN fully working.

I'm on 2.00 with very itchy fingers

schatzi24 · 2026-09-30T08:53:28+0100

Elrond022 · 2026-09-30T08:57:29+0100

qamartheone said:
can you link to exact etahen version ur using

EtaHen 2.6b works with FW13.6

Inaki · 2026-09-30T09:02:36+0100

thekarter104 said:
Am I the only one on a perfectly 00 firmware?

I'm on 13.00, I can confirm ETAHEN fully working.

Did you read my answer ? You should setup an autoloader instead of depending on remote sites...

HS2005 · 2026-09-30T09:04:30+0100

PS5 RetroArch - Alpha 5.5

Pre-release

Highlights

Seven new systems: PlayStation, Nintendo 64, Sega Saturn, Commodore 64,
arcade (MAME), Nintendo DS and Nintendo 3DS. Each has one core, chosen for how
well it runs on RADV and how far it upscales. By default each uses the highest
graphics settings that hold full speed in the games I tested.
Rogue Leader's crash when leaving a mission is fixed. Dolphin needs a small
piece of executable memory for each vertex format a game uses. The title handed
out at most 128 of these, and Rogue Leader passed that between a mission and
the main menu. There is no limit now, for every core with a JIT: Dolphin,
PPSSPP, Mupen64Plus-Next, DeSmuME and Azahar. On the console, 2,000 small
blocks and 300 larger regions were allocated, and each ran its own code. I
haven't replayed the exact mission-to-menu path yet.
Simpler content browsing. Load Content now shows two places: INTERNAL,
the title's own folder, and EXTERNAL, the console's external storage.
Parent Directory from either takes you back to those two, not to the console's
root folder.
Licences in the package. The title folder now carries a licenses/ folder:
the licence texts of every part, and a list tying each executable to its
source revision. The source of every part is attached to this release.

A lot of new cores included.

Link: https://github.com/mihawk-99/PS5_RetroArch/releases/tag/v0.5.5-alpha.5

Post automatically merged: Today at 9:05 AM

qamartheone said:
can you link to exact etahen version ur using

This works for me. 1 on a slim, 1 on a PS5 PRO and also now 1 working on a PHAT system. So 3 systems on 13.60.
Link: https://gofile.io/d/6qQb6iXP

Adamos_22 · 2026-09-30T09:06:02+0100

TheStonedModder said:
what did I break? FW 13.4

View attachment 593218

no network connection

HS2005 · 2026-09-30T09:09:10+0100

yonasz said:
Try not to use etahen just kstuff+ shadomount + FTP if you need it. Just load payload manger and choose payloads

You can use etaHEN. Just the correct version and load it at the end of your payloads. Yes kstuff + SM+ is fine, but if you want to use etaHEN it this is the way to do it.

Inaki · 2026-09-30T09:12:45+0100

TheStonedModder said:
Can anyone share their 13.x auto loader setup ?

Either this is buggy, or my console has a demon and needs to be factory reset

Just one thing, just in case you are referring to something that has happened to me before and even on 13.60 on my PS5pro:

Sometimes, when the autoloader fails, it may hang or not but you kinda need to reboot because the JB doesn't happen. Ok, the thing is, once you reboot after an stuck autoloader, if you go and run the autoloader again, it very probably fails again. So you are stuck in a loop where another reboot ( or even forced reboot ) and another autloader run leads to another failure and it seems the autoloader is broken or something like that.

Well, worry not: the solution is doing not one but two full reboots. The first reboot is to exit the stuck state, probably a forced shutdown + a turn ON and the typical "bad shutdown, repair disc" cycle. The second reboot is the one you do clean: after the first reboot cycle, the "dirty boot" cycle, do not try an autoloader run again, do another clean reboot cycle first, this is the second reboot, and ONLY THEN try another autoloader run, which will very probably work fine.

PS5 Hack Status:

Preparing Your Console:

Select Your Jailbreak:

Additional Information:

Warnings:

Archived Information

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Well-Known Member

New Member

Well-Known Member

The destroyer of worlds

Well-Known Member

Developer

The destroyer of worlds

Well-Known Member

Active Member

Well-Known Member

Member

Well-Known Member

The destroyer of worlds

PS5 RetroArch - Alpha 5.5​

Highlights​

Well-Known Member

The destroyer of worlds

Well-Known Member

Similar threads

Popular threads in this forum

PS5 RetroArch - Alpha 5.5

Highlights