Originally Posted by eraste

Weird dude, I dunno why it wouldn't take I always do the ruu from fastboot with those three messages at top of my screen.

scribed on my clean one x via tapatalk 2

well i just installed HTC Sync Manager instead of JUST the drivers that BriefMobile links you to

trying it now...and..

Error 132: Signature Error

The ROM Update Utility cannot update your Android Phone

Please get the correct ROM Update Utility and try again.

Originally Posted by eraste

yea i knew it was required before guess they phased it out lol

adb always works without it
but they try to keep it similar to tje fastboot command so they put it

fastboot reboot-bootloader
wont work without it...

Sent from my HTC One X using xda app-developers app

Originally Posted by jakew02

well i just installed HTC Sync Manager instead of JUST the drivers that BriefMobile links you to

trying it now...and..

Error 132: Signature Error

The ROM Update Utility cannot update your Android Phone

Please get the correct ROM Update Utility and try again.

which ruu are u trying to flash...
there isnt a ruu for 2.20 yet...
the patched ruu isnt an ruu....
the signature on it is not correct
the only way u can flash is with s-off

you can get 2.20
by ruu 1.85 then dl and copy the ota .zip someone else extracted put on sdcard
and flash it with stock recovery.

Sent from my HTC One X using xda app-developers app

Unless they want the updated hboot Scott already has the base 2.20 Rom posted in the dev section rooted odexed and deodexed

Sent from my Nocturnalized Beast

I don't have my .bin file on my computer anymore. Any workaround for this? I'm not in a rush to upgrade, but just in case xi or some other rom in the future needs me to follow this before flashing.

Originally Posted by daddioj

if you have a higher hboot. u cant RUU with a lower hboot correct?

Generally this is correct without S-OFF

Originally Posted by marionthebarbarian

I don't have my .bin file on my computer anymore. Any workaround for this? I'm not in a rush to upgrade, but just in case xi or some other rom in the future needs me to follow this before flashing.

You can always do the unlock process up until you get the the token and you will be fine.

Has anyone updated then flashed a ROM? I am having an issue when it flashes. Not sure what it is.



EDIT: It looks like the ROM install freezes at the very end but its finally finishes. Strange!

The new hboot has changed something causing the boot.img to not be written on Custom ROMS.

I am trying to figure out what it is but I am too tired now. I need some sleep.


Can you put something in the OP that states you / I / we would recommend holding off on doing the update until this is figured out. Its going to cause issues.

Having a bit of trouble running the 1.85 RUU. It starts up fine, but part-way through the process I get error 171, stating that I do not have a usb connection to my computer. It then stays on a black screen with the HTC logo, until I reboot the phone back into the bootloader. USB is connected just fine, I have the latest HTC sync installed as well. First time running an RUU so perhaps I am missing something, I did lock the bootloader beforehand.

Looks like I won't be grabbing the OTA anyway once back to stock according to Scott, but already relocked at this point. Any ideas?

Originally Posted by Chrysis

Having a bit of trouble running the 1.85 RUU. It starts up fine, but part-way through the process I get error 171, stating that I do not have a usb connection to my computer. It then stays on a black screen with the HTC logo, until I reboot the phone back into the bootloader. USB is connected just fine, I have the latest HTC sync installed as well. First time running an RUU so perhaps I am missing something, I did lock the bootloader beforehand.

Looks like I won't be grabbing the OTA anyway once back to stock according to Scott, but already relocked at this point. Any ideas?

Make sure you shut down sync

Sent from my ASUS Transformer Pad TF300T using Tapatalk 2