Database Info

[Q] HBOOT 2.14.0000 Softbrick & no stock RUU

Hey Guys,
So yesterday I decided I wanted to root my HTC One X (Rogers Canada Unlocked) so I followed the tutorials and unlocked the bootloader and went to install CWM recovery. I flashed it via fastboot, then when I restarted into recovery I was in a bootloop saying that this is for development purposes only, and it just kept restarting. So I booted back in to fastboot mode and installed TWRP 3.0.0.0 but the touch controls didnt work, so I reflashed TWRP 3.0.0.1 and the recovery was accessible. I tried to flash a rom and it said it succeeded but it just keeps going into that bootloop and there is no sign of the old stock ROM on the device at all. So I decided today to relock the bootloader, clear the cache and find a Rogers RUU to flash back on the phone with ARUwizard. It fails to install because of a conflict with my bootloader (obviously because mine is 2.14.000) but there is nowhere on the world wide web that has an updated Rogers RUU to flash to my phone. The only good thing that came out of it, is it just stays on the HTC splash screen and doesn't have the red development purposes only writing. I need some help, thanks in advance. If there is anything I missed please let me know.
Phone: HTC One X (Rogers Canada Unlocked) Evita
Bootloader Relocked, S-ON, Hboot 2.14.000
Secondary: HTC Incredible S (Vigin Mobile Canada)
Bootloader Unlocked, S-OFF, C10 ROM

RUU I have found in the past to be more difficult than the root process. make sure drivers installed and usb plugged into the back of pc.
CMW probably corrupt your SD card btw.
Use twrp. And looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1

The problem is that there is no Rogers RUU for the latest hboot (2.14) that the OP is on. For some reason (that I've never completely understood) Rogers firmwares often don't have corresponding RUUs ever released. And he can't use an old RUU, as it fails version check (you can't run an RUU for a firmware version and/or hboot older than what is on the phone). Maybe they will release a Rogers RUU for the firmware that goes with 2.14. But it wouldn't surprise me if they never do.
The TWRP versions mentioned in the OP look wrong. The newest TWRP version is 2.3.3.1, and is supposed to be compatible with 2.14 (although I think some are still having some troubles). I'd start there, by re-unlocking and installing the latest TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
DvineLord posted the recovery img in Post 432.

If the OTA file is a complete zip, with hboot, sbl images, etc. It can be used as an RUU, but it isn't an automated process. as long as you install TWRP, and then install a ROM/kernel, your phone will work again
jjswain, if you need to RUU, find the complete zip OTA package, and follow the steps here http://forum.xda-developers.com/showthread.php?t=1974272
The same can be done in windows, start at step 9

subarudroid said:
looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.

veemodz823 said:
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
Click to expand...
Click to collapse
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now

jjswain said:
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
Click to expand...
Click to collapse
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.

This sounds very similar to the situation I'm in. People have said the reason why there is no touch is because of 3.17 blah blah blah. If you want to read up on where I'm at, here's the link. We're pretty much in the same boat bro.
http://forum.xda-developers.com/showthread.php?t=2102729

absolutelygrim said:
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
Click to expand...
Click to collapse
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue

jjswain said:
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
Click to expand...
Click to collapse
You have to downgrade your hboot to ruu downgrade to get the old firmware

absolutelygrim said:
You have to downgrade your hboot to ruu downgrade to get the old firmware
Click to expand...
Click to collapse
I could use this rom correct? Its based on 3.17
http://forum.xda-developers.com/showthread.php?t=2075783

Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte

Search for TWRP for the HTC One X Evita (the north American model of the HTC one x) and make sure that the version is 2.3.3.1.
Then install Viper XL by Team Venom.
When installing the rom wipe everything that TWRP will let you wipe, then mount the phone as USB storage put the ZIP file on the phone, and then flash it.
If that doesn't work I dunno what will.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
So first you need to flash TWRP for HTC One X evita, you are going to need version 2.3.3.1.
Boot into the new recovery and wipe everything, SD Card, System everything.
Then download Viper XL by Team Venom, go to the mount menu, make sure everything is unchecked, and mount the phone as USB storage and put the rom on the phone.
Flash the rom and you now have a working phone.

jjswain said:
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Click to expand...
Click to collapse
This depends on the network icon set that was flashed with the rom you chose. For some roms, the values are as follows:
E - Extended network
3G - 3G
H - 4G
4G - LTE
On other icon sets, the last one is replaced by LTE - LTE. Some roms will actually let you install/use different network icons, so you could always take a look into something like that.

^what he said ^ also you can go to dialer and *#*#info#*#* go to phone info and see what network your connected to.
Sent from my HOX w/CM10.1

