Database Info

htc one s boots to logo then turns off - need to recover data

Hi, was advised to post here instead as my phone is in fact the HTC One S Model PJ40110.
The issue with the phone is that upon pressing the power button, the phone vibrates, the HTC logo comes on and after about 20 seconds just shuts off. I need to recover some data first, the data from the internal memory not the sd card.
The phone is S-ON
I can get into the hboot menus but not sure on how to proceed to be able to recover the data.
Fixing this for a friend, i dont believe she is capable of rooting.. etc not sure how the phone ended up this way.
Appreciate your guidance

Not sure why you want "the data from the internal memory not the sd card"
You could unlock the bootloader and flash a custom recovery and mount usb storage to copy the pictures and media.
For S4 version of HtC One S
http://forum.xda-developers.com/showthread.php?t=1583427
After that you can run a RUU.exe to return to stock.
You will have to relock the bootloader
fastboot oem lock
Run the RUU when the phone is in bootloader.
http://www.androidruu.com/index.php?developer=Ville

Hi and thanks for the reply.
Basically I want to recover the contacts and any other personal data that was not on the sd card.
Will it be possible with this method or will it just bring the phone to life but wipe the data?

exclusivebiz said:
Hi and thanks for the reply.
Basically I want to recover the contacts and any other personal data that was not on the sd card.
Will it be possible with this method or will it just bring the phone to life but wipe the data?
Click to expand...
Click to collapse
Yes, you are right. When you unlock the bootloader and press "yes" I believe it wipes your phone. Sorry, wasn't thinking about that.
Sorry, couldn't help. There may be some adb commands, to pull the data, but I don't know them.
Contacts would be saved via google though. So not to worry about that.

Is it possible to boot into recovery? Then you could use adb.

I could boot into hboot. Are you referring to that as recovery mode? would you have any steps on using adb for recovering data?
Im not well versed yet with the backend of the android platform.

