Hi all,
I just bought a Galaxy Nexus and I'm having problems with the ADB port: my Lenovo w520 laptop running win7x64 simply does not detect the ADB device in device manager. I tried connecting the phone to my wife's laptop (HP running win7x64) and the ADB device is detected so it is not a problem of the phone or the cable. On my pc I only get the Galaxy Nexus MTP device and that is all.
It is not a matter of driver, there is simply no device detected hence it is not possible to send ADB command.
I do not know if it is related, but samsung USB mobile driver fails during installation without giving a valid reason.
anyone having similar problem ?
thanks
cheerts
So... how do you know its not a driver issue? Sounds like one to me. Have you tried manually installing other drivers?
Well, what is actually strange is that:
1) if I connect the phone to my wife laptop with USB debugging ON and no driver installed (it's HER pc, I cannot install my stuff), a composite device with two devices (MTP and ADB) is detected.
2) in fastboot mode, my laptop detects the ADB port and install proper drivers; using Galaxy Nexus toolkit, I can successfully list my device.
When the phone is fully booted, my laptop simply see only the MTP device. If it were just a matter of driver i would simply get an Unknown device in win7 device manager...
thanks
cheers
enryfox said:
Well, what is actually strange is that:
1) if I connect the phone to my wife laptop with USB debugging ON and no driver installed (it's HER pc, I cannot install my stuff), a composite device with two devices (MTP and ADB) is detected.
2) in fastboot mode, my laptop detects the ADB port and install proper drivers; using Galaxy Nexus toolkit, I can successfully list my device.
When the phone is fully booted, my laptop simply see only the MTP device. If it were just a matter of driver i would simply get an Unknown device in win7 device manager...
thanks
cheers
Click to expand...
Click to collapse
Eh. Fastboot is all you need. :thumbup:
Sent from my Galaxy Nexus using XDA
After several attempts (including installing win7 x64 in a virtual machine ...) I finally solved my problem: it was indeed a driver issue, my win7 did not automatically searched for proper driver (and the Samsung driver is available on-line in windows update). I forced a driver update for the MTP device so that windows downloaded Samsung driver and now both the phone and ADB port are detected and working. It is still a mystery why the driver provided by various tool-kit failed to install, but nonetheless the GNex is now fully set-up.
Actually the solution is so dumb that I feel a bit ashamed of myself...
thank
bye
Related
[FIXED]
For some reason Toolkit didnt work for me and i used this method to unlock bootloaders and root it.
http://forum.xda-developers.com/showthread.php?t=1362957
Also installed CWM recovery
------------------------------------------------------------------------
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
sukyman said:
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
Click to expand...
Click to collapse
I was facing lot of driver issues when connecting my GNex for the first time to the laptop on WinXP. Installing the drivers through the GNex Toolkit also did not work for me.
Finally what worked for me was, installing the latest version of Android SDK with the additional package of Google USB drivers, and then manually selecting the drivers after connecting my phone instead of asking Windows to look for drivers automatically.
I had trouble when first connecting my GNex too. However, these drivers worked for me (plus work with many many other android devices):
http://forum.xda-developers.com/showthread.php?t=1379875
If you have several android devices you'll find that you don't have to install multiple drivers for adb, fastboot, etc. for each of the devices.
Taken from post#3 of the ToolKit thread:
Note 1: If the driver doesnt install automatically then double click on the Android 1.0 item, then click on the driver tab and select 'update driver'. Select 'browse my computer' and then 'Let me pick from a list'. If no items appear in the list then untick 'Show compatible hardware' and find the Android adb driver or Samsung adb driver.
Try that as they may be on your pc and just not installing.
Mark.
Got them working now but i have problem when rooting, using GNex toolkit 5.6
It boots into android, i set usb debugging but when the phone is suppose to boot back to fastboot it gives error device not connected.
Ok so I have a rooted nexus 7 that won't show up as an mtp device ever since I rooted another nexus 7 on the same computer. I have uninstalled all the drivers and re installed them a million times with device manager and USBDview nothing works. It connects to other computers as an mtp device, however ever since I rooted the other nexus 7 on the same computer it won't work. Also I don't have access to the other nexus because it was my friends. Obviously it's a computer issue because it connects to other computers as an mtp. I'm really out of things to try as I have searched for this problem, but only found people saying to re install the drivers. I would really appreciate some help because I don't know what to do. Thanks.
bkbkaufman said:
Ok so I have a rooted nexus 7 that won't show up as an mtp device ever since I rooted another nexus 7 on the same computer. I have uninstalled all the drivers and re installed them a million times with device manager and USBDview nothing works. It connects to other computers as an mtp device, however ever since I rooted the other nexus 7 on the same computer it won't work. Also I don't have access to the other nexus because it was my friends. Obviously it's a computer issue because it connects to other computers as an mtp. I'm really out of things to try as I have searched for this problem, but only found people saying to re install the drivers. I would really appreciate some help because I don't know what to do. Thanks.
Click to expand...
Click to collapse
I also have weird issues. What I usually do is make sure the Nexus is configured for only one connection. So for MTP mounting I have PTP unchecked and USB debugging unchecked. Then I plug into the computer.
If it doesn't mount as MTP, I find it's usually because Windows has attempted to connect via ADB drivers. So I go into Device Manager and uninstall the device under "Android" while checking the box to remove drivers for the device. Then I unplug the Nexus and plug it back in, and it uses MTP drivers. I've always struggle with these driver issues for the Nexus, i don't know why it's so difficult. Good luck!
When I had issues with my mtp I had to uninstall adb drivers then plug my device back in so it would use mass storage and install the drivers. Somehow I have adb and mass storage working now with USB debugging on.
Check in device manager when you have adb uninstalled and see what your device comes up as.
Sent from my Nexus 7 using xda app-developers app
datallboy said:
When I had issues with my mtp I had to uninstall adb drivers then plug my device back in so it would use mass storage and install the drivers. Somehow I have adb and mass storage working now with USB debugging on.
Check in device manager when you have adb uninstalled and see what your device comes up as.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I uninstall the adb drivers but for some reason windows automatically installs them right back instead of mtp drivers and then if I go to update drivers and select mtp as an option it says it won't work
When I try to install the mtp drivers it says "Windows found driver software for your device but encountered an error while trying to install it...your device can't start" Then it automatically installs the adb drivers. What would be the reason it won't let me install the mtp usb drivers? Has anyone else encountered this?
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
hello guys, just bought that amazing watch today i have an issue. How can i connect it to my pc ? I plug in the usb, while sm3 is off. Win7 start to install and at the end it fails because of the drivers. So my pc doesn't recognise it. I can only see the "empty" E:/ Disk. Any suggestion ?
edit: unistalled the "watch" and then plugged in again and drivers get istalled. Now i have a "sony file-cd usb gadget" . help me pls
edit: wrong section :/ sorry
I have exactly the same problem.
i installed the Google USB Driver from theAndroid SDK Manager and also installed the Sony PC Companion. But the Smartwatch 3 still shows in the device manager under "other devices" without installed driver.
The only way i could connect to it is using ADB over Bluetooth which is really slow.
Anyone any idea?
i used these adb drivers http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
after installation, i went to device manager, update drivers, search pc for drivers, choose from a list of...., and then i selscted adb testing interface version 3.12.0.0
i had to skip the warnin popup, but adb is working fine
Thank you a lot.
i could not find any "adb testing interface" so i installed "Google Nexus 7 ADB Interface" from the list and so far it seems to work with that too.
Not sure why you have such a testing interface driver.
Did this HERE and no driver problem for me.
Drivers can be found in this folder : Program Files (x86)/Sony/Sony PC Companion/Drivers/
The Driver used in the bootloader is a different one. I have no issue there.
But it seems there is no actual ADB Driver used when the device is in normal operation mode for debugging apps or pushing apps directly over ADB on to the device.
Hi
ADK is working fine with my other devices, but my PC can't seem to install the drivers for Huawei Watch. The devices is in the device manager, but a little yellow triangle at the side, which means the device drivers are not installed.
I have tried Google, but the guides just say install the devices drivers but clicking update in Device manager with the xx file I downloaded, but windows can't see the file.
Thanks in advance
only pdanet drivers works for me for adb but in twrp i cannot connect to pc . how have you solved the issue i have same problem in device manager. tried more than 6 ways after googling pc
i've tried pdanet drivers 64bit on my win7 64bit version.
but the installation cannot continue.. did u success installing pdanet ? what version of your windows u have ?
why is this marked as solved because i dont see the solution. i just received my watch today and cant seem to get device manager to recognize any drivers.
PDAnet doesnt fully install because i cant install drivers
Minimal ADB and fastboot dont recognize any devices attached
Universal Naked driver 0.73 doesnt work even after modifying the android_winusb file
I even installed the Google USB driver from the SDK Manager, but i dont see anything on my machine.
ive had this watch for 2 hours and already frustrated as hell lol. can someone provide assistance?
thanks!
PS. im running this on Windows 7 64 bit and the watch is at LCB43B already
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
hendry said:
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
Click to expand...
Click to collapse
i was trying all day on my work computer which runs windows 7 x64 with no luck, but the watch was detected immediately on my windows 10 machine at home. strange.
Success!
I fixed my issue! I had the same issue everyone here mostly had. I could unlock the bootloader, but I couldn't get the Fastboot recovery to work because the drivers were not detected by Windows 10, or my other Windows 7 machine. Both machines installed a standard version of Google Android device drivers and boot loader drivers, but they were not detected by ADB commands once in the bootloader.
First I went here to download all the drivers, but got stuck:
http://www.thecountrycaller.com/37260-how-to-unlock-huawei-watch-bootloader-and-flash-twrp-recovery/
So what I did was ran the commands to reboot to bootloader, then flash commands for the recovery, left my device plugged in. Then I went into the Windows Device manager, and looked for the Android or Adb drivers loaded. I double clicked the driver, and clicked on uninstall driver, and told windows to delete the drivers. I then unplugged my device (still in bootloader mode), plugged it back and in windows instantly detected the ADB flash commands and boom, TWRP recovery completed.
Hope this helps some of you.
this did not solve my issue ive installed the drivers and nothing over and over can someone help me with the drivers please
thanks
running windows 7
tried to install every driver possible
Weird as it may be, I managed to get Hwatch to connect to ADB via USB by installing the watch as a Motorola Android Sooner Composite ADB Interface - in device manager-update driver-select from PC-select from device list-android usb device-motorola
Is there anything what i can do when my classic watch is NOT recognized on both pc and notebook? I hear no sound, i can´t see anything in device manager...any help?
Hi I`m using the huawei 2 LTE version - can I take the same driven from here or will that cause problems ?
---------- Post added at 08:11 AM ---------- Previous post was at 08:09 AM ----------
Is this may be a real help https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/