Develop Bugs

S-ON Security Warning, Help

Ok so here is what I did
I unlocked the bootloader through HTCs site
I installed a custom recovery
I installed a custom ROM
S-ON is still there, so I wanted to downgrade to turn S-OFF unfortunately I did the dumbest thing possible and locked the bootloader again attempting to downgrade so I can use revolutionary. Now I have a security warning
I am not exactly sure what to do from this point. The phone is fully functional on a custom ROM but I have no recovery access and I want to install MIUI.
If anyone has an idea I would like to hear it. I went wrong by not downgrading and turning S-OFF before unlocking the bootloader. I just want to know how I can fix this.

Did you revert back to a locked bootloader? If so, just follow the instructions in Development for downgrading .98 bootloader.

sjpritch25 said:
Did you revert back to a locked bootloader? If so, just follow the instructions in Development for downgrading .98 bootloader.
Click to expand...
Click to collapse
Yeah it's not working :-\
It gives an error when it does the fastboot gets stuck on waiting for device, I manually reinstall the verizon rom and it goes to the black HTC screen. Finishes sending and restarts on the custom ROM I already have on there.

Phone is still locked with the security warning. Person using the phone has been using a sense rom, would really like to get rid of a the security warning :|

as long as you re-locked the bootloader you should be able to s-off. What bootloader do they have? If its .98 you will need to downgrade and s-off.

anytime I try to downgrade the phone goes into a bootloop when I run hack-vivow.cmd
if I manually boot it into the bootloader after that, the script says it's sending the files, once it's done and the phone reboots it goes back to the last ROM it was running as if I never did anything :-\

Try a different computer or account. For some reason it wouldn't allow me to run hack_vivow.cmd or whatever on mine, re installed sdk and adb on my laptop and did the drivers, made sure fastboot was off, and it ran perfectly. Now that was me being on 2.3.4 shipped with the .98 bootloader. Now on my pc I went and s-offed because for some reason on my laptop, it wouldn't recognize my device, and then I pushed the recovery and use adb all the time
Sent from my ADR6350 using XDA

Here are the details of what I am dealing with as of now:
S-ON
Custom Recovery is installed
Phone is Rooted
Bootloader is unlocked
Currently on 0.98
ROM is TSM Bullet
I cannot downgrade even if I relock the bootloader, it will install and run the last ROM that was on there. Only ROMs that are signed appear to work and I'm guessing this is because of S-ON. I need to know how I can get S-OFF or even downgrade at this point. I tried every method I could find here and nothing seems to work

you need to relock install ruu 2.3.4 with hboot .98-do this from bootloader(PG32IMG)
THEN RUN DOWNGRADE TOOL
THEN RUN REVOLUTIONARY FOR ROOT AND S-OFF
---------- Post added at 09:57 PM ---------- Previous post was at 09:41 PM ----------
If your on a custom rom you need too go back to stock or downgrade tool won't work.

Seems to be getting stuck at the command reboot fastboot oemRUU

???? download the ruu rename it PG32IMG put on the root of sdcard. make sure the file on the sdcard reads PG32IMG.zip.(exactly)then boot into bootloader, it will pick up the file and run it then ask to proceed, select volume up to continue, it should install up date. if you phone won't let you put it on your sdcard at this point either put it on another card or pull your card put it in an adapter and move to card with your computer.
---------- Post added at 10:27 PM ---------- Previous post was at 10:25 PM ----------
you don't need to use adb to do the ruu

Sorry it's locking up there on the downgrade. I am going to start on another computer and follow the instructions on downgrading. I am back to stock!

ok step one complete
---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------
make sure you put the vivow hack files on the root of C: then type cd cthe file name)

Phone rooted, S-OFF
THANK YOU!!!

YIPEE!!!!

Fastboot not really flashing ?????

Hy everybody,
My hox is like a surprise box.
Yesterday i could not do anything because of empty battery but i fixed it.
And today fastboot seems not to work correctly.
For example, if i try to flash recovery i doesn t change anything. It shows writing sos partition okay and succes.
And when i go to recovery it s stays with the same recovery.The same trouble with flashing boot.
The i try to install a rom over cwm 6 it shows okay but i get stuck a rom bootscreen. If i try to mount usb, it works
then i put a new rom on it after unmounting rom isn t on the internal memory.If i erase anything on my memory over
windows folder and files disapear but on unmouting nothing was deleted.
It s like i dont have any rigths.
I flashed to hboot 1.39 got no trouble and cid is HTC_102.
Does anybody got a solution ?

