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
Related
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 have been anxiously waiting for asus to post the jb firmware (us tf300t). I found it today, but now realize if i flash it manually i lose my root, backed up with voodoo and superSU or not. I then was reading about this dlpkgfile thing. Am i understanding this correctly?
It is the file that gets downloaded from asus when you check for an OTA, or when an OTA is pushed to your device
It then reboots, and uses the file to update the device.
It does not make u lose root?
So theoretically, I should be able to put it in /cache/directory and then`reboot my tab and it should start updating right? I know i need to make sure i get US version, backup root, etc. But will this work how I am thinking it will?
Oh and, I am not sure why my ota failed in the first place, i think i might have uninstalled a system app by accident without thinking. I am just plain rooted stock, NOT unlocked. I had also run the firmware for ics from asus website yesterday to get all the stock stuff back on my tab, then rerooted, and am waiting for JB update now
I have been searching on the forum and Google but no answer. I had a Sprint Galaxy S3 and it was rooted with custom recovery Clockworkmod. After an update was available I could not install the update, failing with the message "verification failed" when trying to apply the official update file. I couldn't find an answer so I went back to stock recovery.
Now I have a verizon S3 and I would like to back up an image of my phone with clockworkmod but I would like to be able to update, especially with the looming jellybean update coming soon. Did I miss a way to install the updates to the official rom with clockworkmod? Or was it simply not possible.
moreisbetter said:
I have been searching on the forum and Google but no answer. I had a Sprint Galaxy S3 and it was rooted with custom recovery Clockworkmod. After an update was available I could not install the update, failing with the message "verification failed" when trying to apply the official update file. I couldn't find an answer so I went back to stock recovery.
Now I have a verizon S3 and I would like to back up an image of my phone with clockworkmod but I would like to be able to update, especially with the looming jellybean update coming soon. Did I miss a way to install the updates to the official rom with clockworkmod? Or was it simply not possible.
Click to expand...
Click to collapse
With most custom Roms...being able to do OTA updates is blocked because it could interfere with the rooted Rom you are running...its more or less a safety feature for that purpose. If you want to get the new Jelly Bean OTA update, you will have to flash your device back to unrooted stock and it should work just fine...as long as ur rooted, you wont be able to, if im not mistaken.
Thats true, and there is the whole bootloader thing! Now that we have all hacked away our bootloaders, the OTA just won't happen. Hopefully an easy relock becomes available for the vzws3 before that update is released, but I wouldn't panic - big red will probably release it to us after everyone else has gotten it and out phones are outdated! In general though, within a week or two of an official large release, the amazing devs on this site will have a downloadable version available for us to manually install.
If you have modded your phone, never try to take a OTA update. At the least you will lose root abilities. At the worst, potential bricking of your device.
Usually before, lol, if not just after a OTA, the devs have working release for our devices.
Take it easy, relax.
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
AvataroftheSun said:
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Click to expand...
Click to collapse
I had to Odin back to stock and go get a new SIM card from Verizon... Got the OTA instantly after the new sim was put in... It's a known issue
Sent from my SCH-I535 using xda app-developers app
annoyingduck said:
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Click to expand...
Click to collapse
Mm, checked those out, and scrosler says that the bootloader needs to be unlocked, and doesn't provide any other information on how to flash it properly (Odin vs. custom recovery). Though if it's stock, it shouldn't matter...
I odin'd back to root66 and it took the update as soon as i checked for it. (and I dont even live in Verizon coverage)