Database Info

Desire S in one real mess...

Hi all, well i was playing with my Desire S trying to install the generic wwe rom on it since it is brands, and ended up messing up the phone real badly.
Well i used the good old way of creating a gold card and then flash the RUU. The first time went well, i flashed the generic 1.28.401.1 rom on it, retaining the 0002 boot it had.
Then i went to flash the 2.10 wwe RUU and this time things went bad. For some reason the gold card powers were not evoked and it gave me "CID error" but, the all mighty 2.00.0002 hboot was flashed on the phone before it gave the error. So i had to downgrade the bootloader and i used this great guide as a help but once again things went wrong.
I flashed a pre rooted RUU 2.10 rom using 4EXT recovery as the guide tells to do but, i have no wi-fi and usb connection on the rom. This means i got no way to connect the phone to a pc to change the misc_version file and don't even have wi-fi. So i end up asking for any help here as the phone is left in a very bad situation that i can't see the way out...

Try to reflash same ROM again.
Sent from my Desire S

I believe you should have named your thread "I really messed up my Desire S", as the current title is sort of misleading ;-).

In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.

Rapier said:
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Click to expand...
Click to collapse
Well the initial ROM i had on the phone was a branded Vodafone PT and i can't find that ROM anywhere and for some reason goldcards are not working after the bootloader was flashed by the RUU.
I still have the 4EXT recovery and usb works in it. Flashing a ROM via the PG88IMG only works if the RUU has the right CID as the phone is branded, now i don't know if flashing a rooted ROM using that procedure will work. The other thing i may try is flashing an older rooted ROM, like the 1.28.401.1 and see if the wi-fi and usb works.

Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.

smash_07 said:
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
Click to expand...
Click to collapse
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.

Skanob said:
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Click to expand...
Click to collapse
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?

smash_07 said:
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
Click to expand...
Click to collapse
It would really help if you have given your bootloader details.\
Things you still can do:
1. If hboot is updated to 2.00.0002, then you need to unlock it, flash custom recovery via fastboot, flash custom rom, usable phone.
2. If hboot is S-OFF, same as 1 but skip unlocking. Again, usable phone.
Also, there are a lot of ways for you to change your hboot once you are S-OFF. Use search.

You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium

I my case, that was may of this year, I send my desire (not s) back because of bootproblems, and they reflashed it for free. This was in the Netherlands so don't know how easygoing they are in Portugal, but it's worth a shot I guess.

lowveld said:
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Well i can say that this has worked. I flashed the boot.img form the CM7 rom and it worked perfectly, it booted CM7 rom and have wi-fi and usb connection. Now the only thing left is to be able to flash official RUUs passing tne CID error which for some reason the Goldcards are not bypassing.
But many thanks for your help
(ou como se poderia dizer, obrigado pela ajuda)

[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

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.

[Q] ROm Flashing issue

Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks

At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita

timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks

alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk

phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,

phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks

K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk

alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita

That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk