Database Info

[Q] Please help me fix my sensation xe!

Hi, firstly I apologise for being an idiot.
I rooted my XE last week and have been trying to install ROMs onto it since. I followed numerous guides (not very well apparently) and still cannot get it to work. The problem being every ROM i try to flash after it has installed, during the reboot the white htc screen comes up over and over again.
I've tried numerous ROMs, stock ROMs and nothing has worked. I tried to locate the original backup I made but it seems to be gone too
Any help would be appreciated, otherwise I've blown a couple of hundred quid.

Do you know how to run a log cat and post the results as this would help people help you better. But then again there is always the option to just download the correct RUU for your Sensation, flash the stock ROM with it, and then start all over.

T-Macgnolia said:
Do you know how to run a log cat and post the results as this would help people help you better. But then again there is always the option to just download the correct RUU for your Sensation, flash the stock ROM with it, and then start all over.
Click to expand...
Click to collapse
What / how would I start all over if I had the correct RUU and ROM (both of which I think I have). The RUU is an exe file? Is that correct and the ROM I just put on the root of my SD?
Grrrrr. I feel very stupid, usually nae bad at techy stuff!

Yes the RUU is a .exe file that will flash the stock ROM to your Sensation, notice I said stock ROM wich means you will not be rooted anymore, you will have the stock recovery again, and you will more than likely be S-on again. This is why I said you would have to start over again if you use the RUU.
The ROM does go on your SD card but if it is a stock ROM you will have to have the stock recovery to flash it, if it is a custom ROM you will have to have S-off and a custom recovery.

T-Macgnolia said:
Yes the RUU is a .exe file that will flash the stock ROM to your Sensation, notice I said stock ROM wich means you will not be rooted anymore, you will have the stock recovery again, and you will more than likely be S-on again. This is why I said you would have to start over again if you use the RUU.
The ROM does go on your SD card but if it is a stock ROM you will have to have the stock recovery to flash it, if it is a custom ROM you will have to have S-off and a custom recovery.
Click to expand...
Click to collapse
So apparently I have the wrong RUU? How would I find out which is the correct one?
Thanks for your help and patience so far!

Have you made sure you have the correct firmware for the Rom you are trying to install?
Sent from my HTC Sensation XE with Beats Audio using xda premium

radixon said:
Have you made sure you have the correct firmware for the Rom you are trying to install?
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Yeah I'm pretty sure it is! PG58IMG?
When I run the RUU it comes up with current image version: 1.73.401.2
Then when it goes to update the ROM it comes up saying unknown error 155, wrong RUU???

It sounds like you may have the wrong RUU, who is your carrier and what is the region did your Sensation originate from. This is the information you need to get your correct RUU.

T-Macgnolia said:
It sounds like you may have the wrong RUU, who is your carrier and what is the region did your Sensation originate from. This is the information you need to get your correct RUU.
Click to expand...
Click to collapse
It is unlocked from the UK, probably 02 but unlocked as I said, using an orange sim. Where could I find this info?

lewento said:
It is unlocked from the UK, probably 02 but unlocked as I said, using an orange sim. Where could I find this info?
Click to expand...
Click to collapse
Ok if it is from the UK you probably need the "RUU_Pyramid_O2_UK_1.34.206.1_Radio_10.43a.9007.00U_10.51.9007.27_M", you can find it here. Remeber you will have to have the HTC Sync drivers installed on your computer, and you will have to boot into the Hboot then the bootloader and connect your Sensation via USB to your computer before running the RUU.

Accidently flashed stock recovery Help

I just picked up a one x today for att I was able to root it but not unlock my bootloader at the htcdev site. I downloaded rom toolbox and flashed twrp recovery thinking it was like my galaxy note and all would be fine. But now I cant get past the bootloader. I'm on 1.85 and when I go to flash the RUU I get error 170 no connection. I can use fastboot commands so i know my PC is picking up the phone. Can I just reflash 1.85 stock recovery to get it to boot? I cant find stock recovery image anywhere. I've tried every RUU I could find and nothing works. The only thing I've done to it was root, no unlocked bootloader or supercid. What else can I try?

