Database Develop

[BRICKED] I managed to brick my N4 just 12hours after purchase

Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:

interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too

I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.

italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie

berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...

I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app

when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,

juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam

Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium

AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.

linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.

I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium

atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam

linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....

tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:

atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day

linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium

linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.

My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.

On / Off button not working good

Hello everyone,
My phone has had some annoying thing since 2 days ago, everything was fine and it just worked the way it had to, but now i have to press the on/off button atleast like 4 times to get the screen on, at very rare occasions its an 2 times click but mostly 3+
im going back to t-mobile to ask what their advice is, what is your advice?
How to minimize the chance they find out i had done root and unlocked bootlaoder ? ^^

Root will be removed after flashing any rom, as for bootloader, someone said flashing taiwan JB relocked theirs, whether it will stay locked when going back to euro is another thing. If it doesn't flash ICS and pray they dont update it
Sent from my rooted P880

@non4 said:
Root will be removed after flashing any rom, as for bootloader, someone said flashing taiwan JB relocked theirs, whether it will stay locked when going back to euro is another thing. If it doesn't flash ICS and pray they dont update it
Sent from my rooted P880
Click to expand...
Click to collapse
ill unroot it with supersu or just something else if i have to send it, i think they gonna try if it is hardware or software failure, so i hope they do not see i installed cwm and unlocked bootloader xd
i think its hardware failure :S

Tomaat said:
ill unroot it with supersu or just something else if i have to send it, i think they gonna try if it is hardware or software failure, so i hope they do not see i installed cwm and unlocked bootloader xd
i think its hardware failure :S
Click to expand...
Click to collapse
Flash ICS, you're less likely to be found out
Sent from my rooted P880

@non4 said:
Flash ICS, you're less likely to be found out
Sent from my rooted P880
Click to expand...
Click to collapse
Also, if it's a hardware failure and you've bought their phone in Europe, they really can't deny fixing it because you have an unlocked bootloader and/or a rooted phone. Read more about it here, so you can go to them with all the information you might need

ain`t you pressing it hard enough? Mine used to be perfect, after a couple of months using it the button became faulty and now I have to press kind of hard otherwise it doesn`t work. But every time I press it hard enough it works.

Hardware
Me too

gabrielgon said:
ain`t you pressing it hard enough? Mine used to be perfect, after a couple of months using it the button became faulty and now I have to press kind of hard otherwise it doesn`t work. But every time I press it hard enough it works.
Click to expand...
Click to collapse
nguyenthanhphong said:
Hardware
Me too
Click to expand...
Click to collapse
If someone as skills, can try to open the device and check how are the metalic parts that activate the hardware.
Its not hard but, take care! Its your phone, your choice.
View attachment 1907737

Can't stop the bootloop

Like an asshole I tried to install the Romaur rom on the 6606 - apparently a bad idea cause it put me into a bootloop and recovery is broken. So now I'm trying to recover with the flash tool but I can't get the damn bootloop to quit so I can put it in flash mode. Any help?
I apologize if this thread exists elsewhere, I searched the terms "c6606 bootloop" and just plain "bootloop" and found nothing to figure out how to stop it - I'm extremely frustrated with this phone right now so I'll admint that I didn't exactly look all that hard. Just if someone would be kind enough to help me out with escaping the bootloop for recovery I would truly appreciate it. Thanks!

Get flashtool ready for flashing including prepared files, connect phone and then hold power and up in till phone vibrates for reboot then quickly change figure to volume down and hold. When phone reboots this will enter flashmode and flashtool will take over. This does work you just have to do it quick enough so will take a couple of attempts
Sent from my C6603 using xda premium

Maddhouse said:
Get flashtool ready for flashing including prepared files, connect phone and then hold power and up in till phone vibrates for reboot then quickly change figure to volume down and hold. When phone reboots this will enter flashmode and flashtool will take over. This does work you just have to do it quick enough so will take a couple of attempts
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Thank you for the reply. Downloads are going slooooooowww and this constant bootloop is making me want to throw it. Thanks man!

yo i can help you with flash tool and instruction
flash tool MOD EDIT: Links removed
instruction MOD EDIT: Links removed
good luck

khamees_xi said:
yo i can help you with flash tool and instruction
*links removed*
good luck
Click to expand...
Click to collapse
I would only get Flashtool from Androxyde's site-
www.flashtool.net
There's a decent guide for using it here in the general section -
How to flash stock roms with Flashtool
No need to give anyone revenue for hosting files that aren't their work to begin with (that hosting site has an affiliate program that pays per 1000 downloads).
Sent from my C6603 using Tapatalk 4