Can you lock your bootloader?
Try running a RUU. That oughta reset any problems with partition permissions.
Sent from my One X

TToivanen said:
Can you lock your bootloader?
Try running a RUU. That oughta reset any problems with partition permissions.
Sent from my One X
Click to expand...
Click to collapse
Nope when i try to lock it reboots and starts rom instead of going to bootloader and showing relocked

Bloodbreed said:
Nope when i try to lock it reboots and starts rom instead of going to bootloader and showing relocked
Click to expand...
Click to collapse
what is also strange is that i can t erase boot or recovery

is there anyway over gparted to fix partition rights ?

Try using a ruu

Guich said:
Try using a ruu
Click to expand...
Click to collapse
Not sure if it works because i never could install one .
On xda i can t find any working RUU and i think i need a 3.14 RUU do you now
where i can find it please

You can't use RUU if you can't lock the bootloader.
Anyways RUUs here: http://forum.xda-developers.com/showthread.php?t=2104672
Sent from my One X

TToivanen said:
You can't use RUU if you can't lock the bootloader.
Anyways RUUs here: http://forum.xda-developers.com/showthread.php?t=2104672
Sent from my One X
Click to expand...
Click to collapse
that s what i was thinking

Bloodbreed said:
that s what i was thinking
Click to expand...
Click to collapse
AndI guess there is still no apx mode hack tool where i can flash rom from beginning ?

What ROM/kernel have you been running prior to the problem?
---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------
Nevermind, I've seen your posts in Trip's kernel thread. Your HOX is bricked. No solution until we can achieve S-off. Until then you can either wait or send it to repair. You can risk and try to brick your bootloader by trying to relock the bootloader and running RUU (more likely to "avoid" the void warranty so to say but also more likely to be charged for more should they discover you unlocked the bootloader), or just send it as-is.

BlueSingA said:
What ROM/kernel have you been running prior to the problem?
---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------
Nevermind, I've seen your posts in Trip's kernel thread. Your HOX is bricked. No solution until we can achieve S-off. Until then you can either wait or send it to repair. You can risk and try to brick your bootloader by trying to relock the bootloader and running RUU (more likely to "avoid" the void warranty so to say but also more likely to be charged for more should they discover you unlocked the bootloader), or just send it as-is.
Click to expand...
Click to collapse
Thanks for the response.
I m not sure about the bricked device since it boots to android (okay i can not acces to android the user way) but
device seems to connect perfectly to pc with adb and i guess it s just a partition permission that need to be reseted.
Isn t there a way over linux to achieve that?

[Q] How to install Android Revolution HD

Hello,
I've been recently trying to install few times the Android Revolution HD 10.2 ROM however I always fail. Same happened with previous version.
After the ROM installs, i hit reboot and then nothing. It just freezes on the htc logo (with "developer" text) and nothing happens.
So my question is, what am I doing wrong?
I have no problems with installing ViperOne and all of the non-stock based ROMs.
I can't get S-OFF, so I hope it isn't neccessary
Please keep in mind that I'm pretty new at using HTC One m8, however I have experience with android.

If you have the HTC__001 cid or any which is WWE/ Europe you can and MUST flash the firmware.zip for 2.22.401.4 ...otherwise it won't boot or many things will be broken...all necessary things can be found in each Rom thread, how to flash things and what you need etc...Also which recovery do you use and did you flashed a few mods or so afterwards?

One-M8-Master said:
If you have the HTC__001 cid or any which is WWE/ Europe you can and MUST flash the firmware.zip for 2.22.401.4 ...otherwise it won't boot or many things will be broken...all necessary things can be found in each Rom thread, how to flash things and what you need etc...Also which recovery do you use and did you flashed a few mods or so afterwards?
Click to expand...
Click to collapse
Ok, so I don't really know what this CID is. I've seen people talking about this but can't really tell what it is for. Is this some kind of ID a device, for which country it's meant?
You said "flash 2.22.401.4" firmware. Now I would have to find out how to do that (after I do that, will I be able to normally downgrade to 4.4.2 or will there be some problems?)
There's flashtool for Xperia's, Odin for Samsungs and is there a simillar software for HTC devices (I have something called All-In-One_Kit)?
I've seen also something like RUU, but I would need to fix fastboot, as it isn't working after fresh install of Windows.
My CID: HTC_032
Recovery: TWRP 2.7.1.0
Kernel: Unknown, the one that comes with ViperOne (Already tried flashing ARHD with elementaX kernel)
Current version of firmware: 1.54.401.5

