Forum Discussion

thehurz's avatar
thehurz
Explorer
8 months ago

Not Solved - Quest 3 stuck in firmware update loop

A few days ago my Quest 3 rebooted by itself, showed an icon of a chip with an arrow pointing to it and a green progress bar, which most probably means it's trying to update the firmware. Since then I've tried literally everything, multiple reboots, factory reset, sideloading an update via the Meta web page (error connecting to device), got several firmware versions from cocaine.trade/Quest_3_firmware and sideloaded them with adb (which at least _appeared_ to do something), but the problem persists: After every reboot the device goes into that firmware update mode and after it, it's a black screen.

Meta let me down... refusing any meaningful support and also the replacement of the device on the grounds that it's half a year out of warranty. I loved the Quest 3, but this horrible attitude towards the customer is shocking.


5 Replies

  • Zacch1234's avatar
    Zacch1234
    Honored Guest
    8 months ago

    Same thing happened to me exactly two days ago!

    I'm still looking for a solution..

    • thehurz's avatar
      thehurz
      Explorer
      8 months ago

      Let me know if you found a solution, but also if you are stuck with a bricked device.

  • thehurz's avatar
    thehurz
    Explorer
    8 months ago

    Even after mailing back and forth for a week, Meta refuses to help me. The only option they offer is buying a used device for $340. It's mind boggling they can get away with this after they actively broke my device.

     

  • Payne_Max's avatar
    Payne_Max
    Honored Guest
    6 months ago

    The problem with your device is very strange. My Quest Pro is also having issues with the auto-update. Not the same as yours, but I'm still posting it here in case anyone finds this helpful.

    So the problematic behavior is that the device keeps rebooting without any user input. Even though it keeps rebooting, at least it still boots the OS successfully every time, so that you have enough time to disable all auto-update switches before it starts the next reboot. Disabling all the auto-update switches is what stopped this glitch for my device.

    I think the cause for this issue is that the currently installed software is somehow newer than the newest available version from their server. This is very strange but you can check for yourself by going to the software update page in your device's settings, and see if the version code of your currently installed firmware is newer than the version code of the update it's giving you.