Database Users

I think I'm bricked?

I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.

You fool.

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium

Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312

overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.

I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2

ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7

Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up

KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.

So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7

abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.

Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before

First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.

So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?

Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it

Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.

abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way

dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?

[Q] Please help!! Nexus 4 died

My nexus 4 died. Can not boot. No respond but only red flash when plugged in with charger. I already unlocked my phone.
any one can help me?

huangkaiwisdom said:
My nexus 4 died. Can not boot. No respond but only red flash when plugged in with charger. I already unlocked my phone.
any one can help me?
Click to expand...
Click to collapse
Thats the RED light of death. Its a battery problem. Some people have opened their phones and fixed it somehow. I suggest you get a RMA.

Addsome said:
Thats the RED light of death. Its a battery problem. Some people have opened their phones and fixed it somehow. I suggest you get a RMA.
Click to expand...
Click to collapse
Since I already unlocked my phone and flash recovery. Do I still under the warranty?

huangkaiwisdom said:
Since I already unlocked my phone and flash recovery. Do I still under the warranty?
Click to expand...
Click to collapse
Im not 100% sure but since what you did, did not cause the RED led they should fix it. Unless something you did made that happen. When did this happen and how?

Put it on charge overnight. It should boot into recovery.

Addsome said:
Thats the RED light of death. Its a battery problem. Some people have opened their phones and fixed it somehow. I suggest you get a RMA.
Click to expand...
Click to collapse
Addsome said:
Im not 100% sure but since what you did, did not cause the RED led they should fix it. Unless something you did made that happen. When did this happen and how?
Click to expand...
Click to collapse
When I was trying to root my phone, when It on Recovery mod, I left for a while, when I came back, the phone was very hot, and powered off. No response when hit the power button.

calyxim said:
Put it on charge overnight. It should boot into recovery.
Click to expand...
Click to collapse
I tried. Keep in charge overnight. But still only Reg flash light.

huangkaiwisdom said:
When I was trying to root my phone, when It on Recovery mod, I left for a while, when I came back, the phone was very hot, and powered off. No response when hit the power button.
Click to expand...
Click to collapse
Hmm, you might of done something wrong.. Why would you leave it while it was rooting? I dont know what to do. Maybe you did something to the battery. Since you say it was very hot the battery might of overheated and died. Was it hot throughout the phone? Or just the top section. You could always but a battery and replace it yourself.

Addsome said:
Hmm, you might of done something wrong.. Why would you leave it while it was rooting? I dont know what to do. Maybe you did something to the battery. Since you say it was very hot the battery might of overheated and died. Was it hot throughout the phone? Or just the top section. You could always but a battery and replace it yourself.
Click to expand...
Click to collapse
It's just the top section. Maybe I did something wrong. The phone showed the battery logo for one second. But back to Red light then.

Charge it the whole night with another charger, not stock

calanizzle said:
Charge it the whole night with another charger, not stock
Click to expand...
Click to collapse
I will try that. Thanks

I believe some have fixed thier problem by pressing down where the battery connects to phone

Plug it into a USB slot on your computer and repeatedly try and get into recovery. Worked for me when I got the red light. When you do get into recovery leave it there a while to charge.
Sent from my Nexus 4 using Tapatalk 2

Is there any way of avoiding this red light of death issue. I am worried that it will happen on my Nexus

droidmakespwn said:
Plug it into a USB slot on your computer and repeatedly try and get into recovery. Worked for me when I got the red light. When you do get into recovery leave it there a while to charge.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
When plug into USB and connect to computer, it show the battery charge logo for seconds and back to red flash light. And I press volume up + power button, no flash but still Red light. nothing happened.

huangkaiwisdom said:
When plug into USB and connect to computer, it show the battery charge logo for seconds and back to red flash light. And I press volume up + power button, no flash but still Red light. nothing happened.
Click to expand...
Click to collapse
If you have adb access, boot to recovery there.
Sent from my Nexus 4 using Tapatalk 2