mr.loverlover said:
Ok, so I don't really know what this CID is. I've seen people talking about this but can't really tell what it is for. Is this some kind of ID a device, for which country it's meant?
You said "flash 2.22.401.4" firmware. Now I would have to find out how to do that (after I do that, will I be able to normally downgrade to 4.4.2 or will there be some problems?)
There's flashtool for Xperia's, Odin for Samsungs and is there a simillar software for HTC devices (I have something called All-In-One_Kit)?
I've seen also something like RUU, but I would need to fix fastboot, as it isn't working after fresh install of Windows.
My CID: HTC_032
Recovery: TWRP 2.7.1.0
Kernel: Unknown, the one that comes with ViperOne (Already tried flashing ARHD with elementaX kernel)
Current version of firmware: 1.54.401.5
Click to expand...
Click to collapse
Go and read all important guides to how to do that and what you have to do...you really now nearly nothing about those things...so to be in the safe side read all those guides!

One-M8-Master said:
Go and read all important guides to how to do that and what you have to do...you really now nearly nothing about those things...so to be in the safe side read all those guides!
Click to expand...
Click to collapse
Agreed. Messing with things like firmware, without the proper knowledge is a surefire way to brick the phone.
---------- Post added at 02:42 PM ---------- Previous post was at 02:37 PM ----------
mr.loverlover said:
There's flashtool for Xperia's, Odin for Samsungs and is there a simillar software for HTC devices (I have something called All-In-One_Kit)?
I've seen also something like RUU, but I would need to fix fastboot, as it isn't working after fresh install of Windows.
Click to expand...
Click to collapse
RUU isn't going to help you with any of this (s-off, flashing firmware packages, etc.). Its just to restore to a stock image (ROM, radio, hboot, recovery).
I really recommend you get fastboot working. You need adb/fastboot to get s-off anyway.
Toolkits are only of limited use. They don't do anything you can't do manually with a few adb or fastboot commands. And many would say if you can't handle doing these things manually, you shouldn't be messing with the phone at all.

redpoint73 said:
Agreed. Messing with things like firmware, without the proper knowledge is a surefire way to brick the phone.
---------- Post added at 02:42 PM ---------- Previous post was at 02:37 PM ----------
RUU isn't going to help you with any of this (s-off, flashing firmware packages, etc.). Its just to restore to a stock image (ROM, radio, hboot, recovery).
I really recommend you get fastboot working. You need adb/fastboot to get s-off anyway.
Toolkits are only of limited use. They don't do anything you can't do manually with a few adb or fastboot commands. And many would say if you can't handle doing these things manually, you shouldn't be messing with the phone at all.
Click to expand...
Click to collapse
Yeah, I would need RUU to get to stock 4.4.3.
I can't get s-off, firewater isn't working with my phone, and I don't want to choose the paid method, as I will probably soon change this device anyway.

mr.loverlover said:
Yeah, I would need RUU to get to stock 4.4.3.
Click to expand...
Click to collapse
I see what you're saying: RUU to stock, OTA to 4.4.3 to get the firmware package, then unlock bootloader again, install custom recovery and install ARHD.

Exactly, or RUU already to 4.4.3 skipping the ota.
Sent from HTC One m8, or maybe not anymore

mr.loverlover said:
Exactly, or RUU already to 4.4.3 skipping the ota.
Click to expand...
Click to collapse
Are there any 4.4.3 RUUs? More importantly, is there a 4.4.3 RUU for your version?

redpoint73 said:
Are there any 4.4.3 RUUs? More importantly, is there a 4.4.3 RUU for your version?
Click to expand...
Click to collapse
There is no ruu just system dumps/ recovery flashable zip of stock Rom
---------- Post added at 06:30 PM ---------- Previous post was at 06:28 PM ----------
Also there is no need of using a RUU... You can just download the stock Rom zip, flash back stock kernel and stock recovery...but only if that Rom matches your cid...If not you have to take a nandroid backup from Mr hofs collection thread...
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Aaaand to get ota running there is no need for relocked boot loader it will still work

One-M8-Master said:
Aaaand to get ota running there is no need for relocked boot loader it will still work
Click to expand...
Click to collapse
But you do for RUU, which is what I was referring to.

