So for the past few hours, Ive been having issues running the HTC RUU on my x64 Windows 10 Pro Laptop. After countless downloads and installs, I figure I share my solution for those in the future.
Problem: HTC RUU will not run, It will go to Accept or Decline T&E, then goto InstallShield, but does nothing after.
Solution:
HTC Sync
ADB Drivers
DotNet
Visual C++ 2008 x86
Make sure RUU.EXE has compatibility mode set to Windows 7 or XP SP3 ( tried both and got them to work on each setting )
Ive un-installed and re-installed so many versions of each. But only the Visual C++ is what really matters. Even if you're on x64 OS, you will need to install Visual C++ 2008 x86. Because The HTC RUU looks for the x86 files/directories.
Google the downloads and links.
Hope this saves someone a few hours of headaches or in my case 3 hours.
Cheers
-Wayne
are you on a custom ROM or a stock Sense ROM? I had trouble RUU-ing a stock package to update my firmware because of an issue with fastboot and LineageOS. I believe you can place a zip in the root of your SD card (it has to be named 2PS6IMG.zip) and flash it from bootloader mode or some similar mode. Fastboot worked fine while I was on the stock ROM
hello
RyanCanning said:
are you on a custom ROM or a stock Sense ROM? I had trouble RUU-ing a stock package to update my firmware because of an issue with fastboot and LineageOS. I believe you can place a zip in the root of your SD card (it has to be named 2PS6IMG.zip) and flash it from bootloader mode or some similar mode. Fastboot worked fine while I was on the stock ROM
Click to expand...
Click to collapse
you cant run ruu if you are bootloader unlocked, and is obligated is relock bootloader -fastboot oem lock that let you run the ruu again,after you relock and run the ruu , you can unlock the bootloader if want,and install another recovery, and rom
korko said:
you cant run ruu if you are bootloader unlocked, and is obligated is relock bootloader -fastboot oem lock that let you run the ruu again,after you relock and run the ruu , you can unlock the bootloader if want,and install another recovery, and rom
Click to expand...
Click to collapse
There is absolutely no requirement to relock the bootloader to flash an RUU or for that matter anything else on HTC 10.
shortyboy said:
So for the past few hours, Ive been having issues running the HTC RUU on my x64 Windows 10 Pro Laptop. After countless downloads and installs, I figure I share my solution for those in the future.
Problem: HTC RUU will not run, It will go to Accept or Decline T&E, then goto InstallShield, but does nothing after.
Solution:
HTC Sync
ADB Drivers
DotNet
Visual C++ 2008 x86
Make sure RUU.EXE has compatibility mode set to Windows 7 or XP SP3 ( tried both and got them to work on each setting )
Ive un-installed and re-installed so many versions of each. But only the Visual C++ is what really matters. Even if you're on x64 OS, you will need to install Visual C++ 2008 x86. Because The HTC RUU looks for the x86 files/directories.
Google the downloads and links.
Hope this saves someone a few hours of headaches or in my case 3 hours.
Cheers
-Wayne
Click to expand...
Click to collapse
I managed to run the US Unlocked RUU (2.51.617.1.exe) yesterday without (too many) issues.
I am on Win 10 Pro x64 (fall creator update).
From working with my previous HTC (ONE), I had already working HTC drivers, adb/fastboot, and registry hack so Win 10 can communicate with HTC devices over USB in fastboot.
Of note, I also do a bit of programming, so I have Visual C++ installed on this computer.
I ran the RUU.exe in admin mode. (NO compatibility modes set.) It was slooooow to load & run. I thought that the program was broken, but it eventually started. It was like 3 minutes before InstallShield open, then some minutes between each of the "questions" screens. I opened hardware monitor and noted no increased CPU/memory/Lan usages, so I am not sure what all the waiting was. <I have a reasonably fast setup - overclocked Intel desktop, SSD, Gb wired internet ... all the time this was running , I noted only like <10% usage of resources on my machine.>
But once the program got to detecting the phone, and actually doing the update, it was quite fast & painless.
I am pretty sure that the RUU running in slo-mo isn't normal, but at least it worked!
The problem sounds very familiar! Will definitely try with Visual C++ 2008 x86
How about all the rest? HTC Sync, ADB Drivers, DotNet… I’m only installing Windows on one of my Macs in order to run this RUU
Also… do you have an idea if I’ll get the same problem in Win 7? I’m not going to use it anyway, so I don’t really care which version of Windows I install.
Related
I cant get SDK Tools running, installation keep saying Java JDK is not installed. (but it is)
Fastboot drivers wont even start installing. (and phone is not recognized in Device Manager which is main issue)
Did anyone managed to get it running on Windows 8?
Optionally i can get ubuntu but it would be kind of annoying to switch OS just to change hboot etc.
Edit:
Got SDK working using this: https://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows
Edit2:
Got ADB Interface in device manager running aswell, more info here: http://forum.xda-developers.com/showthread.php?p=24487308
Everything is running for now, maybe someone will need this. :good:
k3lcior said:
I cant get SDK Tools running, installation keep saying Java JDK is not installed. (but it is)
Fastboot drivers wont even start installing. (and phone is not recognized in Device Manager which is main issue)
Did anyone managed to get it running on Windows 8?
Optionally i can get ubuntu but it would be kind of annoying to switch OS just to change hboot etc.
Edit:
Got SDK working using this: https://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows
Edit2:
Got ADB Interface in device manager running aswell, more info here: http://forum.xda-developers.com/showthread.php?p=24487308
Everything is running for now, maybe someone will need this. :good:
Click to expand...
Click to collapse
Good to know, getting new computer soon
Sent from my HTC Desire
jmcclue said:
Good to know, getting new computer soon
Sent from my HTC Desire
Click to expand...
Click to collapse
If you're getting a new pc, i recommend sticking to windows 7, mainly because of compatibility reasons.
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.
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..
This thread here: http://forum.xda-developers.com/showthread.php?t=2473644 has very few details on what software and drivers are required. I attempted to run the rumrunner tool on a Windows 8 and a separate Windows 8.1 machine, neither would recognize the HTC One and start the program.
I've never installed HTC Sync, so check that off. Developer mode is on. So I put Linux Mint x86 on a flash drive and booted to a live environment. Running the rumrunner tool from there now. After the third "pouring", it is sitting on "Waiting for ADB (18/120)" and "Waiting for device". It has been at this point for about 30 minutes now, I feel like something should have happened by this point.
I would've posted in the other thread, but apparently this forum is setup for new users to post in the general board first.
Advise?
Edit: Looks like it's finished. I couldn't wait any longer so unplugged it. Rebooted into fastboot and it shows unlocked. Great!
Okay, I have the M9 through at&t with Software number 1.32.502.9 running Android 5.0.2. I'm stock, unrooted, S-On, locked bootloader.
So, I tried for the past two weeks to get the OTA for my phone and it's always the same thing...No Updates Are Available. Still to this moment, same thing. Did they actually push it out for AT&T?
I resolved to do the manual update with the RUU on HTC's website. On my 64 bit Windows 8.1 PC configured with HTC Sync, factory cable, correct drivers, correct ADB/Fastboot, antivirus/firewalls disabled, salt over right shoulder, seven hail mary's said, NOTHING FREAKING WORKS. I tried installing some C++ thing and it didn't work either. I've done registry hacks...NOTHING. Installscript runs, and then quits. I've watched taskmanager to see if the process is hung up, but after running for two minutes, the process quits and nothing happens. I've run the RUU as admin and not with the same results.
I've done all of the above on a windows 7 32 bit system and a windows 7 64 bit system all with the same results. I've talked to HTC chat people and they can't figure it out. Seriously folks, WTF and I doing wrong?
I WAS able to extract rom.zip out of the RUU on a 32 bit windows 7 machine but there was some failed error message when I tried to flash using the fastboot oem flash rom.zip command.
What country are you in?
USA. I finally got it but I don't know how or why.
Nm