Database Info

DS Bricket by using the S-off to S-on Tutorial

i have go to S-On whit this tutorial
http://forum.xda-developers.com/showthread.php?t=1187231
after i reboot i can only in the bootloader an its say Security warning.
I can not flash a RUU .
The VF Ruu say bootloader version error, and the HTC Ruu say User ID Wrong.
wat can i do?? My device is a VF devices..
or iss the device absolutly Bricket?!
Bootloader Shows:
****Security Warning****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
Radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
edit: i think i need a RUU_Saga_Vodafone_UK_1.47. ROM
****....

Try again and again with that RUU.
It didn't worked first time for me either.
Or try other RUU.
I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release

You should go to fastboot and try RUU

thanks for your answers.
i try it again and again (in fastboot)
it say update from 1.47.161.2
to 1.32.161.1 than it stop into 104 Bootloader Version Error.
I use the VF UK 1.32.161.1
all HTC Europe RUU`s says USER ID Error
before i would go to stock i have installed de Virtuos unity 1.31.
and befor this the VF German 1.47...

Try other RUU's...It has to work, anyway the phone is not bricked....maybe you should try revolutionary to get it S-off again. Don't know if it works if you are in fastboot, but you can try.

I try all the RUU`s and all give me (Device ID ERROR, USER ID ERROR) the Vodafone RUU alone give me the Bootloader Version ERROR...
I Try this again and again and ever it give me this errors.
Can not understand that is not worked...
i think i must really wait for a Vodafone RUU Leak that have the version 1.47.
Revolutionary say ever "waiting for Device" i think it will not work into the Fastboot Mode
I am very happy wen any can help me to make the system run.

