OTA with Rooted Phones - Galaxy S III Q&A, (US Carriers)

Do we know yet what will happen as far as OTA updates on rooted phones?
Will OTA not even be offered to rooted phones? Will the OTA complete and then phone won't be rooted? Will OTA complete and then phone will still be rooted?
Will OTA Rootkeeper work?
Coming from a Droid X, I know that OTA wouldn't go unless your phone was nearly 100% stock.
Not sure how things working over at Samsung.
I hopefully will finally have my phone next week. With the consideration that I'd like to restore apps and appdata via Titanium, I'm wondering what the best way to proceed would be. Root phone immediately, restore with Titanium, then get the OTA (if it will even run on a rooted phone?)? If I lose root for a short time after that, I could live since I've already restored my data. I'd really like to keep things as close to stock as possible, with the exception of obtaining root.

Related

[Q] Clarification on this new [awful] update: 1.83

Hey guys, sorry to bother everyone with another question about the update but there are a few things I could really use clarification on if it's not too much trouble.'
I'm currently on 1.57, gingerbreak rooted, gladi ROM and sbf flashed the hsupa radio. I can't really find anything about what's done in the update so i can't even tell if it'd be worth it for me to update. Will anything happen if I don't update? I didn't have any problems with my iphone when I skipped over 3 or 4 updates...just want to make sure nothing bad will happen.
Next, if I do want to update (which I don't think I will because I'm reading that a lot of people have been having problems with some things) if there a program I can use to save all of my rooted features and re-apply them after I've updated? I read about beforeupdate and afterupdate but I can't find any information about what they do and if they'll do what I'm looking for.
I'm thinking that with this update being buggy, moto will have to roll out another update pretty soon and maybe I should just wait for that one.
Here you go: Release Notes from Motorola
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
WiredPirate said:
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
Click to expand...
Click to collapse
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
spitefulcheerio said:
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
Click to expand...
Click to collapse
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
EDIT: You cannot use this method btw since you have modded. You have to sbf first.
Dirtburgler said:
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
Click to expand...
Click to collapse
Yeah i know I once I'm updated, I can root again but I've downloaded tons of apps and changed so many settings to get this phone to run exactly how I want. I've spent a good amount of time changing little things here and there and I don't want to lose all of it!
Is there away to retain all of this information through some kind of backup or something? I have all my apps and user data backed up with TiBackup. If I go back to 1.26 and then update to 1.83, can i restore using TiBackup?
im not too keen on titanium backup other than how to use it for the most part lol. The static phone settings will be defaulted to shipping state if you go back to 1.26. there may be a way to do what you are trying but that's out of my league. These is a setting in Titanium to transfer phone settings across Rom's but i've never tried nor have i seen it on the Atrix Forum. (I never really looked for it, didnt need it, so there may be a thread on it.)
The fact that you have Gladiatrix Rom throws a wrench into the whole easy update thing. Check This if you havent already----- http://forum.xda-developers.com/showthread.php?t=1063618
same here i have no problem
WiredPirate said:
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
Click to expand...
Click to collapse
Exactly what I did and everything is working fine. Ran afterupdate after the 1.83 OTA and things are working great~! everything retained

[Q] Thunderbolt stock gingerbread

Quick question(s).
1) What steps do I take to throw my phone to completely stock (Im running bamf 1.6.3) in order to receive the OTA properly?
2) Any new news on when gingerbread is coming out for the tbolt?
I do have a nand of stock root on my phone, so after I restore that (if thats what i should do) how to i remove root so i can get gingerbread OTA correctly?
As for the reason I'm wanting to do this is because I want to try out the stock gingerbread and I don't like to upgrade android without an OTA, once I get sick of it I will be re-rooting it.
markalyea2 said:
Quick question(s).
1) What steps do I take to throw my phone to completely stock (Im running bamf 1.6.3) in order to receive the OTA properly?
2) Any new news on when gingerbread is coming out for the tbolt?
I do have a nand of stock root on my phone, so after I restore that (if thats what i should do) how to i remove root so i can get gingerbread OTA correctly?
As for the reason I'm wanting to do this is because I want to try out the stock gingerbread and I don't like to upgrade android without an OTA, once I get sick of it I will be re-rooting it.
Click to expand...
Click to collapse
Ota won't roll out for a couple weeks. There's a thread to get you back to security on. I think it's in general.
I'm not really sure what is to be gained by un-rooting, doing the ota update, then rooting again. Other than DRM stuff while you are not rooted (google vids, blockbuster, etc).
I'm sure the stock GB ROM with root will be available here before the OTA upgrades start, certainly no later.
Of course it's your preference, I'm just curious.
markalyea2 said:
Quick question(s).
1) What steps do I take to throw my phone to completely stock (Im running bamf 1.6.3) in order to receive the OTA properly?
2) Any new news on when gingerbread is coming out for the tbolt?
I do have a nand of stock root on my phone, so after I restore that (if thats what i should do) how to i remove root so i can get gingerbread OTA correctly?
As for the reason I'm wanting to do this is because I want to try out the stock gingerbread and I don't like to upgrade android without an OTA, once I get sick of it I will be re-rooting it.
Click to expand...
Click to collapse
1) http://forum.xda-developers.com/showthread.php?t=1009423 will get you back to where you're looking to go.
2) ETA on the OTA is all rumor and speculation but the latest rumor and speculation is end of June. I think someone has concrete info from Verizon that said sometime in 2nd qtr but that's a pretty broad spectrum.
*Usually the OTA leaks before it's actually pushed out by Verizon and we get to play with it for awhile before the rest of the world sees it (it shows up in development.) The MR1 is a good example of that...it was a carbon copy of the leak (and the nand root that you have.) I know it's completely your decision but you'll probably be able to run the OTA for awhile before it actually gets pushed out by Verizon if you stay rooted. You just have to wait for the devs to say it's ready to go for rooted phones (which is usually right after th leak hits the light of day.)

