PS Vita Recovery Menu changelog
v1.2.2 · Nov 16, 2026
Themes. Give the recovery menu a different look, including a PSP M33-style Retro theme.
- New Settings menu on the main menu (above Reboot). It holds the new Theme screen, and FTP Server, Cheat Manager and Check for Updates moved into it, so the main menu keeps the recovery tools. Advanced keeps only system tools.
- Settings > Theme: choose Classic (the normal green look) or Retro, an M33 recovery style: black screen, the PSP debug font, all text in one colour and the selected row in white, with no bars. Retro colours: Red, Orange, Amber, Yellow, Lime, Green, Mint, Cyan, Blue, Purple, Magenta, Pink, Silver.
- The whole app changes as you move through the list (live preview). X saves, O puts the saved theme back. Saved in
ux0:data/vita_recovery/theme.cfg; delete that file to go back to Classic. - Matrix Rain (Retro themes only): turn it on or off with Square on the Theme screen (saved with the theme when you press X). Falling letters, digits, coding symbols, PSP-font extras (Greek / maths signs, card suits) and whole code words such as
sceIoOpen,0x80010002,*KERNEL, in a dim shade of the theme colour. It falls behind every screen, and each line of text gets a black backing so the rain never runs through words. It pauses while the app is busy working. - Every screen follows the theme. OK / warning / error colours (green / yellow / red) keep their meaning in every theme.
- The PSP font comes from pspsdk (BSD license, see
THIRD_PARTY_NOTICES.txt). - Fix: closing a tool with O (Theme, FTP Server, Cheat Manager, Check for Updates, and every other full-screen tool) could also take the menu back one more level, for example from Settings straight to the Main Menu. A button still held when a tool closes no longer counts as a new press.
- Fix: FTP Server screen. The drive list ran off the bottom of the screen, so the last drives and the connection tips were cut off. Drives are now shown in two columns, each marked read/write (green), read-only (yellow, system drives) or not mounted.
- No boot plugin changes: just install the VPK.
Screenshots
s04 main retro red
themes all colours
matrix rain
s02 settings classic
s03 ftp classic
Install
Install VitaRecovery_v1.2.2.vpk with VitaShell. No boot plugin changes, so you do not need to reinstall Boot Recovery. "Enable Unsafe Homebrew" must stay ticked in HENkaku Settings.
Tested on PS Vita 2000 (3.65 Ensō) and PCH-1101 3G (3.60 and 3.65 Ensō), all with SD2Vita.
v1.2.3 · Nov 16, 2026
Crash Reports, and a File Manager that opens files.
- Boot Diagnostics > Crash Reports (new section). Lists the crash reports the Vita saved in
ux0:data(psp2core-*.psp2dmp), newest first, with date, time and what crashed, plus how much space they use. - Home screen (SceShell) crashed 2+ times is reported as a warning: that is almost always a plugin under
*main. Suggested fix: turn*mainplugins off one by one, newest first (the Plugins section shows the newest plugin files). - Crash reports using 100 MB or more of
ux0:are reported as a warning. Old reports can be deleted fromux0:datawith the File Manager. - Fix: File Manager said "File too large to view" for almost every file. The viewer only opened files under 8 KB. Now:
- files up to 256 KB open in full; bigger files show their first 256 KB with a note on top;
- binary files (eboot.bin, .skprx, images) open as a hex view instead of garbage;
- Up/Down scroll and keep scrolling while held, L/R move a page at a time, Left/Right scroll long lines sideways;
- the title shows which lines you are on ("19-35 of 863").
- Battery in the title bar: the battery level and an icon under "By DrinkingSubset" on every screen, read live from the Vita (checked every 2 seconds). Yellow at 20% or less, red at 10% or less, a lightning bolt while charging. Hidden on PS TV.
- File Manager: the folder path was drawn twice on top of itself; long paths now show "..." and the last part so they never run under the battery.
- Menus: the "< Back" rows are gone from Advanced, Plugins and Registry Hacks, like Settings. O goes back in every menu.
- No boot plugin changes: just install the VPK.
Screenshots
Boot Diagnostics summary
Battery states
File Viewer text
File Viewer hex
Install
Install VitaRecovery_v1.2.3.vpk with VitaShell. No boot plugin changes, so you do not need to reinstall Boot Recovery. "Enable Unsafe Homebrew" must stay ticked in HENkaku Settings.
Tested on PS Vita 2000 (3.65 Ensō) and PCH-1101 3G (3.60 and 3.65 Ensō), all with SD2Vita.
v1.2.1 · Oct 31, 2026
Boot Diagnostics, Rebuilt
Boot Diagnostics is there to find the real cause when your Vita misbehaves. This update removes the false alarms and makes real problems much easier to spot.
✅ No boot plugin changes. Just install the VPK; you don't need to run Install / Update Boot Recovery this time.
What's new
- New layout and easier navigation
- Summary screen: overall result at the top ("NO PROBLEMS FOUND" or "1 PROBLEM, 2 WARNINGS"), one row per section with its status, and a short "What to do" list. It opens on the first section with a problem.
- Section screens: press X to open one. L/R jumps between sections, Up/Down scrolls, Square re-scans, O goes back. Long lines wrap instead of running off the screen, and each section lists its own fixes.
- Clearer levels: FAIL only for things that can stop your Vita booting CFW or lose storage, WARN for likely causes of trouble, INFO for plain facts.
- Fixed: "HENkaku file missing" while HENkaku was running. It now checks whether taiHEN and HENkaku are actually loaded and looks for their files in
ur0:tai,ux0:taiandimc0:tai. - No more "High plugin count (boot loop risk)". Lots of setups run 20+ plugins just fine. The count is now shown per section, as information.
- New plugin checks:
- plugins listed in
config.txtwhose files are missing - kernel plugins (
.skprx) outside*KERNEL, or user plugins (.suprx) inside it, which never load - the same plugin listed twice
henkaku.skprx/taihen.skprxadded by hand- your newest plugins, since the newest one is the first suspect when something breaks
- Storage: two storage plugins on at the same time (StorageMgr, YAMT, gamesd, sdgamesd, usbmc) is reported as a problem. Switched-off
#lines no longer count. - tai Config: shows which
config.txtthe app edits, and warns if bothux0:taiandur0:taihave one. - Boot Recovery section: whether the boot plugins are installed and up to date.
- Exploit names follow the current Vita hacks guide: HENkaku (3.60), h-encore/HENlo (3.65–3.68), h-encore2/HENlo (3.69–3.74).
Tested on
- PS Vita 2000 (3.65 Ensō)
- PS Vita PCH-1101 3G (3.60 Ensō)
- PS Vita PCH-1101 3G (3.65 Ensō)
All with SD2Vita. On one of them, Boot Diagnostics found a real problem: a misspelled YAMT helper line in config.txt that had been failing silently at every boot.
Install
- Download
VitaRecovery.vpkbelow and install it with VitaShell. - Open Advanced > Boot Diagnostics to check your setup.
Full details are in [CHANGELOG.md](CHANGELOG.md).
boot_diagnostics_summary
boot_diagnostics_cfw
boot_diagnostics_tai_config
boot_diagnostics_plugins
boot_diagnostics_storage
v1.2.0 · Oct 30, 2026
Home Screen Layout backup & restore
Lost your folders and bubble order after a Rebuild Database? Not anymore.
⚠️ After installing, go to Advanced > Boot Recovery > Install / Update Boot Recovery, then reboot.
The boot plugin changed in this version. The app will remind you with a pop-up if you forget.
"Enable Unsafe Homebrew" in HENkaku Settings must stay ticked.
What's new
- Home Screen Layout (new on the main menu)
- Back Up Layout: saves your pages, folders (names and icons), bubble order and each page's wave colour to
ux0:data/vita_recovery/layout/. The previous backup is kept too. - Restore Latest / Older Backup: puts everything back where it was, then restarts the Vita to apply it. Your current database is kept as
ur0:shell/db/app.db.prelayout, just in case. - Apps you've uninstalled since the backup are skipped. Apps you installed after it are added after the last bubble.
- Rebuild Database now backs up your layout first. After the rebuild, open Home Screen Layout > Restore Latest Backup to get your folders back.
- Boot plugin update reminder: if the boot plugins on your Vita are older than the ones in the app (or only partly installed), a pop-up tells you and takes you straight to Boot Recovery.
Requirements
- HENkaku / Ensō on firmware 3.60–3.74, with "Enable Unsafe Homebrew" ticked
- Home Screen Layout restore and Rebuild Database need Ensō
Tested on
- PS Vita 2000 (3.65 Ensō)
- PS Vita PCH-1101 3G (3.60 Ensō)
- PS Vita PCH-1101 3G (3.65 Ensō)
All with SD2Vita. Sony memory cards are not tested yet; reports are welcome.
Install
- Download
VitaRecovery.vpkbelow and install it with VitaShell. - Open the app, then go to Advanced > Boot Recovery > Install / Update Boot Recovery.
- Reboot.
Full details are in [CHANGELOG.md](CHANGELOG.md).
v1.1.9 · Oct 29, 2026
v1.1.9
Requires HENkaku Settings > "Enable Unsafe Homebrew" to be ticked (the same setting VitaShell needs). Without it the app will not launch. No boot plugin changes — just install the VPK.
- The app is now built as "unsafe" homebrew. It can read all system drives, which is needed for correct System Info (and for layout backup/restore planned for v1.2.0).
- System Info – real firmware: now asks the system's VSH bridge, which returns the real version even with HENkaku's Version Spoofing on (tested: 3.65 Enso slim spoofed to 3.74 now shows "3.65 (system reports 3.74)"). The firmware tier is now correct too, so screens that depend on it (like the Rebuild Database Enso note) no longer get a spoofed value. The debug line shows every source:
raw(partition),mod(os0 module header),vsh,sys. - System Info – model and motherboard: taken from the hardware info chip when available (USS = PS Vita 2000, IRS = 1000, IRT = 1100 3G, DOL = PS TV). This fixes the Slim 2000 showing as "1000 (OLED)" (tested: USS-1002), and 3G units now show as "PS Vita 1100 (3G OLED)" with an IRT-002 (3G) board (tested on two PCH-1101).
- New "Drive access" section in System Info: shows which drives the app can see and whether they are RW or RO, plus whether
app.dbis readable. The Detection debug section also shows the raw hardware info bytes. - Write protection for system drives: File Manager and the FTP server can read every drive but can only write to user storage (
ux0: ur0: uma0: imc0: xmc0: grw0:).os0: vs0: sa0: pd0: tm0: ud0: vd0:and raw devices are always read-only (upload, delete, rename, new folder are refused). Before, File Manager allowed writes tovd0:, and FTP had no checks. - FTP lists the system drives too (read-only), and a small handle leak when listing drives is fixed.
- File Manager: on read-only drives, Delete and Rename are greyed out and labelled "(read-only drive)".
Tested on: PS Vita 2000 (3.65 Enso + SD2Vita), PS Vita 1100 3G (3.60 Enso) and PS Vita 1100 3G (3.65 Enso).
v1.1.8 · Oct 28, 2026
v1.1.8
No boot plugin changes — just install the VPK.
- New: Plugin Fix Mode > Undo Safe Mode. Puts back your exact config from before Safe Mode ran, including plugins you had deliberately turned off. Safe Mode now keeps that copy every time it runs: in Plugin Fix, at L-trigger boot (
<config>.before_safemode), and in Restore / Unbrick (tai_backup/<drive>_config_before_safemode.txt). Undo uses the newest one. - Running Safe Mode a second time no longer overwrites that copy with the already-disabled config. Plugin Fix tells you when Safe Mode is already active.
- "Re-enable All" now says what it really does: it turns on all plugins, including ones you had turned off.
- Fix: the Plugins list now re-reads
config.txtevery time you open it. Before, it was read once at app start, so after Plugin Fix or Restore / Unbrick changed the config, it still showed the old ON/OFF states until the app restarted. - Plugin Fix header now reads "N plugins in config: X ON, Y OFF" instead of "N plugins loaded", which sounded like N were running.
- Plugin Fix backup / restore / undo now handle configs up to 128 KB (was 16 KB).
restore.logno longer grows forever: over 32 KB it's moved torestore.log.oldand a new log starts.
Tested on: PS Vita 2000 (3.65 Enso + SD2Vita) and PS Vita 1000 (3.60, 3.65 Enso + SD2Vita)
v1.1.7 · Oct 26, 2026
v1.1.7
Safety release based on an outside code review of v1.1.6.
After installing, open Advanced > Boot Recovery > Install / Update Boot Recovery, then reboot. Both boot plugins changed.
- Boot entry (hold R) is more reliable and can't get stuck.
boot_trigger.suprxnow launches the menu when the kernel plugin saw R/L held during early boot, not only if R is still held when the home screen loads. Every wait now has a time limit: 60 s for LiveArea, 15 s of launch retries. Before, both loops ran forever, a likely cause of the "custom boot splash + R" boot loop. - Boot loop breaker: after two boots where recovery was requested but the app never started, the plugin stops auto-launching and the Vita boots normally. Flags left over from an earlier boot are cleared at the start of each boot.
- Boot Recovery installer can update in place. "Install Boot Recovery" is now "Install / Update Boot Recovery". When the plugins are already installed, it copies this version's plugin files over the old ones (config untouched) instead of saying "uninstall first". The status line shows "UPDATE AVAILABLE" when the installed plugins differ from the app's.
- Rebuild Database keeps the old database: the boot plugin renames
app.dbtoapp.db.bakinstead of deleting it. - Restore / Unbrick is safer:
- Safe Mode Boot and Reset taiHEN Config back up each config first (to
ux0:data/vita_recovery/tai_backup/) and refuse to change anything if the backup fails. - Both now keep HENkaku, storagemgr / gamesd (SD2Vita) and the boot recovery plugins enabled. Before, they disabled or dropped them, so on SD2Vita ux0: (and this app) could disappear.
- Safe Mode keeps blank lines and line endings. Reset no longer silently overwrites an existing
ur0:tai/config.txtfallback. - "Rebuild LiveArea Database" now runs the same boot plugin flow as Sony Recovery. The old direct delete never worked and reported "already gone" as success.
- Safe config writes everywhere: Restore / Unbrick, Plugin Fix (backup/restore/reset) and the Recovery Installer now write to a temp file, read it back, and swap it in with the old file kept as
.olduntil the swap succeeds. A power cut can no longer leave the config missing. - Plugin Fix "Reset to Minimal" keeps storagemgr / gamesd / boot recovery plugin lines.
- Sony Recovery > Restore PS Vita System is now an honest guide. It explains how to factory reset with Sony's Safe Mode (R + PS + Power) instead of running a fake "restore". The old code only started and stopped a system module and rebooted. The Safe Mode hint in the footer now says R+PS+Power.
- "System Write Mode" removed from Advanced: the toggle did nothing (File Manager always keeps os0:/vs0: read-only).
- Repo cleanup: removed old unused copies
source/boot_recovery.c,source/boot_trigger_user.c,source/CMakeLists.txt, and the stale prebuiltboot_recovery.skprx/boot_trigger.suprxin the project root (the VPK always uses freshly built plugins)..gitignorecovers build folders. - README rewritten for the current version: features, install/update steps, the real boot flow, safety features, known issues.
Tested on: PS Vita 2000 (3.65 Enso + SD2Vita) and two PS Vita 1000s (3.60, 3.65 Enso + SD2Vita).
v1.1.6 · Oct 26, 2026
After installing, open Recovery Installer and reinstall the boot plugin, then reboot. Rebuild Database needs the new boot plugin.
v1.1.6
- Rebuild Database now works, through the boot plugin. The app is a safe homebrew and can't see
ur0:shell, so it now writes a request file (ur0:tai/rebuild_db_trigger). At the next boot, before the home screen starts,boot_recovery.skprxdeletesur0:shell/db/app.dband the system rebuilds it. The result appears as a notice on the main menu. - Requires the updated boot plugin: reinstall it from Recovery Installer after updating. The screen tells you if the plugin is missing or older.
- A clear warning first: home screen folders are removed and bubbles go back to the default order. Games, apps and saves are not deleted. A second "Are you sure?" follows.
- If a rebuild is already scheduled, you can keep it or cancel it.
- Needs Enso (plugins loading at boot). On h-encore the plugin loads too late, so the delete is skipped and reported, never done while the home screen is using the database.
- Sony Recovery: pressing O on a confirm screen goes straight back to the list. The confusing "SUCCESS / Cancelled" screen is gone. Closing a result screen with O no longer also closes the list.
- Fixed the wide gaps in titles such as "Sony Recovery Rebuild Database". A dash character the screen font can't draw is replaced with
-in about 45 messages.
v1.1.4 · Oct 26, 2026
- Plugins menu: toggles now change the right plugin (section headers shifted the index before)
- Plugin changes save immediately; on failure the toggle is undone and the error code shown
- Saving no longer deletes plugin lines that appear in more than one section (e.g. henkaku.suprx in *main / *NPXS10015 / *NPXS10016)
- Safer config writes: config.txt.bak backup, temp file + read-back check
- Remove Duplicates / Clean Config only match duplicates inside the same section
- Plugin Fix Mode: Reset Config backs up to config.txt.before_reset; protected plugins show their real state
- CPU Speed: removed ARM 500 MHz (system rejects it, 0x802B0000) and BUS 166 MHz; old saved settings converted
- Rebuild Database: shows real error codes, backs up app.db first, removes journal files
- Version 1.1.4
v1.1.3 · Oct 25, 2026
PS Vita Recovery Menu v1.1.3
Install: download VitaRecovery_v1.1.3.vpk below, copy it to your Vita and install it with VitaShell.
Changelog
v1.1.3
- Fix: the update check failed at once with "DNS lookup failed (0x80410116)" because the DNS timeout was passed in the wrong unit. It is now 5 seconds.
v1.1.2
- Update check now uses its own HTTPS client (mbedTLS) instead of the Vita's built-in SSL library, which could not complete a handshake with GitHub on firmware 3.65 (errors 0x80435001, then 0x80431075).
- Certificates are checked against 28 root certificates bundled in the app (
source/ca_roots.h). - Follows GitHub's redirects and handles chunked replies; the download still goes to
ux0:downloads/with progress and SHA-256 check. - Error screen shows a readable reason and, for certificate problems, the issuer that was not trusted.
- If the Vita clock is wrong, the certificate date check is skipped and a note is shown.
- Build now needs mbedTLS: run
vdpm mbedtlsonce. - Known: the "retry without certificate check" option (Triangle) is still there; it skips verification for that attempt only.
v1.1.1
- New: Check for Updates item in the main menu.
- Asks the GitHub Releases API for the newest release of this project and compares its tag with the installed version.
- Shows installed vs latest version, the VPK file name and size.
- Press X to download the VPK to
ux0:downloads/(progress bar, O cancels,.partfile so a failed download leaves nothing broken). - Verifies the SHA-256 when GitHub publishes one; deletes the file on mismatch.
- Nothing is installed automatically: install the VPK yourself with VitaShell.
- Triangle on the error screen retries without the certificate check (off by default).
- Fix: HTTPS now starts the Vita SSL library (
sceSslInit) before the first request. The first test build failed with error 0x80435001. - Build: SceSsl stub is linked when the SDK has it; CMake prints a warning if not.
- Internal: network start-up is shared between the FTP server and the update screen (
net_ensure_init).
v1.1.0
- System Info
- Firmware is read from the os0 partition when possible; if it differs from what the system reports, the reported value is shown in yellow ("system reports X").
- Exploit row says "Enso (permanent CFW)" when Enso is detected; the "no Enso" warning is hidden in that case (also in Diagnostics).
- New "Detection debug" section showing the raw values used for model, motherboard and firmware detection.
- CPU Speed (Advanced)
- L/R triggers now change the selected value (D-pad still works).
- The live column shows the real readback from the hardware; mismatches are yellow.
- Error codes from refused clock changes are shown in red.
- Default bus clock is now the stock 222 MHz (old saved default is migrated).
- Added
build.sh:bash build.sh,bash build.sh clean,bash build.sh bump. - Known issues: Vita Slim 2000 is shown as "1000 (OLED)"; firmware may show 3.73 on Enso 3.65; ARM above 444 MHz and bus 166 MHz are not applied by the system.
v1.0.9
- FTP server: the
ftp://address is green while a client is connected and red when no client is connected.
v1.0.8
- Based on the v1.0.7 source.
- Title bar reads "PS Vita Recovery Menu vX.Y.Z" on the left and "By DrinkingSubset" at the far right, on every screen.
- New version system: one
VERSIONfile drives the title bar and the VPK version;bump_version.shraises it by one step (1.0.9 -> 1.1.0 -> 1.1.1 ...).
Older builds (v1.0.8 to v1.1.2) are listed here for history only and are not available as downloads.
2026-10-24-214746
v1.0.6-9017 · Mar 19, 2026
PS Vita Recovery Menu v1.0.6-pre — Build Update (March 19, 2026)
This update covers a full day of development, testing, and fixes across three test devices (PCH-1000 3G on 3.65 Ensō, PCH-1101 on 3.60/3.74 h-encore2, PCH-2001 Slim on 3.65 SD2Vita).
────────────────────────────────────────
BOOT RECOVERY SYSTEM
────────────────────────────────────────
The two-plugin boot recovery system is now fully automated via the installer. Previously, both plugin files and config entries had to be added manually through VitaShell. The installer now handles the complete lifecycle:
- Install: copies boot_recovery.skprx and boot_trigger.suprx from app0: to the active tai directory, inserts the correct entries under *KERNEL and *main using a two-pass atomic config rewrite, and backs up the config before any modification.
- Uninstall: removes both plugin lines and deletes both files cleanly.
- Status screen: tracks all four components independently (kernel file, *KERNEL entry, user file, *main entry) with three-way color coding — green for fully installed, yellow for partial, red for not installed.
During testing, all three devices showed PARTIAL status after the first installer run because the *KERNEL config entry was missing from a prior manual setup. Running Install filled in the gap correctly on all three devices without touching the already-correct entries.
A regression was identified and resolved: the new VPK overwrote the working plugin binaries with an untested fresh build, causing all three devices to shut down at the unlock swipe. Root cause was that the installer copies from app0:, so whatever is in the VPK is what gets installed. The fix was to recompile the boot plugins from the current source, verify on the 2001 Slim first, then copy to the other two devices. The boot trigger now uses the NPXS10079 LiveArea readiness signal before launching the recovery app, eliminating the previous race condition that caused kernel panics on earlier builds.
────────────────────────────────────────
BUILD SYSTEM
────────────────────────────────────────
The root CMakeLists.txt was rewritten to build all three targets in a single pass:
- boot_plugin/ → boot_recovery.skprx
- boot_trigger_user/ → boot_trigger.suprx
- Main app → VitaRecovery.vpk (with both plugins packaged into app0:)
The key fix was passing -DCMAKE_TOOLCHAIN_FILE through to subproject builds. Without this, the nested cmake invocations picked up the host system GCC instead of the VitaSDK cross-compiler and failed. A single cmake --build build from the project root now produces a complete, self-contained VPK with no manual file copying required at any stage.
────────────────────────────────────────
LIVEAREA ASSETS
────────────────────────────────────────
All four LiveArea assets were designed and integrated for the first time:
- icon0.png (128×128): Black terminal style, green border, VITA in plain text, RECOVERY in an inverted green block matching the reference icon provided.
- bg0.png (840×500): Two-column layout — System Boot/Config on the left, Features on the right. Header pushed down to y=80 to clear the LiveArea button bar. Features column positioned at x=608 so it is fully visible past the Start box. Vertical divider removed per feedback.
- startup.png (280×158): Fully opaque black panel filling the entire gate box. All text pushed into the top 112px so nothing is hidden behind the Start button.
- pic0.png (960×544): Full-screen launch splash with boot sequence log lines.
- template.xml: Standard a1 layout wiring bg0.png and startup.png correctly.
A recurring issue during iteration was that LiveArea assets are cached by the system — reinstalling the VPK over an existing install does not update them. The fix each time was to fully delete the bubble before reinstalling. The CMakeLists.txt was also missing the FILE entries for the livearea subdirectory assets, which is why the default Sony background was showing on first install.
────────────────────────────────────────
CPU SPEED CONTROL
────────────────────────────────────────
The CPU speed screen was completely rebuilt from a simple preset list into a full per-domain clock control screen matching PSVshell's frequency steps exactly:
- ARM CPU: 41 / 83 / 111 / 166 / 222 / 333 / 444 / 500 MHz
- GPU ES4: 41 / 83 / 111 / 166 / 222 MHz
- BUS: 55 / 83 / 111 / 166 / 222 MHz
- XBR: 83 / 111 / 166 MHz
All four domains are controlled independently. Left/Right adjusts the selected domain in real time, Up/Down switches between domains. Square resets to default (ARM 333 / ES4 222 / BUS 166 / XBR 166). Triangle applies PowerSave (all domains at minimum).
Several issues were identified and resolved during testing:
- The > arrow was rendering on top of the frequency text. Root cause: x offset was calculated without accounting for the full width of the value string. Fixed by using a fixed-width format (%3d MHz) and placing > at x+320, which is always 16px past the end of the widest possible value.
- The hint text at the top of the screen was wrapping off the right edge. Fixed by shortening the hint to under 45 characters and splitting across two lines where needed.
- Returning to the CPU screen reset the displayed value to 333 MHz even if 500 MHz had been set. Root cause: cpu_init() was being called on every screen entry, and scePowerGetArmClockFrequency() caps its return value at 444 regardless of the actual clock. The hardware was running at 500 but the getter returned 444, snapping the index back. Fixed by removing cpu_init() from the screen entry path entirely.
- Settings did not persist across app restarts. Fixed by saving all four indices to ux0:data/VitaRecovery/cpu_clocks.cfg on every change, and calling cpu_load_and_apply() at app startup before the menu opens. The live display column now shows the set value rather than the hardware readback, since the readback caps at 444 for ARM — a known Sony firmware limitation.
────────────────────────────────────────
KNOWN ISSUES
────────────────────────────────────────
- PS Vita 2000 (PCH-2001) model detection is still incorrect — System Info shows PS Vita 1000 OLED instead of PS Vita 2000 (Slim LCD). Under investigation.
- This is a pre-release build. Not all features are complete or fully tested across all firmware versions.
────────────────────────────────────────
TESTED ON
────────────────────────────────────────
- PS Vita PCH-1000 (3G) — 3.65 Ensō
- PS Vita PCH-1101 — 3.60 / 3.74 h-encore2
- PS Vita PCH-2001 Slim — 3.65 SD2Vita
Full Changelog: https://github.com/DrinkingSubset/PS-Vita-Recovery-Menu-Project/compare/v1.0.5beta...v1.0.6
