[Droid Turbo 2 Q&A, Help & Troubleshooting] maxieds:
Solution update (2017-2018 version) for recent Ubuntu-based Linux and Windows 10

(

NOTE: I am unable to post complete URLs due to having an insufficient number of XDA Forum posts at this time. The bulk of this post and the information contained within is available by searching for my GitHub account (

maxieds

) and selecting the most obvious pinned repo description. My GitHub page is also linked off of my XDA Forum profile just to be clear.

:o)

Preface

: I realize that this thread is somewhat dated, but so is this antique 2015-era phone, so I figured it's worth pointing out a recent solution to those patient Google searchers who like me are still using the device. This solution (works for me on a recent 2017 Debian-derivative Linux box, and/or a loaner Windows 10 laptop) is to avoid the proprietary Motorola software and drivers you will stumble onto from the official ADB links from Android Studio. All you need is the standard Google USB drivers and a more recent list of phone USB device ID properties. I haven't tested, and so cannot confirm, but I suspect that this method should get ADB up and functioning on other hard-to-configure deviant phones using the list of Linux udev supported configurations from this recent (and often updated): <GITHUB>/M0Rf30/android-udev-rules. My modification for the DROID TURBO 2 phone is forked <GITHUB>/maxieds/android-udev-rules. If you find this information helpful, I'd appreciate it if you would STAR my repo on GitHub (<GITHUB>/maxieds/android-udev-rules/stargazers). As a variant of the the old Unix joke goes in obscure 20-year-old Slashdot references: How do we fix Windows? ... Well, I propose we port WINE to Windows ... With this in mind and in this spirit, let's port the oh-so-wonderful Linux UDEV config to Windows.

NOTE

: the DROID TURBO 2 didn't work out-of-the-box on Ubuntu either however, even after installing other variants of the udev rule sets, so my mod is necessary to fix at least this stubborn class of Motorola devices. One possible explanation for why this device doesn't work like nearly every other Android phone is a USB3 bug where file explorer, etc. works on the same USB port, but ADB fails. The purported non-software work around is to chain the phone's USB connection in serial to a cheap self-powered USB hub that effectively masks this bug, but I had no such luck with this experimental fix and of course your mileage may vary. More likely, the cause is that the phone preempts the typical detection sequence by changing the id of it's ATTR{idProduct}=="2ea4" to ATTR{idProduct}=="2ea5" (or some other related ID) when it is connected through USB debugging for use with ADB. See the following image detailing the respective dmesg and lsusb changes pre/post enabling USB debugging on a device connected via USB in Linux:

[IMG="Terminal Output of USB"]https://github.com/maxieds/AndroidADBExtraUSBConfig/blob/master/images/idproduct-discrepancy-illustrated.png[/IMG]

===== Ok, so here, goes with the updated device details: =====

Recent (2017,2018) Solution for Using the DROID TURBO 2 Phone with ADB:

Recently, I finally got into Android development using my Motorola DROID TURBO 2 phone ... only to find that the phone isn't recognized out-of-the-box on either Linux or Windows. After searching around for a while, I finally have found a solution on Linux, which I then "ported" to Windows 10 using the stock Google USB drivers which are easy to find and install with Android studio. The solution is essentially this:

on Linux

(after installing Android Studio / ADB / Android Tools in Ubuntu):

Use this updated udev file to get the TURBO 2 recognized:

<GITHUB>/maxieds/android-udev-rules

. The working forked file basically required setting a few non-standard udev options and inputting the complete device spec found with

lsusb

. After following the instructions at the referenced link, running

adb devices

from your favorite terminal should display the device. Now happy ADB and Android debugging to you and your ancient phone! :svetius: (AND please be sure to STAR my repos!)
​

in Windows 10 (Enterprise):

First, install the Google USB Driver using the SDK manager in Android Studio (under Extras). This puts the driver files in (on my local text box) "Program Files (x86)\Android\android-sdk\extras\google\usb_driver\*". I had to right-click, install and enter the administrator password for the local box to install this. At this point, you can open up "Computer Management > Device Manager" (as ROOT) and see if your phone is automatically recognized by the stock Google USB driver. Mine is not, so we have more work to do. From the GitHub repo (<GITHUB>/maxieds/AndroidADBExtraUSBConfig) I have created, copy the two files under android_google_usb_driver_mod into the default folder for the Google USB Driver files (linked on Windows 10 as above). Repeat the process to install the driver.

Hopefully, now you can get the Motorola DROID TURBO 2 device up and developing with ADB and Android Studio! :good:

---------- Post added at 09:40 AM ---------- Previous post was at 09:32 AM ----------

Since I was unable to post the links to the GitHub repos relevant to the recent solution to this problem, maybe this will get past the XDA Forum filters. Here's a QR-Code to the Wiki page on my repo where you can find complete information and files for implementing the custom USB setup needed to get the DROID TURBO 2 phone working out-of-the-box with ADB under Android Studio: <img src='https://chart.googleapis.com/chart?cht=qr&chl=https%3A%2F%2Fgithub.com%2Fmaxieds%2FAndroidADBExtraUSBConfig%2Fwiki%2FFirstBootConfigurations&chs=180x180&choe=UTF-8&chld=L|2' alt=''>. A link to the original image file (which should have been displayed in the above post) using the repo site is also provided as follows: <img src="https://github.com/maxieds/AndroidADBExtraUSBConfig/blob/master/images/idproduct-discrepancy-illustrated.png" alt="" />.