So here's the thing, my Nexus 5X, when loaded into bootloader and connecting to my computer running Windows 10, doesn't work with the official drivers. (https://developer.android.com/studio/run/win-usb.html)
It connects fine, and reports itself with the hardware id "USB\VID_18D1&PID_D00D", which is not present in the android_winusb.inf or any drivers included in windows. In fact, I couldnn't find *any* official drivers, not even from LG, nor "universal" drivers. Tools like "SKIPSOFT ANDROID TOOLKIT" (http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444) didn't help, either.
I did some research on google and xda, too, and couldn't find anything conclusive. Hundreds of people should have this problem, if the Nexus 5X isn't supported by the official adb/fastboot drivers. I'm honestly puzzled, as it seems that most N5X owners don'tr have this issue. What's "wrong" here?
I found the same.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
You can try the drivers in the attached post if you like. It should work fine on 32/64 bit windows.
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
I don't get it, what happens exactly when you try to run adb commands?
Shebee said:
I don't get it, what happens exactly when you try to run adb commands?
Click to expand...
Click to collapse
Same thing that happens if you ran adb commands with no device connected.
Shebee said:
I don't get it, what happens exactly when you try to run adb commands?
Click to expand...
Click to collapse
Well, without the right drivers, doing anything with adb is kinda pointless.
sfhub said:
I found the same.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
You can try the drivers in the attached post if you like. It should work fine on 32/64 bit windows.
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.
anon768 said:
These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.
Click to expand...
Click to collapse
I had even more problems on the Nexus 7 2013. Not only was adb not working, but neither were the MTP IDs being recognized so I had to "fix" them for myself also. Judging by the number of people that downloaded those drivers, other people had the same problems.
I don't know what the deal is with drivers and Nexus devices that I've used. I would have thought Nexus being a developer oriented device and with them being Google branded, drivers should be the last of my issues.
Perhaps everyone who uses Nexus and needs adb to work is savvy enough to search or fix themselves and Google doesn't get any complaints.
Also some people have installed "universal" drivers in the past, which may account for why they don't encounter issues with recognition as long as this isn't their first Nexus device.
sfhub said:
...
I don't know what the deal is with drivers and Nexus devices that I've used. I would have thought Nexus being a developer oriented device and with them being Google branded, drivers should be the last of my issues.
Perhaps everyone who uses Nexus and needs adb to work is savvy enough to search or fix themselves and Google doesn't get any complaints.
...
Click to expand...
Click to collapse
That's probably part of it. My guess is most developers use Linux or OSX (so they can develop iOS apps too) and simply don't have the driver issues that plague Windows.
anon768 said:
Well, without the right drivers, doing anything with adb is kinda pointless.
These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.
Click to expand...
Click to collapse
I use the Google drivers and they work fine.
On win10
Shebee said:
I use the Google drivers and they work fine.
On win10
Click to expand...
Click to collapse
Could you post the drivers and also their origin (ie came with win10, downloaded automatically by win10, downloaded with Android SDK, etc.)
Just the .inf file.
Related
Samsung Canada is a garbage website which has no drivers to download, only Kies. Installing Kies didn't work because my computer won't recognize the phone.
I also tried installing other random drivers for gnex found on the webz. None of them worked.
I was wondering if anyone knows of a good official driver for this guy.
Btw i'm running the non-verizon one.
convolution said:
Samsung Canada is a garbage website which has no drivers to download, only Kies. Installing Kies didn't work because my computer won't recognize the phone.
I also tried installing other random drivers for gnex found on the webz. None of them worked.
I was wondering if anyone knows of a good official driver for this guy.
Btw i'm running the non-verizon one.
Click to expand...
Click to collapse
Use these: http://forum.xda-developers.com/showthread.php?p=22915085
Sent from my Galaxy Nexus using Tapatalk
If you need the USB drivers so that you can use ADB and fastboot, you can install them in this. Just follow the instructions provided in there. I found it to be the easiest method to get them.
Tried both already. Didn't work. Comp still won't recognize my gnex is plugged into comp. Win 7 x64.
Then would it still be the drivers fault or my phones fault.
I have Win7 64 bit on both my laptops, no problem with recognition. I do however have the Android SDK + Google drivers installed on both machines; do you?
The drivers are shoddy. If you look under Device Manager while plugged in, it probably has a ! on the device. Manually update it, choose list from computer, and go under Samsung Android device or something like that.
I'm trying to install clockworkmod and root, by following the guide here:
http://forum.xda-developers.com/showthread.php?t=2022270
Everything is going well until I reboot into clockworkmod, at which point my computer fails to recognize the Nexus 7 for ADB, and I can't continue.
The weird thing is, after installing the ADB drivers from Asus' website on my Windows 7 PC, it connects perfectly in Windows. However, in clockworkmod, it just shows up in my Windows Device Manager with a yellow exclamation mark next to it.
Anyone knows what the problem might be?
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
manekineko said:
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
Click to expand...
Click to collapse
Thanks verrrrrrrrrrryyyy much guy. It solved my problem:
http://forum.xda-developers.com/showthread.php?p=46754283
You are awsome for share your knowledge.
Hey guys,
Just last week my Nexus stopped connecting to the PC. First it wouldn't even charge or show the phone in explorer.
I tried bending the connector back up and it started charging again. But it still won't connect in explorer.
Drivers shouldn't have changed but I've tried reinstalling and still nothing. Tried different cables, nothing. Tried different ports, nothing.
EDIT: I was trying to avoid it but I've tried a factory reset and reflash of PA2.99... still nothing.
So I'm a bit stuck right now. Anyone have suggestions?
Have tried searching and the like.
On a different note, possibly related. I bought a Nexus 7 today and tried to unlock and root. Fastboot drivers aren't working. Tried several different packages and methods. No dice. Followed instructions etc.
Thanks
Jenkss
Jenkss said:
Fastboot drivers aren't working. Tried several different packages and methods. No dice. Followed instructions etc.
Thanks
Jenkss
Click to expand...
Click to collapse
linux/windows/mac?
can you see your device in 'fastboot devices'?
can you see your device in 'adb devices', while running android or a custom recovery?
check if there's an updated version of fastboot/adb (not sure what OS you're using)
There seems to be quite a large percentage of these phones where the USB port breaks down. Mine was one of them. I had charging issues and my PC didn't recognize my phone. I still had a guarantee and I had it fixed.
Verstuurd van mijn Galaxy Nexus met Tapatalk
danils0n said:
There seems to be quite a large percentage of these phones where the USB port breaks down. Mine was one of them. I had charging issues and my PC didn't recognize my phone. I still had a guarantee and I had it fixed.
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
yeah, so it seems. mine still works, but i try to be extra careful with it, not using another person's usb cable (as paranoid as that may sound, i still don't like it :laugh
bk201doesntexist said:
linux/windows/mac?
can you see your device in 'fastboot devices'?
can you see your device in 'adb devices', while running android or a custom recovery?
check if there's an updated version of fastboot/adb (not sure what OS you're using)
Click to expand...
Click to collapse
64bit windows 7.
Tried with the latest adb/fastboot drivers.
Not recognized in either. Doesnt show up in any device manager.
The only way i know the phone has some form of connection is that the charging icon comes on.
Starting to think its the port that's broken some how. Bought the phone online back just after release so I doubt I'd be able to get a replacement.
Using airdroid at the moment to backup and transfer files around but thinking I might need to think about a new phone soon.
Jenkss said:
64bit windows 7.
Tried with the latest adb/fastboot drivers.
Not recognized in either. Doesnt show up in any device manager.
The only way i know the phone has some form of connection is that the charging icon comes on.
Starting to think its the port that's broken some how. Bought the phone online back just after release so I doubt I'd be able to get a replacement.
Using airdroid at the moment to backup and transfer files around but thinking I might need to think about a new phone soon.
Click to expand...
Click to collapse
I'm sorry to hear that, but IMO, yeah, i think you should start looking for a new phone. Don't keep valuable data on this one.
Same issue here. I just UPSed mine to Samsung under warranty. They better fix it, since it's their hardware issue. The phone support kept telling me they were going to reflash it. Good luck doing that without access to USB.
bk201doesntexist said:
I'm sorry to hear that, but IMO, yeah, i think you should start looking for a new phone. Don't keep valuable data on this one.
Click to expand...
Click to collapse
I was starting to think that would be the case.
Oh well, thanks for the replies everyone. There doesn't seem to be anything that I haven't tried to get it working. Unless I missed something. Doesn't seem like I did though from the replies so far.
When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.
And you've removed all drivers to android and lg for it.
secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.
Which version of windows are you running? On both desktop and laptop???
secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.
Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.
I have this phone at least for another year. So at least someone out here is still willing to help.
secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.