Tutorial  Updated

PS5 Exploit Guide

PS5 Hack Status:


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

6.XX = KEX: PS4/5 backups (KEX+HV+Linux: 6.02 max) (BD/Y2/NF/LUA/YARPE: 6.02 for Linux / 6.50 max)
7.XX = KEX: PS4/5 backups, no HV (
BD/Y2/NF/LUA/YARPE: 7.61 best + max)
8.XX-10.00 = KEX: PS4/5 backups, no HV (Y2/NF/LUA/YARPE)
10.01-12.70 = KEX: PS4/5 backups, no HV (
Y2/NF/LUA/YARPE)
13.XX = No KEX/UL only (Y2/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: Do not update past 12.00. P2JB can take over an hour to exploit on FW up to 12.70.


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

Kernel (KEX):
Highest public Release:
12.70
Highest known: 12.70 (P2JB)
UMTX2:
1.00-7.61 (*WK to 5.50 / BDJB to 7.61)
Lapse: 1.00-10.01
Poopsploit: 4.03-12.00
P2JB: 9.00-12.70 (*Use Lapse up to 10.01)

Userland (UL):
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-7.61 (Blu-Ray exploit + UMTX2, *8.00-13.20 via UN BD-JB + Poops to 12.00)
Webkit: 1.00-5.50 (PSFREE +UMTX2) (*up to 13.XX coming soon)
Mast1C0re: 1.00-7.61 (Depreciated for LuaC0re)
LuaC0re: 1.00-12.70 (Poops: 4.03-12.00/P2JB: 9.00-12.70)

NOTE 1: A userland entry point (UL) chained to kernel exploit (KEX) is required to exploit your console.
NOTE 2: Digital consoles can now use Y2JB+Poops (4.03-12.00) / Y2JB+P2JB (9.00-12.70).


Useful Applications:
Kstuff Lite: 3.00-12.70
HERE
Kstuff Toggle: 3.00-12.00 HERE
PS5 App Dumper: 3.00-12.00 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: (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, 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)

KEY SYSTEM UPDATES:

12.70 SYS MD5: 707B15B07085500EB90205565751ECC3 (Exploited + KEX)
10.01 SYS MD5: 68A31944C1867BF9643798FD1C14998E (Exploited + KEX)
7.61 SYS MD5: D5ECA8B171A8D7DF7BA225167F77E645 (Exploited + KEX)
6.02 SYS MD5: 17b271DE081EB6EB25DBF70CB73EF9E8 (Exploited + KEX/HV/Linux)
5.50 SYS MD5: EDB3513EC531B2BD28F3A0B52A82A54F (Exploited + KEX/HV/Linux)
4.51 SYS MD5: 1330B7BF63BF5C93D809B1EB1F4E1F01 (Exploited + KEX/HV/Linux)
4.03 SYS MD5: 3716E4E6E0D223CD94CD4A8E5BD4FB94 (Exploited + KEX/HV/Linux)
3.20 SYS MD5: (F62F0D595D3F00C213D674D4DB2A7E44 (Exploited + KEX/HV/Linux)

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 is required for 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:
    Enter https://zecoxao.github.io/luasauce/ or https://github.com/kmeps4/PSFree into google > "Click Jailbreak" or wait for it to complete.

    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-7.61 to run this exploit.


    Recommended ISO: Viktorious AIO Auto BD-JB ISO for 4.XX-7.61

    Exploiting:
    1, Burn ISO to a blank BD-R or BD-RE > Insert into console > click on the [DISC PLAYER] icon.

    2, Highlight [PIPELINE RUNNER] > click option 2 [Normaljailbreak-etaHEN-UMTX1.pipe] to auto load etaHEN ready for ItemzFlow.

    ELF Loader uses PS5 IP: port 9021 / BIN loader uses 9020 / Jar loader uses port 9025

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  3. Important:
    LUA entry point works from 2.00 to the latest OFW, but there is no KEX above 12.70 yet.
    (A compatible PS4 game is required to launch the exploit on PS5. See below)

    Your PS5 console must be activated to use save copying for PS4 games.
    1. Insert your game disc and, as soon as possible, make a save file within it.
    2. Copy the save files to USB, go to [SETTINGS] > [STORAGE] > [CONSOLE STORAGE] > [SAVE DATA] > [PS4 GAMES] > select the game save and copy to a USB drive.
    3. On PC, using a Google Drive account, make a new folder with the GAME ID of your game, and upload the savedata & savedata.bin files to that folder.
    4. Share the folder, set it to editor mode, share with anyone, and click "copy the link".
    5. Join the HTOS Discord group: HERE type "/decrypt", select "FALSE" for including SCE_SYS, paste or type in the Google Drive link, and press enter. The bot should begin mounting your save. (If it doesn't, paste in the link again.)
    6. Click "ENCRYPTED" to remove the Sony PFS layer. Download the generated files and extract the folder to your desktop (you should have 4 files in there and be named dec_savedata_CUSA[GAME ID]).
    7. Using REMOTE LUA LOADER, open the savedata folder, copy the 20 files within into your encrypted save folder on your desktop.
    8. Upload the encrypted save folder (now with 24 files in) to your Google Drive. It should be named "dec_savedata_CUSA[GAME ID]" where GAME ID is your games 5 digit number, and set it to editor mode, share with anyone, and then click "copy the link".
    9. Go back to the HTOS discord server, and type "/encrypt", hit "FALSE" for uploading individually, and "FALSE" to include SCE_SYS. Finally, hit shared_gd_link and paste in your link to the original save (4 files) folder. (If it doesn't, paste in the link again.)
    10. When this is done, paste the link to the decrypted save (24 files) folder, and the bot will encrypt the files.
    11. Resign the files by typing "/resign" followed by your account name on the console, or PSN ID associated with that account if using the latest OFW.
    12. Download the resigned files, extract the files to your USB drive and overwrite them into the savedata folder on your USB or external drive.
    13. Copy the saves back to your console [SETTINGS] > [SAVE DATA AND GAME/APP SETTINGS] > [SAVE DATA PS4] > [COPY OR DELETE FROM USB] > [COPY TO CONSOLE STORAGE] > select your game save folder from the USB drive and copy/overwrite old save data.
    14. Load LUA game again, and you should see the LUA LOADER screen.
    15. You can use "SEND_LUA.PY" to send the UMTX files to the loader.
    (NOTE: Some games require manual loading of save game)

    On firmware up to 7.61, you can now load UMTX/2 followed by etaHEN by sending the files to your console IP on PORT 9026.
    On firmware 8.00-LATEST, you can connect with the REMOTE LUA LOADER APP to send debug notifications or FTP on port 1337.

    LUA Loader: HERE or HERE

    Auto LUA Loader Fork: HERE

    Compatible LUA games:
    Aerial Life (CUSA17122)
    Aibeya (CUSA17068)
    Aikagi 2 (CUSA19556)
    Aikagi Kimi to Issho ni Pack (CUSA16229)
    Aikano Yukizora no Triangle (CUSA19370)
    Boku to Nurse no Kenshuu Nisshi (CUSA12049)
    Boku to Joi no Shinsatsu Nisshi (CUSA18107)
    Fuyu Kiss (CUSA29745)
    Hamidashi Creative (CUSA27389)
    Hamidashi Creative Demo (CUSA27390 requires the latest OFW to download from PSN)
    Haruoto Alice (CUSA14324)
    IxSHE Tell (CUSA17112)
    IxSHE Tell Demo (CUSA17126)
    Jinki Resurrection (CUSA25179)
    Jinki Resurrection Demo (CUSA25180 requires the latest OFW to download from PSN)
    Maid-san no Iru Kurashi (CUSA18106)
    Nora Princess and Stray Cat Heart HD (CUSA13303: Rename save9999.dat into nora_01.dat)
    Nora Princess and Strat Cat Heart 2 (CUSA13586)
    Raspberry Cube (CUSA16074)
    Winter Guest (CUSA11977)

    WARNING: using demos is free but can become corrupt, and you cannot upgrade your internal HDD either. If you lose the demo you can no longer use the exploit. Disc recommended.

    Incompatible LUA games:

    Dokyusei Remake Csver (CUSA47117)
    Dōkyūsei: Bangin' Summer - Home Edition Demo (CUSA47132)
    Kiss Trilogy (CUSA19341)
    Love Clear Demo (CUSA18109)
    Mikagami Sumika no Seifuku Katsudou (CUSA11481)
    Sen no Hatou, Arazone no Hime (CUSA09647)
    Tonari ni Kanojo no Iru Shiawase: Two Farce (CUSA09825)
    Tonari ni Kanojo no Iru Shiawase Summer Surprise (CUSA18998)

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  4. Requirements:
    PS5 console must be on 4.30-12.70 and previously activated through PSN or fake activated to use the YouTube app, unless you're restoring a backup.
    (Note: restoring a backup will factory reset your console).

    Information:
    If updating and older installation, download the latest download0.dat > use FTP or PS5 Explorer to place it in the user/download/PPSA01650 folder.

    Preparation:
    Download the Y2JB_backup_X.X(4.03) if you're on 4.03-12.40, or the Y2JB_backup_X.X(12.20) if you're on 12.60 or higher from HERE
    On PC: format a USB 3.0 HDD to exFAT, and copy the PS5 folder from the backup to the root, and put the latest nanodnf.efl from nanoDNS to the root too.
    On console: go to [Settings] > [System] > [System Software] > [Back up and Restore] > [Restore] > select the y2JB back up & let it install (the console will reboot when complete).
    (Note: The exploit will now be accessible under the [MEDIA] tab)

    Exploiting:
    Going to [Settings] > [Network] > [Settings] > [Set up Internet Connection] > [Set up Manually] > set up a wireless or LAN connection > change [DNS Settings] to manual > change [Primary DNS] to 127.0.0.1 > click [Done] > open the [YouTube App].
    (Note: Ignore and internet connection issue warnings)

    Firmware up to 10.01 will use Lapse Kernel Exploit. Firmware 10.20-12.70 and above will use P2JB and could take up to an hour.

    You can send payloads using netcat GUI to PS5's IP Address & port 9021.

    You can swap the download0.dat to itzPLK version for auto loading and payload manager in future (payload manager accessible through browser on 127.0.0.1:8084)

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  5. Requirements:
    PS5 console must be on 4.30-10.01 and previously activated through PSN or fake activated. You will need a 256GB external HDD (minimum).

    Preparation:
    Download balenaEtcher
    Download the latest Extended Storage or M.2 Image (select your m.2's capacity)

    EXTERNAL DRIVE METHOD (Netflix_PS5_EU_Ext.7z):
    1a, On PC: connect your 256GB (min) USB drive to your Windows/Mac/Linux PC > extract the image to your computer > open Etcher > click [Flash From File] & select the extracted image *.zip > click [Select Target] & choose the external drive > Click [Flash!] & allow it to complete.
    (Note: 256GB is the smallest drive you can use)

    2a, On console: click [Settings] > [Storage] > [USB Extended Storage] > [Games and Apps] > press X on [Netflix] > select [NETFLIX] under items to move > select [Move] > move to internal storage & allow it to complete.
    (Note: The exploit will now be accessible under the [MEDIA] tab)

    INTERNAL DRIVE METHOD (Netflix.XXXXGB.7z):
    1b, On PC: connect the M.2 to your Windows/Mac/Linux PC > extract the image to your computer > open Etcher > click [Flash From File] & select the extracted image *.zip > click [Select Target] & choose the external drive > Click [Flash!] & allow it to complete.
    (Note: 4TB will take 80 mins, 2TB 45 mins, 256GB 10 mins)

    2b, On console: Power off the console > insert the M.2 SSD > power on the console > click [Settings] > [Storage] > press X on [Netflix] > select [NETFLIX] under items to move > select [Move] > move to internal storage & allow it to complete.
    (Note: The exploit will now be accessible under the [MEDIA] tab).

    Exploiting:
    1a, for consoles 10.01 and below, on console: go to [Settings] > [Network] > [Settings] > [Set up Internet Connection] > [Set up Manually] > set up a wireless or LAN connection. Go to Proxy > change [Automatic] to [Manual] > enter Address: 172.105.156.37 & port: 42069 > click [Done] > open the [Netflix App].
    (Note: Ignore and internet connection issue warnings)

    1b, for consoles 10.20-12.70, COMING SOON.

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  6. Important:
    YARPE works from 4.30 to 12.70 (9.00 - 12.07 via P2JB)
    (A compatible PS4 game is required to launch the exploit on PS5. See below)

    Requirements:
    PS5 console must be on 4.30-10.01 to use this exploit.

    Exploiting:
    coming soon

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  7. Requirements:
    PS5 console must be on 4.30-12.70 to use this exploit. SWRR

    Exploiting:
    coming soon

    Debug settings will be loaded, and the package installer can be found under [SETTINGS] > [DEBUG SETTINGS].

  8. Important:
    This method modifies the BD-J stack to allows BD-JB entry point to be re-enabled on consoles up to 13.40, for conveninece 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


(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,
I've updated the browser cache so that my etaHEN version updates from 2.3B to 2.4B and now my console fails to launch etaHEN toolbox for some reason. I'm on 5.00 and I have an SSD in the M.2 slot if that matters. I've tried sending the payload from my PC (my console and my PC are on the same network and PS5 is blocking updates and redirecting the User's Guide to the UMTX2 exploit website) but that fails as well. I've tried Payload Injector v1.4 and NetCat GUI v1.3 and the both freeze or say that my PS5 can't be reached so I'm not sure what to do anymore. Does anyone have any idea what I might be doing wrong?

EDIT: I've tried cleaning the cache and after a few retries still nothing. Interesting thing, though, is that I had 0 KPs which is really nice but makes me wonder if they fixed the stability over time, was I just that lucky or does the jailbreaking even works properly? I believe that it does since I do get access to debug tools, just not the toolbox.

After a while, I tried zeco's UMTX2 webkit exploit which has the latest etaHEN on it (2.5B) and... it works! Which is again weird but not that I'm complaining. I've been on 2.3B for a while, but at least now I can continue to test Y2JB to see if that will work better in my use case.

I'm still unable to send ELF payloads from my PC to the console. Both PC and the console are on the same network, both of them are using the custom DNS settings but I'm not sure if that's the issue. From what I understand, as long as they are on the same connection, they should be able to see each other.

EDIT#2: And yes, now it suddenly decided to work. Troubleshooting these issues isn't really an easy task for me. :D Hahahaha
I'm using etaHEN 2.5B and the injection success rate of the Toolbox is like 1/10. It's not just you.
 
5.50 user too, etahen 2.5 and 2.6 had low success rate with umtx2, but with Y2JB (and autoloader) and 2.6 etahen is very high like 80-90%. Injecting payloads from etahen builtin plugin options automatically.
The injection success rate is 80-90% even recovering from rest mode?
 
  • Like
Reactions: solitaire4eva
A little off topic guys. I hope you dont mind :)
From time to time im fixing dualsense controllers for friends/family and other interested people. Im using https://ds.daidr.me/ for full test of the controllers as it have everything including haptic test vibrations speaker etc. As for calibrating new sticks im using https://dualshock-tools.github.io/ . So far everything was great but yesterday i have encountered something very strange. After connecting controller to pc it didnt set to one color asalways it was just flashing all colors available. Test websites were showing everything ok for buttons but haptic test didnt work and vibrations when tested were starting and stopping right away with something looked like short on the controller because lights corresponds to that test. Speaker was also crashing. So first thing i have done was desoldering all the wires and nothing changed. Disconnecting flexi ribbon. Nothing changed . Trying different triggers. Same. Disconnecting touchpad. Same. I have even changed mainboard from a known working controller and it was still the same.I was even thinking that maybe conductive film is making some kind of short as i was having few situations in the past that analog stick was pressing itself when using triangle or sqare. So i have decided to connect my own personal controller and with my surprise it was doing the same. After googling thru the web i have tried many different solutions including setting up dualsense in audio devices and even uninstalling all usb devices ever connected to my pc using usbdeview https://www.nirsoft.net/utils/usb_devices_view.html .But that didnt change anything. So i started checking my installed aplications and updates to them. Finally after 2 days of struggling i have found out that signal rgb https://signalrgb.com/ that i have installed on my pc was a culprit. After uninstalling it everything went back to normal so happy days. Maybe some of you will find this informative. I didnt try to run it and changing setting as that wasnt my goal. I just wanted for everything to work as before. Its important for me. I know you can check your controller with astrobot playroom but connecting it to pc for a first quickcheck its much faster. Thanks
 
I'm using etaHEN 2.5B and the injection success rate of the Toolbox is like 1/10. It's not just you.
etaHEN 2.5 finally fixed the issue for me on 7.61+m.2
as workaround: avoid kstuff being loaded via etaHEN, instead put the no_kstuff file in place and let kstuff be loaded at the end of autoloader.txt with a delay 5-7sec after toolbox-launch
 
If a scalper buys 1000 units at launch price, that's still 1000 units sold. It doesn't change the numbers because they resold them, but do keep making assumptions like that. The ones in the pawn shops are the ones that were already sold, so they were already counted at the time of the original sale. The prices changed because of the lack of availability and like they say, if you control the supply and the demand, you've got yourself a monopoly... don't forget about all those pirates robbing freight trains, that reduces the total number of retail sales.
Can you make your point a bit clearer, because you seemed to originally claim that scalpers artificially increased the sales numbers. Yet none of this proves that the sales were inflated at all, only the price was.
 
etaHEN 2.5 finally fixed the issue for me on 7.61+m.2
as workaround: avoid kstuff being loaded via etaHEN, instead put the no_kstuff file in place and let kstuff be loaded at the end of autoloader.txt with a delay 5-7sec after toolbox-launch
If understand well what you said:
1º Run etaHEN without kstuff
2º Put kstuff the last payload
3º And put 5-7 seconds delay to force toolbox to run after these 5-7 sec (because toolbox need kstuff first)

Is that correct?
 
  • Like
Reactions: peteruk
Is that correct?
1º Prevent etaHEN from immediately loading kstuff by making use of the no_kstuff file
2º Put a 5-7sec delay inbetween etaHEN and kstuff in autoloader.txt to avoid kstuff from disturbing the toolbox bootup process

in addition the workaround is useful for np-fake-signin too, but in my case this led to toolbox being unable to launch itemzflow directly
 
  • Like
Reactions: iguanoPT
I've finally managed to set up Y2JB Autoloader and most of the issues I experienced were due to the poor WiFi signal that I have in my room. Ended up uploading files from USB via PS5 Xplorer instead which worked like a charm. Now I just have to figure out how Back Pork and UFS2 thingy works so that I can finally play Astro Bot. :D Modded Warfare videos were helpful but I had to gather info from three separate videos in order to get the full picture and understanding about how all these things work together.

I'm on 5.00 and so far Lapse didn't work only 1/10 times which is awesome. etaHEN at first didn't load because of my mistake, but after that it was successfully loaded ~7/7 times so far which is great. Before that, KPs occurred maybe 30% of the time, which is a HUGE improvement and I hope it stays that way and that I wasn't lucky so far. :D
 
I've finally managed to set up Y2JB Autoloader and most of the issues I experienced were due to the poor WiFi signal that I have in my room. Now I just have to figure out how Back Pork and UFS2 thingy works so that I can finally play Astro Bot. :D Modded Warfare videos were helpful but I had to gather info from three separate videos in order to get the full picture and understanding about how all these things work together.

I'm on 5.00 and so far Lapse didn't work only 1/10 times which is awesome. etaHEN at first didn't load because of my mistake, but after that it was successfully loaded ~7/7 times so far which is great. Before that, KPs occurred maybe 30% of the time, which is a HUGE improvement and I hope it stays that way and that I wasn't lucky so far. :D

nobody want to say it, ok, I will.

'Most of the issues' are because the etaHEN. If you don't use etaHEN, that in fact it is not required for the different purposes, there are no issues at all, at least with FW 10.0x.
Only problem is on lapse, that some very few times, is not doing the job at first sting and will required the console to be rebooted. Neither KPs are happening on 10.0x.
 
etaHEN 2.5 finally fixed the issue for me on 7.61+m.2
as workaround: avoid kstuff being loaded via etaHEN, instead put the no_kstuff file in place and let kstuff be loaded at the end of autoloader.txt with a delay 5-7sec after toolbox-launch
Forgot to mention that I'm on 4.50 so I'm still using UMTX2 webkit exploit and not autoloader.txt.
1º Prevent etaHEN from immediately loading kstuff by making use of the no_kstuff file
2º Put a 5-7sec delay inbetween etaHEN and kstuff in autoloader.txt to avoid kstuff from disturbing the toolbox bootup process

in addition the workaround is useful for np-fake-signin too, but in my case this led to toolbox being unable to launch itemzflow directly
What is your autoloader.txt set up look like?
 
Last edited by FateNightroad,
I've finally managed to set up Y2JB Autoloader and most of the issues I experienced were due to the poor WiFi signal that I have in my room. Ended up uploading files from USB via PS5 Xplorer instead which worked like a charm. Now I just have to figure out how Back Pork and UFS2 thingy works so that I can finally play Astro Bot. :D Modded Warfare videos were helpful but I had to gather info from three separate videos in order to get the full picture and understanding about how all these things work together.

I'm on 5.00 and so far Lapse didn't work only 1/10 times which is awesome. etaHEN at first didn't load because of my mistake, but after that it was successfully loaded ~7/7 times so far which is great. Before that, KPs occurred maybe 30% of the time, which is a HUGE improvement and I hope it stays that way and that I wasn't lucky so far. :D

Did you use Gezine's backup image and restored that or did you do it the manual way and install the YT 1.03 app and copy across the download0.dat file etc? If you did it the manual way then well done.... I tried the manual approach and kept doing something wrong and got fed up and then resorted to the backup :)

You are right about one thing, you have to follow a number of videos to get the steps exsctly right...

What we need is a simple document which tells us all the steps... Now there's a thought? Hmmmmm
 
Did you use Gezine's backup image and restored that or did you do it the manual way and install the YT 1.03 app and copy across the download0.dat file etc? If you did it the manual way then well done.... I tried the manual approach and kept doing something wrong and got fed up and then resorted to the backup :)
Thanks! Yeah, i used the manual way and it was a bit of a pain to set everything up but now that I've done it I feel like it's pretty much straightforward, it's just that it isn't documented well enough for newbies such as myself. :D Not that I'm new to jailbreaking the consoles in general but I love to have a good written guide for everything I do as YouTube videos get outdated quickly. Restoring backup is probably the best way to go but I didn't want to reinstall and/or restore everything afterwards.

You are right about one thing, you have to follow a number of videos to get the steps exsctly right...
Indeed. ^^ Sometimes he forgets to mention a thing or two here and there which is completely normal, we are humans after all. But it annoys me to hell and back that I somehow manage to run into a couple of bugs every time I try something new. :D Thankfully, I manage to figure it out somehow or someone replies back and I fix the issue so it's all good and it's a good learning process. Sucks that it's a completely different thing every time I update my PS5 setup. :D

What we need is a simple document which tells us all the steps... Now there's a thought? Hmmmmm
I'll make a short guide on how I went from UMTX2 to Y2JB Autoloader setup once I confirm that I've done everything correctly with BackPork and ShadowMount as well. If not, you'll hear my pleas for help once again. :D BackPork and ShadowMount should be pretty straightforward but you never know where I'll run into an issue again.
Post automatically merged:

Well, ShadowMount and BackPork were simple enough (only one KP so far) and I've learned how to update kstuff properly. :D Now all I have to do is figure out how to copy Astro Bot to the internal storage, probably via external HDD, once I make a FFPKG file of it. Glad that something went smoothly enough. :D
 
Last edited by Blythe93,
Thanks! Yeah, i used the manual way and it was a bit of a pain to set everything up but now that I've done it I feel like it's pretty much straightforward, it's just that it isn't documented well enough for newbies such as myself. :D Not that I'm new to jailbreaking the consoles in general but I love to have a good written guide for everything I do as YouTube videos get outdated quickly. Restoring backup is probably the best way to go but I didn't want to reinstall and/or restore everything afterwards.


Indeed. ^^ Sometimes he forgets to mention a thing or two here and there which is completely normal, we are humans after all. But it annoys me to hell and back that I somehow manage to run into a couple of bugs every time I try something new. :D Thankfully, I manage to figure it out somehow or someone replies back and I fix the issue so it's all good and it's a good learning process. Sucks that it's a completely different thing every time I update my PS5 setup. :D


I'll make a short guide on how I went from UMTX2 to Y2JB Autoloader setup once I confirm that I've done everything correctly with BackPork and ShadowMount as well. If not, you'll hear my pleas for help once again. :D BackPork and ShadowMount should be pretty straightforward but you never know where I'll run into an issue again.
Post automatically merged:

Well, ShadowMount and BackPork were simple enough (only one KP so far) and I've learned how to update kstuff properly. :D Now all I have to do is figure out how to copy Astro Bot to the internal storage, probably via external HDD, once I make a FFPKG file of it. Glad that something went smoothly enough. :D
Use drakmor's ftp server to copy over from external HD to internal. I'd copy the files to your pc first and then from there ftp to the data/homebrew folder.... His ftp is much faster than JT's ftp... unless JT has updated his already...

https://github.com/drakmor/ftpsrv
 
Can you make your point a bit clearer, because you seemed to originally claim that scalpers artificially increased the sales numbers. Yet none of this proves that the sales were inflated at all, only the price was.
How do you not realize that someone buying 1000 units inflates the sales numbers? One person bought 1000 units, but Sony thinks that means 1000 people bought their shit. Imagine if the politicians thought all citizens were stupid just because they know a few who are...
 
  • Like
Reactions: schatzi24
How do you not realize that someone buying 1000 units inflates the sales numbers? One person bought 1000 units, but Sony thinks that means 1000 people bought their shit. Imagine if the politicians thought all citizens were stupid just because they know a few who are...
I get where you're coming from, but unless you can name 1000 scalpers who did that, the number is meaningless in comparison to the amount of consoles that actually found their way to customers. Even then we'd talk about less than 2 per cent of total PS5 sales worldwide.
 

Site & Scene News

Popular threads in this forum