redpoint73 said:
But you do for RUU, which is what I was referring to.
Click to expand...
Click to collapse
Yea okay that's right but as long as there isn't any ruu available we don't need to reliving if we aren't s-off

One-M8-Master said:
Yea okay that's right but as long as there isn't any ruu available we don't need to reliving if we aren't s-off
Click to expand...
Click to collapse
But I want to keep talking about imaginary RUUs
But really, fair enough.

One-M8-Master said:
There is no ruu just system dumps/ recovery flashable zip of stock Rom
---------- Post added at 06:30 PM ---------- Previous post was at 06:28 PM ----------
Also there is no need of using a RUU... You can just download the stock Rom zip, flash back stock kernel and stock recovery...but only if that Rom matches your cid...If not you have to take a nandroid backup from Mr hofs collection thread...
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Aaaand to get ota running there is no need for relocked boot loader it will still work
Click to expand...
Click to collapse
Thank You, You gave me so much information I needed to know more about this device.
I've found a link like this but I can't find my cid
So for example flashing "CID HTC__001" file would brake my device?
P.S. I'm currious what would happen if I flashed wrong CID firmware. Could You tell me more about flashing wrong one. Would it work normally, had some issues, wouldn't boot or wouldn't I be even able to flash this?
EDIT: Hehe, the link I provided is Mr hofs thread. So what now, if my CID isn't there? Can I just use any version that is for Europe, like eg. germany?
EDIT 2: Flashed stock, deodexed ROM 4.4.3, but still no luck with ARHD

mr.loverlover said:
Thank You, You gave me so much information I needed to know more about this device.
I've found a link like this but I can't find my cid
So for example flashing "CID HTC__001" file would brake my device?
P.S. I'm currious what would happen if I flashed wrong CID firmware. Could You tell me more about flashing wrong one. Would it work normally, had some issues, wouldn't boot or wouldn't I be even able to flash this?
EDIT: Hehe, the link I provided is Mr hofs thread. So what now, if my CID isn't there? Can I just use any version that is for Europe, like eg. germany?
EDIT 2: Flashed stock, deodexed ROM 4.4.3, but still no luck with ARHD
Click to expand...
Click to collapse
If you are now s-off just get super cid with fastboot oem writecid 1111111 I hope enough ones xD or just write a cid like HTC__001 ... If you have further questions write me a pm and we can talk over hangouts or pm here... easier to follow the progress

Ok, finally got it.
I had to flash "SkyDragon+M8+Sense+444+Kernel+V2.0.1".
Now it's testing time.
Let's see if this ROM is so good.
EDIT: There's nothing cool in this ROM
Going back to skydragon.

Yea arhd is like stock Rom and yea nothing special about it

Hahaha aww man, do you not read what each ROM does before installing it so you know beforehand what you're getting yourself into?

Nah, I didn't. I saw many people were using it so I thought it must be good, but it isn't (no special features).
However I wanted to learn how to make it work, and I must say that the htc is the weirdest phone I ever had. Flashing a rom can't be done logically, here nothing works as it should in theory
Sent from HTC One m8, or maybe not anymore

I often see people who aren't able to get arhd working...but I really don't know why..the normal cwm recovery doesn't work as it should...use instead twrp or Philz...both are working foo and with Philz backup and restore is working where in twrp most of the m8 are having problems :/ I really don't have problems to install a custom Rom.
I got the phone, tried it one day stock, wanted to get a custom Rom, unlocked boot loader flashed custom recovery and afterwards Rom and elementalx kernel...without problems.. few months later was able to do s-off with sunshine and after that most things where again easier
mr.loverlover said:
Nah, I didn't. I saw many people were using it so I thought it must be good, but it isn't (no special features).
However I wanted to learn how to make it work, and I must say that the htc is the weirdest phone I ever had. Flashing a rom can't be done logically, here nothing works as it should in theory
Sent from HTC One m8, or maybe not anymore
Click to expand...
Click to collapse

HTC One (M8) I stuck at the bootloader. Can someone help me?

my htc one m8 stuck at the bootloader after im trying to flash the stock ruu. right now i cant even go to the recovery. how can i fix this and get it running? before this its run on cyanogenmod 12.1 . i cannot found the right ruu for my htc one m8. please someone help me.
My bootloader is relock cause I'm trying to flash it back to stock. And my software status said modified. My HTC one m8 is also S-ON. How can I start from that?

