Database Info

clockworkmod 4.0.1.4 vs. 4.0.1.5

Hi guys. I am s off and on a custom-made rom. My phone charges fine with power off or on. But read about the problem when power is off cause off 100 % dead battery. Is it confirmed that any and if so which one charges phone with dead battery ? Thanks in advance.

What.......

bs android said:
Hi guys. I am s off and on a custom-made rom. My phone charges fine with power off or on. But read about the problem when power is off cause off 100 % dead battery. Is it confirmed that any and if so which one charges phone with dead battery ? Thanks in advance.
Click to expand...
Click to collapse
I keep reading you want 4.0.1.4 with blue text... I have to say I'm a bit surprised not to see more discussions about this.. a stable/working recovery seems like a pretty important thing and its not clear to me that we are 100% there yet...

I'm also surprised there aren't more discussions on this. My battery died and it was a real ***** to get working again.
This is pretty important.
Sent from my HTC Sensation Z710e using XDA App

The version you want is the second 4.0.1.4. Confusing I know but 4.0.1.5 has the charging bug and instead of releasing 4.0.1.6 with a fix someone had the bright idea of going back to a modified 4.0.1.4.

Jutt69 said:
The version you want is the second 4.0.1.4. Confusing I know but 4.0.1.5 has the charging bug and instead of releasing 4.0.1.6 with a fix someone had the bright idea of going back to a modified 4.0.1.4.
Click to expand...
Click to collapse
And the problem is if you use ROM manager which thinks 4.0.1.5 is the latest when it's actually 4.0.1.4 second edition (blue text) you need.

chrisw99 said:
And the problem is if you use ROM manager which thinks 4.0.1.5 is the latest when it's actually 4.0.1.4 second edition (blue text) you need.
Click to expand...
Click to collapse
Agreed. ROM Manager is best ignored at the moment.

i Had 4.015 charge light came on when charge power off but it was false charge, confirmed with adb, updated with 4.014 with blue text. Charging with power off.
Sent from my HTC Sensation 4G using XDA App

I have 4.0.1.5 and mine charges without problems when power is either on or off. Bit i dont know if it charges with dead battery. As i understand the new modified 4.0.1.4 charges dead batteries also ??
Again thanks in advance.... Hope for some answers

I can confirm the new 4.0.1.4 does not charge with the battery dead. However, I've found that some can, some can't. I'm currently on 4.0.1.5 and until I get an alternate charging source I'm not letting the battery die.

I'm on revised 4.0.1.4 and can charge while off, I couldn't while on 4.0.1.5. Haven't let my battery die so can't comment on that, but I guess it's best not to risk it which ever your using!
Sent from my HTC Sensation Z710e using XDA App

Hi!
Strange behavior on my Sensation.
I have installed ARH 1.1.8 (I was back to stock rom due to issues with 1.1.7). I have also installed the CWM 4.0.1.4 Recovery (blue text with Revolutionary logo).
In the Power settings, I unchecked FastBoot.
If I turn off the sensation and plug the wall charger, the battery doesn't charge (led is off) and I can't start the Sensation without first removing the battery...
Then I have flashed the stock recovery, turn off the sensation, plug the wall charger, the led is on during 3 seconds then shut down and again I can't start the Sensation without first removing the battery.
Now I have re-flashed CWM 4.0.1.4 Recovery and re-checked FastBoot in the Power settings and it charges normally...
Do I use the bad version of the CWM recovery? Why doesn't it work with the stock recovery (it did with the stock rom)?
Could it be related to the rom?
Thanks in advance for your help!
NB: Sorry for crossposting but I haven't received any answer in the other posts for the moment...

I had similar problem. I followed guide to debrand and stay s-off. Then I followed the guide for root and super cid to flash 4.0.1.4 updated and then leedroid

