Skip to main content
New Participant
December 6, 2022
Solved

Quest 2 - Quest pro controllers update stuck at 0%

Hi I just got my Quest Pro controllers today and paired them to my headset (Quest 2), however I can't use them and a little pop up saying "Controller update in progress (Left 0%) (Right 0%)" keeps appearing evey 30 seconds, I left the controllers a while to update but they never progress past 0%

This topic has been closed for replies.
BlueberrieSmoothie
Honored Contributor
January 30, 2023

Hey everyone! It seems like this was an issue for quite a few users over the past week. The good news is that we've been hearing reports of Pro controllers finally updating now! If you haven't, go ahead and try again to see if your controllers are updating and working. 

If you're still getting stuck with your controllers not updating, please let us know!

Make sure you smash that Kudos button!

307 replies

DatBoyy
Participant
January 25, 2023

No solution worked for me yet (pair/unpair, boot while controllers are in dock, factory reset, restart again and again and again)

Also I am not really sure on which firmware version I am. It seems to make a difference if your quest is on 47 or 49 software version. Unfortunately, the 49 update is either already installed on mine, or not available for my Quest 2. I tried updating, but the Quest 2 says it's on the latest firmware.

 

Gonna wait a few days and if it doesn't work and doesn't resolve itself, I will send the controllers back to Meta. I might start looking into the Pico headsets then. It really sucks paying so much money for a device, being excited about it being shipped and then spending 5 hours in the evening googling useless solutions because it doesn't work out of the box. Really disappointing.

New Participant
January 26, 2023

I'm having the same issue. I have un-paired and re-paired the controllers several times. I've rebooted the headset probably 50+ times with the controllers on the charger. I'm having no luck getting these to update and work properly with the quest 2. 

MetaStoreHelp
Community Manager
January 26, 2023

Hey EmeryBrun! Oh no! That's not what we like to hear! We know how not having access to your controllers can put a hinderance on your VR experience, so let's get this squared away. Since you've already tried those steps that you mentioned, we recommend reaching out to our wonderful support team here and we will be pleased to assist you further. Once you click the link, please select your device and follow the prompt to be directed to support. We'll be patiently watching for your response!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Participant
January 27, 2023

I'm having the exact same issue and so far all the comments seem to indicate that support isn't able to help with the issue.

New Participant
January 26, 2023

I am also having this issue. I've tried every solution listed in this thread to no avail. I was in a chat with support for two hours. Not even a factory reset of the headset and controllers has fixed it.

New Participant
January 26, 2023

Tried about 25+ reboots, maybe 10 pairs, and 2 factory resets, on top of what was suggested above in this thread, no luck. I am on v47 with no option to update to v49, if that makes a difference. I've contacted support but it wasn't much help and I'm waiting on an email back from their "specialized team."

Participant
January 26, 2023

Please post back here if the specialized team actually turns out to be useful. I've been at it for hours and still no luck

Participant
January 26, 2023

I have the exact same issue MetaQuestSupport.  The pro controllers are unusable and i can't get past the update in progress (0%) message.  Come on guys! give us a solution... how disappointing...

MetaStoreHelp
Community Manager
January 26, 2023

Hey there, bright90! We can definitely understand your concerns regarding your Quest Pro controllers having an update that's stuck at 0%, and we'd love to help out! If you've tried all the steps we recommended previously to others with the same issue, then we'd recommend reaching out to Meta Store Support so that we can continue helping out! 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Participant
January 26, 2023

you guys don't have a clue do  you?

New Participant
January 26, 2023

I know there are posts similar to this seeming to give an answer but I’ve tried everything from unpairing and repairing the controllers, to turning them on and off again, to repairing my quest 2 controllers just to pair my pro controllers again, to factory resetting my whole quest 2 and nothing has worked. I spent 300 bucks on the dock & pro controllers and now I can’t use them. Would either like a solution, to exchange these for a new pair, or my money back because this is very infuriating.

New Participant
January 26, 2023

And before you ask, yes I have restarted my device multiple times and both the device and controllers have optimal charge

MetaStoreHelp
Community Manager
January 26, 2023

Hey NewWorldMan4, thanks for reaching out to us about this over the forums, we're sorry to hear that you are having issues using quest pro controllers with your quest 2! We also appreciate all the things you have tried such as factory reset and repairing. Let's open a ticket with our Online Support Team so they can look into this issue more closely for you! 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Participant
January 26, 2023

Yeah, support is clueless. They asked me to let the batteries drain completely which takes forever. (Took more than 24h for not even 50%.) And I doubt this will help since you can also reboot the controllers by holding the oculus/menu button for ~8 seconds, and that doesn't do anything… 

 

