A RomM companion client for jailbroken PS5 consoles (etaHEN or onionHEN, with kstuff) and PS4 consoles (GoldHEN). Through my insatiable need to mod everything electronic I encounter, I had my 12.70 PS5 jailbroken the minute that P2JB was out. I maintain a RomM server to centralize all my legal ROMs, saves, and savestates, which all my devices sync with, and the PS5 needs similar treatment.

Background save sync
- Monitors save file changes in the background, and uploads them as soon as they've changed. Periodic syncs also ensure that your PS5 always has the latest saves and savestates.
Interactive library
- Browse your RomM library from RommPS, the native app (or some other device), download games and BIOS files into the right emulator folders, and resolve save conflicts.
Pluggable emulator profiles and multiple emulators per platform
- Fully customizable sync destinations, but includes frequently updated preset profiles for existing homebrew emulators.
- Can sync games and saves and states for multiple emulators per platform (PS2 on RetroArch and PS5SX2 as an example) using hardlinks.
Beautiful and Responsive UI
- Based on mihawk-99's Vulkan homebrew apps and BlackBearReloaded's UI kit, we get a nice, responsive feel. So worth it, it looks 1000x better.
Easter Egg
- Check in the Settings, scroll the settings list, see if you find the X.

Supported Emulators and Games

Technically, this RomM client will work with all emulators, but I have included profiles for the emulators that exist for the console as of Oct 2026.

Supported out of the box

Setup finds these on its own. Anything else can still sync by picking its folders during setup.

PS5

