Database Info

Official T-mobile RUU help

Hello, i'm new guy on this forum. I'm going back from s-off to s-on and official stock t-mobile ruu and i'm using tutorial form this forum. But then i try install RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed i'm getting this ERROR[170]: USB CONNECTION ERROR. But my phone is properly connected, i tried europe ruu(no usb erros), but then i got cid error.
Hboot 0.98.0000
cid t-mob005

Ok, turn in bootloader and now no usb error, but now i'm getting bootloader error 140. Any suggestions?
I'm using this ruu RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
My phone info
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

It seems that you used an European unbranded RUU. To fix you have to create a goldcard, use the 1.47.401.4 RUU again to have a booting system, then change the main version and after that flash the TMOB RUU again
Sent from my HTC Desire S

thanks, but now i got another problem, my phone turn only in bootloader(but i cant see it using adb devices). But i can choose fastboot and then i see my device using fastboot devices. So i'cant get card cid maybe there is another way to get goldcard?

cezzka said:
thanks, but now i got another problem, my phone turn only in bootloader(but i cant see it using adb devices). But i can choose fastboot and then i see my device using fastboot devices. So i'cant get card cid maybe there is another way to get goldcard?
Click to expand...
Click to collapse
Use this to get the CID
Then this to make the GoldCard

Big thanks to amidabuddha. Finally i flashed 1.47.401.4 RUU(phone is booting fine), so how i can change main version to install TMOB RUU?

cezzka said:
Big thanks to amidabuddha. Finally i flashed 1.47.401.4 RUU(phone is booting fine), so how i can change main version to install TMOB RUU?
Click to expand...
Click to collapse
Follow this guide.
When you are done I suggest to fill the offset 00000000 to 00000170 of your sdcard with zeroes (as it was before) because various users reported that running a device with a goldcard inside can cause issues.

amidabuddha said:
Follow this guide.
When you are done I suggest to fill the offset 00000000 to 00000170 of your sdcard with zeroes (as it was before) because various users reported that running a device with a goldcard inside can cause issues.
Click to expand...
Click to collapse
Thanks again ! you and this forum really helped me. Now i got what i wanted

Thanks
amidabuddha said:
Use this to get the CID
Then this to make the GoldCard
Click to expand...
Click to collapse
I've signed up JUST to say thanks for this post. Bacon saved.

Help!?
Im a bit confussed, im desperately trying to get back to stock ics but can work out how, i have what seems to be a rare cid: TMOB005, my phone is S-ON, can i use this method?
Thanks!

im having this exact problem same phone same ruu flashed
amidabuddha said:
It seems that you used an European unbranded RUU. To fix you have to create a goldcard, use the 1.47.401.4 RUU again to have a booting system, then change the main version and after that flash the TMOB RUU again
Sent from my HTC Desire S
Click to expand...
Click to collapse
im having this exact problem same phone same ruu flashed can you please tell me what is the 1.47.401.4ruu please give me a link where to download it also i tried to make a gold card think i did but i dont know how to use it as on my bootloader it dont say update from zip on sd card anymore also its got s-on. please help

[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.

[Q]Odexed stock ROM - 1.22.401.1 + OTA

Hello
I have an HTC one mini, unlocked and rooted.
Unfortunately I don't get to it, to install the OTA.
I've tried the two ROMs
Odexed stock ROM - 1.22.401.1
Deodexed stock ROM - 1.22.401.1
both of JMZ.
That works with the deodexed no OTA, was already aware, but now everything I've tried to install the odexed OTA.
It will me displayed constantly, that there is an OTA.
But when I flash the stock recovery, relock bootloader and the OTA update, start it starts in the recovery, where after a short time, a red exclamation mark appears.
Can someone help me?
My Bootloader:
*** UNLOCKED ***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.19.40d.00.14
OpenDSP-v13.2.0268.0620
OS-1.32.502.3
P.S excuse me my bad English

you cant OTA with a unlocked bootloader as far as i know

correct - you have to revert your phone back to stock in order to receive an update. Simply wait for the latest version to be made into a flash-able ROM on xda.

PuffDaddy_d said:
correct - you have to revert your phone back to stock in order to receive an update. Simply wait for the latest version to be made into a flash-able ROM on xda.
Click to expand...
Click to collapse
i use a rooted Stock odexed ROM from JMZ and stock recovery 1.31.401.1
But if i start the OTA is comes first h**p://cdn.androidpolice.com/wp-content/uploads/2010/07/IMAG0014.jpg but ca. 30 sec later h**p://imageshack.us/a/img547/5011/recovery.jpg (photos are not mine)

Hi Guys,
i have bought as second hand used an htc one mini. I live in Italy, so no Us.
The device report the following info, made by the previous owner:
TAMPERED
RELOCKED
M4_UL PVT S-OFF RL
CID-VODAP102
HBOOT-2.19.0000
RADIO 1.20.40d.00.05
It has TWRP recovery and Android 4.2.2.
I would like to restock it, deleting "tampered" and "relocked"
anybody that can help me please? thank you in advance
C:\ADB-FASTBOOT>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.19.0000
(bootloader) version-baseband: 1.20.40d.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.161.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT386W**********
(bootloader) imei: 35**************
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-99c875bb7f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.100s

If the phone was s-off'ed using revone you can use a command to remove the tapered flag. not sure sure about the relocked flag though. But this has all been discussed before. Search Google "revone" and XDA HTC One mini for s-off threads. It's all there.
Sent from my HTC One using Xparent Green Tapatalk 2

RuffBuster said:
If the phone was s-off'ed using revone you can use a command to remove the tapered flag. not sure sure about the relocked flag though. But this has all been discussed before. Search Google "revone" and XDA HTC One mini for s-off threads. It's all there.
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I don't know how was s-offed ... i bought it as used .... any interesting suggestion to see how was s-offed?

Stefano Pech said:
I don't know how was s-offed ... i bought it as used .... any interesting suggestion to see how was s-offed?
Click to expand...
Click to collapse
Check one of the revone guides on here. There is a file you copy to your phones data folder on your root. Read the revone installation guide and see if the files from the guide were previously copied to your phone. If they are already there, then you should be using revone, if the previous user hasn't wiped the phone clean before selling it.
Else reinstall revone and use the commands provided in guide to remove the offending flags. Again not sure you can change the "relocked" flag.
Sent from my HTC One using Xparent Green Tapatalk 2

RuffBuster said:
Check one of the revone guides on here. There is a file you copy to your phones data folder on your root. Read the revone installation guide and see if the files from the guide were previously copied to your phone. If they are already there, then you should be using revone, if the previous user hasn't wiped the phone clean before selling it.
Else reinstall revone and use the commands provided in guide to remove the offending flags. Again not sure you can change the "relocked" flag.
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
ok...thank you. i will let you know how it goes

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

[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!