Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??
Hi guys, i'm having big issues with my phone.
I was on imperium lollipop Rom, everything went fine, and i began to have call issues (bad reception quality), so i decided to update my modem & bootloader to the last lollipop ones. Then i installed a S6 port rom (by albe95), and my phone became crazy.
I have random reboots, shutdowns, sometimes i can pass through the simcode and i use the phone normally, and then it restarts like infinite times, i have to remove the battery. I wiped data, cache, dalvik cache, system like 50 times, i flashed another roms, the problem still exists. Sometimes i can't even get through the boot, it just shuts down.
I even tried to downgrade to a kitkat firmware, and return to imperium rom still the same problem encountered.
I really don't know the problem, i can access download and recovery menus, i can flash with odin, but can't get the phone to work normally.
Has anyone had the same problem? I'm starting to think that the motherboard is bricked, but why is it so random?
Thanks for your responses.
Best regards.
Check all cables
I got the same Problem , so i checked my motherboard and ive Seen that a cable wasnt putted on
kartoffelmann.m said:
I got the same Problem , so i checked my motherboard and ive Seen that a cable wasnt putted on
Click to expand...
Click to collapse
Strange scenario, i changed the motherboard, still the same problem, removed the sd card, same problem, sim too, same problem, so i guess this comes from the battery
I updated OTA my Note 4 n910f to the latest built. It was something about Samsung Cloud. Since then i haven't been able to use my phone for even a minute. It keeps rebooting every 1 minute. When plugged in it reboots but for like every 3 minutes. And it doesn't charge, my battery was 66% when i plugged it on AC, and it keeps going down like 64% plugged it. I don't know if any of you had this issue before or are having now but i cant use my phone for 2 days now. I tried to clear cache data via recovery, also wiped storage, factory reset, wiped everything but no luck. Where is my problem, is my battery dead or software issue. I didn't have this before the last update. Help !
ArnisHoti said:
I updated OTA my Note 4 n910f to the latest built. It was something about Samsung Cloud. Since then i haven't been able to use my phone for even a minute. It keeps rebooting every 1 minute. When plugged in it reboots but for like every 3 minutes. And it doesn't charge, my battery was 66% when i plugged it on AC, and it keeps going down like 64% plugged it. I don't know if any of you had this issue before or are having now but i cant use my phone for 2 days now. I tried to clear cache data via recovery, also wiped storage, factory reset, wiped everything but no luck. Where is my problem, is my battery dead or software issue. I didn't have this before the last update. Help !
Click to expand...
Click to collapse
Flash stock firmware via odin and do a factory reset after flashing firmware.hopefully it should fix the problem. Go to (www.sammobiles.com/firmwares) choose your model number and download latest firmware.
Already did that, no luck. !
ArnisHoti said:
Already did that, no luck. !
Click to expand...
Click to collapse
Try flashing lollipop .
If the problem still persists after lollipop, then go to a service centre .
If they repair it ,well-n-good but if they don't then try rooting your device and then change the kernel.
Sent from my SM-N910G
Hello, i am new in this forum, hope to do everything right :good:
I bought a used G935F which shows a very strange behavior ...
When i got it, it stuck in bootloader. I didnt managed to install stock rom via Odin or Smart Switch, it always left Installation after "Installing Update" with 32% and went into a black Screen of death with a blue lonesome light. Went to a shop an bought a microSD card, flashed TWRP 3.1.1 and tried several custom roms. I managed to install three of them after i wiped cache, Dalvik cache, System, internal storage and formated data three times. Rebooted into recovery and installed the Rom. That worked most of the times :fingers-crossed: But after 1,5 to 3 days of usage, the mobile started crashing. First only a reboot, then some application hangs and finally a total crash with only bootloader working. Seems that system and data partitions had gone corrupt. Starting the procedure again leads to a fully working device ... for a short time, few days. Someone ever heard of that strange Kind of behavior?
Can this be caused by a faulty battery?
Tuxs68 said:
Can this be caused by a faulty battery?
Click to expand...
Click to collapse
I don't think so, because my old s7 has this same problem , i flash any firm or custom firm and when the system will boot up it's freezes in the updating system screen and "die" completely for almost one day, when the battery is discharged and i can recharge and flash a firmware again and the same problem occurs . I think that it's a motherboard issue.
Mine is actually working fine ? Managed to install a slim rom yesterday afternoon. If i start an incomplete installation, i also have to wait until battery ist empty. I wiped all caches and partitions and used twrp to install the rom. Tried a few times until installation reached 100%. THEN ... I let the device start and finish boot. That worked for me ... yesterday ... Now i can use my phone without restrictions. Hope for a loooooong time uptime is now nearly 24 hours.
Uptime now 48 hours:fingers-crossed: Hope is rising
Time of Death 11.11 PM. :crying:
Used app, app crashed, several restarts, dead. Internal storage not mountable. Actually black screen of death, i ll wait till battery is discharged. This afternoon i ll take my mobile to a repair shop to have a new battery
I do not believe that is battery issue,most likely motherboard is dying (emmc memory) i have similar symptoms and under warranty my motherboard vas replaced,
Jap, got a new Logicboard
I own a Zenfone 2 laser and it is currently stuck in bootloop, I did some researche and learnd I have to flash it with a firmware. I tried updating firmware using sd card through revovery mode, update was finished but it did not worked), I tried found a (I think is) a raw firmware, flashed it by clicking the command inside the zip file, it was finished but it was phone is still stuck in bootloop. Lastly I flashed a raw firmware using Asus Flash Tool (AFT does not support stock rom from official site), the flashing was also a success but the phone is still in bootloop.
And there are times that when the phone is plugged in it opens but it always restarts into bootloop after a few minutes or when unplugged
Please help I don't have a phone to use right now and I don't have money to let a repair shop fix it.
Thank you!
hi.
i think I'm facing the same problem.
have you found a solution yet?
musooo said:
hi.
i think I'm facing the same problem.
have you found a solution yet?
Click to expand...
Click to collapse
not yet, but someone in the other forum said it might be the battery problem. I hope not.
I really suspect that to be a faulty battery issue. Let me help you with this. Once I hard bricked my ZE550kl (3 GB) by erasing aboot partition but thereafter I successfully recovered my device and installed AEX 6.7 custom rom. Some days later my device started rebooting itself and ended up in a state where it can't load beyond the boot animation. At first I thought it might be a software related issue hence I rolled back to the stock firmware. But unfortunately the problem persisted. Then I realized my battery is causing the issue and replaced old one with a new battery. My device finally booted up and once again fully functioning. So I suggest you to give it a try. Batteries wear out over time and may drop voltage suddenly from the requisite level and may cause restarting. One more thing to be cautious about is the replacement battery itself. Most of the third party battery for this device available in the market won't charge beyond 92% and may cause device shut down even before reaching 0% ( say at 30% ). So, please try to buy from a legit source or shop that you are familiar with.