Database Info

[Q] Completely Boned - Solved: Was not SuperCID

So I can't figure out how to fix this, and have a completely useless phone at the moment, unfortunately.
I wanted to install Virtuous Inquisition. I was coming from ARHD 4.1.10 Gingerbread. This is the process I followed:
1. Downloaded Firmware and ROM from website.
2. Loaded both onto SDCard
3. Rebooted into recovery, PG58IMG did it's work.
4. Formatted / Wiped all Data
5. Installed Virtuous Inquisition
At this point I was thrown into a continuous boot loop. Read up on the forums, apparently Virtuous is only tested for CWM.
Tried installing CWM - downloaded the zip, renamed it PG58IMG.zip, tossed it onto the phone, gets stuck at "Parsing," and fails.
Tried reinstalling firmware again - Creates error "Wrong CID"
Tried installing CWM from the 1st post of the Sensation Rooting Thread, said "Wrong Version."
Completely confused as to how to fix my phone now.
Please, PLEASE help.
Thanks XDA.

Delete all pg58img.zip from SD card, try to reboot and post result.
Leaving the firmware zip in SD root after update causes boot loops.
Sent from my Pyramid-T

Unfortunately I still get the boot loops -
I get the Virtuous Boot Animation, then it just kills itself.

OK does fastboot work?
Sent from my Pyramid-T

gotpriest said:
Unfortunately I still get the boot loops -
I get the Virtuous Boot Animation, then it just kills itself.
Click to expand...
Click to collapse
Try the virtuous 2.23 thread. It's a 2.3.4 Rom but it comes with its own firmware. See if that boots up before trying anything else.

stringer7 said:
OK does fastboot work?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Unfortunately I'm rather unfamiliar with this term - if you mean can I get into the bootloader, yes, and I can get into 4EXT.
I vaguely remember when rooting my phone that I had to connect it to the computer to do some adb things, but have not tried / done that since.
Currently I have a spare SDCard, and am trying the entire process over real quick, then going to try TC's idea.
Update: Loading the Firmware again still gave me the "CID Incorrect!" error in the bootloader.
Update 2:
tropical cactus said:
Try the virtuous 2.23 thread. It's a 2.3.4 Rom but it comes with its own firmware. See if that boots up before trying anything else.
Click to expand...
Click to collapse
Going to that thread points you to the Virtuous Site - 2.2.0 Rom is Listed, but the Firmware is not bundled. Trying it anyway right now.

gotpriest said:
Unfortunately I'm rather unfamiliar with this term - if you mean can I get into the bootloader, yes, and I can get into 4EXT.
I vaguely remember when rooting my phone that I had to connect it to the computer to do some adb things, but have not tried / done that since.
Currently I have a spare SDCard, and am trying the entire process over real quick, then going to try TC's idea.
Update: Loading the Firmware again still gave me the "CID Incorrect!" error in the bootloader.
Click to expand...
Click to collapse
If you can get into recovery, then all's not lost.
Edit: sounds like you haven't super cided.

gotpriest said:
1. Downloaded Firmware and ROM from website.
2. Loaded both onto SDCard
3. Rebooted into recovery, PG58IMG did it's work.
4. Formatted / Wiped all Data
5. Installed Virtuous Inquisition
Tried reinstalling firmware again - Creates error "Wrong CID"
Click to expand...
Click to collapse
First and foremost, did you do a nandroid backup before you did any of this? If so just revert back.
Next, in step 3, you said you booted into recovery to flash the PG58IMG. You plain can't do that. All firmware updates are done through the bootloader not recovery.
And you also mentioned, wrong CID. Do you recall ever doing a superCID on your phone? If not, read through http://forum.xda-developers.com/showthread.php?t=1459767 to get the correct firmware. IF you go there for the firmware (I suggest 3.24), you do not need superCID on your phone.
GL

