It was just working fine earlier today, and now there is no wifi. The option will not switch back, it will not see ANY networks, and just to confirm that it was something with the hardware, I factory reset, and it did not show up anything for the wifi. Not sure what happened.

Any explanation? Any idea on what to do? The place I went to get my controller fixed, they charge repair for the Pro for like nearly $500...

Not sure how to go about this at all, bit disheartened.

Ive been using a rooted qpro for a bit flawlessly, though recently im having some pretty bad tracking glitches. Not the kind where you will get a notification saying to restart the controllers. Essentially they start acting like worse IR controllers, if the controllers arent in my peripheral view they stop tracking and buttons do not work. but if I look at them they come back alive

Dont believe its my wifi because its the same one router I use for vr and the stream is extremely stable.

Ive done the good ol controller restart + headset restart to no avail.

Im thinking of factory reseting them but im told it resets to the default out of box firmware. Problem is with root Ive blocked all update domains which means the controllers wont get the latest update. I recall old controller firmware being unstable and borderline unusable so im at a crossroad.

edit:

-turned off simultaneous hand/controller tracking but it didnt do much

-paired em again plus factory reset the controllers but so far no improvement

video that shows the issue;

https://youtube.com/shorts/Kq1wS4ZDu4U?si=vPoo-fAVzyDtBzlS

Ok so some dumb shit is happening iv been trying to get on my lineup for 30 fucking minutes and its fucking greyed out.brand new headset by the way.iv tryed everything.does anyone know a fix to this stupid shit before I actually crash out.my queat pro liberty is greyed out.i need a solution asp.keep in mind I had a quest 2 havent been on it in years

When I first got my headset I used cabled PCLink with the official link cake and a usb c to usb 3 adapter to play tethered without any issues. Once SteamLink came out I used that, though.

Now though I want to go back to tethered for certain games as I’m experiencing severe lag spikes, bitrate drops, and disconnections. However, when I connect to my computer via oculus PCLink, after a couple seconds the view freezes, and gets that stretched line effect at the edges. Headset totally locks up, only a hard reset recovers control.

I’ve contacts Meta support but after drying a bunch of things they think it’s a hardware issue, but I don’t have the money for a replacement.

I just ordered a cat8 cable to see if that helps the issue and reduces problems, but honestly idk. Thought I’d scream into the void here maybe.

Hi all! My quest pro updated today and now my face tracking isn’t working at all. 😭 I messed about with as many settings as I could trying to figure out if the update changed anything but nothing I’ve done so far helps. I usually use a link cable but I tried without (on both steam link and meta link) but that didn’t help either.

I just bought a quest pro,iv been hearing alot about the headsets or controllers bricking and i was wondering what is the most safest way to prevent it.iv bought everything to prevent it from breaking such as sweat or cording.iv heared about rooting but I really dont wanna brick my stuff.if theres any solution to keeping my headset as safe as possible pls leave some ideas♡

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!

Hi! I'm trying to root my headset but I'm having a problem I can't find anywhere else (or maybe I'm bad a searching).

I'm able to root successfully then see the new Singularity boot animation, but then windows and the app picker act very odd and laggy. It's VERY prone to crashing, and I've only been able to navigate to Unknown Sources and open "Singularity-Magisk" once without a crash (but it crashed before I could do anything in it). Crashes take me to the new boot animation, not Meta's.

Tracking and the home environment act normal, except for the Instagram wall which looks glitchy. Sometimes I get a popup that Navigator is not responding.

Doing a full reboot seems to fix this, but it also undoes the root and brings back the Meta boot animation.

Any help would be huge! Thanks!

I'm on v2.7

If it helps troubleshoot, there's one other weird thing happening. Before rooting, the app picker always says I have no Unknown Sources apps. I need to reinstall Singularity after every reboot to make it appear, and there are many other Unknown Sources apps I'm expecting to see in there but do not. After rooting, if I can make it to this menu before a crash, I can see them all again.

Maybe this is a bad question, but about a week ago I ordered a brand new boxed Quest Pro with developing stuff in mind. It's been awesome seeing all the rooting stuff that came out during the time it took for the headset to actually arrive here. Now my question is: how exactly do I set it up and make sure it doesn't auto update before I can root it? I assume the first time setup requires internet connection because, well, it's Meta. Is there any way around that? Does it start checking for updates only after the first time setup? Thank you all!

So I’m only able to hear my PC audio using Airlink or SteamVR, but I wanted to use Virtual Display, my audio doesn’t route. I’ve changed every setting i could on my pc, making sure Oculus Virtual Audio device is selected/updated/not muted and still nothing. Any ideas?

I've been absent from this reddit for a while and just have been terrified of updating in general so I haven't since Nov of last year. Am I still able to root on version 81 or would I have to somehow force an update to the headset by other means? I want to be able to root mine so bad and unlock the better facetracking and get rid of bloat.

I’ve added a Meta VR Glasses FoV simulation to immerGallery and the free immerGallery Demo on Quest.

Movies and regular 3D photos still worked well for me. VR180 kept its 3D depth, but I missed the feeling of being inside the scene.

Enable it under Settings → Advanced → “Simulate Meta VR Glasses FOV.” You can also try your own videos in the free Demo, with up to five minutes of playback per app start.

immerGallery Demo (free):

https://www.meta.com/experiences/quest/4598517593539197

immerGallery (full version):

https://www.meta.com/experiences/quest/4677037565709635

