Database Users

[Q] Phone "stuck" on Motorola Logo

I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...

Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.

Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.

Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.

Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095

Phone bricked after Orange UK Gingerbread OTA update?

Hi,
Ive already looked around the forum but cannot find an answer to my question.
I know my phone is not totally bricked, I understand there are probably ways of plugging it into a PC to force an update but i downloaded the OTA update that popped up on my phone last night. As I understand it is meant to update and keep all of your apps and saved data, which I chose to do instead of wiping anything with a manual update to save all the hassle.
The phone was rooted on froyo 2.2.2 orange uk rom but apart from that there were no other mods to the OS.
The phone came up with the "power off" message and now sticks on the black Motorola screen showing
"Failed to boot 2
starting rsd mode"
I can pull the battery out and the phone turns on for about 20 seconds, and I can use the OS in this time but then the "powering off" message comes back up
and it goes back to the error message on the splash screen.
Is there a way I can stop this OTA update from powering off my phone and getting stuck in this loop or do i have to wipe the phone and flash an sbf file?
Can you point me to the sbf file for the new orange gingerbread rom?
Thanks
ryan

Anyone?
When i turn phone on it works for about 20-30 seconds, before it restarts into the splash screen. It seems as if the phone is running some sort of script to continue with the upgrade but when it reboots it cant continue or something...
The OTA update didnt even start flashing, it just downloaded, then i clicked "install now" and it just rebooted to the error.
If i cant fix it easily, can I use RSDLite and an SBF file to go back to stock? Or can you only do this on an unlocked bootloader?
My bootloader is still stock. The only thing I did when I got the phone was root it so that I could install certain apps.
PLEASE HELP!

Link to Orange UK GB SBF is in Atrix 4G Android Dev forum in the Atrix Firmwares Superthread..page 25ish.
I RSDLited this SBF onto my Atrix (unlocked bootloader running Alien #4) with no problems.
This same route may be your only option...not sure about recovery of your apps etc..I have everything backed up via Blur, Google account and Titanium Pro, so no concern for me there.
FYI, this new rom seems to have little Orange bloat and runs great for me in stock form...just rooted...and battery life is very respectable.

[q] stuck in bootloop sprint ls980 please help!!!!

OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER

Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.

G1_enthusiast said:
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
Click to expand...
Click to collapse
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.

Sshaffer1992 said:
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Click to expand...
Click to collapse
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.

Solution?
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.

androidfantic32 said:
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
Click to expand...
Click to collapse
I tried the lg flash tool and it put my phone back to stock but still have the same problem. I also tried lg mobile support tool but it will not recongize my phone. I did happen to get into settings and seen that both my imei and baseband are unknown. Could this be causeing the proble m? is there any way to fix it?

G1_enthusiast said:
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Click to expand...
Click to collapse
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.

Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.

G1_enthusiast said:
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
Click to expand...
Click to collapse
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw

Sshaffer1992 said:
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Click to expand...
Click to collapse
they have coders there, I'm sure if they really want to know they can figure it out. If you send it in to get it fix out of your own pockets (meaning you pay them) then i'm sure they dont care, but if you want a replacement due to warranty then it may be a different story.

Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol

Nba2kgod said:
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Click to expand...
Click to collapse
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.

Sshaffer1992 said:
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Click to expand...
Click to collapse
Not under warranty? Doesn't it have a 1 year manufacturer warranty? The G2 wasn't released on Sprint until November last year so it should have been covered.
Sent from my LG-LS980 using Tapatalk

Yes its still under manufacturer warranty but when i made a repair order with lg it said it would take 2 to 3 weeks to get my phone back and if they found out it was due to being rooted and flashing roms im sure lg would of charged a arm a leg to repair it. With sprint i got a new phone in 2 days or ordering it.

Phone will not shut off all the way

Had my phone for a couple days and decided to root, safestrap, and flash alliance rom. Everything works great when the phone is running but I am running into an issue when I need to reboot or shut the phone down. If I use the power menu to shut down or reboot the phone screen will turn black like normal. The notification light and recent/back buttons light up like they normally do when the phone is shutting down but it just stays like that, no vibrate no sounds, Ive let it sit for 5+ min and it still stays like this. Any help would be appreciated.

shackwrrr said:
Had my phone for a couple days and decided to root, safestrap, and flash alliance rom. Everything works great when the phone is running but I am running into an issue when I need to reboot or shut the phone down. If I use the power menu to shut down or reboot the phone screen will turn black like normal. The notification light and recent/back buttons light up like they normally do when the phone is shutting down but it just stays like that, no vibrate no sounds, Ive let it sit for 5+ min and it still stays like this. Any help would be appreciated.
Click to expand...
Click to collapse
There are known issues with Safestrap... Without even asking, I will venture to say you have created a rom slot and that is where you have Alliance installed.... I found out the hard way too instead of researching what I was doing before installing it. You have to install it on the STOCK slot only and not a rom slot and you will be golden. Odin back to original (drop 5 yards and punt) and go back through the whole process but install on stock slot.

3 finger salute by hard resetting could get you out of the funk.

Thanks for the help, I tried wiping the cache partition, no help. I was on the fence about flashing to the stock slot. I wonder if I can safely restore my backup to the stock slot after wiping the slot1 without bringing the issue with it.
Sent from my SM-G900V using Tapatalk

Just deleted my rom slot, wiped the stock slot, installed a fresh copy of alliance and all is great. Everything even runs smoother. Google app and settings restore worked like it should and didn't even have to use titanium.
Sent from my SM-G900V using Tapatalk

Nexus 4 turning off when unplugged from charger

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??