[summary] How to let ADB identify the problems in the development of VID and PID mobile phone (mobile device) _

Click to open the link

If the phone's vid and PID are modified, plug in USB, turn on USB debugging, run the ADB devices these commands, there may be unrecognized situation, and you can identify with pea pods, then run the ADB command can connect the device (Pea pod cannot be closed, Otherwise the ADB will still be disconnected). The main reason for this is that the ADB is not recognizable after the vid has been modified.

Workaround (This method is only for Windows 7):

1, to find their own equipment vid.

Find mobile phone vid method: Connect the mobile phone to the computer---> right computer---> Management---> Device Manager, find the Android composite ADB Interface---> Right key properties---> Details--- > select Hardware ID

Figure 1

Figure 2

2, into the C:\Users\admin\.android directory, add vid to Adb_usb.ini file.

If you do not have a Adb_usb.ini file in the C:\Users\admin\.android directory, you can find the file in the following ways:

Run--->cmd---> enter the android update adb at the Command Line window, and then C:\Users\admin\.android the Adb_usb.ini in the directory.

Open the Adb_usb.ini file to add the vid to the file and save the shutdown.

Figure 3

3, restart the ADB server, verify the success.

Open the command line----> enter adb kill-server----> enter adb start-server

Enter ADB devices validation is successful.

Please correct me if there is any wrong place.