NeoEnabler

Play PS4 games on your PS5 in PS4 Pro mode at higher resolutions, up to native 4K.

The PS5 already runs PS4 games that have PS4 Pro support in Pro mode. Games without it run as on a regular PS4. NeoEnabler makes those games start as if they were on a PS4 Pro (games with Pro support are left as they are). This alone does not make any game work: every game tested so far broke in Pro mode without its patch (black or corrupted image, or the game closing). The patches in xml/ fix each game for Pro mode and raise its resolution, so NeoEnabler is only useful for the games listed below.

You pick the patches in the NeoEnabler panel. A game starts in Pro mode, and gets the 8 GiB memory budget, only when one of its enabled patches needs it; every other game starts as usual.

Version 0.3.5 supports the 8 GiB memory budget without an HV unlock on firmware 13.20 and 13.60. See validation and limitations: 13.20 has a Bloodborne gameplay and restoration test; 13.60 has community reports of Bloodborne 4K gameplay with 8 GiB enabled and a successful launch after the availability fix.

• A jailbroken PS5 on firmware 4.00 to 13.60 (tested on 13.20) with an ELF loader, such as etaHEN or elfldr.
• ps-patch-system, loaded before NeoEnabler.

1. Download neo-manager.elf from the latest release.
2. After every console boot, load ps-patch-system first, then send neo-manager.elf with your payload sender (port 9021).
3. A notification on the PS5 confirms that NeoEnabler is enabled. It downloads the game patches from this repository and adds them to the ps-patch-system files (see Game patches).
4. Open the panel and tick the patches you want for each game.

The 8 GiB PS4 Pro memory budget follows patches marked "8 GiB" in the panel. This mode requires:

• Firmware 13.20 (Bloodborne gameplay and automatic restoration checked) or 13.60 (community-reported Bloodborne 4K gameplay with 8 GiB enabled).
• A running NeoEnabler manager and the validated ShellCore launch hook. The DATA path does not require an HV unlock and does not read or patch kernel TEXT.

Start from a reboot and load the jailbreak and ps-patch-system before this build. Do not mix it with an older 8 GiB memory payload or an existing kernel TEXT memory patch in the same boot. Close the game before quitting the manager. If a guard refuses a launch or reports a recovery failure, read the memory status before retrying.

When either condition is missing, patches that need 8 GiB are greyed out and cannot be enabled. Everything else works without 8 GiB.

NeoEnabler must keep running for the automatic Pro mode and 8 GiB: send it again after every reboot.

Open http://<PS5 IP>:8765 in a browser on your network, or the NeoEnabler shortcut in the PS5 Media tab.

• Games: every installed PS4 game that has a NeoEnabler patch for its installed version, with its icon, title ID, version and all of its patches. Tick a patch to enable it; the change goes straight to the ps-patch-system settings, there is nothing to save. Only one NeoEnabler resolution entry per game can be on: ticking one turns the others off. In a collection, each game in it can have one resolution on. The collection starts in its first game, so the other games' resolutions need one of the first game: the panel ticks it for you. Collections need NeoEnabler 0.3.3 or newer. Older versions keep only one resolution per title ID, and their patch sync replaces the entry of one game with another game's entry of the same name. Patches that need 8 GiB are marked and greyed out when 8 GiB is not available. Use the search bar to find a game by name or title ID.
• PS4 Pro mode and 8 GiB are automatic. When a PS4 game starts, NeoEnabler checks its enabled patches: the game starts in PS4 Pro mode only when one of them needs it, and 8 GiB is switched on before the game starts only when one of them needs it. 8 GiB returns to the original 5.25 GiB budget after the game closes.
• Status: PS4 Pro mode of the running game, 8 GiB state and the running game.
• Game patches: Update Patches downloads the patches from this repository (also done at startup).
• Logs: Show Logs, Download Logs, Save Logs and Save Diagnostic. They give one text with a report of the console, NeoEnabler's own log (/data/neo-enabler/neo.log) and the kernel log kept in /data/neo-enabler/kernel.log.
• Advanced (collapsed): Pro mode for every PS4 game, or 8 GiB kept on, regardless of the patches.

Quitting the manager stops the automatic Pro mode and 8 GiB until it runs again. Rebooting removes the hook. A failed kernel-write recovery of the memory budget requires a console reboot before launching games.

Anyone on your local network can open the panel.

Open GPU clock in the panel, select a target from 1800 to 2200 MHz in 50 MHz steps, and use Apply boost. The current clock reported by the SMU updates every two seconds. The target and enable flag are saved with Save Settings and requested again when a PS4 game starts. This works independently of NEO and 8 GiB, including PS4 base mode.

GPU boost is off by default, with 2200 MHz selected. It is confirmed working on firmware 13.20 and 13.60 and uses the stock /dev/mp1 driver, without patching the kernel or needing a hypervisor exploit. The sustained frequency may be lower than the target. A short gameplay test at 2200 MHz read around 2155-2200 MHz. FPS gains and long-term stability have not been established.

Disable boost and Quit restore the clock the game had before boost. When the game closes, the system manages the clocks again, and the next PS4 launch starts from a new baseline. If the clock is reset to 1800 MHz while the game runs, the manager restores the target up to three times. If a request or restoration fails, the panel shows the error and stops retrying: use Disable to retry the restoration before enabling again.

Boost does not change CPU clocks, thermal or power limits, memory bandwidth or ROPs. On other firmwares, or when the MP1 driver does not answer, the GPU clock tab is not shown.

Every game needs its patch from xml/ to work in PS4 Pro mode. NeoEnabler installs them for you:

1. At startup (and with Update Patches in the panel), NeoEnabler downloads xml/ from this repository and adds its entries to every ps-patch-system file of the same game in /data/user/patches/xml_orbis/ (all regions, matched by the game title). Entries already there are updated; other patches in those files are kept. An entry with the same patch lines under another name is renamed to the repository name, and stays enabled if it was. A game without a file gets a new <TITLE ID>.xml. Changed files are backed up first to /data/neo-enabler/xml-backup/<date-time>/ (the last 5 backups are kept).
2. In the panel's Games page, tick one resolution entry for the game, for example "Native 4K (PS4 Pro mode)".
3. For 4K entries, set the PS5 video output to 2160p.

Every NeoEnabler entry carries NeoRequires="pro" or NeoRequires="pro,8gib", which tells the manager what the game needs at launch. ps-patch-system ignores this attribute.

Supported games, resolutions and notes: docs/GAMES.md.

Patch IDs, how the hook works and how to build from source: docs/TECHNICAL.md.

Test results by game and firmware: docs/COMPATIBILITY.md. Report yours with the Test result form.

Entries with author "Local experiment" (Pro mode, resolutions, JC3 offline mode) and the NEO fixes inside the Bloodborne resolution entries were made in this project.

GPL-3.0 (LICENSE). The payload includes the ps5-payload-sdk runtime (GPL-3.0-or-later), so the binary must be distributed under GPL-3.0.

Third-party files keep their own licenses:

• src/dynlib.h, src/proc.h: Apache-2.0 (ps-patch-system), compatible with GPL-3.0.
• The Bloodborne resolution code from shadps4-emu/ps4_cheats: the repository declares no license. It is included with attribution to its author.