Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
PS4 Jailbreaking       Thread starter PSXHAX       Start date Apr 12, 2017 at 7:19 PM       10      
Not open for further replies.
Last month we saw a PS4 Real Time Memory Editor for Linux from PlayStation 4 developer @j0lama, and today j0lama returns with PS4ME (PS4 Memory Editor) PS4ME.dll and PS4METool Payload with details below. :love:

Download: PS4METool.rar (23.4 KB) / Github

To quote from j0lama's WebSite, roughly translated: # PS4ME (PS4 Memory Editor)


As I said in my previous post on RTM on PS4, my main goal is to develop a system similar to PS3TMAPI / PS3CCAPI but for PS4 that is simple to use and so developers can create their own tools. This project I want it to be a community project and that all people who want to collaborate to improve the system contact me and so I can create a team.

PS4ME.dll is a Windows library with all the necessary functions to be able to link to a PS4 (Version 1.76 for now) and to be able to read / write process memory. For now it only has the following functions:

SendPayload (string IP, string payloadPath) : Allows to send a payload to a certain IP through port 9023 so that it can be executed by the PS4 Playground of cTurt.
  • Connect (string ip) : Connects to the PS4 with the specified IP.
  • Disconnect () : Disconnects from the PS4.
  • string [] getProcesses () : Gets an array of processes that are currently running on the PS4.
  • string AttachProcess (string ProcessName) : Link to a given process returning an error message in case of failure.
  • byte [] dumpMemory (string Offset, string size) : Performs a memory dump of the specified size and starts in the memory address specified by the offset returning the byte array.
  • writeMemory (string Offset, string value) : Write in the memory address specified by Offset a byte specified by value.
  • string readMemory (String Offset) : Returns the read byte of the memory location specified by Offset.
As soon as I have time I will be adding more functions to get more data about the processes (size, addresses, permissions, etc).

I also include a Payload add-on to PS4ME.dll which is what will run on the PS4 allowing all PS4ME functions to be successful. It is recommended that a payload be executed before starting any game since it deactivates the ASLR and spoofs the console to avoid that updates are made when starting the games.


I have created this simple application for Windows that works with PS4ME.dll as a demonstration. Once the application has started, we have to activate the code execution on the PS4 from PS4 Playground and in the options bar open the right drop-down and give to Send. This will send the payload to the PS4 that will start running.

Once this is done we can give you to connect and update the list of processes with the button Get Process when we are inside the game so that we can see the process corresponding to our game (eboot.bin / default_mp.elf).

Once we have selected the process we give Attach to link and we can select a memory address and a size and give Dump to see the memory. We can check the Auto Update check box so that the memory is updated every 0.4 seconds. If we want to write in a memory address write the value of the byte down to the left and double click on the value that we want to overwrite.

For now this is what has given me time to do with PS4ME. I hope you serve and that you develop your own tools for PS4. Any bug or bug contact me via Twitter or YouTube.

Cheers to @lanaiscool and @raedoob for the heads up in the PSXHAX Shoutbox! :tup:
PS4ME (PS4 Memory Editor) PS4ME.dll & PS4METool Payload by J0lama.png


at this point if the only one who knows something beautiful that we qwertyuiopz scrubbed seen that still has not released anything yet..
I'm on 5.55, I wish my PS4 is exploitable, I really want to play around with this library and make some cool stuff, and I also want to try making my first homework app, game.

Damn this is taking so long for the kexploit to be released more then I expected, but I'll wait.
Not open for further replies.