Sorry, wrong wording, I did originally do the PG58IMG through Bootloader.
Quite, *quite* stupidly, I only did a Titanium backup, not a nandroid backup.
I have not done SuperCID on my phone.
Working on multiple options you guys have posted at the moment, y'all type too fast for my SDCard switching speeds!
As a side question at the moment, the Virtuous website mentioned that it has only tested through CWM. I was under the impression that 4EXT, while a different interface, behaved and functioned no differently than CWM. I may be wrong on this, but either way, I cannot get CWM to take control. It won't flash in the bootloader (gets stuck at "Parsing") and installing a Zip of it through 4EXT opens it, but does not make it the primary Recovery method

Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Update 2: The Virtuous Boot animation has gotten far enough for the V to begin pulsing. It has never gotten this far. I think it may actually be going through the "initial" boot up sequence. May take a few minutes.

gotpriest said:
Sorry, wrong wording, I did originally do the PG58IMG through Bootloader.
Quite, *quite* stupidly, I only did a Titanium backup, not a nandroid backup.
I have not done SuperCID on my phone.
Working on multiple options you guys have posted at the moment, y'all type too fast for my SDCard switching speeds!
As a side question at the moment, the Virtuous website mentioned that it has only tested through CWM. I was under the impression that 4EXT, while a different interface, behaved and functioned no differently than CWM. I may be wrong on this, but either way, I cannot get CWM to take control. It won't flash in the bootloader (gets stuck at "Parsing") and installing a Zip of it through 4EXT opens it, but does not make it the primary Recovery method
Click to expand...
Click to collapse
I use 4ext for my recovery and works just as well. Just use the firmware in that thread I mentioned. That thread is a great one to read up on. Especially for people who are new to CID terminologies.
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
gotpriest said:
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Click to expand...
Click to collapse
The only thing Nandroids do not back up are radios, SD stuff, kernels,firmware and RIL files. The RIL and Radio's are bundled in the rom itself. So essentially the nandroid backs up the ROM itself. Hope that makes sense.

Hope its working now? My thought was the problem was firmware you flashed originally not supported by your CID = boot loop.
SupwrCID def recommended!
Sent from my Pyramid-T

Jesus Joseph and Mary you guys saved my Bacon. Working Phone. Thanks to all, particularly kpjimmy for the right firmware link!
Lessons Learned:
1. Don't be an Idiot.
2. Murphy is an Asshole
3. Do nandroid backups
4. SuperCID my phone.
5. Stop trying to Flash ROMS on my phone when I haven't slept in 24 hours.
6. Don't be an Idiot.
stringer7 said:
Hope its working now? My thought was the problem was firmware you flashed originally not supported by your CID = boot loop.
SupwrCID def recommended!
Sent from my Pyramid-T
Click to expand...
Click to collapse
Correct, you were on the right track. I have not done SuperCID, so when I installed the Firmware straight from Virtuous, it wasn't T-Mo specific.

gotpriest said:
Update: The T-Mobile specific firmware is successfully installing at the moment. Will remind self to SuperCID ASAP :/
While talking earlier about nandroid backups, I was curious - I thought nandroid only backed up certain things, IE: Not the firmware. Am I incorrect?
Update 2: The Virtuous Boot animation has gotten far enough for the V to begin pulsing. It has never gotten this far. I think it may actually be going through the "initial" boot up sequence. May take a few minutes.
Click to expand...
Click to collapse
Happy for you. We've all been to hell and back before.

tropical cactus said:
Happy for you. We've all been to hell and back before.
Click to expand...
Click to collapse
It actually scared the crap out of me. I switched back and forth between about 5 AOSP ROMS on my MyTouch back in the day, and have done countless ones on my Senny. This was my first firmware update though, so clearly that was the issue - but I should really learn to stop doing these things on weekdays when I urgently need my phone...

Glad it worked. Enjoy VI 3.5. I know I am

gotpriest said:
It actually scared the crap out of me. I switched back and forth between about 5 AOSP ROMS on my MyTouch back in the day, and have done countless ones on my Senny. This was my first firmware update though, so clearly that was the issue - but I should really learn to stop doing these things on weekdays when I urgently need my phone...
Click to expand...
Click to collapse
Been there and done that. Leave the high for the weekend.

Looking for a Rogers RUU

