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.

[Q] TWRP: "custom recovery" not working anymore, TWRP not starting

Hi there,
I wanted to install latest CM10.1 coming from 0526 yesterday on my Defy+.
Did a backup with TWRP first.
Then the flashing failed, so I wanted to recover from backup.
Phone now is stuck at Motorola M not booting anymore.
When I enter bootloader (vol down) and want to enter "custom recover" he just jumps back to the same menu. TWRP is not starting.
Choosing "stock recovery" is possible, but if I choose a CM10.1 zip file it's not accepted.
RSD Lite does not recognize the phone when it's in the bootloader menu or in the stock recover menu.
Help is very much appreciated, what can I do?
Thanks and best regards.

are edianKa
[Idiot mode=on]
Okay, I found out why I couldn't enter flash mode by using Vol+ when starting.
The phone powered already up when I put in the battery, so I always pushed Vol+ too late.
Pressing Vol+ WHILE inserting the battery did the trick, phone went into flash mode and I could re-flash 2.3.6 sbf using RSD lite.
[Idiot mode=off]
Still not sure why TWRP was messed up just by recovering from a TWRP-made backup...
Best regards

Same situation to me.
I opened Terminal Emulator, gained root access
then type below command to get recovery mode
# reboot recovery

Custom recovery not running
I have a similar issue.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw

Stuck in recovery mode? Please help !!

Hi,
I was on stock bootloader and stock OTA 4.03 ICS rom. I wanted to upgrade to jellybean rom from tegraowners. I am now stuck in recovery mode.
Here are the steps i did.
1) rooted my A500 succesfully
2) With the Blackthunder APX flash tool i flashed in auto mode the Skrilax_CZ V8 bootloader (with multiboot) also succesfully.
3) Then i flashed with ADB.exe the 1.8.1 Touch recovery image that also went well and succesfully flashed it.
4) Booted in recovery mode and wiped data.
5) Went to install from external zip the latest jellybean rom from tegraowners wich is ofcourse on my sd card.
6) It started to formatting my system partition ( i think it was on 7%) and then it suddenly restarts my tab.
Now the only thing i have is power + -VOL is my recover mode and power + +VOL is my other menu i have wich contain the fastboot menu.
From there i am stuck and don't know what else i can do.
I do have my UID number and SBK.
Here is a screenshot of what i have in recovery mode:
Thanks and hopefully someone can help!

You will have to do a "real" data format. And for more help with ROMs from "other" forums you should ask on those "other" forums.
You will find the moderators here do not condone those "other" ROMs.

Perform a real format, then flash a ROM again (you'd better go to Tegraowners.com for more support), but if the problem persists then it may be a bad download, which means you have to download and flash your recovery again. However at TegraOwners you can also find the latest TWRP recovery.

OP2 soft bricked, can't access recovery, not recognized by laptop

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.

JiaYu S3 TWRP loop

Hello,
I am into a TWRP boot loop.
- I can boot into TWRP
- I can update ROMs
- I can update TWRP
- I can connect to the computer and send files using mtp://[usb:001,003]/
- I can Wipe ...
But when I reboot into the system, regardless of the ROM that I use, I get again into recovery
I have read in some posts that from the TWRP command one could try to clear the first sectors of the misc partition
For instance for a Lenovo ZUK Z2 (Plus) in https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14 it is said that this could help
"dd if=/dev/zero of=/dev/block/platform/soc/7464900.sdhci/by-name/misc"
but ... I cannot find the misc partition in /dev from the TWRP shell ("find /dev -name misc") !
Could someone help me with this one ? I would appreciate it a lot !
Regards

Same problem on MadOS 8.1 (MT6752)!
TWRP loop

Just flash old stock 5.1 Android ROM through Flash Tool. Its pretty easy. Then turn it, turn it off and wipe data. restart TWRP, upgrade TWRP and install new Android 8.1 and gapps. Turn the phone on and its finished. You can do recovery now for the next instalation if you want. I am doing this often because I have same problem for several months. Fortunetaly google backup works pretty fine so its not problem with installing apps again. The command you wrote above doesnt work for me.

I'm having the same problem. I was using my phone today, when it started to show wifi problems (couldn't connect); so, I rebooted it and its screen started to blink; when I rebooted it again, it automatically entered into recovery mode (TWRP). After this, the phone didn't boot normally (MadOS Android 8.1) anymore - only TWRP. Even when I try to charge it, it boots into TWRP mode instead of showing the battery animation.
In my attempts to solve the problem, I firstly reinstalled the MadOS 8.1 ROM but it kept booting into TWRP mode. So I flashed an old Android 5.1 ROM I got (connected and uploaded the device successfully with SP Flash Tools) but it also kept booting into TWRP (now an older version from the 5.1 ROM). Then I uptadated the TWRP and the OS again to MadOS 8.1 but the result was the same.
With any other alternative, I came accross this topic and tried the steps described above (practically identical to what I just did), but again I hadn't any positive results.
What else could I do?

Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.

imascara said:
Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.
Click to expand...
Click to collapse
Thanks! With this method, I solved the problem, identical to yours !!