zim2dive said:
I keep reading you want 4.0.1.4 with blue text... I have to say I'm a bit surprised not to see more discussions about this.. a stable/working recovery seems like a pretty important thing and its not clear to me that we are 100% there yet...
Click to expand...
Click to collapse
I agree that the charging issue and different version numbers are problems. But they are serious inconveniences at most. The safety of our devices is not at risk.
Sent from my HTC Sensation Z710e using XDA Premium App

moto211 said:
I agree that the charging issue and different version numbers are problems. But they are serious inconveniences at most. The safety of our devices is not at risk.
Click to expand...
Click to collapse
??? I was reading some reports of guys having to "jump start" from a battery wired in to USB after having the battery run all the way down??
I dunno, this seems like a rather fundamental issue...
granted it seems like most ppl seem to be getting along just fine.. I'm just not sure I'm ready to be one of the ones who don't

zim2dive said:
??? I was reading some reports of guys having to "jump start" from a battery wired in to USB after having the battery run all the way down??
I dunno, this seems like a rather fundamental issue...
granted it seems like most ppl seem to be getting along just fine.. I'm just not sure I'm ready to be one of the ones who don't
Click to expand...
Click to collapse
I was one of the people who jump started their battery. A serious inconvenience for sure. But at no time was there a risk of ending up with a bricked device.
Sent from my HTC Sensation Z710e using XDA Premium App

Is it safe to use rom manager now

I know earlier rom manager had a charging issue bug for the sensation just wanted to know if the newest version was ok to use

4.0.1.4 clockwork is the correct one for the charge when battery dead.

Non. Rim manager still installs the bugged 4.0.15
Sent from my Cyanogenmod hungry Htc Sensation.

What bug is this? I flashed virtuous sensation kernel v8 and I'm running smooth at an oc'd 1.5 GHz....
Sent from my HTC Sensation 4G using XDA Premium App

Enzopreme said:
What bug is this? I flashed virtuous sensation kernel v8 and I'm running smooth at an oc'd 1.5 GHz....
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
I guess I don't know what bug this is either, I'm on recovery 4.0.15 and it charges fine. Even when its off....If I'm using the wrong recovery point me in the right direction please.

Yeah, I just looked, I'm definitely running 4.0.15 too, and my device charges perfect, if something bad is gonna/might happen please let us know what it is, and how I can change the version of clockworkmod recovery.... Thanks....
Sent from my HTC Sensation 4G using XDA Premium App

@Xsnipuhx, how long have you been on it?
Sent from my HTC Sensation 4G using XDA Premium App

Its acually cwm recovery that you have installed wrong. You need 4.0.14 not what you have. The problem with 4.0.15 is if you uncheck fastboot and your phone shuts off from low battery. You will not be able to charge it in order to get it back on. Therefore you must get the other version. Im sure rom manager is giving you the wrong one. I know you havent seen a problem yet. But you will if you uncheck fastboot and run out of battery. Flash new version alpharev cwm here http://forum.xda-developers.com/showthread.php?p=16125079
Sent from da(Bomb)Cdtdroid Pd3 Neon Rom / Htc Sensation Z710e

Xx12thANG3LxX said:
Its acually cwm recovery that you have installed wrong. You need 4.0.14 not what you have. The problem with 4.0.15 is if you uncheck fastboot and your phone shuts off from low battery. You will not be able to charge it in order to get it back on. Therefore you must get the other version. Im sure rom manager is giving you the wrong one. I know you havent seen a problem yet. But you will if you uncheck fastboot and run out of battery. Flash new version alpharev cwm here http://forum.xda-developers.com/showthread.php?p=16125079
Sent from da(Bomb)Cdtdroid Pd3 Neon Rom / Htc Sensation Z710e
Click to expand...
Click to collapse
This isnt true, and has been spread from day one. Many people have found it to work, just fine, with fast boot off. I have found it to work just fine as well. For those people, the other version (.4) DOESNT work just fine. I found that it wouldnt light the led or let me reboot without a battery pull.
The truth is, is that EITHER may work or ONE OR THE OTHER. Its EASY to figure out which one...
DO THIS WITH A CHARGED BATTERY!!!
Firs try .4 since most people are using it and that keeps us all on the same page.
Start with a partially charged battery. Note the capacity before pulling the battery and replacing it. Charge for an hour and then try to turn the phone on.
If it boots up, check that it charged. If it did, then great. If it did AND it lit the LED, SUPER GREAT! If it didnt light the LED, but you can live with that, then thats just dandy as well.
If it DIDNT work, then try the .5 version. I have yet to find someone that couldnt get either version to work PROPERLY.
DO THIS WITH A CHARGED BATTERY!!!!!
Matt

mrg02d said:
This isnt true, and has been spread from day one. Many people have found it to work, just fine, with fast boot off. I have found it to work just fine as well. For those people, the other version (.4) DOESNT work just fine. I found that it wouldnt light the led or let me reboot without a battery pull.
The truth is, is that EITHER may work or ONE OR THE OTHER. Its EASY to figure out which one...
DO THIS WITH A CHARGED BATTERY!!!
Firs try .4 since most people are using it and that keeps us all on the same page.
Start with a partially charged battery. Note the capacity before pulling the battery and replacing it. Charge for an hour and then try to turn the phone on.
If it boots up, check that it charged. If it did, then great. If it did AND it lit the LED, SUPER GREAT! If it didnt light the LED, but you can live with that, then thats just dandy as well.
If it DIDNT work, then try the .5 version. I have yet to find someone that couldnt get either version to work PROPERLY.
DO THIS WITH A CHARGED BATTERY!!!!!
Matt
Click to expand...
Click to collapse
Yeah, I have .5, and it works beautifully, my battery charges great, ststs charged as long as can be expected, and my led works as well, I also use an evo 3d battery, maybe the difference?
Sent from my HTC Sensation 4G using XDA Premium App

Thanks I already have the newest version of alpha as a recovery I just like to view available roms on the manager and what not I used it on my og droid all the time but in order to check roms you need to flash the recovery and I dont wanna lose my alpha for a glitched recovery. Just gonna stick with alpha for now

mrg02d said:
This isnt true, and has been spread from day one. Many people have found it to work, just fine, with fast boot off. I have found it to work just fine as well. For those people, the other version (.4) DOESNT work just fine. I found that it wouldnt light the led or let me reboot without a battery pull.
The truth is, is that EITHER may work or ONE OR THE OTHER. Its EASY to figure out which one...
DO THIS WITH A CHARGED BATTERY!!!
Firs try .4 since most people are using it and that keeps us all on the same page.
Start with a partially charged battery. Note the capacity before pulling the battery and replacing it. Charge for an hour and then try to turn the phone on.
If it boots up, check that it charged. If it did, then great. If it did AND it lit the LED, SUPER GREAT! If it didnt light the LED, but you can live with that, then thats just dandy as well.
If it DIDNT work, then try the .5 version. I have yet to find someone that couldnt get either version to work PROPERLY.
DO THIS WITH A CHARGED BATTERY!!!!!
Matt
Click to expand...
Click to collapse
This is very true and many people have had this issue!!!!! If it wasnt true it would not be posted on a stickie in a main thread!!!!!!
Sent from da(Bomb)Cdtdroid Pd3 Neon Rom / Htc Sensation Z710e

I'm I lucky..LOL or my phone is crap?

