Unable to adb reboot bootloader on stock android 3.1 - Acer Iconia A500

Basically installed adb/drivers and running this command simply reboots the device normally and it loads back into android.
Power + volume UP does nothing
Power + volume DOWN brings up some text that tries to read something from the SD card, then ends up with the Android robot and an exclamation mark.
Is there a way to get this to boot into bootloader so I can flash a recovery and try to update the version of android higher than 3.1 or a custom rom?
I have seen a few guides but they all expect the device to be running ICS
Many thanks

Pandilex said:
Basically installed adb/drivers and running this command simply reboots the device normally and it loads back into android.
Power + volume UP does nothing
Power + volume DOWN brings up some text that tries to read something from the SD card, then ends up with the Android robot and an exclamation mark.
Is there a way to get this to boot into bootloader so I can flash a recovery and try to update the version of android higher than 3.1 or a custom rom?
I have seen a few guides but they all expect the device to be running ICS
Many thanks
Click to expand...
Click to collapse
You need to root it then unlock the bootloader first then you can install a custom rom/recovery

Related

[Q] Recovery mode help

Whenever I try to boot into recovery mode (PWR + VOL. DOWN) I get the Android guy with gears turning but then it changes to a triangle with a exclamation mark?
Tried multiple times with SD Card loaded with and without data on it but nothing changes.
Please help as I want to try a new ICS ROM.
wf8sjake said:
Whenever I try to boot into recovery mode (PWR + VOL. DOWN) I get the Android guy with gears turning but then it changes to a triangle with a exclamation mark?
Tried multiple times with SD Card loaded with and without data on it but nothing changes.
Please help as I want to try a new ICS ROM.
Click to expand...
Click to collapse
Have you installed a custom recovery. If so what have you flashed ,where did you get it . and what was the result of the flashing.
Reason i ask the above that is if you flash a stock leaked rom you likely over write cwm . If in fact you had it installed.
Please provide more information as what your running and what you want to get it exactly. This is likely the reason you have not had any replies as of yet.
GOOD LUCK .

[Q] Stuck on Splash screen after updated to 4.0.4

I purchased a used Nexus S i9020T that runs on the Wind network in Canada a little while ago. The phone is unlocked and ran 4.0.3. Today i did a manual check for an update, and it found the 4.0.4 version. I pressed update, and after a few minutes the phone rebooted to the splash screen...and stayed there with the animation running for a good 30 minutes.
I searched around and it seems that i will have to reflash the OS to get it to work. It also seems that my SD card will be wiped in the process. Is there a way to backup my SD before its wiped?
what the phone is installed CWM recovery?
cukdus said:
what the phone is installed CWM recovery?
Click to expand...
Click to collapse
I am not sure. But when i press the power button + volume up it says Lock State - Unlocked. When i try recovery it gives me the android bot with triangle.
pickled_onion said:
I am not sure. But when i press the power button + volume up it says Lock State - Unlocked. When i try recovery it gives me the android bot with triangle.
Click to expand...
Click to collapse
erm... its default recovery
try to install CWM recovery... :good:

"No command" message while accessing Recovery

Hello guys !!
I recently flashed the factory image of Lollipop on my nexus 4, since then, I'm encountering a problem while trying to access my stock recovery, i have a screen with a resting droid and an exclamation point saying "No command", I tried to press power button + volume key up, and then I access to a "Android System Recovery <3e>", but I don't know what it is ....
Any help to understand what's happening will be welcome !
samy3s said:
Hello guys !!
I recently flashed the factory image of Lollipop on my nexus 4, since then, I'm encountering a problem while trying to access my stock recovery, i have a screen with a resting droid and an exclamation point saying "No command", I tried to press power button + volume key up, and then I access to a "Android System Recovery <3e>", but I don't know what it is ....
Any help to understand what's happening will be welcome !
Click to expand...
Click to collapse
The Android System recovery is the stock recovery.Its functionality is quite limited compared to custom recoveries, but still lollipop has added new options there. You are able to get into stock recovery from the dead android screen so you should be fine. If you want more options, flash a custom recovery like twrp.

Yotaphone 2 - another bricked phone after update

Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.

Update to marshmallow failed

I'm stock 5.1.1, unrooted but bootloader unlocked. Tried updating with ota but ran through the stock recovery Android booted and it said update failed. Do i have to relock the bootloader? Again, im NOT rooted.
NexusS4gFreak said:
I'm stock 5.1.1, unrooted but bootloader unlocked. Tried updating with ota but ran through the stock recovery Android booted and it said update failed. Do i have to relock the bootloader? Again, im NOT rooted.
Click to expand...
Click to collapse
Also, when I tried booting into recovery manually, after the bootloader unlocked warning screen came up, it went to what was supposed to be there stck recovery but instead was the dead (lying down) Android with this words "No Command" over him. That's all, no other anything. I Powered off and booted back into Android.
BTW, got the phone second hand....
Download 6.0 and flash in fastboot.
You can also use my thread, but remember, there provided files are for EU version of Moto X Style. If you are using another device, steps will remain the same, but you will need files for your device!
Thread is found here.
NexusS4gFreak said:
Also, when I tried booting into recovery manually, after the bootloader unlocked warning screen came up, it went to what was supposed to be there stck recovery but instead was the dead (lying down) Android with this words "No Command" over him. That's all, no other anything. I Powered off and booted back into Android.
Click to expand...
Click to collapse
The dead Android is stock recovery. Hold the power button then tap the vol + button. That will take you into the recovery menu.
From LenoMoto:
Code:
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Press the Volume Down button to highlight "Recovery mode"
Press the Power button to restart into Recovery mode.
You'll see an image of an Android robot with a red exclamation mark.
While holding down the Power button, press the Volume Up button.

Categories

Resources