I'm somewhat in the same position as the OP, but every RUU or rom I try fails at signature check (although the latest one posted above seemed to work but then nothing at bootup). Being that I have stock CID ROGER001, and the same HBOOT 2.14 Evita, Radio .23a.32.09.29 and S-ON, is hoping a Rogers RUU is released my only option?
Well given my specs above I can confirm that the Hatka rom works (insofar as it has booted up and I have a phone again!!) Thank you so much for the link jjswain!!

you will only be able to downgrade if you s-off. i assume you are unlocked with twrp or the new cwm flashed if so as long as you wipe first you should be able to flash roms fine unless you are trying to flash non-evita roms for some reason. which roms have you tried flashing and what version of recovery are you using?

So... I had an awkward moment where I began looking at all the roms and seeing that they were all for a OneX not OneXL...:silly: Thanks for asking me to go through those as I probably would not have realized my mistake! Just flashed Viper3.2.6XL and I'm much happier with the look and feel.

I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?

mcnaught82 said:
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
Click to expand...
Click to collapse
You can't root now. There is no root method for jelly bean yet.
Sent from my Nexus 7 using Tapatalk HD

[Q] OTA Updates on rooted, 111111, s-off, custom rom devices?

I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).

Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.

impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off

ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.

myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.

impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?

real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.

impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?

real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.

impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk

He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here

^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.

myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?

Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.

don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?

ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.

Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.

Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).

The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.

If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.

Stuck at boot loop???

Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment

stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.

The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita

timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.

Maybe he meant cm10.2 and it was a typo?
Sent from my Evita

timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.

redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.

stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.

Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse

With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app

Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita

stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.

stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..

martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.

[Q] Soft bricked HTC One S (S4).. Which RUU to use? Have Fastboot Info

Hi everyone..
I am sitting on a One S which has an unlocked bootloader, is not S-off, Hboot 2.15.
Previously was rooted and had Viper Rom installed 3.1, experienced lot of random reboots, tried to go S-OFF with rumrunner and moonshine, without it working.
Tried to return to a nandroid backup (TrickDroid 9.0) but now system is not responding and results in a reboot after 1-2 minutes after rom is booted.
I would like to return to Stock Rom with a RUU, but I can't seem to find the right one and I really need some help..
Even if I found the right one I don't know how to install it because phone keeps rebooting and fastboot doesn't seem to work on Win 8.
HELP!!

Okay. I got fastboot to work on my girlfriends computer and windows 7..
I got the following from running "fastboot getvar all":
Code:
<bootloader> version: 0.5
<bootloader> version-bootloader: 2.15.0000
<bootloader> version-baseband: 1.15.50.05.29
<bootloader> version-spld: None
<bootloader> version-microp: None
<bootloader> version-main:
<bootloader> version-misc: PVT SHIP S-ON
<bootloader> serialno: H*************
<bootloader> imei: 35***********
<bootloader> product: vle
<bootloader> platform: HBOOT-8960
<bootloader> modelid: PJ4010000
<bootloader> cidnum: T-MOB101
<bootloader> battery-statis: good
<bootloader> battery-voltage: 3867mV
<bootloader> partition-layout: Generic
<bootloader> security: on
<bootloader> buildmode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> cimmitno-bootloader: dirty-64bedd38
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt: 0
Which RUU should I get my hands on?
And do I need to run any fastboot commands before I try installing the RUU?

same
i've ****d mine to lmao

I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!

Hammerbak said:
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Click to expand...
Click to collapse
I have not seen a RUU that had a radio version that high. The highest version I have seen is 1.13. I think that's the problem.

Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app

Hammerbak said:
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
Click to expand...
Click to collapse
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005

808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
Click to expand...
Click to collapse
Well, no I'm not in the US. I live in Denmark.
The phone however was bought in Germany 2 years ago, and was delivered from T-mobile I think.
I will give this a try.
However the reason I want to get back to STOCK is due to getting S-OFF.
If I can get the phone working as it is now with TrickDroid 9.0 ROM that would also suffice. At least for quite some time.
The problem I have with the ROM is that "system" stops responding on boot.
I am thinking that this problem could be due to kernel incompatibility because the phone had the Viper One ROM before, which I think flashed another kernel together with the ROM.
Could this be the problem and could it be solved with flashing a new kernel?
However is it possible to flash a kernel without the use of the recovery?
I can't mount the internal memory and the phone has no slot for a SD card
Again.. Thanks!

I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?