shigga said:
I just picked up a one x today for att I was able to root it but not unlock my bootloader at the htcdev site. I downloaded rom toolbox and flashed twrp recovery thinking it was like my galaxy note and all would be fine. But now I cant get past the bootloader. I'm on 1.85 and when I go to flash the RUU I get error 170 no connection. I can use fastboot commands so i know my PC is picking up the phone. Can I just reflash 1.85 stock recovery to get it to boot? I cant find stock recovery image anywhere. I've tried every RUU I could find and nothing works. The only thing I've done to it was root, no unlocked bootloader or supercid. What else can I try?
Click to expand...
Click to collapse
I guess it's a little late now, but you need to get SuperCID before you can unlock via HTC dev because the AT&T one is blocked and you need to have your bootloader unlocked before flashing a custom recovery. Also, I'm trying to avoid any flaming, but a little reading would have taken you a long way in this case.
Here is a thread where someone did the same thing:
http://forum.xda-developers.com/showthread.php?t=1846507
Edit: Also, isn't Rom Toolbox only for the international One X? You need to stay in this sub forum or you are going to do that again.

Butters619 said:
I guess it's a little late now, but you need to get SuperCID before you can unlock via HTC dev because the AT&T one is blocked and you need to have your bootloader unlocked before flashing a custom recovery. Also, I'm trying to avoid any flaming, but a little reading would have taken you a long way in this case.
Here is a thread where someone did the same thing:
http://forum.xda-developers.com/showthread.php?t=1846507
Edit: Also, isn't Rom Toolbox only for the international One X? You need to stay in this sub forum or you are going to do that again.
Click to expand...
Click to collapse
I actually figured it out. I was using the adb driver from my sony tablet had to install the htc ones manually.

You need to have bootloader unlocked in order to flash a custom recovery. Bootloader unlock requires SuperCID.
As another indicated, ROM Toolbox is not for the AT&T version of the One X. Don't use it. Don't use anything that isn't in the forum for the AT&T version. Flashing things meant for the international One X won't work (completely different hardware), and might brick the device. Only flash things listed here: http://forum.xda-developers.com/showthread.php?t=1671237

[Q] help rooting htc one xl cid -622

hi
i have a cid of htc-622 which is asia -hong kong
software number is 3.17.708.5
evita pvt ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
open dsp-v31.1.0.45.0815
can i follow this guide?
http://forums.team-nocturnal.com/showthread.php/1147

No. Just unlock your boot loader with htcdev.com and flash twrp 2.3.3.1
Sent from my One X using xda app-developers app

exad said:
No. Just unlock your boot loader with htcdev.com and flash twrp 2.3.3.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
thanks for the quick response
in this thread
http://forum.xda-developers.com/showthread.php?t=1677447
it says i have to be rooted to install the recovery?
is there an easy way to root?

emu123 said:
thanks for the quick response
in this thread
http://forum.xda-developers.com/showthread.php?t=1677447
it says i have to be rooted to install the recovery?
is there an easy way to root?
Click to expand...
Click to collapse
You need an unlocked bootloader to install recovery, not root.
As per AT&T, HTC blocks bootloader unlocks for AT&T customers. To do this, HTCDEV.com blocks any requests for bootloader unlocks which have an AT&T CID.
Because of this, for AT&T customers only, one must change their CID in order to trick HTCDEV.com into allowing a bootloader unlock.
To gain write access to the file that needs changing to spoof the CID, you need root access.
So what this means:
To flash recovery, you need bootloader unlocked, not root.
But because AT&T OneXLs needs to spoof the CID before unlocking the bootloader, they require root.
For AT&T > Root > SuperCID > Unlock bootloader > Flash twrp
For everyone else Skip right to > Unlock bootloader > Flash twrp
Because you do not have an AT&T phone, you will have no problems unlocking the bootloader to flash a custom recovery.
At first, things can be confusing because many posts don't really make a point of saying that those steps are only needed if you are with AT&T but when you read more than just one post, and make a point of trying to understand what you're doing, things become clearer.

right managed to get the bootloader unlocked and i am rooted
i have installed team win recovery v2.5.0.0
when i go to try and do a backup of my current rom i get e:not enough free space on storage