kingvortex said:
I would only get Flashtool from Androxyde's site-
www.flashtool.net
There's a decent guide for using it here in the general section -
How to flash stock roms with Flashtool
No need to give anyone revenue for hosting files that aren't their work to begin with (that hosting site has an affiliate program that pays per 1000 downloads).
Sent from my C6603 using Tapatalk 4
Click to expand...
Click to collapse
Hey guys I got it. I'm brand new to the Xperia. Coming from LG devices I did NOT expect to be as easy as it was. It's really as simple as plug in, select dir, and press flash. Coming from LG we had to start flash count 8 seconds, drop a bin file, dance for rain, ...you get it.
Any way, really appreciate you guys being so willing to help.
Anyone know which roms WON'T bootloop/soft-brick the 6606? I use my phone as my primary internet for my laptop so I upgraded to the $70 unlimited LTE plan only to find out that tethering is blocked on the.most expensive plan. BULL****. So...need a Rom. :good:

[Q] Help, Please

HTC One
Sprint
HBOOT 1.55
S [ON]
OS 3.04.651.2
Problem: Friend thought it would be cool to put Android Revolution HD on my HTC One since he did it on his and wanted to surprise me with it...
Long story short he did, and now I have a soft bricked device. I've tried pushing a stock and a custom ROM through ADB sideload and I end up with a phone that acts like it is going to work, gets to the lock screen and freezes. It has no service but that's irrelevant because I can't even get past the lock screen. I can however use my volume key to raise and lower volume.
Can anyone get me past this or am I screwed till a new RUU comes out/way to get S [OFF] after hitting 1.55?

You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569

bigdaddy619 said:
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
Click to expand...
Click to collapse
Thanks so much for the reply, I'll give it a shot. I'm desperate right now willing to try anything.
Also forgot to mention the boot animation does fine, the phone acts like it's going to work fine then it just plain freezes where it would normally give you the "sign into google account" and name your phone. So I'm not sure what's missing if anything, if anyone has solved this and is willing to help I would greatly appreciate it.

Your partitions are messed up because he flashed a GSM rom on your CDMA device

bigdaddy619 said:
Your partitions are messed up because he flashed a GSM rom on your CDMA device
Click to expand...
Click to collapse
Yeah, exactly. Is there any way I can go about fixing that? I'm checking out that guys thread, and it sounds promising... but I can't figure out how to get my drive to sync with my PC to transfer it to TWRP to install it. I'm going to try to ADB it but I doubt that will work. Starting to lose hope at the moment lol but trying to stay optimistic.

Asosaki said:
Yeah, exactly. Is there any way I can go about fixing that? I'm checking out that guys thread, and it sounds promising... but I can't figure out how to get my drive to sync with my PC to transfer it to TWRP to install it. I'm going to try to ADB it but I doubt that will work. Starting to lose hope at the moment lol but trying to stay optimistic.
Click to expand...
Click to collapse
Only way to fix the partitions is to run an RUU which we don't have.
Is your phone seen by your PC when it's plugged in and booted to the rom? I know it doesn't boot correctly but maybe you can move the file to your phone.
You could also try adb push nameoffile.zip /sdcard/ most likely won't work because of the partitions

Format with TWRP first to get partitions clean, then adb push Rom/sideload
Sent from my HTCONE using XDA Premium 4 mobile app

I'm pretty sure the radio partition get overwritten as well so I would say format sd in twrp, flash a radio in fastboot then sideload your Rom and flash it
Sent from my HTCONE using XDA Premium 4 mobile app

18th.abn said:
I'm pretty sure the radio partition get overwritten as well so I would say format sd in twrp, flash a radio in fastboot then sideload your Rom and flash it
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the replies guys, going to try that now. It feels like entire ROM would work fine and there was just "something missing" from my phone. It may very well be a radio. I know something got wiped that shouldn't have because I had to do partition reset due to... well I'm sure you know. Also had to side load TWRP. Learning experience for me, not frustrated at least I'm getting knowledge to help others with it if I can solve it on my own.

Okay so, reporting back that FIXED my no service issue, and it's bringing up updates in the notification bar, only problem is I can't use the touch interface. I don't think my phone is broken, I think it just lacks everything that makes it a smartphone.
Anyone have an idea as to what I can flash to get it back up and running? It feels like it's missing touch interface, and whatever is needed to initiate the "factory" setup screens. Shouldn't the ROM include all of that? I put Viper ROM 1 on there. Progress was made, but it's missing something lol.
The radio also stopped it from resetting and turning itself off after 30 seconds like it was doing previously. Is there a flash-able touch interface I can throw on it? Heh...
Also noticed after it was plugged in for a couple of minutes it's detected by my PC now so I don't need to side-load anymore. Not that it was hard to, just a step forward I think. Just need to figure out what's missing from the boot screen and what I need to put on it to be able to use the touch screen. Any ideas?