droidmakespwn said:
Plug it into a USB slot on your computer and repeatedly try and get into recovery. Worked for me when I got the red light. When you do get into recovery leave it there a while to charge.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I got red light of death and believe me I understand how it feels.
Good news: You can come out of it
1. Plug into wall charger for 1 hour or so. Make sure the wall charger has has at least 5V and 0.7 A, lower than that can not make sufficient charge.
2. After one hour of charging, the red light should go off (It's ok even if its RED light is glowing)
3. take out the charger and press power + Vol Down
4. Holding above two buttons, insert your charging USB to phone
5. The red light should blink and after a while you should be in boot loader.
5.1. If it doesn't do it again (Holding above two buttons, insert your charging USB to phone)
5.2. If you are not getting it after say 15-20 tries, leave it for charge for some more time and then try
6. Once you are in boot loader screen, don't let the screen turn-off, that is every 20-30 secs keep pressing vol button.
7. After 2 mins, chose reboot option and your phone should reboot, you can see zero battery
Bad News: Even though you will come out of RED Light of Death, the battery will become very weak (Very!!) and if again it turns off due to low battery it will go to RED Light of Death again.
If you have warranty and you are rooted, flash Google Firmware when you are in fastboot and claim your Warranty.
Sadly, I am in Singapore and using US set, so I can't do that.
Let me know if it helped.

Red Notification light. Phone won't boot up

I ran antutu benchmark and the phone automatically rebooted. I ran it again, and got forced closed. Now It won't boot up. On charging it, the charging symbol appears followed by the red notification led. On booting while charging, I can go uptill the google screen but not further or bootloader mode. Please help!
It is rooted with cwm and faux kernel and Dalvik and Bionic optimized libs

Ibrahim.Rahman said:
I ran antutu benchmark and the phone automatically rebooted. I ran it again, and got forced closed. Now It won't boot up. On charging it, the charging symbol appears followed by the red notification led. On booting while charging, I can go uptill the google screen but not further or bootloader mode. Please help!
It is rooted with cwm and faux kernel and Dalvik and Bionic optimized libs
Click to expand...
Click to collapse
In all honesty, you were probably right there, but you just didn't let it charge enough. I had a rlod the other day, I must've done it good this time because I had to let it charge for almost an hour before it would power back up. I can't remember though, if it actually chargers when the red light is lit, or if you need to unplug it and plug it back in so that it's plugged in with no red light, no power on, or anything. Let it charge while of with the red light on for about 20 mins. Then fiddle with it, unplugging and plugging back in, until you can get it to stay plugged in without powering it up or the red light coming on. Let it charge for about 20 mins like this too. Unplug it. Turn it on. Plug it back in immediately after seeing the google logo, let it finish booting and finish charging and you should be good. I've had around 5 - 7 rlod (mostly all my fault) and this method has worked every single time. I've never opened or rma'd my phone.

username8611 said:
In all honesty, you were probably right there, but you just didn't let it charge enough. I had a rlod the other day, I must've done it good this time because I had to let it charge for almost an hour before it would power back up. I can't remember though, if it actually chargers when the red light is lit, or if you need to unplug it and plug it back in so that it's plugged in with no red light, no power on, or anything. Let it charge while of with the red light on for about 20 mins. Then fiddle with it, unplugging and plugging back in, until you can get it to stay plugged in without powering it up or the red light coming on. Let it charge for about 20 mins like this too. Unplug it. Turn it on. Plug it back in immediately after seeing the google logo, let it finish booting and finish charging and you should be good. I've had around 5 - 7 rlod (mostly all my fault) and this method has worked every single time. I've never opened or rma'd my phone.
Click to expand...
Click to collapse
I'll try this tomorrow as it's 1 30 am here and I have a test tomorrow. Let's hope it works..
Btw I should mention, when I connected it to my pc, i got 'installing device driver' message with 'unidentified device' I mean is the phone already on? (although fastboot devices or adb devices doesn't show anything)
Thanks!

Sheep.... If its instaling drivrr on rlod then 49% of your phone being stuck at QHUSB_DLOAD mode. Good luck
Sent from my Nexus 4 using xda app-developers app

opssemnik said:
Sheep.... If its instaling drivrr on rlod then 49% of your phone being stuck at QHUSB_DLOAD mode. Good luck
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What's QHUSB_DLOAD mode?

If the phone is completely powered off, your computer shouldn't even know when you plug it in, it shouldn't pop up with any messages at all. What your getting sounds a bit like the message people get when their phone is hard bricked, except reading from your first post, you havent done anything at all to even get close to a hard brick. Try holding your power button for 30 seconds. A real 30 seconds, count it out. When I turn my phone back on from the rlod (after doing all my rlod steps in the previous post), sometimes I have to hold the power button for a god awful long time, it has to be close to a full minute. Your phone might be frozen on some lower level (locked up bootloader maybe?) and might require holding the power button that long as well.

username8611 said:
If the phone is completely powered off, your computer shouldn't even know when you plug it in, it shouldn't pop up with any messages at all. What your getting sounds a bit like the message people get when their phone is hard bricked, except reading from your first post, you havent done anything at all to even get close to a hard brick. Try holding your power button for 30 seconds. A real 30 seconds, count it out. When I turn my phone back on from the rlod (after doing all my rlod steps in the previous post), sometimes I have to hold the power button for a god awful long time, it has to be close to a full minute. Your phone might be frozen on some lower level (locked up bootloader maybe?) and might require holding the power button that long as well.
Click to expand...
Click to collapse
Thanks! I'll do it tomorrow and inform you about any progress..
Goddnight...

Its Mike Download mode for Samsung devices.its trigered by the 2nd bootloader when the 1st onde fails to boot.when on this mode.the nand turns into a pendrive(like) and can be all reformated(re send partition table).but we dont have all the files to do that.
Sent from my Nexus 4 using xda app-developers app

Btw, would leaving it charging for about 5 hours cause any further damage? I mean is it advisable to do so?

opssemnik said:
Its Mike Download mode for Samsung devices.its trigered by the 2nd bootloader when the 1st onde fails to boot.when on this mode.the nand turns into a pendrive(like) and can be all reformated(re send partition table).but we dont have all the files to do that.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Right..

As long is stock charger its ok
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
U can try pressing vol up and down for 1min.then pluging in the charger
Sent from my Nexus 4 using xda app-developers app

username8611 said:
If the phone is completely powered off, your computer shouldn't even know when you plug it in, it shouldn't pop up with any messages at all. What your getting sounds a bit like the message people get when their phone is hard bricked, except reading from your first post, you havent done anything at all to even get close to a hard brick. Try holding your power button for 30 seconds. A real 30 seconds, count it out. When I turn my phone back on from the rlod (after doing all my rlod steps in the previous post), sometimes I have to hold the power button for a god awful long time, it has to be close to a full minute. Your phone might be frozen on some lower level (locked up bootloader maybe?) and might require holding the power button that long as well.
Click to expand...
Click to collapse
So I couldn't sleep. Out of nowhere, idk how I am now in bootloader mode. Should I restart of power off or what?

Ibrahim.Rahman said:
So I couldn't sleep. Out of nowhere, idk how I am now in bootloader mode. Should I restart of power off or what?
Click to expand...
Click to collapse
Wish I had a four letter response. Was this after letting the phone charge? I would power off and let it charge until you wake up. (four letter word was in reference to QLOD and RLOD like the average layperson would know what that means! )
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
Wish I had a four letter response. Was this after letting the phone charge? I would power off and let it charge until you wake up. (four letter word was in reference to QLOD and RLOD like the average layperson would know what that means! )
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
While charging. After selecting power off/Start up/recovery mode/restart bootloader, it again starts getting rlod. it shuts down as soon as I disconnect the cable,

Ibrahim.Rahman said:
While charging. After powering off, it again starts getting rlod. it shuts down as soon as I disconnect the cable,
Click to expand...
Click to collapse
How long did you charge it?
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
How long did you charge it?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Its somewhere between one and a half hour to 2 hours

Ibrahim.Rahman said:
Its somewhere between one and a half hour to 2 hours
Click to expand...
Click to collapse
I'm thinking a hw or battery issue. It's strange (duh) that after that length of time that it would shutdown after disconnecting the cable.
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
I'm thinking a hw or battery issue. It's strange (duh) that after that length of time that it would shutdown after disconnecting the cable.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I hope I don't have to open it up. Its nearly 3 here so im leaving it charging and will remove it in three hours. Will get back later.
Thanks!

So nothing worked.. I guess the only way left is to open the phone up.. Wanted to avoid doing that at all costs :/

Ibrahim.Rahman said:
So nothing worked.. I guess the only way left is to open the phone up.. Wanted to avoid doing that at all costs :/
Click to expand...
Click to collapse
Well i have been writing about this. In short you have to disconect the battery, and try to boot it again.fist try to hold the volume down when conecting the charger, it will restart bootloader , select to start. f that doesnt work, you have to disconect the battery, and wrtie an factory image ( nexus 4 occam ) . Try to boot the phone first when disconecting the battery, before writing the factory img. GL

[Q] Dead phone fix?

Soon after downloading the Facebook and messenger app (not sure if relevant), my N4 died, which isn't unusual, happens maybe once a week. I tried all the usual fixes but this time was different for some reason. I'm running PA 4 Beta 4. There is zero response from the phone while unplugged no matter all the different power button combinations. When plugged in to PC or socket, the red light does appear when I press the buttons after a few seconds, but only while plugged in, no red light while simply "charging". Any help would be appreciated before I send it to get it professionally fixed.
Cheers,
Ger.

GxR92 said:
Soon after downloading the Facebook and messenger app (not sure if relevant), my N4 died, which isn't unusual, happens maybe once a week. I tried all the usual fixes but this time was different for some reason. I'm running PA 4 Beta 4. There is zero response from the phone while unplugged no matter all the different power button combinations. When plugged in to PC or socket, the red light does appear when I press the buttons after a few seconds, but only while plugged in, no red light while simply "charging". Any help would be appreciated before I send it to get it professionally fixed.
Cheers,
Ger.
Click to expand...
Click to collapse
The red light wouldn't be on during charging anyways. Charge the phone from a wall socket instead of the USB port because it'll take a week to charge that way. Let the phone charge for a couple of hours and try again.
Sent with my Nexus® 10 minus 3

Berrydroidcafe said:
The red light wouldn't be on during charging anyways. Charge the phone from a wall socket instead of the USB port because it'll take a week to charge that way. Let the phone charge for a couple of hours and try again.
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Thanks for the advice man, however I left it charging overnight through the wall socket so not very confident of that

GxR92 said:
Thanks for the advice man, however I left it charging overnight through the wall socket so not very confident of that
Click to expand...
Click to collapse
So the phone still won't boot? Can you get into the recovery?
Sent with my Nexus® 10 minus 3

Berrydroidcafe said:
So the phone still won't boot? Can you get into the recovery?
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
No, cannot boot into recovery, phone has been stone cold also the whole time so it doesn't look like its charging (7+ hours), like I said the only indication it is somewhat alive is that the red light does flash while it is plugged in but only while holding the volume down and power buttons. Other than that the phone is completely dead.

GxR92 said:
No, cannot boot into recovery, phone has been stone cold also the whole time so it doesn't look like its charging (7+ hours), like I said the only indication it is somewhat alive is that the red light does flash while it is plugged in but only while holding the volume down and power buttons. Other than that the phone is completely dead.
Click to expand...
Click to collapse
With that, I think you need to call customer service and see if they can point you in the right direction.
Sent with my Nexus® 10 minus 3

Alright man, thanks alot for your help

Any luck? I have the same issue, it won't start and shows a red light when I hold down volume down and the power button. I talked to customer support and they told me to do the typical stuff, said to call LG instead.

uEih said:
Any luck? I have the same issue, it won't start and shows a red light when I hold down volume down and the power button. I talked to customer support and they told me to do the typical stuff, said to call LG instead.
Click to expand...
Click to collapse
No change, will drop it into my local electrical repair shop tomorrow and hope its not that expensive to get fixed, pretty frustrating to have your phone die for no apparent reason

GxR92 said:
No change, will drop it into my local electrical repair shop tomorrow and hope its not that expensive to get fixed, pretty frustrating to have your phone die for no apparent reason
Click to expand...
Click to collapse
I could be wrong but I would think the issue is a dead battery, I would think replacing the battery would fix it but that's my opinion regarding what happened with mine, it was drained down all the way. Not sure if yours was almost dead but mine was very low and crashed, it tried to start again but I think the boot screen took up too much energy and it sucked whatever else the battery had.

GxR92 said:
Soon after downloading the Facebook and messenger app (not sure if relevant), my N4 died, which isn't unusual, happens maybe once a week. I tried all the usual fixes but this time was different for some reason. I'm running PA 4 Beta 4. There is zero response from the phone while unplugged no matter all the different power button combinations. When plugged in to PC or socket, the red light does appear when I press the buttons after a few seconds, but only while plugged in, no red light while simply "charging". Any help would be appreciated before I send it to get it professionally fixed.
Cheers,
Ger.
Click to expand...
Click to collapse
This thread will solve your issue. Its already reported many times.
http://forum.xda-developers.com/showthread.php?t=2250454
Final fix for Nexus 4 red light of death
Sent from my Nexus 4 using Tapatalk

jaison thomas said:
This thread will solve your issue. Its already reported many times.
http://forum.xda-developers.com/showthread.php?t=2250454
Final fix for Nexus 4 red light of death
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you done this? Where are the wires going into exactly? I can't secure it on anything from the battery flex cable.

OK just got a reply from the repair shop, this is what they said:
Task Type : HARDWARE
Notes : between layer of the mainboard the circuit is gone.
new mainboard: 229.-euro
Obviously I'm not going to pay for this, will try the fix in the thread linked but looks like a lost cause. uEih, best of luck with yours, let me know if you manage to fix it. Thanks to those who posted in this thread.

[Q] N4 doesnt turn on. Red Light blinks once.

Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".

easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:

zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.

I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.

Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)

I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.

I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.

Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?

Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.

Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"

charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.

I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".

Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help

AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...

Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved

as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.