0

I am attempting to run adb from a Lil'Debi chroot enviroment. Unfortunately, I keep getting no devices in attached device list. The enviroment created by Lil'Debi links some system folders but does not link /dev; I expect because Android /dev and Linux /dev are not fully compatible. I'm not even sure if this is a requirement for accessing the usb but I have read that since Lil'Debi chroot runs with full root priveleges that I am supposed to be able to access all the devices.

Improve this question
6
  • I have recursively bind mounted /dev/bus to /debian/dev/bus and can now get a read out from lsusb but adb still reports no device attached.
    – stoneAge
    Commented Oct 26, 2020 at 22:01
  • adbd uses Android/Linux kernel's USB gadget/device mode to expose itself to a USB host like a PC connected at the other end of USB. You are trying to access USB device from within USB device, not a host. It won't work simply. Better use ADB over network.
    – Irfan Latif
    Commented Oct 27, 2020 at 15:19
  • @Irfan Latif - Honestly, the goal is not to be able to adb from Lil'Debi chroot, that was just to try to test the connectivity of the usb device. The ultimate goal is to be able to use Rockchip usb tools from one android device to another. Unfortunately, the Rockchip usb tools are proprietary and only compiled to run in a Linux or Windows enviroment thus the need of the Linux enviroment created by Lil'Debi. Thanks for your reply.
    – stoneAge
    Commented Oct 27, 2020 at 16:26
  • github.com/guardianproject/lildebi/issues/41
    – 44yu5h
    Commented Oct 28, 2020 at 4:56
  • @Aayush - after reading that I modified Lil'Debis' start up scripts to include 'mount -t devtmpfs devtmpfs $mnt/dev' and now have the following when issuing mount command with no args - devtmpfs on /dev type devtmpfs (rw,relatime,size=458172k,nr_inodes=114543,mode=755)
    – stoneAge
    Commented Oct 31, 2020 at 16:50

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .