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

[Q] adb devices strange issue, not detecting

Solution:
If you were like me, you couldn't get ADB working no matter what you did with the drivers. As it turns out, I was plugging it into a USB 3 port on my motherboard. I have the USB 3 drivers installed, but there seems to be an adb issue with USB 3 ports. be warned, my issue is now fixed (I probably don't even need them bootleg drivers either). Thank You XDA.
Alright, so I just picked up a Galaxy Nexus (coming from Thunderbolt) today only to find out that my sdk will not detect my phone in adb devices. Now, I have the Thunderbolt and Eris working fine with it, but the NExus seems a little stubborn. Here are the steps I have taken:
1. Plug in phone, wait for win7 (x64) to install all the drivers... Success
1a. MTP and PTP both installed, using MTP for the rest.
2. Turn on debugging on my phone one more driver... Success
3. Went to the GNex Samsung support page to download and install that driver... Success
4. Go into Device Manager, everything is A-OK, drivers all happy
5. Open up my sdk prompt and type adb devices and 1 device is found, offline
6. Type it in again, nothing, maybe a glitch?
So there is nothing wrong in Device Manager, no Windows Updates, SDK works fine, but no device under adb devices. This is honestly the strangest thing ever.
If you have any special instructions regarding drivers, please be specific, stating "update your driver" doesn't really help.
Oh, and this is my first post I believe.

Update your drivers :laugh:
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it.
Srsly though...
If that doesn't work...try the PDAnet option.
My sig has a link.
Install PADnet and plug your phone in.
Then check that the new driver is the one in use.

@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.

efrant said:
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Noob question, but how do I install those drivers?

epicrevolt said:
Noob question, but how do I install those drivers?
Click to expand...
Click to collapse
Is that a joke?
efrant said:
[snip]
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse

Alright, so I have done the following:
Uninstalled all Samsung Drivers through Device Manager
Unplugged phone
uninstalled those official Samsung drivers for the GNex (available for download on their site)
Plug phone back in, both MTP and Nexus unknown
install the 1wayjonny driver... Success (It's now under Android Device in Device Manager)
adb still doesn't work... f*ck
reboot phone into fastboot (vol +/- & power)
install 1wayjonny driver... success
fastboot device recognized by 'fastboot devices' and commads work.
I believe the issue is with the MTP device as it is not recognized so therefore I can't access the phone storage. So far the only way I can get MTP working is by using the official Samsung driver, but that overrides the ADB driver by 1wayjonny (no way around it, even through uninstallation and choosing the 1wayjonny driver, Samsung one is more 'recent').
In the attachment you can see that the MTP device has no driver and therefore is unavailable.
Thank you so much for the help so far.
UPDATE: MTP Driver downloaded through Windows Update, divice still not showing up in adb. Actually when I first run adb devices after kill-server it finds the device as offline, but as soon as I type 'adb devices' again, it's gone. poof.

Cannot stop USB drivers from auto-installing

Hello,
I have searched the forums and Google, and was not able to find anyone else with this issue, so here I am.
I'm on Windows 7 x64 with a stock Canadian Galaxy Nexus 4.0.1 (yakjuux.)
I am trying to install GNex Toolkit and am unable to get past the first step. No matter what I try to do, any time I plug in the phone, it installs the default drivers.
Device installation settings are set to "never install drivers from Win Update." Phone is in development mode, I have removed Google Nexus from my devices (and checked the "delete drivers" box, though it doesn't even appear anymore), there is nothing for Samsung in Programs and Features, I have used USBDeview and there is nothing for Samsung/Nexus. I've tried using PDANet to no avail (I get error 103). I tried using "uninstall drivers" with GNTK, no dice (it seems to just remove a registry entry).
Any other ideas on how to make my PC install the drivers I want and not the default ones?
Thanks.

Read part A of this post.

efrant said:
Read part A of this post.
Click to expand...
Click to collapse
I have read that entire post and Bourne-nolonger's guide. Instead of showing up as "Android 1.0" device in Device Manager, my phone always shows up as Galaxy Nexus, with no yellow triangles or any other issues. (Yes, developer mode is enabled, and it seems to make no difference to how my computer responds.)
From Bourne-nolonger's guide:
"As soon as you enable this Windows will pick up a new device and it will attempt to install a driver - this will fail (or hopefully it will)." - mine never fails, it always installs drivers from somewhere. When I attempt to install new drivers to the Google Nexus device using UNK 0.7, Windows tells me that I already have the newest drivers.
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....

Scarf Face said:
[snip]
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Click to expand...
Click to collapse
Absolutely.

Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
edit: tried doing the same in fastboot mode; the Device Manager recognized it as Fastboot mode, but did not let me install the proper drivers, saying that I already have the newest ones.

Scarf Face said:
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
Click to expand...
Click to collapse
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.

efrant said:
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
Click to expand...
Click to collapse
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.

Scarf Face said:
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Click to expand...
Click to collapse
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Click to expand...
Click to collapse
Seems to be a problem with my PC, so I will try it with a different machine. Thanks for your help!

Ignore this. Wrong thread.

Driver

What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!

mikoal said:
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
Click to expand...
Click to collapse
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.

themadproducer said:
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
Click to expand...
Click to collapse
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!

mikoal said:
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
Click to expand...
Click to collapse
If/when you need ADB (I don't use it) then just look around for ADB. I don't have a link for that.
When I first connected my S3 to my Win7, XP, 2nd XP machine, each one had an issue with the MTP protocol. This is what's used to transfer files to and from phone internal and external storage. I did my homework and massive experimenting and solved the issues. (pretty pathetic really) I just don't have a turn key absolute solution but here are some tips. Try one or all of these till it works...and it WILL!
(Backup your PC before attempting and use at your own risk)
XP
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in XP for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if not, download this and install
- if it's still not working, (which I doubt) then update windows. After the Samsung drivers are installed on some windows machines, windows updates provides a specific update that helps. I watched it happen/work on 2 machines.
- still not working, get ready....sounds crazy...but install Windows Media Player 11. It is tied into the MTP framework somehow. This is the version I used
Win7
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in Win7 for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if it's still not working, (which I doubt) then update windows. (remember to unplug/replug usb after.
- install wmp11 or higher
- if it's still not working, try this file (sorry...can't elaborate on it)
- STILL NOT WORKING...doubt it...but last chance, download this file and place it into c/windows/inf directory and reboot.

USB drivers for Mi 5s

I would like to connect ADB to my Mi 5s, but I don't know where to get USB drivers that are safe for download/install?
I need Windows 10 x64 drivers if possible...
Any pointers?

This tool should contain all needed drivers:
http://en.miui.com/thread-281979-1-1.html
Alternatively, if you use the full Android SDK it also contains the needed drivers (open SDK Manager.exe -> Extras -> Google USB Drivers).
I have the SDK installed and could connect with ADB while the mobile was normally running (and Debugging enabled in MIUI) and also while I was in fastboot.
This on Windows 10 x64.

patoberli said:
This tool should contain all needed drivers:
http://en.miui.com/thread-281979-1-1.html
Click to expand...
Click to collapse
This link seems to be for the Mi5 and not for the Mi5S? Doesn't that matter?
Otherwise I'm using Minimal ADB and Fastboot which is working with Google/Samsung Galaxy Nexus mobile phone. But if I try and connect Mi5S and start ADB Deamon running adb devices doesn't return anything.

Got it working. Thanks.

As far as I understood it, Miflash supports all Qualcomm based Xiaomi devices.
You have enabled ADB Debugging on the 5s? It's disabled by default. You have to enable first the developer options and then you can enable it. Here is the latest version of Miflash: http://api.bbs.miui.com/url/MiFlash but the site is down for me at the moment.
Do you see the Mi5s in Device Manager under USB Devices when it's connected?
I haven't installed Miflash, only the full Android SDK and it was automatically detected.
Here an alternative manual: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=409951&pid=7620087
Please note, you don't actually need EDL, but it nicely outlines possible driver issues and fixes.
[edit]
Damn and I wrote now so much text
[/edit]

USB Drivers
Yes, You may search on Google to get.

Xiaomi USB Drivers
Xiaomi USB Drivers For All Devices Download For Free

USB Drivers
literadesign said:
I would like to connect ADB to my Mi 5s, but I don't know where to get USB drivers that are safe for download/install?
I need Windows 10 x64 drivers if possible...
Any pointers?
Click to expand...
Click to collapse
Have you been wasting your time? it might lest you should get it.
Not better even the way has been downloaded by someone.

patoberli said:
This tool should contain all needed drivers:
http://en.miui.com/thread-281979-1-1.html
Alternatively, if you use the full Android SDK it also contains the needed drivers (open SDK Manager.exe -> Extras -> Google USB Drivers).
I have the SDK installed and could connect with ADB while the mobile was normally running (and Debugging enabled in MIUI) and also while I was in fastboot.
This on Windows 10 x64.
Click to expand...
Click to collapse
It take time to run.