Quest 1 - Guardian fix on the accountless build
How to get Meta's own draw-your-boundary Guardian working again on a modded, accountless Quest 1. Written so the fix can be redone from scratch if the headset is wiped or the flag is lost.
Full build reference: `<workspace>\reference.md` (section "Guardian: WORKING").
The problem
- Quest 1 (`monterey`, 64 GB), firmware v50 build `49845030443200410`, rooted (Magisk), no Meta account, first-time setup bypassed.
- Selecting Guardian in the headset menu did nothing. No boundary at all, which is a safety hazard.
Root cause
The shell (`com.oculus.vrshell`) refuses to run Guardian while its preference `first_time_nux_allow_guardian` is `false`. Meta's first-time setup normally switches it on. The accountless bypass skipped first-time setup, so it stayed `false`.
The Guardian service itself was fine. It sat in "setup active", asking the shell every 10 seconds, and the shell kept answering no.
The fix
Needs: adb connected to the headset, root through `su` (`adb root` does not work on this build).
Wear the headset first (in Steam Link or Quest home). Then run on the PC:
```
adb shell su -c "oculuspreferences --setc first_time_nux_allow_guardian true"
adb shell su -c "am broadcast -a com.oculus.vrshell.intent.action.GUARDIAN -p com.oculus.vrshell --es intent_data systemux://guardian/roomscale-setup --es uri '' --es intent_pkg com.valvesoftware.steamlinkvr --ei guardian_action_type 0 --es intent_cmd ''"
```
- The first command sets the flag. One time only; it persists.
- The second command asks the shell to start room-scale setup. The normal Guardian screen appears: confirm the floor, draw the boundary, confirm.
- Steam Link drops to the background during setup and comes back by itself.
Double-click version of both commands: `<workspace>\quest-guardian-setup.bat`
Redrawing later (new room, furniture moved)
Wear the headset and run the second command again, or run the `.bat`.
For a stationary (stand-in-one-spot) boundary, replace `roomscale-setup` with `stationary-setup`. Not tested yet.
Connecting adb
- USB: plug in, then `adb devices`.
- Wi-Fi: `adb connect <headset-ip>:5555`. The IP is assigned by DHCP and can change between sessions. Find it with `arp -a` and look for the headset's MAC address (`<headset-mac>`, shown in the headset's Wi-Fi settings or your router's client list).
How to check it worked
Read the flags:
```
adb shell su -c "oculuspreferences --getc first_time_nux_allow_guardian"
adb shell su -c "oculuspreferences --getc first_time_nux_guardian_setup_complete"
```
Both should say `true` after a successful setup. The shell sets the second one by itself.
Ask Guardian for its mode (optional, needs a debug gate):
```
adb shell su -c "setprop persist.oculus.guardian_json_cmds_user_build 1"
adb shell su -c "am broadcast -a com.oculus.vrguardianservice.JsonCmdBroadcast --es cmd '{\"statusOutput\":true}'"
adb shell "logcat -d | grep statusOutput:"
```
- `"mode":"room_scale"` or `"stationary"` = a boundary exists.
- `"mode":"invalid"` = no boundary.
- The gate value must be `1`. With `true` the command is logged but ignored.
In SteamVR, the play area should no longer be the 1.20 x 1.20 m default that Steam Link sends when the headset has no Guardian.
What was verified (2026-11-15)
- Setup screen appeared, boundary drawn, boundary works in the headset.
- Guardian reported `room_scale`, valid.
- Steam Link passed the boundary to SteamVR (play area matched the drawn boundary instead of the 1.20 m default).
- Accountless state unchanged: `device_provisioned=1`, `user_setup_complete=1`, `com.oculus.firsttimenux` still disabled, `first_time_nux_complete` left `false` on purpose.
Not verified yet
- Whether the boundary and the flag survive a reboot.
- Whether Guardian remembers each room, or needs a redraw every time the room changes.
- The `stationary-setup` link.
Undo
```
adb shell su -c "oculuspreferences --setc first_time_nux_allow_guardian false"
adb shell su -c "pm clear com.oculus.guardian"
adb shell su -c "setprop persist.oculus.guardian_json_cmds_user_build ''"
```
The second line wipes the stored boundary.
Things that did not work (do not repeat)
- SteamVR Room Setup. Under Steam Link it only recentres. The headset supplies the boundary, and with no Guardian it sends a 1.2 m default box whose walls SteamVR does not draw.
- Guardian's `force_roomscale` debug command. It created a boundary, which vanished about 90 seconds later.
- The setup link without the flag. The shell logs "Fast-forwarding to roomscale setup" and then does nothing.
- OVR Advanced Settings proximity warnings. They read the boundary once at start and go stale after every recentre.
Fallback if Guardian is lost and cannot be restored
A PC-side box inside SteamVR only: `python quest-chaperone.py watch 2.5 2.5` (same folder as `reference.md`), run after Steam Link connects. It draws a floor outline but gives no warning when crossed. Stop it once the real Guardian works, because it overrides the headset's boundary in SteamVR.
How this was found
- Pulled `Guardian.apk` and `VrShell.apk` off the headset and read their strings and disassembled code on the PC.
- The shell's library lists the preference names (`first_time_nux_allow_guardian` and friends) and the setup links (`systemux://guardian/...`).
- Guardian's code shows the broadcast it uses to talk to the shell, including the field name `intent_data`.
- Log line that marks the blocked state: `OverlayGuardianFlow::ParseShellUri IsRequestingActivation() = 0`.
- Log lines that mark success: `IsRequestingActivation() = 1`, then `OverlayGuardianFlow Activate`.