I Am Using Windows 10 (x64). I Am Having Issues Connecting My Android Device In Fastboot Mode. Although I Have Installed Proper Drivers For My Device & It Is Recognized By Windows 10 In Normal Mode (HTC Android Composite Device) But I Am Unable To Use It In Fastboot Mode. My HTC Device Is Also Recognized In "HBOOT Mode". It Shows "Device Failed Enumeration - Error Code 43" In Fastboot Mode. I Have Tried Everything But Unable To Get It Connected.
Having the same exact issues ! i have windows 10 and the cdma version on the htc evo 3d ..
everythings works fine but when it comes to trying to get s off and trying to boot into that fastboot usb my pc is saying device enumeration failed ?
ive tried everything .... phone works fine in all corners except the fastboot , makes no sence .
this guy has a solution.
made my day
In case this is still not working please consider this post : http://forum.xda-developers.com/showpost.php?p=69234983&postcount=6
You are a hero
danamal4real said:
this guy has a solution.
made my day
Click to expand...
Click to collapse
You are definitely a hero, god bless you, you are awesome. Thank you.
Related
So yeah, I got my hands on Windows 8.1 Final a bit early but I can't get fastboot to recognize my Desire X. Listed as unknown device (Device enumeration failed). Any help?
ShadowCodeGaming said:
So yeah, I got my hands on Windows 8.1 Final a bit early but I can't get fastboot to recognize my Desire X. Listed as unknown device (Device enumeration failed). Any help?
Click to expand...
Click to collapse
I had that same problem,but no matter what i tried it just didn't work. So i used live ubuntu cd for that,but now i am back on Windows 7.
The drivers are making a big problem,try doing some search,you might find something. I just didn't have the nerves.
Are there any compatible fastboot drivers for Windows 8.1. Ever since I upgraded to 8.1 the device is not recognized in fastboot. It worked fine in Windows 8 but when I went to 8.1 it no longer would. I have tried numerous drivers to no avail. It connects fine normally to transfer files etc, just when it reboots in fastboot evice not found".
mrpickem said:
Are there any compatible fastboot drivers for Windows 8.1. Ever since I upgraded to 8.1 the device is not recognized in fastboot. It worked fine in Windows 8 but when I went to 8.1 it no longer would. I have tried numerous drivers to no avail. It connects fine normally to transfer files etc, just when it reboots in fastboot evice not found".
Click to expand...
Click to collapse
They work for me in 8.1, however, for some reason, fastboot will NOT work with any USB 3.0 port (with the blue color). Make sure you are connecting to a 2.0 port!
same issue, and i'm using usb 2.0. i'm also using original usb cable and have tried other cables as well.
i am to getting this problem is there any solution on this
I downloaded the latest HTC Sync which installed the drivers. I have no problem with Fastboot and my One. You can unintstall Sync afterwards.
RangerLG said:
I downloaded the latest HTC Sync which installed the drivers. I have no problem with Fastboot and my One. You can unintstall Sync afterwards.
Click to expand...
Click to collapse
And you're using Windows 8.1 right? I just tried that, did a system restore to before I had any drivers whatsoever installed...then installed the latest HTC Sync. The adb drivers work fine but as soon as I reboot into the bootloader I get the same USB enumeration error and fastboot doesn't work. I have no idea how to fix this, it's real frustrating.
Sorry I haven't responded sooner. Yes I am on 8.1 and have no issues.
I can confirm it was a USB 3.0 issue in my case. As soon as I found a regular USB 2.0 port all my Windows 8.1 woes went away.
i have flashed pacman in my phone and now i cant mount usb storage on my pc , i am having windows 8.1 in my pc . But when i am having stock rom i am able to mount usb , please help me . My Phone Model is HTC Desire S
Hello
i have a asus transformer book t100 with windows8.1 and i cant get fasboot to Work... Adb is working
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
dilyn said:
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
Click to expand...
Click to collapse
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
bigdaddy619 said:
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
Click to expand...
Click to collapse
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
bigdaddy619 said:
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
Click to expand...
Click to collapse
That's really strange. I had the drivers working prior to this episode. I thought that the device suddenly being unrecognizable had something more to do with it.
Oh well. Today I learned.
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
dg32 said:
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Windows 8.1 recognized my device in normal operation, but in any modified hboot failed miserably. (such that are used in conversions/etc)
I've long since reverted back to Win7 for anything involving Android....just so much less risky at this point.
Hello!
I was trying to downgrade a Moto E XT1021 and I don't remember how but I ended with the phone stucked in the "bootloader unlocked" screen.
Tried to access the phone on the fastboot flash mode and I can get into the mode by pushing volume down and power on for a few seconds. The problem is that I'm not able to send command to the phone because adb or fastboot doesn't detect it.
The USB cable seems to be working because on the phone screen you can read USB connected and USB disconnected every time I connect or disconnect the cable.
My guess is that there's a problem with the drivers, I've tried everything, of course installing the MotorolaDeviceManager_2.5.4.exe was the first step and then I ended up trying adb-setup-1.4.3.exe and also adb-setup-1..3.exe with no luck. I'm using Windows 7 professional 64 bits.
Right now phone driver says: Android Composite ADB interface.
Hardware ID is USB\VID_22B8&PID_2E80
If I remove the driver the device with no driver says "fastboot condor S"
I want to install 4.4.4 on that phone.
What can I do?
Thanks!
I solved it
Close the thread please.
provide the solution
draxofavalon said:
I solved it
Close the thread please.
Click to expand...
Click to collapse
at least provide the solution if anyone comes wandering again with the same problem
I really don't know why it worked, but I had several folders with adb, fastboot and firmwares and ona of the folders with fastboot detected the phone, I tried the other folder and that version of fastboot didn't detected the device; really weird.
Same software, same dll's but in different hard drives, the one on the C drive worked and the one in the D drive didn't detect the phone.
As I said, really weird.
Whenever I boot my phone into fastboot mode and connect it to my computer, the fastboot logo disappears and is replaced by the message "press any key to shutdown". Miflash says that there is no device connected. I have tried switching ports, I am running windows 10 64-bit with and Intel CPU. I installed the latest drivers and it still hasn't worked. I double check USB debugging and OEM unlocking were enabled.
Same here, minus the shutdown message. Unable to connect to misuite either. No problem connecting via windows explorer.
veekay said:
Same here, minus the shutdown message. Unable to connect to misuite either. No problem connecting via windows explorer.
Click to expand...
Click to collapse
About the MiSuite thing, that is no longer supported for devices running above MIUI 7, so you shouldn't be worried about that
Well, at least that is one problem solved. Silly, but whatever. Still leaves us both unable to use miflash.
Of course I try my wifes laptop and it works instantly. 72 hour wait now. No idea why neither of my two laptops work with it.
Just wondering, what operating system does your wife's computer run? I heard using windows 7 fixes the problem in some cases.
We both run Windows 10 - x64 and Intel.