Headset permanently broken after software update — tracking failure, case being closed with no fix
Hi everyone, I’m hoping someone here can help. About a month ago, my Meta headset became completely unusable immediately following a software update. Since then, it displays only a black screen. The device powers on and I still hear audio, but the display and tracking system completely fail. Support has now confirmed that the tracking system itself is the issue and is not fixable through normal troubleshooting. The headset worked perfectly before the update. I’ve spent weeks working with support, completing every troubleshooting step they asked for. Today I was told they are closing my case without repair, replacement, or refund despite acknowledging the failure happened after the update and that the tracking system is the cause. This is extremely frustrating. A manufacturer software update should not permanently disable the hardware, and closing the case without resolution feels wrong. Has anyone else experienced this after an update? If so, how did you get it resolved? Any advice on escalation paths within Meta would be greatly appreciated. I've truly never had such disappointing treatment and run around from customer service. I just keep getting put off that a team is reviewing the case but no real resolution and then today they are looking to close the case. It's my sons quest 3s and he takes immaculate care of it. His twin is in the hospital a lot and this quest is a life line for him and his friends when things get hard. This ruined a lot of the Christmas gifts we got him as they were related to his quest and he's been without it for over a month. Thank you31Views1like2CommentsStuck on Quest 2 Firmware 50.x — Can’t Update, Can’t Pair, Completely Unusable
Hi everyone, I’m really stressed and discouraged by what’s happening with my Quest 2 right now, and I’m hoping someone here can help me. I don’t use my headset very often since my kids are still too young for VR. Today I wanted to use it again, but it was still on version 50.x, and several things no longer worked — including casting. In the settings, it said there were no updates available. So I followed the official procedure here: https://www.meta.com/fr-ca/help/quest/software_update/ …but I always get the error “Device not supported” when trying to manually update it. I then tried to contact Meta Support, but my headset does not appear in my devices list: https://www.meta.com/my/devices/ Even when I enter the serial number manually, the site says it’s invalid. Because of that, I can’t open a support ticket or talk to anyone at Meta. I tried everything I could think of: another computer, another iPad, anothere Wifi, reinstalling Meta Horizon on iOS, etc. Casting still doesn’t work, updates still don’t work — nothing works. In panic, I made the worst mistake possible: I factory reset my Quest 2. Now I’ve lost everything, and it got even worse: the headset can’t pair with the Meta Horizon app anymore. It’s completely unusable, and honestly I’m freaking out. I’m almost sure this is all caused by being stuck on the old 50.x firmware, but I can’t find any way to force an update or get the headset back online. If anyone has gone through this, knows a workaround, or knows how to manually update a Quest 2 in this situation, please — I’d really appreciate your help. Thank you so much.Solved186Views0likes6CommentsNew 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.1.8KViews1like10CommentsRequest: Add Arabic Language & Keyboard Support for Meta Quest.
Hello Meta Team, I’m writing to highlight the urgent need for Arabic language support (including an Arabic keyboard) on Meta Quest devices. The Arabic-speaking market is one of the largest in the world, with over 420 million native speakers across 22 countries in the Middle East and North Africa. This region has one of the highest internet and mobile adoption rates, and VR adoption is growing rapidly. According to market research, the MENA gaming market is projected to exceed 6 billion USD by 2027, with VR playing a major role. Many potential users in this region are excited to explore Meta Quest, but the lack of Arabic support creates a barrier to entry and reduces the overall experience. Adding Arabic language support will: Improve accessibility for millions of users. Strengthen Meta’s presence in a fast-growing market. Boost sales and brand loyalty in the region. We sincerely hope you prioritize Arabic language support in upcoming updates, as it would be a game-changer for millions of potential customers. If you also want Arabic support, please upvote this post so Meta can see the demand.136Views3likes1CommentStarting at Rift 1 it’s silly that Quest in 2025 still lack basic user controls for core functions
People have been asking Meta for years to add a simple toggle to disable the proximity sensor directly on the headset. Instead, the only way is through ADB or SideQuest, which makes zero sense for a mainstream device. A native setting should exist by now. Meta also removed the option to disable the “double tap to glance” overlay. It’s now permanently on with no way to turn it off. In fast movement or dance sessions, both problems annoy constantly. Quick head movement or leaning forward trips the proximity sensor, and accidental taps or scratches activate room view. It breaks immersion every time. It honestly feels like the product designers don’t actually use the headset actively. Having to open a developer account just to disable Guardian proves it. If there are legal concerns, add warnings. Don’t take away core user control! Small note while on on the train of annoying issues about Pro: -thanks for fixing the odd rendering issue on Pro headset where a diagonal line was breaking the image on the headset after updating to v80 and up its gone BUT when will your microphones ever be flawless? It's not as bad as the Rift S, but occasional mic dying turning robotic or giving a high pitch scream still appears once every few months or weeks does not happen on my Quest 3, Rift cv1, but we all know the famous Rift s mic going robot mode! (all headsets now on newest OS at the time of writing this)15Views0likes0CommentsQuest stuck without menu options
I just updated my old quest; it's an original, not quest 2 and it had been sitting in a cabinet unused for a while so I clicked into system & update its software... I now am stuck without a menu bar & unable to do anything but look around at the dome home screen. Restarting did not resolve the issue. Can anyone help me out here?Solved28KViews0likes14CommentsSoftware Update Needed
I have the post powerful laptop Dell has to offer. Dell Precision 7780 Workstation Processor 13th Gen Intel(R) Core(TM) i9-13950HX (2.20 GHz; 5.5Ghz Turbo) Installed RAM 128 GB (128 GB usable) System type: 64-bit operating system, x64-based processor Graphics: NVIDIA RTX 5000 ADA Generation Laptop GPU 16GB RAM I researched extensively to find the best headsets for use while traveling, as I cannot bring my monitors with me. Used ChatGPT Pro5 with my specs and it suggested Quest 3. After troubleshooting with the technical department, they said it is not compatible as Meta does not recognize my GPU, even though it is exceedingly capable. A simple update could fix the issue, so here I am posting as I prepare my return and researching other competitors that don't have this issue. Please let me know if META is able to update its software to recognize a far more capable GPU in your software code, so I can utilize the device and keep it.21Views0likes0CommentsQuest 3 battery drainage when not in use.
If quest 3 staff read this please read it properly and not give me an automated reply I work in IT I don't want automated or generic support I'm not an idiot. I’ve been dealing with a persistent and widespread issue affecting the Meta Quest 3 headset and controllers related to severe battery drain, both during use and while powered off. For several months, I’ve noticed that even when the headset is fully charged and then turned off properly, the battery depletes at an unusually high rate. After leaving the headset unused for approximately one month, the charge drops from 100% to around 5%. This is extremely frustrating, especially since my previous Quest 2 headset could hold a full charge for months without any noticeable drain, and its controllers maintained more than 60% charge even after extended periods of inactivity. I have thoroughly reviewed all available settings to disable features that might keep the headset active in the background or prevent it from entering sleep mode. I’ve also turned off auto-updates and background services, yet the issue persists. Despite these precautions, the headset still performs auto-updates and consumes power unnecessarily when it should remain idle. To rule out individual hardware faults, I tested two separate Quest 3 headsets in my household both exhibit the same problem. Additionally, several friends and family members who own the Quest 3 report identical behaviour, confirming this is not an isolated defect but a broader design or firmware issue. I’ve kept the firmware updated in hopes that Meta would address the problem, but there has been no improvement. Each update seems to introduce additional complications while failing to resolve the ongoing battery drain I hate the fact the headset will auto update when I have that turned off. At this point, it’s clear that the Quest 3 suffers from a serious power management flaw that needs urgent attention from Meta’s engineering and software teams. The level of battery depletion while the device is off is unacceptable for a headset and significantly undermines its usability. It feels like the setting is a lie when you turn off the device its like turning off is a fake sleep mode where you device is in fact still on and updating even if you disable.99Views0likes2CommentsBoot-loop and Endless Updating
I will tell the story I got on one day, and my headset crashed, so I powered it off It went through the update with the white meta logo with the progress bar THEN it went to a gray screen, then it bootlooped and reinstalled the update, then went to a gray screen and repeat's this. and yes I have factory resetted, and tried to update the software on a computer, and nothing works.33Views0likes1CommentBoot looping in boot menu
So I had to factory reset my quest 2 and now after fixing it it has got stuck in the boot menu and doesn't boot past that menu, it always stays on and the only way to turn it off is threw the power off button in the menu, and if its plugged in it just turns it self back on. I can't even use software update tool to enter recovery mode or put the headset into sideload update cause it just boots back into USB update mode. Not even holding the power button to turn off or reboot/restart and power off will work cus it just turns back on. Please help!66Views0likes1Comment