Database Info

[Q]Serious Problems With HTC Sensation[Q]

Okay, so I guess these problems may not seem serious to you, but they really do to me.
I'm on my third Sensation in two weeks. Ridiculous, I know. My local Orange store seems to have received a 'bad batch'.. yeah right, more like their software messes the phone up. Anyway I'm having problems with S-off'ing.
The first two Sensation's I recieved from Orange, had *Bootloader Locked* on the HBOOT, however this one does not have that at all? It doesn't say anything about a locked or unlocked bootloader at the top of HBOOT.
The problems first started when I attempted to S-Off. I have ALL my drivers installed and do not have any interrupting applications. Revoloutionary manages to complete all steps however on the 2/3rd time rebooting the bootloader it suddenly losses connection with my phone. It manages to root and everything, but then it will loose connection at this point and there seems to be not a thing I can do about it.
I have no idea how to fix this situation, I don't want to run a custom rom, I just want to be able to run a stock de-branded phone with S-ON!
Also, I was wondering if I S-Off, install Stock HTC Software, then S-On again will I be able to recieve updates OTA?
Thnaks XDA.

[Q] Can't Boot Into Bootloader

First, let me say I am a noob and not a developer, just more of a phone enthusiast. That said, my problem is that I cannot boot into the bootloader on my AT&T HOX. I have read through many threads on how this is done (Pwr+VolDown), but it simply doesn't work for me. After about 4 seconds, my nav button baklights flash a few times, then stop. From this point, I have tried two things...1) contine holdign pwr+voldown for well over a minute, nothign happens and 2) releasing the pwr+voldwn bottons and then pressing again and holding for what seems to be an eternity, but still nothing happens. Note that I'm having no issues with a normal boot.
The caviat: in order to sync my company's corporate email via exchange, I have to enable administrator rights by my company's IT policies (which totally blows, I know). This forces encryption on phone storage, even though I think it's really just the sector that houses files related to my exchange account. Regardless, I'm wondering if the administrative rights or encryption is what's preventing me from accessing my bootlader.
Thoughts? I know the thing I should so is just remove my exchange and disable the administrator rights, but to do so I am forced to factory reset the phone, which I'd like to prevent doing unless that's all there is left to do.
Any help is appreciated. If this is a dumb noob question and I missed a previous thread containing a solution, please link and I wont keep this thread going. thanks a lot.

Why are you trying to get into H-Boot? Are you trying to re-flash your phone with the stock ruu or something?
Anyways, to answer your question. No your admin stuff is in no way causing the phone not to get to h-boot, and it's there, I don't think I've ever heard of a phone that boots that can't h-boot.

HydroSkillet said:
Why are you trying to get into H-Boot? Are you trying to re-flash your phone with the stock ruu or something?
Anyways, to answer your question. No your admin stuff is in no way causing the phone not to get to h-boot, and it's there, I don't think I've ever heard of a phone that boots that can't h-boot.
Click to expand...
Click to collapse
To be honest, at this point I am only trying to access it out of curiosity. But ultimately I am checking it out because I have started to have a lot of connectivity problems with wi-fi and was looking into flashing the 1.82 update floating around. I was going to wait until the offical OTA update, but the wi-fi problem is getting worse, or at least it's effecting me more. Anyway, was just looking into accessing it. I initially noticed that I couldn't get in last week when reading a battery thread on calibration since my first couple days witht eh phone had very poor battery life. But it's improved since then and I never went back to check until the wi-fi issues proved annoying. Since I haven't rooted a device before, i figured I woudl familiarize myself with some of the basic steps before assuming I would just jump right in. Checking out how to h-boot seemed like a good place to start.

fitchpuckman said:
To be honest, at this point I am only trying to access it out of curiosity. But ultimately I am checking it out because I have started to have a lot of connectivity problems with wi-fi and was looking into flashing the 1.82 update floating around. I was going to wait until the offical OTA update, but the wi-fi problem is getting worse, or at least it's effecting me more. Anyway, was just looking into accessing it. I initially noticed that I couldn't get in last week when reading a battery thread on calibration since my first couple days witht eh phone had very poor battery life. But it's improved since then and I never went back to check until the wi-fi issues proved annoying. Since I haven't rooted a device before, i figured I woudl familiarize myself with some of the basic steps before assuming I would just jump right in. Checking out how to h-boot seemed like a good place to start.
Click to expand...
Click to collapse
disable fastboot in power options. turn the phone off. Hold down and power, you should see your h-boot
Also if you're looking to flash the unreleased it's just an exe that you run.... it's easy.