I'm pretty sure I bricked my rogers HTC one X.
Where can I find a Rogers RUU?
I can see a lot of AT&T ones, but not a Rogers one.
Is there one around I can snag?

There's a link posted online. I restored mine last weekend.
Sent from my HTC One X using xda premium

I downloaded the Rogers RUU but it's just full of all the image files it's not an exe...? I'm confused
I can't post the link yet google rogers one x ruu
AT&T and Rogers HTC One X LTE Stock RUU (Evita ROM Update ...
androidromupdate.com/.../att-and-rogers-htc-one-x-... - United Kingdom
4 days ago – This is the original Stock RUU (Rom Update Utility) for HTC One X LTE branded versions released in AT&T USA, Rogers Canada and all other ...
You've visited this page 2 times. Last visit: 16/05/12
That's what it looks like on google
wouldn't let me hyper link
how do you make it an .exe? or do i have the wrong one

http://rapidlibrary.com/files/pj83img-evita-ul-rogers-wwe-1-73-631-1-radio-0-16a-32-09-06-10-81-32-14l-release-254934-signed-zip_ulc8eyefx8i89on.html
Here is the link to the Rogers shipped RUU. I am unsure of how to flash it too.

SiqMawsh said:
http://rapidlibrary.com/files/pj83img-evita-ul-rogers-wwe-1-73-631-1-radio-0-16a-32-09-06-10-81-32-14l-release-254934-signed-zip_ulc8eyefx8i89on.html
Here is the link to the Rogers shipped RUU. I am unsure of how to flash it too.
Click to expand...
Click to collapse
Ya that's exactly the one I have yours Isn't an exe either??

they are more than one way of doing it..but the easiest way I recommend to people who are new.
go through this post.
http://forum.xda-developers.com/showthread.php?t=1656516
download the tool I provided.(made by htc)
follow the steps i method in that post.
you should be able to flash it.

I keep getting error 102 for battery being lower than 30% although it's at 80?

adtoes said:
I keep getting error 102 for battery being lower than 30% although it's at 80?
Click to expand...
Click to collapse
are you using vm?

Not sure why you mean by vm but I did get it working put the phone in fastboot after a wall charge. I didn't think you needed to be in fastboot to use ARU
Thanks for all the help now bootloader says "relocked" lol
Completely back to stock ruu

I was unable to find an EXE, but did find the Rogers ZIP file.
Thanks to PeteHTC I used the file that you guys downloaded and followed this process, worked like a charm...
http://forum.xda-developers.com/showpost.php?p=25732586&postcount=4

Hi everyone,
I'm very new to the unlocking world and I couldn't have a worse start. In fact I have done something really stupid, I have installed a AT&T firmware, the latest, 1.85 on my Rogers HTC One X and even though the phone is working relatively well, I don't have my data plan, I guess because of the firmware.
I have tried to install a RUU, shown in this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says it can't update this ROM, saying this ROM isn't for this phone. It probably because my AT&T firmware.
Is there a way I could install a Rogers Firware back on my HTC One X?
Thanks a lot for your precious help, very appreciated.

Fr33man76 said:
Hi everyone,
I'm very new to the unlocking world and I couldn't have a worse start. In fact I have done something really stupid, I have installed a AT&T firmware, the latest, 1.85 on my Rogers HTC One X and even though the phone is working relatively well, I don't have my data plan, I guess because of the firmware.
I have tried to install a RUU, shown in this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says it can't update this ROM, saying this ROM isn't for this phone. It probably because my AT&T firmware.
Is there a way I could install a Rogers Firware back on my HTC One X?
Thanks a lot for your precious help, very appreciated.
Click to expand...
Click to collapse
I've never been able to get the rogers ruu to work either. my advice... If your unlocked... fastboot flash a custom recovery (twrp) and flash king cobra 1.2 rom found in our dev section.
your data issue is 99.9% of the time a missing apn.
Sent from my HTC One XL using xda premium

Hi ptesmoke,
What do you mean by "Unlocked" are you talking about the bootloader? If yes then I'm not but it won't be aproblem I have unlocked the bootloader a couple of times but for this Rogers RUU it says I need to have the bootloader Locked.
As I said, I'm very new to this world when you tell to fastboot a cutom recovery (twrp) are you talking about something like ClockworkMod Recovery? Is (TWRP) a recovery tool too? I have installed ClockworkMod Recovery into my phone.
Could you please post the link for the king cobra 1.2 file, is there a thread that explain how to flash the ROM?
Thank you very much ptesmoke, very appreciated you help

[deleted]

Before I start, all credit goes to JSLEnterprises. This is his method.:good:
I have a always working method, but requires the following:
1. Either having a Rogers Device, or have Supercid (no area limitations)
2. Locked bootloader (relocked is fine)
3. Drivers that can run fastboot USB (if you can unlock your bootloader, this is not a problem)
The way I got Rogers RUU to work is as follows:
1. open the AT&T RUU .exe
2. after the first window pops out (takes a while cause it need to decompress things), don't continue. Look for C:\Users\(your user name)\AppData (often hidden, change your "folder and search settings" in Organization)\local\Temp. In the Temp folder, search for rom.zip (you don't want to go over every f**king sub-folder, right?)
3. Rename the Rogers RUU zip into rom.zip and replace the rom.zip in Temp folder
4. start your One X into fastboot, connect it to the PC, and it should show "fastboot USB"
5. continue your steps in the AT&T RUU program.
Since you have replaced the AT&T ruu rom with rogers, rogers will be flashed.
Again, all credit goes to JSLEnterprises.
---------- Post added at 09:54 PM ---------- Previous post was at 09:48 PM ----------
Fr33man76 said:
Hi everyone,
I'm very new to the unlocking world and I couldn't have a worse start. In fact I have done something really stupid, I have installed a AT&T firmware, the latest, 1.85 on my Rogers HTC One X and even though the phone is working relatively well, I don't have my data plan, I guess because of the firmware.
I have tried to install a RUU, shown in this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says it can't update this ROM, saying this ROM isn't for this phone. It probably because my AT&T firmware.
Is there a way I could install a Rogers Firware back on my HTC One X?
Thanks a lot for your precious help, very appreciated.
Click to expand...
Click to collapse
You know what? this might be caused by two things.
1. At&t firmware
2. RUU don't usually downgrade stuff....you can only downgrade firmware with RUU when you are in fastboot usb
Get Supercid (I believe there's a one click tool for it...not sure if it works on every firmware though...use the search tool), flash through fastboot usb, and you will be fine.
By the way, instead of using the tool in the link you have (which I think is a stripped down version of RUU.exe), run the original AT&T RUU, and replace the rom.zip in temp (look above)...this works better for me than the stripped down version.

Hi xhao1108,
Thank you very much for your reply.
Actually I haven't flashed an AT&T with a Rogers ROM, it was the opposite. I have a Rogers phone that I have flashed with an AT&T (1.85) ROM and even though the phone works, I can receive and make calls, I don't have access to the data.
The Supercid is to root the phone? I've tried prior to flash my phone and I was able to root it, however with the new firmware I can't find a solution that works.
As for the method you propose, I've tried it but I can't find the rom.zip on my Temp folder, I have changed the folder and search options but no luck.
The problem is that I can't find a RUU from rogers, I have tried with this one on this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says the rom isn't for this device.
I'm quite stuck right now because I can't find a RUU from Rogers, I cant find a proper way to root and I can't even reboot on Recovery. I have installed recovery-clockwork-touch-5.8.3.1-evita-modaco and the process goes well, no error message, so I can't even boot on recovery and flash with the zip file.
Once again, thank you for your time and thank you everyone for the precious help.

Fr33man76 said:
Hi xhao1108,
Thank you very much for your reply.
Actually I haven't flashed an AT&T with a Rogers ROM, it was the opposite. I have a Rogers phone that I have flashed with an AT&T (1.85) ROM and even though the phone works, I can receive and make calls, I don't have access to the data.
The Supercid is to root the phone? I've tried prior to flash my phone and I was able to root it, however with the new firmware I can't find a solution that works.
As for the method you propose, I've tried it but I can't find the rom.zip on my Temp folder, I have changed the folder and search options but no luck.
The problem is that I can't find a RUU from rogers, I have tried with this one on this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says the rom isn't for this device.
I'm quite stuck right now because I can't find a RUU from Rogers, I cant find a proper way to root and I can't even reboot on Recovery. I have installed recovery-clockwork-touch-5.8.3.1-evita-modaco and the process goes well, no error message, so I can't even boot on recovery and flash with the zip file.
Once again, thank you for your time and thank you everyone for the precious help.
Click to expand...
Click to collapse
ppl are telling you to do too many different things.
If you've unlocked before... and yes bootloader, unlock it again.
boot into bootloader once unlocked and fastboot flash TWRP recovery, you can find the thread in the dev section.
Once that's flashed reboot into recovery by completely turning off the phone and powering up with vol down and power. select recovery.
find the menu to mount usb storage device. hook up to pc.
download king cobra 1.2 or any other custom rom you'd like to try, and follow Instructions in the roms thread (usually factory reset, wipe cache and dalvik cache then flash rom)
once that's done reboot system.
WINNING
alternatively you could just add the rogers apn info in the rom you have on there now... then your data would work. But I'd recommend kingcobra, works stellar on rogers.
If your stuck pm me..and ill give u my gtalk info so we can txt.
edit; I'd link you to everything but it's 11pm here and I'm mobile...
Sent from my HTC One XL using xda premium

ptesmoke, you are definitely the man you are my hero and my saver
It worked perfectly, I had installed ClockworkMod recovery and I don't know for which reason I wasn't being able to go on recovery, with TWRP recovery it worked like a charm and I now have my data back.
Once again, a thousand thanks for your precious help. If I can do anything for you don't hesitate, if I can help I'm here.

OK,
I did something really stupid. I was able to flash King Cobra 1.2 and my phone was working just fine but then after I wanted to install Sick Sense but it asked to do a reset factory and wipe system in recovery mode which I did. However, after I've wiped the system I don't have the rom on my sdcard anymore, actually it seems I have only the folder structure but no files in it.
I thought the wipe system would erase my rom on my SDCARD, how I don't know how to put the rom back to be able to flash the rom, when I plug the USB cable it asks me to Format, which I don't do of course but I can't see my phone on the explorer.
Is there a way to push the rom file into the phone other than via the windows explorer?
Thanks for your help.

Fr33man76 said:
ptesmoke, you are definitely the man you are my hero and my saver
It worked perfectly, I had installed ClockworkMod recovery and I don't know for which reason I wasn't being able to go on recovery, with TWRP recovery it worked like a charm and I now have my data back.
Once again, a thousand thanks for your precious help. If I can do anything for you don't hesitate, if I can help I'm here.
Click to expand...
Click to collapse
just hit my thanks button that's all
Fr33man76 said:
OK,
I did something really stupid. I was able to flash King Cobra 1.2 and my phone was working just fine but then after I wanted to install Sick Sense but it asked to do a reset factory and wipe system in recovery mode which I did. However, after I've wiped the system I don't have the rom on my sdcard anymore, actually it seems I have only the folder structure but no files in it.
I thought the wipe system would erase my rom on my SDCARD, how I don't know how to put the rom back to be able to flash the rom, when I plug the USB cable it asks me to Format, which I don't do of course but I can't see my phone on the explorer.
Is there a way to push the rom file into the phone other than via the windows explorer?
Thanks for your help.
Click to expand...
Click to collapse
flash addict already? lol
you should be able to go into twrp recovery, mounts, mount usb storage.
plug into pc, copy rom onto phone.
unmount usb, go back, wipe, flash, profit?
if when mounting your pc says it needs to format the sdcard... don't do it. do it from recovery. ive never tried formatting my sdcard "essentially its just a folder" yet with recovery but it shouldn't break anything.. you'll just lose everything on it.. sounds like you already have though.
Sent from my HTC One XL using xda premium

Please help installing CleanROM 4.5....Stuck in Recovery....

I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!

reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp

thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!

bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.

Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.

bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.

Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!

bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!

Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?

bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.

iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on

trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked

gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.

Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.

You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS

[Q] Changed CID back cannot unlock now

I changed my CID back to CID__001 from superCID and re-locked phone. Now when I go back to unlock with unlock_code.bin it does not work.
So I regenerate a token identifier....
C:\Users\M\HOX>fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO639E7B248BDCAB6CBEA0577A98CD11AD
INFO0B20640D8180AB31F0B0DC2DDC62EB6A
INFO2524B5D27105D40678D5CC2C0E492220
INFO6A98F11162989E19E5F326B78E38D72E
INFO31E8D7A04B433C18C204D007D4B58689
INFO693ABAC1650EB10FC962312231F9E548
INFOF8D103A3EE4DD17F2D807751D006C739
INFO6254FA142E08F7DDBDF777300D8C8BE5
INFO4A6BA0CE58FFAAF25646B8B8A21CF068
INFO50F67F9A30A6DD984D50E497AF32485D
INFOFF19DBAB976D7F81CDC9E8320BD25E9D
INFOA56BB0B240AB81E35CD9742922C28320
INFOC02CF3A74B8589948155024DA23D31EC
INFO7620755FE9B5CA879B4968E79E239B39
INFOBFC9203AD5ED5373F568492B61B20700
INFO0C5B33DEA9E101B475EAF0E3CD4076F7
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Users\M\HOX>
On HTC site I get error code 160 mid not allowed when I try to generate a a new .bin

My Token identifier prior to the change was
<<<< Identifier Token Start >>>>
1A5036DDFCC755FA08619C55D40C47D0
A6FB8A57A0F9482C9174A6FA83921F0A
8D639270F2DCA79AD36FFB093D79F319
B9A66170322959FC5A93C12CB3500DF5
C6D42B624710F209FF4A4B70F5EAA9F3
B1947CFA26A96C7969F2788CAA631583
1C643ED6FEA902F1349AC5219AB8648C
C405010F564F16D1F63E3EA5DE089BE6
02D0CC3CBBFDDBBC74B8844144333E0E
BB70889A1F45259AE20ADCE88E7A201A
CF4BEB1A6F44E3162C63959FB800CF99
1E081824821F45DD2BEC4420A29A8F06
F4271D50F0F124EF324F5E41A34CE420
10572E09220654655A467B7AE1EAFB51
1D52CB57BA7154FB9CAC9F782494AF35
D76D2762018B42BEA736906581D9D1BE
<<<<< Identifier Token End >>>>>

The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.

redpoint73 said:
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
Click to expand...
Click to collapse
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.

ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).

