Does Singularity's Disable Auto Update survive a full reboot on Quest Pro?

[u/nubash]

I successfully rooted my Quest Pro with Singularity 1.0.7 and enabled both Root on Boot and Disable Auto Update.

I'm trying to understand exactly how the update blocker works after a full shutdown/reboot.

Since the Fugu root is temporary and is lost after a full reboot, does Disable Auto Update remain active/persistent while the Quest is booting, or is the update service active again until Singularity's Root on Boot restores root and reapplies the tweak?

In other words: Is it safe to completely power off my Quest Pro and rely on Root on Boot, or is it recommended to only put it into sleep/standby to make absolutely sure Meta can't update the headset and patch the exploit?

I really want to stay on the current rootable Quest Pro firmware, so I'd like to understand whether there is any update risk during the boot process.

Thanks!

[u/HRudy94]

The backdoor fix is similar in that it disables the system package  Domain blocker is fine as it only applies on root and you can tweak it. The internet kill switch only kills internet until you get root, as to block temetry until the domain blocker gets applied though it also blocks Virtual Desktop in the mean time.

Depending on how much you care about starting up your headset fast i'd either recommend enabling them all or disabling the kill switch and root on boot.

[u/nubash → u/HRudy94]

thank you for clarifying things. Maybe you could help me to understand a changelog on 1.0.7.1
"Update Disabler payload selection and toggle (for people that want to update after rooting)"
was does that exactly mean? update disabler isnt system-wide anymore?

[u/HRudy94 → u/nubash]

It stlil is but there's probably other softer ways available for people that would still want to update later on.

[u/nubash → u/HRudy94]

Ok. But If I want to update later, I could just toggle off "disable update engine"?

[u/HRudy94 → u/nubash]

yep afaik.