^This. Need to disable fast boot in your power options first.

HydroSkillet said:
disable fastboot in power options. turn the phone off. Hold down and power, you should see your h-boot
Also if you're looking to flash the unreleased it's just an exe that you run.... it's easy.
Click to expand...
Click to collapse
beaups said:
^This. Need to disable fast boot in your power options first.
Click to expand...
Click to collapse
Thanks guys, this is likely the case. I thought I disabled fast-boot mode the other day, but apparently I did not. I'll give it a shot in a little bit when I get back to my desk and let you know if I'm still stuck.
Also, re the unreleased RUU, yeah the thread made it sound pretty simple. there were various folks having issues after the update, so I'm just going to monitor for a few more days to see how my phone performs and if there comes official word of a carrier OTA update.
Thanks again.

S-Off / Hboot 1.27

I sent my phone away to have the dust under the screen issue fixed. Got my phone returned today to find it has been updated to ICS/Sense 3.6. Now on hboot v1.27 which I am only now realising is causing some problems with regards to s-off/rooting etc.
Is Juopunutbears method involving the wire/sd card the ONLY method?
Are the people at revolutionary likely to develop a method for s-off AT ALL for v1.27? Is it worth waiting?
Anyone had any success getting s-off?
I know there has been a few posts/threads on this issue but just require a little more clarity, thanks.

yourpassenger said:
I sent my phone away to have the dust under the screen issue fixed. Got my phone returned today to find it has been updated to ICS/Sense 3.6. Now on hboot v1.27 which I am only now realising is causing some problems with regards to s-off/rooting etc.
Is Juopunutbears method involving the wire/sd card the ONLY method?
Are the people at revolutionary likely to develop a method for s-off AT ALL for v1.27? Is it worth waiting?
Anyone had any success getting s-off?
I know there has been a few posts/threads on this issue but just require a little more clarity, thanks.
Click to expand...
Click to collapse
I almost want to guarantee you that another method isn't going to come about, not anytime soon anyways. I was really nervous about doing this with my replacement a few days ago but once I tried it, it was really a lot easier than I expected... It did take me like 20 tries BUT i'm just terrible at timing things. Lol. Anyway, I say give it a go. I did this as soon as I got my phone out of the t-mobile replacement packaging. Haha.

Did you backup your SD card?

I did not, but I would recommend to. I had to format my card (probably my mistake). It isn't hard, you just have to time it right and it might take a few tries.

Won't turn on and no charge light

Just sent my HTC Sensation off for repair under warranty due to this fault :
Running OpenSensation nightly 20120810 and TamCore 3.0.40 without any issues and updated the nightly every 2-3 days with no issues. had the phone 12 months and had it s-OFF and unlocked about 4 hours after buying it. At that time running CM7 as that's all there was, updated to various ROMs until I settled on OpenSensensation (tried CM9 a couple of times for a few days but prefer OpenSensation). All ROMs installed fine over the past 12 months
Installed Kingdoms and Lords off Google play (huge game 200MB data download via wireless), after first game phone froze and reset. So I reduced the overclock, game running fine. Had another game later on in night playing for about 15 minutes. Phone froze again, switched itself off and didn't come back on again !!!!
Tried charging it thinking battery was flat, no charge. Took battery out as it was an Anker 1900mah just in case it had blown. Put original HTC battery back in, no charge light, nothing. Took battery out and left it out 2-3 hours as suggested on 'net as it 'might' help
No charge, tried another USB lead plugged into desktop. Still no charge .... oh crap
Took to T-Mobile shop I got phone and explained situation, forgetting to mention it was running custom ROM, they tried. Still no charge, no reaction in shop. Zero, zip
They sent it off for inspection/repair yesterday under warranty and said it should take 2-4 weeks
It had been running custom firmware since the day I got it on contract and has never caused me any grief, apart from some roms running better than others while I made a choice which ROM to stick with
Question I'm asking is can HTC still test the phone even though its not taking a charge or I assume not powering and just froze and died, assuming the motherboard is fine does anybody know if they use test points that bypass the USB socket to power it up
And how can just playing a legitimate game downloaded off Google Play freeze the phone and shut it down never to power up again
I'm guessing the possibilities of a faulty USB charge socket, faulty power switch or fried CPU/GPU/motherboard considering it just froze and died
I used it as a phone but did play games quite a lot during the day when I had a few minutes while not working, and had it overclocked to around 1625-1728 which it ran stable at without overheating
If they send it back refusing to touch it due to finding custom firmware on it I'm looking at the Samsung galaxy SIII over the HTC Nexus One simply because the Samsung has a removal battery and additional microsd card slot where for some reason I assume is to make rooting more awkward the HTC has a hardwired battery and NO extra sim card slot. I was looking to replace it when my contract expired in February but if they refuse to fix it citing custom firmware (even though it has been working perfectly for 12 months running various custom firmware) I have no real choice but to buy out my contract and get a new contract. Bummer

