How to modify the VID of android USB

1. Android mobile phone driver:
[GB Version]
File to modify: alps \ mediatek \ custom \ [Chip] \ kernel \ usb \ src \ mtk_usb_custom.h
Modification: VENDOR_ID
[ICS and JB Version]
File to modify: alps \ mediatek \ config \ [Chip] \ init. usb. rc
Modification: sys. usb. vid

2: Computer
On the PC side, modify the MTK release driver and add your new VID and PID.
Please modify android_winusb.inf
In
HTC Magic
% CompositeAdbInterface % = USB_Install, USB \ VID_0BB4 & PID_0C03 & MI_01
Refer to the above sentence and add your changes later. For example:
; ZTE/LENOVO/HUAWEI phone
% CompositeAdbInterface % = USB_Install, USB \ VID_XXXX & PID_XXXX & MI_01

3: Right-click my computer and choose Properties> advanced> environment variable to add the ANROID_SDK_HOME environment variable. If you have an android SDK, set it to the SDK path. If not, it does not matter. Set it to any path that is convenient for you.

4. find the path corresponding to ANDROID_SDK_HOME. android directory. If not, create one. create a new file named adb_usb.ini In the android directory. Remember that the suffix is "ini". Add the obtained VID to adb_usb.ini, for example, 0 xAAAA.

5. Install the adb driver.

6. Enter DOS cmd, and enter adb kill-server, adb start-server, and adb devices respectively. If the list of devices is displayed, the operation is successful.
[Note] 3rd ~ Step 6: if the company's Vendor ID is not in the Google recognized list, this step is required. In addition, Alibaba Cloud can work with Google Inc. to add the company's VID.

In addition, the network references are as follows:
Android usb vid pid and ADB
After the pid vid of the USB driver is modified in the Linux Kernel of the android device, the adb tool may not be able to identify the device, and the prompt "device not found" will be printed, especially for windows, the adb driver cannot be used.
What should I do at this time?

1. First find out the current PID and VID, for example, aaaa and bbbb (hexadecimal)
For linux such as ubuntu, insert a device and query the corresponding devices under/sys/bus/usb/, for example, idVender under "1-1.
For windows, you can obtain it from the properties of the corresponding device.

2. for windows
1. Modify the android_winusb.inf file in the adb driver. You can compare it with other projects.
For example:
; My product
% CompositeAdbInterface % = USB_Install, USB \ VID_AAAA & PID_BBBB
% SingleBootLoaderInterface % = USB_Install, USB \ VID_AAAA & PID_BBBB & MI_01
2. Right-click my computer and choose Properties> advanced> environment variable to add the ANROID_SDK_HOME environment variable. If you have an android SDK, set it to the SDK path. If not, it does not matter. Set it to any path that is convenient for you.
3. find the path corresponding to ANDROID_SDK_HOME. android directory. If not, create one. create a new file named adb_usb.ini In the android directory. Remember, the suffix is "ini". Add the obtained VID to adb_usb.ini, for example, 0 xAAAA.
4. Install the adb driver.
5. Enter DOS cmd, and enter adb kill-server, adb start-server, and adb devices respectively. If the list of devices is displayed, the operation is successful.

III. For linux
1. search for the. android directory under the user's home directory. If not, create it. Create a new file named adb_usb.ini in the. android directory. Remember, the suffix is "ini". Add the obtained VID to adb_usb.ini, for example, 0 xAAAA.
2. In the shell, enter adb kill-server, adb start-server, and adb devices respectively. If you can see the list of devices, the operation is successful.

Here, kill-server is used to kill the daemon of adb. Otherwise, adb retains the information of the first Vender. Start-server loads the new Vender information.

Note:: Some people may need superuser permissions to use adb. In this case, the home directory in step 1 should be/root. I don't want to bother, but I can add both Home directories directly.