Emulator	Systems	Saves
RetroArch (mihawk-99's port)	NES, Famicom Disk System, SNES, Game Boy, Game Boy Color, Game Boy Advance, Genesis/Mega Drive, Master System, Game Gear, Sega CD, SG-1000, arcade (FinalBurn Neo), PS2 (LRPS2), PSP (PPSSPP), GameCube and Wii (Dolphin)	Saves and states
PSXS5 / SwanStationPS5	PS1	One memory card per game, and states
PS5SX2	PS2	Its two shared memory cards, backed up to RomM (5.3 or newer)
PS5N64	N64	Saves and states

PS5NES and Porpoise don't have presets yet, because neither works properly on my console right now:

PS5NES v7 looks for its games in PS5SX2's folder instead of its own.
Porpoise crashes the moment it leaves the app sandbox, with both OnionHEN and Lapy freeing it, so it fails to launch. Issue reported to the dev. In the meantime, you can sync files into the sandbox, but you won't have access to /data.

PS4 (experimental)

Emulator	Systems
RetroArch	The RetroArch systems above, wherever the PS4 build has the core
pSNES, pNES, pGEN, pGBA, pFBN	SNES; NES; Genesis, Master System, Game Gear, Sega CD, SG-1000; GBA, GBC, GB; arcade

Only RetroArch has been tested on the PS4 so far.

PS4/PS5 Games

If you are interested in downloading PS4 and PS5 games from your RomM server, RomM has direct FPKGi support, simply add it as a library. This sync client does NOT handle PS4/PS5 save syncing at this time, but is being researched for potential future inclusion.

Requirements

A PS5 running etaHEN or onionHEN, or a PS4 running GoldHEN
RomM 5.2.0 or newer (5.3.0 if you want to do shared memory card syncing instead of per-game)
RetroArch installed
Whichever other emulators you want

Install

Install RommPS from ProsperoStore and open it. That's it: RommPS carries the RomM Sync payload and starts it for you, then walks you through setup. Its last step makes RomM Sync start with every jailbreak, so you don't have to open the app for syncing to work.

Not using the store? Download PPSA76677.zip from the releases page, unzip it and copy the PPSA76677 folder to /data/homebrew/ on the console.

If you'd rather run just the payload, without the app:

Download the latest romm-sync.elf from the releases page.
Send it to the console (or use whichever favorite tool you wish):
```
nc -w 1 <ps5-ip> 9021 < romm-sync.elf
```
Set it up at http://<ps5-ip>:8780 from another device.

To start RomM Sync with the console, let your HEN start it: the last setup step does this for you. Both HENs start payloads/romm-sync.elf when romm-sync.elf.auto_start sits next to it, in /data/etaHEN/payloads or /data/OnionHEN/payloads (onionHEN's Toolbox has a toggle for it under Payloads). RomM Sync works out which HEN is running. If you build it yourself, make install PS5_HOST=<ps5-ip> copies it there over FTP (add PS5_FTP=ftp://<ps5-ip>:1337 PS5_HEN_DIR=/data/OnionHEN for onionHEN's FTP plugin).

PS4

Experimental. The PS4 build has only been tested with RetroArch so far. Standalone emulators may work, but haven't been confirmed. I spent all my focus on the PS5 build, so I didn't get to test as much, so consider it experimental and there may be gremlins for now.

Needs GoldHEN 2.4b18.5 or newer, whose payload menu runs ELF payloads.

Download the latest romm-sync-ps4.pkg from the releases page and install it with your package installer.
Open RomM Sync from the home screen. It copies its payload, romm-sync-ps4.elf, to /data/payloads/.
In GoldHEN Settings, open the payloader, pick romm-sync-ps4.elf and run it. Add it to the AutoRun queue there and it starts on every jailbreak.
Open RomM Sync again: it shows the web UI. It's also at http://<ps4-ip>:8780 from another device.

The app only installs the payload and shows the web UI; the payload does the syncing, in the background, whether or not the app is open. Without the package, copy romm-sync-ps4.elf to /data/payloads/ yourself (GoldHEN's FTP server, or make install-ps4 PS4_HOST=<ps4-ip>).

Don't send the payload to GoldHEN's network loader on port 9090: GoldHEN 2.4 crashes on ELFs sent there. Make sure the console's date and time are set (GoldHEN can keep them updated), or HTTPS won't work. RetroArch is found in /data/retroarch, with its cores in /data/self/retroarch/cores, as its retroarch.cfg says.

Updates

There are two pieces to keep updated, and they update separately:

RomM Sync (the payload) checks GitHub once a day (you can turn that off) and tells you when there's a new version. Settings can install it for you, but nothing installs on its own. Each payload release is signed, and RomM Sync only installs a file whose signature matches the key built into it, so nobody can slip a modified payload in through the updater.
RommPS (the app) updates through ProsperoStore, like any other homebrew in its catalog. If the payload ever falls behind what the app needs, RommPS tells you to update it.

You can always update either one by hand from the releases page.

Setup

The setup walks you through five steps:

Connecting to your server.
Approving the console in RomM, by scanning a QR code or entering a code.
Choosing which emulators to sync.
Checking what the first sync will do.
Choosing when to sync in the background.

Back up your saves before the first sync. Copy your emulator save folders to a computer or USB drive. RomM Sync keeps a local copy before replacing any file, but your own backup is the safest option.

PS2 Memory Cards

LRPS2 keeps every game on one shared memory card by default. RomM stores saves per game, so pick one of these during setup:

One card per game. Works with any RomM version. In RetroArch, open the LRPS2 core options and turn off Shared Memory Cards. After that, each game's card syncs like any other save. Saves already on the shared card stay there.
Back up the shared card. Needs RomM 5.3.0 or newer. The whole card is uploaded when it changes, and you can restore it from Settings. It isn't merged with other devices.

PSP, GameCube and Wii saves are synced as one zip per game, the same format other RomM clients use. Depending on the client, they may or may not support unzipping the saves (I don't truly know), but this client does!

My opinion? One card per game is better since 8MB memory cards fill up quick.

Emulator Profiles

I've included direct support for most of the emulators that are out right now, except for the ones that won't even launch... you can sync games, states, and saves anywhere you want, but the presets should do it for most people.

Settings has a JSON editor for emulator profiles, and a table showing which folders are used for each platform. A profile lists an emulator's folders and the RomM platforms it plays:

{
  "id": "retroarch",
  "name": "RetroArch",
  "root": "/data/homebrew/PPSA99169",
  "retroarch_cfg": "{root}/config/retroarch.cfg",
  "rom_dir": "{root}/content/{platform}",
  "save_dir": "{root}/savefiles",
  "state_dir": "{root}/savestates",
  "bios_dir": "{root}/system",
  "save_exts": ".srm,.sav",
  "platforms": [{ "romm": ["snes", "sfam"], "dir": "snes", "emulator": "snes9x", "core_name": "Snes9x" }]
}

Building

make host tools       # macOS or Linux build for development, plus tools/release-sign
tools/ps5-build.sh    # PS5 build in Docker, output in build/ps5/
tools/ps4-build.sh    # PS4 payload in Docker, output in build/ps4/
tools/ps4-build.sh ps4-pkg   # plus the PS4 home screen app (platform/ps4/app)
tests/e2e.sh          # end-to-end tests against a mock RomM server

Both consoles build from the same code in src/. What differs lives in platform/<console>/: platform.c (the src/platform.h interface), the make rules and the Docker SDK image. platform/console/ has the parts the PS4 and PS5 share, and platform/host/ is the development build.

P.S to the industry

If buying isn't owning, then piracy isn't stealing. 🖕

Shameless Plug

License

GPL-3.0. Parts of the console code are adapted from ftpsrv and websrv by John Törnblom. cJSON and qrcode-generator are MIT licensed. Monocypher is CC0 or BSD-2-Clause.

v1.2.1

Latest

2026-10-16 03:01:12 +02:00

C 44.7%

C++ 37%

Python 6.2%

Shell 6%

HTML 3.8%

Other 2.3%