"My Computer"---pipe---find the "Device Manager" inside --select android device, find your device, select "details"---find the hardware ID in the drop-down box
3. Record the hardware In the id line, the id mixed with 4 letters or numbers followed by Vid_
(if my id is 4A36, then I will enter 0x4A36)
http://blog.csdn.net/y_lang/article/details/44037431
Use the manufacturer's own driver or perform the above steps and still can't connect (ADB cannot be directly connected, but can be connected using the mobile assistant)
If the driver provided by the manufacturer is used, there may be no android_winusb.inf file. At this time, the manufacturer's driver is generally installed or after the first step above, the Android Phone device can be seen in the device manager, but ADB in cmd still cannot Direct connection, use various mobile assistants to connect.
Right-click My Computer->Properties->Advanced->Environment Variables, check the ANROID_SDK_HOME environment variable, if not, it is the current user's home directory (for example, if the login user name is fsysy, then the fsysy user's home directory is "C:\Users" \fsysy".) Find the adb_usb.ini file in the .android directory
in the corresponding directory , if not, you can create a new one (there is a . in front of android , the suffix of adb_usb.ini is ini ) or run Android update in the sdk directory /tools adb to get the file. Edit the adb_usb.ini file and add the VID of the device in the file, for example, the VID in the first step is 0x1782 eg
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT. # USE 'android update adb'TO GENERATE. # 1 USB VENDOR ID PER LINE. 0x1782
运行
adb kill-server
adb start-server
adb devices