Related
Hi, today a have tried to root my htc desire using revoked 2 method. I was unable to install usb drivers. And now i cant even mount desire as hard drive. Computer still reports that device is unknown. I tried different usb ports, 2 different cabels, windows xp and seven. Before everything worked fine. Do you thing it is possible, that i damaged phone, when i plug it out just disconnecting cable?
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
MasDroid said:
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
I used this tutorial http://forum.xda-developers.com/showthread.php?t=788044
and I stuck at 3. point... On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
and after that i am unable to connect desire to pc... no way...seems like something happend with usb driver in phone or i dont know...just i ve tried 3 computers for now and every reports same when I connect usb, that device is unknown
What Hboot do you have?
What is your PVT version? (also check the Bootloader for this info)
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
benefic said:
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
Click to expand...
Click to collapse
And your PVT version?
Bravo pvt1 ship s-on
hboot-0.93.0001
benefic said:
Bravo pvt1 ship s-on
hboot-0.93.0001
Click to expand...
Click to collapse
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
MasDroid said:
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
Click to expand...
Click to collapse
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
benefic said:
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
Click to expand...
Click to collapse
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
MasDroid said:
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
Click to expand...
Click to collapse
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
benefic said:
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
Click to expand...
Click to collapse
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
EDIT:
With the phone connected, try the following afterwards:
Check to make sure that you have USB Debugging enabled on your phone.
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software'. Browse to the folder (extract the zip to the Desktop) i have attached below and see if it installs them.
MasDroid said:
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
Try the following afterwards:
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software' (Make sure you are connected to the Internet to search for available drivers via Windows Update).
Click to expand...
Click to collapse
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
benefic said:
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
Click to expand...
Click to collapse
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
MasDroid said:
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
Click to expand...
Click to collapse
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
benefic said:
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
Click to expand...
Click to collapse
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
MasDroid said:
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
Click to expand...
Click to collapse
So, linux didnt work either, system didnt even recognize that anything was plug in. Even crossed fingers dident help Well only last thing I have to ask, if there is any possibility to recover hboot, restore it somehow. Forexample through recovery menu in hboot loader and some kind of .zip file, that i will put to SD card. If not, well I will have to step out to that freezing weather and walk to orange store for reclamation, which I hope would be positive for me, but something telling me it surely will.
I found something about usb unbrick here on xda forum, but is only for root phones
well i found this http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15 i think it could work, just i dont know a way how to discover my CID number..to modify mtd0.img file
ok, i did everything step by step using rageagainstthecage tutorial, but nothing happend at all.
If anyone could help...
Are you able to get into Fastboot?
I suppose running your stock RUU in Hboot won't make a difference then... how about trying the PB99IMG method, which involves renaming the extracted rom.zip file to PB99IMG.zip from your stock RUU, placing this to the root of your SD card and then letting it run from Fastboot mode. This would restore your stock Hboot. You could also try AlphaRev's modified 0.93 HBOOT with S-OFF?
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
This helped me... http://www.droidforums.net/forum/dr...b-windows-7-64bit-should-also-work-32bit.html
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
me144 said:
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
Click to expand...
Click to collapse
I have an incredible and it worked for me...good luck.
me144 said:
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
Click to expand...
Click to collapse
Go here and follow her steps exactly....
http://www.droidforums.net/forum/dr...ow-root-stock-2-2-using-unrevoked-3-32-a.html
Sent from my Incredible using XDA App
Hi,
i tryed to get the Desire working with adb and everything works fine. I downloaded HTC Sync, installed only the drivers, and the adb interface worked with the Desire. But if i reboot in bootloader and use fastbootinterface it doesn't work.
fastboot devices get no result.
I downloaded unrevoke modified drivers, i also tryed to uninstall HTC driver and install only the modifed drivers. I also tryed to use this drivers:
http://forum.xda-developers.com/showthread.php?t=1161769
but always the same problem:
The device manager shows adb Intreface and there the HTC bootloader, but with and yellow !. properties of the Device shows me following error:
original Error log said:
Das Gerät kann nicht gestartet werden. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Translation in my own words: said:
The devices can not be startet (Code10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
And i installed the drivers correctly. So with settings, reboot and tha with deactivate the driver signature.
I hope you can help me
You should uninstall everything and start from the beginning. HTC sync clearly messed something up.
First, try to reinstall hboot drivers.
allready tryed but i get the same error.
google "the devices can not be started (code 10)"
happened to me before, its a windows problem. u have to delete something , cant remember what tho.
i uninstalled every thing desire also the not shown devices in devices manager. than i connected the desire in fastboot with pc and the pc gets the driver from alone. But with the error.
Thanks for the tip with the delete something. but the only results i find are something about reinstall the driver, update the driver, uninstall the driver, ask the support of the device -.-
Do you know maybe a link word what i need to delete? is it a file, an old driver,...??
http://www.google.com/url?sa=t&sour...9oGABg&usg=AFQjCNH1CYaPX1ZheHJ-vYr2Y3GDNFFvWw
try here, the thing that worked for me was deleting somthing in the registry.
thank you very much i'll try it
Just found the time to read the link.
One question? I looked for the Device Class GUID for USB. But there is no lowerfilter and upperfilter. What class is the desire?
I got a similar problem on my workstation, I got an Android Phone in device manager and nothing else, I'm not able to connect and mount desires SD Card. Windows 7 x64, on my laptop (same os) everthing works fine. My PC recognizes desire only with drivers from Android SDK software.
i think your problem is a bit diferent. Do you have a custom ROM installed?
If you did and it is an android 4.x ROM there are many Problems with USB mount. Try an app to mount the SD Card.
Back to my problem. I readed all of the site from up to down and than i deletet the Keys. After Reboot 2 times i got the bluescreen -.- after that the autorepair startet it selfs. the first couldn't repiar the system, and the second couldn't either. So i needed to reinstll windows
The good thing with this is There is difently no HTC on the PC anymore. So in what order i need to install which drivers to get the Desire in Fastboot connected?
A the moment I'm using CronMode 2.1 (previous CM 2.0, SpazeDog ICS, BravoBCM). On previous roms (all ICS based on CM9) got same problem. Laptop - ASUS S6F, Windows 7 Pro x64 - phone recognized, usb mount working fine. Desktop - Gigabyte P55-UD3, Windows 7 Pro x64 - just got Android Phone in device manager and that's all.
What app do you mean?
Try Usb mass storage toggle form the market.
Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).
nonline said:
Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).
Click to expand...
Click to collapse
You may have a usb brick. Try the "usb unbrick" option in recovery
abaaaabbbb63 said:
You may have a usb brick. Try the "usb unbrick" option in recovery
Click to expand...
Click to collapse
So why other PC/Laptopts recognize my phone proper?
nonline said:
So why other PC/Laptopts proper recognize my phone?
Click to expand...
Click to collapse
Ok then... reinstall your OS on the PC. If your tried everything, it's the last solution I can think of.
You can first try to reinstall the Driver.
Back to my problem in what order do i need to install the drivers for fastboot?
I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.
nonline said:
I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.
Click to expand...
Click to collapse
Some firms disable this ability and also SD card reading for security purposes. That can be only reason i can think of.
Sent from my HTC Desire
I'm also a sysadmin of this machine, so you can belive me, just a build-in firewall and security essentials as antivirus protection software.
My wife's Desire S shows the same problem. I think it is a driver issue. Can someone recommend a single "htc desire driver" for Windows 7 64bit?
I'm trying to root my HTC Desire but falling at one of the first hurdles: I'm not able to install the driver software, I see the following error:
hxxp://i.imgur.com/5n720Wi.png
I'm running Windows 8 64-bit, and I'm trying to follow the steps to root as described here: androidforums.com/desire-all-things-root/300866-guide-rooting-htc-android-2-2-1-lower-unrevoked-windows-updated-20th-december-2012-a.html
I've installed HTC Sync and uninstalled HTC manager, and uninstalled Dropbox. I can connect to the Desire via USB both in HBOOT (with a successful USB connection message) and in regular Android OS.
I experimented with a couple other drivers - "Universal_Naked_Driver_0.72.zip" and "Acer_A1.win8.usb_drivers.x86_x64.rar" I found mentioned elsewhere.
Are there other drivers available? Any other advice for me to root this for the first time?
I have posted sometime earlier workaround to get it working on Win8, search.
Edit:
http://forum.xda-developers.com/showthread.php?t=1961823&highlight=windows+8+drivers
outofbandii said:
I can connect to the Desire via USB both in HBOOT (with a successful USB connection message) and in regular Android OS.
Click to expand...
Click to collapse
That's not right. Because your screenshot shows an Android 1.0 Device and this means the Desire isn't connected correctly.
Uninstall ALL about HTC and Desire. start the device manager and there activate in the options show disabled Device. Than you look in EVERY directory for Android, Desire, HTC. And remove the Drivers. right klick, remove and than yes and make sure if there is a option that says complete delet the driver say yes.
For Fastboot drivers:
Start Desire in Fastboot, and than you connect to the PC. Normaly Win 8 searches for Drivers. Than it says nothing found. Try in the Device Manager right Klick on Android 1.0 - If there is something about HTC Bootloader with an ! than you have an diferent problem - and research for drivers -> Internet. Than it normaly should work. If not download these drivers directly from unrevoke.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install directly from unrevoked.
and go to device manager, install drivers from PC. Also here make sure the unknown device is an Android 1.0 if the name is different pls tell us.
For Normal use:
after Fastboot works, you download the newest HTC Sync for Desire: http://www.htc.com/de/support/news.aspx?p_id=312&p_name=htc-desire
Ok run the installation BUT After you startet setup it says something like there are a few things missing befor installing. These are HTC Driver, something about Adobe, install these. After that the installer ask for some agreements for HTC Sync now you cancle the install, because all you need are the drivers and they are now installed. It should work now.
If there are some more problems let me know. I had some trouble with the ADB and fastboot drivers a week ago, too but now it works
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.