Database Users

My device stoped working ... is it bricked ?

hi all
i'm beginner in android, i hardly downloaded rom for my iconia, however.
during installing a program on my Acer iconia tab A500 suddenly stopped working, and i couldnot boot it with (black screen written on it acer + with message on the upper left corner of the screen says : secure boot: image lnx checksum fail!)
i read a little about that
1- i tried power+volume down but not working.
2- tried reset but not working.
3- tried adb but not working, its not in debug mod.
4- tried euu but not working ido not have my UID.( is it written on the ouside package.
5- tried to have my uid through usbdeview but there is no memory for previous thethering
6- tried wipe it to factory without recovery but not working
istill have the same fail message
note:
i had done a full backup previously to this problem with clockworkmod contains boot recovery and...
however
could you please help.!!
thanks in advances

Can you boot into recovery by holding down the volume down button and depressing the power on button?? If you can, once in clockworkmod recovery you need to select the "fix a500 boot/recovery checksums" under the advanced menu. It should have done this first time you booted into recovery to install a rom or when you rooted and installed cwm. Good luck, and once you get it fixed install the latest cwm recovery that is located on tegraowners.com.
Make sure you try volume up and down to get into recovery since it isn't very intuitive on which button is up and which is down.

Sounds like you have CWM loaded which has a tool to fix checksums. You boot to recovery mode using power * volume+ and then in the Advance menus is a item to fix your problem.
TD

I had the same issue a while back. If you do not have CWM installed, you should revert back to a 3.0.1 original ROM. I am not sure if 3.0.1 is required, but the original ROM from acer has a Windows Flash utility, so the tab is flashed using a PC, not the recovery mode from the tab itself.
It was a while back (before this summer), but i can't exactly remember if my tab already had CWM or ROOT.
I know there is/was a thread about reverting to 3.0.1 somewhere on XDA, but i can't seem to find it anymore.

Boot to recovery. Hold vol- and pwr until text appears at the upper left corner of the display.
Can you do that? And get the menu?
Say exactly what you did, with filename. All procedures you did.
We are missing information.

Unable to boot my acer A500 into recovery mode.

Right, so I just rooted my iconia using this method:
http://theunlockr.com/2012/09/17/how-to-root-the-acer-iconia-a500-tablet/
And then I used this method to install CWM Recovery on it:
http://theunlockr.com/2012/09/17/how-to-install-clockworkmod-recovery-on-the-acer-iconia-a500/
However, after I install the recovery image and hit Reboot into recovery, once it loads up to the initial Acer loading screen, the following text appears in the top left-hand corner:
Booting recovery kernel image
Recovery verified failed ...
Then it just stays on that screen until I hold the power button to turn it off.
Can anyone explain what I'm doing wrong? I'm just trying to install randomblame's version of JellyBean
http://forum.xda-developers.com/showthread.php?t=1737205
I'm currently running 4.0.3.
If any more info is needed, please ask. I could really use the help.

same problem exactly
CaptainBlackbeard said:
Right, so I just rooted my iconia using this method:
http://theunlockr.com/2012/09/17/how-to-root-the-acer-iconia-a500-tablet/
And then I used this method to install CWM Recovery on it:
http://theunlockr.com/2012/09/17/how-to-install-clockworkmod-recovery-on-the-acer-iconia-a500/
However, after I install the recovery image and hit Reboot into recovery, once it loads up to the initial Acer loading screen, the following text appears in the top left-hand corner:
Booting recovery kernel image
Recovery verified failed ...
Then it just stays on that screen until I hold the power button to turn it off.
Can anyone explain what I'm doing wrong? I'm just trying to install randomblame's version of JellyBean
http://forum.xda-developers.com/showthread.php?t=1737205
I'm currently running 4.0.3.
If any more info is needed, please ask. I could really use the help.
Click to expand...
Click to collapse
same problem exactly .. can't log into recovery .. can't instal any other rom .. i am stuck with the original rom .. while i already upgraded to 4.3 .. but my WiFi is working 20 cm from the router .. help plsssssssss

CaptainBlackbeard said:
Right, so I just rooted my iconia using this method:
http://theunlockr.com/2012/09/17/how-to-root-the-acer-iconia-a500-tablet/
And then I used this method to install CWM Recovery on it:
http://theunlockr.com/2012/09/17/how-to-install-clockworkmod-recovery-on-the-acer-iconia-a500/
However, after I install the recovery image and hit Reboot into recovery, once it loads up to the initial Acer loading screen, the following text appears in the top left-hand corner:
Booting recovery kernel image
Recovery verified failed ...
Then it just stays on that screen until I hold the power button to turn it off.
Can anyone explain what I'm doing wrong? I'm just trying to install randomblame's version of JellyBean
http://forum.xda-developers.com/showthread.php?t=1737205
I'm currently running 4.0.3.
If any more info is needed, please ask. I could really use the help.
Click to expand...
Click to collapse
ahmed morsy said:
same problem exactly .. can't log into recovery .. can't instal any other rom .. i am stuck with the original rom .. while i already upgraded to 4.3 .. but my WiFi is working 20 cm from the router .. help plsssssssss
Click to expand...
Click to collapse
You cannot root and flash recovery on ICS YOU MUST have the unlocked bootloader Everything you need is here

[Q] Stuck in recovery boot loop...?

While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?

It happened to me once. I pushed the power button for 60 seconds as it supposed to do a kind of battery pull, and it worked.

HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???

Lordificated said:
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Click to expand...
Click to collapse
I've done this twice to my nexus now and I think I found a reliable way to restore to running condition. YMMV
1)Boot the nexus into fastboot (power and both volume keys) when you power up.
2)Attach your usb cable from the PC (or MAC I guess, dont have one to try)
3)start WUG Nexxus Root Toolkit. 'Launch' advanced utilities.
4)Test your fastboot with Quick tools. check the button at Fastboot-Bootloader and click 'List Devices' if the box that pops up is empty then fastboot isn't working (I can't help you there and it must be working to continue).
5)If fastboot shows a device then go to "Boot Temporary" and click 'Custom Recovery'.
6)I selected 'Touch TWRP' but CMW may work as well. This will reboot you into (temp)TWRP and from there you can force a reboot that will reset the 'Recovery' flag that has locked your bootloader.
7)Give it a few minutes (be patient for 5 minutes) and hopefully you reboot to where you were prior to this mess.
Long time lurker and couldn't fix my fails without everyone here.
Thanks to all.
Bill

HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.

zeroedout420 said:
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
Click to expand...
Click to collapse
I guess mine worked because I was still on stock bootloader and adding TWRP was an important key but the 5 minutes seems to be the solution after all the rest.

recovery boot loop:- Is coz, one of your partitions would be facing problems while mounting.. So Wipe the Partition and Format it with Ext-2 file format. and reboot the Mobile. Then it'll stops rebooting.

Do you have a Samsung device?
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.

carltasmania said:
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
Click to expand...
Click to collapse
How do you install cf-autoroot when stuck in a boot loop with samsung galaxy S device if there is no fastboot?

My phone is stuck in bootloop too. It shows Twrp at the starting and then restarts. What am i supposed to do? I need help ASAP please

Phone boots into recovery mode on power on

Hi there,
I have just tried to flash cyanogenmod onto my note 3 and must have done something incorrectly. Now whenever I power on the phone it goes straigt to recovery mode after a 3 line message about seandroid not enforcing. I can also boot the phone into download mode. I am using twrp recovery and whenever I try to flash the cyanogen zip file it fails saying e: unable to mount '/usbstorage'. before I orignally tryed to put cm on I created a backup with twrp and I have restored this, and this is the stage I am at now.
I am really stuck now and need some help please.
Thank you

You installing ROM from an external device, like a OTG drive or something?

LG E610 L5 / Can't flash Cyanogenmod / Phone stuck in boot screen

