# HyperHEN components and technical overview > Historical 0.9.2 inventory. The firmware routing table and integration > summary below describe the previous public release. The [0.9.4 appendix](#v094-appendix-hyper-and-runtime-continuity) records the current additions. > For current selectors, startup behavior and support boundaries, read the > [current README](../README.md), [release notes](../RELEASE_NOTES.md) and > [release build instructions](../BUILD_RELEASE.md). This document is the public technical inventory for HyperHEN. It describes what is built into the release, what remains an external dependency, how the firmware routes differ, and where each major component came from. HyperHEN is an integration project. It does not contain the initial PS5 kernel exploit and does not make an unmodified console load payloads. The first launch requires an already jailbroken system and an external `elfldr` endpoint. ## Project ownership HyperHEN integration, branding, firmware-route orchestration, release engineering, and project maintenance are by **MICHELE MEDIA**. The project is based on public PS5 homebrew and reverse-engineering work. All vendored upstream notices and licenses remain authoritative for their files. ## v0.9.2 integration summary Version 0.9.2 consolidates the previously separate firmware engines behind one exact-profile router and makes their completion contracts explicit. It adds or stabilizes the legacy 1.xx-4.51 route, the dedicated 5.xx hypervisor route, the A53/PPR and no-PPR HyperCore routes, and the 13.xx Rest Mode hypervisor route. Automount/backport ownership is restored as a required common stage wherever a complete HEN route exists, while incomplete profiles remain deliberately limited or unsupported. The same release integrates the HyperHEN-branded Toolbox and native Settings assets, plugin/container and title-targeted SPRX management, HyperDPI, HyperLinux clean-boot handoff, the optional startup voice, and three switchable debug services. Readiness markers, independent capability probes, longer A53 timeouts, Rest Mode state tracking, and explicit no-PPR gating prevent later services from starting on an engine that has not actually become ready. ## Release architecture The distributed `HyperHEN.elf` is a wrapper around a compressed bootstrapper. The wrapper verifies the expected size and SHA-1 of the unpacked bootstrapper before execution. The bootstrapper then selects one exact firmware route and starts the remaining embedded services in a fixed order. ```text external exploit host + elfldr:9021 | v HyperHEN.elf | v verified LZMA bootstrapper | +--> one-shot HyperLinux handoff, when armed | +--> exact firmware engine | |- legacy HEN: 1.xx-4.51 | |- 5.xx Byepervisor -> HyperCore | |- 13.00/13.20/13.60 Byepervisor -> Rest Mode -> HyperCore | |- A53/PPR -> HyperCore on exact 6.00-11.40 profiles | |- no-PPR HyperCore compatibility: exact 11.60-12.70 profiles | `- utility-only: 13.40/13.42 | +--> HyperHEN Automount +--> daemon + utility + ShellUI Toolbox +--> debug tools, plugins, payloads, when enabled and supported `--> HyperDPI, when enabled and supported ``` After the first hop, HyperHEN attempts to start its private loader on TCP port `9020`. Port `9021` remains the fallback supplied by the exploit environment. Embedded stages are launched serially and synchronize through explicit ready and failure markers; a dependent stage does not start after a failed required stage. ## Firmware routing Firmware matching is exact. A range in a project description must not be read as automatic support for every version inside that range. | Route | Exact firmware profiles | Startup contract | Components after the route | | --- | --- | --- | --- | | Legacy HEN | 1.00, 1.01, 1.02, 1.05, 1.10, 1.11, 1.12, 1.13, 1.14, 2.00, 2.20, 2.25, 2.26, 2.30, 2.50, 2.70, 3.00, 3.10, 3.20, 3.21, 4.00, 4.02, 4.03, 4.50, 4.51 | The embedded `ps5-hen` engine must publish its completion marker. HyperCore and the newer daemon route are not started on this branch. | HyperHEN Automount; legacy-ready notification | | Byepervisor 5.xx | 5.00, 5.02, 5.10, 5.50 | The embedded 5.xx stage must complete and publish its readiness marker before HyperCore starts. | HyperCore, Automount, daemon, utility, Toolbox, HyperDPI | | HyperCore A53/PPR | 6.00, 6.02, 6.50, 7.00, 7.01, 7.20, 7.40, 7.60, 7.61, 8.00, 8.20, 8.40, 8.60, 9.00, 9.05, 9.20, 9.40, 9.60, 10.00, 10.01, 10.20, 10.40, 10.60, 11.00, 11.20, 11.40 | The A53/PPR loader prepares the required environment and starts the source-built kstuff core. HyperCore publishes readiness only after its ShellCore transaction completes, and the bootstrapper independently verifies the `mprotect` capability. Missing required profile data fails closed. | Automount, daemon, utility, Toolbox, HyperDPI | | HyperCore compatibility, no PPR | 11.60, 12.00, 12.02, 12.20, 12.40, 12.60, 12.70 | The loader deliberately skips PPR installation and disables PPR-dependent runtime hooks. Automount and later services start only after the HyperCore completion marker and independent `mprotect` post-check both succeed. | HyperCore, Automount, daemon, utility, Toolbox, HyperDPI; no PPR-dependent features | | Byepervisor Reborn | 13.00, 13.20, 13.60 | The stage arms the Rest Mode path, waits for resume, and must publish readiness before HyperCore continues. | HyperCore, Automount, daemon, utility, Toolbox, HyperDPI | | Limited userland | 13.40, 13.42 | No complete Hypervisor or PPR prerequisite is present. The route does not claim a kernel-core readiness state. | Utility only; no HyperCore, Automount, daemon/Toolbox, HyperDPI, plugins, or payload auto-start | The source-built HyperCore contains ShellCore tables for 1.00, 1.01, 1.02, 1.12, 1.14, 2.00, 2.20, 2.25, 2.26, 2.30, 2.50, 2.70, 3.00, 3.10, 3.20, 3.21, 4.00, 4.02, 4.03, 4.50, 4.51, 5.00, 5.02, 5.10, 5.50, 6.00, 6.02, 6.50, 7.00, 7.01, 7.20, 7.40, 7.60, 7.61, 8.00, 8.20, 8.40, 8.60, 9.00, 9.05, 9.20, 9.40, 9.60, 10.00, 10.01, 10.20, 10.40, 10.60, 11.00, 11.20, 11.40, 11.60, 12.00, 12.02, 12.20, 12.40, 12.60, 12.70, 13.00, 13.20, 13.40, 13.42, and 13.60. These tables are compatibility data, not a claim that the complete HyperHEN stack was tested on every listed firmware. In particular, a ShellCore table does not supply the missing Hypervisor/PPR prerequisite for 13.40 or 13.42. The combined HyperCore path has console-log validation on firmware 5.00. Additional profiles require hardware testing. Unsupported, incomplete, or non-exact firmware profiles are rejected instead of borrowing offsets from a nearby release. ## Core components | Component | Source or revision | Inclusion | HyperHEN role | | --- | --- | --- | --- | | [OnionHEN](https://github.com/aydencharles/onionHEN) | Supplied source base | Adapted in tree | Modular HEN/Toolbox structure and retained compatibility interfaces | | [etaHEN](https://github.com/LightningMods/etaHEN) | Upstream ancestry of the supplied tree | Adapted in tree | Original daemon, utility, ShellUI, payload, overlay, and cheat architecture | | [GoldHEN](https://github.com/GoldHEN/GoldHEN) | Design reference | Not embedded | All-in-one HEN product model and user-experience inspiration | | [kstuff-a53](https://github.com/Soonniicc/kstuff-a53) | `0a69ea31759f048d24b38bfaa23dbec1fd065916` | Built from vendored source | HyperCore integration container | | [kstuff-lite](https://github.com/EchoStretch/kstuff-lite) | Base `2506a5b15af501734f7ea3dce2759c077cdb76c6` | Built as part of HyperCore | Kernel support and runtime core | | [ppr-patch](https://github.com/drakmor/ppr-patch) | Base `fd4c8224563130e9698d3b2b2f44712826ceb525` | Adapted into the HyperCore loader | A53/PPR preparation and transport | | [BackPork](https://github.com/BestPig/BackPork) | Supplied integration base | Built as part of HyperCore | Process monitoring and the original `app0`/`fakelib` mount path; paused when HyperHEN Automount owns the lifecycle | | [a53-code-exec](https://github.com/cragson/a53-code-exec) | Technical reference | Reference only; its ELF is not shipped | A53 research reference | | [Byepervisor Reborn](https://github.com/PS5Dev/Byepervisor-Reborn) | `ea04f7132b837087f552c57261cb800481a3a910` | Built from vendored source | Rest-Mode hypervisor stage for 13.00, 13.20, and 13.60 | | Byepervisor 5.xx | `9c182a1622dd43ea56641a7080638af3673a723f` | Built from supplied source | Dedicated 5.00, 5.02, 5.10, and 5.50 stage | | [ps5-hen](https://github.com/cragson/ps5-hen) | `699870d16ca4cd5cd70fc88f8cf61b3953d4a292` | Built from supplied source | Legacy engine for the exact 1.00-4.51 profile set above | | [ShadowMountPlus](https://github.com/drakmor/shadowMountPlus) | `98c524890176c7b474fcb03387bec88c4a559861` | Built and embedded as `hyperhen_automount.elf` | Exclusive common automount, image/title discovery, package redirect, and fakelib lifecycle | | [onionHEN DPI v2](https://github.com/OnionBuddies/onionHEN-dpiv2-plugin) | `4e80389a87dd709f5f7ba316cbaa23d05a3cafc3` | Built and embedded as HyperDPI | Browser upload, queue, staged package, and progress service | | [onionHEN Plugin SDK](https://github.com/OnionBuddies/onionHEN-plugin-sdk) | `0cf4346536705fb271ba0eb2226d97ebcb23559c` | Statically linked into HyperDPI | Stable client ABI and HyperHEN plugin-service transport | | pLinux5-NG | Supplied source archive, SHA-256 `316e25ecd25d021ba0318768ca623c2d3891a78c73c4cd7ecd038c259f1ebb64` | Built into HyperLinux | High-firmware Linux boot route and hypervisor handoff | | [ps5-linux-loader 2.5](https://github.com/ps5-linux/ps5-linux-loader) | Supplied archive, SHA-256 `610fa2e1da7e131b4365c2a6e06961b79dc208da89ad6102f706777386911ecb` | Built into HyperLinux | Linux kernel/initrd loader and upstream penguin artwork | | [PS5 Payload SDK](https://github.com/ps5-payload-dev/sdk) | Build dependency | External toolchain | Prospero compiler, headers, runtime, and CMake integration | | [elfldr](https://github.com/ps5-payload-dev/elfldr) | `02cfe91eb3f9697787460ad77d73ff951f801f50`; John Törnblom | External first hop; retained loader source is adapted for internal builds | Initial transport on 9021, private HyperHEN loader on 9020, and separately isolated debug-LAN loader on 9025 | | [klogsrv](https://github.com/ps5-payload-dev/klogsrv) | `c1b64bd3d3b069a09b1a173a82858cba97a5656f`; John Törnblom, with port/quiet argument contribution by Al-Azif | Verified upstream PS5 ELF embedded unchanged | Switchable Toolbox kernel-log server on TCP 3232 | | [ftpsrv](https://github.com/ps5-payload-dev/ftpsrv) | `23737c4738d15b9b9b036665bbf008d8fd6d82d2`; John Törnblom, with current-tree contributions from EchoStretch, Al-Azif, Matthew Vanek, and Gezine | Verified upstream PS5 ELF embedded unchanged | Switchable Toolbox FTP server on TCP 2121 | The exact snapshot notes and local integration boundaries are kept in each component's `third_party/*/HYPERHEN_VENDOR_LOCK.md` file. Supplied reference ELFs are used only for comparison when the matching vendor lock says so; the release build consumes source-built artifacts. ## Libraries and technical foundations | Project | Use | | --- | --- | | [libhijacker](https://github.com/astrelsky/libhijacker) | Process hijacking and kernel read/write support | | [NineS](https://github.com/buzzer-re/NineS) | ShellUI injection foundation | | [cJSON](https://github.com/DaveGamble/cJSON) | Configuration and JSON parsing | | [7-Zip LZMA SDK](https://www.7-zip.org/sdk.html) | Bootstrapper compression and unpacking | | [miniz](https://github.com/richgel999/miniz) | ZIP and cheat-data decompression | | [Keystone Engine](https://www.keystone-engine.org/) | ShnExt assembly support | | BearSSL `79c060eea3eea1257797f15ea1608a9a9923aa6f` | HyperCore cryptographic dependency | | LibTomCrypt `b96e96cf8b22a931e8e91098ac37bc72f9e2f033` | HyperCore cryptographic dependency | | ISA-L Crypto `07d0b253843ace996aa5a44f538c9b83b085aba6` | HyperCore cryptographic dependency | The cheat subsystem also carries the AES, Base64, SHA-256, and miniz sources under `third_party/cheat_support`. The ShellUI and NID resolver use the vendored SHA-1 implementations present in the repository. ## Referenced community work The following projects are not embedded as independent runtime payloads but informed specific compatible behavior or provide optional data/services: - [ps5-payload-manager](https://github.com/itsplk/ps5-payload-manager) by itsplk: listener recovery and socket rebind behavior after Rest Mode. - [HEN-Cheats-Collection](https://github.com/TeeKay87/HEN-Cheats-Collection) by TeeKay87: optional community cheat catalog used by cheat sync. - [PHU Games Tools](https://github.com/ArkSama) by ArkSama: FPS sampling reference used by the in-game overlay. - [onionHEN-ftpsrv-plugin](https://github.com/OnionBuddies/onionHEN-ftpsrv-plugin): optional external FTP plugin. It is not embedded in `HyperHEN.elf`. ## Embedded service responsibilities ### HyperCore HyperCore is produced locally from the pinned kstuff-a53 tree. The build joins the kstuff-lite base, A53/PPR loader work, and the BackPork monitor into one source-built intermediate ELF. HyperHEN does not accept the old precompiled artifact found in the upstream archive. ### HyperHEN Automount ShadowMountPlus is built as the single active automount owner. Before HyperCore starts, the bootstrapper claims the kstuff automount sentinel so the native kstuff scanner and integrated BackPork monitor do not compete with it. If the automount stage cannot initialize, ownership is released and later dependent startup is stopped. The optional SceShellCore bridge is used only for exact verified profiles. An offset-free lifecycle watcher provides the shared pre-exec event path where the bridge is unavailable; it does not invent or approximate missing offsets. ### Daemons and Toolbox The utility daemon starts before HyperCore on the modern route. Once the firmware engine and automount are ready, the critical daemon starts the ShellUI injection and Toolbox. The two-daemon design keeps utility operations separate and lets the critical service supervise recovery. The Toolbox manages configuration, plugins, user payloads, cheats, overlays, network services, account tools, cooling, mount options, and the one-shot Linux handoff. Runtime settings use one versioned INI schema shared by the UI and services. ### Built-in debug services Advanced Debug exposes separate on/off controls for `klogsrv`, `ftpsrv`, and a LAN ELF loader. The first two payloads are verified against their recorded SHA-256 values before they are embedded and are materialized under `/data/HyperHEN/tools`. The LAN loader is source-built as `hyperhen_debug_elfldr.elf`. All three start through the private 9020 loader, and HyperHEN stores each returned PID plus process identity before allowing a stop operation. The LAN loader uses separate state files and TCP 9025, so it cannot collide with the private 9020 loader or the external 9021 first hop. These services are reachable from the network and have no HyperHEN authentication layer. They are disabled until selected in the Toolbox and should be exposed only on a trusted LAN. They are available only on firmware routes that reach the modern daemon/Toolbox stage. ### Plugin runtime Standalone plugin ELFs and compatible descriptor-bearing containers live in `/data/HyperHEN/plugins`. HyperHEN validates the container identity and embedded ELF separately, then launches only the embedded ELF through its private loader. Game-process PRX/SPRX modules use a separate catalog and exact title targeting. ### HyperDPI HyperDPI is built from pinned GPL source and launched from its embedded image; no sidecar DPI ELF is required. Its listeners are disabled by default because the upstream protocol has no client authentication. Enable it only on a trusted local network. ### HyperLinux HyperLinux is deliberately isolated from an already active HyperCore. The Toolbox writes a one-shot marker, the user performs a full reboot, and the next HyperHEN launch consumes that marker before normal HEN services start. Exact HyperLinux profiles are 3.00, 3.10, 3.20, 3.21, 4.00, 4.02, 4.03, 4.50, 4.51, 5.00, 5.02, 5.10, 5.50, 6.00, 6.02, 6.50, 7.00, 7.01, 7.20, 7.40, 7.60, 7.61, plus the experimental 13.20 path. ## Runtime paths and interfaces | Path or interface | Purpose | | --- | --- | | `/data/HyperHEN/config.ini` | Primary versioned configuration | | `/user/data/HyperHEN/config.ini` | User-data configuration mirror | | `/data/HyperHEN/plugins/` | Standalone plugin ELFs and compatible containers | | `/data/HyperHEN/payloads/` | User-supplied payload ELFs | | `/data/HyperHEN/tools/` | Materialized embedded debug-service payloads | | `/data/HyperHEN/cheats/` | JSON, SHN, MC4, and ShnExt cheat sources | | `/data/HyperHEN/sprx/catalog.ini` | Title-targeted PRX/SPRX catalog | | `/data/HyperHEN/HyperHEN.log` | Main runtime log | | `/data/HyperHEN/HyperHEN_crash.log` | Preserved crash and backtrace log | | `/system_tmp/hyperhen/ipc/plugin_service` | Plugin-service IPC endpoint | | TCP `9021` | External first-hop loader supplied by the exploit environment | | TCP `9020` | Private HyperHEN loader used after bootstrap | | TCP `9025` | Toolbox-controlled LAN ELF loader | | TCP `3232` | Toolbox-controlled kernel-log server | | TCP `2121` | Toolbox-controlled FTP server | | TCP `12800` | Default HyperDPI WebUI port when explicitly enabled | ## Build and reproducibility The release build uses the PS5 Payload SDK, CMake, Ninja, Clang/LLVM, GNU Make, NASM or Yasm, and `xz`/`lzma`. `scripts/build.sh` validates the vendored inputs, builds the firmware engines and services from source, assembles the bootstrapper, compresses it, writes its size and SHA-1 metadata, and links the final wrapper. ```shell export PS5_PAYLOAD_SDK=/path/to/ps5-payload-sdk ./scripts/build.sh --jobs 8 ``` The normal output is `build/bin/HyperHEN.elf`. Intermediate embedded artifacts remain under `build/vendor/`. See the root README for the full output table and test commands. ## License boundaries HyperHEN is distributed under GNU GPL-3.0. Vendored third-party files retain their own copyrights, licenses, and notices. HyperLinux contains AGPL-3.0 work from pLinux5-NG and retained GPL-3.0 work from ps5-linux-loader. Cryptographic subcomponents inside HyperCore retain their individual license files. The supplied Byepervisor Reborn, Byepervisor 5.xx, and ps5-hen snapshots do not contain standalone license files at their vendored roots. The supplied Keystone archive likewise lacks matching license metadata in this tree. Their upstream redistribution terms must be confirmed and the appropriate notices added before treating this source tree as a legally complete public release. See [`../THIRD_PARTY_NOTICES.md`](../THIRD_PARTY_NOTICES.md). The project is unofficial, is not affiliated with Sony Interactive Entertainment, and is intended for research and homebrew use on hardware owned by the user. There is no warranty. ## v0.9.4 appendix: Hyper and runtime continuity This appendix updates the historical inventory above; it does not change the meaning of the v0.9.2 snapshot. The current router has **67 exact firmware entries**, grouped in the [current README](../README.md#exact-firmware-profiles): 25 legacy-selector entries, four 5.xx-selector entries, 25 A53/PPR entries, the dedicated 9.40 entry, six no-PPR entries, four 12.70/13.xx hypervisor entries and two 13.40/13.42 lite entries. A table entry is compatibility data, not proof of hardware validation for every console. ### Hyper integration Hyper is an integrated background voice worker. Its independent Toolbox entry is on the main page below **Content Install & Management**, separate from Advanced Debug. Holding **L1 + R1 + Square** activates a turn; the DualSense microphone supplies speech and its speaker plays the response. The saved `hyper.enabled` setting defaults to true. The worker is started only after the existing Toolbox/runtime and asset-readiness requirements are satisfied. The assistant combines local Whisper speech recognition, Qwen2.5 GGUF conversation through llama.cpp, built-in short replies, and eSpeak NG voice synthesis. Model files stay in `/data/Hyper/models`; installed voice data stays in `/data/Hyper/espeak-ng-data`. The installer uses checksum-pinned model downloads and separately installs the bundled voice data. It exposes eight AI model choices and automatic voice selection plus 85 variants. Downloading a model and selecting the active model are independent actions. The interface and speech language follow the console language. The smallest model, **Qwen2.5 0.5B Q4_K_M**, is the recorded working voice configuration. All other catalog models remain **experimental / beta**. The latest R45 7B Q5_K_M console test loaded the model and generated five tokens, but reached the 90-second reply deadline without audio playback. R45 uses a reusable 512 MiB weight arena and a persistent four-thread CPU pool for its 7B path. The arena cap is not a total-process memory limit, and these changes are not a claim of usable 7B dialogue performance. No GPU inference backend is enabled. The documented functionality is local voice conversation; log-reading, service-control and payload-launching AI tools are not advertised as implemented features. See [Hyper usage](../README.md#hyper--local-voice-assistant-beta), [worker source and dependency notes](../source/hyper/README.md), and [the release build recipe](../BUILD_RELEASE.md). The release-compatible build preserves the exact R45 worker as a verified input; the worker source and an optional independent rebuild recipe are also included. ### 13.xx HyperCore and native runtime The **13.00, 13.20 and 13.60** Bypervisor routes retain the restored public 0.9.2 HyperCore component. The selection is restricted by [`hypercore_13xx_rollback.h`](../source/bootstrapper/include/hypercore_13xx_rollback.h); it does not select the rollback for 12.70 or the 13.40/13.42 lite routes. **ShadowMountPlus 1.7 beta9 remains a separate Automount stage.** Native release links explicitly use the isolated CRT containing the corrected 13.60 initializer. It is linked after application objects and libraries with `-nostartfiles`; the build does not silently use the installed SDK default or modify that SDK. The pinned CRT SHA-256 is `817750baf8ff32deb2b480f5c4640978372fe06a952697befa21bc7788edd09b`. The [build instructions](../BUILD_RELEASE.md) record the required input, adaptation recipe and scope. The 13.60 runtime correction was confirmed on the R42 test build; retaining it and passing local checks do not certify every 0.9.4 firmware combination. ### Bypervisor attachments and WebKit handoff The separate release attachments are the original **Byepervisor Reborn** for 13.00/13.20/13.60, the **12.70** variant, and **AUTO 9.40**. The original Reborn attachment is distinct from the adapted component embedded in HyperHEN; its provenance is recorded in the [vendor lock](../third_party/byepervisor-reborn/HYPERHEN_VENDOR_LOCK.md). The download links and exact sequence are in the [current startup guide](../README.md#bypervisor-downloads-and-startup-procedure): **WebKit → matching Bypervisor → Rest Mode → resume → WebKit again → HyperHEN.** After launching HyperHEN in the second WebKit session, close the browser manually and allow the existing two-second quiet interval while Automount and the Toolbox finish initializing. The 5.xx selector retains its own integrated choice; no separate 5.xx attachment is added for this procedure. The 13.40/13.42 lite route remains separate.