Hello friends, i have samsung galaxy s5, when i bought it , it was running kit kat 4.4.2, i updated it to lollipop 5.0 OTA, it was okay and running smooth for a few days, now it is generating heat at the back , because of which the battery percentage drops by 1-2 % after one minute, which is very annoying, i hard rest my s5, the problem was gone for few hours, but then come back , i again hard reset it, and also formatted my MMC, but now after few hours it still showing that problem, please can some one help me here, i love my s5, i dnt want to lose it any one here please provide a possible solution, thanks in advance.
Hard reset?
Factory reset fixes most issues caused by leftover KK files
toohurt said:
Hello friends, i have samsung galaxy s5, when i bought it , it was running kit kat 4.4.2, i updated it to lollipop 5.0 OTA, it was okay and running smooth for a few days, now it is generating heat at the back , because of which the battery percentage drops by 1-2 % after one minute, which is very annoying, i hard rest my s5, the problem was gone for few hours, but then come back , i again hard reset it, and also formatted my MMC, but now after few hours it still showing that problem, please can some one help me here, i love my s5, i dnt want to lose it any one here please provide a possible solution, thanks in advance.
Click to expand...
Click to collapse
Hi toohurt,
I have been having this issue as well, it sounds like its a bug with the lollipop update for s5. If you are with verizon, supposedly their latest update fixes the issue, so I would try that first.
I saw some advice on another forum that if the hard reset didnt work, that rebooting the phone about 5 minutes after you take it off the charger can at least help stabilize the battery drain a little. I've also seen that uninstalling Google Fit and then disabling the "S Health" app can help.
As a last resort you can always go back to kit kat.
Hopefully that helps!
*Detection* said:
Hard reset?
Factory reset fixes most issues caused by leftover KK files
Click to expand...
Click to collapse
Yes by hard reset i mean factory reset, still the problem remains
Goldmeyer said:
Hi toohurt,
I have been having this issue as well, it sounds like its a bug with the lollipop update for s5. If you are with verizon, supposedly their latest update fixes the issue, so I would try that first.
I saw some advice on another forum that if the hard reset didnt work, that rebooting the phone about 5 minutes after you take it off the charger can at least help stabilize the battery drain a little. I've also seen that uninstalling Google Fit and then disabling the "S Health" app can help.
As a last resort you can always go back to kit kat.
Hopefully that helps!
Click to expand...
Click to collapse
Yes dear i do the same, reboot my cell phone for 5 minutes, so the problem goes away for some time, i dnt want to go back to kit kat, waiting for 5.0.1 or 5.1 , may be that will solve the problem, and no mine is not on verizon, and can u tell me how to disabale s health please
Related
hi everybody.
I have a samsung galaxy s4 gt-i9505 which is rooted running echo rom 4.3 and all of a sudden my phone has started to reboot itself constantly..(rebooted about a dozen times already today and ive only been awake about 2 hours!!)
What i was wondering is...
Can i go back to my 4.2.2 backup i made in recovery and then flash the official 4.3 update with odin (i know this will trigger knox but i need my phone to work)
If there are any other suggestions anyone has which will not trigger knox it would be greatly appreciated.
many thanks.
What is your battery serial number?!
Read this thread http://forum.xda-developers.com/showthread.php?t=2488245.
A friend of mine had the same reboot problems and they changed his battery. And gave him a free new one but from the same batch with problems.... now he wants to send it back again since his reboot problems reapeard.
tedfurniss said:
hi everybody.
I have a samsung galaxy s4 gt-i9505 which is rooted running echo rom 4.3 and all of a sudden my phone has started to reboot itself constantly..(rebooted about a dozen times already today and ive only been awake about 2 hours!!)
What i was wondering is...
Can i go back to my 4.2.2 backup i made in recovery and then flash the official 4.3 update with odin (i know this will trigger knox but i need my phone to work)
If there are any other suggestions anyone has which will not trigger knox it would be greatly appreciated.
many thanks.
Click to expand...
Click to collapse
Maybe just start with going back to 4.2.2 and see if that fixes the problem first.
Then take it from there if u wanna choose a custom knox free rom or not
Hi,
do you have only battery drains or also random reboots?
the fact is that samsung shipped out a bad serie of batteries (which is confirmed by Samsung) their serial starts with BD
the symptoms of a bad battery are:
Huge battery drain
random reboots
while rebooting the phone hangs at samsungs logo
battery is swelling
phone shutting down while you have an incomming call/sms
when you are the "lucky one" to experience one of the above symptoms please replace your battery asap under warranty
if you don't do this you risk a phone exploding in the pocket of your pants this is not only painfull for your phone but also for "everything else" whats in there
^^^^^^^
Thanks for the info man.I'll let my wife test out my phone when I get it friday.
Hello , so i got my new phone galaxy note3 and i updated it to the new android 4.4.2 and it seems it drains the battery like way to fast,
in the older version of 4.3 it didnt happen at all this is so obvious that something its the Android System takes to much battery its always on top can anybody help me to root to the original stock rom of android 4.3 with all working functions? Or is any update coming to the note3 to fix this ? i know that the warranty will go off but i dont need it anyway all i want is battery !
fuad541 said:
Hello , so i got my new phone galaxy note3 and i updated it to the new android 4.4.2 and it seems it drains the battery like way to fast,
in the older version of 4.3 it didnt happen at all this is so obvious that something its the Android System takes to much battery its always on top can anybody help me to root to the original stock rom of android 4.3 with all working functions? Or is any update coming to the note3 to fix this ? i know that the warranty will go off but i dont need it anyway all i want is battery !
Click to expand...
Click to collapse
There is no unusual battery drain in 4.4.2 if not factory reseted do it, it will fix your problem, u can't go back to 4.3 now.
If you do a google search you will see there are many many users affected by the battery drain bug. Im yet to find a fix.
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
I have the same problem, can someone help ?
Any updates?
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
no good news ...
hummus said:
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
Click to expand...
Click to collapse
I think it's a defective device. You have to repair or change it. Sorry
No Sensors
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
tiagomoraisc said:
no good news ...
Click to expand...
Click to collapse
hummus said:
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
Click to expand...
Click to collapse
The same situation I have
Fix
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
I made a similar thread, and found a fix.
Here http://forum.xda-developers.com/nexus-4/help/nexus-4-jellybean-4-2-2-t3472292#post68941174
Hi
I've been trying to get to the bottom or this for months and months, no clue what to do.
Firstly, no matter what ROM i try, whether it be stock or not, sensors do not work AT ALL. I've tried about 10 ROMs, and no joy.
When i first had my phone, it was on stock 4.3 ROM, and rotation worked fine. after this i upgraded to 4.4.2 OTA and rotation still worked. As soon as i rooted my phone, all sensors died and now i cannot fix them. The phone also has a stupid amount of lag, especially when trying to answer a call. I tried then going back to stock 4.4.2, but the sensors remained broken
I have tried reinstalling Samsung HUB as i found in a few posts on the internet, but again this does nothing at all.
Can someone please please help, any ideas no matter how far-fetched are welcome,.
Thank you in advance.
Hello guys!
I'm a new guy here, but found no answers to the following issues.
So i've got the 6.0.1 update to Note 4, and now im stuck with issues like the Phone just freezes, crashes and hangs for like 1 minute after i can use it again, so i had to download the WakeLock application from the google play store.
I'm just curious, is this a phone issue, or its releated to the stock rom? I should flash a new ROM based on guides here, or is there any fixes to this issue?
Thanks.
You may have to try a factory reset. I haven't heard of this issue
Mine went into the same issues since a day or 3. Factory reset, cache wipe, no dice until now.
clawlancer said:
Hello guys!
I'm a new guy here, but found no answers to the following issues.
So i've got the 6.0.1 update to Note 4, and now im stuck with issues like the Phone just freezes, crashes and hangs for like 1 minute after i can use it again, so i had to download the WakeLock application from the google play store.
I'm just curious, is this a phone issue, or its releated to the stock rom? I should flash a new ROM based on guides here, or is there any fixes to this issue?
Thanks.
Click to expand...
Click to collapse
i had this problem with my n910C but it was after flashing custom kernel ,
factory reset and it was working like a charm then