Database Info

Stuck on HTC screen, can't unlock bootloader, can't root from Fastboot

I got a bricked T-mobile Sensation today at the shop and after checking it out I thought it would be easy to fix but unfortunately its proving to be much more difficult than I expected. Here's what I'm working with:
Locked s-on
Hboot 1.18.0000
radio 10.14.9035.01_m
First, I tried all kinds of PG58 zips. None worked. I figure I need to be unlocked to do it. Did the HTC unlock and got to the warning screen and where it asks to choose yes or no. I can navigate to yes or no but when I choose yes it just freezes and doesn't do anything. I tried it 3 different times, same thing. I can't even choose factory reset in Hboot, it just freezes. I don't know what the eff is going on. I've been downloading RUUs but have yet to find the correct one. I don't know what firmware it has because it does not boot up.
I thought, well shoot, I have fastboot, maybe I could just s-off and root from fastboot, but I can't find any thread explaining how to do it.
Any help would be great.
Thanks!
Edit:
Found the correct RUU, 1.50.xxxx whatever. WHen I run the utility It says its rebooting into bootloader but stays in the same screen and doesn't do anything. I don't know if this helps, but when I go into the bootloader I cannot go back into hboot. It just, freezes.

Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.

As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.

Kazireh said:
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
Click to expand...
Click to collapse
gol_n_dal said:
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Click to expand...
Click to collapse
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
I have all drivers installed, adb, fastboot, etc

If your on hboot 1.18 you have a gingerbread fw, look for that
Sent from my HTC Sensation 4G

its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?

q said you did not understand, is how I explain more thoroughly I am new to the subject
and my device does not enter the system and when using the mode prop vo comand says device not found what to do? sensation with my ta hboot 1.27.0000 s-s on rl unloked help me

2strokenut said:
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
Click to expand...
Click to collapse
Can you get into "Fastboot USB" ?
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
Click to expand...
Click to collapse
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
Click to expand...
Click to collapse
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
I have all drivers installed, adb, fastboot, etc
Click to expand...
Click to collapse
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.

nickL0V3 said:
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
Click to expand...
Click to collapse
Yeah that's what I'm leaning toward right now, there is nothing else I can do. I have 4 or 5 Mytouchs on the shelf with bad eMMc chips so I guess this one is joining them.
gol_n_dal said:
Can you get into "Fastboot USB" ?
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
Click to expand...
Click to collapse
Yes the RUU was 1.50.531.xxxxxx
Yes, I can get into Fastboot usb, I can do fastboot commands, it just freezes when the RUU tries to do its thing.
Jbear would still work if the bootloader were locked, but I couldn't unlock the bootloader. Revolutionary will not work either because its run while the phone is on, which I can't do.
I think I've exhausted every option, it seems to all point to a failed eMMc chip, shame though, I really like these phones.
Thanks for the help fellas

GL
///////////////

Downgrading hboot

Hey everybody,
after updating to JB with the official RUU found here, the gps is not working properly.. i find it very annoying.
so i decided to downgrade the hboot and try to run the ICS ruu..
i read the tutorial found here - http://forum.xda-developers.com/showthread.php?t=1990043
but it says not to do that if the JB RUU was used.
the question is - is there any other way to downgrade the hboot? and which hboot version do i need?
thanks!
Yossi

