Sleirsgoevy Announces PS5 Kstuff Porting Tool Complete for Missing Offsets

In PS5Scene news today developer @sleirsgoevy announced on Twitter that the Kstuff PS5 Porting Tool is complete allowing others to dump the offsets for the missing PlayStation 5 Firmware on PS5 versions 3.00 to 4.51 that have a kernel exploit while noting the list of currently supported revisions (3.00, 3.10, 3.20, 3.21, 4.00, 4.02 added thus far to 4.03, 4.50 and 4.51) can be found in offsets.c on his Github repository.

This comes proceeding the PS5 Kernel Exploit 4.03 / 4.50 / 4.51 Firmware Version Updates, PS5 Kernel Exploit v1.01 for 4.03 / 4.50 / 4.51, PS5 Kernel Exploit Payload.bin Loader Host, 4.03 PS5 HEN PS4 FPKG Enabler Payload, 4.50 PS5 HEN PS4 FPKG Enabler Payload and 4.51 PS5 HEN PS4 FPKG Enabler Payload with a PS5 Kstuff Porting Tool Guide to dump the offsets of Firmware not yet supported via the README.md:

Instructions for PS5-kstuff porting_tool (original by NotSoTypicalGamer and EchoStretch)

1. Make sure PS5 is jailbroken and running your exploit of choice with the ELF loader active
2. Use Linux, this README is focused on Ubuntu specifically (WSL2 doesnt appear to work)
3. Clone this repository locally:
   1. git clone https://github.com/sleirsgoevy/ps4jb-payloads.git --recursive --recurse-submodules -b bd-jb
   2. move into the right folder cd ps4jb-payloads/ps5-kstuff/porting_tool
4. Create symbols.json in the same folder and the contents should be:

   {"allproc": <ALLPROC_OFFSET>}

   1. to find the ALLPROC_OFFSET for your firmware, search on Specter's GitHub
   2. the offsets are located here document/en/ps5/offsets, find the right .js file for your firmware and search for OFFSET_KERNEL_DATA_BASE_ALLPROC. The HEX value you will find needs to be converted to DEC (just use a website online)
   3. you can finally substitute <ALLPROC_OFFSET> with the DEC value you got and save the file
5. Make sure python3 is installed
6. Install gdb-tools either with pip install gdb-tools or sudo apt-get install gdb if the other command doesn't work.
7. Install yasm with sudo apt install yasm
8. Try and run the script with

   python3 main.py symbols.json <your.ps5.ip.address> <elf.loader.port> kernel-data.bin

9. Once complete you should have kernel-data.bin dumped into porting_tool folder.
10. symbols.json will have also been updated to include needed information.

NOTE: This tool isn't complete. This doesn't grab all the data necessary to port "ps5-kstuff" to other firmwares. It's a WIP.

Finally, Sleirsgoevy states, "You can verify the found offsets by running the script test_offsets.py with the same arguments. It should launch a ps5-kstuff that can run fPKG files. If that works, please submit your JSON file either here, or to the testing channel on PS5 R&D Discord."

Spoiler: Related Tweets & Files

 

[Vkey]

Some of the bracket firmwares .. coming to live action soon ... Cheers !

 

[StickyButton]

Seems like our heroes have been making a lot of progress lately - could be due to having time off for the holidays. In any case, this gives me hope for my own PS5 to be jailbroken one day (5.10 out of the box ).

 

[calvin44]

@StickyButton wish the holiday was longer for best jailbreak work

 

[schaero]

Holy crap, this is the start of a GREAT year

 

[Shockzz]

thank you so much for sharing!

 

[loader1872]

Is there a certain thread that talks about if we should upgrade from older firmware to 4.03 or should we still stay on older firmware like 2.30. I only ask because I don't want to upgrade if something even better is coming for firmware in 2.x or 3.x

Thanks in advance for any assistance

 

[br0ke]

Great year coming up. That's for sure!

 

[Cavannix]

Progress is moving very fast and this is great news

 

[PSXHAX]

@loader1872 There's no dedicated topic for this as everyone decides for themselves whether to update their video game console or not.

• If you're a developer, remaining as low as possible is preferred as based on past console generations they're less secure so more 'holes' are left unpatched... needless to say, you can always update whenever you wish, get a second console to play online, etc.
  
  
• If you're an end-user who simply wants free games / homebrew, you wouldn't be doing any of the technical stuff should something become public for lower firmware versions... so remaining on a currently exploitable firmware will suffice.
  
  
• If you're a non-scener, you likely have been updating your console all along to access PSN, pay for games and are content doing so... if you decide you'd like to get into the scene down the road, simply stop updating the console and wait for your current firmware version to be exploited or get another console.

As for your example of a 2.30 firmware console, nobody knows what the future may bring for it... so it goes back to which of the above scenarios best describe your current situation.

Of course if you have a 2.30 console and aren't a developer you could always give / sell / trade it to someone who can use it, but should that be the case the decision is solely up to you.