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.Controller Light Blinking Help
EDIT: before you read this, the problem has been fixed. (look below) Ok so my left oculus quest 2 touch controller is blinking on and off (spelling SOS in morse code). It appears to be paired in the app, but the headset says otherwise. Its been like this for about an hour. I've searched this problem up online, and apparently its some sort of failed firmware update. There are lots of fixes online but none of them work for me. I have tried: - unpairing then repairing the controllers from the app. (x3) - taking out the battery then re-inserting it. - restarting the headset (x2) - entering Bluetooth pairing mode on the controllers - shutting down the headset and then turning it back on. none of these "fixes" worked for me, and every time I tried one the controllers got more buggy: - left controller (bad one) buzzing every half second - right controller becoming unpaired - default cursor (when no controller is paired) staying in one spot If oculus somehow finds this message, please add some sort of firmware reset that will delete, then reinstall the latest version. Help is appreciated, and if the controllers fix themself (for some reason) ill edit this post. until then, HELP o _ o EDIT: ok so after maybe an hour, the lights started to blink very rapidly. after five minutes the controller reconnected, and after maybe 15 more minutes the blinking stopped. I think that during that time the controller was either updating or reverting to a stable state. Anyways, if you have this situation, just wait about an hour and a half. EDIT: view this post for the continuation of this story (it gets worse) https://forums.oculusvr.com/t5/Support/Controller-not-working/td-p/946474
Firmware update delays
Is there any way as a developer we can force a firmware update as waiting for the roll outs takes way too long (months sometimes). It is becoming increasingly difficult to get the latest firmware to test new features like ASW. I find it ridiculous that devs have to wait in line with consumers for firmware and do not have even early access. If I have missed something and there is a way to update without waiting please let me know. Frustrated dev
Ended up Stuck trying to update a fresh Santa Cruz Dev Kit to Firmware that works with Oculus App
So I was trying to ramp up a santacruz devkit we had on hand that had not been previously opened. But I could not pair it with the current user-flow on the oculus app on a phone. Going through the provided documentation I was able to confirm it worked through skipping the first user experience via ADB commands suggested and able to get it access to a wifi network and begin updating the firmware. However I've reached the point where if I turn on the head set I end up with a 'downloading' screen for updating the Headset, but it does not immediately show a progress bar, and eventually only shows a half full progress bar that never (within the last six hours of the work day) updates. I am not sure but I suspect that I've managed to get my Santa Cruz into a bad state, does anyone have advice on a shell command to restart/force the HMD update or a way to reset to factory settings via ADB? The only other thread I can find related to this magically resolved itself without any clarification on how or why. Any help would be appreciated. oculus/vr_monterey/monterey:7.1.1/NGI77B/256550.5350.0:user/release-keys ------------------------ BEGIN SERVER STATE ------------------------ Battery Level: 100 Charging: true Fast Charging: true Wifi enabled: true Wifi configured: true Wifi connected: true Wifi server reachable: true Wifi IP address: 192.168.2.8 Wifi device name: Controller primary configured: true Controller primary connected: true Controller secondary configured: true Controller secondary connected: true Controller other configured: false Controller other connected: false OTA available: false OTA ready: false HMD Update percentage: 50 PIN configured: false PIN locked: false Horizon logged in: false Developer mode: false ADB: true HSW complete: false NUX complete: true NUX State: DAY0_OTA_READY Headset State: STANDBY ------------------------- END SERVER STATE -------------------------
YUR - v16 Firmware Update - Announcement
Hey this is Dilan from YUR. For all our users that like YUR, we wanted to make a general announcement that the V16 firmware disabled the method we used to render the persistent overlay in our app, this was done due to security reasons outside of the scope of YUR. We have been receiving a lot of messages and reviews who are upset about this. However, the app still works. In addition, a lot of developers were coming to us asking if they can develop apps with this overlay functionality. During a time where people are stuck inside, using the Quest as a supplementary fitness device is a great value for a lot of people. A few key points to get across: 1. Persistent notifications and the overlay were a requested feature by developers and users. 2. We never used the method for anything beyond fitness metrics. 3. We respect the security and performance limits of the Quest and ToS. 4. We and several developers are looking for methods of legitimizing this type of application. Thank you Oculus and our users for your support.Rift keeps crashing, PC too under powered?
I'm very new to PC gaming, so please bear with me. I have Ryzen 7 2600x with an RTX 2070, 16GB ram. So far, my Rift S seems to not like it. I think. I get maybe 20 minutes of gameplay, then a low prolonged beep, static, then all black. An orange light flickers in the headset, slow at first but then gets faster. After, I always get a message to update firmware. Then, everything seems ok, but after a few minutes gaming it repeats the whole process. I absolutely love the Rift, and this is my first introduction to VR. But after purchasing it two days ago and having to constantly deal with this, I'm getting very frustrated. Any advice or suggestions on how to fix this would be greatly appreciated. Thank you.
Updates - accessible outside of client?
TLDR: can I download your update packages separately? I work at a company that uses Rift and Rift S to bring training experiences to clients. This means we have machines all over the world that require updates when they roll out. We don't, however, give our clients admin rights to our machines (for a variety of reasons as you can imagine). So my task has been to remotely access their machines and manually do the updates. this is less than ideal -_- If I had access to the whatever update is downloaded though, I'd be able to push it through a domain, or whatever connection we set up. Is there anyway to grab just the update from y'all, as a more enterprise level client? CheersRift S not detected after failed firmware update
I took delivery of a new RIFT S today. All installed well and immediately after detecting the headset the software wanted to update the firmware. This firmware update failed and as Suggested I tried unplugging / replugging the headset. Since then the headset has not been detected and I am completely stuck All the graphics and USB drivers are up to date. I have re-installed the software and still no luck. This is very disappointing. Any suggestions as to how to proceed would be most welcome