Palmetto_X said:
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
Click to expand...
Click to collapse
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Sent from my HTC One XL using Tapatalk 2

sizemore2000 said:
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Click to expand...
Click to collapse
OP stated in another thread he bought his bootloader unlocked too.
But yes, I agree, there was not point in him relocking it. He wanted to return to stock. I suggested he flash a stock rooted ROM, but he either didn't listen, or was already too far down the relocking path (removed TWRP).

redpoint73 said:
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Click to expand...
Click to collapse
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me

I think you should PILOT the closest vehicle over the phone to end this misery for everyone

954wrecker said:
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
Click to expand...
Click to collapse
Aren't you supposed to be in school?

Palmetto_X said:
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
Click to expand...
Click to collapse
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?

redpoint73 said:
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
Click to expand...
Click to collapse
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
In attempting to fix the RUU problem I have I would flash stock recovery, stock boot.img, relock, try to RUU......my last genius move was rename cid , stock recovery, boot.img, relock...........now I am dead in the water

Palmetto_X said:
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
Click to expand...
Click to collapse
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?

redpoint73 said:
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
Click to expand...
Click to collapse
I just tried it on another PC and got RUU 2.2 to work. Thank you very much for your persistence.

Ouch. 2.20 RUU means you are now stuck with the 1.14 hboot. Fine if you want to stay stock, but a bit of a pain for flashing custom ROMs, as you now have to flash boot.img separately from fastboot. You also can't flash radios now.
1.73 or 1.85 would have been better. Did you try to run those RUUs on this other PC first?

