[Nexus 4 Q&A, Help & Troubleshooting] NeCr0mStR:
Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.

A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).

What I have done thus far:

Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.

I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.

Tried to custom erase system, boot, recovery with the instructions below:

fastboot erase system -w

fastboot erase boot

fastboot erase recovery

fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img

boot to recovery

set up for sideload in CWM

adb sideload pa_mako-4.1-BETA2-20140310.zip

reboot

Same result, just hangs on reboot with animation for boot.

I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.

I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.

Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??

Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.

Ouput from flashing with Google stock 4.4.2 ROM:

sudo ./flash-all.sh

[sudo] password for jscott:

sending 'bootloader' (2203 KB)...

OKAY [ 0.089s]

writing 'bootloader'...

OKAY [ 0.311s]

finished. total time: 0.401s

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.001s

sending 'radio' (45537 KB)...

OKAY [ 1.790s]

writing 'radio'...

OKAY [ 2.541s]

finished. total time: 4.332s

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.001s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: MAKOZ30d

Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98

Serial Number........: 0221a297d9d67206

--------------------------------------------

checking product...

OKAY [ 0.002s]

checking version-bootloader...

OKAY [ 0.002s]

checking version-baseband...

OKAY [ 0.002s]

sending 'boot' (6340 KB)...

OKAY [ 0.253s]

writing 'boot'...

OKAY [ 0.356s]

sending 'recovery' (6888 KB)...

OKAY [ 0.287s]

writing 'recovery'...

OKAY [ 0.398s]

erasing 'system'...

OKAY [ 0.579s]

sending 'system' (713960 KB)...

OKAY [ 26.844s]

writing 'system'...

OKAY [ 40.883s]

rebooting...

finished. total time: 69.615s

Recovery was broken again.

Had to flash recovery again to get in but I can "adb shell" the phone no problems.

If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.

Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.