Database Info

PLEASE HELP!!! My HTC One X is completely messed up and i would like some help**

Hello everybody i am posting because my One X is messed up. I bought the phone from radio shack and i love it. When i first bought it i rooted it and then downloaded fun root apps like titanium backup, and set cpu. I heard about custom roms and i wanted to try one. So i followed the instructions given on the website. Im sorry i dont remember what website it was that i downloaded it from. So i downloaded Clockworkmod from play store and installed it on my phone. Then copied the rom to my sd card. I tried to flash is but nothing would happen. So i tried to boot into recovery mode and i woould get a legal actions page, then my bootloader would say ***tampered*** ***locked*** ***security warning***. So then i tried to unlock my boot loader via htc dev and i got the error 160 mid not allowed. So i wanted to unroot and restore so i deleted supersu and the su files from my phone and i used root checker to check if unrooted. it said *not properly rooted*. But my phone can still view and download root apps.
Then i tried to restore my phone to stock, but when i pressed factory reset i would get the same legal actions page and my boot loader would say *tampered* *locked* *security warning*. And my att software update doesnt work. when i press on it it says htc dm has stopped and after that it does nothing when i press the button. And many apps close unsuspectingly. I would like to completely revert my phone to stock so i can start over again. thank you.
I have the HTC One X dual core usa version
i bought it at radio shack
It is on AT&T

Sounds like you might have tried to install a rom for the international version. Be thankful it didn't work.
You can't unlock via htcdev without changing your CID because AT&T is blocking it.
The version of CWM in the Play Store (ROM Manager?) is not supported for this phone and will not work.
To restore to stock, you need to flash the RUU for your current version. Check your software version in Settings.

This may come across as rude but you are obviously aware of XDAs existence since you are posting here, why on earth would you do anything to your phone without FIRST checking XDA to make sure it's kosher? I see way too many threads like this and it boggles my mind.
You guys don't want to come to XDA for help with your ROMs and mods, but as soon as you screw something up you come running to us for assistance.
Sent from my HTC One X using xda premium

ewokiscool said:
Hello everybody i am posting because my One X is messed up. I bought the phone from radio shack and i love it. When i first bought it i rooted it and then downloaded fun root apps like titanium backup, and set cpu. I heard about custom roms and i wanted to try one. So i followed the instructions given on the website. Im sorry i dont remember what website it was that i downloaded it from. So i downloaded Clockworkmod from play store and installed it on my phone. Then copied the rom to my sd card. I tried to flash is but nothing would happen. So i tried to boot into recovery mode and i woould get a legal actions page, then my bootloader would say ***tampered*** ***locked*** ***security warning***. So then i tried to unlock my boot loader via htc dev and i got the error 160 mid not allowed. So i wanted to unroot and restore so i deleted supersu and the su files from my phone and i used root checker to check if unrooted. it said *not properly rooted*. But my phone can still view and download root apps.
Then i tried to restore my phone to stock, but when i pressed factory reset i would get the same legal actions page and my boot loader would say *tampered* *locked* *security warning*. And my att software update doesnt work. when i press on it it says htc dm has stopped and after that it does nothing when i press the button. And many apps close unsuspectingly. I would like to completely revert my phone to stock so i can start over again. thank you.
I have the HTC One X dual core usa version
i bought it at radio shack
It is on AT&T
Click to expand...
Click to collapse
First, you need to do A LOT more reading before you try to unlock your bootloader and flash ROMs. You missed a ton of steps and it is pretty clear you didn't do your homework. I am not trying to be rude, but trying to save you from ruining your phone.
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
http://forum.xda-developers.com/showthread.php?t=1671237 (AT&T One X Resources. Pretty much every thing you need)

Butters619 said:
First, you need to do A LOT more reading before you try to unlock your bootloader and flash ROMs. You missed a ton of steps and it is pretty clear you didn't do your homework. I am not trying to be rude, but trying to save you from ruining your phone.
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
Click to expand...
Click to collapse
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?

ewokiscool said:
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?
Click to expand...
Click to collapse
I edited my reply and included two links. First is to the 1.85 RUU. Make sure you don't have 2.20 by going to Settings -> About -> Software Information and look at Software Number. As long as you don't have 2.20, download that RUU, plug your phone in, and run it. IT WILL ERASE EVERYTHING! so make sure to back up the contents of your SD card first.
The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Make sure you read ALL of the instructions first!! And I would recommend CleanROM once you get that far.
Disclaimer: I am not responsible if you mess up your phone.

ewokiscool said:
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?
Click to expand...
Click to collapse
Butters619 said:
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
http://forum.xda-developers.com/showthread.php?t=1671237 (AT&T One X Resources. Pretty much every thing you need)
Click to expand...
Click to collapse
dude.
edit: Whoops! Didn't realize the edit had come afterwards. That was some odd timing.
But seriously, poke around the forums. Things are labeled pretty well around here.