fitsuhaimi said:
my htc one m8 stuck at the bootloader after im trying to flash the stock ruu. right now i cant even go to the recovery. how can i fix this and get it running? before this its run on cyanogenmod 12.1 . i cannot found the right ruu for my htc one m8. please someone help me.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have, just install adb and fastboot drivers, then plug m8 into pc and enter fastboot mode. Watch from 2:00 https://www.youtube.com/watch?v=9HWj_1KHbuY and do the same
after you do all that, just put some rom into sdcard or usb, and flash it.

fitsuhaimi said:
my htc one m8 stuck at the bootloader after im trying to flash the stock ruu. right now i cant even go to the recovery. how can i fix this and get it running? before this its run on cyanogenmod 12.1 . i cannot found the right ruu for my htc one m8. please someone help me.
My bootloader is relock cause I'm trying to flash it back to stock. And my software status said modified. My HTC one m8 is also S-ON. How can I start from that?
Click to expand...
Click to collapse
You can't find the proper RUU? Did you try to run an RUU not meant for your device? You should just get errors and the process should halt.
What does it say next to "OS" in your bootloader menu? That will tell you your current firmware version. Does it have two different versions with the newer one in red? If so you need to run the RUU again. The first run just updated the hboot.

There's nothing on the os.

Crying

fitsuhaimi said:
There's nothing on the os.
Click to expand...
Click to collapse
Post the results of fastboot getvar all. Edit out your IMEI and serial# from it first. That is private information you should never post on a public forum.

I already PM you the pictures of my phone.

Why can't you write your
hboot no.
version-main no.
CID
MID
here .. so people can help you ?
If you have those data .. check the thread linked in my signature to see whether there is one backup for you or not.
Can't wait for your answer .. need to sleep now .. good luck & good night

ckpv5 said:
Why can't you write your
hboot no.
version-main no.
CID
MID
here .. so people can help you ?
If you have those data .. check the thread linked in my signature to see whether there is one backup for you or not.
Can't wait for your answer .. need to sleep now .. good luck & good night
Click to expand...
Click to collapse
Hboot 3.19
Version-main blank (of course same as OS in bootloader) You need to update your recovery @fitsuhaimi
CID HTC__621
MID 0P6B11000
He has the M8x. 709 firmware. No RUU for that version AFAIK.
---------- Post added at 02:49 PM ---------- Previous post was at 02:36 PM ----------
fitsuhaimi said:
I already PM you the pictures of my phone.
Click to expand...
Click to collapse
Go to @ckpv5's thread. Link here.
You'll need the backup that is 4.24.709.2 (judging from your baseband you are on Lollipop). The 709 part is crucial! That is for your version of M8 and you can't flash a backup (or RUU, or firmware) made for other versions.

Can you tech me step by step what i should do.

im not that good at this kinda thing but im really interested in learning. And also it can save my phone.

xunholyx said:
Hboot 3.19
Version-main blank (of course same as OS in bootloader) You need to update your recovery @fitsuhaimi
CID HTC__621
MID 0P6B11000
He has the M8x. 709 firmware. No RUU for that version AFAIK.
---------- Post added at 02:49 PM ---------- Previous post was at 02:36 PM ----------
Go to @ckpv5's thread. Link here.
You'll need the backup that is 4.24.709.2 (judging from your baseband you are on Lollipop). The 709 part is crucial! That is for your version of M8 and you can't flash a backup (or RUU, or firmware) made for other versions.
Click to expand...
Click to collapse
What's the baseband no. ?
He may need 4.16.709.9 if the baseband is lower than 1.26

ckpv5 said:
what's the baseband no. ?
He may need 4.16.709.9 if the baseband is lower than 1.26
Click to expand...
Click to collapse
1.26.21331147a1.16g

So what should i do now? Please help me :crying::crying::crying:

fitsuhaimi said:
So what should i do now? Please help me :crying::crying::crying:
Click to expand...
Click to collapse
First thing you need to do is update your recovery to TWRP 2.8.7.0.
Then go to the thread I linked you to, and follow the instructions in post #1 (skip the first step~update recovery). You'll need the 4.24.709.2 backup that is in post #3.
You can stop at step 9. You just need the ROM backup and not the stock recovery. After step 9 just reboot.

RUU Error 155 despite relocked bootloader

Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.

RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.

If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers

Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.

Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.

RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456