You should follow these instructions for getting s-off on your phone then.
It's way more comfortable and can easily be undone than the method you linked to.
Before we had s-off I downgraded a couple of times by bricking/unbricking my device. I was successful, even after the JB OTA with super-cid, maybe I was just one of the lucky ones. Idk.
If you decide for bricking/unbricking, the downgraded bootloader version on your S4 (you're shure about that?) should not be higher but 1.06 or 1.09. Else it's useless.

rootrider said:
You should follow these instructions for getting s-off on your phone then.
It's way more comfortable and can easily be undone than the method you linked to.
Before we had s-off I downgraded a couple of times by bricking/unbricking my device. I was successful, even after the JB OTA with super-cid, maybe I was just one of the lucky ones. Idk.
If you decide for bricking/unbricking, the downgraded bootloader version on your S4 (you're shure about that?) should not be higher but 1.06 or 1.09. Else it's useless.
Click to expand...
Click to collapse
I can second that. I've downgraded and sent s off. S off wasn't as scary as I thought. It was actually easier than downgrading.
Good luck.
Sent from my HTC One S using xda app-developers app

I ran the JB RUU and my GPS isn't working right either. When I previously updated to JB via OTA, the GPS worked. Have you tried just running the RUU again? Maybe that will fix it.

thanks for your reply!
why do i need s-off? what is the next step after doing so?
and are you sure that it it is more safe than following the guide i attached?
thanks!
Yossi

You should do a search on s-off. It switches off the security flag on the phone and simply said it allows you to flash whatever you want on your phone to any partition on your phone. Bootloader version will be of no importance anymore as it simply overrides it...
Downgrading your bootloader is a complicated process, transferring a new bootloader in very little chunks on your phone via the integrated modem using linux. All clear so far?! :laugh:
Compared to all that, facepalm s-off is really easy... and much more efficient. Downgrading bootloader was/is a pain in the ass. I'm glad this is depracted by the s-off.

thanks all!
i know about S-OFFing from my old desire, but thanks for your explanation.
i guess i should try running the RUU again before.

Was on the Desire before the One S. :good:
Jep - RUU is pretty good to go. Just keep away from the TMO US JB OTA. This one might make it impossible to s-off your phone, as it might write protect the partition for s-cid.

so.. i followed the instructions - rooted my phone, changed to supercid and all..
but the S-OFF failed :\ i followed the instructions but when i rebooted to fastoot it's still "VLE PVT SHIP S-ON"
should i try to do that again? isn't it risky?

Please be more specific - what were you doing when what failed?
Else: repeat it until it works!

everything worked - i have a rooted phone with super-cid.
i followed the instructions and it seems like everything went according to the instructions. but it wasn't successful since i still see "S-ON" on fastboot.
are you sure i can do this again?

Very shure. I had some issues as well with my data connection and had to repeat that a couple of times.

yossif89 said:
i followed the instructions and it seems like everything went according to the instructions. but it wasn't successful since i still see "S-ON" on fastboot.
are you sure i can do this again?
Click to expand...
Click to collapse
At step 5 you MUST get the error 'remote 92 supercid' and not 'remote 99 unknown'.
If you get 99, the first thing to try is just power down completely, wait a few seconds, boot back into fastboot and try again. If that doesn't fix it, I don't know really but read around the facepalm thread, search for '99'.

thanks!
meanwhile i've read a lot and tried again - the problem is "error 99" and not 92..
i'm trying to fix it..

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

[Q] Cannot soff, devunlock or anything else

Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !

i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187

rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!

elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?

rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?

elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread

Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?

culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !

elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/

culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?

rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.

culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)

I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34

culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?

rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon

[Q] Help please, can't get past bootloader

Hi, any help will be much appreciated getting my Sensation working again!
What happened:
I am trying to unroot and unS-Off my Sensation XE to get it back to stock (I have a new phone, although I've had a lot of fun with my Pyramid). I stupiudly managed to brick my Sensation completely and have since unbricked it thanks to the clever guys here http://forum.xda-developers.com/showthread.php?t=1522351.
Where I am:
However, now, whatever I try, I can't successfully flash a stock HTC ROM. I'm stuck at the bootloader screen. If I try flashing a stock Sensation RUU file through Windows, and I've tried about four all compatible for my phone varient, towards the end of the process I get an signature check error in the RUU application. This is despite the phone's CID, if that's the right term, matching the RUU's accepted CIDs. Other methods I've tried, e.g. KGS Utilty, also fail (seems to stall).
I'm thinking something needs to be done to the phone before I can flash an RUU, following the unbricking.
Phone info:
Here is the bootlader info etc.
"*** LOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.02_2
eMMC-boot
Aug 2 2011,22:35:52"
It's a European SIM-free Sensation XE (direct from HTC as a replacement after my Desire HD failed a long time ago!)
If more info is needed am happy to oblige, preferably if I can have the fastboot command to show all the details if applicable.
What can I do ?! (That's the Q)
Thank you.

Berky99 said:
Hi, any help will be much appreciated getting my Sensation working again!
What happened:
I am trying to unroot and unS-Off my Sensation XE to get it back to stock (I have a new phone, although I've had a lot of fun with my Pyramid). I stupiudly managed to brick my Sensation completely and have since unbricked it thanks to the clever guys here http://forum.xda-developers.com/showthread.php?t=1522351.
Where I am:
However, now, whatever I try, I can't successfully flash a stock HTC ROM. I'm stuck at the bootloader screen. If I try flashing a stock Sensation RUU file through Windows, and I've tried about four all compatible for my phone varient, towards the end of the process I get an signature check error in the RUU application. This is despite the phone's CID, if that's the right term, matching the RUU's accepted CIDs. Other methods I've tried, e.g. KGS Utilty, also fail (seems to stall).
I'm thinking something needs to be done to the phone before I can flash an RUU, following the unbricking.
Phone info:
Here is the bootlader info etc.
"*** LOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.02_2
eMMC-boot
Aug 2 2011,22:35:52"
It's a European SIM-free Sensation XE (direct from HTC as a replacement after my Desire HD failed a long time ago!)
If more info is needed am happy to oblige, preferably if I can have the fastboot command to show all the details if applicable.
What can I do ?! (That's the Q)
Thank you.
Click to expand...
Click to collapse
post the output from this command
fastboot getvar all
don't show your imei and s/n

The only RUU's I could find according to your device was:
RUU_Pyramid_LE_hTC_Asia_TW_1.73.709.4_Radio_10.58.9035.00U_10.15.9035.02_2_release_221625_signed.exe
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed.exe
As long as you have hboot 1.18 i think you can s-off your device by using Revolutionary S-OFF
When I had a ***Security Warning*** with an Incredible S I had the same problem.The only thing I could do (furtunatly for me) was to s-off it using Revolutionary.As long as you have a working Hboot you should be able to S-OFF it like this and then you run an RUU to fully recover your phone.
** I read you may have to repeat 2 or 3 times the proccess to S-Off your device. **
You can check this guide too:
[Guide] Successful S-OFF after (wrong S-ON) brick for ICS/GB ,Downgrade S-ON firmware

Somewhere I have read when you are in ***Security Warning*** you could still be S-OFF but you possibly have to use a gold card to flash a zip from your device.
[TOOL] Goldcard img creator

Thanks both for your replies. (Sorry for delay, I was away from home.)
rzr86 - attached, thank you.
Gatosbil - I don't want S-OFF, I want S-ON! In case you didn't see that, shall I still follow your suggested links?
I will await any further info you can gleen from my attached screenshot.
Thanks again.

Berky99 said:
Thanks both for your replies. (Sorry for delay, I was away from home.)
rzr86 - attached, thank you.
Gatosbil - I don't want S-OFF, I want S-ON! In case you didn't see that, shall I still follow your suggested links?
I will await any further info you can gleen from my attached screenshot.
Thanks again.
Click to expand...
Click to collapse
use the second ruu from post #3 of Gatosbil
it is an ics ruu.exe

Berky99 said:
Thanks both for your replies. (Sorry for delay, I was away from home.)
rzr86 - attached, thank you.
Gatosbil - I don't want S-OFF, I want S-ON! In case you didn't see that, shall I still follow your suggested links?
I will await any further info you can gleen from my attached screenshot.
Thanks again.
Click to expand...
Click to collapse
I know you don't want s-off but in order to make your device working again after wrong s-on (as long as you are in *** Security Warning ***) you have to revert it to s-off again and after you flash the right RUU (probably it will update your eng boot and you will lose s-off) you can revernt it to S-On.Even if the RUU don't revert your device to S-On after a right RUU flash you could do it by using the command fastboot oem writesecureflag 3.

Cheers both. I'm downloading
RUU_Pyramid_LE_hTC_Asia_TW_1.73.709.4_Radio_10.58. 9035.00U_10.15.9035.02_2_release_221625_signed.exe
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Ra dio_11.76A.3504.00U_11.24A.3504.31_M_release_28100 4_signed.exe
and will let you know how I get on. I think I understand that if this doesn't flash, I'll need to follow one of the processes described, such as make my device fully S-OFF and go from there. Will update you!

Hi guys. The RUU above fails with the same error message. Revolutionary doesn't get past 'waiting for device' with the device in fastboot usb mode - I've tried different USB ports and have installed the recommended HTC 3.0.0.007 Windows driver. Any suggestions from here? I feel I've come too far with this phone to give up on it, it's like a beloved grandmother* to me.
*If my gran was an Android.

Berky99 said:
Hi guys. The RUU above fails with the same error message. Revolutionary doesn't get past 'waiting for device' with the device in fastboot usb mode - I've tried different USB ports and have installed the recommended HTC 3.0.0.007 Windows driver. Any suggestions from here? I feel I've come too far with this phone to give up on it, it's like a beloved grandmother* to me.
*If my gran was an Android.
Click to expand...
Click to collapse
what error msg do you have?
try this one
http://shipped-roms.com/download.ph...0U_11.24A.3504.31_M_release_280871_signed.exe
let's see if you will have success with a ruu for normal sensation

If you are using Windows8 you probably have some problem with drivers (check on device manager / you have to uninstall and clean install HTC 3.0.0.007 drivers).You could also use some linux distribution to execute revolutionary.You have just to download the revolutionary version for linux.

rzr86 said:
what error msg do you have?
try this one
http://shipped-roms.com/download.ph...0U_11.24A.3504.31_M_release_280871_signed.exe
let's see if you will have success with a ruu for normal sensation
Click to expand...
Click to collapse
Thanksrzr86, I tried that one and it fails in the same way (screenshot now attached).
Gatosbil, the PC is s actually ol' WIndows XP! I can't help but read your name as 'The Great Gatsby'.
Okay I will try the Revolutionary on a Linux dist.
Cheers guys, don't go too far!

Berky99 said:
Thanksrzr86, I tried that one and it fails in the same way (screenshot now attached).
Gatosbil, the PC is s actually ol' WIndows XP! I can't help but read your name as 'The Great Gatsby'.
Okay I will try the Revolutionary on a Linux dist.
Cheers guys, don't go too far!
Click to expand...
Click to collapse
yeah man try revolutionary to S-OFF
then change the cid to supercid and use whatever ruu you want

rzr86 said:
yeah man try revolutionary to S-OFF
then the cid to supercid and use whatever ruu you want
Click to expand...
Click to collapse
Cheers, just hope I have better luck doing it on Linux! I guess it is Android's natural home so...

Hi guys, I have Officially Given Up on this!
I tried running Revolutionary from Ubuntu but realised, after following a never-ending series of guides and links that I just don't have the know-how to get Linux to recognise my device ID etc. properly.
Thank you for your help anyway. I'm going to sell this on eBay, don't expect I'll get anything for it but maybe someone somewhere might want it for parts.

Berky99 said:
Hi guys, I have Officially Given Up on this!
I tried running Revolutionary from Ubuntu but realised, after following a never-ending series of guides and links that I just don't have the know-how to get Linux to recognise my device ID etc. properly.
Thank you for your help anyway. I'm going to sell this on eBay, don't expect I'll get anything for it but maybe someone somewhere might want it for parts.
Click to expand...
Click to collapse
did you try it in windows?

rzr86 said:
did you try it in windows?
Click to expand...
Click to collapse
I did mate, extensively. Revolutionary just didn't complete.