Develop Bugs

[Q] GNex ADB device not detected by my PC [fixed]

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

AT&T S3 not seen by ADB

Ok... i've gone through the steps in the one thread to get the phone rooted and everything without tripping the flash counter. At least the rooting with ODIN part. Been trying to flash CWM Touch for it, but for the life of me can't get the S3 to enter debugging mode over USB so that it can be seen by ADB to do so. I have Debugging over USB checked in the settings on the phone, i've rebooted the phone several times... it just never seems to enter debugging mode (or at least not like on my old Atrix 4G, where it actually told you in the notification bar that debugging was enabled).

It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.

gunnyman said:
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
Click to expand...
Click to collapse
I had installed Kies... tried hooking it up, still wouldn't list in ADB. uninstalled Kies, but kept the drivers installed. And i only mentioned the idea of it saying Debugging enabled when you connect the USB cable because my Atrix 4G said that every time from the get-go.

Also odd.... looked into the SuperUser app... and the log shows several allowed access attempts from "shell"... yet never seemed that way in ADB.

I had the same problem... try going in to the "services" settings and update the driver to Android ADB composite. Other than that, my suggestion is to make sure Kies finds the drivers for both Camera mode and USB mode by toggling the selection while plugged in to Kies.
Sent from my SGH-I747M using xda app-developers app

Your last resort would be to remove the drivers and reinstall them... Don't install Kies...

Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.

elementaldragon said:
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
Click to expand...
Click to collapse
It seems to be a driver issue, kies interfering, or a component is missing, or all of that, so I'd start your windows driver and software over fresh...
Uninstall Kies
Uninstall the drivers
Reboot
Install the drivers
Install the Java JDK (64bit has never worked for me, even though the drivers are 64bit)
Install the Android SDK
Use the Android SDK to get the Platform Tools and the Google USB Driver
than adb devices should show a phone
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
elementaldragon said:
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
Click to expand...
Click to collapse
sometimes ADB Devices returns nothing for me, but theres a phone there, it would say nothing connected or to some effect if it didn't find anything...

Yea... every time i entered "adb devices" in the Windows command prompt, it always said "List of detected devices" or whatever it says, but nothing would be there, and if i tried the command to install the recovery it would say it was not a valid directory or whatever. Didn't show up on Ubuntu either, but it still worked...

EDIT/UPDATE: I was using a USB 3.0 port which apparently ADB didn't like (though ODIN rooting on that USB port worked fine...). I switched to another USB port and suddenly it worked!
Sorry to resurrect an old thread but I guess it's better than creating a new one for the same purpose...
Doesn't seem like this was resolved and I haven't been able to get my S3 to connect to ADB. I'm running Windows 7 Ultimate 64 Bit.
I had this driver already installed:
ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0
I enabled USB debugging and it wouldn't connect. I installed Kies, still wouldn't connect. I uninstalled the driver and Kies and rebooted. Reinstalled "ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0", installed the Google USB driver, still won't connect.
I'm still not sure if I'm supposed to see any sort of notification in my bar showing that USB debugging mode has been executed but I'm definitely not getting anything like that.
Code:
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
891b0876 offline
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
List of devices attached

Yea, when i finally was able to use ADB to push a recovery onto my S3, it never actually showed up if i checked the devices in ADB Shell. Well... it DID, but not if i already typed the SU command before "adb devices".

hey guys
i have same problem i wanna adb my galaxy s3 rogers (att) i am trying to do the root no tripping flash counter so i got to the adb shell part
i dont know what else to do to make my computer recognize my phone ??
i installed sdk and extract/installed it in the c:\android folder of my comp i let sdk installed all the things it needs to took a while
so whats left? i have my phone usb connected to comp and debuging on i type adb shell it says adb is not recognized internal or external command???
do i need to have somthing open on the phone b4 openning command?
pleaaase help lol
thanks

You need to navigate to the folder where adb is actually located (platform-tools)

You don't have to use adb, you can use the same commands on terminal emulator

[Q] "adb devices" command not listing my Nexus 7 (2013) !

When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??

Tech2Yantra said:
When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??
Click to expand...
Click to collapse
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.

mdamaged said:
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.
Click to expand...
Click to collapse
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.

Tech2Yantra said:
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.
Click to expand...
Click to collapse
You're welcome, fwiw, if you follow my suggestions, you can make it so adb works in ptp and mtp, but if it's not important to you, then it's not dire.

sm3 driver

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.

OP3 not recognized on Win10

My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.

Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk

Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.

Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk

jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10

Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager

setup driver and try in twrp

A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.

Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.

jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.

peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.

http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.

i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .

You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs

update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.

I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3

jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580