These are logs from the headset: 

ControllerManagement: Fetched headset challenge for controller: SERIALNUMBER
13:05:30.577  1847  2030 I ControllerManagement: [5th Attempt] Sending OTA Zap to SERIALNUMBER; isFullUpdate=false; localOta=false; pulsaRpcMsg: # com.oculus.os.cm.protos.ControllerPulsaRpcMsg@dc5ef745
13:05:30.577  1847  2030 I ControllerManagement: start_ota {
13:05:30.577  1847  2030 I ControllerManagement: headset_challenge: "eyJobWRfZGV2aWNlX2lkIjoxMDA1NzYwMjYyNDY3NTQsImhtZF9kZXZpY2VfdHlwZSI6ImhvbGx5d29vZCIsInRhcmdldF9kZXZpY2Vfc2VyaWFsIjoiMjMwWVQxQUQ4RjAyTDUiLCJ0YXJnZXRfZGV2aWNlX3R5cGUiOiJzdGFybGV0Iiwibm9uY2UiOiJYaFc5bXpJdnIxOUpWOW5SM2pWU3hUdUc3eEJNVHNBMSJ9"
13:05:30.577  1847  2030 I ControllerManagement: headset_flavor: "user"
13:05:30.577  1847  2030 I ControllerManagement: headset_model: "hollywood"
13:05:30.577  1847  2030 I ControllerManagement: headset_serial: "SERIALNUMBER"
13:05:30.577  1847  2030 I ControllerManagement: headset_version: "49068160412800150"
13:05:30.577  1847  2030 I ControllerManagement: version: 1
13:05:30.577  1847  2030 I ControllerManagement: }
13:05:30.577  1847  2030 I ControllerManagement: version: 1
13:05:30.582  1847  2030 E AnalyticsEvent: could not set key=headset_bundled_image_version value=null
13:05:30.681  1847  2017 D ControllerManagement: Got OtaProgress
13:05:30.682  1847  2017 I RemoteService : requestExtendedConnection(timeToLiveMs=60000)
13:05:30.682  1847  2017 D OVRRemoteService: ControllerGlue: streaming extension rescheduled from 982.520489 to 992.860426; now is 932.860427
13:05:30.694  1871  1871 D OculusNotificationListenerService: Notification posted: 0|com.oculus.notification_proxy|4103|controller_firmware_update|1000
13:05:30.696  2460  2460 D [OAO] VrBroadcastReceiver: action: com.oculus.vrshell.intent.action.NOTIFICATION_WAKE
13:05:30.704  1847  2017 D ControllerManagement: Got StartOtaAck

 

This line appears everytime and seems to indicate an error because of an unset variable in the update progress, so it looks like a software issue:

13:05:30.582  1847  2030 E AnalyticsEvent: could not set key=headset_bundled_image_version value=null
Participant
January 26, 2023

interesting... would def seem to indicate a bug in the quest software...

Participant
January 26, 2023

would hope it is just a software fix, but since nobody is talking at meta, it could be months before we see a fix.. ?

magenONE
Inspiring
January 26, 2023

Alright, I just got the V49, after the reboot, to install the update, suddenly the controllers started to update, with a weird way of notification spamming, but at the end everything started to works. By now I solved the issue.
Btw, the update resetted my home preferences and there is something weird with the tracking, I'm going to figure out later, now I'm here just to let you know.

Participant
January 26, 2023

Looks like my theory might have been right. I'm installing the update now too will report back if it works

Participant
January 26, 2023

Updating to v49 has got the controllers to start updating for me. It really must've been the v49 update rollout that was causing this

Participant
January 26, 2023

i already had v49... so ?

Participant
January 26, 2023

I'm not sure if I'm on v49 or v47...

The update menu lists a few different versions. First one is a long number starting with 49, second and third one start with v47. and look more like a typical version number. Not sure if I'm on 49 or 47… 

 

It still says I'm up to date, though, and the controllers are still stuck at 0%

Participant
January 26, 2023

yeah, actually - relooking at my version - it has System Version that starts with 49xxxxx, but Version and Runtime version both say 47.xxx

so i will wait and hopefully there is an updating coming to me...

Participant
January 26, 2023

The one that says 47.xxx (or 49.xxx) is the version I'm referring to. They started rolling it out on the 19th I believe but when I spoke with support yesterday they said only 10% of users had it. My guess is that number has increased by now but isn't a 100% yet so still not everyone has it. I'm guessing it was also the v49 rollout that was interfering with the controller updates since both updates come from Meta itself

Participant
January 26, 2023

Great, so now I have to wait an unknown time for the update to reach my quest. 🤬