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
Related
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Maybe try this...
http://forum.xda-developers.com/showthread.php?t=1781250
Or use this program...
http://forum.xda-developers.com/showthread.php?t=1766475
Lockable said:
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Click to expand...
Click to collapse
Reboot into bootloader (hold power to turn off, as soon as it does hold vol down)
Install the android sdk if you haven't. Download a recovery image from clockworkmod.com, put the image in your /platform-tools folder. Open a command Window there
Fastboot flash recovery xxxx.img
Fastboot boot xxxx.img
Dl a rom
Put it in your platofrm-tools folder
Adb push romxxx.zip /sdcard/Download
Flash the ROM in recovery
Reboot
Sent from my Google Nexus 7 using Tapatalk 2
When I turn on my tablet now, it automatically open up ClockworkMod Recovery. I am able to properly install a rom (wipe all data then install rom from sd) but when i reboot my device it goes back into clockwordmod recovery. Any idea how to bypass automatically booting straight into recovery mood and booting into flashboot?
EDIT
i am unable to push new roms in
mis-post, my bad.
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.
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
After performed wipe cache and firmware update with "Swift&Fast Slim B160 aio" ROM, the phone reboot and stuck at waiting for booting... ==> wait for 3 hours and still show the same as BOOTING.
Performed the factory reset by press Volume Up and Power, the Factory Reset is now stuck at 99%
Please help to the the phone back in working condition.
Resolved yet?
Possible idea
You can probably still load TWRP. Press and hold volume down + power at the same time to load fastboot mode.
ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
1. adb reboot bootloader (requires USB debugging to be turned on).
or...... power off the device then back on with 'vol up' + power button.
Wipe your device.
2. fastboot -w
Update your ROM.
3. fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM. Try another ROM if Swift & Fast Slim isn't working. Your file could be corrupted.
did u get things fixed?
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