Lollipop update has bricked my nexus 4 - Nexus 4 Q&A, Help & Troubleshooting

I did an OTA update of Lollipop on my nexus 4, it got stuck on the 'installing system update' for about an hour, so I tried to restart the phone and it loaded the new lollipop animation, but got stuck there for 20 minutes, so i restarted it and it still didn't want to load into Lollipop, so I went into the bootloader and hit recovery and it came up with 'installing system update' again and still gets stuck. when i'm in the recovery, it won't recgonise vol + and power button press to do a factory reset, it just does nothing. my computer also doesn't recgonise the device... is there anything I can do?
Thanks!

Start into bootloader and try to flash the factory image via fastboot.

boot to fastboot and flash a custom recovery. you can use twrp or cwm to do a standard factory reset and you should be fine.

Related

Nexus 10 not detected in fastboot.

I was on 4.4.4 stock with bootloader unlocked. I flashed custom recovery from fastboot and rebooted into CWM. It was all fine till this point. On next reboot, It booted in OS all fine. I did adb reboot recovery and it got stuck at "No command" screen. waiting a long time ons creen it booted into OS.
I reboot into fastboot to reflash CWM and check but it wont detect my device in fastboot devices. I'm on OS x. I even tried windows (drivers installed) , its the same. fastboot is stuck at "waiting for device".
ps. I installed "recovery-clockwork-touch-6.0.1.6-manta-Wfix-by-damien667.img" from downloadandroidrom.com
Have you tried turning off the tablet, then booting by simultaneously holding the power, volume up and volume down buttons? This is the manual way to boot into CWM. After you are in cwm you should be able to reflash or just reboot into the OS.
uDude
The stock-Recovery is reflashed when you reboot to Stock OS, you have to disable that.

[Q] Stuck in clockworkmod recovery

Hi,
my phone was already rooted and I wanted to update it. But now I'm stuck in cwm recovery and now it won't let me reboot. The USB doesn't work either. I have wiped data/factory reset but nothing changed. Does anyone have any tips?
Download the latest factory image from google and flash it though fastboot.
Hold down the power button for ~10 seconds and it should force your Nexus 4 to power off and reboot.

Flashed TWRP, now can't flash back to stock recovery. Help...

I updated to Lollipop using adb and stock recovery. That worked great. Then I flashed TWRP and made a nandroid backup. I have not rooted again since I'm switching to Nexus 9. So I want to reflash stock recovery, but I didn't save it.
I have the original stock recovery from the mantaray-lrx21p factory image, but when I flash it and boot into recovery, it's just blank screen. I'm assuming the OTA update also updated recovery? Does anyone have a copy of stock recovery after the OTA Nexus 10 update I could borrow?
Thanks,
Steve
Interestingly, I find that if I flash the stock recovery from mantaray-ktu84p, then it works. So it's the stock recovery in mantaray-lrx21p that just shows blank screen...
Same issue here to? Fix
Galaxy 6s Os 6.2.8▪Ss° Pen
I think the fix is we need to get someone with the latest Lollipop patch to extract and give us the recovery.img?
When blank screen appears, press power button for few seconds until the green robot appears, then press power + volume up ( or down ). the stock recovery menu will show up
I don't get any robot when pushing power button on blank screen. After 10 secs, device reboots. Are you sure it works like this now?
Well this is strange. I started all over with ktu84p, then applied the OTA lrx21p update. After the update, the recovery still says ktu84p so it did not get updated by applying the OTA update. Is that what everyone else sees as well? If I flash the recovery.img from the lrx21p factory image, then I get the blank screen instead of robot.

[Q] Nexus 4 Stuck on Reboot after Android 5.1 Update Error

Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Check my thread, I had the same problem. 5.0.1 was fine but sensors went kaput, yes all of them. Flashed factory image 5.1, endless boot screen. After a day or two of flashing 4.4.4 (sensors were back working okay, wow big surprise), tried flashing 5.1.1 pure stock, same.
I'm back to 4.4.4 after restoring apps and data. Not sure I want to use 5.0.1 due to hte memory leak and other bugs that should be fixed with 5.1. But I'm certain that the factory image of 5.1.x won't boot on the N4.
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
Try doing this
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Hope that helps
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
I don't think that the factory reset will solve the problem. Have you tried waiting for 10-15 minutes for the phone to boot up? After OTA's and clearing cache the phone usually takes a while to boot up. If that doesn't work, factory reset using a custom recovery (this will delete your /data folder but not /data/media so your internal storage won't be wiped)
Blacksmith5 said:
.. Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
My, that text looks familiar....

Stuck at "Google" screen after TWRP wipe

Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
goister said:
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
Click to expand...
Click to collapse
So since everything was checked, that means you wiped the system partition. The device will not boot if you do that unless you flash a factory image via fastboot or new ROM via TWRP
OK, I thought wiping /system would just bring it back to factory state. 2 questions now
1. How do I get to recovery when it's always stuck at the Google screen with no adb access? Would I have to wait for the battery to run out (hence turn off), charge it for a while, then use the buttons to boot to recovery, or is there a faster way?
2. I am actually trying to revert to stock ROM (downloaded at https://developers.google.com/android/images#angler) by following step 10 of the Heisenburg guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) which advises me to use fastboot to flash the individual images. In my case, how do I boot to fastboot?
OK, so I managed to boot to the bootloader and run the following commands as per the Heisenberg guide (using the stock MTC20L firmware)
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Everything was successful, and I did a fastboot reboot after that.
However, my device still doesn't boot up. This time. It's boot loops for a few times before turning off.
I tried booting up to bootloader with power/vol-. Curiously, I can now only do this when cable is connected. If cable is disconnected, the orange LED just blinks once when power button is pressed, and nothing happens. Once cable is connected, then I'm able to boot up to bootloader with the button combination. I then retried the flash process again, but still no go. I noticed after fastboot reboot that the orange LED blinked a few times before rebooting and boot looping.
Kinda stuck now, any ideas?
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Face_Plant said:
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Click to expand...
Click to collapse
Thanks. Booting into stock recovery shows an exclamation sign with "no command", since I don't have TWRP anymore. Would I need to first flash TWRP before I can do a factory reset?
I just tried flashing to the same sock firmware as before the problem happened (7.1.2 N2G47W) but still same problem. I notice that after the Google logo disappears and the screen goes blank, the orange LED blinks 10 times before rebooting.
Edit: Tried factory resetting in stock recovery (by holding down power button and pressing vol+), the rebooting after factory reset. Still getting a boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
goister said:
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
Click to expand...
Click to collapse
brother help me! i am facing same issue
first little info abt my device.
my device was running on android nougat with twrp recovery installed but the device was not rooted.
so get back to stock and install oreo I followed every step given on http://www.androidexplained.com/nexus-6p-revert-stock/ but somehow my phone is stuck at bootloop with no recovery installed.
Please help me here.
As per the Heisenberg guide, if you don't install root (SuperSU or Magisk), TWRP won't stick, so you'll go back to stock recovery.
For me, simply unplugging the USB cable after rebooting after a flash solved my problem. For some reason, if the cable is connected during reboot, it would boot loop.
brother, somehow I managed to install twrp. but everytime I touch it 2-3 times the phone gets switched off.
then it keeps rebooting to 'Google' logo.
can you tell me what should I do now?
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
tommast said:
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
Click to expand...
Click to collapse
hi, did youmanage to solve this problem? I am aving the exct same problem. Disconnecting the ucb isnt working for me

Categories

Resources