Installation and Setup

Installation & Setup

You need three things: hsr_renderer.exe, adb, and the old home file. The annoying parts (signing, choosing the right APK, installing) are automatic.

1. ADB — just three files

The converter installs to the headset with Google's adb. You do not need the full Android SDK / "platform-tools" install — just three files, placed next to hsr_renderer.exe:

hsr_renderer.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll

The tool searches for adb in this order:

1. $HSR_ADB (if you set it to an adb path)
2. beside the exe (the three files above, or a platform-tools\ folder next to the exe)
3. C:\Android\platform-tools\adb.exe
4. adb on your PATH

So dropping those three files beside the exe is enough — no install required.

Get the three files from Google's SDK Platform-Tools zip (copy just those three out of it), or from any existing platform-tools folder. On Linux/macOS only the single adb binary is needed.

2. Developer Mode on the headset

1. In the Meta Quest phone app → your headset → Developer Mode → On.
2. Connect the headset over USB.
3. The first time, the headset shows "Allow USB debugging" — accept it (check "always allow").
4. Verify on the PC: adb devices should list your headset.

Wi-Fi instead of USB: enable "Wireless debugging" on the headset, then in the Cook tab type the headset IP in Wi-Fi IP and press Connect before cooking.

3. Signing toolchain (automatic)

APKs must be signed or the Quest rejects them (INSTALL_PARSE_FAILED_NO_CERTIFICATES). The tool signs automatically. Build-tools are found from an installed Android SDK, or — on a clean PC with no SDK and no Java — auto-downloaded beside the exe on first use (needs curl + a network connection).

Pre-fetch the toolchain anytime:

hsr_renderer.exe --fetch-tools

Next: Cooking a Home.