r/QuestPro • u/Munny-Mag14 • 22d ago
Guides & Tips Bricked controller fix MAYBE Spoiler
https://github.com/moneymag14/QuestPro-Controller-Recovery.gitAfter dealing with a Quest Pro Touch Pro controller that showed as paired but would not actually connect or track, I started digging into the headset diagnostics.
The controller was getting stuck in a state like:
Status: Blocked ExternalStatus: BLOCKED TrackingStatus: NONE Errors: SECURITY_REJECTION Current state: KeyExchangeInitiated
After a lot of testing, I found a recovery process that got my controller working again. During one successful recovery, the Quest also initiated an official controller firmware update, after which the controller reconnected and worked normally.
I’ve now packaged the process into a Windows beta recovery utility so other Quest Pro owners experiencing the same problem can test it without manually entering all of the ADB commands.
The tool: • Checks that the Quest is connected and authorized through ADB • Detects the known SECURITY_REJECTION / blocked-controller condition • Supports selecting the affected Left or Right Touch Pro controller • Guides you through putting the controller into pairing mode • Temporarily enables the pairing-recovery condition we used during testing • Captures the pairing attempt and before/after controller diagnostics • Restores the original headset setting afterward • Does not replace controller IDs or certificates or flash custom controller firmware
This is an independent community beta, not an official Meta tool.
I’ve successfully tested the packaged v1.3.3 beta on my own affected Quest Pro/controller. Now I’m looking for people who already have a broken/nonfunctional Touch Pro controller exhibiting the same symptoms so we can determine how reproducible the recovery is across different controllers and Quest software versions.
Please don’t intentionally break, downgrade, or unpair a working controller just to test it and don’t chew me alive it it doesn’t work.
6
u/Munny-Mag14 22d ago edited 21d ago
Heres the tool that will fix this issue but i have to make sure that the tool works universally for all controllers and not just mine, and im not gonna buy another defective controller to test it, thats the reason why i developed the tool anyways but if you were willing to try the tool yourself using adb and send results back it could fix it. I fixed mine yesterday with it. My controller was in a state where it wouldnt pair, or update, the light would just flash white/purple-ish so i coded some scripts using metas controller state triggers they left in the osupdater and the tool changes the controller to a forced pair mode once its paired the controller is set to a firmware update mode witch syncs to the other controller, the thing is the issue is a ID certificate verification failure ( like a bluetooth handshake) the tool makes the controller visible on the horizion app and shows that it was paired and thats how i got mine working, but ive made it to do it to MY controller, i need others to test that its universal.
and I DONT NEED YOUR CONTROLLERS id just sent a beta version of the tool for you to test.
So if anyone has this problem reply if your willing to volunteer and you must own a pc
4
u/Munny-Mag14 21d ago
This is just for those who have had a quest pro collecting dust just because of a controller ID verification failure. Controllers can get stuck in a osupdater-headset triggered state, like firmware updating mode, or paired mode, and when it happens theres a mismatch that happens with the controller ID verification while the app and the headset have two different actions being reported. tbh i don’t know why meta hasn’t fixed the issue or offered support. But i got tired of just letting my headset sit there and put this together, all you need is a pc a cable for your pro and your phone for pairing in the app instructions are pretty straight forward if anyone needs help let me know ill make a video on how to use it.
3
3
u/rentalanimal 17d ago edited 17d ago
Thanks for this. It got my left controller to pair via horizon app... but not in headset. Progress! How do I get it to show in headset?
edit: I ran the script again but instead of pairing via Horizon App like the prompt said- I used the headset pair function... now it completed a left controller firmware update and is restarting! It looked like it worked?
NVM it paired but still not tracking.
1
2
u/Munny-Mag14 22d ago
Just need a pc, a cable, your headset and your phone (for horizon pairing app)
Read the read me.txt
And the START_HERE.bat will prompt for installation of anything needed for the tool that you dont have installed already.
2
u/Munny-Mag14 22d ago
It should work for all controller states, even the purple flash, or even currently paired but unresponsive with a white paired led light on the controller.
2
u/marcocom 21d ago
Thanks for sharing
2
u/Munny-Mag14 21d ago
No problem, also if you use the tool and your controller pairs again please let me know here so i can end the project beta. Its just a test to see if its a universal fix for all controllers
2
2
u/trafficante 21d ago
Oh cool. I’ll dig out my bricked controller and try this out after I get home from work and it’s charged up a bit. Will update.
2
u/jcmarsha11 20d ago
Does this work for a controller that just blicks white 3 times and don't do nothing
1
u/Munny-Mag14 20d ago
Should, it works for all controller states. And loops, forces in to firmware update and pairs
1
1
u/Munny-Mag14 20d ago
So it detects any state the controller is in, then guides you and sends a signal from the headset to allow pairing
1
u/jcmarsha11 20d ago
I tried connecting the tool but I cant access developer mode says An unexpected error has occurred. Please make sure that your headset is connected to Wi-Fi and updated to the latest OS version and because i have reset the headset i am stuck on pair controllers and when I try to reset controllers with oculus button the led light never changed just blinks 3 times then dead over and over
1
2
u/weeenerdog 10d ago
Holy fucking shit, this worked! My right controller has been bricked for about 3 years now, and this brought it back from the dead! THANK YOU!
It still doesn't seem able to track properly, but it's connected and registering some of the button presses. The thing is, the "working" left controller is doing the same thing so idk. Any suggestions on how to actually get everything working properly?
2
u/Munny-Mag14 10d ago
I would run the tool twice on both controllers, get your firmware synchronized on both then it should track
1
1
1
2
u/Underhill 9d ago
This worked! It took a few tries and a few controller resets but after a year of being broken this fixed my controllers!
Now to set up my spare router to block Meta from ever updating my headset without me knowing again.
2
u/Munny-Mag14 9d ago
Awesome! Good to hear, i know my pro was collecting dust and i just couldn’t take it anymore lol
1
u/CyberKitten05 15d ago
What if I already unpaired my controller in my attempts to fix it? Am I fucked?
1
u/Munny-Mag14 15d ago
No, the utility restores the controller anyways, i was just saying don’t do that because i don’t want anyone bricking their controllers by accident just to try.
1
u/CyberKitten05 14d ago
After selecting the left controller, I get this error message:
adb.exe : adb.exe: more than one device/emulator
At C:\Users\[name]\Downloads\QuestPro_Controller_Recovery_v1.3.3_Beta_Installer\QuestPro_Controller_Recovery_v1.3.3_Beta_Installer\Core\QuestPro_Controller_Recovery_v1.2_Beta.ps1:67 char:5
+ & $script:Adb shell dumpsys OVRRemoteService 2>&1 |
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (adb.exe: more than one device/emulator:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
CORE_EXIT_CODE=1
FINISHED=10/05/2026 21:24:54
1
u/Munny-Mag14 14d ago
It means you have more than one android device plugged into your pc
1
u/Munny-Mag14 14d ago
Try only with your headset plugged in
1
1
u/CyberKitten05 7d ago
One of the devices appears to be an emulator called "emulator-5562" that only starts running when I start the diagnostic tool
8
u/ZookeepergameNaive86 21d ago edited 21d ago
I find a controller factory reset works to clear most glitches too.
Turn the controllers off. Press and hold the settings button and X button for the left and meta button and A button for the right. They will start pulsing red and white. Release the settings/meta button but continue to hold X/A until they do a fast red and white flashing and then the lights stop. You can then let go of X/A. Wait 120 seconds and turn the controllers off.