He deserves hboot 1.14 after talking trash earlier. Hopefully he didn't even try the earlier ruu's
Sent from my HTC One XL

Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.

iElvis said:
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
Click to expand...
Click to collapse
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.

so... theres a way to permanently brick your CID to the point where it cant be changed/unlocked again? :/ now i'm REALLY going to read up on how to relock and get my phone back to the 2.20 RUU (came on that, no sense trying to get an earlier one) for selling it....

redpoint73 said:
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
Click to expand...
Click to collapse
I'd like him to root his phone and brick it. Then he can come back here to whine about how crappy the phone is when he's the retard.

SIM unlock didn't work, factory reset wiped everything, phone doesn't boot.

But wait, there's more.
I just exchanged an Xperia S for this HTC One S in excellent condition. It was already bootloader unloked, has TWRP only that it was sim locked. I tried the unlock.sh script (both from terminal emulator, and root explorer) then manually getting the UN_lock_code and subtracting the reversed 7 digits from the IMEI (with the added one), and even the automated app. The script kept running and never show the unlock code, and the one I got using this method wasn't accepted.
Then I thought I should to a factory reset and try again. So I reboot to bootloader, chose factory reset and now everything is wiped. No OS installed so I can't boot, TWRP won't mount USB storage so I can' flash any other rom.
Please help.

