Boot loop might be occurring due to a simpler. ** (If your vendor isn't Google Inc., also replace the vendor id with the one before the colon in lsusb). Im trying to get my react-native project to run on an android emulator while on a Mac operating system. Android Features: Install Programs without Android SD Ihr knnt die adbLink 4.0 fr Euer Betriebssystem hier herunterladen: Windows Mac OSX Linux. This can be solved by creating a new udev rule - I used /etc/udev/rules.d/les- to add the device to the group plugdev, which adb already assumes you to be a member of (you shoukd be, check using id) SUBSYSTEM='usb', ATTR='4ee7' with your own product id that you found out in step one. This which means that the device file will be owned by the user root and the group root, which is why adb can access it as root but not as your standard user. Likely you will see something like crw-rw-r- 1 root root 189, 5 Sep 8 21:47 /dev/bus/usb/001/006

Point of interest in this case: Bus 001 Device 006: ID 18d1:4ee7 Google Inc.Ĭheck out the corresponding device file $ ls -l /dev/bus/usb/001/006 I too had this problem & came across a relatively simple solution.īus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 8087:0a2b Intel Corp.īus 001 Device 002: ID 05c8:03a2 Cheng Uei Precision Industry Co., Ltd (Foxlink)īus 001 Device 006: ID 18d1:4ee7 Google Inc.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Very likely udev is incorrectly adding your device. Let’s install, setup and use android emulator in Windows, linux and Mac through command line without installing android studio.

Mac android emulator unauthorized