View Single Post
Old 09-13-2014, 09:02 PM   #12
tuxor
Addict
tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!tuxor has a thesaurus and is not afraid to use it!
 
Posts: 320
Karma: 99999
Join Date: Oct 2011
Location: Germany
Device: Onyx Boox M92, Icarus Illumina E653
Here is how to get adb access under linux. (You don't need a special version of adb or something like this. It's as easy as telling adb that the connected device is in fact an Android device that will support adb.)

1. Connect the device to your computer and check with lsusb or dmesg which vendor ID the reader has. Unfortunately lsusb output might be a bit confusing. The Icarus E653 shows up without any name or description:
Code:
Bus 002 Device 005: ID 2207:0010
Whereas in dmesg it will show up like this:
Code:
[ 3152.457286] usb 2-1: New USB device found, idVendor=2207, idProduct=0010
[ 3152.457295] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3152.457302] usb 2-1: Product: rk30sdk
[ 3152.457307] usb 2-1: Manufacturer: Icarus
However, the point is to extract the vendor ID, which is in this case 2207!

2. Disconnect the ereader, edit (or create) with root permissions /etc/udev/rules.d/51-android.rules by adding:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="2207", MODE="0666"
3. Restart udev, which might be something like "/etc/init.d/udev restart" or on some distributions "systemctl restart systemd-udevd.service && systemctl restart systemd-udev-trigger.service && systemctl restart systemd-udev-settle.service" (requires root privileges).

4. Edit (or create) ~/.android/adb_usb.ini and add the vendor ID on a new line in the following format:
Code:
0x2207
Make sure that this line is not already contained in that file!

5. Now run "adb kill-server" and connect the reader. After that it should show up in "adb devices" and adb should work as usual.

Remark: The above procedure is a standard procedure that can be used with many different Android devices. In this case adb-access is also sufficient for rooting the devices because "adb remount" is not prohibited...

Last edited by tuxor; 09-13-2014 at 09:18 PM.
tuxor is offline   Reply With Quote