So basically Samsung wants me to update to the new android 12 update (I am already on Android 12 just some fixes that would be implemented). However usually from what I have heard Samsung doesn't push any updates since the phone is rooted and iirc it will actually tell you. And now I am wondering if any other people have this.
Wait you're on Android 12 and rooted? There was a thread somewhere where someone (not me) was asking if the old root method was possible with Android 12 or not. I'm on Android 10 myself.
But to answer your question, rooting doesn't stop the notifications that a new update is available, its just that if you try to take it it'll fail because you're rooted. I forget the verbiage that is used, something like your device can't be trusted or something like that. But rooting doesn't stop the notifications themselves.
Try this if it bothers you. Go to Settings>Apps, select "All" from the dropdown list, then from the three dots on the upper right hand corner, select "Show System Apps". Scroll all the way down to "System Update", select it, hit "Force Stop" then "Disable".
It shouldn't re-enable itself, I leave mine enabled cause I don't mind it, but try that.
RodimusConvoy said:
Wait you're on Android 12 and rooted?
Click to expand...
Click to collapse
Root (Magisk canary) and TWRP (unofficial) are working fine for me on android 12
(and root worked on android 11 too (magisk stable release))
However, since fixing this phone often requires wiping everything, updating magisk canary scares me (it once resulted in a lock screen loop)
Related
Hey all,
I'm running a T-Mobile G1, rooted with JF's newest 1.5 firmware and running just fine. As of last night I started getting notified that my phone had downloaded the new security fix from Google and would like to install it. There is no "Don't install" option that I can find, just "Install Now", "Install Later...", or "More Info". I just have been going to the "More info" option and backing out from there which seems to delay it for a few hours, but it just keeps coming back. Does anyone know if it will be safe to allow it to install (I don't want to try for fear of losing my precious root)? If I can't let it install, does anyone at least know of a way to get it to stop bugging me about it?
Thanks,
Bob
I thought JF's builds blocked OTA Updates...apparently not JF's ROMS are old flash the cyanogen's cupcake! So many goodies inside
That's what I thought too. After telling it off enough times it seems to have given up, so that should fix it for now, just hope that it doesn't come back.
I haven't heard of anyone loosing root from any OTA updates...think about it, it's the same as flashing a new ROM.
It will never go away as long as there's an update though, only when you actually do update. Google is picky like that!
bregant2 said:
Hey all,
I'm running a T-Mobile G1, rooted with JF's newest 1.5 firmware and running just fine. As of last night I started getting notified that my phone had downloaded the new security fix from Google and would like to install it. There is no "Don't install" option that I can find, just "Install Now", "Install Later...", or "More Info". I just have been going to the "More info" option and backing out from there which seems to delay it for a few hours, but it just keeps coming back. Does anyone know if it will be safe to allow it to install (I don't want to try for fear of losing my precious root)? If I can't let it install, does anyone at least know of a way to get it to stop bugging me about it?
Thanks,
Bob
Click to expand...
Click to collapse
To keep the phone from checking for new updates try:
Go to Settings>Security, then scroll to the bottom, click firmware download and tick never. Should do the trick tho I don't know for sure as I haven't ever been prompted.
Then again, you shouldn't be getting OTA updates at all, haha.
lukekirstein said:
I haven't heard of anyone loosing root from any OTA updates...think about it, it's the same as flashing a new ROM.
It will never go away as long as there's an update though, only when you actually do update. Google is picky like that!
Click to expand...
Click to collapse
You lose root because the update replaces the boot image and other images which are the key thing that is needed for root access on your phone.
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Sn0w0nS said:
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Click to expand...
Click to collapse
you can always flash the factory image, whenever you want.
Yes I know. But I would like to know if their is a way to force OTA update. Thanks.
Sn0w0nS said:
Yes I know. But I would like to know if their is a way to force OTA update. Thanks.
Click to expand...
Click to collapse
Once someone snags the OTA url, then you can adb sideload it (I haven't really been paying attention to see if this has happened yet). Until then there isn't much you can do but wait.
Ok thanks
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Sn0w0nS said:
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Click to expand...
Click to collapse
How to sideload OTAs
Where to find OTA files (Still waiting right now for the URLs to get captured for Marshmallow)
boomerbubba said:
How to sideload OTAs
Where to find OTA files (Still waiting right now for the URLs to get captured for Marshmallow)
Click to expand...
Click to collapse
It looks like the URLs have been captured. OP in that thread hasn't been updated, but there are a couple links that seem to be the OTA URLs.
Thanks for all the responses. I allready manually updated using my computer. I couldnt wait for OTA.
Xenosis said:
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Click to expand...
Click to collapse
this appears to have totally screwed my phone as it's now been "restoring data" for over an hour and I received an email saying "congrats on your new android phone".
MichaelChirico said:
this appears to have totally screwed my phone as it's now been "restoring data" for over an hour and I received an email saying "congrats on your new android phone".
Click to expand...
Click to collapse
that had nothing to do with your issue. congrats email happens every time you factory rest your phone, as of now. and you did factory reset it. your hour long restoring data is just that. if you have a weak signal, it can take days as well. or, it could not be doing anything, just sitting there. if so, youd need to factory reset your data again. but its nothing to do with the procedure that you followed. you can always try just rebooting, that might fix it as well.
Xenosis said:
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Click to expand...
Click to collapse
Pulled the old Nexus 6 out of the drawer and the update wasn't showing. Followed your instructions and magic happened. Wanted to post a thanks and confirm working instructions =D
Google doesn't recommend clearing the data on Google services framework
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
While it is not going to brick your phone, it can cause "nuisances on the device" - read more at the link above.
jj14 said:
Google doesn't recommend clearing the data on Google services framework
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
While it is not going to brick your phone, it can cause "nuisances on the device" - read more at the link above.
Click to expand...
Click to collapse
From the link: said:
"Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient."
Click to expand...
Click to collapse
I'm perfectly fine doing a fake factory reset like this to be able to get an update only real factory reset phones get. They need to optimize their OTA release system so folks can actually get updates reliably when they arrive. The way they do it now is just terrible and drives folks to do things like this. I didn't notice any weird side effects either. The difference between side-loading and this is often 1.xGB vs 14-150MB for a download as well as the additional necessary work on a PC. I'm no stranger but it's clearly not easier.
Instead of the OTA system seemingly randomly choosing early adopters, it should be up to the user whether or not they want to chance it. The "Check for Update" button, as a result of this silly system lies/is pointless - why even have it. The only time it's useful is if you're several versions behind and even then you usually just get an update prompt because it's often a factory reset phone.
Xenosis said:
They need to optimize their OTA release system so folks can actually get updates reliably when they arrive. The way they do it now is just terrible and drives folks to do things like this.
Click to expand...
Click to collapse
Amen to that
I think a better way would be to make the update available to everyone on day 1 - but don't push it out to everyone on day 1 - do it in a phased rollout as it is done today. But if an impatient person (like me) wants the update, let me go to the "check for updates" screen and if I click it, push the update to me!
This way, a majority of the folks (that are likely not even aware of new updates being released, and don't care) will get the updates in a phased rollout, while the enthusiasts that are waiting around drooling for a specific fix that will be addressed in the next update can get the update when they want.
jj14 said:
Amen to that
I think a better way would be to make the update available to everyone on day 1 - but don't push it out to everyone on day 1 - do it in a phased rollout as it is done today. But if an impatient person (like me) wants the update, let me go to the "check for updates" screen and if I click it, push the update to me!
This way, a majority of the folks (that are likely not even aware of new updates being released, and don't care) will get the updates in a phased rollout, while the enthusiasts that are waiting around drooling for a specific fix that will be addressed in the next update can get the update when they want.
Click to expand...
Click to collapse
Well said. You'd think they would have figured that out if they cared.
Sn0w0nS said:
Is there anyway to force my nexus 6 to receive the OTA update for android 6?
Click to expand...
Click to collapse
Just sideload the OTA update using wugz
Xenosis said:
I had luck with this procedure but it was for 5.1.1 > 5.1.1 and I knew there was an update available (already got it but the OTA failed and lost it):
1. Go to settings
2. Apps ->All running Apps
3. Next-> Google Framework Service -> Click on it.
4. Clear Cache and data.
5. Tap on Force close.
6. Tap on Disable
7. Switch off mobile.
8. Switch on mobile.
9. Go to Google Framework Service in settings ad said above.
10. Clear data n cache.
11. Enable it.
12. Go to About Phone in settings.
13. Tap on System Update.
14. Tap on Check now.
Click to expand...
Click to collapse
Nexus 6P user is here, find this thread on google search.
March update hadn't reached to my device after 15 days, lazy to connect it to computer and sideload the ota but clearing Google Framework Service's data did the job.
Thanks :good:
how?
How does one go about capturing OTA update download URLs?
simms22 said:
that had nothing to do with your issue. congrats email happens every time you factory rest your phone, as of now. and you did factory reset it. your hour long restoring data is just that. if you have a weak signal, it can take days as well. or, it could not be doing anything, just sitting there. if so, youd need to factory reset your data again. but its nothing to do with the procedure that you followed. you can always try just rebooting, that might fix it as well.
Click to expand...
Click to collapse
Those steps worked just fine for me .
My XT1095 is running the stock 6.0 rom and it's rooted. I keep getting the "Install System Update" nag screen all the time. It won't leave me alone. I don't want to update yet because I read it'll cause problems with root and I'll have to unroot or reroot or whatever and I don't want to mess with it right now. I was hoping that it would get bored of me telling it to go away and leave me alone but it hasn't. It shows up every time I unlock my phone if it's been sitting for more than 10 minutes. It shows up when I'm literally in the process of typing a text message, or when I'm surfing a web page, or when I'm in the middle of doing a dozen other things... like it thinks it's so mightily important that it can interrupt anything I'm doing.
It's version: 24.201.3.en.US. Just a security update from what I read elsewhere. It's not a notification so I can't long-press and force stop it or anything. I read that it's supposed to go away on it's own after a week but it's been quite a bit longer than that now. Any ideas on how to get it to stop nagging me? Or an easy way to apply this without screwing up root?
an actual app is in charge of nagging you to update the system software. I cant remember its name but it is located in system/priv-app, "ccc.motorola.ota" or something like that, cant really remember. You can try either deleting it or disabling it.
What i personally did to prevent this is installing fresh stock system image, updating to latest version AND THEN rooting, so updates wont nag me anymore
billybully said:
an actual app is in charge of nagging you to update the system software. I cant remember its name but it is located in system/priv-app, "ccc.motorola.ota" or something like that, cant really remember. You can try either deleting it or disabling it.
What i personally did to prevent this is installing fresh stock system image, updating to latest version AND THEN rooting, so updates wont nag me anymore
Click to expand...
Click to collapse
I did the same, but when I installed a fresh stock image, this new update wasn't available yet. It only came out recently.
DrvLikHell said:
I did the same, but when I installed a fresh stock image, this new update wasn't available yet. It only came out recently.
Click to expand...
Click to collapse
Take a look at this post:
http://forum.xda-developers.com/showpost.php?p=66479956&postcount=15
This should disable the system update nagging.
desertcat said:
Take a look at this post:
http://forum.xda-developers.com/showpost.php?p=66479956&postcount=15
This should disable the system update nagging.
Click to expand...
Click to collapse
I did that, except the app name on my phone was a bit different. So far no more nagging. Thanks a bunch.
Hello guys and Gals, this will be my first time posting so please bear with me. I have been trying to find the best option to root my Samsung Galaxy Note 3 Sm-n900a for a while now, seems to be one of the harder phones to root... this will be my first time attempting to root a device, so I want to make sure I do everything correctly. I have watched multiple videos and read a lot of threads on the subject but it is hard to find anything that is current and has the proper links to be files needed. if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it, if you do respond to the thread please dumb it down I am still learning terminology. I am determined to get this done come hell or high water. so if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it. Thank you for helping me put a nail in this coffin i I have been trying to do this far too long.
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/note-3-att/general/root-att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
GregJ7 said:
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/no...att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
Click to expand...
Click to collapse
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
XxLightxX said:
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
Click to expand...
Click to collapse
I just ended up stayin on kk rooted on mine. Everytime i goto lolipop i brick it. Its almost a hassle to try. I would odin the kk firmware and use towel root. Install xposed and some root apps. If ures is anything like mine dont debloat it. I debloat lightly. And next reboot get all kinds of spen and other force closes. The note 3 in general seem unstable. But i need to restore m8ne back stock now as its keeps force closing. I will be starting mine over for the 100th time it feels like. Dont let my ramblings discourage you. It is a awsome device and having a lgg5 iphone 5 and a few others my note 3s outer glass is destroyed. Got it like that. I would take the note 3 over the rest if i could get it to run rite more than 2 or 3 days at a time. Ive. Always set all my devices the same way. Debloated them the same but this one is really touchy.... Im on here a lot if u gots any ?s just hollar at me.
If you're still interested in an easy way to root, use Wondershare Dr Phone. It worked for me on stock OC1 and then the just used Flashfire to flash whatever I wanted.
It took me a long time but I have finally gotten things settled down and working adequately on my new 405QA with Android 9, root w/Magisk, etc. I read here <https://www.theandroidsoul.com/lg-v40-update/> and elsewhere there may be an Android 10 coming. While for some that may be great news, for me it isn't. I need to rest and recover from the migration from my old Samsung Note 3 with 4.4.2!
So the question is: how do I 100% avoid any new Android OS updates from being (a) downloaded and (b) installed? In developer options, I have turned OFF "automatic system updates". But I fear this is not enough.
On my old Samsung, rooted with SuperSu, this alone seemed to prevent OS updates. But somehow I wonder if using Magisk and all will make preventing updates a bit different. What is the best way to handle this?
Thanks!
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Android# said:
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Click to expand...
Click to collapse
Thanks. Have not cross-flashed but I have used Magisk debloat to deal with fota and software updater. I feel better/safer now. Cheers