just found out i only have 1gb free of space on my memory so it was not enough to backup

last question
with mine being the international version can i choose any rom?

emu123 said:
last question
with mine being the international version can i choose any rom?[/QUO
Any evita rom
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse

emu123 said:
last question
with mine being the international version can i choose any rom?
Click to expand...
Click to collapse
Considering your version (EVITA) the "international version" will get you into trouble. Most people consider the quad core Tegra3 variant ENDEAVOURU the "international" version. Yes, this is confusing, and dates back to the time when the ENDEAVORU was available in multiple countries across Europe and other regions, and the EVITA was only available in North America. Of course, the EVITA is available in many countries now, so the term "international" is basically meaningless. Stick to ROMs for the dual core Snapdragon S4 version of the One X/XL, and you will be okay.
Better yet, just use my Index thread. Any of the ROMs linked here are fine for the EVITA: http://forum.xda-developers.com/showthread.php?t=1671237

thought i would give cm10 a go
flashed the zip then extracted the boot img and flashed it and now touchscreen doesnt work
tried to get back into recovery and now it looks like my internal sd card is messed up
managed to reflash recovery and now the touchscreen works again
but having trouble getting the internal memory to show up and restore my backup

emu123 said:
thought i would give cm10 a go
flashed the zip then extracted the boot img and flashed it and now touchscreen doesnt work
Click to expand...
Click to collapse
If your phone was shipped with Jellybean, or your RUU or OTA'ed to it, the touchpad firmware was upgraded, and will not work with any AOSP ROMs.
You can downgrade the touchpad firmware, but you need to be S-off: http://forum.xda-developers.com/showthread.php?t=2159863
emu123 said:
tried to get back into recovery and now it looks like my internal sd card is messed up
managed to reflash recovery and now the touchscreen works again
but having trouble getting the internal memory to show up and restore my backup
Click to expand...
Click to collapse
If you tried to do a factory reset in bootloader, you corrupted the SD card (known bug, don't ever do it, always factory reset in recovery).
See Question 15 here: http://forum.xda-developers.com/showthread.php?t=2136172
There are also other fixes for this, if you search around this forum.

thanks
managed to get the card back , but think i will have to sideload a rom as i cant connect it to my computer and copy across my twrp backup
bit messy this flashing business lol

for some reason cleanrom wont install it was stuck on the boot logo for about 30 mins
i did try and flash the boot.img from the rom as well with the same results
viper one xl seemed to work fine
if i manage to get my twerp back up back onto my sd card and flash it back
when an update comes out does it wipe the custom recovery and root?
really struggling to find a proper ruu for my phone and the only one i could find as a .zip file

[GUIDE] Root, SuperCID & S-Off for Evita Hboot 2.14 - Firmware 3.17 [Orange UK]

This is for International hTC One XL/Evita - Hboot 2.14 & firmware 3.17 (Orange UK)
If you own AT&T One X please look elsewhere, this guide is not for your phone
There is an abundance of information scattered in these forums and not all root methods/exploits work universally due to variation in firmware builds and Hboots.
I had to read a lot of threads to figure out how to S-off my Orange UK One XL with Hboot 2.14 and firmware build 3.17.
I was only interested in attaining S-off but had to start with HTCDev bootloader unlocking which I didn't really want to do but none of the known root exploits worked on my firmware.
I am sharing this hoping it would help others avoid taking pills for headaches when pursuing this noble quest
AIM:
Provide a short guide to others with similar device and configuration on where to start and simple clear steps to follow with needed links.
PREREQUISITES:
1. latest htc drivers for your Windows PC/laptop if you have one of those. Check here.
2. a working adb environment preferably from latest Android SDK, if you don't have this already set up please check here.
3. "USB debugging" must be checked under Phone settings>Developer options
4. an original htc USB cable is strongly recommended.
5. phone charged at above 50%
6. basic knowledge of using command prompt (cmd) in Windows and adb commands.
STEPS:
So in my case the steps were:
[1] Unlock bootloader through htcdev.com
[2] Flash/install TWRP recovery
This is done manually. All-In-One Toolkit didn't work for me BTW.
1. download latest TWRP recovery for One XL/Evita from here
2. you can rename file for easier command prompt typing later, like TWRP5.img
3. place file recovery file in your adb/fastboot folder
4. connect phone in fastboot mode to PC, make sure it displays fastboot USB on phone before you proceed.
5. start command prompt from within fastboot folder by right clicking inside folder and choosing "open prompt here", type following command:
Code:
C:\yourFastbootFolder> fastboot flash recovery TWRP5.img
Not a bad idea to test your recovery by making a nandroid backup before proceeding to next step.
[3] Flash a custom rom (root)
All custom roms are rooted by definition. If you chose e.g. ViperXL like I did remember to flash boot.img extracted form same rom zip afterwards, otherwise bootloop!
You can of course flash a SuperSU zip instead to gain root but I don't see the point.
[4] SuperCID
This is the simplest way that I found accidentally during my endless searches, all credit goes to @beaups for this one and @Austempest for sharing :good:
1. connect phone to PC in Android mode (mode where you can use phone)
2. Run the following command from command prompt (CMD):
Code:
C:\>adb shell
To enter adb shell, then enter following commands after each other:
Code:
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
3. Reboot to bootloader and hopefully you'll see 11111111 as your CID ...... yes
[5] S-Off
Now that your are rooted with SuperCID you can just follow @beaups simple steps for S-Off found here Facepalm S-Off
That is it.... you broke your shackles :laugh:
I am not a dev and for sure not taking credit for other people's work, merely giving back and hoping this assists clarify stuff and save some time.
Cheers!

the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a not in your guide that this guide wont work for at&t phones.

exad said:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a note in your guide that this guide wont work for at&t phones.
Click to expand...
Click to collapse
Thanks for this important reminder, note added in red on top!
You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!
Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.
So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:
I hope it's in order to add some info for European Evitas
guys kindly don't quote whole post(s), thanks

Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.

Great guide, thanks you! it worked !
Now i'm stuck at the next step. ha :crying:

i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.
i can :
flash RUU 3.17, running a stock RUU 3.17.
unlock bootloader
flash custom recovery(twrp mess with my internal storage)
i cant :
root my device on stock rom
touchscreen wont work on custom rom
any help will b greatly appreciated.

Do not make multiple posts about the same thing. It is strictly against XDA rules.

sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.

You cannot
Sent from my One X using xda app-developers app

sir how to back or normal cid help me
sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid

Fastboot oem writecid whateveryourcidwas
This will only work once with s-on after supercid but will work as many times as you want if s-off.
Sent from my One X using xda app-developers app

ignore this post. found a relevant thread

How to upgrade bootloader to 2.14
So what if you are not on HBoot 2.14?
EDIT:
Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here
http://forum.xda-developers.com/showthread.php?t=2119610
and the tutorial for upgrading RUU on a previously modded phone here
http://forum.xda-developers.com/showthread.php?p=26260005
I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.
First you need the superCID from this post:
http://forum.xda-developers.com/showthread.php?p=42351491
Next Step S-Off:
http://forum.xda-developers.com/showthread.php?t=2155069
Then RegawMOD the appropriate bootloader from this thread and flash:
http://forum.xda-developers.com/showthread.php?t=1786498
The procedure was easy once I had found the appropriate threads on XDA

You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Sent from my HTC One XL using xda app-developers app

New CM10 and derivates require HBoot 2.14
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Click to expand...
Click to collapse
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.

ernstlustig said:
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
That's exactly why you should not do it that way. You may get issues along the way as a result of the software not properly utilizing your hardware. This is why you're supposed to update hboot. What you did is more like tricking it into thinking you updated the firmware.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse

ernstlustig said:
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.
The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.
All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.

How did you get s-off? i have a rogers version

salt204 said:
How did you get s-off? i have a rogers version
Click to expand...
Click to collapse
Links to XDA threads updated. (Sorry.) Please look again.

Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?
as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.
I have tried the hex with adb method, but it doesn't work.

Firmware Update Q&A [extra noob friendly]

WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin

Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware

Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553

One more just in case

rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though

vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!

I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!

rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!

thank you!

I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?

khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?

rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.

khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)

rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?

khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse

forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good: