System recovery not working after android 'update' - Android Q&A, Help & Troubleshooting

Hi everyone!
Im using a Hisense U-980 with android 4.2.1. When i installed the latest system update i immediately had issues with my certificates and the phone was unable to read the SD card anymore, so i tried to do a system recovery. When i booted the phone into recovery mode and selected the 'recovery' option it just showed a pic of an android laying down with a red X on the chest with the words 'NO COMMAND' waited about 2 min later and it booted into normal mode again. I have no idea what this update did or whether its even a real update or not but it screwed up a lot of things and there seems to be no way to get back the previous andorid version. Any tips or suggestions on what i can do to get system recovery working again or am i screwed?
Thanks!

Related

[Q] Not Sure How to Fix Nexus 5

Yesterday I was trying to update my Nexus 5 from 4.4.2 to 4.4.3. It rebooted me into CWM recovery and asked me to install the .zip to update. It finished successfully, but then it asked me something upon rebooting about fixing root that I had not seen before. I clicked "Go Back" but when I did it shut down and now it will not boot android (all I can see if the coloured circles forever) and when I try to enter recovery mode all I can see is an android symbol with its chest open and a red error triangle. So I have no access to android or CWM, and only to fastboot mode. Is my phone bricked or is there a fix?
mrxip1 said:
Yesterday I was trying to update my Nexus 5 from 4.4.2 to 4.4.3. It rebooted me into CWM recovery and asked me to install the .zip to update. It finished successfully, but then it asked me something upon rebooting about fixing root that I had not seen before. I clicked "Go Back" but when I did it shut down and now it will not boot android (all I can see if the coloured circles forever) and when I try to enter recovery mode all I can see is an android symbol with its chest open and a red error triangle. So I have no access to android or CWM, and only to fastboot mode. Is my phone bricked or is there a fix?
Click to expand...
Click to collapse
Don't worry your device is not fully bricked, just soft-bricked. You have two options, since you have access, to fastboot you can reflash a custom recovery and then sideload a custom ROM and flash that in the custom recovery. Or your other option is to use fastboot to flash the stock factory image for Android 4.4.3 for the Nexus 5 which can be found here. Let me know if you still have questions I'll be happy to help you out.

Bricked Asus TF103C

Hi all.
I have an Asus TF103C that had been updated to lollipop that is currently (soft?) Bricked
I've been through pretty much all the threads and tried all of the fixes. Still unable to boot into android. I am unsure what step to take next. I cant apply official firmware updates via SD card nor sideload via ADB
Currently I can get it to boot up to a UEFI BIOS screen(where I can only scroll up and down via volume keys on the first page and nothing else.) or a fast boot screen showing firmware version ( 209.05 just incase its needed.) I can get it back to a droidboot screen, but I still cant flash any system img. If it's important this tablet uses an Intel Z3745.
Just a quick bump. Still only have access to the fastboot screen and recovery. I attempted flashing images again, and while it eventually goes through after breaking the image down into smaller parts, upon reboot I'm stuck at the android screen.
Open to any help what so ever.
It should also be noted that upon flashing via fastboot, after the system image goes through, I get the error " Flash Capsule Failed." And then it reboots to just the android screen.
Mine also bricked
Hi cronus2
Did you manage to solve this problems? I gather from your second post that you managed to get past uefi... I'm still stuck there: how did you do that?
Thanks to anyone who can give me some help here...

Phone boots into Android system recovery

Just got a new phone and rooted it. Then later was prompted that there was a firmware update for the phone. After, installing it, it gave a quick message saying something like the update failed. Then it booted into Android recovery system. Now whatever I do, I can't get out of this tab. I tried the "wipe out/factory reset" option as well but when I restarted the phone it still booted into the Android recovery tab. Anyone got a solution for this? :crying:
Try posting and searching in XDA section for your phone model .

Moto E 1st gen bootloop and no recovery all of the blue?

Hello!
I'm one of the folks who did OTA update on my Motorola Moto E (1st gen) and after that the phone became unusable due to lacking internal space. After that my phone started to restart randomly on daily basis (according to other posts it was caused by almost no free internal memory).
I was so tired of not being able to install apps that I decided to root my phone, I've never done it before but somehow I managed to root it, unlock the bootloader, install twrp, su and then downgraded my phone to 4.4.4, I'm not sure but most likely from there:
https://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
Anyway it's been working perfectly fine but the phone was still reseting itself (which was odd, having over 500 MB of free internal memory). About 4 months passed by and I'm unable to turn on the phone, it's stuck on logo. Pressing power and volume down gives me access to factory and recovery options but factory worked only once and now doesn't work and when I try to do recovery I'm getting red triangle with Android robot on his back.
How do I fix that? Recovery is unusable. I've got https://dl.twrp.me/condor/twrp-2.7.1.0-condor.img, did
HTML:
fastboot boot recovery-twrp.img
but still recovery doesn't work.
Any hints?
[edit]
I managed to install twrp using "fastboot flash recovery recovery-twrp.img", installed latest Linage OS from official thread on our forums, did everything as in: https://www.youtube.com/watch?v=9esNxdH8-eA and I was stuck on loading screen (blue swiping dot along a curved line), but after like 10 minutes the OS finally booted. Not sure what caused my problems, but they seem to be resolved.
[edit 2]
The OS reseted itself right after booting. I guess I might have some hardware issue after all Can I somehow find out what's the state of my internal memory? I think it might be corrupted. Damn.

XT1225 Boot Looping issues, Lost IMEI and No TWRP Recovery

Hello Everyone,
I own a Motorola quark XT1225 64GB indian version. I had earlier rooted it and installed Lineage OS 14.1 (Unofficial) in it. The installation was without any issues and worked for few months then one day i pressed the power button to turn on the phone and it went into a boot loop and nothing would work. i gave it to a repair shop and he installed android 6.0.1 in it and gave me back. But my phone wont connect to WIFI and later i found out that there was no IMEI or any network related information left in it. only the OS booted and nothing else was working. Even the Developer options were not available as for some reason tapping the build number was not giving any result. he refused to fix it. I tried a factory reset from the settings menu with no result. even the recovery was not available any more in the phone. I tried installing new android stock images both for android 5 and 6 first from RSD lite and fast boot mode which kept failing and then i tried it using the command promt. After installation was complete the phone rebooted and android appeared with erasing written under it but then it went into boot loop and would keep restarting every time android appeared. I tried installing TWRP recovery from the command promt the initial image of the recovery appears but then next second it says unable to mount data and keeps rebooting again and again. Kindly suggest ways to fix my OS as well as have my IMEI restored.
Really need help.
Thanks a lot.

Categories

Resources