Hello.
I've got an LG E610 L5 phone which was given to me with some custom-built Android ROM already installed. My wish was to install CyanogenMmod on it so I downloaded the latest release for the device and flashed it; however, after flashing the ROM into the device, the phone's stuck in CyanogenMod's boot screen.
I'll explain what I did:
I downloaded the latest CyanogenMod built for the LG E610 L5 phone from the official website.
I placed the .zip file on my microSD card.
I placed the microSD card inside the phone.
I booted the phone into Recovery Mode (ClockworkMod).
I backuped the previous installation to the SD card (a backup that I now lost, sadly).
After the backup, I wiped/factory reseted the phone from Recovery.
I wiped the cache partition.
I went to "Install .zip file from sdcard," and then "from ext_sdcard."
I selected Cyanogenmod's .zip file from the microSD card and installed it.
After the "Successful install!" message, I rebooted the phone.
And now the phone's stuck in CyanogenMod's boot screen. It's been in that state for maybe one hour already.
Is there a way to prevent this from happening? What steps should I follow to solve this? Should Iprovide any more information? I currently don't have access to anything further than Recovery Mode and I don't know what to do.
Many thanks in advance.
Best regards,
Manuel M.

Mnljndr95 said:
Hello.
I've got an LG E610 L5 phone which was given to me with some custom-built Android ROM already installed. My wish was to install CyanogenMmod on it so I downloaded the latest release for the device and flashed it; however, after flashing the ROM into the device, the phone's stuck in CyanogenMod's boot screen.
I'll explain what I did:
I downloaded the latest CyanogenMod built for the LG E610 L5 phone from the official website.
I placed the .zip file on my microSD card.
I placed the microSD card inside the phone.
I booted the phone into Recovery Mode (ClockworkMod).
I backuped the previous installation to the SD card (a backup that I now lost, sadly).
After the backup, I wiped/factory reseted the phone from Recovery.
I wiped the cache partition.
I went to "Install .zip file from sdcard," and then "from ext_sdcard."
I selected Cyanogenmod's .zip file from the microSD card and installed it.
After the "Successful install!" message, I rebooted the phone.
And now the phone's stuck in CyanogenMod's boot screen. It's been in that state for maybe one hour already.
Is there a way to prevent this from happening? What steps should I follow to solve this? Should Iprovide any more information? I currently don't have access to anything further than Recovery Mode and I don't know what to do.
Many thanks in advance.
Best regards,
Manuel M.
Click to expand...
Click to collapse
Can you enter in recovery mode?

Jonas Cardoso said:
Can you enter in recovery mode?
Click to expand...
Click to collapse
Yes, I can. What I can't do is get past it.
If I select "Reboot system now," the phone restarts and gets stuck in CyanogenMod's boot screen.

Mnljndr95 said:
Yes, I can. What I can't do is get past it.
If I select "Reboot system now," the phone restarts and gets stuck in CyanogenMod's boot screen.
Click to expand...
Click to collapse
install this recovery http://forum.xda-developers.com/opt...overy-twrp-3-0-0-1-l5-e610-e612-e617-t3331127
after make wipe system, data, cache and dalvik.
install and reboot system

Jonas Cardoso said:
install this recovery http://forum.xda-developers.com/opt...overy-twrp-3-0-0-1-l5-e610-e612-e617-t3331127
after make wipe system, data, cache and dalvik.
install and reboot system
Click to expand...
Click to collapse
I didn't get to install that recovery because this other problem arised: now I can't even acess Recovery Mode.
When I try to access Recovery Mode (holding down Home and VolDown + Power), the screen remains off while the button lights (Back and Menu) flash repeatedly.
I tried to access Download Mode (VolUp + Power) to flash a stock ROM via KDZ, but when I try to enter the mode, the screen turns completely white and remains that way.
I also tried to acess Download Mode holding down both Volume buttons after plugging the USB cable into the phone, but I only get a "Windows couldn't recognize the device because it malfunctioned last time" message and the phone's screen won't show "Download mode."
Whenever I turn on the phone normally, I still get the neverending CyanogenMod boot screen.
If I turn off the phone using the Power button, the phone turns itself back on. The only way to turn it off is removing the battery.

is there no tool like the AIO -ToolKit to just override everything for the 610?