Howdy,
Ok, I'm one of those who are having issues connecting my Nexus 6P to my Windows 10 PC. I've tried the usual fixes (I'll enumerate what I've done below) but right now where I'm in the state where Device Manager shows the Nexus 6p under the Universal Serial Bus controllers. Shows up as:
Unknown USB Device (Device Descriptor Request Failed)
Device status is:
"Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed."Properties -> Details -> Hardware Ids = USB\DEVICE_DESCRIPTOR_FAILUREOk, what I have tried:
1) Settings -> Developer Options -> Select USB Configuration = MTP (I have tried all options here, no change to above)
2) Settings -> Developer Options -> USB debugging = On (I have tried both on and off)
3) Using the USB A to USB C cable which came with the phone
4) Tried multiple USB ports on multiple PCs, no difference
5) NOT seeing the USB configuration type in the notification pulldown so I can not comment on that
6) I have factory reset the phone
7) Tried to update to the latest Google USB Driver.. Unable to... Experience is:
- Steps performed: Device Manager -> Update Driver Software -> Browse Computer -> Navigate to Directory (yes, include subfolder is checked).
- Outcome: Windows tells me the Best Driver software is already installed- Second attempt: Device Manger - Update Driver Software -> Browse Computer -> Let me pick from a list of device drivers
- Outcome: No driver with Android, Google or Nexus shows8) I have tried a couple of the universal USB drivers but none look to work
Is there anything else I can try? I am starting to wonder if there is a hardware error on my phone.
I have windows 10 and I've never had problems. When I plugged in my device my computer recognized it right away.
Sent from my Nexus 6P using Tapatalk
Have you tried to install ADB with the universal installer found somewhere on XDA, which also installs the Google drivers and see if your device is detected?Can you try it on a different PC to rule out the cable being problematic?
Might go down the path of updating the drivers for your motherboard. Especially USB 3. I've had that same error from outdated drivers on windows 8.1 and the htc m7. I actually had to use drivers from a different manufacturer but for the same chipset.
Went on vacation shortly after the last response and trying the suggestions now. Still no luck. I am starting to wonder if there is something shorted out on the phone. Is there any way to do a sanity check?
Since the last response I have tried:
Repeated the behavior on 2 different PC's
Updated all firmware on my laptop. I have connected a Moto X to this laptop in the past but do not have access to that device anymore.
Tried the Naked Driver
Tried the PDANet driver
Ran through the steps on the Diagnosing USB Driver thread
I have only tried this with 2 cables. One is the cable the phone came with. The other is a cable that Leung says does not work correctly (bought before I saw him reviewing. wondering if this did damage to my phone)
Anything else I could try? That or is there a way to test the hardware?
Related
I have used Nexus Root Toolkit twice successfully on two different computer, but on both occasions that has left the computer unable to connect to the Nexus 10 outside debugging mode.
I think it is "Step 1" in the driver install guide that tells me to:
2.) Launch Device Manager using the button bellow.
- Identify whatever device resembles your Nexus and right click it
- Select 'Uninstall'
- Check the box for 'Delete the driver software for this device'
- Select 'OK'
3.) Unplug your device and Launch USBDeview using the button bellow
- Use USBDeview to uninstall any;
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- ... or ANYTHING else you see that resembles your Nexus.
- In particular look for devices with Vendor ID
- "18d1" or... "04e8"
- Simply right click these devices, and select the option to:
- "Uninstall Selected Devices"
Click to expand...
Click to collapse
After doing this i can no longer connect the Nexus 10 as usb drive or/MTP. If i connect it, it simply says charging, and the Windows device manager doesn't list any new devices at all. Its like it isn't connected at all. If i enable usb debugging, i can use Nexus Root Toolkit without problem.
The computer in question is running Windows 8.1, and i first installed the Universal drivers that didn't work, and then got it to work with RAW drivers.
I assume that something got uninstalled that shouldn't have been, but i don't know what. Any help is appreciated, i don't fancy reinstalling windows
Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Re
Hi Ghosta,
Are you using a USB 3 port? as i have had many strange issues with these the ports. The issue is caused by one of the intel drivers cant remember exactly which way but there is no easy way to fix this. If this is your issues i would try and find if you have a USB 2.1 port you can use or the Esata ports on laptops tend to be usb 2.1 inside...even though they dont look like it haha
Hope this helps
ghosta12 said:
Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Click to expand...
Click to collapse
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
peterk-1 said:
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
Click to expand...
Click to collapse
Thanks for the replies and suggestions. All shows up OK in device manager, the device is not password protected, and the laptop has usb2 ports. I had another try today, after connecting the nexus it shows up in my computer as a camera, labelled nexus 10, with the camera icon. When I click on the icon it opens a special folder, must be a camera folder and the camera and scanner wizard starts. After a while it detects the photos on the nexus ( I have loaded a lot on it via USB otg using flash drive ), but thumbnails of the photos are not downloaded as I usually see when I connect a camera. The wizard downloads photos back to the computer, but each photo is about 18 kB instead of the 2 mb they originally were. So it appears a connection is happening, but a very strange one. I don't like to be beaten on problems like this one, but searching the net has not given me any answers, and I don't understand the android system well enough to know what to try next.
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
peterk-1 said:
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
Click to expand...
Click to collapse
No PTP conection or MTP connection either. The Nexus also shows up in Device Manger under Imaging Devices when USB deugging is on, which is causing the camera and scanner wizard to start, although it doesnt work properly. When i disable it nothing happens at all. No idea where to go from here.
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
peterk-1 said:
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
Click to expand...
Click to collapse
Thanks for the suggestion, I had already tried that but I did it again just to make sure. It did not work for me.
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
capnkrunch said:
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
Click to expand...
Click to collapse
I used a program called usbdeview to uninstall every USB driver with an "android" or "adb" description which should have cleaned up my drivers? Then after reinstalling drivers I tried again no difference. I ran android-tools and can push and pull files to and from the computer and nexus, (from command line) so I believe I have eliminated hardware problems and software problems on the nexus. This leaves the computer, which works perfectly with my other android devices running 4.1.1.
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
peterk-1 said:
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
Click to expand...
Click to collapse
This info does provide me with some way forward. With USB , when connected ptp I have a nexus 10 USB composite device and a nexus 10 digital still camera connected with the green light in USB deview, and also a blank device name, connected, description android composite device with a purple light. I'm guessing purple means not working. But changing drivers does nothing to change the purple light. Switching to mpt gives an additional blank name Google nexus adb interface also with purple light shown as connected. All connected devices show vendor 18d1. Drivers tried 1) clockworkmod (supplied with skipsoft); 2) naked drivers 3) Google drivers. Any clues what to try next?
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
peterk-1 said:
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
Click to expand...
Click to collapse
I gave up completely on this, and connect via wifi using ES file explorer. I bought my wife a new tablet an Acer Aconia A1-830 and it has the same problems, impossible to connect via ADB, with exactly the same symptoms. Yet our phones connect via ADB without a problem, but both are Androild 4.1 or earlier and the tablets 4.2 or younger. Obviously an Android generated problem that arose when 4.2 was released and on which has no fix.
Hi
I am a new user for nexus 6p, For the first time I connected my device to Computer running windows 10 updated. My laptop didn't detect the usb and the driver is not installed properly, I tried downloading the latest usb driver but it didnt help , While searching for the driver folder it throws
Windows was unable to install your unkown drive
You can get the USB drivers straight from Google and try to uninstall/reinstall or download Wugfresh's NRT. There is very good driver installation tool and test to confirm you get both USB and fastboot drivers installed properly. Just follow the "Full Driver Installation Guide"
Tonyjaqs92 said:
Hi
I am a new user for nexus 6p, For the first time I connected my device to Computer running windows 10 updated. My laptop didn't detect the usb and the driver is not installed properly, I tried downloading the latest usb driver but it didnt help , While searching for the driver folder it throws
Windows was unable to install your unkown drive
Click to expand...
Click to collapse
Hi... Do you have ADB enabled in developer options? If you don't have developer options enabled, go in: settings>about phone and type 7 times on the build number, then go back in settings > developer options and enable "android debugging".
Plug your N6 on your computer, check your phone screen and allow press ok when it asks to "allow USB debugging".
Does it change something? Is your N6 recognized in device manager? Does the driver updates?
...
So My puter recognizes my phone fine....
Pop opened the configuration and General tab says:
This device is not configured correctly. (Code 1)
A service installation section in this INF is invalid.
To find a driver for this device, click Update Driver.
I try and update the driver using the "Let the puter search" feature and it finds one and tells me:
Windows encountered a problem installing the driver software for your device.
Windows found driver software for your device but encountered an error while attempting to install it.
MPE Device
A service installation section in this INF is invalid.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software.
This is all AFTER I downloaded the latest Google USB drivers and unzipped them.
Phone is set to MTP mode and debugging mode is unlocked and usb debugging is on.
No Go.
Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.
FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.
Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy
I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On
I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.
Same issue
Even I'm facing the exact same issue on my op5
dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.
I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....
Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk
try changing port (and remember to restart the pc)
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk
I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.
Since a few days my Redmi Note 7 can't be seen anymore by my computer (Windows 10). In Device Manager there's the yellow alert icon with the message "Unknown USB Device (Device Descriptor Request Failed)".
Attempts I've tried:
- Connect the cable into the PC's rear USB ports
- Connect the cable into another PC
- Update the drivers in Device Manager
- Uninstall / reinstall the drivers in Device Manager
- Manually install drivers from SDK Tools, Mi Flash and% windir%\inf (wpdmtp.inf)
- Enable USB debugging in Developer Options and select "Data Transfer" by default
- Dirty reflash MIUI (wiping data)
- Connect the phone in Fastboot and Recovery (OrangeFox)
- Use other cables (the official one and three more)
But the error persists.
Everything points to a hardware problem of the USB-C input (which I also tried to clean, but nada), although the phone charges regularly and it can also indicate a software problem.
Somewhere I read that I could try formatting (and not wiping) the data partition, and I will do it as a last resort.
Do you have any other clue before i bring it to repair?
Thanks!
Did you try disable digital signature driver on windows 10?
Google it
zpower said:
Did you try disable digital signature driver on windows 10?
Google it
Click to expand...
Click to collapse
Tried that too