i found the debug files of the RUUs and cane see wat he do..
i check and can make Fastboot commands over cmd
like this : fastboot devices
than it give an output like:
SH16KTJ01149 fastboot
wen i use any adb commands it never found the device....
can we any make over the Fastboot commands for fixing my problem?!
Or can we any moddifing the RUUs that this accept my device?!
i have copy two debug messages of the Vodafone RUU and a other:
Code:
<T011153><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{95567211-FFFE-46A1-B012-975D1FD8FE2D}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T011153>
<T011237><DEBUG><OUT>sending 'zip' (268758 KB)... OKAY</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011237>
<T011318><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T011318>
or debug messages like this:
Code:
<T230252><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{FB1AC174-A654-4612-B610-902E97243E0E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T230252>
<T230335><DEBUG><OUT>sending 'zip' (254595 KB)... OKAY</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T230335>
<T230414><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
</DEBUG></T230414>
HTML:
<T011638><DEBUG><OUT>sending 'zip' (254865 KB)... OKAY</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011638>
<T011717><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T011717>

Stuck in bootloader after use the S-off to S-on tutorial
no one can help???
edit: i see that is the exact same problem in this treath : http://forum.xda-developers.com/showthread.php?t=1190050
should i extract the boot.img and recovery.img from the rom.zip (VF Ruu) and install it over Fastboot commands??
i see a topic about this, but it was another htc phone
http://forum.xda-developers.com/showthread.php?t=1168081
can this work ?!
or should iflash CWM over fastboot ?? can i acces than CWM on s-on hboot??
i have backups from my stock rom.

should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.

Silverbullet09 said:
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Click to expand...
Click to collapse
I'm afraid that I don't really know what is the best step for you to do next, so aren't going to offer any advice in case it's incorrect.
Don't buy an xtc either look into the pay as you go xtc option or find someone who owns one near where you live, and pay to use it, should be about a tenth the cost.
See a very old thread that I created regarding the xtc clip http://forum.xda-developers.com/showthread.php?t=1076937
Swyped from HTC Desire S using XDA Premium

Try to use steps 1 - 10 from this guide : http://forum.xda-developers.com/showthread.php?t=1190992

If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.

globatron said:
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
Click to expand...
Click to collapse
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded

@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.

Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
Very glad to hear it
Swyped from HTC Desire S using XDA Premium

Nomader0 said:
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
Click to expand...
Click to collapse
do not use this procedure to s-on your Phone wen it iss branded, and you never have a 1.47 RUU from your Provider.
Your Phone is not Bricked but it will Stock on the bootloader,
i think wen you make a GoldCard before you S-on with this methode you are able to install a 1.47 RUU wen this is avaibled for you.
(I am not Sure, i think this only)
The know way to fixed this Problem wen you will not have a GoldCard will tell you another. Thats not my Fame
I think the best iss all have to wait off a SAFE S-ON methode.
We have not the Vodafone UK RUU can install than its not leaked with Version 1.47.
We have install the HTC Europe RUU with this Versions number on my Phone.
A Super CID let you install all RUU Updates with Version 1.47.Never need a GoldCard for this, wen you have Super CID.
I Know the workaround for this but i will tested this before i post this thing her.
@ben_pyett

so if my phone is not branded=i am super CID?
and it is safe to s-on with this method?

no you must enter the super cid wen you are s-off ...
i think you can go with the tutorial but all HTC RUU Europe for unbranded Phones avaibled.

Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
How to you fixed it ?
my DS work only fastboot cmd
help me, plzz...

poppy8x:
In order to bypass CID errors while flashing a RUU you can try one of two methods:
- If you're still S-OFF, you can change your CID to a SuperCID using fastboot (many guides are available at the HTC Sensation forums). Remember to write down your original CID.
- If you're S-ON already, you can create a goldcard using this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ You can get the SD's CID from another Android phone, doesn't have to be yours. Insert the goldcard before flashing the RUU (and keep it in until the process ends), and you should be good to go.

problems with flashing PG58IMG.zip

I just used htcdev.com to get s-off on my HTC Sensation then if i try to flash PG58IMG.zip I get "Model ID incorrect"

You weren't supposed to unlock that way u should have used revolutionary
Anyways u did go into bootloader to do this right?
Sent from my HTC Sensation Z710e using XDA Premium App

I'm having the same problem here. Model ID is incorrect error. I used HTCdev as well to unlock. But mine also still says S-on.
Sent from my HTC Sensation 4G using xda premium

If I'm correct htcdev won't actually give you full s-off. It's only a partial unlock. If possible try to unlock with revolutionary. I don't see why people use the htcdev when we've already done it.

What PG58IMG are you flashing? Full ROM or something else? More information required!!

use revolutionary to get s-off then flash PG58IMG in hboot

EddyOS said:
What PG58IMG are you flashing? Full ROM or something else? More information required!!
Click to expand...
Click to collapse
I used this PG58IMG provided here http://forum.xda-developers.com/showthread.php?t=1192300
Now when i try to use the revolutionary S-off method it says wrong device with my drivers and such. I'm lost.

Shall we try.... if you install the latest stock ruu and then try to use revolutionary, that might help as you'd flash the hboot which is in the ruu, thus revert back to the original condition of the phone for which the revolutionary tool is designed.
Give it a shot and post back
and install the relevant ruu for your device (unbranded/branded) and if it doesn't work try to flash it trough fastboot

freakzone said:
Shall we try.... if you install the latest stock ruu and then try to use revolutionary, that might help as you'd flash the hboot which is in the ruu, thus revert back to the original condition of the phone for which the revolutionary tool is designed.
Give it a shot and post back
and install the relevant ruu for your device (unbranded/branded) and if it doesn't work try to flash it trough fastboot
Click to expand...
Click to collapse
Tried doing SUPERCID. And i get his error and will not change my CID:
C:\adb>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.094s]
finished. total time: 1.094s

Put the zip on ur sd card -go into fastboot... wanna update-yes. U want to update ur radio... right ?

chiligamba said:
Put the zip on ur sd card -go into fastboot... wanna update-yes. U want to update ur radio... right ?
Click to expand...
Click to collapse
Yup. Done that but it gives me a Model ID incorrect error once i try to update it.

Same problem with HTC S-off.

illuminarias said:
If I'm correct htcdev won't actually give you full s-off. It's only a partial unlock. If possible try to unlock with revolutionary. I don't see why people use the htcdev when we've already done it.
Click to expand...
Click to collapse
Perhaps because we don't want to send phone identifier information to revolutionary to get a beta key.

Bootloop after flashing RUU

Hello everyone
i'm suffering from a very huge problem with my HTC sensation XE since the last october and can't solve it till now and need your help very much
my HTC have a bootloop that does not want to go away even after flashing RUU, i'm sick of it
i also can't get to recovery
HBoot 1.29
i have flashed RUU-Pyramid-LE-ICS-35-hTC-Europe-3.33.401.153-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-281004-signed
and
RUU-Pyramid-LE-ICS-35-hTC-Asia-WWE-3.33.707.106-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-268334-signed
Please help me.

