ADB driver connection - Droid Turbo 2 Q&A, Help & Troubleshooting

Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?

rayjr13 said:
Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?
Click to expand...
Click to collapse
Yes but I know if you update to Windows 10 it can cause issues you need to reinstall moto drivers
Sent from my XT1585 using XDA Premium 4 mobile app

My Turbo 1 connect just fine not T2 I'll try it again when the wife brings it back

I had a small issue. I think mine cleared up when I installed Vysor, and installed the drivers through that.
http://koush.com/post/universal-adb-driver
Give this a shot and let me know how it goes. btw, Vysor is pretty fun.

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. )
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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
===== 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
Code:
lsusb
LSUSB Outputs: Bus 001 Device 0XX: ID 22b8:2ea5 Motorola PCS, where the XX is a decimal integer local to the running linux box
Click to expand...
Click to collapse
. After following the instructions at the referenced link, running
Code:
adb devices
from your favorite terminal should display the device. Now happy ADB and Android debugging to you and your ancient phone! (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="" />.

Related

Linux Window Manager on Android.

Do any of you think it's possible to run a full blown Window manager on our phones?
Not anything like gnome or kde, but awesome or lxde.
I have grown increasingly tired of all of Android's home applications.
Look forward to seeing comments
Well, I know you can run Debian Linux on our phones... I don't really think there is a point though because our CPU isn't powerful enough to make it very functional. The Droid may have a chance, and the Nexus One or Evo probably could.
Our phones should be powerful enough. Awesome and similar window managers use very little cpu.
wow, I'm no where near able to answer your question but what an interesting idea!! That would be very cool!
Thanks to REGAW helping me learn I used my new gnome bootable usb last night, how cool!!
Only downside is it doesn't save ANYTHING from the session, I'm going to partition some space for it on my hdd
id love to see ubuntu ported to our heros. the tp2 users have it, why not us?
I'd say Ubuntu is a bit too much I think a Debian port would be much more friendly.
Now that I think about it, I wonder if gentoo could be compiled on the phone and used as a phone.</off topic>
This topic is about running a *Window Manager* on the phone, not another operating system. I was reading about Android on the Wikipedia page earlier, and I read that there was no X support, so I dont think it would be very easy to get it working :/
Some of those manager are deathly simple. I guess they could potentionally be ported.
if you were running one of these overclocked roms would this change anything, I found this elsewhere, I didn't write it, you may have read it before:
OK, here's howto get Debian up and running on your HTC Hero running the MoDaCo Custom Rom 2.9:
1. Download this archive:
androidfanatic.com/cms/unofficial-app-repo.html?func=fileinfo&id=21
2. Extract the archive, resulting in a folder 'debian'. Inside this folder
replace 'installer.sh' and 'bootdeb' by the files provided with this howto.
Make sure they are replaced, delete the old ones first!
3. copy the folder 'debian' to the root of your sdcard. The root is the highest level, e.g.
drive E:\ if you are on a windows pc. Unmount sdcard on pc and phone.
4. Download ConnectBot from the market. See included QR-Code for use with Barcode Scanner app.
5. Start ConnectBot and open a local shell. To do so click on the drop down menu on the lower left
that says 'ssh' and select local.
6. As this is your first start of Debian you need to "install" it first. Execute the following
commands (press enter at the end of each line, always allow root access if asked):
su -
cd /sdcard/debian
sh installer.sh
bootdeb
At this point you are changing into the Debian environment. From now on do not restart
your phone or kill ConnectBot without executing 'exit' first. Now continue with commands:
/scripts/onetime.sh
exit
That's it, you are done! Now you can do whatever you want with your Debian installation.
7. To go into Debian from now on you use the following commands in a local shell in ConnectBot:
su -
bootdeb
You can automate that by passing these two commands as 'post-login automation' in ConnectBot,
long click the 'Local' entry in ConnectBot and edit the host.
Remember to leave with 'exit'! Alternatively you can click the trackball once and then press 'd'
on the keyboard. This resembles 'Ctrl+d', which is the logout command for unix shells. Do this
two times more to shut down the local shell in ConnectBot.
8. If you want to access your Debian by ssh execute the following command:
/etc/init.d/ssh start
9. To free some space in your image file execute the following command in the Debian environment:
apt-get clean
Do this also after every usage of 'apt-get upgrade' or 'apt-get install'.
10. For additional information here is howto resize your debian.img (for Linux only):
androidfanatic.com/cms/community-forums.html?func=view&id=1610&catid=9
And see here howto install a graphical desktop enviroment, in this case lxde or icewm:
(Note that i had to resize my debian.img first!)
wiki.lxde.org/en/Android
I'm not going to quote the entire post
@tmachovec: thanks for the info, but I'm looking to see if we can actually run it on the phone. Not connect to a fake X11 server over local ssh. I appresicate the input. But I'd like to run this on the phone
http://www.gentoo.org/main/en/where.xml
Gentoo has an ARM build, so it's possible.
noidea` said:
I'm not going to quote the entire post
@tmachovec: thanks for the info, but I'm looking to see if we can actually run it on the phone. Not connect to a fake X11 server over local ssh. I appresicate the input. But I'd like to run this on the phone
Click to expand...
Click to collapse
Gnome, KDE, IceWM or LXDE Desktop on your Android! 1 Year, 2 Months ago Karma: 9
IMPORTANT UPDATE: Many comments on sites that have blogged this post seem to be getting the wrong end of the stick. This is not connecting to a remote desktop on another machine! This is x11 and LXDE Desktop running LOCALLY on the G1 device, the reason I had to connect back to LOCALHOST using VNCViewer (also running LOCALLY on the device) is because there are no drivers available. This circumnavigates the need for any special drivers.
Now back to business!
It's official you can run X-Windows and your choice of GUI (Gnome, KDE, IceWM etc on an Android device!
Screenshots are below!!
androidfanatic.com/community-forums.html?func=view&catid=9&id=1620#1620
wow im lost in all this (NOT linux savy)
what does this mean?
Ok, so I've been trying to do this and I can never manage to get it working. When debian boots, it gives me an array of errors, but its too quick to reboot so I can't read whats wrong. I'm 99% sure it has something to do with the image being read off the sdcard. I read the installer script and manually moved all the necessary files because the script would not do it.
Yes, I ran everything as su
Has any one else had problems with this?
Thanks tmachovec
Any one have info on my problem?
I couldn't get it to load either, same problems with getting Debian to boot. I know a little about linux but not enough solve these issues.
noidea` , I have no idea.
just wondering has any one been able to do this successfully on their Hero's?
noidea` said:
just wondering has any one been able to do this successfully on their Hero's?
Click to expand...
Click to collapse
Have you tried doing some of the stuff from this site
http://android.modaco.com/content/htc-hero-hero-modaco-com/292093/debian-lenny-now-running-on-hero/
Its the gsm htc hero.. Different phone, but some of the stuff might definitely apply.
Heres a post I made after i got it to work
http://forum.xda-developers.com/showthread.php?p=6438126#post6438126
I GOT IT WORKING
here is a screen shot.. Im willing to do any kind of screen shot to prove it
Ill zip up my exact files that I use and the simple command to get it up and running.
Ill open up something and type my name and post a screen shot in a bit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[GUIDE] Fix ADB USB driver for Rockchip RK3066 - Ployer Momo7 Dual Core

I am struggling to make my USB debugging works for Momo7 dual core with RK3066 chip. This is what I found to make it works at least for my Windows 7 64bit. This should be the same with other RK3066 devices also.
1. Install ADB driver
After connect to USB (make sure USB debugging enabled and don't mount the mass storage device) You will find that MOMO7 is not recognized in the Device Manager. The simple way is to install Moborobo, it will find and install a driver for you.
If you dont want to install Moborobo, you can use standard adb driver comes from SDK but you need to edit the android_winusb.inf file to add
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
in both Google.NTx86 and Google.NTamd64 area.
For other model and manufacturer, just change the VID and PID which you can get from Device Manager > Properties > Details > Hardware Ids.
2. Use suitable ADB
Using adb from Android SDK is not working for some/almost RK3066 device (I think). I tried a few adb embedded from the other application like SuperOneClick but not working. No device found if you run "adb devices". I almost giveup but suddenly adb from ROOT.bat here contain is the only adb that can see my device.
Credit goes to bindassdost to point to the adb in the first link here
and yuvarajv to mentioned the adb embedded in root script contain ROOT.bat here
Root Momo7 & Momo8 Dual Core
The Momo7 & Momo8 using RK3066 can be root by using a Chinese program ZhuoDaShi. http://www.dashi.com/
Thank you for posting the solution for adb. I am using Cube U9GT4 tablet. I was also having the same problem of device not getting listed. But now I am able to use the adb.exe from your zip. Thanks again ... :good: :good:
Thank you. This worked for my MINIX Neo G4 with an uncommon pid.
btw, you needn't install the sdk or usb drivers at all or go through that driver modding thingy, the pdanet drivers also work out of the box
thank you very mutch !!! it works for me and my rk3066 China tablet !!! now ADB work
Thank you, it worked with Qware TB-1517 :good: (RK2926)
had very similar problems with the timingpower Mini PC RK3066. I could not get the USB driver to install no matter what I tried (Win 7 both 32 and 64 bit)
Moborobo worked for me but I did not like the way it installed (and kept installing) Moborobo apps on my device - particularly as it had access to a rooted device under adb.
I will now do a full reset, restore my original ROM and try the alternative adb method described in the first post.
I am probably being over cautious but you can't be too careful these days!
htc6500uk said:
had very similar problems with the timingpower Mini PC RK3066. I could not get the USB driver to install no matter what I tried (Win 7 both 32 and 64 bit)
Moborobo worked for me but I did not like the way it installed (and kept installing) Moborobo apps on my device - particularly as it had access to a rooted device under adb.
I will now do a full reset, restore my original ROM and try the alternative adb method described in the first post.
I am probably being over cautious but you can't be too careful these days!
Click to expand...
Click to collapse
Hi there.
I've found another way by installing the Rk30XX driver from BQ, :
https://s3.amazonaws.com/Drivers/ADB_drivers_RK30.rar
1- Extract the folder and you will have a folder "bq edison" with two folders inside (tools and usb_driver).
2- Unninstall previous drivers and install the usb_driver from this folder, using device manager.
3- Go to folder tools, that contains patched files (adb and dll's) and copy them. Take note to their names
4- Now go to the SDK_FOLDER\plataform_tools\ and backup the files with the same name that you copy on step 3 (just rename them... to something like adb.exe.bck)
5- Now copy the files and open a terminal, perform 'adb kill-server' , 'adb start-server' and 'adb devices' will show your ID device .D
This worked with a RK30XX device as well my Denver TAC70071 with an RK2928 chipset , since the USB vendor id and pid is present on the driver.
PS.: Sorry for my poor english
It works!
Dimitrico said:
Hi there.
I've found another way by installing the Rk30XX driver from BQ, :
(URL deleted, use above)
1- Extract the folder and you will have a folder "bq edison" with two folders inside (tools and usb_driver).
2- Unninstall previous drivers and install the usb_driver from this folder, using device manager.
3- Go to folder tools, that contains patched files (adb and dll's) and copy them. Take note to their names
4- Now go to the SDK_FOLDER\plataform_tools\ and backup the files with the same name that you copy on step 3 (just rename them... to something like adb.exe.bck)
5- Now copy the files and open a terminal, perform 'adb kill-server' , 'adb start-server' and 'adb devices' will show your ID device .D
This worked with a RK30XX device as well my Denver TAC70071 with an RK2928 chipset , since the USB vendor id and pid is present on the driver.
PS.: Sorry for my poor english
Click to expand...
Click to collapse
Hi Dimitrico,
This works with my DFP1008R china noname tablet with RockChip RK2918 and Android 4.0.3 too!
Tried lots of ADB drivers, but the key is special adb.exe from this pack!
how to avoid windows 8.1 security warnings ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, Finally got ADB working on my JXD 7800.
I kept thinking it was the driver turned out to be the ADB build.. what makes this one special?
eh.. anyway now how do I get fast boot running? anyone know of a special build of that?
I suggest use auto installer for win 7/8
http://minix.com.hk/downfile/RK_DriverAssitant.zip
for rooting "Uberizer":
http://www.techknow.me/forum/index.php?board=154.0

[GUIDE] adb and fastboot drivers for Windows

If someone has problems installing the official Motorola adb and fastboot drivers for Windows, try the following, this works for me:
1. download the UniversalADB driver from @Koush here: https://github.com/koush/UniversalAdbDriver
2. install it
3. locate the file android_winusb.inf in the folder (may vary) x:\Program Files\ClockworkMod\Universal Adb Driver\usb_driver
4. open it with any texteditor
5. add the following two lines (somewhere in the devices section) and save the file:
Code:
MotorolaADBInterface = USB_Install, USB\VID_22B8&PID_2E76&REV_0228&MI_01
MotorolaBootLoaderInterface = USB_Install, USB\VID_22B8&PID_2E80&REV_0100
6. let Windows install this driver from koush's directory once in adb mode and once in fastboot mode (two drivers!)
7. enjoy!
Work fine thanks
Is the phone recognized by RSD Lite in fastboot mode with these drivers?
I have the Motorola drivers, using Windows 7 SP1 32-bit.
With USB debugging enabled I get a "Mot Composite ADB Interface" device in device manager (Driver Version 2.0.1.0).
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
t-bon3 said:
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
Click to expand...
Click to collapse
Got the same with the universal ADB/fastboot drivers damn.
[edit]
The MotoG PID is missing in PST.ini and/or sdk_common.ini, maybe we have to add it manually or wait for a new RSDlite
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Worked great. Thank you
maty3ux said:
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Click to expand...
Click to collapse
Not yet, last version is 6.1.6
I do not understand this instruction:
shaftenberg said:
let Windows install this driver from koush's directory
Click to expand...
Click to collapse
Windows doesn't attempt to do anything when I connect the phone in ADB mode. Device Manager lists XT1034 under Other devices and says "The drivers for this device are not installed. (Code 28)". If I do "Update Driver Software" manually and direct it to the "ClockworkMod" directory, Windows says it cannot find driver software for the device. If I right click on the "android_winusb.inf" file and choose Install, Windows says the "file doesn't support this method of installation".
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Thank you!!
it works for me
i installed Motorola device manager and this application
reversegear said:
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Click to expand...
Click to collapse
that's right .. i didn't do that too and it works
I've tried this and when I try to install it, it says "The INF file you selected does not support this method of installation." What do I do?
Didnt work for my moto g
sir, i am really new at this backup thing.
i just want to backup my injustice save game, so that i can restore it to previous point if something goes wrong.
i downloaded latest version on universaladbdriver but still my laptop didnt recognised my MOTO G.
i want to use HELIUM/CARBON for backup and i cant proceed till this problem is removed
please help me, i am new to xda as well.
THANKS
my os is win7 32 bit
hey
same problem i cant install adb or motorola drivers in my pc windows 7 64bit. the links with drives dont work for me..any solution? i want to unlock my bootloaderrrrrrrrrrrr :silly::silly::silly: (when i start to install the adb drivers stuck )
https://www.youtube.com/watch?v=RDA8PpPSFuk here i found solution for me i hope u help guyz(turn the music off )
Gronnd said:
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
Click to expand...
Click to collapse
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
nuri-d said:
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
Click to expand...
Click to collapse
To solve this when u are in ADB go in device manager, find ur phone with yellow exclamation mark ( !), right click, insta driver-> manual-> android single sooner ADB interface! It will work like a charm!
Sent from my XT1032 using XDA Free mobile app
I had a similar problem on W7 x64, no driver available for my phone (Moto G LTE, XT1039) even with the Universal ADB driver from CWM and the two lines of the first post added in the INF file.
But, you can notice that all Motorola phones in the android_winusb.inf file refer to the same driver : MotCompositeInterface.
So I went to the Device Manager, found my phone, chose to Update the driver, Find a driver from my computer, Choose from List (sorry if the names are not accurate, my Windows version isn't in English).
Then, you can select ClockworkMod, scroll down to Mot Composite ADB Interface and choose it as your driver.
It worked for me (both in adb and fastboot mode), I was able to unlock my bootloader and flash a recovery using it.
Hope this helps !
Hi, I tried all the solutions in this post unsuccessfully, but I found one here: stackoverflow.com/questions/22217792/android-moto-g-mobile-doesnt-show-in-the-devices-list-of-eclipse
that is the simplest and the only one that worked for me.
Download 'Adb Driver Installer' from here adbdriver.com/downloads/
after this connect your Moto G and start the AdbDriverInstaller.exe it will list your device and then press install.
Click to expand...
Click to collapse

[Guide] Fix for device not working in fastboot / unable to install official driver in Windows 10 / 11

If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.
I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.
Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.

How To Guide [Guide] Make Cisco-Linksys USB200M Ethernet Adapter work in Windows 10

Compact USB 2.0 10/100 Network Adapter Windows 10/11​
Foreword​I recently found this compact network adapter lying around somewhere. It's an older network adapter for sure (100mbp/s max), but why throw it away instead of using it? There is just one mayor catch: it won't work in Windows 10 natively. (Download link at the end of article)
How to make it work in Windows 10 (guide)​Since Linksys didn't update the driver to 64bit, it doesn't match to a modern OS like Windows 10 or 11 (latest driver for Windows Vista 32-bit, Windows 10 32-bit doesn't work as well). Windows doesn't run 32-bit drivers on 64-bit operating systems. So instead of downloading the device driver (Linksys USB200M), I searched the internet finding out, which Ethernet controller is used. It turns out that it is a AX88772A controller. On the manufacture site of the AX88772A there is a driver available to download. Once you downloaded (unzip first), head to the device manager. Find the unknown device, right-click and select update driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select Browse my computer for drivers. Then choose Let me pick from a list of available drivers on my computer.
Search for Network adapters (tip: press "n" to jump to letter first n record). Open it. Now, instead of searching manufacturer (it wont work), simply choose Have Disk.
Now browse your downloaded driver folder and find a .inf file. Search for a entry called AX88772A. It might work with the non-A variant, but I selected this one.
Click next and accept the warning. The driver will be installed and you'll receive a success message.
After a optional reboot (I would recommend), the network adapter is ready to go.
A device named ASIX AX88772A Fast Ethernet Adapter appears in device manager under Network adapters:
Download link​----------------------------------------------------------------
>>AX88772A information page<<
>>Windows 10 (64-bit) AX88772A driver download<<
>>Windows 10 (32-bit) AX88772A driver download<<
----------------------------------------------------------------
I hope this helped!
I just found my old adapter, too. Which version are you using (mine is USB200M ver. 2.1)? I can't seem to get it to work. Windows is telling me that there are no compatible drivers for my device even after selecting the correct folder.
nm3th said:
I just found my old adapter, too. Which version are you using (mine is USB200M ver. 2.1)? I can't seem to get it to work. Windows is telling me that there are no compatible drivers for my device even after selecting the correct folder.
Click to expand...
Click to collapse
It turned out that my guide was incomplete. Let me know if it worked. Thanks for your hint & have a nice day!
doxtsgaming said:
It turned out that my guide was incomplete. Let me know if it worked. Thanks for your hint & have a nice day!
Click to expand...
Click to collapse
I finally got some time to take another shot at this and your updated guide works great. Thanks a lot for putting this together.
Thank you very much. Helped a lot.
OKN_ said:
Thank you very much. Helped a lot.
Click to expand...
Click to collapse
I'm glad it helped
doxts said:
Compact USB 2.0 10/100 Network Adapter Windows 10/11​
Foreword​I recently found this compact network adapter lying around somewhere. It's an older network adapter for sure (100mbp/s max), but why throw it away instead of using it? There is just one mayor catch: it wont work in Windows 10 natively. (Download link at the end of article)
How to make it work in Windows 10 (guide)​Since Linksys didn't update the driver to 64bit, it doesn't match to a modern OS like Windows 10 or 11 (latest driver for Windows Vista 32-bit, Windows 10 32-bit doesn't work as well). Windows doesn't run 32-bit drivers on 64-bit operating systems. So instead of downloading the device driver (Linksys USB200M), I searched the internet finding out, which Ethernet controller is used. It turns out that it is a AX88772A controller. On the manufacture site of the AX88772A there is a driver available to download. Once you downloaded (unzip first), head to the device manager. Find the unknown device, right-click and select update driver.
View attachment 5670405
Select Browse my computer for drivers. Then choose Let me pick from a list of available drivers on my computer.
View attachment 5670411
Search for Network adapters (tip: press "n" to jump to letter first n record). Open it. Now, instead of searching manufacturer (it wont work), simply choose Have Disk.
View attachment 5670417
Now browse your downloaded driver folder and find a .inf file. You can choose the first listed device as there are many others of the same type. Click next and accept the warning. The driver will be installed and you'll receive a success message.
View attachment 5670431
After a optional reboot (I would recommend), the network adapter is ready to go.
A device named ASIX AX88772A Fast Ethernet Adapter appears in device manager under Network adapters:
View attachment 5670385
Download link​----------------------------------------------------------------
>>AX88772A information page<<
>>Windows 10 (64-bit) AX88772A driver download<<
>>Windows 10 (32-bit) AX88772A driver download<<
----------------------------------------------------------------
I hope this helped!
Changes made
- 07/25/2022 misspelling corrected
- 07/28/2022 added screenshots modified text
- 02/23/2023 misspelling corrected
Click to expand...
Click to collapse
When I try to update the driver as instructed I get "Windows found drivers for your device but encountered an error while attempting to install them." followed by the name of the drive (same as your screenshot) and then, "This device cannot start. (Code 10)." Any suggestions or am I SOL?
LinusMandel said:
When I try to update the driver as instructed I get "Windows found drivers for your device but encountered an error while attempting to install them." followed by the name of the drive (same as your screenshot) and then, "This device cannot start. (Code 10)." Any suggestions or am I SOL?
Click to expand...
Click to collapse
Hi @LinusMandel
Have you selected the A variant of the driver (ASIX AX88772A)? That may have caused the error.

Categories

Resources