ewokiscool said:
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?
Click to expand...
Click to collapse
Please read and make sure you know what you are doing before you do! I can not stress this enough.
Rooting/unlocking is very easy and take no time at all, but please read.
---------- Post added at 11:23 AM ---------- Previous post was at 11:21 AM ----------
Protogon said:
dude.
edit: Whoops! Didn't realize the edit had come afterwards. That was some odd timing.
But seriously, poke around the forums. Things are labeled pretty well around here.
Click to expand...
Click to collapse
I am just trying to guide him in the right direction. It is up to him to make sure to read everything and know what he is doing to his phone.

Butters619 said:
I am just trying to guide him in the right direction. It is up to him to make sure to read everything and know what he is doing to his phone.
Click to expand...
Click to collapse
It certainly is, but it says something when he asks for this information despite having a large and detailed resource roll-up stickied in the Development forum.

Butters619 said:
I edited my reply and included two links. First is to the 1.85 RUU. Make sure you don't have 2.20 by going to Settings -> About -> Software Information and look at Software Number. As long as you don't have 2.20, download that RUU, plug your phone in, and run it. IT WILL ERASE EVERYTHING! so make sure to back up the contents of your SD card first.
The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Make sure you read ALL of the instructions first!! And I would recommend CleanROM once you get that far.
Disclaimer: I am not responsible if you mess up your phone.
Click to expand...
Click to collapse
before i do anything i want to know if it will work because my software number is: 1.73.502.1

Protogon said:
It certainly is, but it says something when he asks for this information despite having a large and detailed resource roll-up stickied in the Development forum.
Click to expand...
Click to collapse
Yeah he followed a YouTube video and then went straight to Q&A when things went wrong and clearly never stopped by the dev threads once. Perhaps I was being too nice by giving links. Hopefully he shakes that habit quickly.

The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Revise - 4.a Make nandroid backup
:beer::beer:
Sent from my SPH-L710 using xda premium

18th.abn said:
The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Revise - 4.a Make nandroid backup
:beer::beer:
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Good point! I just automatically do that every time I flash a rom so I always forget to include that as an additional step. But that will save a lot of time if anything goes wrong.
---------- Post added at 12:03 PM ---------- Previous post was at 11:53 AM ----------
ewokiscool said:
before i do anything i want to know if it will work because my software number is: 1.73.502.1
Click to expand...
Click to collapse
Although the answer is already in this thread, if I were you, I would take this time to use the search and find out what an RUU is and what it does. You are going to use them many times in the future so might as well know.

This is really starting to become an epidemic
Sent from my One X using xda app-developers app

InflatedTitan said:
This is really starting to become an epidemic
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You should see all the skyrocket users coming to the i777 forums saying they bricked and have no idea why... Probably by flashing a rom for the wrong phone....

Butters619 said:
First, you need to do A LOT more reading before you try to unlock your bootloader and flash ROMs. You missed a ton of steps and it is pretty clear you didn't do your homework. I am not trying to be rude, but trying to save you from ruining your phone.
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
http://forum.xda-developers.com/showthread.php?t=1671237 (AT&T One X Resources. Pretty much every thing you need)
Click to expand...
Click to collapse
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so

ewokiscool said:
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so
Click to expand...
Click to collapse
Did you make sure to use the 1.85 RUU?
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
ewokiscool said:
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so
Click to expand...
Click to collapse
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
ewokiscool said:
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so
Click to expand...
Click to collapse
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.

Butters619 said:
Did you make sure to use the 1.85 RUU?
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.
Click to expand...
Click to collapse
yes i looked at the whole thread and i am !))% sure i downloaded 1.85 i tried your link and looked at the whole thread and bumped the date ahead and rebooted a bunch of times and it didn't work. my error was when i would press att software update, nothing would happen. it would not check for updates or reboot. i tried two other root options like one click root. and another way from the link you sent me. does not work.

ewokiscool said:
yes i looked at the whole thread and i am !))% sure i downloaded 1.85 i tried your link and looked at the whole thread and bumped the date ahead and rebooted a bunch of times and it didn't work. my error was when i would press att software update, nothing would happen. it would not check for updates or reboot. i tried two other root options like one click root. and another way from the link you sent me. does not work.
Click to expand...
Click to collapse
So you run the one click method, it tells you to try to run the AT&T software update, and your phone does nothing? That is what is happening?

Butters619 said:
So you run the one click method, it tells you to try to run the AT&T software update, and your phone does nothing? That is what is happening?
Click to expand...
Click to collapse
yes when i press check for updates nothing happens. im not sure if this is the reason but after the RUU was done and my phone was put back to stock, a popup for att software update came up and it downloaded and i had the update. i went to about then software info the software number is 1.85 so i am very confused.

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

[Q] HTC Sensation totally stock in boot loop

Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.

theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya

AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).

astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s

jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.

astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.

AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.

If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.

astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.

jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb

rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible

Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work

Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.

theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.

theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it

rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.

I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io

Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?

HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.

theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++

CleanROM 7 stuck at splash screen

Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?

It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita

timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:

klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.

Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/

klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.

Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita

Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.

What did you flash?
Sent from my Evita

Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.

timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.

I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita

Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.

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?