Database Info

Phone refuses to stay off

I only noticed this after flashing CM7.1 stable. Never saw it on RC1.
For some reason, any time I power off the phone, it immediately turns on again. If I pull the battery and put it back in, it turns on again. I can't seem to do anything to keep the phone powered off short of keeping the battery out.
I can't imagine how the ROM could cause this, but is anyone else experiencing the same issue? Maybe it's a bug in Clockwork Recovery?
Sent from my HTC Glacier using Tapatalk

It might not be the ROM or clockwork at all. One of my OLD phones that was just a basic Samsung slider did that same thing and I had to take the battery out to get it to stay off.
Try switching roms or even unrooting and re-rooting. If that doesn't do anything then its most likely a hardware problem and you should unroot it and bring it to t mobile.
Sent from my HTC Glacier using xda premium

Power button stuck.
Sent from my HTC Glacier using xda premium

It's the HTC Panache from Mobilicity, not from T-Mobile, but same hardware. And I'm using it on WIND, so I hope warranty won't be an issue.
It's not the power button because the button works fine in all contexts. When I sleep the phone it stays slept. It's just that when I power it off, it pops back up again.
I tried rolling back to an older Clockwork recovery. No change. Logically this function should probably be controlled by the bootloader. I know I have the bad eMMC but no obvious symptoms of failure. Is this perhaps a sign that it's starting to fail?
Sent from my HTC Glacier using Tapatalk

Update: if the phone is plugged into power when I turn it off, it stays off. Once I unplug it, within 5 seconds it boots up again.
Sent from my Nook Color!

Update: I took a full Titanium Backup and a full nandroid backup, and then tried flashing back via PD15IMG.zip to the original Mobilicity HTC Sense ROM.
Once Fast Boot is disabled (as that results in a "fake shutdown"), if I power off the phone... one, two, three, four, five, and it comes back on. So this doesn't seem to be related to the ROM after all. Something has gone weird with the phone that prevents a full hardware shutdown.
Fortunately this is the only hardware problem I'm experiencing. So now I'll have to think about whether to bring this in for warranty. Restoring the Nandroid to CM for now...
EDIT: Well this is interesting. After restoring the nandroid backup, I selected power off in CWM and it powered off... and stayed off! Puzzling.
Booting back into CM7.1, and powering off one more time. Drumroll... and it stays off!
Well... I guess I... fixed it? *shakes head*

I had the same issue with an earlier nightly of CM7. In fact, it was probably multiple builds.
I think clearing cache/dalvik cache probably would fix it. I had a confusing moment where suddenly it stayed off as well, hasn't bothered me since.

[Q] Screen not turning off

Anyone else having a problem when trying to turn their screen off? My screen turns off and then immediately turns back on and brings me to the lock-screen. I have to press the power button 3-4 times in order for me to turn the screen off and keep it off. I use a case, but even with the case removed this still happens. VERY annoying, any help would greatly be appreciated!
EDIT: This happens to me on every rom I flash, I've used ARHD, InsertCoin, Pyramid3D, Sense-O-Maniac, and am currently running Hypernonsense. Same problem persists throughout, so I'm guessing the rom is not the problem

That is a very known issue, if you are on stock rom and recovery, you would be able to download an update from HTC, (if you live in Europe or USA) that would "delete" the error.

I'm having the same issue as well. Although it's a small little error, it can get annoying/irritating. My phone is fully updated from HTC and I'm having this problem.
Sent from my HTC Sensation 4G using XDA App

I take it back. There is an update, lol. It's checked under automatic updates and it never told me. The other times it has, though
Sent from my HTC Sensation 4G using XDA App

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.

newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium

Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!

I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?

I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.

Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?

newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.

Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.

He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O

@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves

Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

Phone wont turn on while charging. Orange led blink [Solved]

Yesterday i flashed my HTC Sensation with Virtuous Inquisition v.4.0.2. I used the instructions on this site techsliver.com/how-to-s-off-root-flash-cwm-recovery-on-htc-sensation-with-hboot-1.27.0000
Everything else is fine except the fact that when my phone is off and i plug the charger the orange led blinks. I don't remember doing it before.
If i try to start the phone with the charger plugged in it wont start, but if I remove the charger it starts normally. When the phone is on it also charges normally. I read somewhere that it might have to do with CWM. My CWM version is 5.8.0.9 and i installed it using Android SDK.
My HBOOT is like this:
=JunopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.24A.3504.31M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
Can anybody help pls?

