Quest Pro: Controller pairing failure after factory reset & stuck at 5-digit code screen
I am experiencing a severe issue where my Right Quest Pro Controller completely refuses to pair. Through various troubleshooting methods, I managed to bypass the initial 5-digit code screen and successfully connected the headset to the Meta Horizon app. However, the controller pairing still fails. There is absolutely zero physical damage to the controller or headset. This happened after an official firmware update bug.
Here are the detailed symptoms and the exhaustive list of troubleshooting steps I have already performed:
1. The Symptoms
The controller LED endlessly loops: White (standby) → Blue → Green → Blue.
When attempting a firmware update, it flashes Purple/White but abruptly crashes and returns to White. Hardware vibration works, indicating a software-level block.
2. Basic & Hardware Resets (Failed)
App pairing results in a Timeout error. Manual pairing (Meta + B) vibrates but fails to connect.
15-second hard reset (until Amber light) & 60-second button hold for capacitor drain: Both failed.
Controller Factory Reset (A+Meta / X+Menu): Successfully triggered the Red/White alternating LED, but pairing still fails afterward.
3. Network & Environment Isolation (Failed)
Forced a 2.4GHz mobile hotspot connection and turned off the 5GHz router to prevent internal Wi-Fi interference.
Covered the proximity sensor with tape to prevent the headset from sleeping during the update phase.
4. App & ADB Debugging (Critical Findings)
Unpaired from the smartphone's Bluetooth list and completely cleared the Meta Horizon app cache/data.
Headset Factory Reset: Performed multiple times via the Android Recovery Menu.
CRITICAL LOG: I ran the adb shell dumpsys bluetooth_manager command. The controller's MAC address is entirely missing from the headset's bonded devices list.
Attempted adb shell pm clear com.oculus.controllerpairing and adb shell setprop persist.bluetooth.btsnoopenable true, but encountered permission/SecurityException errors.
I didn't write it down here, but I've tried many things on the Meta Quest developer hub and have seen the logs, but I can't seem to solve it myself at the moment
Is there anything else I can try