Database Info

Htc sensation semi brick

HI ALL
I have a massive problem with my htc sensation xe. My phone is a t-mobile sensation xe.This is what i have done to it i unlocked the boot loader from the htc dev website. I then rooted it using super click one. I then installed clockworkmod recovery. I then tryed to flash a leedroid rom to my phone and my phone would always restart after the htc logo.
I tryed to flash many other roms but same result, phone would either freeze or continuosly reset.
Can somebody help me please. I have attached a picture of my recovery screen as this is the only thing i have access to.
Thanks In Advance

And what happens when you choose an option from there?
try
fast reboot
factory reset
Try going back to the thread for you rom read, reread and reread agan,
Then follow the instructions 100% and as if by magic........................

I have been assisting this person on the sensation forum he was originally rooted with ship s off however he installed a Rom and apprantly his hboot has changed.
He has tried to change Rom but his phone is boot looping with the HTC logo and as you can see he his picture he is back to ship on.
I provided a list of ruu but he's phone fails while attempting to run application.
He has tried resetting phone through recovery and clearing data,cache,formatting system.
He explained he tried to root following the current 4 methods but still no sucess.
I advised him to seek help on here.
Sent from my HTC Sensation XE with Beats Audio using Tapatalk

I done as you told me
1.)I went into recovery and clicked factory reset
2.)I then clicked wipe cache partition
3.)I then clicked wipe davlik cache
4.)I then clicked fix permissions
5.)I then tryed to install the shipped t-mobile rom
It did not work
6.)I also tryed to install another custom rom same problem. The phone would hang on the htc logo boot up screen.
I have included pictures to make it easier to assess the problem

I don't think flashing a Rom will get you back to s-on. From your pictures I noticed you're trying to downgrade from ICS to GB, no? If you have the ICS firmware (3.06), how come you have hboot 1.18 s-on? Either there's something missing in your explanation or you really have messed up the software. Anyway, why don't you cross referenced what you've done with this guide http://forum.xda-developers.com/showthread.php?p=16125079
Cheers
Sent from my Kindle Fire using Tapatalk

I want my phone to work wetaher with original rom or custom rom.
This is what i done.
1.)I went onto htc.dev and unlocked my bootloader
2.)I used super click one to root my phone and gain super user access
3.)I then installed rom manger and clockwork recovery to my phone.
4.)I then used rom manger to download leedroid rom for my phone and installed it.
This is were it all went wrong. My phone would continuosly restart and not let be do anything. If i installed any other custom rom through recovery myphone would freeze at the htc screen untill i removed the battery.
Somebody please help i do not want to send it into htc and pay £60 odd pound

Have you tried to select fastboot from hboot, connect to a pc and run the ruu from there?

I have run into the same problem with Sensation 4G (TMO).
Here's what I did:
1. Tried revolutionary to gain s-off - and it failed
2. Unlocked phone with HTC (so my hboot scren says "Unlocked")
3. Flashed recovery
4. Flashed Android Revolution HD™ 6.5.1 | ICS |
Now stuck in a boot loop (with HTC logo on white background). Tried multiple RUUs, none of them worked (including the latest one from T-Mobile).
No luck resurrecting device so far.

weird. ive used revolutionary 3 different times to gain s-off and have never had it fail. i would give it another shot and be extra careful and follow the instructions to a T.

What version of leedroid are you trying to flash? Remember to have the latest firmware to flash ICS roms...
This is were you can get them...
http://forum.xda-developers.com/showthread.php?t=1459767
Select the proper firmware according to your cid and mid... If you have supercid, you can get any file... 1.17 is for Gingerbread.... 3.32 is for the latest ICS roms out there...
Sent from my HTC Sensation 4g with Beats Audio

AndroidNeophyte said:
What version of leedroid are you trying to flash? Remember to have the latest firmware to flash ICS roms...
This is were you can get them...
http://forum.xda-developers.com/showthread.php?t=1459767
Select the proper firmware according to your cid and mid... If you have supercid, you can get any file... 1.17 is for Gingerbread.... 3.32 is for the latest ICS roms out there...
Sent from my HTC Sensation 4g with Beats Audio
Click to expand...
Click to collapse
I've tried firmware from thread you are suggesting (cid and mid matched). Hboot does recognize the zip on sd card, parses it and takes me to normal menu. Nothing else happens. I verified that my cid and mid match androidinfo.txt in zip file.
Any other clues?
I've also tried flashing "boot loop" at the bottom of the same post, but HBOOT keeps doing the same: loads zip, parses it, shows regular menu. Nothing else.

