This is the newest OTA update...
***Boot into recovery, flash, directly after the update finishes(DO NOT REBOOT YET)--> flash the attached root_update.zip, NOW reboot
This is just for Milestone and Droid, not Milestone XT720 or Motoroi correct?
NorskHelgen said:
This is just for Milestone and Droid, not Milestone XT720 or Motoroi correct?
Click to expand...
Click to collapse
we'll have to wait my friend
snandlal said:
This should update without writing over superuser.apk...rename update.zip and flash from recovery
Click to expand...
Click to collapse
This breaks root, you really should test stuff before release. Now I have to re-root the hard way.
Ya its OTA.
Booo! :/
I updated my [rooted] Droid to the FRG22 build and it totally messed with my phone... I kept getting the "Low Disk Space" notification (despite the fact that I have almost 15 Gigs of memory available) and it was rejecting incoming texts for almost 24 hours before I finally reverted back to my backup of FRG01B. Complete pain in the a$$! I've been getting the System Update message as well... Not touching that until these bugs get squashed. Be careful if you push this update!
for those getting the notifications, im using the BB FRG01B and i got the notification for the update last week but since i am rooted and have spbrecovery
it wont allow the update.zip to be installed, i went to update for the heck of it but it blocks it because you have to go in and allow update.zip before you can apply any updates. so since i let it update but got blocked, the notification went away
try at your own risk
Related
Yesterday I randomly turned on 'Check For Update' on my Milestone XT720 in case 2.2 came out at some point and an update appeared although it did not indicate if it was Froyo. All it said was an update was found, so I downloaded the update and tried to update. Sure enough it failed though so obviously it's not Froyo for the XT720. Does anyone know why my phone keeps trying to update now to something it cannot update too?
It could be the 720MHz update rom.
I've updated manually with RSD Lite, still 2.1 but some interesting improvement in video and other things.
Sent from my Milestone XT720 using Tapatalk
Even if it were the 720MHz update, the update will not work. That's the strange thing. I have deleted the update and redownloaded it twice, and even after going into recovery and trying to update my phone that way it still will not download to my phone. That's why I don't get why I'm being asked to download something that doesn't even seem to be compatible with my XT720.
Hey! How do you delete it???
moto release a soft pack for cpu,i think u got it!
I have a rooted NS4G with custom kernel Matr1x #5. Im currently on 2.3.4 and have not added any roms or updates. I kept recieving the OTA updates every 1/2 hr. im assuming for the 2.3.5. OTA was 22mb.
I was holding off for a while to not to update but finally gave in. I went to install OTA and my phone turned off and look as tho it was going to update my system. I let 15-20mins go by and I was still at a screen where there was a triangle with an exculmation and the android.
I thought it shouldnt take that long to update so I pulled the battery. I rebooted my phone and it still has 2.3.4 as my android version but when I click on system updates it says my system is up to date which is not the case.
If anyone install this OTA how long did it take for the whole process??
How do I fix this is with my system saying its up to date but clearly its not since im on 2.3.4???
I no longer get the notification to install a OTA. I would like to install an OTA instead of doing it manually.
I still want to be able to receive updates OTA when the are released. Im afraid I messed something up
Any assistance would be greatly appreciated
Thanks
http://forum.xda-developers.com/showthread.php?t=1185812
Flash this in clockworkmod it should update u and u keep root.
Sent from my CM7 powered Nexus S 4g using XDA Premium App
Rooted phone + OTA = fail
You need a stock recovery to install an ota....
Sent from my Nexus S 4G using xda premium
I am rooted using the Universal Xoom Root method. I am still running stock, only with SU and apps which require SU. Why can I not accept an OTA update? It seems like the worse that could happen is it overwrite the SU.apk and I need to re-root.
Thanks in advance.
I was wondering about this as well. I am rooted and am running Rogue kernel. I guess I'll just update and see what happens. Worse comes to worse, I will have to re-root.
Seems like the Xoom forums are quiet...did a lot of people abandon the device for the Galaxy Tab 10.1...When previous OTAs happened, the forums were chock full of chatter about to or not to accept the update.
Yeah, I just tried an OTA update and it wouldn't work. Got the Droid with exclamation point. Up + power put me back where I was.
Sent from my Xoom using XDA App
same here. No dice on the update, just stuck at the install screen. On a positive note, the update notifications are gone. Damn those were annoying.
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
place your unrooted backup on, take update and reroot.
if you don't have one, their are some around.
I keep a backup that isn't rooted with all my apps installed, then when update comes, it is real quick to restore, update and reroot ....
jerrycycle said:
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
Click to expand...
Click to collapse
Yeah, diddo here with it not bothering me about OTA updates anymore after trying. It didn't put me in a boot loop, just the pretty droid screaming (exclamation point)
I have a backup from before I rooted, but what the heck, it didn't hurt anything, and I was just playing around.
Thanks for everyone's input.
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
flippingout said:
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
Click to expand...
Click to collapse
Yeah, diddo. Mine started again about three days after I tried to install. I too am looking forward to ICS.
Sent from my Xoom using XDA App
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Tbalon said:
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
try to flash CWM via fastboot then update via a zip file throw cwm.
if not u can get ur phone back to clean stock using adb and then u will receive again the ota and u can try to update again
Tbalon said:
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
It is not necessary to flash in order to get the OTA update again. Instructions to force another OTA update are here (basically: clear data on the Google Service Framework app, this resets the time the phone last checked for an update).
However, I'm facing the same problem and even after re-downloading the 4.1 update on my stock Nexus S, the update still fails. The phone reboots and starts to install the update then shows the dead droid with red exclamation before rebooting to 4.0.4.
I've seen other suggestions to get the device back to stock so I guess that's my next course of action (and likely yours).
Are these instructions appropriate? http://forum.xda-developers.com/showthread.php?t=1785672
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
That is what appears to have happened. I was just confused regarding this and assumed my previous update was to 4.1.
I tried several times to "checkin" and eventually I got the update to 4.1.1 which, unlike the update I did a few days ago,
took longer ( about 10minutes ) to update. I now have 4.1.1 JRO03E , very snappy
Thanks !
No problem, man! Us I9020A's gotta stick together!
Sent from my Nexus S using xda app-developers app
I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse
You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.
I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium
kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse