| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the recovery switches between adb and adb,mass_storage modes,
it overwrites them with its built-in values.
This could be troublesome for Windows users who will end up seeing
a device change when moving between modes.
The existing USB PID+VID in recovery work for all devices, but users
need to have the correct driver installed if using Windows.
Check the Device Manager and see if "Android Composite ADB Interface"
is correctly identified. If not, see
http://developer.android.com/tools/extras/oem-usb.html
for driver update instructions, where you can simply use the drivers
included with Google's Android SDK for ADB.
Koush's universal drivers should also work.
If you have problems using adb on Linux, then it is almost certainly
seeing a UDEV rule problem.
Copy the following set of rules to a text file and save it as
'/etc/udev/rules.d/51-android.rules'
and reboot your system:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0664", GROUP="plugdev"
Thanks at Matt Mower <mowerm@gmail.com> for pointing me on that.
Change-Id: I9884a71d397ff810df0fda86fa75f0ca8878ec4f
|
