Develop Bugs

Overheating?

I seem to be having an issue with my phone overheating and rebooting. It seems to happen consistently when using navigation or when playing games (I'm hooked on Gem Miner). Always at an inopportune time. To me this seems like a result of bad hardware or something but is it possible that rooting and installing ROMs like CM7 or Kingdom Stock Sense?
I bought my phone at Best Buy and ended up getting the warranty, so assuming I can revert the phone back to stock, I should be able to get this covered under warranty. Right?

My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible

Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.

TheWhiteBandito said:
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Click to expand...
Click to collapse
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...

k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Hot enough that it's shutting down. I couldn't tell ya specifically.

k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Its higher than 119F. Mine hit 122F the other day and didn't reboot, unless the safety shut off didn't kick in on mine. Don't think it is much higher than that though before it does.

I had heard it shuts down at 119 but my phone hasn't ever gotten that hot. I've only managed to get it up to about 114, that was multitasking and charging, overclocked to 1113.

When it reboots, do you get 5 vibrations and then the indicator flashes green until you pull the battery? If so, you are starting to have serious problems.
This thread helped me recover my Incredible..
http://forum.xda-developers.com/showthread.php?t=982454

I had mine at 120F the other day loading a new rom and no shut off
Sent from my Incredible using XDA Premium App

Mine gets hot when using wireless tether.

jetsaredim said:
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
Click to expand...
Click to collapse
I'm leaning toward a hardware issue. The reason I say that is because I'm using CM7.0.3 and Chad's Incredikernal and when I use navigation I also connect my car charger and have never had a heat issue nor any reboots. I drove from SC to FL back in Feb and had navigation running the whole time.

Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?

jetsaredim said:
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
Click to expand...
Click to collapse
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.

fLaWx said:
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
Click to expand...
Click to collapse
I assume you're not completely an expert in this matter, but let me see if I get this right... I have to go back to having CWM on my phone so I can apply the S-ON zip and then re-run the stock recovery to get back to complete 100% stock. Sound right? I wouldn't even consider it if I didn't think there was a slight chance that I'd get flagged on the warranty review for having S-OFF set. I don't want them to have any reason to deny my getting a new phone.

Hi - long time lurker, barely ever post, but I'm gonna chime in here.
My DInc also reboots, and it is warm to the touch when it does happen. Don't know how hot though sry. I've been rooted since November, but haven't installed a Custom Rom, just removed bloat, and added some other useful tools. The biggest change I've made was changing the fonts. I don't over/under clock either (it runs just fine for me). My reboots seem to be increasing in number. At first it would be once a month, then a few times a week, and now a couple times a day.
Sometimes, my phone will reboot just once, and then continue to work. Sometimes 2-3x in a row, and then continue to work or not. Sometimes, it just vibrates 5x quickly, and then is locked (LED flashes), and the only way to recover is to pull the battery and start over.
Seems to happen MOSTLY around certain times of day - 4:30-6pm when I'm on my way home from work (no, not using my phone, but it happens anyway), and around lunchtime (again, not using it, or if I am it's barely). Other times it happens too - but really randomly. I'm ruling out different apps that might be triggering it, but don't think that's the issue.
QUESTION - if it is heat related, and the phone is supposed to go into shut-down mode at 119*, but seems to be different temps for everybody, could it be the thermostat? Could it be registering a false temp reading and think it needs to shut down? Has anyone explored this?
I'm not an engineer, or even a programmer, but I like to play one on TV. Thx

Oh - I forgot to add this:
There have been times when it would reboot, and I've placed my phone and battery (removed from phone) on the vents of an airconditioner, or even sitting on a frozen ice pack (the kind for a cooler) and it would still happen afterwards. To the touch, my phone would be cold, not freezing, but cold. Seriously lower temp than what it was when it was very warm to the touch...

I'm definitely with you on the first scenario. I just brought it to my local Best Buy where I bought it (with warranty) and they sent it off and gave me a loaner DInc to use till mine's repaired. They said, if they can't repair it, they'll give me a DInc2 as a replacement since the Dinc1 is "backordered" (aka not being carried).

