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
Been trying it for two days, says no software update available..Does anyone know if this has been pulled back?
When I called AT&T about the update, I was told that the new update was only for selected devices that needed it based on the IMEI. Don't know if true but doesn't sound far fetched. Seems like only certain people have it while others do not.
Ive been trying for weeks with no luck, when i called att the rep told me that i had to wait for the notification from att to show up, going to settings and update software wont work at all. So i was told. I wish we could get some solid information about what happened to our update.
Sent from my Transformer TF101 using xda premium
Yes, unfortunately or fortunately I had the update bugging me for 2 days, back in Nov. I had CWM recovery then, so the update failed, now of course it says that no updates are available. So I am not sure about the IMEI theory as I cannot get it anymore, as I went back to Stock recovery hoping I could do it.
When I was on the Samsung Moment they pushed an OTA update that was only for the first 1000 phones that downloaded it. They were using their customers as beta testers.
Izmir Stinger said:
When I was on the Samsung Moment they pushed an OTA update that was only for the first 1000 phones that downloaded it. They were using their customers as beta testers.
Click to expand...
Click to collapse
Sounds likely, esp with CIQ installed!
I got it about 2 days after getting my phone, then I had to flash back to stock with ODIN to 2.3.5, it now says no update aval. Not sure it's IMEI based...
Were there any noticeable changes anyhow?
If you want 2.3.6 and you can't get the 2.3.6 OTA update, why don't you flash the stock 2.3.6 zip in the Development section using CWM? (posted by silver03wrx).
When we called into Samsung last week about some browser questions (pinch reflow) we also asked about the update. We were informed it was pulled because of issues and to watch for further updates.
Sent from my SAMSUNG-SGH-I727 using XDA App
I received the update on day one...can't tell if there is any actual change in the device...other than the one-click riot methods NOT working. Which is really frustrating. Lesson learned: don't be quick to update.
Sent from my SAMSUNG-SGH-I727 using XDA App
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'm curious if anyone else waits a bit before rooting. Just in case the phone breaks early on and needs to be sent back.
I'm thinking maybe wait 1-2 months?
Am I paranoid, or does everyone else do this too?
.jond said:
I'm curious if anyone else waits a bit before rooting. Just in case the phone breaks early on and needs to be sent back.
I'm thinking maybe wait 1-2 months?
Am I paranoid, or does everyone else do this too?
Click to expand...
Click to collapse
Personally I don't worry about that. I DO wait to give myself time to familiarize myself with how the phone functions and such before rooting so that I know when there is a problem, rather than second guessing.
It is also hard to tell if a Rom/kernel is running better when you have no base line to compare it to.
I rooted my phone almost immediately. I don't like using custom ROMs but I do like using apps and tweaks that require root.
Sent from my Nexus 5 using xda app-developers app
1-2 months??? I didn't even make it 1-2 hours. My phone was unlocked and rooted within 30 minutes of delivery.
I unlocked, installed TWRP, and rooted within 20 minutes of UPS delivering it.
I used to root and start flashing almost immediately. But as the years have passed and I've become more reliant on my phone for work and such, I've started pulling back a bit. I've reached a point where I just get too frustrated with even the slightest bugs so now I immediately unlock the bootloader (to prevent having to do a full factory restore later) and just use the phone as is until a fully stable ROM comes around that I feel comfortable flashing without losing any functionality at all.
This time around I'll probably stay stock with Nova Launcher (once the new 4.4 version is finalized) for another couple months. Time will tell though, I suppose.
.jond said:
I'm curious if anyone else waits a bit before rooting. Just in case the phone breaks early on and needs to be sent back.
I'm thinking maybe wait 1-2 months?
Am I paranoid, or does everyone else do this too?
Click to expand...
Click to collapse
Seeing as I have a Nexus device, with factory images provided directly from Google that will return my phone completely back to stock (except lock the bootloader), I usually don't hesitate to root or flash custom ROMs. The only reasons I haven't unlocked my bootloader yet is because CWM isn't completely stable yet (I don't like TWRP for some reason), and because my brother is debating on a Nexus 5 for his new phone, and I wanted to show him complete stock because he won't be a tinkerer. He'll be using the unmodded, unrooted bare stock image.
I rooted it out of the box yesterday.
Waiting myself. Want to get a feel for this device as is. Maybe later I will root/flash. But for now I am happy as is. No rush.
The important thing is you learn about the phone and how to root it and potential issues before you do it. I'm still waiting for my phone but the first thing I'm going to do is put a custom recovery on and make a nandroid. Then I'll root it as I have apps I like to use that require root. I'm not worried about warranty issues as it's pretty straight forward to put the factory image back on it and relock it.
Also, remember that when you unlock it you'll lose all your data and apps. And you'll need to unlock it to root it.
I booted, took the ota, unlocked the bootloader, installed TWRP and Super SU as soon as the phone was in my grimy hands.
Rooted immediately after taking out of the box .. no point waiting...
I unlocked and rooted before activating. Not really planning on flashing any ROMs, but just wanted it done in case I needed to tweak cpu to increase battery life.
Just until you familiarize with your new device.
Just successfully rooting won't affect the end results when using the stock Rom. Everything should still work the same way but with more options for the user.
I jut waited until next day, but took time to play some games, make calls/texts, web browsing and tested all features. There I learned the battery life, Net speed and stock performance. Everything was the way should be Firmware/Hardware wise:good:. Then, unlocked/rooted/ & flashed its first Rom
and here we are!
I didn't even boot it. I powered it on in download mode, fastboot oem unlocked, flashed twrp and rooted. Then booted for the first time. I only rooted for tibu and adaway. Now just waiting on aokp.
I waited 4 days only and mainly because we have no stable recoveries yet. Twrp is a joke while cwm is not official yet.
caribouxda said:
I waited 4 days only and mainly because we have no stable recoveries yet. Twrp is a joke while cwm is not official yet.
Click to expand...
Click to collapse
I'd say just the opposite, but then I like twrp
You can unroot, so....
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
NevetsDrassel said:
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
Click to expand...
Click to collapse
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Jank4AU said:
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Click to expand...
Click to collapse
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
NevetsDrassel said:
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
Click to expand...
Click to collapse
I don't know how to permanently disable the update, but I'm sure there's a way. As info, I was able to easily fix my phone with the help of this thread posted by @thecubed: http://forum.xda-developers.com/showthread.php?t=2451696. I didn't read it all, but this might be what disables the update.
I'm not rooted. I took the latest update and all is fine. It's google+ fixes and Google wallet support. It actually let me set up tap & pay! I'll have to go somewhere to try it out.
Sent from my LG-D800 using Tapatalk
I got the notification too but figured that it would probably screw things up since I'm rooted and running TWRP so I did a little searching and came across this, http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3 . It's been a few hours since I changed the setting and haven't seen the update notification again although AT&T pushed the update into CACHE/FOTA sometime this morning.
Well scratch that, the notification just came back. I'll try freezing it now.
Well if rooted just use TB to freeze software update. I am also running a mixed partition D80020c. I am on Straight Talk AT&T. Before rooting I tried taking the official OTA of KitKat but for some reason you can't enter an APN type so I couldn't get or send MMS. So I flashed back to the D firmware,rooted,added custom recovery,entered the APN type and then flashed the modified C firmware. You could also use Root Freezer instead of Titanium Backup to freeze