Is this a ville or the ville C2?
From your hbot, it seems like C2

42freelancer said:
Is this a ville or the ville C2?
From your hbot, it seems like C2
Click to expand...
Click to collapse
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?

cars ontols
zgomot said:
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
Click to expand...
Click to collapse
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want. As far as SIM unlocking, shouldn't you be S-Off first?
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.

42freelancer said:
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want.
Click to expand...
Click to collapse
How about ViperSC2? Will that do?
42freelancer said:
As far as SIM unlocking, shouldn't you be S-Off first?
Click to expand...
Click to collapse
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
42freelancer said:
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
Click to expand...
Click to collapse
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.

For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
zgomot said:
How about ViperSC2? Will that do?
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
Click to expand...
Click to collapse
Not sure if you saw my last post before this one, I forgot to reply with your quote.

42freelancer said:
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
Not sure if you saw my last post before this one, I forgot to reply with your quote.
Click to expand...
Click to collapse
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.

That seems to be an issue with Windows 8.1. It also seems to be the only OS affecting fastboot. There is a file I used to get all of my drivers working properly, with ADB and fastboot. Fastboot is required with any S-Off attempt. I'll go scope out the file and return here.
---------- Post added at 08:04 PM ---------- Previous post was at 07:59 PM ----------
zgomot said:
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
Click to expand...
Click to collapse
Try this! This should work: http://forum.xda-developers.com/showthread.php?t=2588979
This is what I used last night to reinstall my drivers with working ADB and Fastboot. It also comes with a picture guide on how to fix the device detection. It's fast, easy, lightweight, and best of all, it works!

Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.

Tried that and I still can't get fastboot devices to enumerate my device. Pfffft.

zgomot said:
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Click to expand...
Click to collapse
No sweat. I've got nothing going on later, so I'll do some research for ya! Night

OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?

zgomot said:
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
Click to expand...
Click to collapse
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601

42freelancer said:
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
Click to expand...
Click to collapse
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.

zgomot said:
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
Click to expand...
Click to collapse
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?

42freelancer said:
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
Click to expand...
Click to collapse
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.

zgomot said:
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
Click to expand...
Click to collapse
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess

42freelancer said:
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
Click to expand...
Click to collapse
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.

zgomot said:
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
Click to expand...
Click to collapse
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] http://forum.xda-developers.com/showthread.php?t=2644607 TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.

42freelancer said:
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
Click to expand...
Click to collapse
PROGRESS!
I managed to get S-OFF. Do I try sim-unlocking now, or is there anything else I have to do first?