Will temp-rooting and debloating prevent the OTA?

I just got a CLNR Rezound with the 1.xxx software--if I temp-root to debloat will the OTA still take, or will it fail? Is there a reason to want the 2.xxx software over the 1.xxx? I'm sure this has been discussed, but I'm still trying to figure the Rezound out. Seems awesome, so far.
1/2
I can confirm that I had removed QUITE a bit of bloat, but the OTA still self-installed on my phone. I was not temp rooted at that moment.
jdmba said:
I can confirm that I had removed QUITE a bit of bloat, but the OTA still self-installed on my phone. I was not temp rooted at that moment.
Click to expand...
Click to collapse
Did it reinstall all the garbage? I'm basically just going to strip everything out.
Seems Ok
tekhna said:
Did it reinstall all the garbage? I'm basically just going to strip everything out.
Click to expand...
Click to collapse
I don't recall 100% of what I removed, but I remember NFL something was one thing, and its still gone. So is VZW Navigator. Seems it did not reinstall those items; but I suspect if it was going to update something you removed, that would come back.
New bloat was installed (e.g., Verizon Location), per other threads.
Rezound OTA
I had used CleanTOOL to debloat and the OTA update would download ok but would not load. I tried it several times. I went back into CleanTOOL and rebloated, and the update loaded just fine the first time, though I had to wait overnight until I could download it again.
Now, of course, I can't temp boot and CleanTOOL no longer works. I hope this OTA update is worth it.
For me the OTA keeps downloading but it doesn't seem to want to install. I have frozen some of the bloated apps using the temp root method. This is the 2nd day in a row where I have caught the phone downloading the firmware update. I'm unsure what I can do to start it because it looks like it just retrys over and over without any success.
Why not just perma root? You can download cons otarom, completely debloat, dont have to worry about the turning off and having to re root? Heck, use TI and you can save all the bloat, and put them back on at anytime if you so desire.
Mitalis said:
For me the OTA keeps downloading but it doesn't seem to want to install. I have frozen some of the bloated apps using the temp root method. This is the 2nd day in a row where I have caught the phone downloading the firmware update. I'm unsure what I can do to start it because it looks like it just retrys over and over without any success.
Click to expand...
Click to collapse
You can do a factory reset and accept the OTA but iirc you cannot temp root again afterwards though, but I believe you can perm root afterwards. But while you are temp rooted you might want to back up your settings and apps with Titanium backup or MyBackup first.
Don't take my word on perm rooting though, search first if you want to perm root. But I believe that since you can unlock the bootloader you can perm root by flashing Amon Ra recovery then installing su with that, but the one-click perm root won't work any more.
I think I had used CleanTool as well, I love my Rezound and really wanted the bloat off. The update downloaded 3 times and then didn't install. I gave up and did the factory reset. Although I hate bloat, really I am happy with Sense and the way the phone itself functions so I didn't feel the need to do a full root.

What exactly prevents an OTA from being accepted?

