https://github.com/ps4dev/elf-loader

Run ps4sdk elf files via TCP on you ps4
https://github.com/ps4dev/elf-loader

Last synced: 2 months ago
JSON representation

Run ps4sdk elf files via TCP on you ps4

• Host: GitHub
• URL: https://github.com/ps4dev/elf-loader
• Owner: ps4dev
• License: unlicense
• Created: 2016-05-10T19:26:33.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2018-07-28T19:10:48.000Z (over 6 years ago)
• Last Synced: 2024-08-03T23:05:19.330Z (6 months ago)
• Language: JavaScript
• Homepage:
• Size: 486 KB
• Stars: 29
• Watchers: 11
• Forks: 9
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• Awesome-PS4-Jailbreak - PS4 Elf Loader

README

        
# Elf loader

Runs ps4sdk elf files in-process on your PS4.

## Prerequisites

* clang (not the OSX version though)

* make

* [ps4sdk](https://github.com/ps4dev/ps4sdk)

* node.js to run server.js (or any alternative to serve /local)

* socat, netcat, etc. to send files and to communicate with the standard IO

## Important

The elf loader does not support dynamically linked executables. All libraries need to be statically linked into the executable. [ps4sdk](https://github.com/ps4dev/ps4sdk) provides a variaty of position independant, statically linkable libraries, such as a libc, for the PS4. Depending on their build system and requirenments, you can compile third party libraries using the ps4-lib target of the sdk. Alternatively you will have to alter their build system to compile them as PIC statically linked libraries.

## Example

```bash

# Build as raw binary to bin/ and then convert to ldr.js in /local (you can 'make keepelf=1' to debug)

make clean && make

# Start server

cd local

node server.js

# Browse ps4 browser to local server (:5350)

# Wait until the browser hangs in 'step 5'

# Connect debug/stdio channel

socat - TCP::5052

# Send elf file to the user space process for execution

socat -u FILE:ps4sdk-examples/libless/stress/bin/stress TCP::5053

# OR Send kernel elf file (mode for long-running code, or module-like code)

socat -u FILE:ps4sdk-examples/kernel/function-hook/bin/function-hook TCP::5055

# OR Send kernel elf file (runs in the browsers process, but is loaded and executed into the kernel)

socat -u FILE:ps4sdk-examples/kernel/cache/bin/cache TCP::5054

# Some examples (esp. kernel) use a second socket for their comminication. The default choice is 5088

# Connect to it after the upload to trigger the execution of the code - please see the examples sources for more

socat - TCP::5088

```

## Docker images

A stand alone elf-loader container is available (but currently a bit large):

```bash

# Make sure newest container is used (only do this as needed)

docker pull ps4dev/elf-loader

# Run the elf loader (listens on port 5350)

docker run -p 5350:5350 --rm ps4dev/elf-loader&

# Stop elf loader

docker kill $(docker ps -q -f ancestor=ps4dev/elf-loader)

```