Asosaki said:
Okay so, reporting back that FIXED my no service issue, and it's bringing up updates in the notification bar, only problem is I can't use the touch interface. I don't think my phone is broken, I think it just lacks everything that makes it a smartphone.
Anyone have an idea as to what I can flash to get it back up and running? It feels like it's missing touch interface, and whatever is needed to initiate the "factory" setup screens. Shouldn't the ROM include all of that? I put Viper ROM 1 on there. Progress was made, but it's missing something lol.
The radio also stopped it from resetting and turning itself off after 30 seconds like it was doing previously. Is there a flash-able touch interface I can throw on it? Heh...
Also noticed after it was plugged in for a couple of minutes it's detected by my PC now so I don't need to side-load anymore. Not that it was hard to, just a step forward I think. Just need to figure out what's missing from the boot screen and what I need to put on it to be able to use the touch screen. Any ideas?
Click to expand...
Click to collapse
Looks like you just need to flash a 4.3 rom

bigdaddy619 said:
Looks like you just need to flash a 4.3 rom
Click to expand...
Click to collapse
Really? That's the only problem you think? I'mma try that out I'll give you a message as soon as I do. Thanks again.
Also, is there any way I can get a MOD or someone to un-lock my account? This 5 minute wait is for the birds lol I got hardware on the line here :angel: Need all the posts/help I can get hahaha.

bigdaddy619 said:
Looks like you just need to flash a 4.3 rom
Click to expand...
Click to collapse
You are the MAN my phone's fixed now. BoO YaH. Now I can go beat my buddy up with peace of mind knowing my phone is in good working order.
Now running Stock with goodies, guess the other custom ROMs I put on it were just lacking 4.3 stability. You rock broski.

Asosaki said:
guess the other custom ROMs I put on it were just lacking 4.3 stability.
Click to expand...
Click to collapse
New firmware had updated touch drivers. That's why your touch screen wasn't working right.

bigdaddy619 said:
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
Click to expand...
Click to collapse
Your the man bigdaddy, good to know there is a glimmer of hope for those with 4.3 and s-on.
Sent from my HTCONE using xda app-developers app

Since you're on the newest firmware you can only flash 4.3 sprint roms..the touchscreen firmware has been updated. You can't downgrade or s-off because you're on hboot 1.55. Just sideload a 4.3 Rom and you'll be up and running fine
Sent from my HTCONE using XDA Premium 4 mobile app

If phone doesn't boot...

Well, I was browsing around the market and my n5 just abruptly shut itself off. It hasn't been able to turn back on since. I've tried every key/charge/magic trick in the book so its DEAD!
Happy to jump in the RMA line at this point but was wondering if any others can confirm DEAD devices. The RMA thread is kinda full of nitpick issues but a dead device is a dead device.
This was the only discussion chain I could find on the issue but maybe someone from google will comment on dead devices. lol
https://productforums.google.com/forum/#!msg/nexus/lI6A3fA8bvw/d3eQlqEqabEJ
EDIT:
so it appears holding down both volume buttons + power while it's plugged in to the charger (not USB to PC) will temporarily boot the phone. You can then do a restore to stock and issue gets fixed. :good:

Damn. That blows.
Sent from the jaws of my Hammerhead!

mrro82 said:
Damn. That blows.
Click to expand...
Click to collapse
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Since I was able to get it booted tethered to the power I'm going to have it drain the battery to dead and see if it resets itself or something. Maybe a bad idea but I guess I don't care at this point it's already RMAd and I don't know what else to try. lol

Zenoran said:
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Click to expand...
Click to collapse
Do you have a backup you can attempt to restore?

Have you tried to adb into it?

Delete damn it

I would never install twrp.

There is a stock rom in here somewhere. Flash it boot loader and see what happens.

Synyster06Gates said:
Do you have a backup you can attempt to restore?
Click to expand...
Click to collapse
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.

Zenoran said:
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Click to expand...
Click to collapse
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701

caribouxda said:
I would never install twrp.
Click to expand...
Click to collapse
Why wouldn't you? In situations like this, it is extremely helpful. Do you expect him to install CWM or something? From my understanding, at least when I first got my phone and flash a custom recovery, CWM wasn't booting. If you are here to try and press your opinion on which custom recovery you prefer, go to their official thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app

floxrin said:
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.

Zenoran said:
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Click to expand...
Click to collapse
That's good to hear man. I couldn't imagine how I'd feel if that happened to me. Thankfully XDA us the place that it is and the members, for the most part, have the ability to help us troubleshoot most of our issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app