Home

V79 Quest Home Editor & Porter — Wiki

Turn an old (V79-era) Meta Quest Home into an APK you can install on a current Quest 2 / 3 / Pro. This tool loads the old home, lets you (optionally) edit it, then cooks it into a modern HSL environment APK, signs it, and installs it for you.

⚠️ Work in progress — but a lot now works. Cooking produces installable, signed APKs, and static geometry, textures, baked lightmaps, most materials, node animations (spin / sway / UV-scroll / flipbook) and skeletal HZANIM skinned meshes (clouds / dragons / creatures — large ones auto-split so they load + animate) now port. Still rough: some PBR material variants, certain vistas, and a few effects, plus Quest 2 can miss some content. See the repo README.

Quick start (the happy path)

1. Put adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll next to hsr_renderer.exe → Installation & Setup.
2. Plug the Quest in over USB and accept the "Allow USB debugging" prompt in the headset.
3. Drag the old home (env.apk / .gltf.ovrscene / .opa) onto hsr_renderer.exe.
4. Open the Cook tab, leave the defaults, press COOK + SIGN + INSTALL.
5. Put the headset on — your env loads in place of Haven 2025 (the tool relaunched the shell). An unrooted Quest can't switch to a custom environment, so the spoof becomes Haven 2025 instead.

That's it — the tool cooks, signs, picks the correct APK for your device, and installs it.

Pages

• Installation & Setup — adb (3 files), Developer Mode, signing toolchain.
• Cooking a Home — the Cook tab, every option explained.
• The Two APKs — spoofed (no-root) vs own-package (rooted), and why the spoof exists.
• Restoring Haven 2025 — the automatic backup and how to put the stock home back.
• Troubleshooting — foggy default home, black void, signing/adb errors.

What you need

Need	Why
hsr_renderer.exe	The editor + cooker (one binary).
adb (3 files beside the exe)	Installs the cooked APK to the headset.
A Quest in Developer Mode	To allow USB/Wi-Fi installs.
An old home file	.apk / .gltf.ovrscene / .opa to port.