Known Problem - v71 BRICKED LEFT CONTROLLER. DO NOT UNPAIR!

[ishlogan]

@MetaQuestSupport Issue Description:
I am experiencing persistent difficulties pairing my Quest Pro headset with its Pro Controller. The pairing process consistently fails with the error code -22, which indicates a LOCAL_SECURITY_REJECTION during the secure pairing handshake. This suggests a certificate mismatch or compatibility issue between the headset and controller firmware.

Key Observations:

Error Details:
Logs show the following:
Peer cert valid?: false
KeyExchange failure Reason: LOCAL_SECURITY_REJECTION
These errors suggest the Quest Pro is rejecting the Pro Controller’s certificate, likely due to firmware mismatches or validation issues.

Firmware Handling:
I used the official Meta tool to sideload and reinstall the latest available firmware on the headset. Despite this, the pairing failure persists, confirming the issue is not due to incomplete or corrupted firmware on the headset.

Connectivity:
Bluetooth:
Fully operational (SCAN_MODE_CONNECTABLE).
The controller is discovered during pairing but fails at the secure handshake stage.
Wi-Fi Direct:
Functional: The headset establishes a P2P connection as the group owner (192.168.49.1).
Communication occurs between the devices over Wi-Fi, ruling out connectivity issues.

Logs Supporting Diagnosis:
Pairing failure consistently halts at cms_secure_pair_rejection.
Certificate validation fails (Peer cert valid?: false).
Network-related logs show no issues, emphasizing a firmware or security protocol conflict as the root cause.

Steps Already Taken:
Deleted existing Bluetooth pairings via ADB.
Verified functionality of Bluetooth and Wi-Fi subsystems.
Used the Meta tool to reinstall the current firmware on the Quest Pro headset.
Repeated pairing attempts, confirming consistent failure at the same handshake stage.
Reviewed extensive logs for additional insights, which confirm a certificate validation issue.

Request for Support:

Firmware Compatibility:
Are the firmware versions of the Quest Pro headset and Pro Controller confirmed to be compatible?
If not, how can I update both to ensure compatibility?

Certificate Mismatch:
Is there a known issue with certificate validation between these devices?
If so, are there steps to manually bypass or resolve this mismatch (e.g., through an ADB command or support-provided tool)?

Further Debugging Steps:
Are there additional commands, tools, or configurations that I can use to diagnose or resolve this issue?

[ishlogan]

@MetaQuestSupport 

Issue Description:
I am experiencing persistent difficulties pairing my Quest Pro headset with its Pro Controller. The pairing process consistently fails with the error code -22, which indicates a LOCAL_SECURITY_REJECTION during the secure pairing handshake. This suggests a certificate mismatch or compatibility issue between the headset and controller firmware.

Key Observations:

Error Details:
Logs show the following:
Peer cert valid?: false
KeyExchange failure Reason: LOCAL_SECURITY_REJECTION
These errors suggest the Quest Pro is rejecting the Pro Controller’s certificate, likely due to firmware mismatches or validation issues.

Firmware Handling:
I used the official Meta tool to sideload and reinstall the latest available firmware on the headset. Despite this, the pairing failure persists, confirming the issue is not due to incomplete or corrupted firmware on the headset.

Connectivity:
Bluetooth:
Fully operational (SCAN_MODE_CONNECTABLE).
The controller is discovered during pairing but fails at the secure handshake stage.
Wi-Fi Direct:
Functional: The headset establishes a P2P connection as the group owner (192.168.49.1).
Communication occurs between the devices over Wi-Fi, ruling out connectivity issues.

Logs Supporting Diagnosis:
Pairing failure consistently halts at cms_secure_pair_rejection.
Certificate validation fails (Peer cert valid?: false).
Network-related logs show no issues, emphasizing a firmware or security protocol conflict as the root cause.

Steps Already Taken:
Deleted existing Bluetooth pairings via ADB.
Verified functionality of Bluetooth and Wi-Fi subsystems.
Used the Meta tool to reinstall the current firmware on the Quest Pro headset.
Repeated pairing attempts, confirming consistent failure at the same handshake stage.
Reviewed extensive logs for additional insights, which confirm a certificate validation issue.

Request for Support:

Firmware Compatibility:
Are the firmware versions of the Quest Pro headset and Pro Controller confirmed to be compatible?
If not, how can I update both to ensure compatibility?

Certificate Mismatch:
Is there a known issue with certificate validation between these devices?
If so, are there steps to manually bypass or resolve this mismatch (e.g., through an ADB command or support-provided tool)?

Further Debugging Steps:
Are there additional commands, tools, or configurations that I can use to diagnose or resolve this issue?

[ishlogan]

@Dibelabbes @CYMK @LeonardoXDXD @stallingblock2 @fitzvb @shiveringice @WootM4ge @ThyRuinedKing 

[oculusness]

@ishlogan  why not post in a thread where this is already an issue - 

Solved: Quest Pro left controller not work/pairing - V71(c... - Meta Community Forums - 1259627

[ishlogan]

Because the issue was not solved and meta support is a robot.

[oculusness]

@ishlogan  tell us something we don't know.  Just keep spamming the thread to keep it at the top of the forum until the bots do something about it.

[ishlogan]

Wanted to consolidate the issue into a thread with a concise and detailed account and explanation of symptoms and attempts at fixes.

[oculusness]

@ishlogan  meta need to do betta!

[ishlogan]

@MetaQuestSupport 

[ishlogan]

@MetaQuestSupport