ghallab said:
Hello everyone
i'm suffering from a very huge problem with my HTC sensation XE since the last october and can't solve it till now and need your help very much
my HTC have a bootloop that does not want to go away even after flashing RUU, i'm sick of it
i also can't get to recovery
HBoot 1.29
i have flashed RUU-Pyramid-LE-ICS-35-hTC-Europe-3.33.401.153-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-281004-signed
and
RUU-Pyramid-LE-ICS-35-hTC-Asia-WWE-3.33.707.106-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-268334-signed
Please help me.
Click to expand...
Click to collapse
the bootloader is locked or unlocked?
if it is unlocked then relock it

ghallab said:
Hello everyone
i'm suffering from a very huge problem with my HTC sensation XE since the last october and can't solve it till now and need your help very much
my HTC have a bootloop that does not want to go away even after flashing RUU, i'm sick of it
i also can't get to recovery
HBoot 1.29
i have flashed RUU-Pyramid-LE-ICS-35-hTC-Europe-3.33.401.153-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-281004-signed
and
RUU-Pyramid-LE-ICS-35-hTC-Asia-WWE-3.33.707.106-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-268334-signed
Please help me.
Click to expand...
Click to collapse
Try this command with your terminal (computer) : fastboot flash boot boot.img <---this is the boot.img in the ICS zip file
Sent from my HTC Sensation using xda premium