Hello all,
Just had a quick question. I didn't know what search terms to use to get an accurate answer, since the search seems to pick up any and everything related to any of your search terms. I was wondering what exactly prevents an OTA update from taking. Is it the recovery that is installed? Is it having root? It's been a while since I have accepted an OTA for a device, outside of the Nexus on launch day. I have my Razr Maxx rooted, no custom rom. I tried a few of the ICS leaks but they were in safestrap, my non safe partition remains only rooted. When the OTA actually hits should I be able to accept it fine or will I need to go back to completely stock unrooted?
Things that prevent an OTA: ROMS, Bloatware frozen/uninstalled, custom recoveries (safestrap, bootstrap) so yes, when you want the OTA you'll need to fastboot back to complete stock for it to work. Root won't stop an OTA but OTA's generally break root.
You can try just uninstalling safestrap but I've read cases where just uninstalling it doesn't work and you need to fastboot back to stock.
everything wrong with motorola and Android has to do with idiot upper middle management execs having endless powerpoint presentations babbling corporate gibberish so they can make the next payment on their overpriced overlarge joke of a house and BMW. we are left to sort out the steaming pile of ****. i pray google has the sense to fire every last one of them and give their salaries and bonuses to the engineers!
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
tech_head said:
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
Click to expand...
Click to collapse
What is the difference between freezing and removal, from a technical standpoint? I rooted my Razr using CASUAL and then installed Titanium Backup Pro and have been zapping the Verizon bloatware. I do want the stock ICS when it comes out. I guess I could reinstall the bloatware from backup and then freeze it rather than uninstalling. I don't care so much if the OTA doesn't install, I can troubleshoot that, but I don't want the OTA to brick my phone, that's the main concern.
The main reason I don't want the bloatware on there is that I don't want there to be any danger of clicking on anything that will make my monthly bill go up. Sometimes I let my girlfriend or other people use my Razr and if they manage to get a $10 monthly charge on my bill because they just had to see NFL Mobile or something similar, I'm gonna be pissed
I'm fairly sure it just changes the extension to .apk.bak, but I could be wrong
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Rooted, stock 2.3.6
bpingry said:
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Click to expand...
Click to collapse
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
quarky42 said:
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
Click to expand...
Click to collapse
Apps in preinstall folder are required by OTAs those are the real bloats. Any other system modification will be verified too, like build.prop, init.d CWM and so on..
Remember an OTA update is an incremental update wich will check any required system piece, especially those I've mentioned.
Cheers
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
MarkyG82 said:
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
Click to expand...
Click to collapse
Yes, it's a system modification. You'll need to flash stock rom to flash an OTA update.
When installing an OTA you can press both volume buttons at the same time to to see dialog, and if anything fails you will have filename and directory of failed checks. And it won't auto reboot until you tell it too. I found the problem files for the ics leak from early April leak and was able to install without wiping.
Sent from my DROID RAZR using xda premium
See I'm not fussed about wiping. Id quite happily have stock ICS and mod it from there. Looks like I'll be hacking some way or other to get the official anyhow as I'm on linux. Unless someone can point me to a UK suitable stock rom I can fast boot or add flash from linux. I have add setup if that helps. My system version is 167.26.
Sent from my XT910 using xda premium
cause they arent bronies, duh.
ExtraDan said:
cause they arent bronies, duh.
Click to expand...
Click to collapse
Sorry, I don't understand.
Sent from my XT910 using xda premium
and you wont...
MarkyG82 said:
Sorry, I don't understand.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I don't understand them either, just don't make a big deal about it
Thanks for all the replies. I don't have any bloatware frozen and no system mods done so I guess once the OTA hits, as long as safestrap uninstalled smoothly, I should be good to go. Ill check out ota root keeper here shortly.
Sent from my DROID RAZR using xda premium

Rooted Pixel Experience OTAs

Running latest Pixel Experience w/ root right now and was wondering about OTAs.
When updating, is there anything I need to do with root or can I just run the OTA normally and update?
Last time I ran an OTA update w/ root, my phone would restart randomly sometimes during usage and I couldn't figure out why so I reflashed everything and it hasn't happened since.
Leads me to asking whether updating while still rooted messed with the phone in some way. So yeah, do I need to unroot before running the OTA or do I unroot and then OTA and then reroot?
(Also, if I need to unroot, how do I do that? Have only ever rooted phones, never had to unroot one.)
thevietmonk said:
Running latest Pixel Experience w/ root right now and was wondering about OTAs.
When updating, is there anything I need to do with root or can I just run the OTA normally and update?
Last time I ran an OTA update w/ root, my phone would restart randomly sometimes during usage and I couldn't figure out why so I reflashed everything and it hasn't happened since.
Leads me to asking whether updating while still rooted messed with the phone in some way. So yeah, do I need to unroot before running the OTA or do I unroot and then OTA and then reroot?
(Also, if I need to unroot, how do I do that? Have only ever rooted phones, never had to unroot one.)
Click to expand...
Click to collapse
disable magisk modules, reboot then try.
better to just n download the rom and dirty flash imho

Categories

Resources