Unknown USB device (Device Descriptor Request Failed) when in Fastboot Mode - Asus Zenfone 5Z Questions & Answers

Hi all,
I've unlocked my bootloader via the official tool and rebooted into fastboot, but I'm afraid my device isn't being correctly detected on Windows 10. I've tried multiple devices and multiple cables. The device comes up as "Unknown USB device (Device Descriptor Request Failed)" in Device manager, and under events lists "Device USB\VID_0000&PID_0002\7&192ea77b&0&4 was configured."
I know that's a generic VID & PID so I may manually need to set those values, but I don't know what the correct values would be for a Asus Zenfone 5z Z01RD, so I'm stuck unable to access the device via my PC.
I've got the latest version of Google Platform Tools, and I've re-downloaded and installed the drivers from the Asus Support page. Not had this issue in the past with my Zenfone 3...
I've also tried the following to no success: https://forum.xda-developers.com/t/...r-request-failed-fastboot-windows-10.3375320/
Appreciate any ideas or if anyone can provide the correct VID & PID!

Also posted to Zentalk, though they don't tend to get a lot of help there...

Got a response back at Zentalk, but they thought I was asking about the app rather than drivers...
Clarified with the following:
I've successfully used the latest version of the app and it's worked fine, as such the app is not the issue, rather than the 5z doesn't have accessible drivers when it is in fastboot mode, therefore it cannot be connected to via Windows 10. Without the correct IDs, it is not possible to update the device via Fastboot. If it is possible to get the correct VID & PID for a phone plugged in via fastboot mode, drivers, or both, it'd be appreciated. Otherwise I can try to get the VID & PID from the Zenfone 3 in fastboot mode, and hope they work for each other.
In the USB support files on your site titled "ASUS_Android_USB_drivers_for_Windows", inside the zip there is the file "android_winusb.inf", inside which there are records which tell Windows 10 which driver to use, for example:
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D05&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4DAE
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
None of these line up to my device. Because my PC cannot determine what the device is (error = Unknown USB Device (Device Descriptor Request Failed)) it allocates a generic VID & PID (USB\VID_0000&PID_0002), so I can't find out what driver to apply. I need to know the correct one so I can get it to recognise.
Click to expand...
Click to collapse
Fingers crossed I get an answer, but if anyone can just put there device into Fastboot mode, plug it into Windows and tell me the device instance path (the USB\VID_XXXX&PID_XXXX) part or what drivers they use, that'd be great!

Probably my final update. I've tried this on many different systems (apparently AMD Ryzen has issues, tried on Intel, AMD Ryzen and AMD FX), different USB-C cables, different OS (Linux Mint, Win7 and Win10), different drivers (Google vs ASUS vs My own modified ASUS hack), registry hacks. Nothing works. At this point I have to assume it's either a hardware issue or corrupted fastboot bootloader image, which is immensely frustrating when I can connect and transfer data fine via cable.
I've posted on damn near every forum possible, and hunted everything from "can I manually force the driver" to "can I hack/redirect the fault USB descriptor". My only other thought at the moment is downloading and then trying to sideload the updated fastboot via sdcard, but that probably won't work and probably won't give me root access. So now I'm just left with a phone with an unlocked bootloader I can't modify, all all the DRM on the stock OS disabled so you can't use every app with it. I'm deflated, heartbroken, anguished and frustrated...
To anyone who reads this, I've spent so many nights trying to work this out, sorry that I can't provide an answer...

Related

fastboot not detecting phone