Other option is to supercid your device if you can.... Makes your device more flexible...
Sent from my HTC Sensation 4g with Beats Audio

@paul.turchenko, the firmware will not flash as HTC.dev unlock only unlocks part of your bootloader. Radio and boot images (included in each fw package) will not flash unless you have s-off.
Have you tried to relock the bootloader then run a gingerbread ruu? Try to match the baseband, software version, carrier, area etc. as closely as you can to your original setup.
Sent from my Pyramid-T

mohammedkhalilaslam said:
HI ALL
I have a massive problem with my htc sensation xe. My phone is a t-mobile sensation xe.This is what i have done to it i unlocked the boot loader from the htc dev website. I then rooted it using super click one. I then installed clockworkmod recovery. I then tryed to flash a leedroid rom to my phone and my phone would always restart after the htc logo.
I tryed to flash many other roms but same result, phone would either freeze or continuosly reset.
Can somebody help me please. I have attached a picture of my recovery screen as this is the only thing i have access to.
Thanks In Advance
Click to expand...
Click to collapse
What type of from you trying to flash gb or pics if its pics you need to flash firmware for the from build
Sent from my HTC Sensation using xda premium

stringer7 said:
@paul.turchenko, the firmware will not flash as HTC.dev unlock only unlocks part of your bootloader. Radio and boot images (included in each fw package) will not flash unless you have s-off.
Have you tried to relock the bootloader then run a gingerbread ruu? Try to match the baseband, software version, carrier, area etc. as closely as you can to your original setup.
Sent from my Pyramid-T
Click to expand...
Click to collapse
Thanks for reply. Any giudance on relocking bootloader? Which T-Mobile RUU should I try? All RUUs I've tried keep failing on me saying something like "this RUU is not compatible with your device" - error 155.

This might help you:
http://forum.xda-developers.com/showthread.php?t=1497404
I have never used htc.dev, but I've read other users posts and understood there are instructions for relocking on the site too?
Sent from my Pyramid-T using xda premium

