Related
Hey everyone! I'm new here in a way with this being my first post but have been on xda for months lurking the forums and absorbing information having to do with samsung vibrant to now the g2. Before i ask my question I must say this website is the best website i have EVER got any sort of information about phones and everything and anything you can possibly do with them! And want to say thank you to EVERYONE who makes it possibly! Now for the question and some sort of problem. I permrooted my g2 last night and everything to my knowledge has gone well. I also even turned S-Off and now i can boot into recovery no problem. The only problem I seem to have and can't find the solution through google or on the forums is that when I have my phone completely powered down and put it on the charger after it's powered down the phone will just automatically boot into recovery without me even doing it. It says "go back to end debugging" when I go to check the key test and I really don't understand what and where it's talking about debugging when I just have my phone plugged into a outlet. If anyone has this problem or maybe has solved this with some sort of solution your insight would be greatly appreciated.
Nickb1989 said:
Hey everyone! I'm new here in a way with this being my first post but have been on xda for months lurking the forums and absorbing information having to do with samsung vibrant to now the g2. Before i ask my question I must say this website is the best website i have EVER got any sort of information about phones and everything and anything you can possibly do with them! And want to say thank you to EVERYONE who makes it possibly! Now for the question and some sort of problem. I permrooted my g2 last night and everything to my knowledge has gone well. I also even turned S-Off and now i can boot into recovery no problem. The only problem I seem to have and can't find the solution through google or on the forums is that when I have my phone completely powered down and put it on the charger after it's powered down the phone will just automatically boot into recovery without me even doing it. It says "go back to end debugging" when I go to check the key test and I really don't understand what and where it's talking about debugging when I just have my phone plugged into a outlet. If anyone has this problem or maybe has solved this with some sort of solution your insight would be greatly appreciated.
Click to expand...
Click to collapse
It is a known issue of ClockWork Recovery. Nothing we can do now, until/IF Koush-the author of CW OR anyone knowledgeable enough to sort it out.
androidtoy09 said:
It is a known issue of ClockWork Recovery. Nothing we can do now, until/IF Koush-the author of CW OR anyone knowledgeable enough to sort it out.
Click to expand...
Click to collapse
on the dot.
its specifically within cwm, even other phones are experiencing the same issues with cwm
So no possible fix or something like that to keep it from happening? I mean I usually shut my phone at night just to give it a rest and to charge but now I can't because of recovery. Does everyone who permroots their phone experience this or only some?
Sent from my T-Mobile G2 using XDA App
Nickb1989 said:
So no possible fix or something like that to keep it from happening? I mean I usually shut my phone at night just to give it a rest and to charge but now I can't because of recovery. Does everyone who permroots their phone experience this or only some?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
No possible fix I've seen as of yet. I'm sure many people do witness this happening, but I personally never turn my phone off at night just to charge it. I hear its not good for batteries to over charge them again and again. I usually charge mine in morning and throughout the day and leave it be over night.
r3s-rt said:
No possible fix I've seen as of yet. I'm sure many people do witness this happening, but I personally never turn my phone off at night just to charge it. I hear its not good for batteries to over charge them again and again. I usually charge mine in morning and throughout the day and leave it be over night.
Click to expand...
Click to collapse
There's no such thing as over charging Lithium Ion battery lol. You can plug it in 24/7 and be safe. It is a myth.
Read this: http://batteryuniversity.com/index.php/learn/article/charging_lithium_ion_batteries
It is impossible to overcharge Lithium Ion Battery.
Well I guess I'll just have to wait and deal with it until a fix hopefully comes out for it. And ya I never heard of overcharging lithium ion batteries...but idk. Now while waiting for a fix for that little bug i'd like a flashable overclock
Sent from my T-Mobile G2 using XDA App
androidtoy09 said:
There's no such thing as over charging Lithium Ion battery lol. You can plug it in 24/7 and be safe. It is a myth.
Read this: http://batteryuniversity.com/index.php/learn/article/charging_lithium_ion_batteries
It is impossible to overcharge Lithium Ion Battery.
Click to expand...
Click to collapse
Nickb1989 said:
Well I guess I'll just have to wait and deal with it until a fix hopefully comes out for it. And ya I never heard of overcharging lithium ion batteries...but idk. Now while waiting for a fix for that little bug i'd like a flashable overclock
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Meh. I've had a bunch of people tell me they had to buy new batteries from leaving their phone charging all night and a few reps have told me not to do it. I think specifically that was when I had my BlackBerry. That's only reason I thought that. =P Either way, thanks for the info. Learning is great. =]
Well i can tell you i had an adp1 and my wife had a g1 she would charge throughout the day and i only charged at night. While we both had to get new bats because of swelling hers died a lot faster then mine. So i say charge when its dead at night is better but thats just mho.
Sent from my HTC Vision using XDA App
shortlived said:
Well i can tell you i had an adp1 and my wife had a g1 she would charge throughout the day and i only charged at night. While we both had to get new bats because of swelling hers died a lot faster then mine. So i say charge when its dead at night is better but thats just mho.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I agree. Night time charging to me seems to be the best amd I've never had a problem with a battery from doing that. Even if the phone wasn't completely dead. Seems to be ok with me lol
Sent from my T-Mobile G2 using XDA App
ever notice ur phones charging led change colors when its full? we have a smartphone fellas, its smart enough to hold a charge, stop charging, let it trickle, and maintain a full charge safely.
Sent from my T-Mobile G2 using XDA App
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.
Does anyone know where I can find the original backup for my Verizon Galaxy Nexus? I got a refurbished phone sent to me Monday and I have to send the phone back because the headset cant hear phone calls and I have rooted my phone and upgraded it to Jellybean without backing up the original OS
Use the second link in my signature
Sent from my Galaxy Nexus using Tapatalk 2
If you want an even older build that what Zepius suggested, you can always look at oldblue910's website: http://www.randomphantasmagoria.com
I'm sorry if this is too off topic. But I don't know what thread to place the question on.
I was told by a Verizon rep (taking his words with large grains of salt) that they have had more Nexus's returned than any other recent device. Its plagued with issues. And a few of them are 4G connectivity issues. Where it will be always connecting and disconnecting from 4G many times a day, even in a fully covered area. The GPS does power cycling all the time using much more battery than necessary. And horrible battery, buggy interface are just a few he mentioned to me.
Are these issues just a Verizon rep trying to push me away from a open and rootable device? Or are they real? And if so, are they only with the Stock Nexus ROM, and most if not all are fixed after flashing one of the many Custom ROMs available? What are some of the most common issues with the Verizon LTE version of the Galaxy Nexus? Both before and flashing a Custom ROM.
Thank you guys for any help, and God Bless
clem11388 said:
I'm sorry if this is too off topic. But I don't know what thread to place the question on.
I was told by a Verizon rep (taking his words with large grains of salt) that they have had more Nexus's returned than any other recent device. Its plagued with issues. And a few of them are 4G connectivity issues. Where it will be always connecting and disconnecting from 4G many times a day, even in a fully covered area. The GPS does power cycling all the time using much more battery than necessary. And horrible battery, buggy interface are just a few he mentioned to me.
Are these issues just a Verizon rep trying to push me away from a open and rootable device? Or are they real? And if so, are they only with the Stock Nexus ROM, and most if not all are fixed after flashing one of the many Custom ROMs available? What are some of the most common issues with the Verizon LTE version of the Galaxy Nexus? Both before and flashing a Custom ROM.
Thank you guys for any help, and God Bless
Click to expand...
Click to collapse
This is my 3rd Galaxy Nexus. The first had a software issue. The second one, which was a new device, stopped charging while the phone was on. Replaced the battery and the phone still wouldnt hold a charge. This one is a refurbished replacement phone and since I've rooted it and installed Jelly Bean, I can only use the phone on speaker, wired headset, and bluetooth. I took the second phone to the Verizon dealer and the sales rep said his Nexus was starting to exhibit the same thing my phone started to do.
llenroht said:
This is my 3rd Galaxy Nexus. The first had a software issue. The second one, which was a new device, stopped charging while the phone was on. Replaced the battery and the phone still wouldnt hold a charge. This one is a refurbished replacement phone and since I've rooted it and installed Jelly Bean, I can only use the phone on speaker, wired headset, and bluetooth. I took the second phone to the Verizon dealer and the sales rep said his Nexus was starting to exhibit the same thing my phone started to do.
Click to expand...
Click to collapse
Have you ever tried a ICS ROM? One that has had much work done with it and has been labeled fully stable and released? Jelly Bean ROMs seem to all be in fairly early stages. So its really hard to know if the issues were with the ROM or with the phone.
Can any one confirm @llenroht 's list of issues? And are these fairly common, even when using a ISC Custom ROM?
Hey I have been noticing a weird issue with my phone.
Ive flashed a few different ROMS to see if it was a specific one or if it is something else. Yes, that didnt work.
I am still having random turn offs which shut the phone down. Whether on it or not it happens at least twice a day.
Does this have something to do with the battery? When i reboot the phone the battery level shows at what it was...
last example I had was 68%. So it wasnt fully dead. I was going to send my phone back but decided to stick it out and maybe a new
battery will work? Any help will be greatly appreciated.
Take your battery out and place it on a flat surface. Try to spin it. If it spins, it's time to replace it.
Sent from my SPH-D710 using xda premium
Try a stock rom for a few days if the battery seems fine. My phone has the sleep of death issue with various jellybean AOSP based Roms.
deviouskind said:
Hey I have been noticing a weird issue with my phone.
Ive flashed a few different ROMS to see if it was a specific one or if it is something else. Yes, that didnt work.
I am still having random turn offs which shut the phone down. Whether on it or not it happens at least twice a day.
Does this have something to do with the battery? When i reboot the phone the battery level shows at what it was...
last example I had was 68%. So it wasnt fully dead. I was going to send my phone back but decided to stick it out and maybe a new
battery will work? Any help will be greatly appreciated.
Click to expand...
Click to collapse
One thing I've noticed. My Battery will get extremely hot. I'll pull the battery, wait for 5 min, put the Battery back in and will be able to proceeded.
Just my $.02 worth
It's certainly the battery, only fix is to replace it.
Happens to me once every other day. Not a big problem just take out the battery and replace it back in.
I'm about to change the rom temporarily from goodness to blu kuban to see if it continues.
If it does then it has to be a battery issue at least on my end...
Sent from my SPH-D710
Time for a new battery.
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
Battery issue with Galaxy SII
The shutdown issue seems to be inherent in many SII regardless of carrier. I have had this problem with my Sprint phone since new. It has been exchanged twice thus far but the problem continues. Samsung will tell you to do a factory reset. DONTdo it. It will not fix the problem.
It is NOT the battery in most cases.
It seems to be OS related. I have cleaned the battery contacts; not charged unless below 20%; unchecked the Power Saver and Optimization functions; and did a factory reset without loading in any additional apps for awhile. Nothing stopped it from shutting down.
I was able to prevent shutdown for about a two week period by not charging it until it went below 20%.
I did notice that my RAM consumption was over 60% prior to the phone acting up.
Could it be a memory issue?
Thus far, I have not received any real support from Samsung or Sprint. The Galaxy SII is one of the few phones that cannot be run through a diagnostc test by Sprint. If you have warranty coverage, they will replace it but I can almost guarantee the problem will beda plague to the new one.
If anyone has found a solution to this shutdown thing, I would love to know it. Right now, I check my phone status very often throughout the day to see whether it is one or not.
:crying:
qanda said:
The shutdown issue seems to be inherent in many SII regardless of carrier. I have had this problem with my Sprint phone since new. It has been exchanged twice thus far but the problem continues. Samsung will tell you to do a factory reset. DONTdo it. It will not fix the problem.
It is NOT the battery in most cases.
It seems to be OS related. I have cleaned the battery contacts; not charged unless below 20%; unchecked the Power Saver and Optimization functions; and did a factory reset without loading in any additional apps for awhile. Nothing stopped it from shutting down.
I was able to prevent shutdown for about a two week period by not charging it until it went below 20%.
I did notice that my RAM consumption was over 60% prior to the phone acting up.
Could it be a memory issue?
Thus far, I have not received any real support from Samsung or Sprint. The Galaxy SII is one of the few phones that cannot be run through a diagnostc test by Sprint. If you have warranty coverage, they will replace it but I can almost guarantee the problem will beda plague to the new one.
If anyone has found a solution to this shutdown thing, I would love to know it. Right now, I check my phone status very often throughout the day to see whether it is one or not.
:crying:
Click to expand...
Click to collapse
What rom/build are you on? Rooted?
Your problem isn't a common topic here unless your running experimental nightlys or doing a bad flash/install or your battery is no good.
I have two Epics since 10/2011 and have never encountered this condition. We did replace the batteries on both phones in 12/12 because of rapid discharges, going from 90% to 50% after a reboot or running a system heavy app like browser, camera, or YouTube.
Other than that all we do is use and charge when necessary.
Both phones are rooted, her phone is a workhorse because of her job, fashion design NYC, keeping track of 4 email accounts (2 gmail, 2 Microsoft Eexchange) plus crazy messaging all day long.
Check your phone model.
It may be different. Maybe you have the wrong battery in your phone?
There where some instances that had some Epic's with 1500 mha batteries instead of 1800mha!
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
Battery Issue?
PanchoPlanet said:
What rom/build are you on? Rooted?
Your problem isn't a common topic here unless your running experimental nightlys or doing a bad flash/install or your battery is no good.
I have two Epics since 10/2011 and have never encountered this condition. We did replace the batteries on both phones in 12/12 because of rapid discharges, going from 90% to 50% after a reboot or running a system heavy app like browser, camera, or YouTube.
Other than that all we do is use and charge when necessary.
Both phones are rooted, her phone is a workhorse because of her job, fashion design NYC, keeping track of 4 email accounts (2 gmail, 2 Microsoft Eexchange) plus crazy messaging all day long.
Check your phone model.
It may be different. Maybe you have the wrong battery in your phone?
There where some instances that had some Epic's with 1500 mha batteries instead of 1800mha!
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
Click to expand...
Click to collapse
Phone is not rooted....straight OS. I will check the battery to ascertain if it is a 1500 or 1800.
Phone is an SPHD710. It's only three months old and has been swapped twice by Sprint. I think it may be ICS. When I got it, they updated it to the latest OS which was ICS fron Gingerbread, so I don't know if it would have had the same problem with GB.
I'll try to get a new battery from them and see if it makes any difference.
Thanks.
qanda said:
Phone is not rooted....straight OS. I will check the battery to ascertain if it is a 1500 or 1800.
Phone is an SPHD710. It's only three months old and has been swapped twice by Sprint. I think it may be ICS. When I got it, they updated it to the latest OS which was ICS fron Gingerbread, so I don't know if it would have had the same problem with GB.
I'll try to get a new battery from them and see if it makes any difference.
Thanks.
Click to expand...
Click to collapse
Most definitely I would say ICS. !!!!!
If it had been left on gb you wouldn't be experiencing these issues. :thumbup:
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
deviouskind said:
Hey I have been noticing a weird issue with my phone.
Ive flashed a few different ROMS to see if it was a specific one or if it is something else. Yes, that didnt work.
I am still having random turn offs which shut the phone down. Whether on it or not it happens at least twice a day.
Does this have something to do with the battery? When i reboot the phone the battery level shows at what it was...
last example I had was 68%. So it wasnt fully dead. I was going to send my phone back but decided to stick it out and maybe a new
battery will work? Any help will be greatly appreciated.
Click to expand...
Click to collapse
Sounds like the power button might be going bad. If you are not getting sudden large drops or increases in battery % I would lean towards the power button.
Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
I'm having the same sort of issues on my S2. I've had it for about 6-7 months and it's worked fine but the last few weeks it's been almost unusable. Within 5-10 minutes of using my phone it will shut off, regardless of the battery level. Turning it back on would show that it was critically low on battery and it would shut off again within seconds. Plugging it into a charger would let me turn on again and restore the battery level to what it was, oftentimes over 60%.
It seems that the false battery reports come and go, but the real problem is that the phone just keeps turning off. It's useless without a charger anymore. I've looked on Sprint's forums and it seems like many people have been having the same problem. Especially after the new JB update. I've been running stock so I figured I might try a custom rom. I rooted and went back to FF18 but I can't load up a custom recovery to install a ROM. The link to download the autoroot package in this thread is dead.
I have run into the same issue starting about three weeks ago. I am already on my second battery, which is only six months old, but it was behaving as if it was dying again, so I got another brand new one from the sprint store just to make sure... Phone was still shutting off though. After some more research, I came across someone who had a bad card reader in their phone. They even wrote a program that keeps track of mounts, ejects, and bad ejects. I downloaded it (its called sd card monitor), and sure enough, my card is ejecting itself multiple times an hour (which is no surprise, this phone has destroyed several cards already)... If I remove the card, I have no more problems... So for now, I am using my phone without a sd card. I am not paying Sprint $50 for a refurbished replacement at this point, I am fed up with their service and will be changing carriers after the S4 comes out...
The strange thing though, the sd card issue doesn't affect the phone if it's plugged in.
MECHAnized said:
I'm having the same sort of issues on my S2. I've had it for about 6-7 months and it's worked fine but the last few weeks it's been almost unusable. Within 5-10 minutes of using my phone it will shut off, regardless of the battery level. Turning it back on would show that it was critically low on battery and it would shut off again within seconds. Plugging it into a charger would let me turn on again and restore the battery level to what it was, oftentimes over 60%.
It seems that the false battery reports come and go, but the real problem is that the phone just keeps turning off. It's useless without a charger anymore. I've looked on Sprint's forums and it seems like many people have been having the same problem. Especially after the new JB update. I've been running stock so I figured I might try a custom rom. I rooted and went back to FF18 but I can't load up a custom recovery to install a ROM. The link to download the autoroot package in this thread is dead.
Click to expand...
Click to collapse
Can you confirm that your phone is having the same issues due to the card reader.?
If so please share.
(Otherwise you need a new battery.)
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
PanchoPlanet said:
Can you confirm that your phone is having the same issues due to the card reader.?
If so please share.
(Otherwise you need a new battery.)
Click to expand...
Click to collapse
I ran that SD card monitor app for about 4 hours and no disconnects, so I guess it's a battery issue.
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.