I have an HTC Incredible 4G LTE. I underwent the process detailed here to unlock the bootloader.
When i got the HTCDev website, i ran a fastboot command and it just says <waiting for device>. I tried to detect the device with adb devices, and fastboot devices, but with no success. the THC Sync manager is not installed. HTC drivers should be installed. I am plugged into a USB 2.0 port, the same one used through out the process (i even tried the other one).
I am at a loss as to what is happening. I do know that the device manager sees my phone, and shows the drivers as the latest version. It does give this message:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
The device manager is listing the driver as version 2.0.7.3.
EDIT: Was able to get driver updated to 2.0.7.18
Also, when connected to the computer normally an orange light shows near the speaker. I wasn't concerned at first as I know the Android OS is not actually up and running on the phone, but do wonder if it doesn't indicated a problem.
Another note, I am running Windows 8.
EDIT 2: More research has yielded the following "Android Bootloader Interface". Every reference installing this from the usb_driver in the ../extra/google/usb_driver folder. When I attempt to do so from the device manager Have Disk ui I receive the following error
The folder you specified doesn't contain a compatible software driver for your
device. If the folder contains a driver, make sure it is designer to work with
Windows for x64-based systems.
Click to expand...
Click to collapse
EDIT 3: Removed entire android sdk, redownloaded and installed. Removed all HTC software and drivers. Booted phone into fastboot, and windows detected an "Android 1.0" device, installed the Android Bootloader Interface driver from the google usb_driver successfully. However, fastboot devices still does not detect the phone, and device manager still shows code 10.
As of now:
No HTC Sync, or HTC Driver
phone booted into fastboot, phone displays "FASTBOOT USB"
phone is set to usb debug
phone is connected to pc with good cable to a usb 2.0 port
I have:
rebooted pc, re-installed drivers, changed usb cords, changed usb ports, even tried a usb 3.0 port, i have tried some generic fixes for code 10 errors, and completely run out of ideas
EDIT 4: After using a different computer running Windows 7 I was able to complete the process, however, i would very much like toresolve the issue with my own PC, as the Win7 laptop is not mine. I utilized the adb/fastboot/winapi files from my Win8 machine. Win7 automatically found HTC drivers (2.0.7.18) and everything seemed to work just fine. Any ideas?

[Q] [BootLdr] Computer not seeing Phone.

I am new to android, HTC One VX being my first phone ((Got it like Last year as a gift iirc)).
Using Stock rom and my os is 8.1 pro x64
I am trying to unlock the bootloader.. I went to HTCdev, followed the directions for unlocking the bootlader.
1. Got the Android SDK and installed
2. Got the HTC SYnc Manager for the drivers.
3. Got Fastboot and moved it to where the ADB .dll file is.
I get my phone into bootloader after making sure USB Debugging is enabled, then I plug it into my computer. After a few moments, Windows pops up with USB Device is not recognized. I check Device Manager, it shows "My HTC" under unknown devices. I manually point the thing to where the W8 x64 driver is , and it says the driver is up to date. Bring up the Property info of the device, this is what is showing int he text box,
Code:
A request for USB BOS descriptor failed
Just to make sure, I navigate back to the ADB folder, bring up CMD there and type in
Code:
adb devices
. No device was listed despite my phone being connected to my computer. Tried it with 3 different cords, front and back of my computer. ((USB 3.0 ports.))
I put it in one of my USB 2.0 ports and the issue persists, the device status shows
Code:
A device which does not exist was specified
.
Is there anyway to fix this, its quiet annoying, Apparently doing clean reinstalls of everything isn't going to fix it for me.

Windows 10 not recognizing Moto g6 Play

