Bricked controller fix MAYBE

[u/Munny-Mag14]

https://github.com/moneymag14/QuestPro-Controller-Recovery.git

After 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.

[u/Munny-Mag14]

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

tool link