Database Info

[SOLVED] Hangs on bootscreen after RUU

Downgrading hboot with this guide ... OK
Used revolutionary ... OK
Use RUU to install RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_382 ... OK
Rebooting ... HANGS
Now i can't enter recovery mode any more. When i try i get a red triangle with an exclamation mark (like this). So i can't boot, but i can't flash a new rom either. The bootloader still says "revolutionary" and S-off.
I have tried booting a couple of times. The phone won't boot even after 2 hours.
Any way to flash a new (custom) rom?

Why did you downgrade only to upgrade later down the line when you're saying you want to install a custom ROM.
If you have your heart set on flashing that RUU do this;
The problem you are having is because you're still on the rev hboot. Flash eng hboot 0.98.2000 (use fastboot) then try the RUU again.
The recovery you are seeing is the stock one.
I'm unsure if flashing a recovery like cwm right now will allow you to flash roms like normal. I assume it will though.
Do some more reading cause you need it.

The phone didn't had the right language (Dutch) so i wanted to flash a new rom.
Before i could flash the rom i needed to downgrade because of the wrong hboot version.
I have downloaded Eng S-off from here. I can boot into fastboot and run that batch?

Problem solved.
Flashed Clockworkmod through fastboot. After that recovery worked again.
I flashed a custom rom this time. That one worked, so i'll stick with that.

[Q] Unable to flash new roms