Hmmmm,
Reading a few postings it appears there is a possibility that the motherboard is fried somehow, or a 'hard brick' through a bad ROM install ... I wasn't updating and firmware, not updating any ROMs
Just playing a game downloaded and installed off Google Play, but if it means the motherboard is fried then at least it means HTC will have to replace it as 'faulty' so saving me the upfront cost of buying out my contract thas has 6 months to run

Actually if you overclock the device or flash a kernel htc doesn't have to replace anything.. by "playing a game downloaded from google play" you mean "playing a game downloaded from google play on a device controlled by custom drivers which clearly make your device out of warranty". So I'm not sure.. altough it's possible that it's not the fault of the kernel but the mainboard had some issues. They are able to test the charging port and the main board seperately. Let us know abouth the end.

It would interesting to see HTC's response either way so I'll report back once they have a look at the phone
As I don't have a loan phone at present so have no phone until they get one back from customers having their phone repaired, I have to use the 'net to check on the status of the repair via the T-Mobile website

I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with

thescrapyard said:
I got my phone back yesterday with a new motherboard, under warranty
Now seriously struggling to get it to S-OFF as its running HBoot 1.27 as teh guys in the shop also said its had "new firmware upgraded for you", or to prevent me from getting S-OFF
Tried the all in one kit, tried the 'official' unlocker method from HTC. Keep getting the same error about token mismatch when trying to unlock the bootloader
Reading postings from here and there it's suggested that as the motherboard has been changed and a new IMEI, the IMEI and hardware serial numbers now don't match so causing a mismatch between number so the unlock obviously fails
Looking at trying the JB_Bear flash wire trick when I have more time to see if that work with replacement motherboards, so any suggestions as I'm stuffed and want S-OFF as well as full root again. Unlocked it when it was running HBOOT 1.18 was a doddle but now its a pain and T-Mobile branding is pants so want to be able to have my phone how I want it without all the crappy restrictions
Unless somebody can S-OFF and root for me in the North-West Lancs area without sending the phone away, I'll have to do a bit more digging to see what I come up with
Click to expand...
Click to collapse
for replaced mother boards ..there is a different version of jb ..check my soff guide ..link in my signature

Will let you know how it goes, thanks

Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far

thescrapyard said:
Managed to get S-OFF using your method after a few tries did nothing so started making me nervous I was about to fry my new replacement motherboard, eventually it beeped and did the S-OFF by following yours steps to the letter
Problem is now, I want to remove the ***LOCKED*** but every recovery.img I try fails with a token error, which reading about it is down to teh bootloader apparently still locked
Also changed the HBOOT to your JB_HBOOT with no difference, still S-OFF but ***LOCKED***, so can't get the next step to get a fully rooted fully unlocked system so I can get back to where I was before the original motherboard died
I'm now looking at installing CM10 JellyBean 4.1 by KANG, I used to run OpenSensation CM9 quite happily and nightlies with zero issues installed a few ROMs over the past 12 months with a couple of minor issues I solved myself with reboot loops and ROMs getting confused and having to wipe the entire phone, plus when I wiped the core by accident during yet another ROM install .... that was fun to solve. Took a couple of days of reading about that one
Anyway, any suggestion as to how to get full unlocked or at least so I can install 4EXT recovery and SuperUser to get a bit further on the custom ROM route and get a phone that's what it should be instead of crippled by T-Mobile UK
Thanks for your help to get where I am so far
Click to expand...
Click to collapse
for flashing eng-hboot aka changing from LOCKED to Juopunutbear
check the troubleshoot point #3 solution in my soff guide ..its explained there
and for thanks ..there is a button to say that

