Quest 2 stuck in pairing loop, couldn’t pair with headset after factory reset
Hello Meta Community, I am reporting a persistent Meta Quest 2 pairing issue that does not appear to be caused by user error. My Quest 2 is stuck in the initial setup pairing flow and the Meta Quest or Meta Horizon app consistently shows the message “Couldn’t pair with your headset”. This issue persists even after factory reset and across multiple Android devices including Samsung Galaxy A15 5G, Samsung Galaxy A54, and a OnePlus device. I have performed factory reset using the boot menu, verified the headset shows a 6 digit pairing code, updated the Meta Quest app, cleared app cache and data, granted all permissions including Bluetooth and Location, used manual pairing with the code instead of auto detect, ensured the phone and headset were on the same network using a mobile hotspot, and disabled VPN and private DNS. The app detects the headset and sometimes shows “Headset connecting” but pairing never completes and Add New Device always fails. The same behavior occurs across phones and networks, suggesting a backend or account pairing deadlock rather than hardware or user error. I am posting to ask whether this is a known issue and if Meta support can reset or clear pairing state on the account or device. Thank you.
New Quest 3 locked on software update, impossible to fix.
Hi guys, I bought my first Quest 3 today. When I turned it on, it started a software update but it gets stuck there — the device keeps turning on and off without completing the update, and I can’t get past that screen. I haven’t even set up my Meta Horizon account yet, and since I didn’t purchase my Quest 3 through the official Meta store, when I try to enter my device’s serial number on the website it gives me an error. I tried doing the sideload update (the only fix I found on the internet) by holding the volume down and power buttons on the Quest 3. But when I select my device in the browser, I get a message saying: “your device is not supported, please try reconnecting your devices.” Weird cause both my PC and Chrome are detecting it as Quest 3. I also tried disabling adblock, deleting caché and cookies, incognito mode, other browsers, other PCs, other cables, connecting it on different times, etc. There is not a single thing I haven't tried. (Every single one of these attempts were done while having 50% battery. There’s nothing else I can do, literally — I’ve already tried factory reset several times as well. Do I need to return my device? I'm submitting this post so support can help me. I'm quite desperate, I don't see my issue anywhere on google and I spoke to support via Whatsapp and everything they told me to try, I already had.
Can I setup my Meta quest without needing a phone?
I bought my quest and i see it needs a mobile, a google account, wifi and tons of permisions for the mobile. I just want to play it without needing all that. When i bought the product no where they were saying all those requisites, neither was on the box.
Quest 1 Headset Stuck in Setup Loop. Serial Number Not Recognized.
Hello everyone! I've encountered a very strange and frustrating issue with my Meta Quest 1 headset and I'm hoping someone in the community has faced something similar and can help. My headset is stuck in a setup loop after I performed a factory reset. The screen constantly shows a message to "Continue setup in the Meta Quest mobile app," and I can't proceed past it. I have already tried all the standard solutions I could find: Factory Reset: I performed this both through the phone app and the Fastboot menu, but nothing changed. App Data Clearing: I cleared all the data for the Meta Quest app on my phone and tried to connect again. Manual Firmware Update: I successfully sideloaded both the latest and an older firmware version onto the headset. The headset updated, but the problem remains. ADB Commands: After the firmware update, I tried to run a command to complete the setup, but it failed because the headset was not detected by ADB. Here's what puzzles me the most: Serial Number Not Recognized: When I enter my headset's serial number on the Meta website for verification, I get a message that the device could not be found. My account page also shows no registered devices. ADB Issue: Before the factory reset, my headset connected to my PC without issues and showed the "Allow USB debugging" window. Now, it doesn't. It seems that the problem isn't with the headset or the firmware itself, but with its connection to Meta's databases. I have exhausted all the solutions I know. Also, the headset hasn't been launched for a year Has anyone else encountered a similar issue where the device's serial number is not recognized by the system? Are there any other options besides contacting official support? Thanks for any help!
Unable to log into Meta Developer Hub App and finish setting up
I signed up my Meta account to be a developer account, created my organization, turned on debug mode, and downloaded the Meta Developer Hub App to finish setting up. When the app asks me to login through a browser, it takes me to the typical Meta login that asks to "Continue as Name", which I press, but then nothing in the app progresses, it keeps the "Continue in Browser" screen up, and nothing happens. I noticed that every time I press the "Continue as Name" button, in task manager a new instance of the app shows up, even though I do not see any second screen. I do see an invisible square show up and disappear almost instantly after pressing the button, and if I am looking at the hub app while pressing the continue button, it briefly has a loading screen, but never changes. Occasionally if I spam the "Continue as Name" button, it will say that my email or password are incorrect, even though they are and I can login literally everywhere else easily. I have been unable to find a solution to this problem, so I am hoping someone on here can help me out! Thanks!Prompt Player Eye Tracking Setup via ADB or API call?
My team is performing a study utilizing the Quest Pro eye tracking feature. Many of our participants are new to VR and we don't want to make them traverse through many menus outside of our experience. Is there a way we can start the eye tracking calibration pop-up prior to starting our demo? It is trivial for us to load our game via an ADB call. Is there a similar method for calling the eye tracking calibrator? Can we otherwise call the eye tracking calibrator via an in-game API call? Are there any options at all to solve this problem aside from manually guiding each of our participants through to start the calibration themselves?
