As title says.
I'm not trying to be rude, but could you not have asked this question in one of the existing "Red LED" threads? The mods try very hard to limit redundant threads.
Again, I'm not trying to be rude.
Edit: Oh wow. That was your first post.
estallings15 said:
I'm not trying to be rude, but could you not have asked this question in one of the existing "Red LED" threads? The mods try very hard to limit redundant threads.
Again, I'm not trying to be rude.
Edit: Oh wow. That was your first post.
Click to expand...
Click to collapse
My apologies. Thought this would be easier as i think i'm not the only one with this question and this is easier to find for people.
I've had my rev_11 for about three weeks now with no red LED. I RMA'd my Rev 10 for a red LED.
Right, but whats the issue? Not working at all. Working sometimes, showing orange instead?
Come to think of it though, ive never seen a red LED on my Rev_11......
Rev 11 since December 6. Still nothing so far. *knock on wood*
neo6776 said:
Right, but whats the issue? Not working at all. Working sometimes, showing orange instead?
Come to think of it though, ive never seen a red LED on my Rev_11......
Click to expand...
Click to collapse
That your phone is not willing to boot/turned on and showing the red led blinking on charge as sign something is wrong.
Sent from my Nexus 4 using xda premium
I encountered the red LED, twice. But luckily it wasn't ruined. I got it to work and boot up normally.
FALSE ALARM: It might've been something else.
My rev 11 still flies, havent seen a red LED yet.
It's been charged in all possible manners, with different chargers on different locations.
Most often it gets charged when it reaches around 40%, but I've had runs where I went to 20% and also having it drained completely. One time was a max runtime test (I got 3 days by using the phone only when I needed to, so just skipped the entertainment bit) and once while playing Ingress it died on me.
Related
I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.
Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.
If it's fried I don't believe that depends of a rom.... I think it was the fault of the AC adapter...try to charge the KF with another adapter...
jlocohustler said:
I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.
Click to expand...
Click to collapse
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
BluesHawk said:
Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.
Click to expand...
Click to collapse
It shouldn't overheat, just freeze and force a hard restart (hold power button for about 20 seconds then turn on). If it is overheating there is something else going on like the AC adapter or some sort of major malfunction from a bad flash. Most likely the AC adapter though.
dnathan13 said:
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
Click to expand...
Click to collapse
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.
jlocohustler said:
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.
Click to expand...
Click to collapse
Yes I read the op where you claim... "very dangerous rom that one" that is the part that I would say is harsh.
Many people have been running the show rom for days with no issues, but one or two people claiming it will overheat and kill their fire is all it takes for everyone to start bashing a rom and make a dev want to leave.
Sorry I came off as a jerk I just get upset when claims are made based on one bad experience that could have been caused by a number of things (bad flash, left over bits of stock conflicting with rom, lack of knowledge of ICS issues about screen timeout, kernel issue ratjer than rom issue although related, etc...)
Sent from my SPH-D700 using xda premium
No over-heating problems at all for me -- I installed Kang ICS ROM three days ago.
I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.
Thanks!
Sent from my Kindle Fire using xda premium
It happened to me already, but it woke up with the original charger.
Thanks!
yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
This just happened to me...
My kindle died after shutting down for one day. No battery at all...
Did you even read the first post of the kernel thread?
ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA
StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
If the devs were offered a dime every time somebody failed to follow directions...
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Not going to argue with you on that one.
ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.
This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2
It will always work best with the stock charger, but until the bugs are fixed, who knows.
KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).
For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA
So I just beat DeadSpace (yay), then I decided to reply on a harder difficulty. Within 15 minutes the phone turned itself off and the LED flashed RED once really briefly. Now it won't power on at all. The issue just happened, I don't know what's up.
I hope it isn't in the untouchable state (soft-bricked) again...................... Of course this stuff happens to me at this time in the night when nobody is awake to respone ......... What do I do? How can I fix it?
If it fixes itself I'll let you know.... I know for sure that I'm not playing Deadspace again after this...
EDIT 1* Just unplugged the charger and popped it into another wall. Now the Red Flash is just staying on, the phone is plugged in. What's going on?.......
EDIT 2* The Red LED stopped, phone still won't power on
EDIT 3* The phone now shows the low battery screen while being powered off... I'm guessing it'll power on now
EDIT 4* The phone successfully powered on, nothing is wrong with it now
Sorry for posting this thread it seems like a waste now..
Soooo! To make it not so pointless, I think I found out why it does this. I think Deadspace drained more battery than the phone could charge so the phone died (battery drain) with no warning. And when it did die the phone was in a state of "what the heck - - - computing - - - enjoy this RED LED!!!!!!". I guess it just means "Super dead battery". So in case anybody else fears for their $500 investment, just give it 10-15 minutes before you panic, and let your phones actually charge
From what I can gather from the various threads about the "Red Led Of Death" is that if it's flashing - it's recoverable in some way, if it's just a solid glow you're SOL. I've spent the last 2 days trying to get my N4 to live again Would actually help if people where more specific about if it's flashing or not.
Just got off the phone to the Play Store and arranging for them to start the RMA process. I guess I'll find out in a couple of weeks what the problem is.
When I first rooted I had the light for 4 hours, got it in and out of the red LED state 3 times that night. It was a horrifying experience. I do not know how I fixed it. I was jamming buttons and eventually got into the boot loader mode, from there I flashed stock boot.img and the rest is history... I wish you luck!!!
Sent from my Nexus 4 using xda app-developers app
I've read it has something to do with the stock charger..
calanizzle said:
I've read it has something to do with the stock charger..
Click to expand...
Click to collapse
I wasn't using the stock charger
Sent from my Nexus 4 using xda app-developers app
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app
Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348
So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??
Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution
Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2
Yes, it's what I said, ah I forgot this link.
When you search, you find
Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.
Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.
Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.
I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app
Alright. Sounds good.
Got mine last week but it's a Rev 10 not an 11.
indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)
Loosen the screws?? Do you have a link to the YT video?
Ordered mine when they were first available, got it 2-3 weeks later (end of November).
Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again
I don't know how I did it. I've been rooted/unlocked for over a month (running CM the whole time) with stock kernel. Last night I upgraded to the 03.24 nightly and everything was fine. 3 hours later I downloaded a franco kernel after some reading and I wanted to try it out. I used Rom Manager to reboot into recovery (like I always do) and install the kernel and as soon as I hit "restart now" apps started FC'ing and my phone never came back on. It never made it to recovery mode or anything. It just died completely and I was around 40-50% battery life.
Currently this is what I'm dealing with:
Holding the power button down for 10 seconds flashes a red LED light. No changed on the screen
Holding any combo of the volume keys (up, down, and both) + power does the same as above
The only time the LED flashes red is when I'm plugged in via USB or AC. Otherwise nothing
I've had to charging for nearly 10 hours now... it's like it has no power at all
When plugging it into a PC I see "QHUSB_DLOAD" in my device manager.
I have the Android SDK and Nexus 4 drivers installed
I have seen NOTHING On the screen since this has happened - no charging animations, fastboot, not even a flicker
I've down A LOT of reading and the only thing I haven't tried is charging it for days at a time and taking it apart (which I'm not opposed to doing) but I'd prefer not to. Is there anything else I can try? Thank you
Sounds like you flashed the franco kernel for the Nexus 7. You aren't the first and probably won't be the last. Unfortunately if you see QHUSB_DLOAD its dead.
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
That's what I was afraid of... do you think this is legit? I saw the video and it looks good. Says it fixes phones that don't boot at all. I e-mailed and asked them about my situation but I'm curious if you have heard anything about them?
http://mobiletechvideos.mybigcommerce.com/lg-nexus-4-jtag-brick-repair/
blahblah13233 said:
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
Click to expand...
Click to collapse
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
blitzzz3434 said:
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
Click to expand...
Click to collapse
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
Most of them are pretty reliable. The one that you linked to, they have their own YouTube channel where people have left pretty positive comments. They seem legit. I'd try them out if you want to be nice and not RMA it.
https://www.youtube.com/user/MobileTechVideos
Yeah its really legit. I got my HD2 Unbricked from there. I flashed a wrong radio and came back with a "RESURRECTED" Bootloader and just flashed a new rom. Its probably different on the Nexus 4.
duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
I would still google them to see if there are actually legit. But hope it all works out for you!
Thanks for the replies everyone. I'm going to send it to them to fix it... I'll post back here with the results so other people can search this thread for answers
its bricked. Next time make sure you look at what your flashing.
I got the red light of death, just charged the phone for around 8 hours and it came back.
Sent from my Nexus 4 using xda app-developers app