I tried to install the factory image to my Nexus 10. After it is installed successfully, the system reboots. However, it gets to the google logo X and just stays there. Has anyone else had issues like this? If so, how did you resolve it? I followed the instructions on the google factory image page. Unfortunately, I had to wipe it and restore the to factory image.
Thanks
Are you restoring the factory image using the flash-all batch file Google provides in the archive?
Also, if your trying to unlock the bootloader by some chance, doing this seems to require a factory restore.
This happened to me after unlocking the bootloader. The following fixed it:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time (this is the side of the volume rocker that is away from the power button for those new to the device).
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
I tried using flash-all.sh. Like you said I had to do a wipe data to get it to work. Thanks for the replies.
Related
As the title suggests, after installing Kit Kat (OTA) and waiting for the device to finish the process, my Nexus 4 is now stuck on the Nexus splash screen. Have let it sit for 20+ minutes now and it will not go any further.
Some assistance is welcome
Thank you
By the way, the phone is completely stock; no root/locked boot loader...and the OTA was pushed to me, not sidel oaded.
Same problem...
Reboot into recovery and wipe cache. (Hold VOL - and Power), in Recovery, (hold Power first then VOL +) to enable the menu.
Be careful with the factory reset option, which in this case will wipe your entire device.
You can also use the adb sideload feature to sideload the OTA package manaully that might fix it. You can download them here with insrtuctions on how to flash: http://forum.xda-developers.com/showthread.php?t=2145848. You might need adb drivers to have your device recognize, http://developer.android.com/sdk/win-usb.html
eksasol said:
Reboot into recovery and wipe cache. (Hold VOL - and Power), in Recovery, (hold Power first then VOL +) to enable the menu.
Be careful with the factory reset option, which in this case will wipe your entire device.
You can also use the adb sideload feature to sideload the OTA package manaully that might fix it. You can download them here with insrtuctions on how to flash: http://forum.xda-developers.com/showthread.php?t=2145848. You might need adb drivers to have your device recognize, http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Clearing Cache did not work...Will have to try other options.
same problem too
I have the same problem too... but now it´s even worse because (after touching all the recovery menu) my N4 gets stuck in the Google screen, and it cannot conect to my PC (but it does charge the phone when connected to the computer)
Any help please!!??? I´m completely lost
thank you
luiiinho said:
I have the same problem too... but now it´s even worse because (after touching all the recovery menu) my N4 gets stuck in the Google screen, and it cannot conect to my PC (but it does charge the phone when connected to the computer)
Any help please!!??? I´m completely lost
thank you
Click to expand...
Click to collapse
Download the OTA package and follow the Scenario #1 steps from here to flash the OTA manually: http://forum.xda-developers.com/showthread.php?t=2145848
If after that and wiping data in recovery the phone won't work, then you need to do a factory reset in recovery (you will lose all your data).
After factory reset, if it still don't work you need to manually flash the factory image. See the guide links in my signature.
Same case, nothing works
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.
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....
Out of the box, remote paired, went straight to update to version 5.1.1, but the cable on my power strip must have come loose during the update and now im stuck at the Google screen.
Ive pressed and held down the bluetooth button on the bottom of the player and got into recovery mode. When it gets to the "No command" portion, I press and hold again to get the options to factory reset the device, but this does not fix the problem and the Nexus Player boots right back to the Google screen. So I wipe the cache, then factory reset, but that fails to work too.
I have OTG USB adapters, is there a way I can copy a stock image to a flash drive and restore the system?
Is there an app that I can install to help restore via USB cable?
Ive read alot of threads, but almost all of them have to do with rooting or flashing to Lollirock, so I dont have any dev tools installed and have only had limited success in using ADB in the past. What am I missing?
SOLUTION!
Got a factory image and unziped it into a folder with fastboot and adb.
https://developers.google.com/android/nexus/images
Followed the steps, but it kept failing. What was I doing wrong?
Well I was using a OTG USB adapter, when I should have been using a normal MicroUSB to USB cable.
Also, I was in the wrong boot mode.
There appears to be two types of recovery mode in which my Nexus Player is detected in Windows/DeviceManager. One is where you press and hold the lone button under the player and apply power, letting go a few seconds into the Google logo. In this initial recovery menu, I have the options to boot normally, boot into recovery, or restart the recovery menu, well I should have stayed there and ran the flash-all script, because when I did do this, it failed initially. Trying a 2nd time worked in restoring my Nexus Player.
The second recovery mode is, from the initial recovery menu, you option to boot into recovery, get the no command error, then pressing and holding the lone button to boot into a menu where you had the option of factory resetting, wipe cache, reboot and apply update from adb. Applying the update from adb allowed my device to get detected in Windows/DeviceManager, but the flash-all script failed. Then tried the sideload command to send a recovery image zip file to the player, but the file transfer would fail about half way through each time. Nexus player would report install aborted.
LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).
LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand