hi, im corrently runnning 2.2.2 liberty with the old HBOOT
and now i want to upgrade to the the HBOOT so i've read a little bit and found that i have to upgrafe the new RUU so that the HOOT will be replaced.
but i dont manage to istall it..
Hboot driver is istalled
htc sync is istalled
in device manager everything is OK
the RUU setup recognize the device.. then "boot into bootloader"
and then it loading for a while , the htc gray logo apeer on the aria and then it fails
what am i doing wrong?
havlaz said:
hi, im corrently runnning 2.2.2 liberty with the old HBOOT
and now i want to upgrade to the the HBOOT so i've read a little bit and found that i have to upgrafe the new RUU so that the HOOT will be replaced.
but i dont manage to istall it..
Hboot driver is istalled
htc sync is istalled
in device manager everything is OK
the RUU setup recognize the device.. then "boot into bootloader"
and then it loading for a while , the htc gray logo apeer on the aria and then it fails
what am i doing wrong?
Click to expand...
Click to collapse
What do you call the old HBOOT (I know what it is but I just want to make sure you are not mistaken)? There is no 1.2 HBOOT. With the 2.2.2 update, you are supposed to have 1.02.0000 as the bootloader version.
If you still have the HBOOT drivers installed from using Unrevoked on your computer previously, you should uninstall them before using the RUU. To do that, go to the HBOOT screen on your phone, connect the phone to the computer, then go into Device Manager, right-click on "Android Bootloader Interface" and choose Uninstall.
You should have "HTC Driver Installer" or something like that listed in Add/Remove Programs. If you have it you're good. If you don't have that, then install this: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Now you should be able to use the RUU.
If it still doesn't work (and I've had times when I swear everything was configured right and it still didn't work), you can use this alternative method which does the upgrade process completely from the phone, thus eliminating any driver related issues: http://forum.xda-developers.com/showpost.php?p=18541475&postcount=145
If you plan to use Revolutionary after doing this (I assume so), then you should uninstall HTC Sync before you do that. You should not uninstall the HTC drivers though.
Related
Hi guys, I have an HTC Hero, it was bought half a year ago and rooted.
Was running without problems until now.
The touchscreen stopped working
To eliminate the possibility of software malfunction I restored backup from nandroid.
There were no problems during the restore but it didn't help.
Next morning the device is bricked? FTW?
It was turned off all night and when tried to turn on in the morning it didn't come pass the HERO logo.
tried to go into recovery again but it wasn't there..
just have the "Fastboot" and "Simlock" features.
Any idea to what happened or how to fix this? can I flash an RUU somehow?
i remember it happened with my sapphire, i think you should try RUU.
ok so how do I flash RUU via FASTBOOT?
and how do I know what ruu should I use?
Find the one for your region, let you phone stay in fastboot, and be sure that the installed driver is the HTC one, and start the RUU... Profit!
mljjlm said:
Find the one for your region, let you phone stay in fastboot, and be sure that the installed driver is the HTC one, and start the RUU... Profit!
Click to expand...
Click to collapse
what do you mean by "be sure that the installed driver is the HTC one"?
If you installed HTC Sync, you probably have the right driver. Don't use the generic Google driver.
So... was running the MikVirgin ICS rom on my S-on 1.50 Evo 3d. Was going to bring it back to scratch and go through the S-Off process to run something better. I have Revolutionary 4.0.1.4 installed and fastboot on my computer. For the life of me, I cannot get the phone to accept anything now :\ Trying to run the RUU gives me the 170 error and any rom I try loops at the boot loader (not the white HTC screen, but the boot image for the rom).
Help would be appreciated
bl4ckllama said:
So... was running the MikVirgin ICS rom on my S-on 1.50 Evo 3d. Was going to bring it back to scratch and go through the S-Off process to run something better. I have Revolutionary 4.0.1.4 installed and fastboot on my computer. For the life of me, I cannot get the phone to accept anything now :\ Trying to run the RUU gives me the 170 error and any rom I try loops at the boot loader (not the white HTC screen, but the boot image for the rom).
Help would be appreciated
Click to expand...
Click to collapse
The 170 error is normally a USB connectivity issue caused by a bad USB cable or Windows driver problems. You also need to have your bootloader relocked if you are S-ON.
See this post for RUU.exe troubleshooting steps. If you planning to get S-OFF you might be interested in trying my guide.
ramjet73
ramjet73 said:
The 170 error is normally a USB connectivity issue caused by a bad USB cable or Windows driver problems. You also need to have your bootloader relocked if you are S-ON.
See this post for RUU.exe troubleshooting steps. If you planning to get S-OFF you might be interested in trying my guide.
ramjet73
Click to expand...
Click to collapse
Yeah, I've tried it in Relocked status, and still no go. Even under fastboot USB (and I made sure the drivers are there) it won't recognize the phone is attached. I've factory wiped and I'm going to try and re-install the Mikvirgin rom again.
bl4ckllama said:
Yeah, I've tried it in Relocked status, and still no go. Even under fastboot USB (and I made sure the drivers are there) it won't recognize the phone is attached. I've factory wiped and I'm going to try and re-install the Mikvirgin rom again.
Click to expand...
Click to collapse
Have you tried another cable and/or PC?
ramjet73
I had a similar (not identical) problem, and I solved it by pulling the zip out of the exe by letting it run without plugging the phone in and then looking through the folders in my temp folder until I found rom.zip. Renamed it PG86IMG, put it on my sd card, re locked with fastboot, and boom! Phone rescued.
Sent from my Nexus 7 using xda premium
Was finally able to get it loaded with an ICS rom after doing a factory reset, installing the rom, and then manually installing the boot file through fastboot. Maybe I'll try again tomorrow, doing the s-off procedure first Thanks for the input all!
Has anyone had a problem with the windows USB drivers when trying to apply an RUU or an update like RumRunner?
I'm running Windows 8/64 and have been trying to get my EvoLTE to a known "whole" state .. software running 3.17.651.4.710 (rooted/stock as posted elsewhere here), but have been trying to update my radios.
I'd tried returning to a prior version via RUU, but it reports USB driver issues after the first boot when I think it is trying to boot into recovery.
i.e. the phone boots to an HTC logo and stays there until the host times out.
I've tried using RumRunner to get s-off and update the radios that way, but the results are the same.
The USB drivers installed are the ones included with Windroid and otherwise appear to be properly installed (RUU correctly queries the operating version / runrunner reboots the phone to a "ready to receive" mode (presumably through adb).
Any thoughts?
What is your current Hboot & radio version? If you're on the 3.16 update, there is no RUU for either 3.16 or 3.17. Check out my Hboot guide in the top link in my sig-it'll tell you what S-off method to use based on your current Hboot & software version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What is your current Hboot & radio version? If you're on the 3.16 update, there is no RUU for either 3.16 or 3.17. Check out my Hboot guide in the top link in my sig-it'll tell you what S-off method to use based on your current Hboot & software version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Hboot-2.09.0000
Radio-1.12.11.1210
My problem is I'm stuck in some intermediate phase where things like Moonshine and Rumrunner fail after the first adb "boot into receive" command.
satsuke said:
Hboot-2.09.0000
Radio-1.12.11.1210
My problem is I'm stuck in some intermediate phase where things like Moonshine and Rumrunner fail after the first adb "boot into receive" command.
Click to expand...
Click to collapse
Shoot bigdaddy619 a PM. I know he helped somebody find the right drivers for Windows 8 here recently.
You need to use Moonshine, not Rumrunner.
Sent from my HTC EVO 4G LTE
Try this.
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
latest drivers are HERE
ok ,. figured it out
Two things were going on,.
First thing was the adb was essentially broken whenever the phone rebooted without going into the menu and manually selecting "Disk Drive" mode instead of HTC sync .. with all the rebooting I had to reselect this a half dozen times during the process.
The other was a pretty simple problem with moonshine,. the timeout value to return to adb was 60 seconds, too short for the actual boot times.
Rumrunner had timeouts of 120 seconds .. enough time to get through the menus and complete the process.
Anybody here successful in using RumRunner on T-MOBILE HTC-ONE? (with 1.55 HBOOT and 3.24 firmware)?
Steps I performed..
1) Unlocked Bootloader (with HTC DEV)
2) Installed Team Win Recovery
3) Installed SUPER SU from Recovery
4) Using T-Mobile 4.3 ROM (from HTC T-MOBILE RUU)
6) Disabled Firewall (Windows 7)
7) Uninstalled Anti-Virus (Microsoft Security Essentials)
8) Installed HTC Sync (for Drivers only - uninstalled right after)
9) Rebooted PC
10) Disabled Lock Screen (no lock screen on HTC ONE)
11) Made sure fastboot was disabled
12) Made sure usb debugging was enabled
13) Made sure "Verify Apps" was unchecked
14) Made sure "Unknown Sources" was checked
15) Told Super SU to automatically grant super user privileges WITHOUT prompting
16) Ran soju in "administrator" console
It does it's thing and reboots several times but it fails with the following
"FATAL: Download updated package at www.rumrunner.us"
I also tried the same thing with the Android HD Revolution ROM (4.3 - ver 31.6) - fails at the same spot (installed via Recovery). I am able to get to www.rumrunner.us without issues and i'm using ver 0.5..
Note: adb Commands Work, fastboot commands all work..
Same sh*t...cant proceed above this point.
Just did it earlier this week. It ran fine for me.
All I did was unlock, root, done. I was on stock T-Mobile 4.3
Successfully done with the international one :highfive: tough i had some problems on the adb connection. maybe just try to reinstall the drivers..
000zui said:
Successfully done with the international one :highfive: tough i had some problems on the adb connection. maybe just try to reinstall the drivers..
Click to expand...
Click to collapse
Just did one just now actually
1) download the universal option
2) unlock bootloader, twrp and root
3) ran on Linux went through perfectly
FWIW, I had no issues doing it with Windows. T-Mobile (PN07130) [previously] bone stock.
any updates on your side @funks?
@ownmart , @850csi , @omgar , @000zui ??? are you running with hboot 1.55 when you did it?
i have an hboot 1.55 with 3.24 firmware too... same problem.
still cant get past that FATAL error.
tried also all the steps on different PCs.
finding to S-Off this very frustrating. haha.
-SS-
@SilverSamurai have you tried using Linux? That's what @funks did and it worked for him. See my thread about GPE conversion for a link to his post. I was hboot 1.55 and it worked perfectly for me on Windows 7. Are you sure your antivirus/firewall is disabled completely?
Perhaps there's some kind of firewall built into your router or modem that's messing with rumrunner? If you're using different PCs on the same network with that result, this could be what's going on.
Not an expert at all on this, just throwing stuff out there.
SilverSamurai said:
any updates on your side @funks?
@ownmart , @850csi , @omgar , @000zui ??? are you running with hboot 1.55 when you did it?
i have an hboot 1.55 with 3.24 firmware too... same problem.
still cant get past that FATAL error.
tried also all the steps on different PCs.
finding to S-Off this very frustrating. haha.
-SS-
Click to expand...
Click to collapse
Yeah, worked on the international one, hboot 1.55 & win7, don't remember on which fw. Though i had some problems until i uninstalled some Samsung USB drivers..
hi,..
I have an HTC Desire S,and like everyone else I want to upgrade from GB (2.3.5) to ICS (4.0) I downloaded the RUU from here:htcdev.com/devcenter/downloads and I downloaded the WWE one (404mb).
Now I have installed the latest HTC Sync and I got the RUU setup to start and proceed until it gets to the point where it say "sending..." and this process takes forever without changing,the message says at the bottom "Remember,the operation will take about 10 minutes.".
any ideas why it is not completing the setup and stuck at sending,.... ?
help is much appreciated. :angel:
Iby Khan said:
hi,..
I have an HTC Desire S,and like everyone else I want to upgrade from GB (2.3.5) to ICS (4.0) I downloaded the RUU from here:htcdev.com/devcenter/downloads and I downloaded the WWE one (404mb).
Now I have installed the latest HTC Sync and I got the RUU setup to start and proceed until it gets to the point where it say "sending..." and this process takes forever without changing,the message says at the bottom "Remember,the operation will take about 10 minutes.".
any ideas why it is not completing the setup and stuck at sending,.... ?
help is much appreciated. :angel:
Click to expand...
Click to collapse
Do you have the correct fastboot drivers? You can check in your Device Manager to make sure there are no errors there. Also, have you relocked the bootloader? This step is important for most HTC phones for the RUU to run correctly. A possible easier method would be just to download this: https://docs.google.com/file/d/0B-TZlsB2RGXja3d0dnBoRGFOTGc/edit and put it on your external storage without changing the name and then reboot to the bootloader screen and if everything is working right, it should pick up the file and start checking it to make sure everything is in place and then will prompt you to update or cancel. Just let it do it's thing. Alternatively, there is also a way to pick the rom.zip that the RUU extracts when it is preparing itself on your PC from a hidden folder and copy that to a normal folder and run some commands to install from there, but let's check the other methods first...
one more confusen
Thanks for guide! Remember my bootloader is unlocked, hboot version is 2.00.002 and s-on,
Can i install updates on this by ruu?