Forum Discussion
Solved
Anyone else with a new Oculus Quest headset stuck at version 213561.4150.0 and unable to update?
Hi, we're developing a few apps for the Oculus Quest, sideloading and running development builds used to work fine until this morning when we set up 2 new Oculus Quest headsets. Now when I try to run a sideloaded app, it tells me "Update in Progress Please Leave your device on, connected to Wi-Fi and plugged into a power source until the update is finished." Running store apps seem to work fine.
Did anyone else encounter this issue?
Did anyone else encounter this issue?
- Guys I fixed it!
Ok here are the steps:
1. Plug your quest to power.
2. Turn it off completely
3. Hold down the power button along with the volume up (+) button. It should boot you into a menu with a list of options.
4. Select Factory Reset from this menu using the volume buttons
5. Keep it plugged into power the whole time while it does its thing. Wait 5mins
6. On your phone on the Oculus app, select your quest and choose "Finish Setup"
7. Go through the setup process. Leave it alone on the screen where you watch the video tutorial on your phone for like 10 mins. (I was on the phone so I waited about that long, not sure if this helped)
8. Put on the quest, you should have the new firmware now
15 Replies
- Im getting the same error...
- Same problem here, can't update 4 brand new Quest I needed for an event and I can't launch any app. Can't Open My Unreal apps or any app I download in the store
- I also get this message after i build my game using Unity with settings IL2CPP with ARM64 Target Architectures. I have tested this on 2 different quests and 2 different projects. They all show the same message about updating in progress when using ARM64 with IL2CPP.
As a temporary fix i have to build to IL2CPP with ARMv7 only, in the Configuration (Project settings). But i really want to use ARM64, so it would be great if someone could fix this problem.
My setup:
Unity 2019.1.2f1
Unity Integration 1.39
Using Quest version 358570.9320.0
EDIT solution:
I downgraded my project to Oculus Unity Integration 1.38 and it solved it for me. I can now build with IL2CPP and ARM64 without getting the stupid "Update in Progress..." message when i start the game on the quest.
https://developer.oculus.com/downloads/package/unity-integration/1.38.0/ - Sorry double post. Delete me.
ChickenBacon said:
I also get this message after i build my game using Unity with settings IL2CPP with ARM64 Target Architectures. I have tested this on 2 different quests and 2 different projects. They all show the same message about updating in progress when using ARM64 with IL2CPP.
As a temporary fix i have to build to IL2CPP with ARMv7 only, in the Configuration (Project settings). But i really want to use ARM64, so it would be great if someone could fix this problem.
My setup:
Unity 2019.1.2f1
Unity Integration 1.39
Using Quest version 358570.9320.0
EDIT solution:
I downgraded my project to Oculus Unity Integration 1.38 and it solved it for me. I can now build with IL2CPP and ARM64 without getting the stupid "Update in Progress..." message when i start the game on the quest.
https://developer.oculus.com/downloads/package/unity-integration/1.38.0/
The firmware for our headsets are still stuck at 213561.4150.0 though
H1V3RLAB said:
The firmware for our headsets are still stuck at 213561.4150.0 though
Have you tried to do a factory reset of the quest?
Last time i did a factory reset on a quest, it triggered a firmware update after the reset.- I'm seeing the same issue. Is there anyway to force a firmware update?
- same here, strange that support replies like its first time they here this while their forums are floded with people having same issue.
Also
having the same issue with a headset on firmware 358570.6090.0
ChickenBacon said:
H1V3RLAB said:
The firmware for our headsets are still stuck at 213561.4150.0 though
Have you tried to do a factory reset of the quest?
Last time i did a factory reset on a quest, it triggered a firmware update after the reset.
Yup tried that twice, got the same results both times
