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??
Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
tank0412 said:
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
Click to expand...
Click to collapse
Yup. Tried all this.
Just format again and re flash rom with xposed it fixed my bootloop.
The solution is,
Go back to stock rom. ???
Can anyone tell me how to back stock ROM from resurrection remix???
yasin0005 said:
Can anyone tell me how to back stock ROM from resurrection remix???
Click to expand...
Click to collapse
Download latest firmware from Asus' Support Page. And flash it via adb sideload.
I m now on Stock Rom without any problems no screen freeze no bootloops ...
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
I accidentally posted in Android development. so sorry
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
fatboyinlycra said:
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Click to expand...
Click to collapse
I'm in a doubt about the battery, I think it's slightly swollen.
I guess I'll give it a try.
shaggyskunk said:
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
Click to expand...
Click to collapse
First thing I did.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
dineshh said:
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
Click to expand...
Click to collapse
Battery issue, solved with replacement
jetbruceli said:
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
Click to expand...
Click to collapse
Solved with battery replacement
huge thanx
First of all I'm not a very techy girl so please give me step by step instructions to recover my Yureka (Phone Details are given below). Few days ago (as usual) I restarted my phone and suddenly noticed a weird thing, It was stuck at YU-bootscreen/Logo for many minutes but suddenly started getting booted but I ignored it. I never knew it's going to be a big mess soon. After few days I again rebooted my phone but this time it refused to boot, the same situation. It was stuck at YU Logo. I waited for a long time but no gain. Screen was constantly on and it was literally scaring me. finally I ejected/removed the battery forcefully and reinserted it and restarted the phone and again after getting stuck at YU Logo/bootscreen for a while it got booted and it was a relief of sign. Here comes the main problem. Again after few days Yureka started hanging as usual and I again rebooted it but this time it was dead-end for me. It's again stuck at YU Logo Screen. I tried restarting/removing the battery many times but no luck. It's stuck at the screen forever. I am trying/restarting/reinserting-the-battery again and again but seems it's stuck forever at the bootscreen. It's been few days but no luck. I am totally frustrated and don't know what to do! I have important data in the phone especially App Data like Hike/WhatsApp and some GamesData/SMSes/Contacts etc. Please guys help me. How to revive my Yureka without damaging the precious data?
Things I tried to solve the problem:
1) I removed the battery many times. I did reboots many times.
2) I tried "Wipe cache partition" option in the recovery menu (Power+Volume Up+Volume Down) multiple times. But no gain.
What could be the reason of this problem? Is this faulty internal memory? Because my phone is behaving weird since the day I purchased it. Random App crashes happen multiple times regularly. This service stopped that service stopped blah blah. It's so annoying and counter-productive. It Started hanging and lagging a lot too. And finally bricked. I think this bricking problem only happens when you fiddle with your OS or try to root or install any unsupported custom ROM, But I am on stock ROM then why did it happen with me? Hardware defect? Did I get a faulty phone? I always ignored App crashes/Google services crashed /Random auto-reboots because I though Cyanogen OS is prone to bugs. But this is insanely odd! So many bugs are too much. Stock ROM has to be stable. I think YU gave me a faulty device! Please help me. What to do now to turn on my device without losing the data? I didn't try the Wipe data/factory reset OR Wipe media because it will remove all of my data which is very important to me.
P.S. Please note that my phone is stuck at YU Logo (NON-Animated logo) NOT on Cyanogen Logo.
One Another Indication of the problem:
When I tried to charge my phone by turning it off completely and then connected the charger with it the same YU logo came up and screen never went blank/off (screen with YU logo was constantly ON) and the Red LED light (charging indicator) didn't turn on, It means I can't even charge my battery because I think it's not getting charged cuz it's stuck on the same screen and never shows battery indicator while soft-pressing power button curiously just to check I removed the battery and tried connecting the charger without battery in the phone and the Red LED turned on normally.
Phone Details:
Phone Model: simple YU Yureka A05510 (NOT YU Yureka plus)
Cyanogen 11.0-XNPH05Q (Android KitKat 4.4.4) (NEVER updated Yureka)
NEVER rooted
Stock Cyanogen ROM
Stock Cyanogen Recovery
Are you sure it's still on KitKat?
Please confirm once again then I'll give you flashing guide.
saurav007 said:
Are you sure it's still on KitKat?
Please confirm once again then I'll give you flashing guide.
Click to expand...
Click to collapse
Yes it's KitKat 4.4.4
Download CM11 fastboot.zip and follow the flashing instructions from here.
This will erase everything from your device. If you don't want to lose data then download CM11 signed zip and flash it manually from stock recovery.
saurav007 said:
Download CM11 fastboot.zip and follow the flashing instructions from here.
This will erase everything from your device. If you don't want to lose data then download CM11 signed zip and flash it manually from stock recovery.
Click to expand...
Click to collapse
Hi! When the problem occurred I was thinking about the same solution, I mean flashing the ROM by putting it on a SD card. But I've two confusions on my mind
1. Should I directly flash CM 11.0 (the same ROM which I have currently) or the upgraded CM 12.0 (Lollipop)? I am confused
2. When this catastrophe happened, free space on internal memory was very low (I don't remember exactly but may be 100MB or 200MB or 300MB but very low). Will the ROM flashing process complete successfully?
Sarika CoolGirl said:
Hi! When the problem occurred I was thinking about the same solution, I mean flashing the ROM by putting it on a SD card. But I've two confusions on my mind
1. Should I directly flash CM 11.0 (the same ROM which I have currently) or the upgraded CM 12.0 (Lollipop)? I am confused
2. When this catastrophe happened, free space on internal memory was very low (I don't remember exactly but may be 100MB or 200MB or 300MB but very low). Will the ROM flashing process complete successfully?
Click to expand...
Click to collapse
1. COS12.1 Signed zip can be used to flash directly over COS11, but since there is lots of things happening in your phone, I'd suggest you to flash COS11 first.
2. 300MB is very low. Use external SD card because the size of signed zip is 500 MB.
Solution
Guyss plz plzz help me out, even my yureka has started behaving like this, im really fed up i tried many things but no use i tried the following things
1.installed stock rom using fastboot
2.flashed cm11 signed zip using recovery
3.clearing cache in storage
4.wiping dalvik and normal cache
Currently now i am using cm11 signed zip version