QCC5125 and QCC3034\QCC3031 programming


New member
2021-12-15 2:13 pm
Hi khseal,
thank you very much for the link!
I've installed the drivers from \drivers\cda\Qualcomm_Drivers_WIN_CDA_104.0.0.exe and tried ADKConfigTool.

Before installing them the Windows device manager showed these devices:
  • Audio devices > QCC5125
  • USB controller > Generic USB hub (HW ID USB\VID_0A12&PID_4010&REV_1669)
  • USB controller > USB device (HW ID USB\VID_0A12&PID_4007&REV_1970)
Now the Windows device manager shows one changed driver - the rest remains the same due to unmatching device IDs in the .inf files:
  • Audio devices > QCC5125
  • USB devices > Qualcomm USB Hub Filter Device - 0001 (HW ID USB\VID_0A12&PID_4010&REV_1669)
  • USB controller > USB device (HW ID USB\VID_0A12&PID_4007&REV_1970)
The ADKConfigTool shows two devices but no connection is possible:


Also the QCC_Tool from this post does not recognize any devices:

If there are any advices how to establish a connection I would be happy :)



2021-12-16 4:14 am
What is your operating system? Recommend Windows 7.
Perhaps something needs to be short-circuited on the chip to enter the programming mode.
Perhaps the debug needs to be disabled.
Perhaps you need version ADK6.3 ...
Alternatively, try changing the PID and VID in the driver...
Perhaps you need to unlock the interface.
After the installation is complete, the MDE cannot confirm the USB Debugging interface, and you need to write an unlock key through the following command to let MDE know that it is not through TRB but USB.
ADK's tools\bin\TransportUnlock.exe writeunlockkey ..\..\..\unlock_usb.txt
unlock_usb.txt I used the default 0000000000000000000000000000000, a total of 32 characters, as the unlock key
Last edited:
I am having a lot of trouble changing my QCC3031's name. I have the exact same module referenced by Xerom in post #27. I was able to get it connected via USB and unlock it. The "QCC Tool" also doesn't work for me, though I can access it via Configuration tool. From what I could gather from Google translate, it is asking me to put in a registration code. I also have an older copy of MDE (ver., but cannot for the life of me figure out how to just save the new name to the device. Wish we still had good old PSTool... Please help, thanks!
So, like I said, QCC Tool works great for me now but I am unable to access my chip in ConfigApp. It seems ConfigApp requires a chip configuration database file (.sdb) that is specific to your chip (in my case, the F-3020 QCC3031 chip). The only database files included in the QCC Tool file shared in this thread are for the QCC512X series.

Is this .sdb file something I can generate on my own using the ADK/BlueSuite/MDE apps? If not, any advice on where to find it?


New member
2022-01-15 9:55 am
From the picture you sent 1.27mm pitch pins are top to bottom
1 - NC
2 - D-
3 - NC
4 - VBAT
5 - D+
6 - VCC
7 - GND

I have the same board and I don't remember where I found it but I found a datasheet for the BTM331 and was able to trace out the pinout to confirm them. To be clear your connections between the two will be

VCC 1 --> 6
D- 2 --> 2
D+ 3 --> 5
GND 4 --> 7

I have the same module with the qcc3031 and I have connected them as supposed by Maddnezz.
My PC (Win10) detects something (Hardware ID matches with the one from the unlocking guides). But it keeps disconnecting every 1-2 seconds, then reappearing. When I try to install the driver I get an error message.
Is there something else that needs to be connected?
Tried powering it with 3.3V at VBat in addition, but it did not help.
I tried with a second module with the same behavior, so either both are broken or I am doing something wrong.

Anyone else had this issue?


  • IMG_20220113_232724.jpg
    516.3 KB · Views: 13


New member
2022-01-15 9:55 am
Is anyone able to change some DSP setting permanently?
I tried the "Write Persistence" option from the QACT tool as mentioned in the QACT Introduction guide.
There is no error message, the tool shows the write to be successful, but unfortunately the values are still lost after a power cycle.