Hi, all.
Here is the situation....
In the past week or so I been getting update notices for .....45.....
Message was so brief that I haven't had a chance to get all numbers..
After accepting an update phone was hanging on the exclamation mark doing absolutely nothing over night...
Of course, I have my phone S-off and rooted. Nothing else was done yet, same stock ROM with no alterations. Now the tough part. Since that attempted update battery life was awful... Needed to charge almost twice a day...
NOW!!!! Does not take the charge at all... Charger works, charging my HD2 + USB computer charger nothing works. When plugged in and I remove the battery, insert it back it gives me an amber light for 5 seconds, then goes dark. Cannot boot with power cable plugged in..... Bunch of crap...
Did anybody else ran in to the same problem? Was that update meant to kill the phones with S-OFF? Or it's just my phone crapped up or battery?
Please give me some guide... 3 week old phone and so many problems.
Thanks all!!

No problem to bump my post.
Phone doesn't charge at all

Never, really never install an ota on a rooted ROM, even if its stock. I guess you should start by reinstalling stock ROM and wipe before. The charging thing is a known bug due to recovery. An update is available which you should install. You will have to manually charge the battery with a cut charging cable. Instructions can be found in this forum.
Sent from my HTC Sensation Z710e using Tapatalk

Did you look here, http://forum.xda-developers.com/showthread.php?t=1192300 I havent got my phone yet just been reading

70challenger said:
Did you look here, http://forum.xda-developers.com/showthread.php?t=1192300 I havent got my phone yet just been reading
Click to expand...
Click to collapse
You don't have a Sensation yet and you are educating yourself in a proper way? I wish more people would be like you. Now, if only natural selection would work on online forums as well.

Tester30 said:
No problem to bump my post.
Phone doesn't charge at all
Click to expand...
Click to collapse
I have the same as youuuu one week ago.
first I try S-off, root, and install new rom In XDA rom.
Every thing work fine, until the night my phone go to sleep, then It never weak up anymore.
And my phone have the same acting as you.
I call my local HTC service. he say he will take my phone to check.
After one day HTC told me the problem is the mainboard. He have to change for me, but do not have the spare prats now, so I have to wait.
But today HTC call me he will change the new phone!!!!!.
I am waiting to confirm for the date.

thanet said:
I have the same as youuuu one week ago.
first I try S-off, root, and install new rom In XDA rom.
Every thing work fine, until the night my phone go to sleep, then It never weak up anymore.
And my phone have the same acting as you.
I call my local HTC service. he say he will take my phone to check.
After one day HTC told me the problem is the mainboard. He have to change for me, but do not have the spare prats now, so I have to wait.
But today HTC call me he will change the new phone!!!!!.
I am waiting to confirm for the date.
Click to expand...
Click to collapse
They told you its the Mainboard without looking at it?
This is stupid!
Search for the solutions in this forum its a well known and discussed bug!

Thanks all for educating links and replies!
Got the phone exchanged today. Not gonna do anything yet, until all dust settles and all updates will be in place.
THANK YOU!!!
Tester

[Q] Sensation in QHSUSB_DLOAD mode