Some more details on the phone
*** locked ***
vle pvt ship s-on rl
hboot-2.15.0000
radio-1.11.50.05.28
opendsp-v31.1.0.45.0815
emmc-boot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **
(bootloader) imei: **
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: **
(bootloader) battery-status: good
(bootloader) battery-voltage: 4083mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Ive been reading some more on fastboot and tried to give it a go with a clockwork recovery img and "fastboot boot" command.
I get the following
downloading 'boot.img'...
OKAY [ 1.070s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.073s
Is this because S-On? Anyway around it?
What can adb do in regards to recovering data?
Thanks for your help thus far guys.

exclusivebiz said:
I could boot into hboot. Are you referring to that as recovery mode? would you have any steps on using adb for recovering data?
Im not well versed yet with the backend of the android platform.
Click to expand...
Click to collapse
In hboot click on recovery.
With "adb shell" you should have access to the phone. With "adb pull <filename>" you can transfer files to your pc.
Don't know about contacts.
---------- Post added at 07:48 AM ---------- Previous post was at 07:44 AM ----------
exclusivebiz said:
*** locked ***
vle pvt ship s-on rl
...
Ive been reading some more on fastboot and tried to give it a go with a clockwork recovery img and "fastboot boot" command.
I get the following
downloading 'boot.img'...
OKAY [ 1.070s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.073s
Is this because S-On? Anyway around it?
Click to expand...
Click to collapse
This is because the bootloader is locked. You could unlock it at http://www.htcdev.com/ but don't do that. It will erase the phone.

hi, thanks for the reply, i will work on setting this up.
question - how do i know the files names, is there a directory/file listing command so i see everything available that i can "pull"?

hi, so i got into hboot menu then clicked on recovery, waited for the red triangle and finally pressed volume up and power to pull up another menu consisting of the following:
Android system recovery ,3e.
...
reboot system now
apply from sd card
apply from phone storage
apply from cache
wipe data/factory
wipe cache partition
I understand this is the recovery section but when i connect my phone to the computer and run adb devices it shows blank. When i ran adb - s [serial number] shell i get error:device not found.
I did it a few times and one time i got
adb -s [serial] shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
How do i get it to find the device?
Running Win 7 64 bit here

[Q] Please help, I've done something unusual

I've rooted my HTC ONE X (EVITA) with spoof-cid method. Couldn't turn S-OFF. Tried to install roms - didn't like something, wanted to go back to original.
Here when everything went wrong.
While not having any bootable roms,
I've changed CID to "CWS__001" (that was stupid)
Did "fastboot oem lock" (even more stupid)
And here I am - I can boot into fastboot only, no recovery, no rom. Can't flash anything - signature fail.
Fastboot output:
Code:
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v43.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Here is "fastboot getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2B3W304230
(bootloader) imei: 359691049791521
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Is there anything I can try at that point? Also, I have linux on my pc, so, can't run RUU.exe (don't also know if it would help).
Thanks for any help.

Edit: to eliminate confusion, read my post below.

This is a shining example of why you need to actually know what you're doing before doing it.
That link you provided is for the HTC One, you're lucky you haven't bricked your phone. Do you still have the proper Evita hboot etc?
Sent from my Evita

Dimath said:
Did "fastboot oem lock" (even more stupid)
Can't flash anything
Click to expand...
Click to collapse
Of course not. You can't flash anything with a relocked bootloader and S-on. Its the very definition/purpose of a locked/relocked bootloader.
---------- Post added at 10:06 AM ---------- Previous post was at 10:01 AM ----------
timmaaa said:
This is a shining example of why you need to actually know what you're doing before doing it.
Click to expand...
Click to collapse
Agree 110%.
The biggest mistake by the OP was the lack of understanding, research, and knowledge.
I'm guessing the reason for ROMs not originally installing was as simple as a ROM for the wrong device (as the OP seems to be dangerously bouncing around device forums) or just neglecting to extract and flash boot.img manually (required with s-off).
The the subsequent steps of changing CID and relocking the bootloader seem misguided. The only reason to ever relock the bootloader is to run RUU, which OP already says he can't do on his Linux machine, anyway.

redpoint73 said:
Of course not. You can't flash anything with a relocked bootloader and S-on. Its the very definition/purpose of a locked/relocked bootloader.
Click to expand...
Click to collapse
You all are absolutely right - you need to know what you're doing if you don't want to brick the device. And I didn't really research that much.
I've locked the bootloader to flash original, signed image, that was the idea. I feel like I need to clarify what I've actually done:
1. I've got 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.exe from here.
2. Since I have linux, I couldn't just run the RUU.exe. I've used HTC ROM-extractor to convert RUU.exe to RUU.zip.
3. I've flashed the RUU.zip as:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Since the rom has correct signature, it worked on S-ON and signed bootloader. The problem was, I guess, to find the correct RUU (with correct signature), and then to figure out how to flash it on linux. Well, and to know better what I'm doing

Did you have some issue when trying to flash a custom ROM (when you were still bootloader unlocked)? I don't know what "didn't like something" means in the OP.
The fix you are suggesting is complicated and risky. Extracting files from the RUU and manually flashing is very dangerous, unless you know exactly what you are doing. I've seen at least a couple folks on here brick their phones trying something similar.
Did you try both s-off methods (facepalm and Rumrunner)? Rumrunner is supposed to be easier.
Also, there was no reason to have ever changed the CID. RUU can still be run with SuperCID.

3.18 contains 2 rom.zip packages inside the exe. No one really knows why HTC did this and I have no idea what you have created via extracting from the exe.
I would say your 3.18 rom.zip is not correct.
If you want the quickest and easiest way forwards, just run the ruu exe on a Windows machine. I am sure between family, friends and work/school you have access to a Windows XP/Vista/7/8 machine.

twistedddx said:
If you want the quickest and easiest way forwards, just run the ruu exe on a Windows machine. I am sure between family, friends and work/school you have access to a Windows XP/Vista/7/8 machine.
Click to expand...
Click to collapse
That's my thought as well. Windows machines are so common, most people should be able to find one they can use for the purposes of running the RUU. Much easier and safer than what the OP is trying to do.

I just broke the whole phone..

Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>

Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon

thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded 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 which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )

prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded 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 which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon

Stock AT&T XL won't boot after factory reset

I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.

He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)

Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img

I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon

Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?

Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.

I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.

Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon

Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.

Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382

[Q] Rogers HTC One X help with customer recovery issue...

Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?

If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong

nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.

13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved

Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?

audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.

I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!