Database Users

HELP - Nexus 4 Won't Boot + Other Issues

Hi All,
I tried to complete a manual update of the 4.3 OTA on my Nexus 4 this evening, however unfortunately it didn't work and my phone would not boot past the 'Google' screen. After wiping the cache, and still having the issue, I decided to do a factory data wipe/restore. However the problem still persisted.
With this, I thought the only way past this was to install the factory image. I installed the 4.3 factory image just fine (after going through the various steps, including unlocking the bootloader) and it was up and running for a while installing apps. However, with this, the device had a black/blank screen for a fair few minutes and after leaving it I thought I might has well reboot. Unfortunately, this time is did not boot again.
So; off to do the same previous steps again.... fastboot oem unlock (as I relocked the device previously), load bootloader, etc, etc. Got to the system update, and it passed an error saying that fastboot is not available on a locked device. Strange as I had unlocked it, but there is was on the menu "LOCK STATE - locked"....
I am now at the stage where I can't actually keep my phone unlocked. I can complete the command fastboot oem unlock, but once I complete fastboot reboot-bootloader, the device is stating it is locked again. - This is where I need some help, PLEASE.
Sorry for the long post, but wanted to describe the situation. If you need further info from me, just let me know. I'm hoping someone far wiser than I am can help me resolve this issue...

Any help on this? - It would be much appreciated.

I too have the same problem with my phone
but my phone is 4.2.2. rooted and wouldn't load past the 'google' boot screen
I can still go into clockwork recovery mode and I wiped cache, did factory reset and I can't even access my phone through the computer

[Q] Nexus 4 no life after fastboot oem unlock

When using Fastboot oem unlock to flash the kitkat image, I got this message:
C:\Users\riel>fastboot oem unlock
...
FAILED (status read failed (Unknown error))
finished. total time: 122.501s
Now, I cannot see to get the phone on. When I plug the phone in the PC, I hear the usb connection sound but unknown device. It did boot once after this error, and got me into a fresh 4.3. Then, after turning it off to charge, it is not turning on again.
I saw the red light very shortly, and now it is doing nothing when I press power button or power / vol down.
Any next steps? I only see 'red light fix' but maybe something went wrong with fastboot?

not to get down on you or anything, but fastboot oem unlock does not flash anything. it only unlocks your bootloader. and fastboot oem lock locks it back up. if you are trying to flash the factory image, its also done via fastboot and the bootloader, but there are other commands for it. theres a how to flash the factory image thread in general, you should check it out.

simms22 said:
not to get down on you or anything, but fastboot oem unlock does not flash anything. it only unlocks your bootloader. and fastboot oem lock locks it back up. if you are trying to flash the factory image, its also done via fastboot and the bootloader, but there are other commands for it. theres a how to flash the factory image thread in general, you should check it out.
Click to expand...
Click to collapse
I only did fastboot oem unlock for now, and rebooted.
My battery is very dead maybe? It's not turning on anymore, no lights, nothing.

Riel said:
I only did fastboot oem unlock for now, and rebooted.
My battery is very dead maybe? It's not turning on anymore, no lights, nothing.
Click to expand...
Click to collapse
It has nothing to do with fastboot. Search for Nexus 4 red light fix on this forum or google. Or let your battery charge for a while.

Riel said:
I only did fastboot oem unlock for now, and rebooted.
My battery is very dead maybe? It's not turning on anymore, no lights, nothing.
Click to expand...
Click to collapse
its possible. if you turn off the device, and plug it in, it charges?
have you flashed a custom recovery yet? try charging it a little, the go into your stock recovery(if you didnt flash a custom recovery) and factory reset/wipe data. see if you will boot then.

simms22 said:
its possible. if you turn off the device, and plug it in, it charges?
have you flashed a custom recovery yet? try charging it a little, the go into your stock recovery(if you didnt flash a custom recovery) and factory reset/wipe data. see if you will boot then.
Click to expand...
Click to collapse
it failed when he done oem unlock, so he is everything stock.
Now to fix - for me looks like eMMC fail to me,if red light fix dont work, see if u can get your phone to recognize as QHSU_DLOAD so u can use QPST to recover it.

Nexus 6P black screen will not boot into OS

Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.

You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !

hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S

xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this

Hard brick? Can't boot to recovery

So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.

You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM

vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.

I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.

hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.

eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!

Essential phone not booting after OTA update to Oreo. No recovery, bootloader locked

So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?

Did you hold the power button down until your phone completely powered off? I'm assuming you did. What you described isn't supposed to happen on a dual partition phone. If an update goes bad the phone is supposed to recover by booting from the other partition. If powering the phone down completely and then turning it back on doesn't allow you to boot I would honestly go straight to Essential Support since you didn't mod your phone or unlock the bootloader. I dealt with support via email and if nothing else they are definitely very responsive. They answer emails so promptly it was almost like being in a chat.

devon4786 said:
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Click to expand...
Click to collapse
Hello
Tell us the status of your phone Did you solve the problem? Tell us the way I'm stuck in the same problem