Database Users

[Q] Nexus 4 boots with 4.2.2 (JDQ39 but no radio) but no new ROM, including stock

I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????

contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
doing a system wipe (factory reset) when you update from 4.2 tp 4.3..? also just reminding you 4.3 based roms need new radio and bootloader update.. but that radio also works with 4.2..

Same problem
contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4

Antonio0 said:
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4
Click to expand...
Click to collapse
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?

i dont think i have a solution
smoka206 said:
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?
Click to expand...
Click to collapse
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device

Antonio0 said:
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device
Click to expand...
Click to collapse
i have the same problem too.. can someone help please??

try this http://forum.xda-developers.com/showthread.php?t=2347060
http://forum.xda-developers.com/showthread.php?t=2453364

Nexus 4 TWRP encryption with password - I think the phone is gone

So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.

Bump

Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4

eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.

This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app

It's happening to me now too
Sent using T-Mobile S4 4.3 MK2

LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?

I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2

[Q] D803 Phone freezes then reboots every few minutes

What's currently happening is my phone will boot and work normally except it appears the radio is not working then after 60-120 seconds freeze for a second then reboot. Wifi does work but I just see an x for the cell network signal and if I take out the SIM I get no notification. Curiously if I'm using the camera it seems to delay the rebooting by a few minutes.
I've tried http://forum.xda-developers.com/showthread.php?t=2432476 LG G2 Stock Firmware (Go Back to Stock) to no success, I was able to flash, it removed TWRP but I get the same symptoms anyway.
I've tried flashing the Rogers modem and this did not make a difference.
When I noticed this problem was when I was installing/testing some xposed modules, although it seems strange that they could break the phone in this way.
I've run out of ideas and although my phone isn't bricked per say it's near useless if it's going to reboot every minute or two. The phone doesn't reboot if I leave it in download mode or TWRP so this makes me think there's some hope.
Assuming it's not against the rules I'll PayPal anyone who comes up with the fix $50 CAD because right now I'm hooped.

Did you download and try flashing the exposed disabler zip file?
Sent from my LG-D803 using XDA Premium 4 mobile app

Of course there is hope!
All you gotta do is just download this ROM...
http://forum.xda-developers.com/showthread.php?t=2451592
Download it with your PC, then connect your phone to the PC to transfer the file.
The TWRP and flash it and that should fix it all.
Good luck

Do you have a gmail widget on your lockscreen? (Was worth a shot since others have reported varying issues with gmail widgets on the lockscreen).

I lost my recovery when I tried to go back to stock, and I can't seem to install any apps. I'm trying "upgrade recovery" from the LG Mobile Support Tool to see if that works. Otherwise I guess I have to find out how to root and flash a recovery entirely over ADB

I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.

mrsocksfox said:
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
Click to expand...
Click to collapse
If flashing to stock didn't work then your phone may as well be defective...

crzykiller said:
If flashing to stock didn't work then your phone may as well be defective...
Click to expand...
Click to collapse
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.

EFS. Flash or push your backed up EFS.

Steamer86 said:
EFS. Flash or push your backed up EFS.
Click to expand...
Click to collapse
I don't have one. I made a backup in TWRP but ended up losing it when trying to fix things :silly:. I believe I can still see my IMEI if that's any sign of things not being completely ****ed.

Hi I have LG G2 D802 . My problem is that my phone hangs a lot . I did hard reset but problem didnt go. After hard reset i tried to install custom built rom but still same problem. Then I re installed lolipop 5.0.2 still the same problem .. now
i have downgraded to kitkat and again same problem .. Even now when it hangs It turn off completely like it got bricked or something but it work some time and again after some use it hang.. now i have hardreset my device and putted on standby mood but phone was working fine after some use phone hanged again . I dont understand what is the problem with my LG G2

