So I booted in recovery mod and had this image on the display for almost a second and then disappeared. It happens every time I enter in recovery mode.
Any idea what's up with this?
Normal, pretty sure they all do it, when they boot into recovery they look for update.zip initially and don't find it
Think I've seen it saying "Update not found" or something along those lines, nothing to worry about
Related
Would not use this option! From reading the comments here, sounds like a manual install works.
Had everything working perfectly (rooted, fastboot) and it soft-bricks you to the "red screen of death". From the batch file text that flows by quickly, looks like it was unable to properly download TWRP from the server and messes up the install.
Fastboot still works for me (can successfully upload images), but I'm not sure how to completely recover the device. Any ideas?
Using the recovery image + boot image here (from KFFire Aide creator):
http://forum.xda-developers.com/showpost.php?p=37278819
I can get the Kindle to move past the red screen of death and prompt me for a "would you like to recover this device or reboot" screen. If I choose "full recovery", it processes for a while, then eventually reboots and shows the same screen. The automated recovery process is obviously not working to completion.
Using the recovery image + boot image + bootloader image here (originals):
http://forum.xda-developers.com/showthread.php?t=2128175
They also seem to upload fine, but then the red screen of death returns. If you can successfully upload all three of those, why would that happen? Isn't the Kindle loading each of those in order before moving on to any other files on the device?
i recently flashed my phone with Gapps in order to upgrade to CyanogenMod 11, after that i downloaded an app called Reboot Recovery to boot my android into recovery mode. I didnt boot android up into recovery mode manually due to the irregular booting it has recently (such as boot up then shutdown sequences) after that the screen went black with only 2 words in blue "recovery booting" then shutdown again. I attempted to boot it up with power button but the 2 words appear again and shutdown once more, also tried manually enter recovery mode, that also did not work, and i took off the battery, tried to charge with phone etc....to no avail. Please help.
Flash recovery with Odin and try again
I have been having issues trying to update my rooted zenfone 2 to 40.168. I found out that I am unable to get into recovery since I have been trying to update. I was able to enter recovery mode before during and after I rooted my phone. When I try to enter recovery mode, it does not go to the error android anymore, instead it goes back to fastboot screen. No matter how many times I try to enter recovery mode, the phone just reboots. I have tried unrooting by uninstalling xposed and unrooting through supersu, but this did not change the fact that I can not enter recovery or update ota. The second method I tried was using ADB sideload: once I got to the step to enter the code 'adb sideload file.zip', it did not recognize the command. The third method I tried was clearing the cache with fastboot format cache but it said permission denied. I just recently attempted another method of updating ota while rooted but still no success. In fact I think I made it worse now because my phone has just randomly rebooted three times within about 2 minutes of being on. The last thing I tried before I am getting these random reboots was steps to apply OTA manually.
I followed these steps..
Download the OTA file from here, check under ota update heading [get the latest one ,check the version number]
rename the OTA zip which you download to "MOFD_SDUPDATE" zip[verify with this pic], paste the renamed zip in external memory[not in internal, tried to place in internal but it didnt work]
now power off, Once it is off, hold down the volume up button and hold on to the power button until the phone vibrates. After the vibration stops, release the power button and continue pressing the volume up button until the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command" ,Now here click vol down till you see Recovery mode in top big rectangle box,now click power button,and thats all it will update your phone..
I have nearly lost hope and I am thinking about a full reformat of the device if I can even get to settings and restore to factory without it randomly rebooting again. I did not need the latest update however I wanted it. Hopefully someone here can help me.
UPDATE1:
Somehow the random reboots have stopped while I am typing this. Just fyi.
UPDATE2:
So I tried to flash the prerooted img of 168 to my phone via fastboot but every command I entered, I recieved permission denied. I still continued with every command and after I finished I wanted to reboot normally to see if it changed anything. I ended up getting my phone stuck on asus boot logo screen(or bricked).. I just booted into fastboot again and attempted to enter recovery mode again. Now recovery mode is actually doing 'Installing system update' like I wanted it to before but it didn't till now!.. It is making progress and is about 1/4th complete so I will keep this thread updated.
UPDATE3: SO that did fix it. I guess I had to brick my phone in order to fix my recovery lol. Now I am going to try to root this 168 version. Thanks for no help people I didn't need it anyways
You're welcome, remember we are all at your beck and call 24/7 (we even have a TARDIS to go back in case you need our help and no one is available) Just hold your breath while someone pops back to help you...
Glad you got it up and running again but seriously, you ask for help and fix it yourself in less than 1 1/2 hours... How many people are available to help you in that time, we all have lives too...
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.