MQDH Won’t Connect Quest 3 at Final Cable Step Despite USB and ADB Working

Hello everyone,

I’m encountering a frustrating issue with Meta Quest Developer Hub (MQDH) v5.7.2 on macOS while trying to set up a Quest 3 running firmware V78.

ISSUE DESCRIPTION

I enabled Developer Mode on Quest 3 via the mobile app.
In the Quest headset, I selected “Always allow USB access.”
SideQuest and ADB (adb devices) can successfully detect the Quest 3.
However, when I run “Set Up New Device” in MQDH, it stalls at the final step asking me to plug in the cable, even after doing exactly that.
No prompt appears inside the headset; MQDH hangs without progressing.
I tried reinstalling MQDH and rebooting both Mac and headset—problem persists.

WHAT I’VE TRIED

Verified Developer Mode is enabled, and USB Connection Dialog permission is granted.
Confirmed USB‑C cable works (SideQuest and ADB both connect).
Rebooted Quest and Mac multiple times.
Uninstalled and reinstalled MQDH, cleared caches/settings.
Used both bundled Quest cable and a known good USB‑C data cable (I tested USB 3.2 cable / Thunderbolt cable with Mac mini USB‑C Thunderbolt port).
adb works fine.

REQUESTED HELP

Could someone please advise on potential causes why MQDH stalls even though ADB and SideQuest work?
Has anyone else experienced this on Quest 3 running firmware V78 with MQDH 5.7.2?
Are there any logs or advanced diagnostics I can capture to pinpoint the blockage?
If anyone has successfully connected MQDH after the V78 update, what steps resolved it?

FULL ENVIRONMENT INFO

Headset Firmware: Quest 3 V78
MQDH Version: 5.7.2 (macOS)
OS: macOS (latest version)
USB cable: Verified data-capable USB‑C
ADB Output: adb devices correctly lists the headset (adb cmd / MacDroid)
MQDH Behavior: stuck at final prompt, no progress

NEXT STEPS

I’m considering doing a factory reset and strictly following the community-suggested flow (skip Air Link until first USB prompt), but not sure if firmware V78 changed behavior.

Thank you in advance!