All sorted, now running the latest nightly of Kanga JellyBean 4.1 and full rooted and back to how it was before the motherboard dies, apart from running Android 4.1
Also feels much smoother and much faster, even though its only running the default slight overclock that Kanga sets as teh default, so might leave it at that as it feels faster than previous when running OpenSensation 4.03
Great stuff

[Q] Q about rooting a contract phone with insurance

Hey guys, I'm considering going with they option of rooting my HTC Sensation, but I'd like to clear something up beforehand.
At the moment Im on a pay monthly contract with my HTC Sensation and I pay monthly for insurance on the handset, before I go rooting my phone, if for some reason I need to send this phone off to my provider will my insurance be void? Or is this just the case if I haven't managed to return the phone to stock setup?
Id really like to try rooting my phone, but I dont want to have the problem of not being able to send the phone off for repairs or whatnot in the future. By repairs, obviously Im not referring to any problem that could occur during the rooting process, I mean more in the sense of hardware issues etc.
Any help is appreciated, and I apologise if this has been asked/answered before, I did do a forum search but found nothing.
Thanks.

You can S-Off your device without unlocking the bootloader over HTCdev. This way you can root and flash custom ROMs/kernels without loosing your warrenty.
If you have issues and you have to send the phone in, you can just run an RUU for you phone and S-On it again. Nobody would know that you have rooted it.
And if you want to S-Off take a look at the Hboot version! Hboot 1.2x has a different and more difficult way of S-Off'ing.

Oh right, how would I go about S-off'ing my phone? Would it still require me to go through the whole root process first off?
Thanks for your help

First we have to know your H boot version to direct you to the proper guide. To find out, pull battery, put battery back in, then at the same time press power and volume down button. Hold. Then you will see a screen pop up. Look at the information on Top of the screen. Then tell us your H Boot version. by the
Way, I also pay insurance every month on my device and I'm rooted and S off. If anything should happen I would restore back to stock and S on again. This way they would not know device was rooted. Hope this helps.
Sent from my HTC Sensation

Just did as you asked and my H boot version is 1.27.0000. That is what I was curious about, the whole insurance deal.
My main reason for considering rooting is to be able to theme my phone a bit more than what a launcher lets me, so what is recommended for this, just rooting, just S-off'ing or both?
Thanks

Gaz1521 said:
Just did as you asked and my H boot version is 1.27.0000. That is what I was curious about, the whole insurance deal.
My main reason for considering rooting is to be able to theme my phone a bit more than what a launcher lets me, so what is recommended for this, just rooting, just S-off'ing or both?
Thanks
Click to expand...
Click to collapse
Both process are reversible, once its s-off and rooted, just dont change your hboot and your good to go. I had the same concern, yet when i needed to return my phone for the warranty, they never even cared and sent me the other one without question (after i turned back the s-on of course). Follow Ganesh's guide here: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNGNDWtlRFM7pBTIlQr-Y6Vd4nJEgw
Very easy and completely safe!
BoB!!

I suggest rooting and S off. I don't regret it for a second! I try all kinds of awesome roms and I'm able to customize to exactly how I want things! It's been a totally positive experience for me. As I mentioned in above post, I too pay the extra insurance monthly. If there we're a issue I'd return to stock. As above member mentioned he did it and didn't have any problems. I think once your rooted and s off you will be very happy. But do take the extra effort to s off because it's worth it in the long run and makes things easier for you, You will have the ability to do more with s off. Best wishes.
Sent from my HTC Sensation

Oh right, thanks you guys. I now feel more able to go ahead and root, now I just need to decide whether I think Im capable of doing it correctly.
Just had a look at that link you posted BobThaBear, it looks abit on the daunting side so Im going to have a long, hard think about it first.
Thanks for all of the help though, its very much appreciated