According to give instructions, need to install the USB driver, and then using the ADB to burn,
But after computer and development board to connect the USB cable, computer device manager shows the USB serial port devices, not Android devices,
Give the driver can't install, this is for documentation:
Both Please note:
Default there are four functional interfaces created only one other is the ADB are 2 as the diagnostic purpose (QPST, MDM, DIAG, MASS STORAGE).
Only one endpoint with following is applicable for ADB.
Your android_winusb. J inf file should have below lines ADB.
Android_winusb. J inf
[Google NTx86]
; Qualcomm SURF/FFA
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025 & amp; MI_01
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025 & amp; MI_01

; Qualcomm SURF/FFA (ADB) inhibits PTP +
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E & amp; MI_01
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E & amp; MI_01

; Qualcomm SURF/FFA (MTP) + the ADB
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039 & amp; MI_01
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039 & amp; MI_01

; Qualcomm SURF/FFA (UMS + ADB)
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015 & amp; MI_00
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015 & amp; MI_00
[Google NTamd64]
; Qualcomm SURF/FFA
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025 & amp; MI_01
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025

SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9025 & amp; MI_01

; Qualcomm SURF/FFA (ADB) inhibits PTP +
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E & amp; MI_01
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_904E & amp; MI_01

; Qualcomm SURF/FFA (MTP) + the ADB
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039 & amp; MI_01
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9039 & amp; MI_01

; Qualcomm SURF/FFA (UMS + ADB)
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015
CompositeAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015 & amp; MI_00
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015
SingleAdbInterface % %=USB_Install, USB \ VID_05C6 & amp; PID_9015 & amp; MI_00

(Strings)
SingleAdbInterface="Android ADB Interface"
CompositeAdbInterface="Android Composite ADB Interface"
SingleBootLoaderInterface="Android Bootloader Interface"

When you see a Windows pop - up requesting drivers, dojo.provide the usb_driver folder path. The Other device notifications from Windows should be ignored.

Each time you change your USB connection type from the Android Settings APP, you will see one time installation pop - up requesting for the ADB driver to be installed, dojo.provide the usb_driver folder.
I tried it using a mobile phone can be installed, check the device ID is USB \ VID_05C6 & amp; PID_9015 & amp; MI_00 this format, but development board device ID is different format, name is a usb serial port, don't understand how to install the driver can use to burn the ADB,

CodePudding user response:

Fastboot flash using adb toolkit, you must first make sure the development board into fastboot mode to be able to flash,

CodePudding user response:

Hello! I now also in the study, 820 of the board, but there's no way to the right to enter fastboot mode, can you help to see what is wrong, please http://bbs.csdn.net/topics/392037070

CodePudding user response:

To drive is installed under the Windows, in under the Windows device manager, find did not identify the device, and then update drive, choose to the usb_driver folder, rather than a folder,,
Need to enter fastboot mode flash, and then can identify, I hope you don't meet similar problems and I...

CodePudding user response:

reference xianlingjianke reply: 3/f

give drivers are under the Windows installation, the device manager under the window, find the unidentified devices, and then update drive, choose to the usb_driver folder, instead of a folder,,
Flash, if need to enter fastboot mode, and then can identify, I hope you don't meet similar problems and I...

Why use it to the USB driver drive folder, prompt can not find the driver file? Depressed for a long time

CodePudding user response:

Chose to include a folder? Should be no problem

CodePudding user response:

Yes, contains a folder, I think there should be no problem here, to see the driver file found inside the device ID does not contain qualcomm 820 device ID, after added or not, is it possible to have a look at your driver file?nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull