[Nexus 4 Q&A, Help & Troubleshooting] vipero07:
Solved - with no need to RMA

Yup the device works fine now. I wiped the whole thing and lost all my data doing so, reinstalled the factory image from developers.google.com and it is back to normal, no need to RMA. Good thing I did a full ADB backup, so i should be able to go back to the way it was before the whole ordeal.

For those who are having this issue, regardless of what caused it, try this before RMAing, as you probably don't need to RMA, and if you do you need the original images on the phone anyhow. Especially if this occurred while installing a new kernel or new image or rom.

You need fastboot set up on your computer before you attempt this, there are plenty of guides on the matter.

Plug the phone into the computer and hold the volume down button to get into fastboot mode.

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata

That should erase any bad half copied data from the phone, it may not be necessary if this occurred while doing other stuff in fastboot/recovery but can't hurt.

Then go here Google Factory Image. Download the factory image, and make sure the checksum matches.

extract it to the fastboot directory and do this

fastboot flash bootloader bootloader-mako-makoz10l.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img
fastboot reboot-bootloader
fastboot –w update image-occam-jop40d.zip

Now... here is the hard part... unplug your phone from the computer and plug it into an outlet charger and wait 30 minutes to an hour. After that wait try to turn on the phone, it should boot no problem. If you leave it over night plugged into the wall and it still doesn't boot you may be screwed, in which case boot back into fastboot while plugged into the computer and use one last command.

fastboot oem lock

Call google and RMA.

But to be clear this issue looks like the phone just isn't charging or perhaps isn't getting enough juice while in recovery or fastboot and plugged into the computer.

Also please be courteous and do not RMA unless there really is no other solution. There are plenty of people getting shipped actual broken phones, and you are costing our open source phone providers unnecessary money.

---------- Post added at 08:11 PM ---------- Previous post was at 07:59 PM ----------

I understand that, my main issue was while attempting to find any help in regards to the matter the majority of posts were instead of something helpful like try this or try that, just anonymous garbage that really wasn't helpful and just cluttered the thread, making it difficult for those who really need help to find any.

On the plus side, I have typed up the solution to the problem (as it was for me at least) and I imagine its the same problem for everyone else who has experienced it.

The nexus 4's notification LED lights white for notifications green when it reaches a full charge (it flashes it once, and you may never actually see it) and red when the battery is dead (which is goofy because it has little charge to flash red). So the red led of death loop and the fact the phone wont turn on at all when unplugged from the computer is really just it telling you hey I need more charge before you can boot me back up, please plug me into an outlet and not this useless low charge USB port.