Mobile driver terminal:
[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]\
Modification:
2: Computer
Please modify the driver of MTK release to add your newly added VID and PID.
Please modify android_winusb.inf
exist
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
Refer to the above sentence and add your company's changes later. for example:
; ZTE/LENOVO/HUAWEI phone
%CompositeAdbInterface% = USB_Install, USB\VID_XXXX&PID_XXXX&MI_01
3: Right-click My Computer->Properties->Advanced->Environment Variables and add the ANROID_SDK_HOME environment variable. If you have an android SDK, set it as the path to the SDK; if not, it doesn't matter, set it as any path you find convenient for.
4. In the path corresponding to ANDROID_SDK_HOME set earlier, look for the .android directory, if not, create one; create a new file in the .android directory, called adb_usb.ini, remember, the suffix is "ini"; add the VID obtained earlier to adb_usb.ini, such as 0xAAAA.
5. Then install the adb driver
6. Enter DOS cmd and enter adb kill-server, adb start-server, and adb devices respectively; if you can see the devices listed, then it will be successful.
[Note] Steps 3 to 6, if the Vendor ID of Guisi is not in the default list of Google, these steps are required. In addition, Kusita can contact Google to contact you how to add Kusita's VID.
In addition, the reference materials on the Internet are as follows:
Android USB VID PID and ADB
After modifying the PID VID of the USB driver in the Linux kernel of an Android device, the previous adb tool may not recognize the device, and a prompt of "device not found" will be printed, especially for Windows, and the adb driver will not be used.
What should I do at this time?
1. First find out the current PID and the VID is, for example, aaaa and bbbb (hexadecimal)
For Linux such as ubuntu, insert the device, and then query the corresponding device under /sys/bus/usb/, such as idVender, idProduct under "1-1".
For windows, it can be obtained from the properties of the corresponding device
2. For windows
1. Modify the android_winusb.inf file in the adb driver. Just add it according to 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 and add the ANROID_SDK_HOME environment variable. If you have an android SDK, set it as the path to the SDK; if not, it doesn't matter, set it as any path you find convenient for.
3. In the path corresponding to ANDROID_SDK_HOME set earlier, look for the .android directory. If not, create one; create a new file in the .android directory called adb_usb.ini, remember, the suffix is "ini"; add the VID obtained earlier to adb_usb.ini, such as 0xAAAA.
4. Then install the adb driver
5. Enter DOS cmd and enter adb kill-server, adb start-server, and adb devices respectively; if you can see the devices listed, then it will be successful.
3. For Linux
1. In the user's home directory, look for the .android directory and create it if it does not exist. Create a new file in the .android directory called adb_usb.ini. Remember, the suffix is "ini"; add the VID obtained earlier to adb_usb.ini, such as 0xAAAA.
2. Enter adb kill-server, adb start-server, and adb devices in the shell; if you can see the devices listed, then it will be successful.
Here, kill-server is the daemon that kills adb, otherwise adb will still retain the previous Vender information. start-server loads the new Vender information.
Notice: Some people may need super user permissions when using adb. At this time, the home directory in the first step should be /root. If you don’t want to worry, you can add both Home directories directly.
[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]\
Modification:
2: Computer
Please modify the driver of MTK release to add your newly added VID and PID.
Please modify android_winusb.inf
exist
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
Refer to the above sentence and add your company's changes later. for example:
; ZTE/LENOVO/HUAWEI phone
%CompositeAdbInterface% = USB_Install, USB\VID_XXXX&PID_XXXX&MI_01
3: Right-click My Computer->Properties->Advanced->Environment Variables and add the ANROID_SDK_HOME environment variable. If you have an android SDK, set it as the path to the SDK; if not, it doesn't matter, set it as any path you find convenient for.
4. In the path corresponding to ANDROID_SDK_HOME set earlier, look for the .android directory, if not, create one; create a new file in the .android directory, called adb_usb.ini, remember, the suffix is "ini"; add the VID obtained earlier to adb_usb.ini, such as 0xAAAA.
5. Then install the adb driver
6. Enter DOS cmd and enter adb kill-server, adb start-server, and adb devices respectively; if you can see the devices listed, then it will be successful.
[Note] Steps 3 to 6, if the Vendor ID of Guisi is not in the default list of Google, these steps are required. In addition, Kusita can contact Google to contact you how to add Kusita's VID.
In addition, the reference materials on the Internet are as follows:
Android USB VID PID and ADB
After modifying the PID VID of the USB driver in the Linux kernel of an Android device, the previous adb tool may not recognize the device, and a prompt of "device not found" will be printed, especially for Windows, and the adb driver will not be used.
What should I do at this time?
1. First find out the current PID and the VID is, for example, aaaa and bbbb (hexadecimal)
For Linux such as ubuntu, insert the device, and then query the corresponding device under /sys/bus/usb/, such as idVender, idProduct under "1-1".
For windows, it can be obtained from the properties of the corresponding device
2. For windows
1. Modify the android_winusb.inf file in the adb driver. Just add it according to 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 and add the ANROID_SDK_HOME environment variable. If you have an android SDK, set it as the path to the SDK; if not, it doesn't matter, set it as any path you find convenient for.
3. In the path corresponding to ANDROID_SDK_HOME set earlier, look for the .android directory. If not, create one; create a new file in the .android directory called adb_usb.ini, remember, the suffix is "ini"; add the VID obtained earlier to adb_usb.ini, such as 0xAAAA.
4. Then install the adb driver
5. Enter DOS cmd and enter adb kill-server, adb start-server, and adb devices respectively; if you can see the devices listed, then it will be successful.
3. For Linux
1. In the user's home directory, look for the .android directory and create it if it does not exist. Create a new file in the .android directory called adb_usb.ini. Remember, the suffix is "ini"; add the VID obtained earlier to adb_usb.ini, such as 0xAAAA.
2. Enter adb kill-server, adb start-server, and adb devices in the shell; if you can see the devices listed, then it will be successful.
Here, kill-server is the daemon that kills adb, otherwise adb will still retain the previous Vender information. start-server loads the new Vender information.
Notice: Some people may need super user permissions when using adb. At this time, the home directory in the first step should be /root. If you don’t want to worry, you can add both Home directories directly.