[SOLVED]
AWESOME!
Thanks to post above I successfully unbricked my Sensation 4G.
For those who stuck with the same problem:
Symptoms:
HBOOT:
*UNLOCKED*
S-ON
1.18
Solution: use tool from post above (can't post links) and lock bootloader back. After that your HBOOT will show
*RELOCKED*
S-ON
1.18
After this, phone will accept RUU (which failed before with *UNLOCKED* bootloader).
RUU:
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed
I will keep all files for a while so if anyone wants them - PM me.

I got my bootloader locked

After I installed ROM 4.0.3 it required to install new Firmware before that, I did that and everything went smooth but my bootloader got locked and now I cant install new ROM. I am using Soff and got locked bootloader. Can anyone help me. Thanks in advance.

todorchelebiev said:
After I installed ROM 4.0.3 it required to install new Firmware before that, I did that and everything went smooth but my bootloader got locked and now I cant install new ROM. I am using Soff and got locked bootloader. Can anyone help me. Thanks in advance.
Click to expand...
Click to collapse
Hi,
The new 4.0.3 firmware shows the bootloader as "locked".
It isn't really locked ,it is just shown as locked.
I have installed 3 ROMS with my "locked" bootloader.

Some fastboot commands are locked with the new firmware i believe. If u had s-off and custom recovery before installing u can install stuff through recovery. If u don't have a custom recovery check the development forum

But i cant install new Rom

You should install the rom via Clockwork recovery, Same process as before

malybru said:
Hi,
The new 4.0.3 firmware shows the bootloader as "locked".
It isn't really locked ,it is just shown as locked.
I have installed 3 ROMS with my "locked" bootloader.
Click to expand...
Click to collapse
hey.i also flashed that firmware. but my bootloader shows as "**unlocked**"" how could this possible???
Sent from my HTC Sensation using XDA App

Did you unlock using HTCDev.com? If so, that's why

EddyOS said:
Did you unlock using HTCDev.com? If so, that's why
Click to expand...
Click to collapse
yeah.
Sent from my HTC Sensation using XDA App

EddyOS said:
Did you unlock using HTCDev.com? If so, that's why
Click to expand...
Click to collapse
Unlocking via Revolutionary gets re-locked with the firmware upgrade too.
The 1.23 firmware should be unlockable soon by the way. HTC wants the HTCDev.com method to work for it, but it's got a glitch. I am to understand they are working on it.
Once that's fixed i am to understand that fastboot commands should work again even on 1.23.

Skipjacks said:
Unlocking via Revolutionary gets re-locked with the firmware upgrade too.
The 1.23 firmware should be unlockable soon by the way. HTC wants the HTCDev.com method to work for it, but it's got a glitch. I am to understand they are working on it.
Once that's fixed i am to understand that fastboot commands should work again even on 1.23.
Click to expand...
Click to collapse
ah .i unlocked hboot via htcdev. and i used revelolutionary tool to s-off
Sent from my HTC Sensation using XDA App

[Q] root + official ics = bootproblem HELP!

i have unlocked my htc sensation XE on htcdev.com then has it been rooted and i have installed cwm but then have i installed the original ics update and now stops the bootsreen at the htc logo on the white background without the "quietly brilliant". i have already been searching in many forums and i know i should install another rom through bootloader but if i try this it fails every time i try it, so does anyone know how i can install a different rom through bootloader?
the bootloader is unlocked, s-on, and the hboot version is 1.18.0000 .

You have the wrong hboot version. You need to update to 3.32 you can find it on this thread.

Yet another example of why you don't flash an OTA file over a rooted ROM. I wonder how many more we'll get before people get the picture...

i need hboot version 3.32? do you have the link? because i can´t find it here.

check my signature.
Sent from my HTC Sensation Z710e using XDA

EddyOS said:
Yet another example of why you don't flash an OTA file over a rooted ROM. I wonder how many more we'll get before people get the picture...
Click to expand...
Click to collapse
so do you know any way to undo this?

Flash the RUU for your phone
Sent from my HTC Sensation with Beats Audio using xda premium

EddyOS said:
Flash the RUU for your phone
Sent from my HTC Sensation with Beats Audio using xda premium
Click to expand...
Click to collapse
i have tried this already but if i try it on my computer using htc sync: it doesnt work and the same with adb drivers. i get always error 155: unknown error and if i try flashing it with bootloader it happens nothing: its loading and then, it happens nothing.

The problem was not from flashing the OTA to a rooted device. The problem was flashing the OTA without the stock recovery. You need to flash the proper RUU for your device. Who's your carrier, and what RUU are you trying to flash?

GROGG88 said:
The problem was not from flashing the OTA to a rooted device. The problem was flashing the OTA without the stock recovery. You need to flash the proper RUU for your device. Who's your carrier, and what RUU are you trying to flash?
Click to expand...
Click to collapse
i tried to flash the ruu with ics for the htc sensation xe. would it help if i try to install the last ruu with gingerbread? and what do you mean with "carrier"? sorry but my english isnt very well...

Carrier means what company gives you calls, texts etc.
Sent from my Wildfire using Tapatalk 2 Beta-5

e-plus (mymtvmobile), i was trying to flash the ics ruu for htc sensation xe with android 4.0.3 and sense 3.6

Root Rleocked DS

Long time ago I had a rooted Desire S. I flashed a Rom and the Rom installation was aborted. After that I couldn't flash any Rom. So I decided to get back to stock rom. After trying to install the Ruu with Android 2.3.5 and Sense 3.0 the phone stuck in bootloader with secrurity warning.
Last week I installed the Ruu with ICS and it worked. Now I've got that Relocked in bootloader
Now I want to know how I can root my Desire S again because I read that you can't root a phone with the normal way (htc.dev, downgrade, install old Ruu etc.)
How can I root my DS with that ***Relocked*** in the bootloader?
(Sorry for my bad English)

Do your research.
Htc-dev unlock. Custom recovery. SuperSU or SuperUser.
Sent from my HTC Desire S using xda app-developers app

One S 4.1.1 update

Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app

mrminor13 said:
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.

fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
That's what I thought. I'm excited that I get to see it on my wife's phone.
Sent from my One S using xda app-developers app

fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2

SoTacMatt said:
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
That's been my experience. Try it without if you would like. Can't hurt anything.

i am currently S-off and running viper rom. If I change my cid back to the TMo version and reflash the ruu so I return to stock, would I get the update? DO i need to lock the bootloader and S-ON?

I hav relocked the bootloader bt cn some one provide me stock recovery for cid 044 jelly bean
Sent from my HTC One S using xda app-developers app

Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...

aegentirony said:
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
Click to expand...
Click to collapse
You should not use supercid for an ota there are many reports of bricked phones that way! change your cid to original also stock recovery is a must!

fbihawk said:
That's been my experience. Try it without if you would like. Can't hurt anything.
Click to expand...
Click to collapse
Re-locked bootloader and the RUU is working. Thanks!!!

Have you guys updated your phone yet, and if so were you able to unlock and root again? I just finished restoring the gf's phone back to stock but all her apps were backed up via Titanium and from Viper 2.0, which is JB based. I can't restore her apps and data unless she's on a JB rom, if I remember correctly.
Sent from the other One.

Could someone please point me in the right direction to where I can get my wife's T-MobileUS One S (S4) back to where she can OTA update it to JB? I've been around quite awhile, but am personally a Nexus user and am not very familiar with Sense roms yet. I've done a lot of reading up on it but am getting a little confused. I keep reading about the HBOOT version possibly causing problems? Here is her setup.
Stock 4.0.4/rooted
CWM recovery
CID-T-MOB010
***TAMPERED ***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012,18:01:48

I'm not sure what ROM my gf was on. First I backed up with Titanium Backup. I flashed the stock recovery with fastboot, locked the bootloader, ran the 2.35 Tmobile RUU (to get her to completely stock), ran the Software Update from the About Menu to get JB, unlocked the bootloader, flashed TWRP recovery with fastboot, and flashed the supersu.zip in TWRP. All is good, I have working root and was able to restore using Titanium. She'll be happy when she wakes up.

Is a locked bootloader necessary?
SoTacMatt said:
Re-locked bootloader and the RUU is working. Thanks!!!
Click to expand...
Click to collapse
Did you try updating without re-locking the bootloader? I was able to update the last time (the security fix they pushed out) without re-locking the bootloader. I'd like to avoid re-locking if possible. I know I need to revert to the stock recovery (that's fine).
--------------
ROM: T-Mobile Stock 4.0.4
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes

