Fastboot broken in Windows 8.1 - HTC Droid DNA

This may be an "old" issue, but i ran into a problem. I have tried every compatible driver for my phone and adb works fine. However, when i reboot into fastboot, the phone is not recognized.
I've tried changing the id of the usb drives and changing the drivers for my phone. I have a functioning adb and fastboot, but now that i've upgraded to 8.1, i can't fastboot flash anything.
Does anyone know of a solution for this on our DNA?

-DroidIsDNA- said:
This may be an "old" issue, but i ran into a problem. I have tried every compatible driver for my phone and adb works fine. However, when i reboot into fastboot, the phone is not recognized.
I've tried changing the id of the usb drives and changing the drivers for my phone. I have a functioning adb and fastboot, but now that i've upgraded to 8.1, i can't fastboot flash anything.
Does anyone know of a solution for this on our DNA?
Click to expand...
Click to collapse
Have a look at
http://forum.xda-developers.com/showthread.php?t=2521504

Related

RSD won't recognize ATRIX (but does in fastboot)

I'm trying to reset my atrix because of warranty issues. I tried everything so far I could find but RSD 6.1.4 wont recognize my Atrix. I installed the newest drivers, and I've tried different usb ports, run as admin.... Everything won t work for me. Whenever I boot in fastboot and use "moto-fastboot devices", my phone will show up. It s just not working with rsd
I'm running WIN8 64-bit (might be the problem?)
Have no idea what else to try
coolni said:
I'm trying to reset my atrix because of warranty issues. I tried everything so far I could find but RSD 6.1.4 wont recognize my Atrix. I installed the newest drivers, and I've tried different usb ports, run as admin.... Everything won t work for me. Whenever I boot in fastboot and use "moto-fastboot devices", my phone will show up. It s just not working with rsd
I'm running WIN8 64-bit (might be the problem?)
Have no idea what else to try
Click to expand...
Click to collapse
Probably yes I too have WIN8 and to get working drivers I used some program to disassemble driver and install it manually but in my case fastboot doesn't work too, but it can bee new atrix series where is blocked rsd. And does you put phone in rds mode

[Q] device not recognizable in fastboot

I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Use command fastboot devices to see it while in fastboot. Adb devices is for when it is booted.
3L3C7R0 said:
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Click to expand...
Click to collapse
I'm running windows 7 and have yet to get mine to see the device. Good luck.
3L3C7R0 said:
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Click to expand...
Click to collapse
put device in fastboot.
got pc, setting, system, device manager. towards top click my htc and update drivers. dont search automatically, coose device from list.
when the list comes up, you should see a few different drivers listed. choose one and try.
if one dont work, try another
Ps make sure you usb drivers are up to date. i had to install updated axhi usb drivers for my motherboards usb 3.0

[Q] ADB Issue

I have a Win 8.1 machine with the HTC drives installed and when I run ADB with the phone booted to the ROM everything is fine. ADB returns the device ID and it is recognized. When I boot into the fastboot, I get fastboot usb but ADB does not recognize the device, I get List of devices attached and then nothing. I have rebooted both the phone and computer, uninstalled and reinstalled the drivers but no luck. Anyone ever seen this behavior?
Please close thread.

Fastboot not detecting device

For whatever reason fastboot on my PC (win10) doesn't detect my phone, adb detects it fine when it's in recovery or booted normally, I cannot send fastboot commands as it says waiting for device. I've tried a few things like the LG Mobile Driver and a universal driver but it still isn't working. Any ideas?
Just to clarify I am in Fastboot mode when trying this.
Edit: Also tried the Google USB drivers from the SDK manager, didn't make a difference
I ended up simply doing it on an Ubuntu installation. Works perfectly on there, not sure why Win10 doesn't work though.
My problem is solved.

Driver problems on Recovery and Fastboot after trying magisk.

Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814

Categories

Resources