I was trying to do the OTA update 2.33.709.6 in Taiwan.
At first, I flash the wrong stock recovery, so got the red exclamation mark screen.
Then, I flash the correct 5.0 stock recovery (thought so, as I was able to reboot my phone properly)
I did the OTA update, and got stock at reboot.
The screen just went black out after the white htc boot screen
I believe there are people having the same issues.
Please let me know how to fix it.
If possible, I would prefer not to flash ROM completely and keep my data.
I'm guess I need to flash the correct recovery and boot from OTA update 2.33.709.6.
Please share it with me if you have it.
Thanks.
I got my phone to work again, but have to lose some data
I relocked it and use flash RUU from SD card.
Basically, almost like factory reset
I did backup some data, but not all
If someone run into the same problem, this is not a perfect solution
Of course, please still share if you have better solutions without losing any data
Related
Long story, but here goes...
About a week ago I turned off my Droid. When I attempted to turn it back on it got stuck at the Motorola logo screen. After a few minutes it would reboot and do the same over and over. I had never rooted or done anything custom to the phone at any point. It was 100% stock original. Nothing had changed recently to suddenly cause an issue, no new apps or anything. I spoke with Verizon about it and they walked me through the process of attempting to boot to the recovery screen. During this call we found that I could not even boot to the recovery screen. I am outside of the warranty and inside of my renewal date.
Since I don't intend to pay for a new one I decided to try to fix it myself. My first attempt was simply to get to a point that I could boot to recovery. I flashed the phone with SPRecovery and sure enough I was able to boot to recovery. I then attempted to flash it with 2.2 and ended up back in the same situation with the boot loop. During all of this I noted that the Bootloader version was 2C.7C.
I then decided to go back to the SPRecovery/rooted configuration and attempted to load a custom ROM from Liquid. This also failed.
My next train of thought was to flash back to an older version of the Droid OS. I chose to flash to VZW_A855_ESD56_QSC6085BP_C_01.3E.01P_SW_UPDATE_03. Low and behold, that worked and the phone booted up and ran fine. It immediately updated to 2.1 update 1. I noticed after this flash that I was on Bootloader version 2C.6C.
Shortly afterwards I was prompted to install the OTA 2.2 update. After accepting and installing I was back to having a bricked phone. This was through the OTA update. Nothing I did or forced.
So basically, I can flash the phone back to VZW_A855_ESD56_QSC6085BP_C_01.3E.01P_SW_UPDATE_03 again and it works fine. But the second it tries to install the 2.2 OTA update or if I attempt to flash to the 2.2 image it gets stuck in the loop.
Notes that may be important:
1. I get the "E:Can't open /cache/recovery/command" error when I am able to get into recovery.
2. I have been sure to wipe data, cache, etc and formatted the SD Card through the phone OS when possible.
3. I use Ubuntu to flash the phone as it seems more stable and easier for my preference (I like Linux commands )
Any help would be greatly appreciated!!
I'm also stock in a bootloop, lost count already...
Hey guys I need to get my phone back to complete stock in order to warranty it. Now I'm fine with flashing the stock rom for the i9020a, what I need some help with is getting back to the stock recovery and re-locking the bootloader.
Currently I'm running CWM so that has to be replaced with the stock recovery, wondering how to go about this,
and I also need to re lock the bootloader so that the lovely little unlocked padlock disappears.
Any help or a link to a guide for would greatly appreciated.
First backup all data you need, sdcard and phone, since you're taking it in for warranty.
Have your stock image ready on the sdcard. Go into recovery and factory reset, format /system and format /boot. Now install the stock full rom.
Reboot the phone and skip through the setup. Now go back into recovery and make sure it is stock now, you'll see an android and exclamation mark. Now reboot again and connect to computer. Now on the computer issue:
fastboot oem lock
Now you should be ready.
Hi folks,
I'm a little kerfluffled if you will by the sheer number of threads - search isn't pointing me to a thread that deals with this - so apologies if this has been answered before.
I originally rooted my phone with towelroot. I kept stock but installed a few things like Xposed, greenify, gravity box, etc... (also i switched to ART some time back).
Once i received the OTA notification, I deactivated greenify and gravity box, then uninstalled them, then "unrooted" the phone using SuperSU. I did forget to reset my "startup animation" but otherwise everything seems fine. The root checker confirms that the phone is no longer rooted. Since i forgot to backup the stock animation i just renamed the .zip and now when i boot the animation just says Android (with a little animation regarding the color of the letters).
I then DLed the update, restarted and approximately 30 ~ 40% of the way through the update screen it freezes up and then i get the little android dude with his belly open and the red error triangle. The text below says "error" but provides no further information. The only way to resolve the issue is to power off the phone and then turn it back on. It goes back into 4.4.4 and works fine but i can't get past that error and have no idea how to tell what the error actually is.
Any suggestions will be appreciated! I would prefer to not have to wipe my phone if at all possible.
You'll must wipe your phone as I am. Then you'll be able to OTA update your phone.
I do exactly like you, but error appears every time in the middle of update process. After wipe everything was fine
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Lokke9191 said:
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Click to expand...
Click to collapse
Since I'm not concerned about root in Lollipop for now - if i can find the original boot animation and "reinstall it" so to speak - will that allow me to use the ota without having to wipe my phone?
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Lokke9191 said:
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Click to expand...
Click to collapse
okay thanks! i'm going to try and find the original boot animation somehow and if that doesn't solve the problem, i'm going to fastboot everything.
Just dont flash userdata, or you'll lose your setup.
Lokke9191 said:
Just dont flash userdata, or you'll lose your setup.
Click to expand...
Click to collapse
thanks mate!
Hi guys! I am stuck with a dilemma if I should format my phone. I am quite aware of the dev tools as an IT student but this is the first time I've experienced this problem:
First I stupidly installed Nexus 5's Ambient Display mod without making a backup of the apk's affected resulting for I guess maybe a coincidence but I cannot install the 5.01 OTA as when I went back to the original recovery, I get the green Android logo and "Error" under.
So I flashed via the flash-all.bat the 5.01 stock firmware from Google but removed the userdata.img as I don't want to lose any of my files. It worked seamlessly. No lags, no crashes, bootloops, nothing.
Now, my problem is I want to get the Ambient Display 5.01 to run again, but this time when I tried installing CWM/TWRP via fastboot, it says okay then when I select recovery, it goes back to the Google logo then it boots normally.
What do you guys think is the problem? Should I re-flash the whole firmware? BTW I was able to root my phone the other day. So I don't know what's up. Any suggestions would be great. Thanks!
Remove the scripts in the ROM that flash stock recovery on boot. Then, fastboot flash the recovery of your choice.
http://forum.xda-developers.com/google-nexus-5/help/flash-recovery-stuck-dead-android-t2978052
Recurrent reboot after applying “cm-13.1.2-ZNH2KAS3P0..." thru stock Cyanogen Recovry
Hi
Yesterday I downloaded cm-13.1.2-ZNH2KAS3P0-bacon-signed-8502142fdc.zip from the Cyanogen website. Copied the same in my Stock Oneplus One file directory
Later I rebooted to recovery and applied update by selecting the package.
these are the exact step I followed (note: I did not wipe or factory reset my handset)
It took some time to apply the updates and ever since it rebooted, its been rebooting again and again
emphasized text
The frequency of reboots is getting higher each hour and I dont find any stimulus for this cause. I am unable to operate my phone normally as it reboots as soon as i try do something.
Kindly help, if anybody knows the solution to such a problem
a termporary or a quick fix is also appreciated
regards,
Shailendra
Boot into recovery-> factory reset
You won't get data ... But it will save you from random reboots.
You can't do much if you don't have unlocked bootloader and TWRP, the stock recovery doesn't let you to do certain actions, if you have unlocked bootloader I would suggest you to download the signed fastboot ROM and flash from fastboot everything but userdata_64G.img and this will keep your data and most likely fix the issue since it will rewrite system.img