I did try to use the RUU without locking the bootloader. It failed. That is when I did 'fastboot oem lock' and everything else went smoothly!!!

Not necessary to re-lock bootloader for OTA
I can confirm that it is not necessary to re-lock the bootloader to receive the OTA update to JB. I am on Stock TMOUS, rooted and with an unlocked bootloader. I suspect that one needs to re-lock the bootloader only if one is restoring the device to factory settings using an RUU. It certainly isn't required for a successful OTA update.
Here are the steps I followed (assuming you have the android SDK configured and the phone plugged in via USB into a PC):
1. Installed the stock recovery (fastboot flash recovery <name_of_recovery_file.img>)
2. Un-installed Superuser.apk to remove root. ( rm /system/app/Superuser.apk )
3. Rebooted the phone.
4. Checked for system update (Settings - About - Software updates - Check now...)
5. Chose to download the update. It took a while to download even on WiFi.
6. Chose to install the update.
7. Let the phone settle for about 30 minutes. It will not be as responsive during this time.
8. Re-install custom recovery (I use ClockworkMod).
9. Re-install root.
Once the update was complete (step 6 above), I did have a minor issue where the keypad was not showing up for me to enter the PIN to unlock the phone. I rebooted (hold down the Power button for about 10 seconds) and then I was able to get past that just fine.
------------
ROM: T-Mobile US Stock 4.1.1
HBOOT: 2.15.0000
Radio: 1.13.50.05.31
Recovery: CWM 5.8.3.1
Rooted: Yes