First some background. I am S-off and currently running cleanrom6 r2. I tried to flash the unoffical cm10.1 but got some errors (can't remember all of it but i think it had something to do with an error code 7?) so I restored my backup from twrp and was able to reboot with no problem. I then decided to try running viperxl 3.27. It says that it installs properly but when I go to reboot it just sits at the htc boot screen with the tamper warning. I have to reboot into recovery and then I can restore to the backup and then it boots fine. I am doing the whole clear cache and system thing before i am flashing the roms. Any ideas?

wmorrow said:
First some background. I am S-off and currently running cleanrom6 r2. I tried to flash the unoffical cm10.1 but got some errors (can't remember all of it but i think it had something to do with an error code 7?) so I restored my backup from twrp and was able to reboot with no problem. I then decided to try running viperxl 3.27. It says that it installs properly but when I go to reboot it just sits at the htc boot screen with the tamper warning. I have to reboot into recovery and then I can restore to the backup and then it boots fine. I am doing the whole clear cache and system thing before i am flashing the roms. Any ideas?
Click to expand...
Click to collapse
What Hboot and what recovery?

exad said:
What Hboot and what recovery?
Click to expand...
Click to collapse
hboot is 1.14.0002 and my recovery is TWRP 2.3.1.0

wmorrow said:
hboot is 1.14.0002 and my recovery is TWRP 2.3.1.0
Click to expand...
Click to collapse
RUU up to 2.14 (3.18 or 3.17, depending on your carrier) Then downgrade the touchscreen firmware (sticky in original android development). I've seen others not able to boot newer AOSP and Sense roms based on 3.17/3.18 unless they are on 2.14 hboot. Why? I'm not sure. But I'm positive it will work after.
When you RUU, since you're S-OFF, no need to change CID or relock the bootloader, in case you didn't know.
You can update TWRP or flash the same one, just don't flash any version above 2.3.3.1 I'm not sure 2.3.1.0 will work (the touchscreen that is) until you downgrade the touchscreen firmware.

exad said:
RUU up to 2.14 (3.18 or 3.17, depending on your carrier) Then downgrade the touchscreen firmware (sticky in original android development). I've seen others not able to boot newer AOSP and Sense roms based on 3.17/3.18 unless they are on 2.14 hboot. Why? I'm not sure. But I'm positive it will work after.
When you RUU, since you're S-OFF, no need to change CID or relock the bootloader, in case you didn't know.
You can update TWRP or flash the same one, just don't flash any version above 2.3.3.1 I'm not sure 2.3.1.0 will work (the touchscreen that is) until you downgrade the touchscreen firmware.
Click to expand...
Click to collapse
I will try this once I get some freetime today. I have never really messed with RUU's. Do you flash them the same way as you would a ROM? Thank you for your help on this.

wmorrow said:
I will try this once I get some freetime today. I have never really messed with RUU's. Do you flash them the same way as you would a ROM? Thank you for your help on this.
Click to expand...
Click to collapse
Download the exe and run it on your PC with your phone plugged in. To say it's simple would be an understatement.

exad said:
Download the exe and run it on your PC with your phone plugged in. To say it's simple would be an understatement.
Click to expand...
Click to collapse
After running the ruu and downgrading the touch screen firmware and then loading the twrp I tried to load Cleanrom and once again got stuck on the htc quietly brilliant screen with red text.

wmorrow said:
After running the ruu and downgrading the touch screen firmware and then loading the twrp I tried to load Cleanrom and once again got stuck on the htc quietly brilliant screen with red text.
Click to expand...
Click to collapse
Weird, what version of TWRP? did you wipe cache, dalvik, system, factory reset prior to flashing?
If so you can try to fastboot flash boot boot.img from cleanrom though you should not have to if you are S-OFF.

exad said:
Weird, what version of TWRP? did you wipe cache, dalvik, system, factory reset prior to flashing?
If so you can try to fastboot flash boot boot.img from cleanrom though you should not have to if you are S-OFF.
Click to expand...
Click to collapse
I'm using 2.3.1.0 and im doing "System", "Factory Reset", Dalvik Cache" and "Cache" in that order.

Hmm, did you check MD5 of twrp before flashing?
Did you check MD5 of Cleanrom before flashing?
If so, I would try flashing TWRP 2.3.3.x and then do fastboot erase cache
then wipe everything in twrp then reflash rom

exad said:
Hmm, did you check MD5 of twrp before flashing?
Did you check MD5 of Cleanrom before flashing?
If so, I would try flashing TWRP 2.3.3.x and then do fastboot erase cache
then wipe everything in twrp then reflash rom
Click to expand...
Click to collapse
Still nothing and i installed 2.3.3.1. Why should I not install 2.5?

wmorrow said:
Still nothing and i installed 2.3.3.1. Why should I not install 2.5?
Click to expand...
Click to collapse
TWRP 2.4+ has issues wiping and leads to the kind of issue you're having now. I'm at a loss.. I'm really not sure why you can't boot. If you're doing everything as directed you shouldn't be having any issues.

exad said:
TWRP 2.4+ has issues wiping and leads to the kind of issue you're having now. I'm at a loss.. I'm really not sure why you can't boot. If you're doing everything as directed you shouldn't be having any issues.
Click to expand...
Click to collapse
I went ahead and wiped the sd card and went step by step from the RUU and I was finally able to get it to load roms again. Thank you very much.

Need help installing RUU, S-off, hboot 2.16

Hi all,
I installed MaximusHD ROM and messed up my partitions so now I have only 2 GB available. I want to fix it by going back to stock ROM.
Currently my phone is superCID, s-off, hboot 2.16, radio 1.20.
From what I've read I should be able to install any RUU but I have not been able to. I tried to do it in fastboot mode and in normal mode when Android is on but without success. Setup starts but some unknown error appears, I think it is error 105... or 150.
I've followed some guides here but the setup won't work because of the unknown error Do I have to look for a specific RUU ?
The only thing that I have not done is to lock my bootloader prior to installing the RUU. However the guides state that I do not have to lock it if my phone is S-OFF.
If I do fastboot getvar all next to "version main" I see nothing, it is empty.
Please help!

I changed my CID to HTC__001 but this did not help Please help me to get back to stock !

mkoev said:
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
Click to expand...
Click to collapse
I had similar issue what I ended up doing was pulling the recovery image out of the install package and flashing it via fastboot and it restored my sd storage I had to use the modified recovery supplied I would try that- I believe you could change your cid to whatever RUU your trying to flash and it should work also,its seems some have downgraded to hboot 2.1.5 to flash RUU (read,read,read)best of luck

Somehow I fixed my problem yesterday. I was not able to install RUU however I was able to change my hboot back to 1.04 ... afterwards I installed the latest version of TWRP and suddenly I was able to see stuff on my internal memory. Prior to that TWRP 2.3.x.x was not able to detect my whole internal memory. Anyway... my advice to people is not to install MaximusHD via CWM although it says that it works. It does work, but it is easier with TWRP

[Q] unalbe to install recovery or reset phone to factory

Hey
[edit]
don't know if i did good or bad, but i installed hboot 2.16 since i want kitkat,
but when i select recovery in the bootloader i still get the constant reboot.
[/edit]
my phone is s-off and super-cid, hboot 1.09, but when i try to install a new version of either CWM or TWRP through their apps, it says installed successfully, but after a reboot i can;t get into recovery - the phone just keeps rebooting.
also - rom manager says i have both installed.
also i can't reset the phone, when i click reset phone in the settings menu, it says it does, but after it reboots - everything is still as it was.
I guess i should not do a factory reset (in hboot menu) unless i have some sort of recovery working?
thanks

OK, all fixed now.
what i did is this:
downgraded to HBoot 2.15
relocked bootloader
installed the 3.16 RUU (only able to do it after the downgrade to 2.15 hboot, and only on one computer - otherwise got error 158)
unlocked the bootloader through HTCDev
installed latest TWRP
tried to load CM without success (didn't read all the instructions)
read all the instructions
flashed the CM boot.img
install CM11 without a problem
hoe this will help someone

how did you go from 2.16 to 2.15?
i'm having a similar issue. http://forum.xda-developers.com/htc-one-s/help/help-load-recovery-boot-rom-hboot-2-16-t2827392
thanks!

[Q] RUU now can't twrp properly

Need some help here please. My phone was running CM11, hboot 2.14 but I had to unlock the phone (locked to Rogers). So I s-off, and RUU the only version there is available. Now the unit is unlocked but running hboot 1.09. I tried flashing twrp so I can install CM back but fastboot say flash successful but won't boot to it in recovery, it boots straight to OS. Something I'm doing wrong? And should I upgrade hboot to 2.14 again? If so, how? Btw, the OS works fine but it'll ask if I want to install OTA but once it reboots, it just goes back to the OS without upgrading.
Thanks

You can find the most recent hboot & how to flash it here - http://forum.xda-developers.com/showthread.php?t=2659091
I found the easiest way was to flash the zip rather than use the FUU but use what works for you

Ahh, found the problem. Didn't know I have to manually reboot it after flashing. Thank you