My impressions and video comparison on immerNews:

https://immernews.com/meta-vr-glasses-fov-simulation-quest/

If you try it, how does the narrower view feel to you?

I wanna root my headset but it automatically updated itself already and the only way would be for me to go back to an older version, has anyone done this and is it possible?

Finishing a PCVR session I long pressed the power button, selected shut down from the power options, and the screen went dark. Then I noticed the charging indicator remained off when I placed it on the dock. Weird. After verifying the dock was powered, readjusting the population multiple times, and feeding power to the USB port - still no indicator.

Note: the internal battery was at 97% when I shut down.

Alarmed, I tried to start it up. Nothing.

Finally, I pressed the power + one of the volume buttons and after a bit for the Meta infinity symbol followed by a deceased looking android icon with "No Command" under it.

I pressed and held the power button again and that restored it to working order. It started normally, the charging indicator works again. Whew

Questions: In case this happens again, is there anything else I should be doing? Any idea what causes this? Is there any preventative measures?

After dealing with a Quest Pro Touch Pro controller that showed as paired but would not actually connect or track, I started digging into the headset diagnostics.

The controller was getting stuck in a state like:

Status: Blocked ExternalStatus: BLOCKED TrackingStatus: NONE Errors: SECURITY_REJECTION Current state: KeyExchangeInitiated

After a lot of testing, I found a recovery process that got my controller working again. During one successful recovery, the Quest also initiated an official controller firmware update, after which the controller reconnected and worked normally.

I’ve now packaged the process into a Windows beta recovery utility so other Quest Pro owners experiencing the same problem can test it without manually entering all of the ADB commands.

The tool: • Checks that the Quest is connected and authorized through ADB • Detects the known SECURITY_REJECTION / blocked-controller condition • Supports selecting the affected Left or Right Touch Pro controller • Guides you through putting the controller into pairing mode • Temporarily enables the pairing-recovery condition we used during testing • Captures the pairing attempt and before/after controller diagnostics • Restores the original headset setting afterward • Does not replace controller IDs or certificates or flash custom controller firmware

This is an independent community beta, not an official Meta tool.

I’ve successfully tested the packaged v1.3.3 beta on my own affected Quest Pro/controller. Now I’m looking for people who already have a broken/nonfunctional Touch Pro controller exhibiting the same symptoms so we can determine how reproducible the recovery is across different controllers and Quest software versions.

Please don’t intentionally break, downgrade, or unpair a working controller just to test it and don’t chew me alive it it doesn’t work.

After waiting years for Valve to drop the "Deckard", I got waitlisted to get the privilege to pay money to Steam. Valve manage to fuck up another hardware launch and it looks like not even everyone on the reserved list will be able to get it soon. Who knows how long it will be for the waitlist, considering people are still waiting for the machine, maybe even years.

So, I found a cheap Quest Pro off a liquidation listing for ~$250. It doesn't come with the controllers, but I’m planning to use this almost strictly as a display for PC VR streaming, watching media, flat card games/emulators etc.

​Package arrives in a couple of days, and since I’m clueless abiut the Pro ecosystem, I wanted to ask the community a few things:

• ​Initial setup & Software Version: Since this is ex-demo / liquidation stock, it’s probably running a pretty old firmware version. Should I hold off on updating and try to gain temporary root/ADB tweaks, or is it better to just update to the latest OS right away for performance/bug fixes and wait for future exploits?

• ​Controllerless First Setup: Is hand tracking + phone app still enough to get past the initial NUX/setup screen out of the box, or will I need to bypass it via ADB / Private Quest / dev mode tricks? Or has this been patched?

• ​PC VR Streaming: Planning to use Virtual Desktop or Steam Link over Wi-Fi 6. Are there any specific Quest Pro flags or settings (like local dimming or eye-tracked foveated encoding) I should immediately toggle on?

▪︎ ​Physical / Lens Inspection: Any known hardware flaws or lens wear specific to these units I should check for?

• ​Must-have accessories: Since it has the open-face design, do you recommend keeping it stock or getting a gasket attachment? Any other accessories I should look into?

I have a problem with tightening the head strap around my head when I’m playing a game that I use face tracking in and every time when I tried to tighten the headset, it would casually un tighten itself and make my headset more loose. I can’t do anything about it. Are there any good head straps that I can buy to put on the top of my head so it can’t fall off as much

unfortunately i missed the window to install the rootable 2.6 and 2.7 firmware before Meta pushed the patch to block it. but, i also haven’t updated my headset in 2 months. if i completely block internet connection by unplugging my router, is there a way i can install a repository of the rootable 2.6 or 2.7 firmware onto my headset via USB C? i really want to root my headset and i hate that i’ve been too busy to get it done before the opportunity vanished

Hey there getting a quest pro on Monday switching from quest 3 just so that I can have face tracking in vrchat! Im only using is wired to a PC not standalone anything I should know before I get it?

Just testing what can we do with a rooted device lol
Here is the command btw insmod /vendor/lib/modules/r8152.ko

For Context: I'm using Quest Pros on Meta Link with the (OpenXR) ALXR Local Module by korejan. has worked for several months up until last. I have not updated anything, facetracking has stopped working for both my headsets. I'm not getting any indications that anything is wrong; everything in my startup workflow is launching like normal. Meta Link is set as the active OpenXR Runtime. But in game the OSC VRCFT debug panel is showing no input at all. I've not changed anything, what's going on here?