Hello everyone I have a HTC Sensation XE, which mounted Android jelly bean with Rom CM10 Kang Alpha, everything worked perfectly until one day the battery has reached the 2% and the phone is turned off, as there are no longer on, and connecting the power does not turn on no led, I tried to leave it attached a few hours, remove the battery for a while and I also tried it with a charged battery (my friend's) but to no avail.
Connecting it to the PC recognizes it as qhsusb_dload, (but can not find the driver)
I discovered that the qhsusb_dload mode means that the phone is a brick.
Now I wonder: is it possible that my phone is a brick just because the battery is completely discharged? or is it more likely to be a hardware problem?
In your opinion, support HTC notices that are S-OF?
When they call and ask me what I was doing with the phone, what do I tell him?
Thank you all! :good:

remove battery sim and sdcard and charge the phone overnight (should be atleast 6 hrs ) ..it helped ppl who fell in the same scenario

indicating bycepag
ganeshp said:
remove battery sim and sdcard and charge the phone overnight (should be atleast 6 hrs ) ..it helped ppl who fell in the same scenario
Click to expand...
Click to collapse
then think that my phone is neither broken nor a brick?
and because it is in QHSUSB_DLOAD mode?
Thanks very much!

Bern_ said:
then think that my phone is neither broken nor a brick?
and because it is in QHSUSB_DLOAD mode?
Thanks very much!
Click to expand...
Click to collapse
its because the battery drained too much (the internal power )
i may be wrong ..but thats my guess

Sometimes if battery drains to zero the battery goes into a deep sleep and this possibly is causing this. I lost battery down to zero once and no charging light or anything came on. I did not try to see what my phone was recognized at so I'm not sure about QHSUB_DLOAD but I do know it had no vital signs not even charging light! What I did was immediately put another battery in my device and it came back to life ! If you do have another battery put it in and see if this works for you. It worked for me! But like I said, I don't know if device was QHSUB_DLOAD or not because I did not test it. All I know is it had no charging light or anything! It's sure worth a try ! I wish you the best and hopefully this issue will be resolved soon.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.

realsis said:
Sometimes if battery drains to zero the battery goes into a deep sleep and this possibly is causing this. I lost battery down to zero once and no charging light or anything came on. I did not try to see what my phone was recognized at so I'm not sure about QHSUB_DLOAD but I do know it had no vital signs not even charging light! What I did was immediately put another battery in my device and it came back to life ! If you do have another battery put it in and see if this works for you. It worked for me! But like I said, I don't know if device was QHSUB_DLOAD or not because I did not test it. All I know is it had no charging light or anything! It's sure worth a try ! I wish you the best and hopefully this issue will be resolved soon.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.
Click to expand...
Click to collapse
Hello and thank you for your reply, I already tried with another identical battery and charging, but unfortunately to no avail, now I'm trying to let it charge without battery for about ten hours, hopefully good!

I doubt if its a brick, What I think is that HTC put some code into the kernel and other things that means if the phone has run completely flat then it wont boot up until at least 40% charged - This is what has happened to me and lots of others

Jonny said:
I doubt if its a brick, What I think is that HTC put some code into the kernel and other things that means if the phone has run completely flat then it wont boot up until at least 40% charged - This is what has happened to me and lots of others
Click to expand...
Click to collapse
I tried to turn it on with a battery that had at least 70% charge, and unfortunately did not come on.

Very strange. What were you doing before the battery died? This could be an important factor in what is
Happening. Were you flashing anything ? Or changing anything ? Were you in the middle of anything? Very strange it would do this from just the battery draining ? I've heard of this happening to others also when battery drains to zero. It kind of makes me afraid of draining my battery to zero. I do wonder what exactly causes this. You say you tried a new battery and the charging advice given in posts and still no joy. I wish I could be of more help but I'm not even sure why this would happen .I do hope you get this issue solved soon! I wish you the best.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.

realsis said:
Very strange. What were you doing before the battery died? This could be an important factor in what is
Happening. Were you flashing anything ? Or changing anything ? Were you in the middle of anything? Very strange it would do this from just the battery draining ? I've heard of this happening to others also when battery drains to zero. It kind of makes me afraid of draining my battery to zero. I do wonder what exactly causes this. You say you tried a new battery and the charging advice given in posts and still no joy. I wish I could be of more help but I'm not even sure why this would happen .I do hope you get this issue solved soon! I wish you the best.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.
Click to expand...
Click to collapse
I also can not understand what happened.
Before the phone is turned off, I was playing a game. I was not fleshad it, touching it with sensitive data.
I flashed a Rom for weeks and everything worked without any problem.
I have NEVER done any overclocking the system.
The only thing I think is that it is a hardware problem and the battery was just a coincidence.
I think I'll try with the assistance hoping to be adjusted with the warranty.
I attach the phone to a sheet where I describe what happened, what do you think I can write to you to be as convincing as possible and do not put a check in the bottom of the story?
Thank you very much! :good:

Have you tried using the sensation unbricking project? They deal with phones stuck in download mode from wrong s-0n. You may have luck there with that tool.
Sent from my HTC Sensation XE using xda premium

heavy_metal_man said:
Have you tried using the sensation unbricking project? They deal with phones stuck in download mode from wrong s-0n. You may have luck there with that tool.
Sent from my HTC Sensation XE using xda premium
Click to expand...
Click to collapse
I tried this solution but when I run the script to find the phone (. / Brickdetect.sh) misses the phone and I can not go on.

Just tell the warentee people that the phone just simply died. I wouldn't go into the part about it being bricked if I were you. Then they can say you somehow caused it. Actually the less you say the better! Don't tell them its rooted, don't tell them its bricked just play ignorant and say it died and won't charge. They will replace it then. When they ask questions play as ignorant as possible ! This will work in your favor. If you go into the part about it being bricked it will raise a red flag up and likely they will blame you. Simply say it died.. ..it won't charge. .....that's it. I don't think you will have any trouble that way. And surely it will be replaced ! No worries friend. But between us how the hell does a dead battery brick a phone? Its bizarre. Now I'm going to make sure and never run my battery to zero again! It makes me worried. So strange don't you think ? Oh well I know they will replace it and all will be good. Please keep us posted on what happens OK. Best wishes to you and don't worry they should replace it without any problem.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.

realsis said:
Just tell the warentee people that the phone just simply died. I wouldn't go into the part about it being bricked if I were you. Then they can say you somehow caused it. Actually the less you say the better! Don't tell them its rooted, don't tell them its bricked just play ignorant and say it died and won't charge. They will replace it then. When they ask questions play as ignorant as possible ! This will work in your favor. If you go into the part about it being bricked it will raise a red flag up and likely they will blame you. Simply say it died.. ..it won't charge. .....that's it. I don't think you will have any trouble that way. And surely it will be replaced ! No worries friend. But between us how the hell does a dead battery brick a phone? Its bizarre. Now I'm going to make sure and never run my battery to zero again! It makes me worried. So strange don't you think ? Oh well I know they will replace it and all will be good. Please keep us posted on what happens OK. Best wishes to you and don't worry they should replace it without any problem.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.
Click to expand...
Click to collapse
That usb mode is for RIFF box resurection. Mode in witch u can flash bootloader, it must be done with riff jtag box! Trust me, i know what i'm talking about... For some reason, bootloader is corrupted. You can aks that in any mobile service shop that have riff.
It's a very simple to flash it again, after that you can flash stock or custom rom. After that everything will be fine again!
Sorry for my eng...
Sent from my HTC Sensation Z710e using xda premium

Just before you do anything else does the phone vibrate at all still? When you try turn it on? And were you s-off
Sent from my HTC Sensation XE using xda premium

Hello im new here.. but the exact same thing happened to me...I just bought an HTC sensation 4G and was gonna use it but when I put my sim card in and turned it on, it booted up to T-Mobile and then shut off. Now it ddoesn't even boot up at all no led nothing .... when I connected it to PC it said the QHSUSB_DLOAD. Should I try doing the HTC unbricking method? Btw the phone isn't rooted and has s-on since I just got it
Sent from my LG-P500 using xda premium

realsis said:
Just tell the warentee people that the phone just simply died. I wouldn't go into the part about it being bricked if I were you. Then they can say you somehow caused it. Actually the less you say the better! Don't tell them its rooted, don't tell them its bricked just play ignorant and say it died and won't charge. They will replace it then. When they ask questions play as ignorant as possible ! This will work in your favor. If you go into the part about it being bricked it will raise a red flag up and likely they will blame you. Simply say it died.. ..it won't charge. .....that's it. I don't think you will have any trouble that way. And surely it will be replaced ! No worries friend. But between us how the hell does a dead battery brick a phone? Its bizarre. Now I'm going to make sure and never run my battery to zero again! It makes me worried. So strange don't you think ? Oh well I know they will replace it and all will be good. Please keep us posted on what happens OK. Best wishes to you and don't worry they should replace it without any problem.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.
Click to expand...
Click to collapse
Thanks a lot of good advice.
I will keep you updated on the matter, I'm going to deliver assistance in the phone.
I also can not understand what happened, I flashed a dozen times without any problems and always with caution, and now I'm a brick phone just because the charge is arrived at 1%
djoxdev said:
That usb mode is for RIFF box resurection. Mode in witch u can flash bootloader, it must be done with riff jtag box! Trust me, i know what i'm talking about... For some reason, bootloader is corrupted. You can aks that in any mobile service shop that have riff.
It's a very simple to flash it again, after that you can flash stock or custom rom. After that everything will be fine again!
Sorry for my eng...
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
We had heard about this solution, now first try with the help hoping that me to adjust it with the warranty, if it is not rather use this method!
heavy_metal_man said:
Just before you do anything else does the phone vibrate at all still? When you try turn it on? And were you s-off
Sent from my HTC Sensation XE using xda premium
Click to expand...
Click to collapse
The phone when the battery is exhausted never gave any sign of life, it is a real damn brick.
Ecuadude said:
Hello im new here.. but the exact same thing happened to me...I just bought an HTC sensation 4G and was gonna use it but when I put my sim card in and turned it on, it booted up to T-Mobile and then shut off. Now it ddoesn't even boot up at all no led nothing .... when I connected it to PC it said the QHSUSB_DLOAD. Should I try doing the HTC unbricking method? Btw the phone isn't rooted and has s-on since I just got it
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Also your story is strange.
If you have just bought and the guarantee I would refer back immediately demanding immediate replacement.
If not you can try with the unbricking project. With me it was not successful!

no i mean now that you i assume have charged the battery does it vibrate or is it totally dead?

heavy_metal_man said:
no i mean now that you i assume have charged the battery does it vibrate or is it totally dead?
Click to expand...
Click to collapse
No, I did bettery load up to 80%, I tried to load it for one night, I tried to load it without battery, I've tried everything, but gives no sign!

Bern_ said:
Thanks a lot of good advice.
I will keep you updated on the matter, I'm going to deliver assistance in the phone.
I also can not understand what happened, I flashed a dozen times without any problems and always with caution, and now I'm a brick phone just because the charge is arrived at 1%
We had heard about this solution, now first try with the help hoping that me to adjust it with the warranty, if it is not rather use this method!
The phone when the battery is exhausted never gave any sign of life, it is a real damn brick.
Also your story is strange.
If you have just bought and the guarantee I would refer back immediately demanding immediate replacement.
If not you can try with the unbricking project. With me it was not successful!
Click to expand...
Click to collapse
Yes, this bothers me also. And its not the first time I've heard of this happening. I read somewhere that some batteries when brought down to zero or one percent have a deep sleep trigger that most chargers can't bring the battery out of and I'm wondering if that happened and effected the device somehow? Somehow bricking it? This is just a thought, I don't know for sure but it's all I can think of that could have possibly happened. Just guessing here but it's possible ? Perhaps? I can't imagine what else could have happened?? I now will try to never bring my battery down to zero. Just in case....it could be completely unrelated but it seems suspicious. Also having heard this happening before makes me wonder?? I do Hope you get your replacement soon and all goes well for you! Please do keep us posted on what happens and good luck!!
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.

[Q] HTC Sensation Keeps Shutting Off by Itself

A very good day to everyone.
I have been using my HTC Sensation for a year and a half already and recently it's starting to crank up.
It started last week when I was using my phone when suddenly it just switched off by itself and no matter how I attempted to switch it back on again it would boot up to the lock screen page and baam, it shuts off again. It doesn't restarts by itself or anything, it just simply switches off and no, I am unable to switch it on again. The only time I am able to do so again is when I plug it into a power source, that is when it would finally be able to start up.
At first I thought that it wasn't something big until recently it started occuring more frequently and I noticed that it only occurs whenever I have my 3G switched on. If I'm plugged in, my phone would still be working without switching off even though I have my 3G switched on. But when I unplug it from its power source, I'll be able to use it with 3G on for a good 20-30mins or even lesser at times and there it goes shutting off by itself again. What actually got me dumbfounded is how I can be having 80% of battery power when this happens.
I have tried the using a card/paper as a wedge for the battery so that it connects better but to no avail even though I have noticed that indeed, my battery seems to have some extra allowance for it to fidget about within the confinements of the spot which is allocated for the battery. I have tried the switching the phone's data usage to GSM only as well as switching it to WCDMA only but both still didn't work. I have also done a factory wipe which didn't work, super wiped it before flashing ARHD once again which didn't work as well.
To make things worse, my phone is not covered under warranty anymore and my only last hope is that the problem lies with my phone's battery rather than the PCB board which is why I'm putting all my hope on the Anker battery which stocks would only come in next Monday which I don't wanna spend on only to find out that it's not gonna be able to save my phone from its miserable plight...
This is my phone's setup:
Android Version 4.0.3
Sense Version 3.6
Software Number - Android Revolution HD 6.8.0 XE by mik1986
Kernel Version - 3.0.16-g31a4fc7 [email protected] #1 SMP PREEMPT
Baseband Version - 11.76A.3504.00P_11.24A.3504.31_M
I'm really desperate to find a solution to this so if there's anyone of you who has faced this issue/solved this issue please enlighten me as to what I can do, any/all help would be greatly appreciated.

Try other Roms..yrs might be unstable...
Sent from my HTC Sensation XE with Beats using xda-titanium app

I've tried other ROMS already but it still force shuts itself whenever my phone's 3G is switched on. Any solutions?

seems like a radio problem ..reflash the firmware you are having or ..flash 3.33/3.32 universal firmware from kohr-ah firmware thread in sensation development section
once done ..get getril app ..open it and flash proper ril for the firmware if you not having matching ril

I've been using the 3.33 firmware for quite a while already but it's still not working. :/

Sorrowed said:
I've been using the 3.33 firmware for quite a while already but it's still not working. :/
Click to expand...
Click to collapse
Reflash it and see ...
Sent from my Nexus 7 using xda premium

ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.

I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon

It would help a lot of we had your last_kmsg file. To get the file, you can use this app: https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack. Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it

ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried reflashing the 3.33 firmware but it keeps telling me that the installation has been aborted.
Skipjacks said:
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.
Click to expand...
Click to collapse
I've tried this method of yours as well but apparently it tells me the same thing when I try to flash the firmware. "Installation aborted" and I don't know why is this happening...
stanix.de said:
I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon
Click to expand...
Click to collapse
I've found a seller over here in my country who I'm going to be meeting tomorrow and finally test it out as to whether has it been my battery's problem or is it just my hardware being faulty. Will test it out and let you know of the end results, thanks mate!
android1234567 said:
It would help a lot of we had your last_kmsg file. To get the file, you can use this app: LumberJack(Had to change due to my account lacking the minimum requirement of 10 posts before I can post a link) Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it
Click to expand...
Click to collapse
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?

Sorrowed said:
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?
Click to expand...
Click to collapse
No, it would not.

Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.

Sorrowed said:
Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.
Click to expand...
Click to collapse
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:

TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
Definitely! Thank goodness it was just the battery otherwise there goes a great phone. Not to mention that with the anker battery it has a greater and better lifespan!

TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
My situation is identical to yours. 1,5 years old, constantly rebooting, after reboot the battery power drops to 4%. If it's connected to the power cord it works normally. Already ordered Anker battery and I'll see what happens.
If I look closely, I can see that my battery is a little bloated and not completely flat. Did anybody else noticed that?
So I guess all of this should be written on HTC Sensation FAQ page since it's not a bug, but a feature...