Hi guys
I've just recieved the new security update from HTC, but when I try to install it the phone shuts down, and a white triangle with an ! mark and a little droid man standing by it apears and nothing happens. The only way I can turn the phone back off to reboot is by removing the battery.
Have any of you experienced problems with the new OTA?
My phone is rooted, but with stock ROM and nothing other than the stock font has been changed on the phone, so I can see emoji characters.
I've also tried to download the update a few times, to make sure I didn't download a currupt file or something, but it doesn't help either.
Any thoughts?
Thanks in advance.
Edit:
Well I found out that I could boot with CWM Recovery and force install of the OTA from the download folder problem fixed!
hey how can i get this update to download it. im`
s-off rooted but i dont have the stock rom. by updating this update i will lose my root?
can i root back like i did?
I doubt you can get the update when you have a custom ROM.
Related
Hello,
I received a notification that 2.3.4 update available for my phone (Unbranded bought from Amazon.co.uk, I am on o2 and rooted). I tried to download that update and tried install it but it always stuck on startup showing error icon (Exclamation mark and Android green guy logo).
But when I took the battery out and put back in it works… showing old 2.3.3 not the new version.
I factory reset it but still same issue.
Anyone having same issue or solution.
Before anyone start slamming me… I tried to search it but unable to find that particular issue resolution.
Please HELP.
Thanks
raheelqureshi said:
Hello,
I received a notification that 2.3.4 update available for my phone (Unbranded bought from Amazon.co.uk, I am on o2 and rooted). I tried to download that update and tried install it but it always stuck on startup showing error icon (Exclamation mark and Android green guy logo).
But when I took the battery out and put back in it works… showing old 2.3.3 not the new version.
I factory reset it but still same issue.
Anyone having same issue or solution.
Before anyone start slamming me… I tried to search it but unable to find that particular issue resolution.
Please HELP.
Thanks
Click to expand...
Click to collapse
Wrong section.
Make sure you're on stock recovery.
Sorry, I thought this is the right section.
Also can you please explain a little bit more what is stock recovery?
Thanks
MOD can you please move to correct section. Thanks
raheelqureshi said:
...... and rooted). I tried to .......
Click to expand...
Click to collapse
I think this is your problem. You can not install the update if you are rooted.
To the OP:
If you don't mind losing your data (backup with Titanium Backup as a precaution) just flash the 1.45.401.2 RUU - gives you 2.3.4 and then you can just root again and restore your data if you did decide to back it up first
Hey fellows.
So I wanted to try a custom ROM for my SNS, so I rooted it with this guide: http://www.youtube.com/watch?v=xwe4sWH67dk
And since I'm completly green in all this root thing, I didnt manage to get a custom ROM on my device. So I just stayed with stock android and a launcher, and to be fair, I dont need any more than that.
Then the 2.3.6 OTA update came and I wanted to install that, so I hit "Install" and my phone rebooted. Come to the Google logo with the padlock on the button... and frooze (have to remove battery to restart my phone). Nothing I have done can help it, I tryed factory reset, nothing (get stuck on the same screen again)!
So I looked around the SNS topics in here, and frankly, I can't fix it! I read that locking the bootloader would probably help it. So I installed drivers for my device on my computer, and tryed to use this guide http://forum.xda-developers.com/showthread.php?t=875630 since it seemed fairly easy. But I cant make it work.
My phone version number is GRJ22 and my phone lock state is unlocked.
WHAT DO I DO? Remember, I'm completly green, so cut it into small pieces would be nice!
Hope that there is some helpfull sole out there that can help
arNooold said:
Hey fellows.
So I wanted to try a custom ROM for my SNS, so I rooted it with this guide: http://www.youtube.com/watch?v=xwe4sWH67dk
And since I'm completly green in all this root thing, I didnt manage to get a custom ROM on my device. So I just stayed with stock android and a launcher, and to be fair, I dont need any more than that.
Then the 2.3.6 OTA update came and I wanted to install that, so I hit "Install" and my phone rebooted. Come to the Google logo with the padlock on the button... and frooze (have to remove battery to restart my phone). Nothing I have done can help it, I tryed factory reset, nothing (get stuck on the same screen again)!
So I looked around the SNS topics in here, and frankly, I can't fix it! I read that locking the bootloader would probably help it. So I installed drivers for my device on my computer, and tryed to use this guide http://forum.xda-developers.com/showthread.php?t=875630 since it seemed fairly easy. But I cant make it work.
My phone version number is GRJ22 and my phone lock state is unlocked.
WHAT DO I DO? Remember, I'm completly green, so cut it into small pieces would be nice!
Hope that there is some helpfull sole out there that can help
Click to expand...
Click to collapse
I had a similar issue some time ago and I think I can help you. In my case, I had removed some system apps. I removed books and talk, and it couldn't update because the recovery didn't find these apps to update them. Also, if you don't have the stock recovery, but clockwork instead I think it will not work. You can find in the General section of this Nexus S forum links with the official updates zips. Download one of these and then flash it in recovery(stock or clockwork). Copy the zip to the USB storage and in recovery select 'flash update from usb storage' and select the downloaded zip. Personally, I downloaded the GRJ22 and flashed it, so I can have a clean and upgradeable GRJ22. Then I updated using the incorporated update tool from google OTA to GRK39F. It is better to do a factory reset before you flash the zip with the rom. Sorry for the messy explanation hope this helps. GL
Hmm, I downloaded the GRJ22 fitting me device from http://forum.xda-developers.com/showthread.php?t=1063664, placed it on the SDcard and tryed to go to recovery in fastboot, then the same thing happend again :/ (If that was what you meant)
I installed ClockworkMod Recovery through ROM Manager, then I installed the downloaded file on my device. Now I'm running 2.3.6 :O Thanks for the help dude!
Got the official update today, was so excited. did not relise i would have so much trouble with it. first off i didnt relise having a rooted phone even with stock rom meant i could not install it. so i followed a few tutorials on here and installed my original RUU was fine but now after it all working, i downloaded the update and its reboots and comes up with an android phone with a red triangle then reboots. so i googled it and thought it my be recovery problem. so i re unlocked my phone. flashed the original ville_recovery_signed.img. re ran the ruu exe and all went well. downloaded the updated officialy again and still the same error? i have no idea what to do next, any help?
Thanks
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
filmfanatic09 said:
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
Click to expand...
Click to collapse
You cannot be rooted or you must hide root w/ voodoo or super su. Also you must use stock recovery.
the update will not actually fail if you are rooted, although it may report failing.
if it actually fails, you can obviously see it doesnt go through the process, then there is some other factor causing it to fail.
some things that would cause it to fail all together are: non stock recovery, freezing any bloat, removing any bloat, pretty much any modifications to the stock software other than rooting will cause it to fail.
once you have any system deficiencies fixed, use voodoo from the market to protect root and temp unroot before taking the update.
if you cant figure out what you did to the system to fix it, you may want to re-flash using the proper utility for your current system, re-root, protect and temp unroot through voodoo, then try the update again.
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
filmfanatic09 said:
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
Click to expand...
Click to collapse
you can flash the hole system using this http://forum.xda-developers.com/showthread.php?t=2474393 get the 1.33 version to match what you are on or the 1.34 to go right to the version you are trying to upgrade to. either is fine.
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.