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.
Related
Hello everyone.
I am a happy owner of NEXUS S and I wanted to ask if I will ever receive future official updates OTA, has I've unlocked and rooted the same with the superboot MoDaCo (Even used Rom Manager to donwload ClockWorkMod)
Thank You very much
You will receive the update notifications as long as you don't flash a custom rom that has it disabled (which most do). In your current state, you will receive the update but if you choose to accept it, you will lose root and clockwork and will need to re-root again. The best way to update is to wait for a flashable update release on xda where you could update without losing root.
Sent from my Nexus S using XDA App
you will receive the update being rooted long before you would if you were stock and never rooted. when the next OTA comes out, it will be on the forum in the first 3 seconds and you will flash it. but if you were stock you'd be waiting 1 week for the rollout to hit your device.
and you can alwyas go back to stock ROM if you REALLY want to sit there and wait for google to push the update to your phone the official way. otherwise, everybody just manually updates as soon as the link is released.
just ignore the OTA update, as it will usually break the custom ROMs if you try to install them.
wait for the custom ROMs to include the OTA update into their next build
thank You very much for support.
only one question even if it is OT
After manually updated my nexus 2.3.2. to original stock 2.3.3 I've seen that there is an app called BOOK of 0kb that can't be uninstalled. Why? How can I remove it?
that is Google books
it is build in part of the stock ROM
that means it is not using any storage space
thank You very much.
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
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
I haven't really been into screwing with my phone but since they finally fixed that bad update, I might try to at least get new system software.
I am still on VRBLK3, I am rooted and pretty sure I unlocked the bootloader last year but can't remember. However when I try to get into the recovery, I get the Samsung logo and a bit of text at the top and then it just shuts down again. So I'm guessing in this case a full ODIN of a new ROM is going to be necessary or can I have a go with just installing a recovery and trying to update?
And since I am back on VRBLK3, do I have to do incremental updates or can I just go with this latest one or a new ROM?
Thanks!
You have use odin back to stock. You don't have to doil incremental updates as all stock firmware are available online.
Just wondering if I'll be able to take an OTA update from 6.0 to 6.0.1 whenever it is available? I received a message saying a software update was available and when I told it to install it, it rebooted into TWRP, checked the current software for about 3 minutes, then rebooted? Upon looking, I am still on 6.0? I had the system check to see if there was still an update available, but it said there was nothing. Maybe it was just a radio update? I am anxiously awaiting the update so that I may install Xposed. Any input would be greatly appreciated :good:
AT+T US Unlocked
Rooted/S-off
6.0
1.10.502.3
You can't take OTAs with rooted phones and twrp. The OTA looks at the system partition and if anything is changed...it will not install.
You have to either take a backup somebody made with the OTA/stock basically. Flash it via TWRP. Or RUU back to the lastest for your phone. Then, take all OTA updates, then TWRP, Format Data, then SuperSU again, reboot...start/restore phone.
There is no easy way without Dev support/Custom Roms to get latest bases/OTAs right now without wiping/starting over somehow.
This is why having devs creating Roms is really a luxury. Because they already have the proven installer/Rom customized. They will then take OTAs/new bases, roll that into their Rom, and you just do an update/flash, like Viper, and not lose anything, and no need to wipe.
Likely never to happen with this phone since Devs really only work on the Mainline/Flagship M models, like M8/M9/M10 etc...