How Android USB modifies vid specific implementation _android

1.Android Mobile phone driver end:
[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 End
PC Side Please modify the driver of MTK release plus your new vid and PID.
Please modify the Android_winusb.inf
In
; HTC Magic
%compositeadbinterface% = Usb_install, usb\vid_0bb4&pid_0c03&mi_01
Refer to the following sentence, plus your changes. Like what:
; Zte/lenovo/huawei Phone
%compositeadbinterface% = Usb_install, usb\vid_xxxx&pid_xxxx&mi_01

3: Right-click My Computer-> Properties-> Advanced-> environment variables, add anroid_sdk_home environment variables. If you have the Android SDK, set the path to the SDK; if not, it doesn't matter, set it to any path you find convenient.

4. In the previous set of the android_sdk_home corresponding path, search for. Android directory, if not, create one; in the. Android directory new file, called Adb_usb.ini, remember, suffix is "ini"; add the previously obtained VID to In Adb_usb.ini, such as 0xAAAA.

5. Then install the ADB drive

6. Enter DOS cmd, enter adb kill-server, adb start-server, adb devices, if you can see devices listed, then success.
The 3rd to 6th step of "Note", if the vendor ID is not on Google's list, it takes these steps. In addition, you can contact Google how to join the expensive division's vid.

In addition, the resources on the network are as follows:
Android USB VID PID and ADB
After the USB-driven PID VID was modified in the Linux kernel of the Android device, perhaps the previous ADB tool could not identify the device and print out the "Device not found" hint, especially windows, which the ADB driver could not use.
What should we do at this time?

first, understand the current PID, VID for how many, such as AAAA, BBBB (hex)
For linux such as Ubuntu, insert equipment, and then query/sys/bus/usb/under the corresponding equipment, such as "1-1" under the Idvender, Idproduct obtained.
For Windows, you can obtain from the properties of the corresponding device

second, for Windows
1. Modify the Android_winusb.inf files in the ADB drive. Add on to the other items.
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-> Properties-> Advanced-> environment variables, add anroid_sdk_home environment variables. If you have the Android SDK, set the path to the SDK; if not, it doesn't matter, set it to any path you find convenient.
3. In the previous set of the android_sdk_home corresponding path, search for. Android directory, if not, create one; in the. Android directory, new file, called Adb_usb.ini, remember, suffix is "ini" oh; add the VID that was previously obtained Into the Adb_usb.ini, such as 0xAAAA.
4. Then install the ADB drive
5. Enter DOS cmd, enter adb kill-server, adb start-server, adb devices, if you can see devices listed, then success.

third, for Linux
1. In the user's home directory, look for the. Android directory, if it is not created. Create a new file in the. Android directory called Adb_usb.ini, remember, suffix is "ini" Oh, add the previously obtained VID to Adb_usb.ini, such as 0xAAAA.
2. In the shell, enter the ADB kill-server, adb start-server, adb devices, if you can see devices listed, then success.

Here Kill-server, is killed the ADB daemon, otherwise, the ADB still retains the previous vender information. Start-server loaded the new vender information.

Attention: Some people may use the ADB to require superuser privileges, when the first step of the home directory should be/root, do not want to trouble, directly two home directories are added.