I am having the exact same problem on stock 4.4.2 with my D803. I have random reboots every few minutes. I suspect it is a hardware issue since the problem persisted even after returning to stock using kdz. Unfortunately, I don't have an EFS backup.
I have tried multiple other ROMS (CM12.1, DU, Cloudy 3.2 and 3.3) and all are even less usable than stock (reboots while I am doing the initial setup).
Any suggestions? I don't know what else to try and am ready to buy a new phone now as this G2 is basically unusable... I'd greatly appreciate any help.

mrsocksfox said:
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
Click to expand...
Click to collapse
If you have restored it to stock ....... and you still have the problem, u may have a short somewhere in the phone. The only thing that remains the same is the hardware .... u have changed the software

Phone Semi-BrickeD?

Main:
Ok, so I was waiting until i got a new phone so i can root my g2, well never happened as my g2 decided to randomly freeze up and restart and get stuck in boot loops either on the LG logo, or freeze on the T-mobile splashscreen and restart infinately. So now i got a new phone and i want to root the old one, But first up I need to figure out what is causing the random boot loops, freezing, and shut offs. It's a T-Mobile variant
ALSO: IT WAS NEVER ROOTED, So it's not a root related issue.
NOTES:
plugging it in help increase chances of escaping loop
It doesn't require a plug in to fix but it helps.
Reboot/Glitching occur when phone is in use and out of use.
Phone works normally otherwise but suffers these glitches
Phone has be factory reset twice
Phone has no external damage
Possible Internal:
Broken L. speaker due to rain
Maybe water damage from steam (phone was on counter as i showered a few times)
possible battery issue
Maybe a bit of drop damage as i did drop it a bit, but it was in a tech21 impactology case, and it remains not cracked

I have a similar issue. The phone will loop the LG logo, but only sometimes--at other times it will poop android's boot animation until it decides it wants to boot normally.
It happens in every ROM(ota or cuatom) even after flashing the stock .tot file about 4 times, so it's clearly a hardware defect for me & probably you too. I read the logs & saw rtc blah blah time will be lost on reboot & other errors. During normal use it randomly freezes prior to rebooting itself, though it reboots even while idle for long periods.
Unfortunately I don't have a solution for your problem besides restoring the stock image.
http://forum.xda-developers.com/showthread.php?t=2432476
After that you can trade the phone in, sell it, or send it to LG.
Powered By "Yeeart!"

So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops

pvt900 said:
So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops
Click to expand...
Click to collapse
It fixed my problem temporarily, but not too long afterwards all the issues came crawling back. For this reason I suggested ditching the phone completely unless you really want LG to examine it.
Powered By "Yeeart!"

Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff

pvt900 said:
Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff
Click to expand...
Click to collapse
I've heard of the random reboot issue. Fixes have been created and detailed. Please give me the following info, and I can help you resolve the problem:
Current Baseband Version
Current Bootstack / Modem
Root status in recovery
Current ROM and Carrier
Current Recovery

I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?

jkeats20 said:
I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?
Click to expand...
Click to collapse
What I had in mind is a multi-step solution that didn't involve opening the device - we can try it, and if it doesn't work then I guess you should try it. I've never actually heard of the pin-shorting, can you post links to the threads?
Anyways, this is roughly what we can try (I can give you all the files you need if you give the info from my first post):
1. Get to fastboot
2. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things
3. Reboot to download mode
4. Reinstall the kitkat TOT
5. Install custom recovery and wipe all partitions
6. Kitkat TOT again
7. Factory reset (yes, even though this is a fresh install)
8. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things AGAIN
I've tried these steps before on a friend's VS980 and they seemed to fix the problem. I know that this seems overly complex, but it has been documented in other threads. Provide the info, I'll get the files, and let's get started.

I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

jkeats20 said:
I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.

dmezh said:
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.
Click to expand...
Click to collapse
Did you have a chance to try this out? It sounds like a good way to get the phone into fastboot but am reluctant to try without knowing if it's going to work. Thanks for your suggestions so far - and no rush on getting back I have a working backup phone at the moment.

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