I'm trying to get adb shell work w OB, but no device is showing up after "adb devices" command.
There isn't any "Android composite adb device" in the device manager, only
"LGE Android Platform Composite USB Device" (does not work width the android sdk drivers).
- No "Other devices" present (Edit: There is a couple - all of them are Bluetooth related)
- Latest LG USB drivers installed
- USB debugging turned on
- tried all 4 usb ports
- Win7 32bit
Disclaimer> Did not found any Q&A Topic in Optimus Black sub-forum
Serval driver rei stall and phone reboot solved the issue.
Thread sould be deleted.
Sent from my LG-P970 using XDA App
having little bit different problem - i do have LGE Android Platform Composite USB Device in device manager. Driver says it's 2.2.0.0 from 30.11.2010 by LG Electronics Inc.
But adb can't find any devices.
edit:
usb debugging somehow has turned off
Related
ADB stopped working on my desktop suddenly (It still works on my laptop) adb devices show nothing, and adb shell brings "error: device not found."
I've uninstalled the drivers and reinstalled many times, going over the process outlined here: http://forum.xda-developers.com/showthread.php?t=532719&highlight=adb+noobs
Running KingxKxRom 2.2 (Hero rom)
I've looked on the forums for people with the same problem, but their solutions didn't work for me. Example: stopping the adb.exe process, etc
USB debugging is checked.
Device manager shows:
Android Phone:
Android Composite ADB Interface
USBDeview shows:
Android Phone: HTC Android Phone USB Device
Android Phone: USB Mass Storage Device
Android Phone: Android Composite ADB Interface
Any ideas how to fix this?
What OS are you running?
On my computer?
Windows XP
Have you tried removing your usb drivers in the device manager?
This same thing happened to me. I just uninstalled all of the usb ports, and when I reset my computer it recognized the ports, and everything seemed to work again.
I installed the usb drivers for my nook as per the instuctions in this guide: http://nookdevs.com/NookColor_USB_ADB#Windows_XP.2C_Vista_and_7
It seems to have worked and in device manager "ANdroid composite ADB device" shows up under Android Phone.
But when i type adb devices when my nook is plugged in, i still dont get and devices there.
Im running 64 bit Windows 7 on an Intel Core i7 machine.
I couldn't get the ADB drivers to work via those instructions either. Luckily we have people around here that are MUCH smarter than I am.
http://forum.xda-developers.com/showthread.php?t=910008&highlight=adb+driver+install
Follow the instructions and install the software from that thread, worked for me great.
I am having the same problem here. It seems like everything is installing fine. I deleted the old usb mass storage device, installed everything, but then when I try to do adb devices, I get a blank line. No serial number. I then tried adb wireless, I connected using adb connect 192.168.2.4 and it said connect it was connected. I then ran adb devices and it spit back that it was connected to that ip address but it still doesn't give me a serial number.
This is what I get:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Sorry for the multiple posts.
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.
I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).
This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.
For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!
Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.
Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?
Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse
mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!
'fastboot devices' does not return anything
win10 says that driver isn't installed, manually tried to feed 'Google USB driver' from SDK package - no luck, Android sits with yellow warning in Device Manager
but it detects the device from recovery, adb sideload works and win10 correctly shows Android Composite ADB interface
tried on 3 different PCs, no luck with fastboot driver
any ideas?
You can try finding a machine with windows 7, it will probably find drivers right away