(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 ...
Enter recovery and delete dalvik/cache. To enter recovery you have to hold Volume up + Home + Power (The same with Volume down is download mode). Once in recovery, select the option to wipe cache/dalvik, then restart the phone.
If the phone keeps rebooting as it was doing before, try searching the log of the boot sequence to see if you can find where it ...
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 ...
This answer is only really helpful for unlocked tablets.. Look after this paragraph if that is already the case. Otherwise read on.
"fastboot oem unlock" also does a factory reset, you need to have it unlocked before you need it, alas. This is both good for privacy and bad for recovery from half-bricked devices... The factory reset does In fact a ...
Honestly, I am not 100% sure that this was really a problem related to the kernel. I think that the "problem" could be also caused by the fact that pressing the home key in recovery mode results in a reboot. The correct way to select a recovery item is to press the power button.
I had the same issue two days ago. The problem was the ...
I finally figured it out, here's how I did it:
Even though adb can't get root, and the phone it's self can't get root, as it turns out, there is in fact one more way to clear the cache without fully booting the phone.
Turn the phone off
Make sure you have fastboot working on your computer
Press the power button on the phone and then hold down the volume ...
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'
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 ...
No, you MUST NOT reformat it before copying! Formatting a storage device means to prepare it to hold files, and it will delete everything on it (see the tag wiki of the formatting tag for details). So yes, formatting woul imply losing all contents on the formatted device (in this case, from your SDCard).
New cards usually come pre-formatted, so there's no ...
Some devices (I don't know about the Nexus 7, but I think it will be about the same) only charge when they have still a little charge left on their battery, because - believe it or not - charging happens electronically. So it can be that your device has absolutely no juice left to run. An example of such a device is the BlackBerry PlayBook (not Android) ...
If you've just plugged it in to the charger, leave it a while before you try to turn it on. The boot sequence uses power faster than USB can provide it, so you will need a little juice in the battery in order for it to boot up all the way.
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?
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 ...
You will know if the kernel has hung, the led light stays on and not go further.
As for your question, you need to be more clearer and specific as we do not know and since you posted a similar question before. You have not stated, what device is it, what android version is it, what kernel is it, all those are left out and thusly playing a guessing game ...
To fix my device I did the following:
pull the battery to get the device to stay off (if you are quick you
might be able to hold the power button and select shut down before it
While the device is off hold both volume buttons and the power button. This will bring up a bootloader menu
Use the volume buttons to change selection to "Recovery Mode" ...
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.
If you have fastboot, boot into that. You can then procede to wipe data while in fastboot mode by issues the fastboot -w command. You can then reboot the device using the fastboot reboot command.
Be aware that not all devices come with fastboot. If you can access ADB while the device is booting, then you can issue an adb reboot recovery command to reboot ...
Try booting while pressing the back key. That will get you into fastboot, and you can access hboot (and hence recovery) from there.
If it worked try any solution among this..
It depends on the cause of the boot loop
Wipe cache and dalvik (depending on what recovery you look in different places for these. I think ClockworkMod may have wipe dalvik in ...
I just had a quite similar problem with my Galaxy Nexus (it didn't go past the Nexus X logo) and it seems it's not possible to make a backup with a locked bootloader and without root (at least not with Android 4.2).
I thought ce4's method could be a good try and so I unlocked the bootloader and then immediately booted clockwork recovery. Next, using adb ...
That's unlikely to be possible. Dalvik cache is stored in /data/dalvik-cache, and doing an ls -l /data (as root) shows:
drwxrwx--x system system 2013-03-29 14:54 dalvik-cache
As you can see, it is owned by user system of the group system, and all other users only have "execute" permission (i.e. they are only permitted to change into that ...
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 bootloop 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 menu.
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 "...