As far as I know this is normal. Phone should turn on whilst charging though, first make sure your phone has more than 40% charge, then switch off, plug it into charger then wait for the orange led then press power button. Wait for 30 secs then if it hasnt turned on thats not normal. Having said that, I have never used virtuous inquicision so it could be normal behaviour for the kernel included in that ROM

Well I have tried what you said and it doesn't work. It's not that i don't have enough battery, I have about 70%. I noticed that the orange light flashes while the phone is off. This is supposed to happen when there isn't enough battery. My phone refuses to start unless I remove the charger. Virtuous inquisition say they use stock kernel.

elvisypi said:
Well I have tried what you said and it doesn't work. It's not that i don't have enough battery, I have about 70%. I noticed that the orange light flashes while the phone is off. This is supposed to happen when there isn't enough battery. My phone refuses to start unless I remove the charger. Virtuous inquisition say they use stock kernel.
Click to expand...
Click to collapse
Does this happen with any other ROM's or is it just the VI one?

Well I had before a stock rom and no problems. I think it's this rom's fault. Can you give me any suggestions? I am afraid that if my battery dies I wont be able to charge the phone.

elvisypi said:
Well I had before a stock rom and no problems. I think it's this rom's fault. Can you give me any suggestions? I am afraid that if my battery dies I wont be able to charge the phone.
Click to expand...
Click to collapse
What I meant was has this happened on any other custom ROM's. but by the sound of it you havent tried any so my suggestion would be to try a different one (take a backup of VI using recovery so you can easily restore your current ROM) and see if the issue still persists.
As to the charging issue, I very much doubt that will happen, only 2 things that I know of will stop a phone from charging:
1. Bricked phone - yours definitly isnt so no need to worry there.
2. Faulty charge - by the sound of it, yours isnt so again no need to worry

No it's the first custom rom I try. Can you suggest any sensless rom for HTC Sensation with ICS?
Thank you, I hope I'll fix it.

elvisypi said:
No it's the first custom rom I try. Can you suggest any sensless rom for HTC Sensation with ICS?
Thank you, I hope I'll fix it.
Click to expand...
Click to collapse
Personally I'd recommend SmartDroid Beserk by memnoc.

I just tried the ROM you suggested but it didn't work either. What can I do now?

Try to install another ROM...install team venom's ViperS 1.0.0
Sent from my HTC Sensation Z710e using xda app-developers app

hunt007 said:
Try to install another ROM...install team venom's ViperS 1.0.0
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
I have a bunch of sarcastic replies to this post which I'm just dying to use, but for the sake of not wanting to cause the moderators any additional work I will keep them to myself (for now):
1. I have already asked him to do this except with a slightly different ROM (smartdroid beserk - which is still sense based but looks and feels like AOSP, like VI ROM)
2. My suggestion didnt help the OP and I'm searching for other methods to hopefully solve this.
Edit2: @hunt007 looking at your post history all your posts seem to advertise the team venom ViperS ROM so I would like to know how much team venom are paying you?

If you have a secondary battery I'd try that, your current one may be getting a bit old. Any issues with random reboots/shutdowns after your battery gets below 30%?
Sent from my HTC Sensation using xda app-developers app

If you have a secondary battery I'd try that, your current one may be getting a bit old. Any issues with random reboots/shutdowns after your battery gets below 30%?
Sent from my HTC Sensation using xda app-developers app
No issues at all. Now I was on vacation and I eventually my battery died one day. so the phone was off and i plugged the charger. I saw the orange light blinking, and i wasn't able to turn the phone on. after a while i unplugged the charger and it turned on the battery had gone 23%, so the phone was in fact charging. so basically the phone charges while it is off, it just doesn't understand it's battery level while off and charging, this is my theory.

Finally I found out what was the issue If anybody else has the same problem the solution is to reflash the CWM.
Maybe I had flashed an older version or a CWM for another phone, idn.
Anyway the correct latest revovery is here http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-pyramid.img

[Q] Phone occasionally becomes completely unresponsive with non-stock ROMs

Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?

power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?

redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.

What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app

c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.

GPS on when this happens, by any chance?

redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.

Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app

Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me

I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.

No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.

nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.

I understand what you're saying but i have checked it,i'm sure..

nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).

No my main problem are the Sleeps of Death.There are no BSODs in android

nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.

Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.

I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often