I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
keaukraine said:
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
Click to expand...
Click to collapse
Goto developer tools and enable usb debugging ADB on the ROM your using it should do the trick.........
There are no new ADB drivers the same drivers are used for all the ROMS.......:laugh:
keaukraine said:
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
Click to expand...
Click to collapse
Make sure your Motorola drivers are up to date. Just go to:
https://motorola-global-en-roe.custhelp.com/app/answers/prod_answer_detail/a_id/89881
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Related
when I install driver, the windows find the ADB Interface as my driver
but the guide says it should be Android Bootloader Interface
so what's the difference?
will the ADB just be fine when I in fastboot?
Adb is available when you boot android...
Either Recovery or the ROM itself with USB Debugging enabled.
ADB = Android Debug Bridge.
ABI is to connect with HBOOT (similiar to PC BIOS) and not Android (the OS).
DoomFragger said:
Adb is available when you boot android...
Either Recovery or the ROM itself with USB Debugging enabled.
ADB = Android Debug Bridge.
ABI is to connect with HBOOT (similiar to PC BIOS) and not Android (the OS).
Click to expand...
Click to collapse
got it ,thx ~~~
proxylullaby said:
when I install driver, the windows find the ADB Interface as my driver
but the guide says it should be Android Bootloader Interface
so what's the difference?
will the ADB just be fine when I in fastboot?
Click to expand...
Click to collapse
When you see the ADB Interface as your driver, right-click on it and you will go through the process of selecting the new driver. If you are following Allgamer's guide, you can pick up around the step where he tells you to right click and select update driver software. HTH
Every time I try to update the drivers, I pick Android Bootloader Interface from the three options, it installs, and then says it has finished installing driver software Android ADB Interface, not ABI. No matter how many times I try it, I can't get ABI to show up.
I've tried USBDeview, but I'm not sure exactly what I should be doing in there to get this problem fixed.
Any help would be appreciated...
anonymou38 said:
Every time I try to update the drivers, I pick Android Bootloader Interface from the three options, it installs, and then says it has finished installing driver software Android ADB Interface, not ABI. No matter how many times I try it, I can't get ABI to show up.
I've tried USBDeview, but I'm not sure exactly what I should be doing in there to get this problem fixed.
Any help would be appreciated...
Click to expand...
Click to collapse
I did it anyways, even though it wasn't showing Android Bootloader Interface and it worked fine.
I've been trying for quite a while to get my Infuse to talk to ADB, still with no success.
I'm running:
PC:
Windows XP (32-bit) SP3
Samsung drivers from the AT&T website (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)
Infuse:
Firmware: 2.2.1
Baseband version: I997UKCH1
USB debugging turned on
No matter what I do, I get a Code 37 from the SAMSUNG Android Composite ADB Interface. (It shows up under "ADB Interface" in the device manager, but I get "Windows cannot initialize the device driver for this hardware. (Code 37)".)
If I disable USB debugging, I can mount the device with no problems in Media player mode or Mass storage mode.
I've also tried with the Kies package drivers and the Samsung driver from PdaNet, still with no luck.
I can debug an emulator session with no problem - just not the actual device.
I started with the guides here:
http://forum.xda-developers.com/showthread.php?t=1388644
I've tried the instructions for Epic here:
http://forum.xda-developers.com/showthread.php?t=1109374
and looked at the Galaxy issue here:
http://forum.xda-developers.com/showthread.php?t=1022272
I've tried with a Samsung-branded USB cable as well as a third-party one.
Any ideas what might be going on?
Do youvhave the android sdk installed? With the platform tools add on? Because adb is no longer in the sdk/tools folder of the android sdk ...its in the add on platform tools...then once installed you need to navigate to the platform tools to get advanced to work.
Sent from my SAMSUNG-SGH-I997 using xda premium
Yep, I've got the SDK installed - can run adb from the platform-tools directory, but it never sees my device:
C:\Program Files\Android\android-sdk\platform-tools>.\adb version
Android Debug Bridge version 1.0.29
C:\Program Files\Android\android-sdk\platform-tools>.\adb devices
List of devices attached
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
I believe you need the android usb drivers supplied by google to get it to connect. They can be downloaded using the sdk package manager. Also I'm not sure it will work having the Samsung drivers installed and you may have to uninstall them first.
they are installed already since i installed the whole sdk manager pack
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
ringnutz said:
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
thx for answer but I already done that..any other suggestions?
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
What drivers are showing up when you plug in the device? If it says Samsung then you don't have the android drivers installed. And I believe you can't have both installed only one or the other as only one will load when you plug in the device not both.
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
tzacapaca said:
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
Click to expand...
Click to collapse
When you plug the device in, under Device Manager in Windows, there should be listed Android Composite ADB Interface under the device. If not the Google USB drivers were not installed properly.
yeah I dont think my theme is the culprit, there are many reasons why ADB wouldnt show devices. Also Heimdall>Zadig is good for drivers.
run sdk manager and install latest google drivers as well.
are you on Windows OS?
nope,not your theme its the culprit..cuz i didnt install it and i cant install it cuz of no adb connection which is required by a tool named AutoDEOTool1.0.3
I installed latest google driver via sdk manager too..
yes,on Win 7 64 bits
*pulling hair*
I didn't have my usb cable yesterday to check it out but adb actually works with the Samsung drivers. Device Manager>Android Phone>SAMSUNG Android ADB Interface. And when I type the command "adb devices" it shows up. This works both if you plug the tablet in wihtout powering it up and when its turned on so I'm not sure what your problem is. I do have Kies installed on the laptop too so yours should be working if you installed the sdk and drivers correctly.
Which Tab do you have? I have the 6210 unlocked wifi only, it could be other models work differently. Not sure if you have a locked bootloader that you can access the tab through adb.
GT P6200 European
and here is what i get on cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tavi>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Tavi>adb devices
List of devices attached
C:\Users\Tavi>
EDIT:SOLVED!
Thank you all for answers
How did you solve this?
I input in cmd adb fastboot reboot and suddenly the device got the command and then recognized my tab..(pretty strange i know)
make it done
tzacapaca said:
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
Click to expand...
Click to collapse
do this steps:
1) remove battery
2)insert battery
3) connect the phone via usb will turned off and leave it till usb android phone installed
4) turn ur android phone on
5) wait for full boot
6) install Motorola usb driver .zip attached down there
7)select charge only mode
8) then write the commands of tacoroot.bin
9) when all is done hit the thanx button
ADB wireless
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Unitedforlife said:
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Click to expand...
Click to collapse
What do u mean adb wireless?
I've tried every single possible solution, and nothing works. I'm running windows 8, but all the drivers are installed. When in the rom, it shows under the device manager as a linux gadget usb device under disk drives. When in the bootloader, it shows up as "my htc" under android usb devices. I have no problems with fastboot, just ADB. I also noticed that ADB works when on a sense based rom. Can anyone help me with this? I'm on the latest cm 10.1 nightly. Nothing shows up under unknown device in the device manager by the way. Thanks for the help guys
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Unable to connect to usb
I installed Carbon-cr-5.1-moo-release-bacon-20180202-1444.
I am unable to get usb connection working and having tried many different things...
-I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
-In Android Studio SDK Tools I have installed Google USB Driver v12.
-I have developer options turned on and Android Debugging turned on.
-When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
- when I go into developer options and hit 'select usb configuration' my selection of mtp or whatever is always ignored and charging selectiomn remains
-Device Manager / Portable or Other devices does not have the phone beneathn it.
-When I run adb devices in cmd there are no devices attached.
-I cannot find a OnePlus One adb usb driver. I thought I found one but I have no way to verify and after installing it made no difference
I want to update to the latest rom in case this may be the cause, but after I download it to the phone and click flash
I just get the oneplus icon forever and the recover app twrp does not come up. It used to be there but then after I installed
the first rom after a couple of uses it disappeared for some reason or at least will not boot to it.
When I installed that first custom rom I folowed instructions for rooting and on completion it says to open up the installed
su app but when you open it it says there is a more up to date version but when you try to install that it fails.
Now all the apps that will not run if your app is rooted say it is rooted and all the apps that will not run unless it is rooted
say it is not rooted.
I think I need connection via usb in order to reinstall the twrp recovery app in order to install an up to date rom, hoping this may help
me solve the usb issue, but I cannot get the usb connection working as described above,
any hehlop would be appreciated.
Same Situation
hardya said:
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Click to expand...
Click to collapse
but my phone connects in edl mode just for 10 seconds and then automatic