I've found a few posts on other sites with no solutions yet. Hopefully I'm not being a pain and asking an already answered question elsewhere.
I have the amazon version of the Moto G6 Play, and I've been trying to unlock the bootloader. The problem is that motorola's device manager doesn't seem to install the necessary drives for the PC to recognize the phone is connected via usb, and frankly, Motorola's customer service hasn't helped in the slightest.
I'm running Windows 10, fully updated to the latest release, and my G6 is running android 8.0.0.0. I've unlocked the developer options, allowed OEM unlock, USB debugging, and changed the USB connection settings from "charging" to "MTP." I've installed the latest Motorola Device Manager, but I continue to see that the phone is listed as an unknown USB device from my device manager. I've tried manually updating the drivers both by searching the install folder for the MDM, as well as the Windows System 32 folder. I've also tried using the troubleshooter to find drivers online with no luck. When I run abd from the command console, it lists no connected devices and trying to run any commands fails to yield any response on either the phone or the console. I feel like there's something obvious that I must have missed, but for the life of me I can't figure out what.
Any suggestions? Thanks in advance.
:aneburchette said:
I've found a few posts on other sites with no solutions yet. Hopefully I'm not being a pain and asking an already answered question elsewhere.
I have the amazon version of the Moto G6 Play, and I've been trying to unlock the bootloader. The problem is that motorola's device manager doesn't seem to install the necessary drives for the PC to recognize the phone is connected via usb, and frankly, Motorola's customer service hasn't helped in the slightest.
I'm running Windows 10, fully updated to the latest release, and my G6 is running android 8.0.0.0. I've unlocked the developer options, allowed OEM unlock, USB debugging, and changed the USB connection settings from "charging" to "MTP." I've installed the latest Motorola Device Manager, but I continue to see that the phone is listed as an unknown USB device from my device manager. I've tried manually updating the drivers both by searching the install folder for the MDM, as well as the Windows System 32 folder. I've also tried using the troubleshooter to find drivers online with no luck. When I run abd from the command console, it lists no connected devices and trying to run any commands fails to yield any response on either the phone or the console. I feel like there's something obvious that I must have missed, but for the life of me I can't figure out what.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Use this. https://support.motorola.com/us/en/solution/MS88481
Also, make sure to restart your PC after you install them.
my pc did not recognize it in fastboot mode, after trying other cpus ... the solution was to do a factory reset, and go! the adb fastboot already recognized it ... I hope it works for you

Pixel 2 XL isn't detected on my PC [help]

After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared).
Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
simplepinoi177 said:
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
Click to expand...
Click to collapse
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
blancheSX said:
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
Click to expand...
Click to collapse
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions.
You can find the latest version linked in the 9x guide in my signature.
Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC.
There is also a basic troubleshooting guide in the same link in my sig.
Best regards!
simplepinoi177 said:
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
Click to expand...
Click to collapse
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
dallas90733 said:
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
Click to expand...
Click to collapse
i tried those tuturial and ended in error code : 10, device cannot started.
SageWilliams said:
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
Click to expand...
Click to collapse
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
blancheSX said:
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
Click to expand...
Click to collapse
blancheSX said:
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
Click to expand...
Click to collapse
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly.
*One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…)
If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands
Code:
adb devices
and
Code:
fastboot --version
.
Hopefully, if you do all of these things, it might get things reset and working from a stable established set up.
If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out...
Let me/us know how it works out, good luck, and hope this all ends up being helpful…
simplepinoi177 said:
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Click to expand...
Click to collapse
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
blancheSX said:
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
Click to expand...
Click to collapse
Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding...
If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......
Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit.
Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.

Question LE2125 Driver issue

I'm trying to restore my Oneplus 9 Pro to factory defaults. I downloaded the latest stock OOS Img from the oneplus site and then followed the direction in this thread (https://forum.xda-developers.com/t/restore-oneplus-9-to-stock-via-fastboot-commands.4265153/) to extract the payload.bin file.
I have all the img files and I tried using the powershell script in the link posted above to flash all the imgs. It seems to get through everything, up to the point where it tries to flash the flashbootd partition. When it gets to that part, I get a bunch of errors stating that it can't write to it.
When I look at device manager in Windows, I see the "LE2125" device with a exclamation mark. The hardware ID for that device is:
USB\VID_18D1&PID_4EE0&REV_0504
USB\VID_18D1&PID_4EE0
I can't seem to find any compatible drivers that work for this. It works fine when I'm plugged in and at the booloader, and also in Windows, but when I go into fastbootd, it doesn't seem to recognize. I tried connecting to USB and USB-C connectors (I have an adapter that allows me to also plug into USB)
Anyway, I'm posting this because I can't seem to find much information about the driver or hardware ID, and I'm sure I'm not the first person with this issue. Any assistance is appreciated. Maybe I'm doing something wrong.
I had the issue in fastboot mode yesterday (with win11), I solved it by installing the Oneplus driver, loading windows "disabling driver signature enforcement" mode.
Thank you that did work for me, although I have to add that simpy installing the oneplus driver wasn't enough for me. I had to manually go into device manager right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.

Categories

Resources