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
Related
OK so I've got root but I'm not sure at what point do you lose the ability to receive updates from Asus? Can I flash CWM and still receive updates? Or is it only if you flash custom ROM?
Are you able to flash OC kernal and still get OTA?
Just don't want to lose functionality and updates with this being such a new product.
Thanks guys!
you need stock recovey for the ota updates to work correctly...so if you have cwm, it's best you turn off updates. updadtes will also cause you to break root.
don't worry about missing out on updates though. the devs typically get the updates merged into their custom roms quickly enough (typically 1-2 days). and if you're rooted but stock, typically, those come even sooner. you'll probably miss out on 1/2 to a day or so of "i got the newest update" gloating, but IMO, it's worth it with all the benefits of rooting.
Sent from my Transformer TF101 using Tapatalk
Long-time lurker, this is my first serious post here, so... be gentle
The Hardware: Verizon Galaxy S3 16GB SCH-i535 (Pebble Blue, if you must know )
Where I was: Rooted Stock ICS 4.0.4 (Root66) VRALF2 with OTA blocker to keep it there.
What I did first:
Unblocked OTA updates.
First update 40MB VRALF2 to VRALG7. Updated succeeded but broke root. Restored Root using Voodoo OTA Rootkeeper
Second Update: 62MB VRALG7 to VRALHE. Updated succeeded but broke root again. Got a Custom Padlock screen on bootup that wouldn't go away even if the phone was not rooted before the upgrade. Restored Root using Voodoo OTA Rootkeeper.
Third Update: 400MB VRALHE to VRBLK3. Update FAILED. Repeatedly. Each time, the update would download and reboot into recovery mode to install. It would get about 40% of the way through and the widdle gween andwoid would fall over with a yellow twiangle above him. Then it would reboot back into VRALHE.
Hmmm...
What I did next:
ODIN flashed back to VRALF2 Root66
Took OTA updates.
First succeeded as before, so did the second. To my surprise the third ran to completion. Restored Root using Voodoo OTA Rootkeeper. Still has a custom padlock on boot, but when I unlocked the bootloader it disappeared - either that or the boot screen didn't stay on long enough for it to appear - not sure which.
Anyway, I am now on JB. The last to the party. as usual. Project butter must have worked - the interface feels smoother.
Battery life is a mixed bag. I use Battery Widget Reborn Pro to measure the average time to use 1% of battery life. Under ICS it was 6-9 minutes. On initially installing Jelly Bean, this initially dropped to about 3 minutes. I assumed that this was because of post-upgrade housekeeping, as the CPU was continuously busy (according to Usage Timelines Pro). After leaving it running and on the charger all night long, it settled down. It is now at 10-15 minutes per 1% of battery life - almost double what I was getting before.
OTA blocker supports VRALF2 and VRALG7, but it does NOT support VRALHE or VRBLK3. This is not surprising; the last version is three months old. With no OTA Blocker, I am at the mercy of whatever method Verizon comes up with to bugger up my phone. The OTA blocker folks need to get their fingers out and update the app.
On the other hand, the folks who built Voodoo OTA Rootkeeper (which I originally bought for my Droid X2) are on the ball and they have saved my bacon thus far.
Hope this helps anyone out there in a similar predicament. The usual caveat applies: Before trying anything drastic, BACK UP YOUR DATA!
Finally I would like to recognize two apps that have been very useful to me during this process: I have no interest in either developer or program, just a satisfied customer.
Usage Timelines -- A neat program that tells you how busy your CPU is (Free, full version is $2.49)
EZ Recovery -- on-the-fly recovery flash of CWM, CWM Touch, TWRP, Stock or... just about anything else. (Free, but I sent the dev a few dollars)
If you want to block OTA, and own Titanium Backup you can freeze the process that triggers them. The OTA Blocker that your talking about is not needed.
Hmmmm...
Elite49 said:
If you want to block OTA, and own Titanium Backup you can freeze the process that triggers them. The OTA Blocker that your talking about is not needed.
Click to expand...
Click to collapse
Funny... I had tried blocking processes before using the OTA blocker, and it hadn't worked. Did I miss something? Which processes do I need to freeze?
SDM 1.0
lol smh
I'll be gentle.
Curious. Why would you go through all of that? You know you could have just unlocked the BL, flashed Vzw JB stock zip and then the radios? And be at the same spot? 8 days sooner? Lol
I never understood the allure of wanting to take an OTA. I like the fastest way possible. We all end up with the same product . Never got it
Oh, and sorry about your X2. I had one of those. Horrid device....
Sent from my SCH-I535 using Tapatalk 2
1ManWolfePack said:
I'll be gentle.
Curious. Why would you go through all of that? You know you could have just unlocked the BL, flashed Vzw JB stock zip and then the radios? And be at the same spot? 8 days sooner? Lol
I never understood the allure of wanting to take an OTA. I like the fastest way possible. We all end up with the same product . Never got it
Oh, and sorry about your X2. I had one of those. Horrid device....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I decided to go OTA because... it was there. I wanted to know what the fuss was about. Since I had alreay Odin-flashed a ROM I knew I could, but I had never taken an OTA, and wanted to see how far down that rabbit-hole went.
Had that not taken me where I wanted to go, flashing a JB ROM would have been my next move. The eight-day delay was not an issue - when it comes to updates, I tend to wait until others have taken the arrows in the back.
More than a week later, the phone is rock-solid. Under ICS, I used to have to reboot the phone once or twice a day. This phone has been running for over a week without being rebooted (see screenshot), and is still going like a champ. There are just two problems: The GPS pop-up and the Bluetooth Pop-up... but that is another subject for another thread.
As for the X2, it was a lovely little phone, and I was happy with it. The biggest problem with the phone was the lack of support from Verizon (just like the S3 ) I had to upgrade to keep my unlimited and get to 4G, and that is why I took the S3.
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
Ok I know I'm late in the day;
I bought my Asus transformer very early on and rooted it via the App Backup exploit. I've never unlocked my tablet. I've done a couple of OTA and am now on build 9.4.3.30. When JB came out I didn't update because of problems to start off with and losing Flash. Things have obviously changed now and I'm contemplating the idea of updating to the latest JB version from ASUS via OTA. When I look at the forums there's a lot of posts about problems with people flashing custom ROM's, but I can't find much on how people are getting on with the old rootkeeper method. How are you guys getting on with this method? Is JB worth updating to? Or should I stick to ICS?
My biggest problem with ICS is I'll get random crashes with the Launcher and the desktop shows only the wallpaper, and Google Maps constantly crashes.
Thank you!!!
psjw12 said:
Ok I know I'm late in the day;
I bought my Asus transformer very early on and rooted it via the App Backup exploit. I've never unlocked my tablet. I've done a couple of OTA and am now on build 9.4.3.30. When JB came out I didn't update because of problems to start off with and losing Flash. Things have obviously changed now and I'm contemplating the idea of updating to the latest JB version from ASUS via OTA. When I look at the forums there's a lot of posts about problems with people flashing custom ROM's, but I can't find much on how people are getting on with the old rootkeeper method. How are you guys getting on with this method? Is JB worth updating to? Or should I stick to ICS?
My biggest problem with ICS is I'll get random crashes with the Launcher and the desktop shows only the wallpaper, and Google Maps constantly crashes.
Thank you!!!
Click to expand...
Click to collapse
Do you plan on installing a custom ROM? If so, I would suggest unlocking while on ICS and get your NVFlash files created. I just updated last week from ICS and I would say it's worth it. I have no idea about rooting JB with a stock bootloader or if it's even possible. When the first OTA for JB dropped, it was hit or miss keeping root if you had VooDoo OTA root keeper and used supersu.
Good luck with your choice.
As for your launcher crashes, have you tried an alternate launcher such as apex launcher?
Organized_Chaos said:
As for your launcher crashes, have you tried an alternate launcher such as apex launcher?
Click to expand...
Click to collapse
I've not tried any other launcher. I think there's problem coming from the graphics because after some time of the tablet being on (about 24-48 hours), all 3D applications will crash and the home screen will not draw correctly.
Dredz said:
Do you plan on installing a custom ROM? If so, I would suggest unlocking while on ICS and get your NVFlash files created. I just updated last week from ICS and I would say it's worth it. I have no idea about rooting JB with a stock bootloader or if it's even possible. When the first OTA for JB dropped, it was hit or miss keeping root if you had VooDoo OTA root keeper and used supersu.
Good luck with your choice.
Click to expand...
Click to collapse
I'm planning on sticking to the stock room on JB. So plan is I won't unlock it. I think warranty runs out in May so I'm waiting till then to unlock.
This is my first post on this site, though I have trolled these forums since I got my smartphone. I have learned a lot too!
Currently my phone is a rooted Maxx HD (xt926) running JB 4.1.1. From what I have read on the forums, going to 4.1.2 might break my root and WILL keep me from going back to ICS using a tool I found on this site (Matts tool I think its called). I have decided its not worth the upgrade until someone gets root with a stock JB instead of with ICS then a JB upgrade.
I am glad I caught it in time. The updater started the 4.1.2 download so I turned off wifi and data to stall it. I couldn't cancel the download. I have Titanium Backup and froze Updater 4.1.1. This took my downloading notification away completely. Now if I try to do an update, it says an update is currently downloading, however I have no notification or any sign something is actually downloading, so I think that stopped it.
I am hoping this doesn't mess up future OTA updates should I defrost and try again.
This isn't a question so much as I didn't see a thread that covered stopping OTA notifications with this phone after a search. This procedure seemed to work great so far. This is probably such a simple thing to veteran android users that it probably wasn't posted, or I didn't find the post. I am hoping this will help other noobs. Or if this won't work or breaks something else, hopefully someone will point it out.