jetsaredim - I was able to get a replacement DInc sent to me overnight (free!). My first replacement had a faulty USB port, so I couldn't charge my phone. I have 'another' DInc being sent to me now. Other than the faulty USB port, I haven't had any overheating issues so far (knock on wood).
First phone manufactured in June 2010
First replacement phone, manufactured in April 2010, and remanufactured June 2011 (via ##7764726)

I just got my replacement Incredible today. I just tested my original phone again by watching 15 minutes of video on youtube and BANG!!!!!!!!!! It rebooted as usual. Screen and battery get very warm. The reboots seem to happen when watching videos online or offline, playing games for 10 to 15 minutes, browsing the web for 15 to 20 minutes, using Google Maps with or without charging at the same time, and charging and talking on the phone at the same time. Well, I'm sending back the original and hoping that the replacement doesn't fail me. Glad that I swapped it just before the manufacturer warranty was up.

Have had the Dinc since week one. 100% stock - have not rooted (yet) and stock battery - in the past month it has 'overheated" and rebooted twice. Never happened before. Both times while using navigation and charging. Could it simply be the battery? It's not holding a charge like it used to too which also makes me wonder about the battery.

bricked using alpharev

Hi guys, I have a massive itch, I am badly in need of memory and I am sick of a2sd, so the obvious route is alpharev. But i am bricking it Just expecting a kid right now and I can just see me gal saying "go right ahead, your infernal meddling has ruined a perfectly good phone, but no matter take £300 n git a newun!" Mmmmm...??
Anyway, just wanted to hear from some people who have bricked using alpharev (to see how many have) and if there is any way back after said bricking. I've heard you can't.
That's it, thanx in advance!

It's basically impossible to brick your device if you follow the instructions, which are very simple
Sent from my HTC Desire using XDA App

elliottg61 said:
It's basically impossible to brick your device if you follow the instructions, which are very simple
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
This.
Also you should change the thread name which is kinda confusing...

A description of your problem doesn't exist so nobody will be able to help you.
I never heard or read from someone who bricked his phone using alpharev. And if your phone is bricked it would not react anymore (as if it would be dead.
TouchPaled from Oxygen with Transparent XDA App

I'm not asking for help. Just interested in other peoples experience. I'm temped, but cautious as like I said, it's a mistake I cannot afford to rectifiy at the moment. So really all I wouldlike to know is if it had happened to others how they solved it or not.
Sent from my HTC Desire using xda premium

Hboot is the ultimate base for your phone. By using alpharev/revolutionary this gets 'updated'. If there something goes wrong, your phone is completely bricked. And there is absolutely no so solution for this. Your desire is then nothing more than an expensive paperweight.
TouchPaled from Oxygen with Transparent XDA App

However, in order for it to go wrong, the flash itself must go wrong. So a problem anywhere else along the process won't cause these kinds of problems. And because the flash of the bootloader is done by the old bootloader, the only way this can go wrong is, if you pull the battery half way through.
That will cause a serious brick though(you will never even see your screen turn on again) and that you won't recover from.

Thanx for the replys. I fully expected that sort of response about fixing the brick. Oh well. But have you guys heard of this ever happening, apart from the unlikely event of interrupted flash due to battery on laptop or phone being dead. Any stories about "alpharev ate my desire, killed my hamster & broke my toe!"
Just wondering
Sent from my HTC Desire using xda premium

Nope don't think anyone has ever bricked a device doing it my friend
Sent from my HTC Desire using XDA App

Please do read my post again...
The way this is done(and the way the bootsystem on those phones work), there is no way other than a bad bootloader flash that will actually brick your phone. And a bad bootloader flash only occurs, as i already told you, if you interrupt it by pulling the battery mid-way(pulling the plug or the computer-battery shouldn't even do it as the flash itself is done entirely by the phone). So no there is NO ONE who used alpharev as intended, who have ended up with a bricked phone.
You might see a few "brick" stories though, which is essentially just bootloops happening to people unaware how their phone work and how to fix such simple problems.

Thanx people, put my mind at ease about doing this.
Sorry, but I'm gonna ask a thick question. You mentioned bootloop and the simple fix. Er... I just take out the battery. Is that the simple fix?
PS would you use the live Linux CD or live USB. My gut tells me to use USB. But I've had a few curries recently and I don't know if I trust it all that much.
Sent from my HTC Desire using xda premium

I used the live CD and it worked without a hitch.
And bootlooping can't be fixed by removing the battery, because next time you turn it on, you'll bootloop again.
I've had one bootloop with my phone and it was fixed by just reflashing my current ROM, so I'm not too experienced with these things.

Bootloop is not a brick in any means, in fact it's 1 of the easiest things to fix.
Wipe/Factory Reset and reflash.
Thats why i want to kill people which creating threads like "HELP BRICKED MY PHONE !!!1111oneneone" and then inside i see "i'm stuck on htc logo!"

Yeah, a real brick would mean your phone is completely dead and nothing more than an expensive paperweight.
TouchPaled from Oxygen with Transparent XDA App

Dont use alpharev..
Alpharev have joined forces to come up with some epic software
Go here
http://revolutionary.io/

I am also a n00b when it comes to Android. I have decided after using almost 1 year my desire to root and s-off my phone. I always look for the detailed and visual tutorials and if you follow everything step by step it is hardly impossible to brick anything. (I have also flashed my navi, PSP and Wii before) I have used this thread http://forum.xda-developers.com/showthread.php?t=1016084and followed the videos and steps. The only thing I have to do now is to apply a custom rom on it.
You'll have no worries if you follow these steps.

don1bong said:
Alpharev have joined forces to come up with some epic software
Go here
revolutionary.io
Click to expand...
Click to collapse
thats absolutly right! this new tool did a great job for me recently (wildfire)
but the "old" alpharev.iso is doing a good job, too!
i had no probs one year ago - this livedisc is almost foolproof (if you dont touch batteries or powercables) - just follow the instructions

Australian OTA Update for OPTUS 128.980.10

128.980.10 is now out on Optus branded handsets. See any difference?
My phone was running great before, but now I am stuck at title screen, and its very difficult to scroll on the menus!
A bit wierd Im sure it will come good.
So I played with it for about 2 mins and it finally cleared up. Running pretty smooth. Some parts are super laggy, but my phone was like that when I first got it. Once I had been around the phone and seen everything the phone behaves super smooth. Its like it needs to see everything one time then its smooth.
Anyways ill report back any noticable differences over the next few days.

Just did the same update and first thing I can notice is that my WiFi has become alot more responsive. Is very quick to react when searching over WiFi and no delays. Apart from that I'm not too sure because it's too early to comment. Will keep all posted
Sent from my HTC One X using xda premium

Unfortunately, im getting a wierd error Ihave never seen before, and everything is now reaaaaly unresponsive.
It says "android.process.acore has stopped unexpectedly".
What can I do to stop this. sort of annoying cause my phone was actually pretty smooth and had great battery life before hand anyway!
EDIT:
While typing this message. I just got:
"com.android.settings" is not responding.
Help!

did ur hboot got updated ?

tids2k said:
did ur hboot got updated ?
Click to expand...
Click to collapse
WHAT!>?
Where is it.
PS My phone is getting worse and worse.. the home keys barely work anymore. i have turned it on and off. I have even done that clear contacts cache under manage sources for contact info. Sometime when I try and wake the phone from sleep with the power lock button, it just stays off, for about 45 seconds. When it comes to, it is almost bricked.. just slow and the menus wont scroll properly.

Ah yes, google search leads me here.
http://forum.xda-developers.com/showthread.php?t=755968
So my HBOOT whatever that is, is 0.94.0000

im going to have to start my phone from scratch.. sorry guys I cant recommend this update for Aussie Optus people. maybe its something simple I dont know, but i updated it following the instructions perfectly, and the phone is now screwed. Im going to try and hard reset and reinstall everything on my phone all over again.

ONE981 said:
Ah yes, google search leads me here.
http://forum.xda-developers.com/showthread.php?t=755968
So my HBOOT whatever that is, is 0.94.0000
Click to expand...
Click to collapse
damn less chances of getting s-off not good

ONE981 said:
Unfortunately, im getting a wierd error Ihave never seen before, and everything is now reaaaaly unresponsive.
It says "android.process.acore has stopped unexpectedly".
What can I do to stop this. sort of annoying cause my phone was actually pretty smooth and had great battery life before hand anyway!
EDIT:
While typing this message. I just got:
"com.android.settings" is not responding.
Help!
Click to expand...
Click to collapse
You're downloaded update had an error. Are you rooted from HTC dev? If not (judging from your question re hboot) take it back. The update failed and needs to be reflashed. Unfortunately without being rooted this can't be done. Easy enough to gain root but that has other consequences.
tids2k said:
did ur hboot got updated ?
Click to expand...
Click to collapse
yes hboot updated along with radio and firmware to 1.28 base.
ONE981 said:
im going to have to start my phone from scratch.. sorry guys I cant recommend this update for Aussie Optus people. maybe its something simple I dont know, but i updated it following the instructions perfectly, and the phone is now screwed. Im going to try and hard reset and reinstall everything on my phone all over again.
Click to expand...
Click to collapse
Hope this worked but I'm not sure it will. The android core process error is common with flashaholics who have not wiped a phone properly when changing base firmwares. Which is what we have done with the Optus ota. For me it worked fine.
tids2k said:
damn less chances of getting s-off not good
Click to expand...
Click to collapse
We will see fingers crossed.
Sent from my HTC One X using Tapatalk 2

The phone is now bricked guys. No I don't do any of this rooting stuff, I'm just learning the phone as it is from factory. I just got the Optus OTA installed it and now my phone is stuffed.
It's stuck on the 3 android with white background picture. I can't make the menu come up in this white screen. It just says "checking SD card update".
If I go to menu, normal menu with icons and sense 4.0, doesn't like any touch, completely unresponsive and will not accept me doing any functions, including resetting the phone. I can't do hard or soft reset.
Damn Optus update. Even before my phone got that green banding. Now this tops it off.

Two options return and enjoy new one. Or obtain root and flash ruu to return phone to stock software. Pick one and I can walk you through it. Will provide links to show you exact method but without flashing experience you will have questions that I can answer for you. Up to you which path you want to go.
Sent from my HTC One X using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=1609190 is probably best current how to recover tutorial. It lists a lot of options from various sections of forum.
Sent from my HTC One X using Tapatalk 2

Take it back man. Stop wasting time and get a refund before they tell you that it's too late. My One X updated fine but is the loading time while on WiFi that's honestly eating at me severely. Don't know what else to do at the moment.
Sent from my HTC One X using xda premium

ASavva said:
Take it back man. Stop wasting time and get a refund before they tell you that it's too late. My One X updated fine but is the loading time while on WiFi that's honestly eating at me severely. Don't know what else to do at the moment.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
What WiFi loading time are you referring to? Mines super fast, lot faster than the 3g connection I have.
Sent from my HTC One X using Tapatalk 2

Aust S5 said:
What WiFi loading time are you referring to? Mines super fast, lot faster than the 3g connection I have.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
the time it takes to connect to ur wifi router.

I still seem to be quick there as well. Takes my device approx 5 sec once within network. Also running extenders and no problems there. Seemless movement from one to next. Running n speeds with aes security
Sent from my HTC One X using Tapatalk 2

How's the optus version of One X ppl?
Same issues as Europe or have we got better stocks in Oz??
I'm still using gs1 on ics and it has absolutely no problems but I'm up for new upgrade.
Should I?
Thanks.
Sent from my GT-I9000 using XDA

Short answer is yes. BUT will be interesting to see sgs3 launched soon. Might suit better and you don't lose anything by waiting a week ish
Sent from my HTC One X using Tapatalk 2

Android Newb needing advice or help

Hi. I'm new here and first, want to say hello. I've been on iPhones for many years. Finally got bored and crossed over to the "Dark Side" lol.
Second....I need help!!! lol or just some good old advice. I've searched and searched but can't really find a definitive answer. Too much conflicting info out there. One thing I did learn is that this forum is thee best so here I am!
I successfully rooted my i747 Galaxy S3 (Rogers). The trouble arose when I tried to install a Custom ROM. I kept getting errors, and after a bunch of research, I read that I should update my CWM. I did and that's when the trouble started. It went into a loop. It would just stay on a black screen. I can't get into Recovery mode or anything else for that matter. It will not power up in any way. It will now show the charging indicator light when it's charging. It's as dead as my ex-wife in the sack . Obviously I've bricked it. I've learned that a jtag repair would fix it....and have since been told by an android buddy that it won't. Any advice or info would be appreciated!
The phone was on 4.1.1 and it's the Rogers i747 model (same as AT&T)
P.S, Rooting on a Mac sucks! I'm thankful that I had a PC at home too! Not that turned out too good
Update...as per Tech Support at Rogers, I removed the battery and plugged it in. The red indicator light came on. But it does not stay on and it goes out shortly after, battery in or not. Thought one more piece of info may help someone figuring this out.

Charge it as much as you can, search for the return to stock thread on here (make sure you get the one for your carrier), do that and if it isn't working after that, then you'll probably have to get it replaced.
Sent from my SGH-I747 using xda premium

Monkeymannnn said:
Charge it as much as you can, search for the return to stock thread on here (make sure you get the one for your carrier), do that and if it isn't working after that, then you'll probably have to get it replaced.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I appreciate the reply but I can't connect to the phone at all. Couldn't return it to stock even if I wanted to.

mrkay said:
I appreciate the reply but I can't connect to the phone at all. Couldn't return it to stock even if I wanted to.
Click to expand...
Click to collapse
Once it's charged, are you able to get in download mode? If so, there's a light at the end of the tunnel. Odin can bring you back up.
If your pc doesn't recognize it, reboot it (pc). Try a different cable/usb port. Reinstalling the drivers is an option too.
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
Once it's charged, are you able to get in download mode? If so, there's a light at the end of the tunnel. Odin can bring you back up.
If your pc doesn't recognize it, reboot it (pc). Try a different cable/usb port. Reinstalling the drivers is an option too.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It won't charge at all. Left it overnight and nada. I'll try again, but highly unlikely that it will. I also tried different ports as well as different computers to connect to. My only concern is that I take it back and Samsung discovers that it's been messed with. Oh well, it's only money

mrkay said:
It won't charge at all. Left it overnight and nada. I'll try again, but highly unlikely that it will. I also tried different ports as well as different computers to connect to. My only concern is that I take it back and Samsung discovers that it's been messed with. Oh well, it's only money
Click to expand...
Click to collapse
Could say that you tried to update with kies and that's what you got.. Works like a charm usually

In my stupidity I've hard bricked not one but TWO AT&T GS3's same thing black screened and nothing else. I doubt very seriously you'll get it to charge. Here's the good news I'm assuming it's still under warranty and if it is when you take it to the warranty store at AT&T they will try two batteries to see if it boots and when it doesn't you'll get a new phone. You don't have to tell them nothing. As far as you know you shut it down to charge when you went to bed and it wouldn't boot in the morning.
Worked for me needless to say I'm WAAAAAY more carefull and spend a lot of time here reading and double and triple checking everything!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

S3freak said:
In my stupidity I've hard bricked not one but TWO AT&T GS3's same thing black screened and nothing else. I doubt very seriously you'll get it to charge. Here's the good news I'm assuming it's still under warranty and if it is when you take it to the warranty store at AT&T they will try two batteries to see if it boots and when it doesn't you'll get a new phone. You don't have to tell them nothing. As far as you know you shut it down to charge when you went to bed and it wouldn't boot in the morning.
Worked for me needless to say I'm WAAAAAY more carefull and spend a lot of time here reading and double and triple checking everything!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Not to make you sound stupid, there are no such things as stupid questions here at least I've learned that while enjoy my stay here at xda, but did you accidentally flash an international ROM? This sounds like a case of it.

The first phone I hard bricked I'm sure that's what I did. It became a beautiful paper weight. Not sure what happened the second time I had got off work late and instead of going to bed I was tinkering with my phone. I don't really know what happened. Careless and not reading, not making sure of what I was doing. I learned the hard way and I spend a lot more time studying and staying with the AT&T forums for my phone.
I have to admit I've really had fun here learning.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] M7VZW Died twice, after installing cm11. Over heating and battery draining fast.

Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!

ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.

Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk

The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.

This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.

peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol

On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.

Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao

ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.

Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:

Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.

I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.

I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.

I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk

I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.