Database Users

officially bricked

I tried to load up the new gingerbread roms from my current one. I downloaded its content and tried to install it via clockwork.
I first deleted system, logo, and cache followed up by a restore format. When trying to download the new rom, I was getting a weird error that was stopping me from completing the full installation. So basically was in a chokehold because I didn't have any backup files or another working rom in the sd at that time. I just restarted the phone and it for a few times was stuck on the M screen, but now its just green led when I plug it into the computer usb. When plugging it into the outlet, it imediately turns on stuck on the M screen and shuts off when unplugging as if the battery isnt charging at all.

Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App

bigshotrob22 said:
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
thats the problem.. i got the X.340 sbf and the program aswell but I cant get into bootloader mode. is there an alternative way to sbf?

Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App

Could be your battery same thing happened to me try using a friends battery your battery could be dead and it no longer charges
Sent from my DROIDX using XDA App

bigshotrob22 said:
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
bootloader is such a rare occurance for me, i just had it come out but it was flashing low battery. the thing is, im not quite sure if its charging if i have it plugged into the computer. when i have it plugged into an outlet, the M splash screen comes up so i'm worried that draining the power..
edit: now it flickers for a split second, am i supposed to hold on to it til something shows up? been like 1 minute
i dont think bricking phone blows your battery. at least i hope it doesnt, was working fine before.

Plug it in without the battery if a question mark comes up you ned to use another battery cuz it won't charge in boot loader and the boot loader should pop up right away hold power volume down and camera button it takes about three seconds
swyped from my DROIDX using XDA App

well its basically the same thing. when plug into the outlet it shows the m splash screen with or without the battery.
when its plugged into the compuiter however, its just flickers once. when it is done with the battery in, the led is on forever
EDIT: OBSERVATION
when on the wall, it is actually charging, but REALLY slowly because of the fact that the splash screen stays on. found this out because i had it in for30 min and then tried to connect mit to my comp with bootload and it loaded for a few minutes with the low battery flashing.
is version 320 the latest?

Okay. so it isnt charging as I though because its not working at all... problem is, I dont know if it truly is a battery defect. If I were to Buy a new battery, how would i know if it is charging if it doesnt boot and just stays stuck on the M logo screen?
perhaps I should by a battery charger where i take the battery out and charge it through there? because my bootloader always gives me the same low battery.

Do you have any friends with the same phone? There is also a macgyver (spelling?) Method of doing this by cutting the USB cable open and attaching the cable ends to the battery. However I would only do this if you're really desperate

i just really need make complete sure that this phone is INFACT dead battery
when not plug, it doesnt turn on what so ever with a white spark on the led.
when plugged nto outlet the logo shows but i isnt charging because it isnt booting
when plugged into the computer it is a solid green which i think represent a dead or a low battery state(can someone back thisup?)

Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.

raziel36 said:
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
Click to expand...
Click to collapse
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen

jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
There's a usb trick u can try. Google it.
Sent from my DROIDX using XDA App

jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
You definitely need to use the bootloader, and I was implying that in the first reply(SBF'ing requires going into the bootloader). If you had a stand-alone battery charging cradle/dock, that should do the trick. Just make sure to let the battery charge sufficiently. I've successfully gotten an SBF completed, starting with only 30% battery. SBF takes about 7 minutes on my laptop(not that I've timed it, but I usually light up a smoke when I start the process lol). So, as long as the battery is charged enough to no longer give the "Low Battery" warning in the bootloader, you should be fine.

You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App

froyli said:
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
al the tips or just red for pos and black for neg

Positive and negative google it before you do it
Sent from my DROIDX using XDA App

okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone

jinho11050 said:
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
Click to expand...
Click to collapse
Glad you got it working! Nearly everyone on here has needed help, at one point or another, and that's what makes Android so great... the community.
Sent from my DROIDX using XDA App

ok so my phone hates me

Had Build 5 of the team hacksung ICS. i went to turn my screen on and nothing, I figure ok, pulll the battery, it will be fine. NOT. I pulled the battery, put it back in, tried to turn the phone on and all I got was the battery charging screen (with a grey battery with the loading symbol in it) and it kept turning off and coming back on over and over. I threw it on the charger for shi*s and giggles and it booted into recovery, nothing I tried made it boot past recovery (while plugged in) or past the half charging screen (when not plugged in)
I managed to go home and odin back to stock (full DL09 w/ atlas 2.2 pit) but if I turn the damn thing off and then try to start it again, same damn thing! idk what the hell to do or even what happened. no amount of odin is helping.
Anyone have any idea what the heck happened here?

Neuman.Tim said:
Had Build 5 of the team hacksung ICS. i went to turn my screen on and nothing, I figure ok, pulll the battery, it will be fine. NOT. I pulled the battery, put it back in, tried to turn the phone on and all I got was the battery charging screen (with a grey battery with the loading symbol in it) and it kept turning off and coming back on over and over. I threw it on the charger for shi*s and giggles and it booted into recovery, nothing I tried made it boot past recovery (while plugged in) or past the half charging screen (when not plugged in)
I managed to go home and odin back to stock (full DL09 w/ atlas 2.2 pit) but if I turn the damn thing off and then try to start it again, same damn thing! idk what the hell to do or even what happened. no amount of odin is helping.
Anyone have any idea what the heck happened here?
Click to expand...
Click to collapse
Are your volume buttons stuck?
Sent from my SCH-I500 using xda premium

Nope but I'm thinking I'm going to try some electronics cleaner just in case. My phone is my music when I lift so I change songs often meaning its a distinct possibility that's its gummed up a bit in there lol
Sent from my SCH-I500 using XDA App

Neuman.Tim said:
Had Build 5 of the team hacksung ICS. i went to turn my screen on and nothing, I figure ok, pulll the battery, it will be fine. NOT. I pulled the battery, put it back in, tried to turn the phone on and all I got was the battery charging screen (with a grey battery with the loading symbol in it) and it kept turning off and coming back on over and over. I threw it on the charger for shi*s and giggles and it booted into recovery, nothing I tried made it boot past recovery (while plugged in) or past the half charging screen (when not plugged in)
I managed to go home and odin back to stock (full DL09 w/ atlas 2.2 pit) but if I turn the damn thing off and then try to start it again, same damn thing! idk what the hell to do or even what happened. no amount of odin is helping.
Anyone have any idea what the heck happened here?
Click to expand...
Click to collapse
I kinda have the same issue. When I have the phone unplugged and off, I cannot turn it on. When I push the power button I get a blank battery charging image. However, when I plug the phone in and wait for the battery charging icon to appear , then push the power button the phone will start. Also, when on and not plugged in, the notification area intermittently presents "USB connected". I have chalked this all up to being an issue with my USB port on the phone being damaged and learned to ignore the notification. I have tried several ROMs and have the same issues across the board (GM and ICS ROMs)

truckinpaul said:
I kinda have the same issue. When I have the phone unplugged and off, I cannot turn it on. When I push the power button I get a blank battery charging image. However, when I plug the phone in and wait for the battery charging icon to appear , then push the power button the phone will start. Also, when on and not plugged in, the notification area intermittently presents "USB connected". I have chalked this all up to being an issue with my USB port on the phone being damaged and learned to ignore the notification. I have tried several ROMs and have the same issues across the board (GM and ICS ROMs)
Click to expand...
Click to collapse
Try a different battery

That was my next step once I get home. Half afraid to turn the dang thing off at risk of having to start over..again
Sent from my SCH-I500 using XDA App

Ok so I finally got around to some testing. If I power off the phone and power it back on its fine, if I reboot, its fine, if I take the battery out (like when I flashed the ec09 radio earlier) then it does the same crap as before. If I plug the charger in and try again its good. I tried my buddys battery and all was well so its my battery.
Hope this helps anyone who runs into this problem!
Sent from my SCH-I500 using XDA App

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.

[Q] Flashing red light - recovery works but nothing else

Phone was on about 60%. Plugged in the charger, downloaded Bricked Kernel to add to my r11 Modaco Cyanogenmod rom. Ran antutu and the screen went to the charger symbol. Pressed the power button then the charger symbol went and the red light started flashing.
Read up on here and tried the volume up + power for 60 seconds and plugged in the charger. Nothing
Tried volume down + power for 60 sends and plugged in the charger - Google symbol then into bootloader. This allowed me to get into teamwin, where I could recover my backed up image. Pressed reboot. Nothing just the red light again.
Been on a 1.5a charger for over an hour and still flashing
I'm now trying the charger in recovery mode.
I would take the back off and disconnect the Battery but my darling Mrs has had a clearout so I don't have the right screwdrivers :/
Anyone had this particular combo?

Had the red led ligth too after flashing some roms and testing it out. It powers off and shows the red led. Nothing works. I noticed that my n4 was very hot so i let it cool down for about 3 hours. After that all was fine and my n4 booted up normal. Had a heart attack as i see this red led. I think it is becouse the n4 is overheating but dont know. Hope that helps you
sent from my AOSPA3+ Nexus⁴ with Tapatalk 4

ChaosChris said:
Had the red led ligth too after flashing some roms and testing it out. It powers off and shows the red led. Nothing works. I noticed that my n4 was very hot so i let it cool down for about 3 hours. After that all was fine and my n4 booted up normal. Had a heart attack as i see this red led. I think it is becouse the n4 is overheating but dont know. Hope that helps you
sent from my AOSPA3+ Nexus⁴ with Tapatalk 4
Click to expand...
Click to collapse
Thanks
I did notice it was hot when it first happened. Its been a while now though and certainly feels cool to touch.
When I do boot into bootloader or recovery, as soon as I unplug the charger it turns off again. :/
Perhaps I'll leave it longer (in the fridge ) and try it again

mrew42 said:
Thanks
I did notice it was hot when it first happened. Its been a while now though and certainly feels cool to touch.
When I do boot into bootloader or recovery, as soon as I unplug the charger it turns off again. :/
Perhaps I'll leave it longer (in the fridge ) and try it again
Click to expand...
Click to collapse
It sounds that your battery seems to be defect. I know that some one on xda says that removing the backcover and then remove the battery and plug it in again solve that for him. Dont have the link right now but there is a thread about the red led issue. Try to Google it a bit
sent from my AOSPA3+ Nexus⁴ with Tapatalk 4

Thanks again
I found that thread but am currently missing the right screwdrivers to remove the back. That's for tomorrow when I can pick some up from the phone shop. Damned piece of crap LG nonsense. First no USB OTG and now this!!

Battery is definitely munged. Whenever I manage to get into Recovery (TWRP) tha clock is always back at 12:00.
Soon as I unplug the charger, even after an hour or so, it shuts down. After a full night just on charge, just the flashing red light, no response to pressing the power button.
Just gone through the Google replacement process, but being Thursday evening it will probably be Monday at the earlier before it turns up.
On a lighter note I stuck CM 10.1 on my wifes SGS. Apart from being smaller, slower and with a quarter of the memory, the Helium back restored without a hitch and I have virtually the same experience .....