1.76 PS4 API, PSN API, PS4API Open Sourced and recent PS4API 4.05 Port work today PlayStation 4 developer @BISOON made available a PS4API Server for PS4 4.05 Firmware to handle client R/W game memory requests aiding devs in making RTE/RTM tools.
Download: PS4API.bin / PS4 API Server GIT / PS4Lib-master.zip / PS4Lib GIT (Dynamic link library to create RTMs for PS4)
To quote from his post on NGU: Hello everybody after a while being away for a long time
Recently I got my PS4 (4.05) and thanks for everyone who spent his effort to make this happen on 4.5 and also we will not forget who is working on useful things for this community.
I spent the past two days looking for PS4API to control over the app memory using desktop tools/rtms, and unfortunately I got some but seems not worked with me or not stable enough (I am not underestimating their work, I really respect what they are done) also no new commits or updates on their projects for a long time.
So today I just pushed my PS4API server project into github for contribution, or for testing purposes. The client side not finished yet due the lack of time, so I will create the client lib based on the PS3Lib By iMCSx components (if he doesn't mind) to make it easy for people who already has created PS3 rtm tools and to make it simple for updating PS3 tools to PS4 (only changing the addresses will be enough) and the RPC as well if needed.
And from the README.md: PS4API Server
This project allows you to control PS4 game memory for reading/writing calls. with this project you can make RTE/RTM tools
use CTurt's PS4 *** from xvortex's repository. then follow the instructions on how to add the *** path to your environment.
commands:Code:char sendCommand(char command, void* args);
- * 'a' attach to game process (eboot.bin) and the process will continued.
- * 'c' continue the process.
- * 'd' detach the process.
- * 's' suspend the process.
- * 'u' resume the process.
- * 'k' kill the process (seems not works)
- * 'n' send notification with text.
- * 'r' read memory.
- * 'w' write memory.
- * 'a'(void);
- * 'c'(void);
- * 'd'(void);
- * 's'(void);
- * 'u'(void);
- * 'k'(void);
- * 'n'(char text);
- * 'r'(unsigned int length, unsigned long int address);
- * 'w'(unsigned int length, unsigned long int address, char data);
Added some *.bin to test or you can follow the args mentioned above to create a *.bin (Little Endian) and inject it to the server (PS4IP:9090) using nc/ncat. I will create the complete client side project ASAP.
- Fork it!
- Create your feature branch: git checkout -b my-new-feature
- Commit your changes: git commit -am 'Add some feature'
- Push to the branch: git push origin my-new-feature
- Submit a pull request
- more system functions.
- Improve tcp communications.
- Improve memory allocation.
- process dump
- process list
No unknown bugs as far as I know already tested on IDC exploit page, and worked smoothly using nc/.bin
Feel free to comment below any bugs to fix. also your feedback is valuable.
CTurt -> the ***. Specter -> exploit implementation. IDC, xvortex, 2much4u, who else I missed (message me for the Credits)
Cheers to @HydrogenNGU for the heads up on Twitter earlier today!