Database Users

[Q] ADB not recognizing, please help

Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.

If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk

neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb

corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App

Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)

So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.

Problems with ADB

So I'm not a novice ADB user and have used it to root at least 5 or 6 phones. I'm attempting to root my kindle fire right now and running into problems. I built a new PC since the summer and never bothered to reinstall ADB. I just downloaded the Google SDK and from my memory that includes ADB and you can usually get it going from there. I read some tutorials on how to set it up but after following them perfectly I can't get it to even start the ADB server. Anytime I type any ADB commands in it says adb.exe not found or it not being a valid command.
Any quick advice?

Get_Out_and_Push said:
So I'm not a novice ADB user and have used it to root at least 5 or 6 phones. I'm attempting to root my kindle fire right now and running into problems. I built a new PC since the summer and never bothered to reinstall ADB. I just downloaded the Google SDK and from my memory that includes ADB and you can usually get it going from there. I read some tutorials on how to set it up but after following them perfectly I can't get it to even start the ADB server. Anytime I type any ADB commands in it says adb.exe not found or it not being a valid command.
Any quick advice?
Click to expand...
Click to collapse
Download Kindle Fire Utility...
http://forum.xda-developers.com/showthread.php?t=1399889
It has a batch file that will install the necessary ADB drivers and you'll find the fastboot/adb executables in the tools directory.

That's what I thought was weird. I ran the drivers.bat, it says they're all installed and I still can't start the adb server or communicate with it. And the kindle shows up as it's supposed to when the adb drivers are installed under devices.
PS thanks for the quick response.

Get_Out_and_Push said:
That's what I thought was weird. I ran the drivers.bat, it says they're all installed and I still can't start the adb server or communicate with it. And the kindle shows up as it's supposed to when the adb drivers are installed under devices.
PS thanks for the quick response.
Click to expand...
Click to collapse
That's a new one to me. I think the adb server should be able to start even without the device attached. Maybe your original SDK install went wrong and it did something funny to your system? Sorry... I got nothing.

kinfauns said:
That's a new one to me. I think the adb server should be able to start even without the device attached. Maybe your original SDK install went wrong and it did something funny to your system? Sorry... I got nothing.
Click to expand...
Click to collapse
Don't want to sound too simple, but have you changed to the directory that adb.exe is installed in before trying to run it?

Yeah I changed the directory. I got it up and running kind of but now when I try the adb devices command it pops up as "connected devices" with nothing showing under it. The kindle fire utility also shows the adb server as not running always. Odd?

This happened to me its supposed to show up as Android composite adb interface its just a problem in that .android hidden file
Sent from my R800a using Tapatalk

Sorry I dont have my laptop with me and this happened like 2 months ago so my memorys rusty
Sent from my R800a using Tapatalk
---------- Post added at 10:09 PM ---------- Previous post was at 09:53 PM ----------
my adb_usb.ini http://www.box.com/s/e74b32cff87b7c9363fb
http://www.box.com/s/d785bcc0969b7c0999f0 -androidwin.cfg
http://www.box.com/s/da267d41c04c6284f084 -ddms.cfg
http://www.box.com/s/242c14da6a4fa8f2664d -repositories.cfg
to use these click my computer then at the search bar on the top left type in %userprofile% make sure hidden folders are sshown go to the .android folder and put these files in their. if it still doesnt work try superoneclick connect your kindle and go to the advanced tab and click update drivers
if none of this works follow the first half of this tutorial-http://www.youtube.com/watch?v=f409qNgpzSA

jeffbud98 said:
Sorry I dont have my laptop with me and this happened like 2 months ago so my memorys rusty
Sent from my R800a using Tapatalk
---------- Post added at 10:09 PM ---------- Previous post was at 09:53 PM ----------
my adb_usb.ini http://www.box.com/s/e74b32cff87b7c9363fb
http://www.box.com/s/d785bcc0969b7c0999f0 -androidwin.cfg
http://www.box.com/s/da267d41c04c6284f084 -ddms.cfg
http://www.box.com/s/242c14da6a4fa8f2664d -repositories.cfg
to use these click my computer then at the search bar on the top left type in %userprofile% make sure hidden folders are sshown go to the .android folder and put these files in their. if it still doesnt work try superoneclick connect your kindle and go to the advanced tab and click update drivers
if none of this works follow the first half of this tutorial-http://www.youtube.com/watch?v=f409qNgpzSA
Click to expand...
Click to collapse
Thanks I appreciate the help. Once I get home I'll try this and report back on how it works. I'm glad someone else experienced the same problem a d got around it.

The youtube video did it for me. I appreciate the time taken to help point me in the right direction.

ADB Connection to The Fire HD

This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.

I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?

I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse

Thread Moved​
As the contains no development.​

How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?

androitri said:
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
Click to expand...
Click to collapse
from the notification area click on more , security , ADB on

ADB doesn't see my Kindle HD 7
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:23 AM ---------- Previous post was at 08:55 AM ----------
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
Well, I added the magic line you suggested, and this now works for me. I'm surprised that running "C:\android-sdk\tools\android.bat update adb" (the corrct directory for me) didn't fix this.
Ah well - so many things to learn. Thanks for your guidance.
Pat

tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
This didn't do anything for me. Any other ideas?

Driver install problem
dotvezz said:
This didn't do anything for me. Any other ideas?
Click to expand...
Click to collapse
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!

Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.

PMcHargue said:
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
Click to expand...
Click to collapse
USB hubs cause problems, just sayin'.
I went round and round with this until I decided to plug directly into the PC and avoid the hub. Worked perfectly.
---------- Post added at 05:37 PM ---------- Previous post was at 05:33 PM ----------
If you have tried everything and still no workie, make sure you aren't using a USB hub. ADB wasn't listing it as a device but yet I was able to see it in Device Manager and even transfer files to/from it. Once I eliminated the USB hub, all was well. ADB now sees it.

dburckh said:
This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
Click to expand...
Click to collapse
Thank you so much for this, I was fially able to get ADB to recognize my Fire and root it.

reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Mine was doing the same thing
Follow the link that the OP gives(i'll also post it)
Follow the instructions in BOTH the links below. The second link are instructions to get kindle fire add-ons(including usb drivers) for SDK.
https://developer.amazon.com/sdk/fire/connect-adb.html
https://developer.amazon.com/sdk/fire/setup.html#step6

I had the same problem, with adb, not finding my Kindle Fire. I downloaded the current Android SDK und used that ADB without changing anything. Works fine for me I also just copied the adb.exe in the same directory as rootqemu.bat and replaced the old one ( old ~159kb new ~796kb ).

Very helpful

Hello All,
I could use some assistance. I have ADB installed properly and the drivers for the Kindle Fire HD from this thread installed also. My issue is the Kindle Fire HD driver states:
Android Composite ADB Interface
The device cannot start (Code 10).
I am using the driver from 12/3/2012 version 1.2.0.0 and I get this error code if I have the Fire directly connected to the usb port on the pc or through the usb hub. Same issue over and over. Even if I attempt to use other Kindle Fire HD drivers.
Also, I have made the change in the adb_usb.ini file.

Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This ABSOLUTELY helped me! Was bangin' my head against the wall for a WHILE before I this little nugget got me going! THANK YOU!

My issue is fastboot takes commands but says flashing not allowed

Hi, I have no issue connecting to my Kindle Fire using ADB under Ubuntu using a USB cable, no drivers were needed.
However I'm trying to get ADB over WIFI to work, but I get "unable to connect to 192.168.1.234:5555"
Has anyone managed to do ADB over WIfi or is it not implemented on the Kindle Rom? Thanks

[PSA/FIX] Newest adb doesn't work on WinXP + 5x USB drivers that work

I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.

Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.

WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip

Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.

Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?

For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.

The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?

Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.

Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards

Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards

ADB driver woes

New laptop (to me) Dell e7470.
Win7 x64
Phone: XT1575
Installed:
MotorolaDeviceManager_2.5.4
MotoHelper_2.1.32_Driver_5.4.0
Motorola_End_User_Driver_Installation_6.4.0_64bit
(also tried Kushik Dutta universal adb driver from 2013)
No adb driver detected or found when all the other drivers install fine when plugging in the phone
I've tried multiple usb cables, but this all works fine on my other computers.
If reboot to fastboot Motorola ADB driver is found and installed
But no adb driver when in rom
I've done this successfully for years, first android device many moons 2008ish
I dont know why this laptop is giving me troubles, or maybe i'm just gettin old and forgot a basic sequence or step to success.
Thanks for any ideas, its got to be something dumb.

You need to turn on usb debugging - developer options.
Minimal adb & fastboot installed too.
Dev.opt. - settings - infi about phone - tap few times compilation number. @eigerzoom
What for do you need adb if fastboot works?
MDM is all you need for drivers.

I have adb debugging enabled
I apparently need it for tethering, since that isn't working.
Works just fine on my other win7 asus laptop.
Any other ideas?
it feels like windows is missing something, but its hard to feel a computer

Run cmd and type:
adb devices

I've done that, thats how i test it.
its blank
actually i test it with 'adb usb' which gives error: no devices

File transfer works?

how would it transfer files if no device is found?
adb device shows up in device manager with an error

File transfer - mtp - not needed adb drivers. From notification bar you can change/enable when connected.
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Error in win dev manager - rpm - update driver - choose from installed.
Find & choose "adb device".

I'll test it soon, sorry
Also in developer settings you can choose usb configuration mode
if I cycle through them all
All drivers get recognized except in 'audio source' mode xt1575 no drivers install, and in 'rndis usb ethernet' no adb drivers install

I haven't Windows english version - I don't know names.
So I suggest:
Uninstall all Android programms(apps) & drivers from pc, restart pc.
Install and run MDM, when it finished connect Moto with debugging on, allow the connection on Moto(it should ask itself) .

Anyone else???

eigerzoom said:
Anyone else???
Click to expand...
Click to collapse
No try what @dzidexx suggested, before asking for someone else! Especially since his solution isn't hard to try out and see if it works!

I've done all that....obviously....
ANYONE ELSE ???

something tells me i have to install a stock rom to get the adb driver to install
and then it will work fine installing other roms after that
running LOS13 currently
i've run into this in the distant past on pre 2010 devices
anyone else with ideas?