Other Troubleshooting

Hey there,So, I bought my first Meta Quest 3 almost a year and a half ago... and after a few months, it died. Black Screen, no connectivity, factory reset does nothing... and was told to send it in for RMA replacement.Then that one died.Then the next one...... and the one after that...... then one time it died after less than two weeks...... and again today.I've honestly lost track. I know it's been at least 5 headsets have died on me. Every time I've asked for what the cause might be... but no one can tell me.I'm told I'm an outlier... that people have enjoyed a single headset for years without issues or needing replacements... but I've never had a headset that lasted more than a few months. So I'm really starting to think it must be me.... but again... no one can tell me.Presumably someone checks the dead headsets for what the issue might've been. Because presumably Meta has some sort of interest in the failure points of their products. But that data is, as I was told today "for inte

 Launching the game Virtual Virtual Reality (by Tender Claws) seems broken on Quest Pro. The game launches but the controllers/hands/cursor are not recognized by the game and I can not interact with it. Clicking the Oculus/Meta button reveals the shell/Navigator with the controllers rendering just fine. Clicking to go back to VVR and they disappear again.This is a classic game and I wanted to check out the recent Anniversary update but it isn't working. This is after a fresh factory reset of the headset and 2-3 reinstalls of the game.Anyone else having this issue?Same in Chess Club, too.

I really HATE that my kid's headset needs to have my account on it, to share my games.Anyway, I have the "master account" , and it boots and works fine.When he switches to his account, he sees passthrough , no home environment, no menu.menu button makes sounds as if menu opens/closes. Long press runs recenter animation.I deleted his account from the headset, and re-added it, and it worked for a day or two, now the issue is back.There was an old case of same-looking bug, where the "solution" was to switch off/on headset while removed (not on-head).This does not work, as the stupid sharing requires my account, and every time he switches on the headset, he is presented with user selection. - there is no way of making "his" account be the primary, always selected on power-on.

I have 2 devices on my account that I dont have anymore. How do I remove it? I already did factory reset, and returned the items. 

Hi. I have a Meta quest 3 and there is a Critical issue with the Meta Ui/Home Ui. I boot into my account via account switcher and i am stuck in passthrough with no menus, the navigator is gone. Recentering fails. Nothing.. I cast from meta horizon mobile app and it works but app launching doesn't work nor does any of the cast options. IDK what is happening as i have rebooted, hard rebooted and did the boot menu reload but nothing. Please Help😥😥

HelloI lost the battery cover of the right controller for the Meta Quest 3. On the Meta site, I find a kit, but it’s only for those from the Meta Quest 2. Can you give me the correct link to this article ?Thank you

Meta Quest Remote Desktop on macOS fails at login every single time with "Something went wrong. Please wait 2-5 minutes and try again." Waiting doesn't help. The failure is instant and deterministic, so it is not rate limiting despite what the message implies. The app's own log shows the real error. The browser login succeeds and the deeplink comes back fine. The crash happens in credential verification, 275ms later: I0807 22:24:09.961064 AppDelegate.mm:232 MainThread] Received deeplinkI0807 22:24:10.585398 LoginManager.cpp:302 LoginThread0] Verifying credentialsE0807 22:24:10.860221 LoginManager.cpp:233 LoginThread0] Login failed: TypeError: expected dynamic type 'int/double/bool/string', but had type 'null' App version 101.0.0.1.112, build 1029758790, macOS on Apple Silicon. There is a related null earlier in the same session: I0807 22:23:03.527899 Roadblock.cpp:37 Received roadblock query result {"extensions":{"is_final":true},"data":{"xfb_remote_desktop_roa

I have a Meta Quest 3 that cannot complete a factory reset.In Android Recovery I get errors such as:• “make_ext4fs failed”• “I/O error”• “failed to make ext4 on /dev/block/by-name/metadata”The /metadata partition cannot be formatted and the system cannot rebuild itself.The device enters Android Recovery and Fastboot normally, but it cannot create the internal partitions.I need the full firmware to reinstall the system via fastboot/ADB, or confirmation that the internal memory is damaged.

Hello,I recently just bought a quest pro again, I got it used, and I've been having this issue where I can't get past the code screen. What usually happens is I factory reset it from the power + volume down menu. I connect to my wifi, go through the steps, and then it tells me there's an update. It stays on the screen for about 5 minutes, but the headset does not restart as if it didn't update at all? I try putting my code in on my phone and it will tell me "Can't Pair Yet". I've tried restarting the headset, pairing from another phone, pairing on another wifi, factory resetting again, no luck. I've tried going to the website to manually update the headset from https://www.meta.com/help/quest/software_update/ but every time I do it, it'll reach 50% then say the headset was disconnected and reset the headset. I've been trying to do the MQDH way that people say, but the headset won't detect on the app for some reason even if I have the headset plugged in directly to my computer. My

Hi there! Just created a website using a-frame to simply load any .glb model to view it in VR in Meta Quest (or any headset), to preview fast our models without having to connect and/or load on unity or unreal or anything. Also if some of you want to help me implement the grab interactions with controllers (right now I didn't manage to add it with super hands, it just previews the model static), if some of you know how to do it don't hesitate to fork (otherwise I'll look more into it).

Controllers already provide clear haptic vibration feedback, making force-fed UI sound effects completely redundant.​Currently, these click/tap sounds cannot be turned off. The sound triggered when pressing the Meta button is especially sharp and causes severe sensory discomfort. The issue is far worse when using headphones, as the high-frequency sound directly blasts the ears.

I bought meta quest 3. Turned it on and connected to my network. I immediately installed the update and rebooted. I downloaded the app to my phone and granted access. I connected to the same Wi-Fi and clicked add device meta quest 3. Every time I get the same message saying that it was not possible to connect to the device. When there is no such notification (after 10-20 presses of REPEAT), the loading is simply endless. Not only can I for some reason not connect my device, but the serial number on the left side of the device is not added to my Meta products because... for some reason it is WRONG. I can't write to support anywhere!!!!! this piece...how is this even possible???  

I’m experiencing a problem on my Meta Quest 3S where the menus won’t load when using my child’s profile. When I sign in with the main profile, everything loads normally. I’ve also noticed that if I log into the main profile first and then switch to the child’s profile, the menus will load correctly. However, if I start the headset fresh—after a restart or powering it on—and sign directly into the child’s profile, the menus fail to load. I’ve already tried a factory reset, but once I set up the profiles again, the issue returns. Has anyone found a solution for this? Note: The Meta Quest 3S is running the latest software version.

Hello. I'm using a Meta Quest 3S. My headset is fully up to date, and I have already performed a factory reset. I can use the Store and download games normally, but I cannot enable App Sharing or add a second account. The headset says "Something went wrong. Please try again later," and the Meta Horizon app shows: GraphQL error 1675012 - "Device ID must be specified explicitly." Could you please check whether my headset's device registration or account needs to be repaired?

Meta Quest Remote Desktop on my Mac fails at login every time. It shows "Something went wrong. Please wait 2-5 minutes and try again." Waiting never helps. The failure is instant, so it is not really a rate limit. The browser sign-in part works fine. It is the hand back to the app that fails. The app log says the login failed because a value came back as null while it was verifying my credentials. I think I know why. My Quest 3 shows up correctly in the Meta Horizon mobile app under Devices, and in Accounts Center on my phone. But on the web, my account page says it cannot find any devices associated with my Meta account. Same account, no account switching. I also cannot open a support ticket, because the support form cannot find my device either. My serial gets rejected and signing in shows the same no devices message. Has anyone seen this? Happy to share the full log with a moderator.

Hola. Tengo unas Meta Quest 3 compradas en España en 2024. He observado unas marcas o zonas deterioradas en la superficie de ambas lentes.Durante el uso se perciben especialmente en zonas claras y afectan a la nitidez de la imagen.No tengo claro si se trata de un deterioro del recubrimiento superficial de las lentes o de otro problema,por lo que antes de intentar cualquier intervención quisiera solicitar asesoramiento. El dispositivo no ha sido desmontado ni reparado. ¿Existe algún procedimiento oficial de Meta para diagnosticar este tipo de problema?En caso de que sea necesaria una reparación,¿Meta puede indicarme un servicio técnico autorizado en España, preferiblemente en Castellón o Valencia?También agradecería saber si este tipo de problema puede ser evaluado dentro de la garantía legal del dispositivo y cuál sería aproximadamente el plazo de diagnóstico/reparación.Puedo proporcionar el número de serie y fotografías de las lentes si son necesarios. Muchas

My 3s is stuck into a black screen regardless of the attempted actions I've taken (updated software from PC via USB, factory reset, hard reboot, etc, etc). My next option is to open a warranty claim however my device is not shown in the accound to proceed with it. The Meta Horizon Android app is the only one recognizing my headset but still, I cannot proceed with any warranty proceedings. It is quite frustrating... can anybody support? 

MetaStoreHelpI lost my F2A authenticator device and now I can't log into my previous F2A authenticator. This means the Meta account I used before can't be logged into on any device. And I can't reach any customer service through support (SN  is not supported). Please help me.pls

The little bar on the top of my 3s that holds the top bar of my head strap broke, I have tried contacting meta support, but there is no option for this problem, so It won't let me request a fix. It is still under warranty and I could attempt to fix this myself, but I don't want to make it worse or void my warranty.

Since the update the other day the floor level on our meta quest 3 is too low. I have tried everything. Clearing the previous boundary settings, doing the floor level and creating a new boundary but it STILL keeps it low. WTH can I do? We can't play anything and we have wasted hours trying to get the dang thing to work. And no, the lying down option isn't selected so that isn't an issue either. 

I recently got the meta pro and wanted to use it for face tracking primarily through VR chat. I downloaded all the things needed to make this work (i.e VRC face tracking on steam and I already had desktop simulator). I tried to run this through desktop simulator with the correct things installed on vrcft app and nothing was working. I made sure that all the settings were correct, restarted, refreshed and nothing. Then I installed the steam app on my pro so I could bypass desktop sim straight to steam and run it through there. The only issue is that my eyeballs are the only things tracking and nothing else. I did the same assessment with desktop sim and nothing changed. I tried multiple different avis, personal Avis and the ft was enabled but still just the eyes and nothing more. Face tracking works perfectly fine on the headset itself when I am in the meta menu screen in the mirror. I'm not sure what all I can do, I have researched into this and was recommended to go bac

Morning at all.I followed the diferents steps to put my meta 3 on developper mode:Go to meta Horizon and turn on the developper mode on the app.The issue is : When i try to execute an apk on the Meta 3 nothing appears.Perhaps i forgot something?Thx for ur answer

This is an alternate throwaway account I made so I can post about my issues on the forums. I have a Meta Horizon account linked to my Meta Quest 2. However, when I try to log in, it wants to send a code to my email (which is perfectly fine!) and then a code via SMS to my phone number. However, since I last used my headset, I got a new phone plan and new SIM card, and with it a new phone number. I have completely lost access to the phone number the code is being sent to. This is stopping me from logging into my account, and the stupid support AI wants me to log into my account before it will transfer me to a human support agent. I just want to change my phone number to the one I'm currently using or disable SMS verification of my account.

I have been battling with Meta support for TWO months to get my son’s oculus account reinstated. It’s a supervised account managed by myself. Anytime I try to verify his birthdate, it tells me that’s not what they have on file. I’ve tried the birthdate of every family member and still no luck. Support is useless and only replies with the same steps to verify over and over again after I’ve repeatedly said they don’t work. Has anyone else come across this and received and actual working solution? 

Hello! I can't log in to my Meta account. Two-factor authentication is enabled on it, but access to google authenticator is lost. Recovery codes are not suitable. I can't fill out the online support form. When confirming the device, when I enter the email or serial number of the device, I recieve a message that the device has not been found. In order to create this message, I had to register an additional Meta account, as there was no other way to contact technical support.