• Make sure ShadowMount+ is running: it shows a notification when it starts.
• Check the folder: it must be called exactly homebrew and sit at the top level of the drive, not inside another folder.
• Check the file still ends in .exfat. Some PCs hide extensions: a file renamed to Overdrive.exfat.zip or unzipped into a folder won't be found.
• Give it a minute: ShadowMount+ waits until the file has finished copying before it installs it.

The new version is installed but the console still has the old one loaded. Restart the console and open Overdrive again; the app tells you this itself if it happens twice in a row.

The update is downloaded next to the installed app, so the drive holding Overdrive needs about 600 MB free. Free some space on that drive and press Retry. Nothing has been changed yet when this happens.

Install it by hand: download Overdrive.exfat from the latest release, close Overdrive, and copy the new file over the old one in the homebrew folder.

Delete Overdrive.exfat from the homebrew folder first, then delete its icon from the home screen. In the other order ShadowMount+ finds the file again and puts the icon back.

Overdrive is a React app running on ps5-react, and its whole JavaScript bundle sits in plain text inside eboot.bin. A bundler merges every module into one scope, so imports between modules turn into bare names; since each top-level name stays unique, the module that declares a name can be worked out again. That split the bundle back into its 137 original modules with their real import/export lines, checked against the original bundle until every import edge matched.

What a bundler throws away could not come back: most comments, the JSX syntax (it reads as jsx(View, {…}) calls), and const/let (now var). None of that changes how the app behaves.

Builds run on ubuntu-24.04 with clang 18, only from Run workflow: a push builds nothing. Each run puts Overdrive.exfat and update.zip in a draft release named after app/version.js, which only maintainers can see.

The same build locally, on any Linux with the packages the workflow installs (clang-18, llvm-18, cmake, ninja-build, nodejs, npm, zlib1g-dev, build-essential, pkg-config, unzip, curl, exfatprogs, and Pillow from ps5-react/requirements.txt):

cd ps5-react
python3 tools/build_ps5.py --app-dir ../app --llvm /usr/bin
sudo ../packaging/make-exfat.sh dist/PPSA99058 ../Overdrive.exfat

The build downloads its pinned dependencies into ps5-react/.deps and writes the app folder, a .zip and a .receipt.json into ps5-react/dist. It verifies the result itself (tools/verify.py), so a green build means the payload structure and signatures check out. --llvm /usr/bin points it at the system clang; upstream defaults to the Homebrew LLVM path because macOS is its supported development environment.

The image is a plain exFAT volume whose root is the app folder, with 64 KiB clusters and the label OVERDRIVE. To release a new version, raise the version in app/version.js and app/app.json, run the workflow, test the draft's image on a console, then publish the draft: that creates its tag, and installed apps offer exactly the tested files on their next start.

Two fixes in the vendored framework, both in the build tooling and both reported by a Linux build:

• ps5-react/tools/common.py read the git apply --summary line with a fixed space count, which glued the file mode onto the path (100644 <path>) and made every fresh dependency checkout fail on the first patch that creates a file. It now splits on whitespace.
• ps5-react/tools/build_ps5.py opened the pinned LLVM package's data.tar.zst with tarfile, which reads zstd only from Python 3.14 while the documented minimum is 3.12. It now falls back to the zstd command.

Nothing else in the framework is changed.