Database Info

[Q] Sensation Newb- Locked Bootloader 1.23 CM9 Woes

Yes, I am a newb to the Sensation, but not flashing in general. I have previously had hacked SamVibrant, HD2, and most recently, the G2x, so I know from a constant flasher's POV generally what Im doing.
I've been searching for answers to this for days now, and nothing really seems to work, so let me just start with what is going on.
CURRENT STATS:
-PHONE-TMO Sensation 4g
-S-OFF
-ROOTED
-BOOTLOADER-1.23.0000
-RADIO-10.14.9035.01_M
At the top of the bootloader screen it says ****LOCKED**** Which I am guessing is obviously in refrence to the bootloader itself.
Also I currently have the latest 4EXT recovery flashed. When I got the phone it had CWM 5.00.2 or whatever the latest was.
Just bought a Sensation from a guy on Craigslist, and when I got it, it had a CM7 AOSP ROM running on it. I definitely wanted ICS, so I started reading and trying to get it.
So I started here:
http://forum.xda-developers.com/showthread.php?t=1192300&highlight=hboot+1+23
I tried the PG58IMG.zip install via the bootloader, but kept getting errors and security fails. So I researched more and found a post about how to fix that, but the problem is that there is almost always a need to use Revolutionary, and I can't because it doesn't support the 1.23 bootloader.
I have also tried the PG58DIAG via bootloader, and still got mismatch and security errors.
I also just recently tried flashing back to the "REALSTOCKEXPERIENCE" stock ROM which was successful, but it didn't fix my bootloader or unlock woes. Lastly I tried the HTC dev Unlock, and it would not work, because When I got to the part where it attempts to connect to the phone via USB to do get the identifier token it would not connect. It just kept waiting. I tried resetting my phone and reloading the BL but it would not work.
Also I have noticed that I cannot get my phone to connect VIA USB to the PC when in FASTBOOT or Bootloader. Is that normal?
Please help a brother get some ICS on my new phone! I loved my HD2, although it was a bi#$% to flash sometimes, I loved it, and that is why I went with HTC again. This all makes me miss my Vibrant, where you could flash all day long and root without a computer... Good times....

You're already s-off, so most of the work has already been done for you. Make sure you have fast boot unchecked in power options in your current rom. After that, all that's left to do is check your cid. If you're supercid, then grab any 3.32 base firmware from one of the many rom threads in our dev forum, install it via bootloader, remove the firmware file from sd card (do it from pc after you power down the phone), then flash a rom. This will also upgrade your bootloader to 1.27 unlocked and change your radio to the latest. Don't forget to check md5!
If you're not supercid, then you'll need to find kohr-ah's firmware thread because he has corresponding firmware for all cids. Then grab any rom and enjoy.
As for connecting fastboot via USB, you need the htc sync drivers installed on your PC.
Sorry for lack of links. I'm on mobile and searching is a PITA on the phone.
/edit
Make a nandroid backup before you do any of this.

Thanks a bunch. I will give it a go a third time, but that is one of the problems that I am having, is that I can't flash anything via bootloader. I just get tons of errors...
Lets see if the third time is a charm.
EDIT: I still can't use revolutionary for Super CID because the bootloader is 1.23, but I used a Terminal window and the getprop ro.cid/mid and got this:
Cid-T-MOB010.... is this super CID'd?? I was looking for a reference post, but cant remember where I found it before.

no you are not super cid, it would say 111111. But your good everything is already done really.... Go to kor ah's noob friendly firmware thread, find the 3.32 firmware from T-Mobile with the tmobo10 included. Put it on the root if your SD and there you go flash an ics rom. Just remember to delete it after.
Sent from my HTC Sensation Z710e using xda premium

delete this please

