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
Related
Hello there.
i have a nexus one from vodaphone and im sure you all know (ive only just found out) that the ROM on these devices has a problem installing updates to android and does not recieve OTA updates. i believe this is to do with vodaphone actually releasing these?
any who, i used the superoneclick Root application, worked like a charm.
so then i procede to download gingerbread rom but it does teh whole E: verification error.
so i search the internet a little and come across a post with a person with teh same problem, Fantastic i thought! i follow the steops but am cut at my first hurdle as it says i need to revert from teh Vodaphoen Rom to teh original google shipping rom, the problem is that i cant seem to download it, it never works and i dont know why the D/l is incredibly slow and sometimes never connects. this is from Shipped-roms.com
if any1 could assist me in reverting to the original shipping rom i can do teh rest and update to 2.3.3
Thanks for reading.
Horizon.
Root your phone, then install rom manager recovery. With this, you will be able to flash any rom you want.
SalsaForte said:
Root your phone, then install rom manager recovery. With this, you will be able to flash any rom you want.
Click to expand...
Click to collapse
ive installed the rom manager and installed the cyanogen room, how ever im still on 2.2.1 and the OTA wont update it just downloads then nothing happens. any idea?
Horizonspace said:
ive installed the rom manager and installed the cyanogen room, how ever im still on 2.2.1 and the OTA wont update it just downloads then nothing happens. any idea?
Click to expand...
Click to collapse
The OTA won't update automatically, you have to manually flash it. OTA will auto-update only from official version and authorized version. Anyway, why don't you flash CM7 RC4?
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.
Hi,
I have a htc pro 7 bought in the uk and was running mango running the latest 5.11 bootloader, and i wanted to go to the newtech rom.
I downloaded RUU_Gold7Pro_HTC_Europe_5.11.401.02_Radio_5.71.09.02a_22.51.50.21U_NT_Mango_8107_22L_by_ansar (1)
and
RUU_Gold_7Pro_Europe_5.10.401.03_SLSPL_by_ansar
from the links in the forum and they downloaded completely.
I first powered into bootloader with vol down and then used the ROMUpdateUtility to flash the RUU_Gold_7Pro_Europe_5.10.401.03_SLSPL_by_ansar file which seemed to flash fine, the progress bar completed and phone ended up in the bootloader again.
Then following the instructions i went to the other file but when i ran the update utility this time it found the phone and tried to update but never got past 0% before prompting me that it failed after a 10minish wait.
I was able to pull the battery and turn on back into bootloader mode but when i tried flashing the second file again, it failed. (Should I be reflashing the first again every time too?)
I wondered if the package was faulty and so downloaded 7713_GOLD_USA_CHT_CHS_JPN_KOR(www.dft.so) package of the dft release but the same thing, stalls at 0%.
I am left in bootloader (attached pic) and before trying to go back to stock mango using the zune update would like to know if there is a way to get to (ideally) the intrinsic rom.
Many thanks for your help,
Edit:
Adding that I am using windows 7, will try xp on my old PC as soon as zune software can download....
Also is there a way to get out bootloader mode? as restarting just goes back into the bootloader again...?
Edit 2
Solved!
Solved!
Ok Sorted it in the end, It was my fault, I missed a step.
If anyone else gets this problem (and the error 262 in romutility to go with it) and you are left in bootloader 1.7 its simple.
My first steps were right, first flash RUU_Gold_7Pro_Europe_5.10.401.03_SLSPL_by_ansar
and then you get the bootloader, and you then have the 1.7 bootloader problem, but are NOT yet ready for custom roms!
you must then flash RUU_Gold_HTC_Europe_1.22.401.01_Radio_5.63.09.13_3a_22.36.50.15U_by_ansar
(or similar) which will you give you a 1.22 radio.
From here you can then use the dft tool to get a rspl or hspl as needed, and from there you can then flash a custom rom.
I stupidly didn't realise and thought that the slspl replaced the downgrade, which it doesnt!
Glad I got that cleared up! Am now on the custom rom and all seems good!
Edit:
Exact same symptoms here http://forum.xda-developers.com/showthread.php?t=1318726
Bootloader:SPL - 1.7.2250.0
MID: PC921000
my current Windows Phone 7 Version: 7.0.7392.0
wont appear in zune, wont flash with custom rom, gives error 262.
多谢楼上分享！！！！
So after downloading and trying to install the ota ics update my phone is stuck on the moto splash screen. The update was downloaded successfully and the install was going smoothly up until 30% completed i guess. The normal android update screen disappeared and the 'dead' android appeared, the phone then rebooted and was then stuck on the initial moto splash screen. I was running stock 2.3.6 gb before the install. Pretty lost here as to whats going on with my moto paperweight. I have read the 'noob' thread, downloaded rsd lite, moto drivers, and the fxz to go back to 2.3.5. But am hesitant to pull the trigger on anything as I am far from being sure! Any help would be appreciated!
name_the_if said:
So after downloading and trying to install the ota ics update my phone is stuck on the moto splash screen. The update was downloaded successfully and the install was going smoothly up until 30% completed i guess. The normal android update screen disappeared and the 'dead' android appeared, the phone then rebooted and was then stuck on the initial moto splash screen. I was running stock 2.3.6 gb before the install. Pretty lost here as to whats going on with my moto paperweight. I have read the 'noob' thread, downloaded rsd lite, moto drivers, and the fxz to go back to 2.3.5. But am hesitant to pull the trigger on anything as I am far from being sure! Any help would be appreciated!
Click to expand...
Click to collapse
You need to grab the ota files from the post alteredlikeness posted in the general section, and put it on your sdcard.
Here:
http://forum.xda-developers.com/showthread.php?t=1930634
Then boot into stock recovery, and hit both vol + and vol - button, then from the menu select apply update from sdcard.
The dead android you saw updated your recovery binary, give this a try... if you get errors, then keep track of them, so you can post then here. That way we can better help.
Thank you Jim. I will give this a try and report back any results.
So I have been relying on my trusty Nokia e71 for the past few days as I have been very busy with work and have had no time to work on my Atrix 2. Finally found some time tonight and have successfully updated my phone! I tried Jim's method to install from the SD card but it repeatedly failed; the phone gave errors pertaining to the signature or security? I honestly cant remember as I have been drinking for a while now. I then tried installing from cache and found success after a looooong install. I'm now enjoying ICS on my Atrix 2 thanks to Jim!
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.