Related
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
kinglime said:
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
Click to expand...
Click to collapse
I just experienced the exact same issue following the same steps on my laptop also running 8.1
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
gzbrambila said:
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
megaorange1 said:
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
Click to expand...
Click to collapse
From all of my research, you're the first person I've heard of having it working. Any specific drivers used? I'm very curious (currently, I have to use a backup machine to push TWRP updates to my VZW One)
Same thing here. 8.1 broke fastboot. Is this a Microsoft problem specifically because if it is I seriously doubt they will be in a hurry to patch it.
Sent from my HTC One using Tapatalk
I have found out something based on the VMware experience. Can somebody try it out and report back???
I feel that the fastboot problem in windows 8.1 is related to the USB port.
For those people that having problem, are you guys using USB 2.0??? If yes do you have USB 3.0 port in your computer??? The real problem maybe is that fastboot only works with USB 3.0 but not USB 2.0 in windows 8.1...
I tried both USB types, and half a dozen drivers and workarounds, and nothing.
I don't believe the dude above got it working. He is probably thinking Win 8, not 8.1. I have it working on 8.
Flash Image GUI will probably do everything you need to do in fastboot without the need for a computer. I just threw 8.1 on one of my extra PC's, I'll see if I can get the drivers going. I feel like this was answered in another thread though, I think it is in the rumrunner thread...
Just another reason why 8 is bad
cgskook said:
Just another reason why 8 is bad
Click to expand...
Click to collapse
fastboot was working on windows 8 and adb !!!
so the update win 8.1 have change sometihng but the question is what
and i try different drivers (from google,intelandroiddrv) and noting work
why have micro change something with drivers pffffff
kaverorzi said:
yep,definitely not working on Win8.1x64
Rooted a couple weeks ago on Win8x64, no issues.
Only noticed this issue today after I couldn't flash a different splash screen for my NuSenseOne.
Click to expand...
Click to collapse
I don't have the link on hand but there is a driver update to support 8.1 I have it working fine.
Sent from my HTC6500LVW using Tapatalk
i just used http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ and fastboot works on a 3.0 port on 8.1
I've just had this problem last week, and now got a solution...
Hi guys,
For anyone interested, due to something DreamerTKM said - I tried both USB 2 & USB 3 sockets on my Dell L701X laptop and both failed:
ERROR: Unknown USB Device (Device Failed Enumeration)
I did a clean install of Win 8.1 Pro and it still failed...
Anyway, I was using Windows 8.1 Pro default drivers for my system when this issue came up last week - default as in Microsoft's own out of the box drivers (drivers on the install DVD and Windows Updates) for my CPU chipset, USB chipset, etc... - my entire system (except for my nVidia graphic card!)
My laptop is now a few years old and my official "Dell" CPU chipset drivers are not compatible with Win 8.1, so I need to rely on Microsoft for these, but my USB 3 originally had Dell supplied "Renesas USB 3" drivers which I hadn't installed or even thought about installing as my USB 3 socket worked - and worked well...
...anyway, after installing the original Renesas USB 3 drivers the fastboot commands work once plugged into a USB 3 socket! USB 2 still wouldn't work though, but now my Win 8.1 laptop can do fastboot commands through a USB 3 socket.
I understand not everyone will have a Dell L701X laptop but the moral here is before blaming Microsoft and their Windows 8.1 O/S (which is truly awesome), try installing the correct drivers first!
DreamerTKM - thank you for putting me on the correct path with this!
Hopefully this post may help some of you!
solution
guyz if u r working on win8.1 just plug it in ur usb 3.0 then it will wrk...if u put in usb 2.0 it wont!
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
wex28 said:
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
Click to expand...
Click to collapse
Full fastboot and ADB support is available in windows 8.
Watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
morrowa2 said:
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
Click to expand...
Click to collapse
Also, there is this: http://forum.xda-developers.com/showthread.php?t=2703585
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Try these steps:
-uninstall previous version of SDK tools from PC
-download latest SDK Tools from HERE
-have a USB 2.0 cable available
-follow these steps to verify connectivity
see if these things help
Unless there is a specific reason you're still on Sept 8.0, I'd take this chance and upgrade to lasts 8.1 factory image.
evanxalmighty said:
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Click to expand...
Click to collapse
I'm just spitballing here but....
With phone plugged in, on your pc, under device manage. When you open it up do you see unknown android device? That driver may need to be updated. Also, USB debugging is on, and the option to transfer files? Is your SDK platform-tools up to date?
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
I haven't seen it with this phone yet, but try changing the USB mode on your phone from the notification; I've had a few phones that refuse to work in specific modes.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
Have you tried a different USB-C-A cable just for the heck of it. May have to factory reset and see if that solves it.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
So your driver is messed up. Did you use the driver below?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Sent from my taimen using XDA Labs
It won't let me install the driver I get some kind of error when selecting it. I was able to get it to work after plugging it in and out. Now that I updated to 8.1 everything was fine untill I got home. Now it's doing it again. I tried 2 different cables restarted my computer and laptop and can't figure out why it was working fine before without doing anything different.
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
JimSmith94 said:
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
This definitely worked for me -- Thanks for posting!
I am having sort of the same problem. I was on Android 11 on my 2xl, rooted with fast boot boot twrp.Img and installed magisk and super super, all latest. I could not get gaps so I used Android flash tool to attempt to go back stock and it downloaded and flashed it but it is now stuck in loop, I reboot to recovery and it’s stock now and it will not be recognized by adb or fast boot,!0plesase help
Fastboot does not recognize when unlocking bootloader.Fastboot does not recognize when unlocking bootloader.
Check to make sure you have the latest drivers installed.
I could not for the life of me get it to work on my windows laptop. Tried installing the OnePlus USB Drivers, tried isntalling generic USB drivers, rebooted multiple times, tried differetn cables, tried different versions of ADB, through chocolatey and the minimal ADB installer here on XDA.
On my other laptop running Arch Linux i installed the android-tools package and it worked perfectly though. adb reboot, and then fastboot devices, and fastboot oem unlock on first try.
I have one device (I do not remember what one) that always needed to be unplugged on the computer side after a reboot to bootloader for fastboot to find it.
A bit annoying but, I got use to it. I use USB-A 2.0 Port to USB-Micro/USB-C cables.
Unplugging the cable on the device side did not make a difference, it had to be the computer side.
Also try a different cable and USB port on computer.
Not sure if it helps or makes a difference in your circumstance. ¯\_(ツ)_/¯
I just remember it driving me crazy until I accidentally unplugged it and it was found as soon as I plugged it back in.
Cheers.
PS.
Found a post I recently made about cables I use for adb/fastboot.
USNF - [ xdaThread ] - Post # 2,638
To provide you with some context, I messed up a custom ROM install on my Redmi Note 5 Pro/Whyred Global version/ where the phone starts up and get stuck on the Orangefox Recover logo screen.
I thought I could just reinstall Orangefox via fastboot and format the phone to start fresh but the phone is refusing to be recognized by Windows in fastboot. It's the same Windows 10 PC that I used to unlock the bootloader on this phone and flash a custom recovery a year ago, and now it refuses to recognize my phone altogether.
Its giving me the USB Device Descriptor Request Failed error.
The drivers are not the issue here on my PC, I recently used this PC to unlock my Poco F3 and the procedure on that went flawlessly. But now it's refusing to recognize this phone. To rule out the little stuff, i changed cables, changed and tried different PCs, decided to use a USB 2.0 port on my PC thinking that might be the problem but still no luck.
I was planning to try this guide, but for that, I would need the hardware ids for the phone when its in fastboot mode. So if anyone has the phone, please I beg you give me the hardware Ids. I really want to fix this phone and give it another life.
Just in cast this fails, my last option would be to get the micro USB port replaced. I have gotten the USB port on this phone replaced twice as it used to cause problem when charging, so my final doubts are going to this.
My only evidence against a borked USB port is that the phone used to fast charge fine with this port. And since fast charging utilizes the data cables to negotiate with the fast charger, but I might be wrong about this.
So if anyone can help me regarding this issue, I would highly appreciate it.
https://forum.xda-developers.com/t/fastboot-not-detecting-my-phone.4544585/post-88035749
aIecxs said:
https://forum.xda-developers.com/t/fastboot-not-detecting-my-phone.4544585/post-88035749
Click to expand...
Click to collapse
I tried that , but I am still getting that error. Do you think this might because of faulty USB port?
probably Windows issue. use linux
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
abeel_siddiqui said:
Its giving me the USB Device Descriptor Request Failed error.
Click to expand...
Click to collapse
That's an indication of basic USB enumeration failing.
It could be bad cable, bad port or your device has failed initializing USB.
It's not an indication of anything to do with Windows drivers (at this point).
Renate said:
That's an indication of basic USB enumeration failing.
It could be bad cable, bad port or your device has failed initializing USB.
It's not an indication of anything to do with Windows drivers (at this point).
Click to expand...
Click to collapse
I have also tried swapping cables, the micro USB fault might just be faulty on the phone.
aIecxs said:
probably Windows issue. use linux
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
Click to expand...
Click to collapse
That could be possible, I will try booting into a live Linux environment and try it there.
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Try on Windows
ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.
limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.
limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...
simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.
Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.
TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.