808phone said:
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
Click to expand...
Click to collapse
Already did post in there, with no responses so far..
Well I had TrickDroid 9.0 running fine before I updated to Viper One ROM, and this was when problems started happening.
Then I went back with a NAND restore from recovery..
I don't remember flashing the boot.img, as I thought that followed along when I flashed the TrickDroid ROM, but since I think that doing a NAND recovery, doesn't bring a long the kernel I guess that if I installed the kernel from TrickDroid I could get the phone working with this.. What do you think?
Which file contains the kernel..? Is that the boot.img?
Once again, thanks for putting an interest in this post and helping me out! You're a lifesaver so far!

If you are not s-off then you need to flash the boot.IMG.
If you didn't do this, then could be the problem. AFAIK the boot.IMG contains the kernel.
http://forum.cyanogenmod.com/topic/79408-fastboot-flash-boot-bootimg/
Here's another link that might help.
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom/

Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck

Rapier said:
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
Click to expand...
Click to collapse
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD
Rapier said:
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Click to expand...
Click to collapse
Thanks.
There's definitively a lot I will have to work with.
As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you.
I would very much like to get back to TrickDroid first of all, since it's the ROM already installed on the device I think I only have to flash the kernel and then it should be working.
If it is so I can then put Viper One ROM on the phone and flash that using the procedure that you described above.
However I am unable to find the TrickDroid 9.0 ROM since the ROM seems to have gone out of development.. Or at least that is my guess. If I'm lucky I have it somewhere on my old laptop and can get the boot.img from there. And as well I know how fastboot and ADB works, I just need the commands that I will be using.
I will try to find the TrickDroid boot.img and flash that using fastboot and then I will get back to you.
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?

Hammerbak said:
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD...
Click to expand...
Click to collapse
HERE is a list with all RUUs, taken from dev section. Find what you may need
Hammerbak said:
...As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you...
Click to expand...
Click to collapse
No, you don't have a card slot but you should be able to mount the internal memory as an sdcard
Hammerbak said:
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Click to expand...
Click to collapse
Yes, you could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies

Sounds good. I would try and flash that boot.img. I had a similar problem but was able to find an RUU that worked.
Maybe you just missed this part (or not)
Reboot into bootloader
Go into fastboot mode
fastboot flash boot boot.img
fastboot erase cache
Reboot
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
I should point out that I did NOT have success with ViperOneS. It looks awesome and did lots of things well except hold onto calls! Every time I would make a call, it would hang up for no reason. This problem apparently doesn't happen to everyone, but it did to me.
BTW: I have CM11 running so smoothly on my HTC One S. Pretty much all of my major issues are fixed. Only the limitations of google remain.

Rapier said:
HERE is a list with all RUUs, taken from dev section. Find what you may need
Click to expand...
Click to collapse
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
Rapier said:
You could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Click to expand...
Click to collapse
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer..
Another thing I could do would be to go to the HTCDev page and try to unlock the bootloader again..
Which would you recommend?

Hammerbak said:
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer
Click to expand...
Click to collapse
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed). You could even flash an AOSP KK ROM if you like, the same way

Rapier said:
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed)
Click to expand...
Click to collapse
Okay. Just to put in aspect I have the following choices:
Try to gain S-OFF as phone is now with rumrunner or moonshine
Try to get TrickDroid to work by flashing a kernel that is supported
Try to flash Viper and it's kernel from fastboot
If I try to gain S-OFF using rumrunner, do I still need to unlock the bootloader through HTCDevs?
I will try the first mentioned choice first, since gaining S-OFF would ease stuff up quite a bit.
If I can't gain S-OFF using rumrunner I will try to use moonshine.
If that doesn't work either I will be happy with just getting TrickDroid 9.0 to work as a starter.. Step by step procedure to actually gaining a working device firstly.
Then I can start thinking of how to get Viper One working after that or going back to stock to try the S-OFF methods once again.
My list of intentions is to:
Get S-OFF - whether it works or not
Getting the device to be booted and actually perform phone calls and etc.
Research the method and possibilites of getting back to stock to try S-OFF again.
Plan further upgrades to either new ROMs and/or Kernels

I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.

808phone said:
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
Click to expand...
Click to collapse
Okay.
Is was just about to write what you put in your edit. Haha lazy me.. xD
Well I guess as a starter I can go and unlock the bootloader, flash a recovery and try rumrunner.
When I get the recovery working I can start to plan what to do next
EDIT:
Bootloader is unlocked now and for some reason recovery wasn't removed
so I have unlocked bootloader and have a working recovery now.
Will try rumrunner S-OFF now..

[Q] Unable to get in to recovery or install CWM or TWRP

I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.

Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...

I've tried that too, still just reboots as normal.

Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.

HTC One S S4 running Android 4.0.4 ICS

mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all

LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?

mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before

LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.

mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.

LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good: