The purpose of this thread is hopefully to stop all the new threads being created because of the two very recent updates (MA6+MB1).
Frequently Asked Questions about OTAs
Question 1: Will I lose root if I update?
Answer 1: Yes, if the update goes through at all. See FAQ #3 and the [GUIDE] for more details.
Question 2: How do I update to XXX if I am rooted? Do I need to unroot and go back to stock?
Answer 2: No, this is a common misconception. There is absolutely NO need to unroot, or even to use apps that feature an "OTA survival mode". What you CAN do is head over to freeza's thread and flash the "firmware/modem/baseband" update zip in recovery, and then either wait for the dev of your ROM to update his base to the latest and greatest--most devs will do this one or two days after an update is released--or flash freeza's simple stock rooted rom (from the link above) of the latest update. You could also flag the stock rooted rom and then your preferred custom rom. This way you get the benefits of the latest update, but the features of your preferred rom.
Question 3: How do I get rid of the update notification?
Answer 2: Now, galaxys3man already beat me to the punch on this one, so I will quote his post as this is the only surefire way to get rid of the update notification, but there are a couple alternatives that may or may not work, should you decide to try them, see the [GUIDE] in the second post.
Question 4: I updated to XXX and now I can't find the PRL Write feature? Help!
Ok, so first head over to digiblur's PRL Write Enabler thread and download the one for your version and then just sideload the app. This feature has been disabled for whatever reason on builds ≥ MA4.
Remember: Root is lost, Root is lost, Root is lost, when you take the official update!
GUIDE: Disable the Update Notification
Surefire #1
This method requires editing the build.prop. For a comprehensive guide on how to do this, please head over to galaxys3man30s {Guide} How to edit build props for noobs.
Open your /system/build.prop file and change all instances of MB1 to MD4.
Inside /system/build.prop
ro.build.id=JZO54K.L710VPBMB1
ro.build.version.incremental=L710VPBMB1
ro.build.description=d2spr-user 4.1.2 JZO54 L710VPBMB1 release-keys
ro.build.fingerprint=samsung/d2spr/d2spr:4.1.2/JZO54K/L710VPBMB1:user/release-keys
ro.build.PDA=L710VPBMB1
ro.build.hidden_ver=L710VPBMB1
NOTE: Its not necessary to change ro.build.id if you don't want to, it will only change what you see under "About Phone" in Settings.
---------------------------------
Surefire #2 (thanks to @rocket321! )
Download the app from this thread
Using a root explorer, move the app downloaded above to /system/app and set the permissions to rw-r--r-- or 644.
Reboot into recovery, wipe cache and dalvik and all will be good.
Ok, as I said, the above are the only SUREFIRE way to get rid of it, but there are three other methods if you are willing to take the risk.
Alternative 1: Download the update (on a stock rom) and allow to fail when it tries to flash in recovery. There have been mixed reports as to the success of this method, some have had the update flash even while on a custom rom and custom recovery, while others couldn't get it to go through even on pure stock-rooted! The point is, even people with the exact same setup had different results, so try this one at your own risk.
Alternative 2: Disable the items in /system related to the update
I quote:
Solution:
Step 1. Delete the update located in /cache/fota/ and then click the update notification prompt to install it, it will instantly fail and the notification will disappear.
Step 2. Disable Otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak
Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/
Step 4. Reboot
FWUpgrade.apk may be the only file you need to disable to prevent future notifications, but I disable all just in case.
Alternative 3: Freeze the Software Update app with a program like TitaniumBackup
1. Open the app
2. Scroll to the "All Apps" list, or similar
3. Select the app by either long-pressing on it or selecting its checkbox
4. Freeze it using the menu that either pops up, or is floating at the top or at the bottom
5. Profit
So those are all the ways I know of, but remember the golden rule: ALWAYS make a Nandroid (aka backup) of your current setup!
And, of course, be careful with whatever you decide to do!!
Disclaimer:
I take NO responsibility for your actions, but I would be glad to help if anything goes wrong.
To the S3 community: I appreciate, and welcome, any suggestions as to what I can add to this FAQ/Guide
Last edited: