

Integrated Rate Matching Hubīus 001 Device 003: ID 125f:a11a A-DATA Technology Co., Ltd.īus 002 Device 003: ID 413c:2107 Dell Computer Corp.īus 002 Device 004: ID 046d:c077 Logitech, Inc.īus 001 Device 009: ID 04e8:6860 Samsung Electronics Co.If you are getting the error ‘ADB’ is not recognized as an internal or external command, operable program or batch file” while running the ADB command in command prompt or Power Shell, here is the solution. Integrated Rate Matching Hubīus 002 Device 002: ID 8087:0024 Intel Corp. The thing that perplexed me is the listing of the tab when running the following cmd :īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 002: ID 8087:0024 Intel Corp. If your device is still not detected, it most likely was plugged in while you did the changes you need to disconnect and reconnect the USB cable then. (alternatively, you can simply force UDEV to reload its rules using Two additional remarks: After changing the UDEV rules, the UDEV service needs to be restarted to accept the changes. By adding the device in both places (which cannot hurt anyway), the device finally showed up. but that doesn't mean there are no such exceptions).

Im krlmlr's case, it was not an "either-or", but seemingly both parts were needed (I never had that before, and I never even used the Details can be found in the linked question (or rather its answers). Syntax for both files differs: while in the first case it's sufficient to simply add the vendor id (įor a Nexus 4), the entry for the UDEV rule is a bit more complex. Of course, USB debugging is enabled in the tablet's settings, and I have already rebooted it.Īs described in Configuring ADB for Nexus 4 on Ubuntu 11.10, under Linux it is important to be listed in either I have verified this by runningīus 002 Device 005: ID 10d5:5000 Uni Class Technology Co., Ltd The first entry below is from another device, the second entry from the tablet. Output is special for this device, no textual description is shown.

(I know that it should be possible to runĪs non-root, but this test was to rule out permission errors.) Do I need a special type of cable to connect a tablet for USB debugging?

I have tried different cables and different USB ports. The same setup does not work when I exchange the phone by my "no-name" i.onik TP10.1-1500DC tablet. I have followed various instructions and finally was able to connect my ZTE Blade to my Ubuntu laptop for USB debugging.