wadill said:
no you are not super cid, it would say 111111. But your good everything is already done really.... Go to kor ah's noob friendly firmware thread, find the 3.32 firmware from T-Mobile with the tmobo10 included. Put it on the root if your SD and there you go flash an ics rom. Just remember to delete it after.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
^^ This. Kohr-Ah's thread is the way to go then.
On a side note, you might be able to write supercid after flashing the 1.27 bootloader because the one floating around is already unlocked by revolutionary. Why bother? Because it'll make things easier if we have to upgrade our firmware again in the future.

antiparadigm said:
Thanks a bunch. I will give it a go a third time, but that is one of the problems that I am having, is that I can't flash anything via bootloader. I just get tons of errors...
Lets see if the third time is a charm.
EDIT: I still can't use revolutionary for Super CID because the bootloader is 1.23, but I used a Terminal window and the getprop ro.cid/mid and got this:
Cid-T-MOB010.... is this super CID'd?? I was looking for a reference post, but cant remember where I found it before.
Click to expand...
Click to collapse
Forget Revolutionary. You are already S-OFF so you don't need the tool any more. All you need to do is flash the 3.32 firmware (it comes with HBOOT 1.27, ICS won't boot on 1.23) from >here<, and SuperCID (look here at step 4: http://forum.xda-developers.com/showthread.php?t=1192300).

Okay, I am on the right track now. I hunted and hunted, and finally found a PG58IMG that would flash on my bootloader. That put me on the 1.27 bootloader which allowed me to flash the unlocked 1.17 Bootloader which previously would not flash. now I am trying to get the RUU to flash me back to a non-Rooted ROM so I can reflash the 3.32 and then ICS... Once again, I miss my Vibrant's flashing simplicity... but it will all be worth it.
Thanks for your assistance, everyone with positive non-flaming comments. Expect your thanks buttons to get some love!

Someone else correct me if I'm wrong here due to misunderstanding that last post...
But if you're on the 1.17 bootloader unlocked and everything is smooth there, you should be able to flash the 3.32 firmware right not, then flash whatever ICS ROM you want. The current ROM should have no bearing on this. There is no reason to flash to a non rooted ROM just so you can immediately flash a new ROM.
You just need to have either Clockwork or 4EXT recovery installed to flash the ROM. (And you'll need 4EXT to flash a couple of them. Not all will work with Clockwork)

antiparadigm said:
Okay, I am on the right track now. I hunted and hunted, and finally found a PG58IMG that would flash on my bootloader. That put me on the 1.27 bootloader which allowed me to flash the unlocked 1.17 Bootloader which previously would not flash. now I am trying to get the RUU to flash me back to a non-Rooted ROM so I can reflash the 3.32 and then ICS... Once again, I miss my Vibrant's flashing simplicity... but it will all be worth it.
Thanks for your assistance, everyone with positive non-flaming comments. Expect your thanks buttons to get some love!
Click to expand...
Click to collapse
Thanks for the thanks.
Though once you had the 1.27 revolutionary bootloader, you could've just flashed an ICS rom right then and there and been done with the whole thing. The 1.27 bootloader that's floating around actually comes from the 3.32 (rom base) firmware so you would have been good to go. You really didn't need to revert to 1.17 hboot and flash a non rooted rom.
Don't worry, it really is easy flashing a Sensation, you'll see. It's just that a lot of our guides are outdated and end up confusing people who come into the scene post gingerbread.
/edit
Skipjacks is right. You can go from 1.17 hboot to 1.27 hboot (3.32 rom base firmware) without worrying about your current rom.

I had tried to flash the ICS Rom several times, only to have Boot loops and get stuck. I was following several guides posted here that say that you have to be on a non-rooted rom. I will give it another go to see if there is any change.

That's really weird. Which ICS rom are you trying to flash?
Did you get the T-MOB010 3.32 firmware from here and make sure md5 was correct? This firmware is really the only prerequisite for flashing a 3.32 base ICS rom.
Just keep in mind that 3.32 firmware only works for ICS and will bootloop a gingerbread rom.
There's a really good and simple step by step on how to flash ICS in the first post on the link. Check it out.

OMG It Works! I was boot looping like crazy and could not get anything to boot!
I am not sure but I think the problem may have been the radio, or the wrong Firmware for my CID. My phone would not work with the adb Radio.imgthough so I left it alone.
Correct me if I am wrong on the radio idea, but I flashed the 3.32 and I would get stuck at the White HTC screen. Tried SuperWiping and Flashing three different Roms and no-go.
Then I found this thread:
http://forum.xda-developers.com/showthread.php?t=1459767
I downloaded the right one per my TMO CID and was able to flash it, which also updated the Radio. After another superwipe and Rom Flashing, it worked!
THanks again for all of the help. You are all really appreciated. ALong with this whole community.

Haha that's Kohr-Ah's thread where we were telling you to go to for 3.32 firmware.
Honestly, I'm not really sure what was causing your bootlooping. There's so many little things that could cause a bootloop, it's hard to pinpoint. But hey you've got it running now so it's all good.
Welcome to ICS and welcome to the Sensation community.

Red ! when I tried to flash a custom rom, now I am stuck...

So a few days ago I rushed into using htcdev to unlock my bootloader without fully researching. I then tried to flash: aospX 1.0.0-MR1 in haste. I couldn't use cwm or ext4 because it stated the phone was not rooted. I assumed since I unlocked the bootloader using htcdev that I wouldn't need either for some reason. I tried flashing the rom using the directions found in glevitan's newbie guide: http://dl.dropbox.com/u/30674730/ULTIMATE ACE GUIDE V5.pdf. In the directions that were given on step 5 I just booted in hboot instead of cwm or ext4. So basically what I did is go into hboot and fastboot and tried flashing the boot img.
After that it seemed as though it was flashing but then it went to a picture of a phone with a red exclamation point next to it. Now in the past two days I have been researching how the fix my problem from acting hastily without researching first. None of my research or actions thus far have been able to get me past hboot. I have tried the directions in the following thread and have not been able to fix the issue: http://forum.xda-developers.com/showthread.php?t=1396229
When I try to reinstall recovery by the directions given in that thread nothing really happens and it just goes back to hboot. When I try flashing the Inspire 4g stock rom in the thread I get error messages in hboot that say invalid image! and it will flash to the white HTC splash screen for a few seconds and then vibrate and go black then back to htc splash screen for a few seconds then back to the picture of a cell phone with a red exclamation point next to it.
The only semi-success I have it trying to flash a RUU (RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe)
But when I try to install the RUU it will install for a few minutes but then I get an error message because it is an older version than I have and wont allow me to "downgrade" because I am currently on 3.20
Any help to try to get this phone back up?

Best guess is (and double check first) relock the bootloader and flash the ruu.
Sent from a dream.

Teichopsia said:
Best guess is (and double check first) relock the bootloader and flash the ruu.
Sent from a dream.
Click to expand...
Click to collapse
First thing, thanks for the response.
It wont let me flash the RUU, I have version 3.20.xxxx and the only ruu I can find is older versions and it wont allow me to flash an older version. The bootloader is already relocked btw.

I'll get back to you. I have to finish doing a few things that will take me a few hours or maybe more, then I'll see what I can find.
Sent from a dream.

You have a few options. The exclamation point is because you don't have a custom recovery installed. You have to flash it manually ie fast boot flash recovery recovery.img my guide doesn't cover that as it was written before HTC dev method was available. And those in the inspire land were recommended from flashing the eng hboot.
So anyways. You can flash cwr via fast boot,then attempt to flash aospx. BUT I suggest you actually gain soff.
The 3.20 ruu is available straight from HTC website.

marsdta said:
You have a few options. The exclamation point is because you don't have a custom recovery installed. You have to flash it manually ie fast boot flash recovery recovery.img my guide doesn't cover that as it was written before HTC dev method was available. And those in the inspire land were recommended from flashing the eng hboot.
So anyways. You can flash cwr via fast boot,then attempt to flash aospx. BUT I suggest you actually gain soff.
The 3.20 ruu is available straight from HTC website.
Click to expand...
Click to collapse
Wow can't believe I didn't check there...
Thanks, running the 3.20 ruu at least got me up and running.

Now that your up and running and want to root you should read this.
http://forum.xda-developers.com/showthread.php?t=1839855
As the process is a little different now. Should also check out attn1 site for the kit for any updates

marsdta said:
Now that your up and running and want to root you should read this.
http://forum.xda-developers.com/showthread.php?t=1839855
As the process is a little different now. Should also check out attn1 site for the kit for any updates
Click to expand...
Click to collapse
Thanks that fixed me up. Now rooted and getting ready to flash aospx
EDIT: Got AOSPX running smooth, thanks again!!

[Q] Can not get any Rom or Ruu to flash my soft bricked device

New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL

citats said:
New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
Click to expand...
Click to collapse
Have you tried flashing with an older version of twrp
Verstuurd van mijn HTC One S met Tapatalk

citats said:
New to HTC One S.
Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
Click to expand...
Click to collapse
Use 2.3.3.0 instead...

Thanks guys, I have actually tried 2.3.3.0 due to reading that in another thread. What I see is I can get various aroma installers to start, but at the actual install they seem to fail gaining access to areas on the phone. It's worth mentioning that I have reflashed stock boot img and stock recovery, relocked and attempted various RUU's but I understand that the hboot at 2.15 is most likely why that method fails.
I'm unlocked again but I think I'm going to try reflash stock recovery relock clear and reset all storage etc. then unlock use twrp and re-attempt a flash.
Any suggestions on a rom that should'nt have issues with hboot 2.15?

To flash RUUs you need to be on stock recovery, not custom.
2.15 came with JB. Trickdroid or ViperOneS would be sense roms, else you could flash CM 10.1 or derivates (AOSP/AOKP).
As long as you flash the according kernels in fastboot mode you can also use ICS roms. That doesn't matter.
--- edit
as with 2.15 you could only flash the 3.16 RUU which still isn't available (the one here is for ONE S SE and exits with errors. To flash earlier RUUs you will need an earlier bootloader version. There are two ways: To downgrade bootloader or s-off. As downgrading is a pain you should think about s-off.

Thank You
Yes I was on stock recovery and stock boot img and relocked during that attempt.
does the hboot version matter?
(based upon what I have read it won't flash if my hboot is newer)

Ok, just answered this as edit while you posted. lol

Thank You again!
I have looked into downgrading and a pain might be an understatement I'm looking into the One S toolkit to see what i can do for me... Here's hoping the RUU with hboot 2.15 gets leaked soon.

Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:

rootrider said:
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
Click to expand...
Click to collapse
OK that would be great thanks!
WiL

Holy crap that was painful...
I once again have a rom running! I did so many things but in the end I pushed Energy Rom to the device and it's boot.img after wiping multiple times reformating. Energy Rom is the only one that would complete install without write errors. Very strange stuff but for now i am happy.
Thanks again man!

Damn, I searched this thread for 20 minutes... :cyclops:
Which recovery are you using?
Anyway you should better use TWRP <= 2.3.3.0 for flashing roms.
(gonna write your pm now, will take some time and sorry for the delay!)

I'm all good now. Running Venom and very happy. I appreciate your efforts.
The recovery question tho I had to swap back and forth between twrp 2.3.3.0 and the most recent cwm. Mainly because of I could only send adb via twrp and I could only use adb shell with cwm, the nightmare is over!
Sent from my HTC One S using xda app-developers app

Unable to install ROMs after failed ViperRom Install? Possibly now a paperweight.

Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...

Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.

watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.

Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?

Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.

redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14

Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.

exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".

./

Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.

Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app

exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.

Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app

exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,

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.