Quest 3 Controller Bricked by OTA Firmware Update - No Recovery Options, Only $50 “Fix”
On June 6th, 2025, my Quest 3's right controller abruptly stopped working after briefly reporting a low (but likely incorrect) battery level. It was working perfectly a few days prior. After trying the standard troubleshooting steps, I’ve concluded that the controller was likely bricked by a failed firmware update, and there’s no available way for me to recover it except to pay $50 for a refurbished replacement. Here's what happened: libosutils Failed to get real path of file '/data/vendor/misc/sensors/latestfwversion/f43058c4acd3faab', err: No such file or directory 18:48:39.573 SensorService Failed to read from file /data/vendor/misc/sensors/latestfwversion/f43058c4acd3faab 18:48:39.573 libosutils Failed to get real path of file '/data/vendor/misc/sensors/batteryinfo/f43058c4acd3faab', err: No such file or directory 18:48:39.573 SensorService Failed to read from file /data/vendor/misc/sensors/batteryinfo/f43058c4acd3faab These errors show that the controller is failing to report its firmware version and battery status, and never fully initializes. It can pair, but: Doesn’t vibrate during pairing (haptics subsystem never loads) Doesn’t send telemetry (battery, firmware, etc.) Can’t complete firmware update via OTA What likely happened: Quest v76.1027 began rolling out on June 2, 2025. I used the headset on June 4, which likely triggered a silent controller firmware OTA. The controller may have shut down during the update due to battery instability. This resulted in a corrupted firmware image, leaving the controller stuck in a partial boot state. After factory resetting the headset, the controller worked briefly until the headset likely tried to push the firmware update again. Now the controller pairs but never becomes usable again. My support experience: I contacted Meta support and was immediately offered the out-of-warranty program. $50 to send in the controller and get a refurb. No one reviewed the logs I provided. Every email was answered by a new agent, and every escalation request was ignored or redirected back to the same scripted reply. I did not cause this issue. Meta pushed an update that bricked my device, and now I’m being asked to pay for their mistake. What I'm Asking: All I want is for Meta to repair or replace the controller they broke, without charging me $50 for it. If I had access to the reflashing tools, I could fix this myself in minutes but those tools are not provided externally. If anyone from Meta is listening: please escalate this to someone who understands firmware. This is a known class of failure and it shouldn’t be offloaded onto customers who had no control over the OTA update process.Can I connect my Quest 3 controllers to my Quest 2?
I have Quest Pro Controllers that I have been using on my Quest 2 (Great!!) I purchased a Quest 3 and will be moving the Quest Pro Controllers to it. I would like/prefer to pair my Quest 3 Controllers to my Quest 2 Headset. Currently this is not an option to select in the App. Are there any plans to allow Quest 3 Controllers to work on a Quest 2 (similar to how the Pro Controllers work on Q2)? What would be the reason to not allow/support it? Thank You! MrTasselhof YouTube (MrTasselhof) Twitch (MrTasselhof)
Linux Support???
I'm really disappointed that I wasted $400 on a Rift S just for it to become a paper-weight since I don't want to use Windows on my computer. I have no clue why a multi-billion dollar company can't afford to support more than one operating system. I'm by no means expecting perfect support with no performance issues or hiccups on the less popular OS's, but having the headset be COMPLETELY UNUSABLE is not at all excusable. Just let me use the headset, and I'll do the optimizing myself. It's pretty embarrassing that Valve, a company valued at $8 billion, can comfortably support Linux and Windows almost flawlessly on their headsets, but Oculus, which is owned by Meta, a company valued at $572 billion can only support Windows. I understand the tone may seem harsh, but as someone who spent $400 dollars on the thing, I should have the right to use it on whatever computer I see fit even with less than desirable performance.Build Deployment Automation Failing on Server Side using ovr-platform-tool.exe
Hi, I've been working on a bash script that deploys to the app lab using the ovr-platform-tool.exe, the idea is to hook it up in my build automation machine and for specific targets (like a release) deploy it automatically from Unity Cloud Build to the App Lab. I referenced a lot of the code provided in the Unity SDK, particularly the content of OVRPlatformTool.cs I'm getting a server side error: [error] ERROR: An unexpected error occurred [error] 2024-02-24T03:02:04.219Z [ERROR] Server log: {"app_id":6906526809465140,"client":"COMMAND_LINE","log_level":"ERROR","event_name":"UNEXPECTED_ERROR","stack_trace":"TypeError: Cannot read properties of undefined (reading 'eventStart')\n at y (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at Function.from (<anonymous>)\n at Object.genUploadChunksConcurrently (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js","extra":"{\"caught\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.96.0.000001\",\"compatibility_version\":2,\"session_id\":\"6906526809465140_2024-02-24T03:01:58.650Z\",\"command\":\"upload-quest-build\",\"app_id\":6906526809465140,\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.96.0.000001","session_id":"6906526809465140_2024-02-24T03:01:58.650Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":5569} [error] 2024-02-24T03:02:04.242Z [ERROR] Server log: {"app_id":6906526809465140,"client":"COMMAND_LINE","log_level":"ERROR","event_name":"COMMAND_FAILED","stack_trace":"TypeError: Cannot read properties of undefined (reading 'eventStart')\n at y (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at Function.from (<anonymous>)\n at Object.genUploadChunksConcurrently (C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js)\n at C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async C:\\snapshot\\D_Zfull-fbsource\\edenfs\\redirections\\arvr\\js\\temp\\build-ovr-platform-util\\lib\\ovr_platform_util.js","extra":"{\"caught\":true,\"os\":\"{\\\"platform\\\":\\\"win32\\\",\\\"arch\\\":\\\"x64\\\",\\\"type\\\":\\\"Windows_NT\\\"}\",\"cli_version\":\"1.96.0.000001\",\"compatibility_version\":2,\"session_id\":\"6906526809465140_2024-02-24T03:01:58.650Z\",\"command\":\"upload-quest-build\",\"app_id\":6906526809465140,\"platform\":\"ANDROID_6DOF\"}","platform":"ANDROID_6DOF","cli_version":"1.96.0.000001","session_id":"6906526809465140_2024-02-24T03:01:58.650Z","binary_id":"","duration":null,"is_patch_upload":0,"duration_since_session_start":5592} [error] [2024-02-24T03:02:05.869Z] - 7.3.35.2.7.4 - ERROR: User script exited with status 1. Aborting. [error] [2024-02-24T03:02:05.995Z] - 7.3.35.2.7.4 - ERROR: Build of 'release' failed. 783: unexpected token at '' Any idea about whether it's a bug or something I'm missing on my end? This is my current deployment script: https://gist.github.com/hector-yumebau/2611b0c094de90231ab1be461bf5e5e6
Head set carry case
Hi I have had problems with my carry case that I purchased with my quest three. The zipper has failed. Has anybody else had this problem? I have repeatedly tried to get in contact with Meta quest regarding this issue. However nobody replies to any of my messages I’ve raised about five different, issues with the help centre and I am yet to receive one reply. All I’m trying to do is get the case replaced under warranty, just wondering if anyone else has experienced any issues in getting in contact with MedQuest help thanksWhy is Oculus Developer Support so bad?
This isn't supposed to be a rant thread, but I am genuinely surprised about how bad the experience has been for us so far developing for the oculus platform in terms of available resources and support. On the end-user side, oculus/Meta seems to do a really good job in providing resources and quick support, but it seems to be quite the contrary on the developer side and it just puzzles me why this is the case. There are hardly any answers from oculus engineers on this forum, support tickets take forever and don't yield any actual help and SDK documentation is often seriously lacking. Given that Meta is so dedicated in pushing the Metaverse, I'm genuinely surprised about the way they treat developers that dedicate their time and resources building experiences for their platform, and thus I wonder whether they maybe internally have the stance that developing polished VR experiences is something rather difficult that they don't expect independent developers to come up with and thus focus their resources on providing direct support channels to the big studios instead? I'd be interested to hear about the experience of other devs on here and also what place you go to when you have problems or questions (because the official developer forum doesn't seem to yield any results for any non-trivial questions/problems)? MetaQuestSupport
How to contact meta support as a developer?
I'm part of a small indie studio and we submitted a game to be reviewed for app lab 7 months ago. Nothing has happened and the game is stuck in review. We've had no communication from Meta, and we fear that something has gone wrong during the review process and the game will be stuck in review forever. How do we contact Meta support as a developer? Is there an email, phone number, website, ANYTHING we can use to contact them? What are you supposed to do if you have issues during the submission process if there's no one to contact and you can't do anything while the game is being reviewed?