seb_labine said:
Try this command with your terminal (computer) : fastboot flash boot boot.img <---this is the boot.img in the ICS zip file
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
that's the results
sending 'recovery' (5786 KB)...
OKAY [ 1.504s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
rzr86 said:
the bootloader is locked or unlocked?
if it is unlocked then relock it
Click to expand...
Click to collapse
It is Relocked
any ideas??

ghallab said:
that's the results
sending 'recovery' (5786 KB)...
OKAY [ 1.504s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
It is Relocked
any ideas??
Click to expand...
Click to collapse
S-OFF right?
Sent from my HTC Sensation using xda premium

ghallab said:
that's the results
sending 'recovery' (5786 KB)...
OKAY [ 1.504s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
It is Relocked
any ideas??
Click to expand...
Click to collapse
if you want to use a ruu find the appropiate one
if you aren't supercid then i think the ruu must supports your cid
also do you have htc drivers installed?
for ruu see here
http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98

Solved
seb_labine said:
S-OFF right?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
it was S-ON
rzr86 said:
if you want to use a ruu find the appropiate one
if you aren't supercid then i think the ruu must supports your cid
also do you have htc drivers installed?
for ruu see here
http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
Click to expand...
Click to collapse
i was Supercid before flashing then i changed it to HTC__01 and flashed RUU again and it worked i'm verry happy at last :laugh:
thanks for everyone replied to me

ghallab said:
it was S-ON
i was Supercid before flashing then i changed it to HTC__01 and flashed RUU again and it worked i'm verry happy at last :laugh:
thanks for everyone replied to me
Click to expand...
Click to collapse
Happy to see it worked
Sent from my HTC Sensation using xda premium

[Q] Warranty

So I have an official RUU, No custom recovery but when I go in bootloader it says I have S-OFF. Will this affect my warranty in any way?
EDIT: I tried S-ON By using this method:
http://forum.xda-developers.com/showthread.php?t=1201773
But abd says this:
.....
OKAY [ TIME TAKEN ]
FINISHED. Total time: TIME TAKEN
Thanks in advance

owner eod said:
So I have an official RUU, No custom recovery but when I go in bootloader it says I have S-OFF. Will this affect my warranty in any way?
EDIT: I tried S-ON By using this method:
http://forum.xda-developers.com/showthread.php?t=1201773
But abd says this:
.....
OKAY [ TIME TAKEN ]
FINISHED. Total time: TIME TAKEN
Thanks in advance
Click to expand...
Click to collapse
probably it won't affect your warranty
but take a look here also
http://forum.xda-developers.com/showthread.php?t=1672425 (only step 3.3)
be carefull when returning to S-ON

rzr86 said:
probably it won't affect your warranty
but take a look here also
http://forum.xda-developers.com/showthread.php?t=1672425 (only step 3.3)
be carefull when returning to S-ON
Click to expand...
Click to collapse
I tried that But it returned with:
\Desktop\Sensation files\Android>fastboot oem writesecureflag 3
...
OKAY [ 0.006s]
finished. total time: 0.007s
Edit Nevermind, Will just send it with S-OFF, bootloader says locked so it might seem as if I bought it like that

owner eod said:
So I have an official RUU, No custom recovery but when I go in bootloader it says I have S-OFF. Will this affect my warranty in any way?
EDIT: I tried S-ON By using this method:
http://forum.xda-developers.com/showthread.php?t=1201773
But abd says this:
.....
OKAY [ TIME TAKEN ]
FINISHED. Total time: TIME TAKEN
Thanks in advance
Click to expand...
Click to collapse
If ur bootloader is ublocked ur warranty is void, they say so on htcdev site
Sent from my HTC Sensation XE with beats audio z715e using xda premium

dany xe said:
If ur bootloader is ublocked ur warranty is void, they say so on htcdev site
Sent from my HTC Sensation XE with beats audio z715e using xda premium
Click to expand...
Click to collapse
My bootloader says***LOCKED*** But s-off at the same time

owner eod said:
My bootloader says***LOCKED*** But s-off at the same time
Click to expand...
Click to collapse
Some Sensations shipped like that.
Sent from my GT-P5110 using xda app-developers app

[Q] Trying to get back to stock

Some info
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot getvar version-main
version-main: 2.20.502.7
finished. total time: 0.026s
And I have HBOOT-1.14.0002
I show
TAMPERED
RELOCKED
I can not seem to flash back to stock using htc_one_x_RUU_2.20.502.7_att_us_08022012.exe, it fails.
So then I get the rom.zip file from htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and run...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.983s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.433s
Im guessing this is because I followed the instructions (to relock the bootloader) before I ran htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
What would you recommend as my next step?
Im following this guide http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone

I was able to unlock the bootloader... Now Im stuck here...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.981s]
writing 'boot'...
OKAY [ 1.548s]
finished. total time: 2.531s
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.016s

"Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working due to system.img file being to large."
The error that you are getting seems to be indicative of a known issue. I am sure someone who knows whats up will be along shortly. At least you can take comfort in knowing you are not the only person with this issue. That is when things get scary lol.

Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita

timmaaa said:
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON and I do not have SuperCID.

LanceM said:
I am S-ON and I do not have SuperCID.
Click to expand...
Click to collapse
fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.010s]
finished. total time: 0.010s
fastboot getvar cid
cid: HTC__621
finished. total time: 0.003s

When I try and flash
1.85 or 1.83
I get this error
<T111504><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>

You can't RUU backwards unless you're s-off.
Sent from my Evita

timmaaa said:
You can't RUU backwards unless you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ok Tim... So what do I do to get 2.20 on the phone, stock...

If you're wanting to run the at&t RUU you'll also need the at&t CID. Otherwise you need to run the RUU that corresponds with the HTC__621 CID. Why is it the 2.20 in particular that you want?
Sent from my Evita

Im not stuck on 2.20. I just want the phone back to stock.

Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita

timmaaa said:
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
Click to expand...
Click to collapse
Well, that is my question... What RUU is compatible with my CID? And can I change the CID to work for an AT&T RUU, because it seems like 621 is a tawian RUU. If I can, what do I need to change the CID too?

Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita

timmaaa said:
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
Click to expand...
Click to collapse
No, when I got the phone a while ago, I rooted and superCID'ed it. It was changed to 1111111, but now for some reason it has changed to 621, which I dont quite understand and has caused quite an issue for me trying to go back to stock.

The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita

timmaaa said:
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
Click to expand...
Click to collapse
I bought the phone in San Antonio at an AT&T store.... Way back when the phone just came out...
At that point, after XDA had root and SuperCID, I did those... And put CM10 on it... Through many upgrades and tinkering, somehow the phone got the CID 621. An Asian CID, I did NOT do this.
Regardless, it is fixed now. I followed the instructions in this thread to change the CID back to 1111111. It worked, then what I did was push the recovery and boot from 2.20 to the phone, then re-locked it.
At this point, I ran the 2.20 RUU and it took... Then I ran the 3.18 phone and now... QHSUSB_DLOAD
Off to http://forum.xda-developers.com/showthread.php?t=1966850
Now downloading linux...
I will fix this damn thing lol!

You pulled a classic megadoug. S on super Cid ruu strikes again. JTAG is the only way to fix it now
Sent from my HTC One XL

Yep. S-on + SuperCID + jb RUU = brick. So you'll need a jtag repair. It's worth tying the unbrick method but nine times out of ten it doesn't work.
Sent from my Evita