Related
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??
Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric
Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric
Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric
I have a I9505 and it was working fine (samsung ROM), when I decided to 'encrypt' my device! It was fully charged and connected to a charger.
After starting, it stayed connected for 5-6 hours, but nothing was seemingly happening.. After 6 hours I switched it off. Then back on again.
The device after starting (just the system) didnt let me do anything else, and told me that since encryption failed, I need to format the device. So I restarted, formatted. Still same msg
Wiped the device completely. Still same issue. Tried changing file system from ext4 to ext2.. still same problem! I installed a couple of roms, they seemingly installed ok, but after starting, the same msg!
Please help me!
My bootloader is TWRP by teammate I think
Did you attempt to flash the stock ROM via Odin?
find a place that can do a JTAG
I had this issue last week.
1. Flash Stock rom with Odin
2. Boot into stock recovery (Must be stock)
3. Choose factory reset
Fixed.
SOLVED
Thank you guys! Flashing with ODIN worked fine! Not sure why I didnt think of that earlier!!
hdaackda said:
I have a I9505 and it was working fine (samsung ROM), when I decided to 'encrypt' my device! It was fully charged and connected to a charger.
After starting, it stayed connected for 5-6 hours, but nothing was seemingly happening.. After 6 hours I switched it off. Then back on again.
The device after starting (just the system) didnt let me do anything else, and told me that since encryption failed, I need to format the device. So I restarted, formatted. Still same msg
Wiped the device completely. Still same issue. Tried changing file system from ext4 to ext2.. still same problem! I installed a couple of roms, they seemingly installed ok, but after starting, the same msg!
Please help me!
My bootloader is TWRP by teammate I think
Click to expand...
Click to collapse
Dude did you try to use an aosp rom
Hi everybody.
Dis morning I woke up and I realized that my phone was gone. I used AOSP Extendend ROM when it happens. At first, the rom completely froze. I thought it was a bug, so I rebooted the phone, but after did dis, the phone kept on rebooting and froze on first screen and I couldn't do anything. Touch didn't respond, nothing worked.
So I tried to go on recovety, but nothing.
At the end, I gave up about take back my data and try to install the stock ROM through MiFlash. I tried different stock ROM, but at the first they works, but during the installation guide they froze again and reboot. I can't even finish the setup!
So I tried again, unlock bootloader, flash TWRP, but still there:
- only TWRP v2.0 works, other versions won't start
- even with TWRP v2.0, after did wipe everything and format, when I tried to install a custom ROM, even TWRP froze and reboot the phone
- TWRP is pretty useless, it keeps on froze and when I boot recovery again, TWRP is locked and I have to format everything again, but still don't work.
Someone could tell me what happened to my phone? Any suggestions about what I could to to install something on my phone?
Pls help me, I am completely lost and disperate
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
cobben said:
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
Click to expand...
Click to collapse
Ok, I will listen your tip. Yeah, I have tried everything but nothing. Technically, I bought this phone last december, so it's still covered by warranty, but I have to send it to China, I would avoid that if I can.
I hoped there would be something that I didn't but...nothing.
Thanks anyway dude
Hi,
A few days ago I unlocked my bootloader and tried to install a ROM on my phone, more specifically the latest version of Bootleggers, to my surprise it didn't work and now I have a serious problem, because of my lack of patience(I didn't wait for health to get better to buy a bigger memory card, mine is only 2gbs sad life), I didn't back up my phone (nooby and stupid, sry guys), and now my phone doesn't want to boot into any OS I put on it (even the original one), I've tried pretty much everything (I know off), do mind that i only have 2 days of experience so I don't know that much. If anybody knows anything that might change my phone for the better I would appreciate the help.
Stuff that happened
I think I might have deleted something I should't have when trying to install Bootleggers for the first time.
I have successfully installed a OS ones, Havoc OS 2.9 (through ADB though), but I didn't like the interface so I deleted it and tried others, Resurrection Remix and ASOP, none of them worked so I tried flashing Havoc through ADB again, but this time it failed, it stopped in the middle of booting like all the other ones.
I can get into Recovery, eRecovery and Fastboot mode.
I don't have ROOT (Magisk) on it (at least I think), I installed it ones, but my OS didn't load so I tried deleting it afterwards and I got a error in the terminal probably because I didn't have it installed.
I still don't have a bigger SD card, I'm gone buy it tomorrow tho.
Info
Phone - Huawei P10 Lite
Model - LX1A
Firmware - WAS-LX1 8.0.0.368(C432)
Software (Mentioned in the quick start guide that came in the box) - WAS-LX1AC900B049
TWRP - 3.3.1 (also 3.2.1 but only for the MTP function(sometimes it gives me a black screen after opening it))
Problem - Phones starts booting the OS I put on it, but then stops and returns or to Recovery or eRecovery.
I dont know what more info to put here, like I said earlier nooby (and pls dont hack me if ive put the wrong info online, thx).
AlphaReigN said:
Hi,
A few days ago I unlocked my bootloader and tried to install a ROM on my phone, more specifically the latest version of Bootleggers, to my surprise it didn't work and now I have a serious problem, because of my lack of patience(I didn't wait for health to get better to buy a bigger memory card, mine is only 2gbs sad life), I didn't back up my phone (nooby and stupid, sry guys), and now my phone doesn't want to boot into any OS I put on it (even the original one), I've tried pretty much everything (I know off), do mind that i only have 2 days of experience so I don't know that much. If anybody knows anything that might change my phone for the better I would appreciate the help.
Stuff that happened
I think I might have deleted something I should't have when trying to install Bootleggers for the first time.
I have successfully installed a OS ones, Havoc OS 2.9 (through ADB though), but I didn't like the interface so I deleted it and tried others, Resurrection Remix and ASOP, none of them worked so I tried flashing Havoc through ADB again, but this time it failed, it stopped in the middle of booting like all the other ones.
I can get into Recovery, eRecovery and Fastboot mode.
I don't have ROOT (Magisk) on it (at least I think), I installed it ones, but my OS didn't load so I tried deleting it afterwards and I got a error in the terminal probably because I didn't have it installed.
I still don't have a bigger SD card, I'm gone buy it tomorrow tho.
Info
Phone - Huawei P10 Lite
Model - LX1A
Firmware - WAS-LX1 8.0.0.368(C432)
Software (Mentioned in the quick start guide that came in the box) - WAS-LX1AC900B049
TWRP - 3.3.1 (also 3.2.1 but only for the MTP function(sometimes it gives me a black screen after opening it))
Problem - Phones starts booting the OS I put on it, but then stops and returns or to Recovery or eRecovery.
I dont know what more info to put here, like I said earlier nooby (and pls dont hack me if ive put the wrong info online, thx).
Click to expand...
Click to collapse
Hi,
have you tried to enter into eRecovery and click download and flash and then tried it?