(Self answering here because I only found this answer after hours of dredging through 200 page threads of forum posts.)
There are two non-standard but semi-prevalent methods that may work depending on your make and model (and why recovery isn't working in the first place).
Some phones actually respond to fastboot reboot recovery. This is quite natural ...
I think you encountered the issue with a stuck power button. I had the exact same behaviour that also went away without explanation to return a few weeks later. I read the one trick is to bang it in a hard surface and shock the button out of its stuck state.
The second time it occurred I actually found a much more gentle way to temporarily fix this. Take an ...
Episode 3: Return of the Shell.
If I ever had any chance of solving this, I first had to figure out why the shell wasn't working. adbd itself was responding, so it was started on the tablet side - but it could not execute the shell, even when I hack-patched it to invoke a file (/sbin/sh) that I myself placed in the boot image - being 100% sure that it had ...
I also had a boot loop today, after flashing Semaphore's ClockworkMod Recovery according to these instructions, then trying to boot to recovery mode. What helped me out was the hint at the bottom of that page: to use Replicant's recovery.img instead:
heimdall flash --KERNEL recovery.img --no-reboot
Update: Note that the hint has now been removed with the ...
/data/property/persist.sys.dalvik.vm.lib contains the name of the runtime library you wish to use - libart.so or libdvm.so. So, you can switch back to Dalvik like so:
adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
I just came across this problem myself on my Nexus 5 running Android 6 and after tinkering with it for a few days I was able to resolve it without wiping all my data, so I wanted to share what I did in case anyone else ever comes across a similar issue and is up for the challenge of debugging the issue instead of wiping the phone.
My problems all seemed to ...
Proper research would have prevented this, in the future if you need information on rooting a device, go to a REPUTABLE source like XDA or a similar forum and make sure the information is specific to your device AND the current Android version. Lollipop, Marshmallow, and now Nougat are changing the way rooting is being done.
All retail/unlocked Moto devices ...
As of this moment, it is a known fact (not necessarily an issue) that the Xposed framework DOES NOT WORK with ART.
So, you either:
Stay with Dalvik runtime, and get the advantage of using Xposed; OR
Uninstall Xposed framework, and get the advantage of using ART
After installing Xposed, the runtime gets reset from ART to Dalvik. Can you stop it please?
Thank you for your answers everyone. Unfortunately I was unable to boot into Clockworkmod Recovery.
Fortunately I found the following solution:
Downloaded and installed RSD Lite (on Windows 8 Professional x64)
Downloaded and installed the Motorola USB Drivers
Downloaded a SBF image from here: http://sbf.droid-developers.org/umts_jordan/list.php
Started RSD ...
The flash-all.sh script does not take into consideration that your bootloader is locked after each restart.
I opened the shell script and executed each command one by one, re-unlocking with the following after each command:
fastboot oem unlock
I flashed each image with no errors, but it did not seem to write to memory regardless.
It seems you've already found some kind of solution to your problem (there's a lot of text to read on this page), but it seems this probably could have been resolved much more simply.
linuxbox# fastboot getvar all
(bootloader) version-bootloader: 3.03
(bootloader) version-hardware: rev_c
(bootloader) variant: LEOPARDCAT 16G
To reach Google and proceed with the next steps, you need to set up a PC that's capable of penetrating through that wall (e.g. with VPN), and make it a proxy server on the local network for your phone to use. Here's the way I do it:
On your PC, install Privoxy and let it through your firewall (if exists)
Go to its installation directory and open config.txt. ...
Thank god I figured out how to fix it.
The problem was that I was using software that was meant to root a first gen Nexus 7, and I had the second gen (2013) version. Whoops.
In order to fix it, I downloaded the Unroot/Stock Toolkit from
and then downloaded the factory images ...
The reason for a boot loop after editing build.prop is its permissions.
Just go to TWRP > Advanced > File Manager and navigate to /system/build.prop. Select it and change its permissions to -rw-r--r--. To do that, enter 0644 in chmod and reboot your device.
If you cannot see build.prop in /system folder, go to Mounts and select System in the TWRP home ...
Find problem apps by rebooting to safe mode
If your device keeps restarting itself, freezing, crashing, or is slow to respond, it could be caused by an app you’ve installed. You can use safe mode to start up your device with only the original software and apps that came with your phone. If the issues with your device go away in safe mode, the problem is ...
On an earlier version of Lollipop, after an update, my Nexus 5 would turn off randomly and enter a boot loop. I tried entering recovery just as you did but it too kept rebooting. I researched reasons for a boot loop and discovered some users of the Nexus 5 have faulty power buttons.
Try repeatedly tapping the power button as if to get it unstuck. See if the ...
Now that you can enter into fastboot, you can execute the commands below
fastboot flash recovery ~/Downloads/bootZ3monxtest01.img
and fastboot reboot and install a custom rom.
flash boot boot.img is used to flash kernel images.
boot.img is a file which contains kernel and ramdisk.
More on Boot & Recovery images can be found here
Whether an app is enabled or disabled is stored in a single file /data/system/users/0/package-restrictions.xml.
I took the following steps to re-enable the Google App and solve my bootloop problem:
Boot the Android-x86 virtual machine in debug mode (i.e. append DEBUG=2 to the GRUB entry)
mount the filesystem:
cd /dev # these are necessary to "...
Been busy working on the issue for a couple of hours now...
I have tried to reproduce the boot loop issue and I think when you update the su binaries somehow the system.img file is getting fried for no reason, so I tried to get the logs, but they don't have any useful information:
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
This was a long process with lots of side problems coming up. Somethings I don't know why they worked or did not work. I will give a recount of what did work in hopes the information will be useful in the future.
At a high level the idea is to backup the data partition, reflash firmware and ROM to fix the bootloop, reload the backed up data partition. ...
I had same problem with logo loop.. I somehow screwed my EFS folder, but don't actually know how... Anyway I tried like 150 different thinks to fix it that I googled out but non of it worked for me..
Finaly I download orignal stock ROM but the old one with 4.0.4 android. Flashed via ODIN and only then get rid of logo loop and phone turned on normally (it ...
Since you said you have aready use Odin to flash, I think you know how to get these necessary files: Bootloader, PDA, PHONE, CSC, PIT.
Then, let's start.
Force the device to the upload mode by this way: simultaneously press power button and down button.
When the device is in download mode, plug Odin software and flash ONLY bootloader file (normally ...
You have to download a rom for your mobile.
Download it from
Download a flashtool from
open the flashtool
Connect a USB cable to your computer.
Turn off your phone.
Connect your phone to the USB cable while holding the Volume down key.
After leaving it in the loop for days using 4 different wall adapters and a USB port, I found the wall-to-USB adapter that originally came with my device. I plugged my tablet in with that and it booted normally and started working; I don't know why that fixed it, but it did.
I was having the same issue as this. I was in a "recovery boot loop" and could not get to the recovery options. I did have ADB access to the device after I installed the "Naked Drivers". Once I did this I was able to see the device using the command "adb devices". The MAGIC command once I had adb access was "adb reboot bootloader" BAM! It rebooted mid ...
I had suspected that formatting additional partitions like /firmware and /persist might be somehow related my boot loop - but I have no educated confirmation of this! Any CM aftermarket firmware that I tried would get stuck at the boot though.
The following solved my problem:
Install the (latest) Google Stock Android - this is just as easy as installing ...
As your device supports an external microSD card: take that card, put it into a card-reader (if you don't have one: now's the time to buy it; they come for less than 10 bucks), attach the reader to your PC. Now, copy the file to the root of the card, safely unmount, then put the card back into your phone. You should be able to flash it then.
For what ...
Apparently, the 'Google Search' app now contains large parts of the application launcher in Android 4.4.4. Thus, disabling it also stops the launcher and the next reboot leaves you in a catch-22 situation.
With previous versions of Android 4 this wasn't a problem - one could disable 'Google Search' without such drastic side effects. Use-case: make the ...
Okay, same thing happened to me: I disabled the Google search (on Kitkat 4.4.4) because it was draining battery and then my homescreen disappeared. I restarted my phone and it got stuck on the four circles.
As strange as it might sound, once you have the four circles displayed, have someone call you and then the call screen will appear. ...