Related
Help, I rooted my phone and I don't want it installing updates. But I got this notification that it has downloaded a system update and will install it when there's enough power. So I'm going to keep my phone on low until I find a way to prevent it from installing. Any tips guys and gals?
Does anyone know what the update is? The development may like for you to extract it from your phone. Could help in future development.
abjc89 said:
Help, I rooted my phone and I don't want it installing updates. But I got this notification that it has downloaded a system update and will install it when there's enough power. So I'm going to keep my phone on low until I find a way to prevent it from installing. Any tips guys and gals?
Click to expand...
Click to collapse
I just had the same problem to what I did was let it try to install but it can't because u don't have stock recovery.so it will still try but it will freeze and just pull the battery out then turn the phone back on and it will load right into cwm then just restart your system from there and u will be good to go. Its fast and easy
Sent from my SPH-D710 using xda premium
Any way to stop the phone from asking to update?
pbiancardi said:
Any way to stop the phone from asking to update?
Click to expand...
Click to collapse
If I am not mistaken we had an app on our Evo's called FOTa.apk, do a search for it in google and see what they say....I have it on my Xoom and it works fine
I am going to try shfub's method. I think he removed the .zip update file so the phone will have nothing to flash.
I don't know if it is permanent but I clicked on the notification, went to /cache, removed the .zip update file, went back to the notification, asked it to install, had it reboot to recovery and fail, and booted into android. It stopped bugging me and stopped trying to download after that.
Click to expand...
Click to collapse
hmmm, tried that and after a couple days it came back. Anyone got a solution?
abjc89 said:
hmmm, tried that and after a couple days it came back. Anyone got a solution?
Click to expand...
Click to collapse
Do the same thing, except this time, after the failed install, when you are back in Android, type in adb shell or terminal
su
pm disable com.samsung
Alternatively you could freeze System Updates in Titanium.
can someone point me i'm the direction of this thread? i've seen it b4 but haven't been able to find it now. Thanks in advance.
Sent from my SPH-D700 using Tapatalk
Let it install it will fail pop out the battery and it will boot into cwm then just reboot
Sent From My "epic" SPH-D700 via XDA Premium
What Biggie said. The threads you are looking for are in General. As long as you are not fully stock it will fail and probably boot into CWM after popping battery and rebooting. Just hit reboot system.
Sent from my SPH-D700 using XDA App
I have allowed it to fail, let it boot to CWM, but it just keeps coming back. It is quite annoying. Does anybody have a way to stop it?
mikebarr said:
I have allowed it to fail, let it boot to CWM, but it just keeps coming back. It is quite annoying. Does anybody have a way to stop it?
Click to expand...
Click to collapse
Google Fotakill. It is an app you have to put in your system\app directory.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Google Fotakill. It is an app you have to put in your system\app directory.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I tried FOTAKILL, it worked when I was on EC05 to stop the OTA prompt.
But it's not working for me this time. The only thing that stops it for a while is doing like you said. Accepting the update & letting it fail. It came back again one time since then & I did the same thing, this has fixed it for now. But I do still have foatakill installed if that matters.
At least I have a way to stop the prompt for a week or so. I'm just waiting for CleanGB MTD to be updated.
Not sure if it's any help, but according to the Sprint Rep I spoke with, all security updates come from Samsung. If that is true, its very disturbing. I have used the superfreeze and am running a gingerbread based rom already that does NOT have Carrier IQ. I did find the update zip in the system cache and deleted it, but no luck. The update pops up less often though, but still annoying. With that said, Samsung still has access to download files without consent, dispite a root command to freeze updates. Again very disturbing. []
jerm1027 said:
Not sure if it's any help, but according to the Sprint Rep I spoke with, all security updates come from Samsung. If that is true, its very disturbing. I have used the superfreeze and am running a gingerbread based rom already that does NOT have Carrier IQ. I did find the update zip in the system cache and deleted it, but no luck. The update pops up less often though, but still annoying. With that said, Samsung still has access to download files without consent, dispite a root command to freeze updates. Again very disturbing. []
Click to expand...
Click to collapse
Check the op of my thread in general on how to stop the update message for a PERMANENT fix to the update message...
Sent from my CM9'd epic!
I copied this from a thread in development. This works great. Open up an adb shell. Copy/paste this and run it. It modifies the build.prop file to identify your system as 2.3.6, which will stop the update prompts.
Code:
su
remount rw
sed -i 's/SPH-D700-user 2.3.5 GINGERBREAD EI22 release-keys/SPH-D700-user 2.3.6 GINGERBREAD EL30 release-keys/g' /system/build.prop
sed -i 's/sprint\/SPH-D700\/SPH-D700:2.3.5\/GINGERBREAD\/EI22:user\/release-keys/sprint\/SPH-D700\/SPH-D700:2.3.6\/GINGERBREAD\/EL30:user\/release-keys/g' /system/build.prop
remount ro
DaggettBeaver said:
I copied this from a thread in development. This works great. Open up an adb shell. Copy/paste this and run it. It modifies the build.prop file to identify your system as 2.3.6, which will stop the update prompts.
Code:
su
remount rw
sed -i 's/SPH-D700-user 2.3.5 GINGERBREAD EI22 release-keys/SPH-D700-user 2.3.6 GINGERBREAD EL30 release-keys/g' /system/build.prop
sed -i 's/sprint\/SPH-D700\/SPH-D700:2.3.5\/GINGERBREAD\/EI22:user\/release-keys/sprint\/SPH-D700\/SPH-D700:2.3.6\/GINGERBREAD\/EL30:user\/release-keys/g' /system/build.prop
remount ro
Click to expand...
Click to collapse
Yep same method in my thread in general
Sent from my SPH-D700 using Tapatalk
Noooo...your method was in General so it must not be right...only the one from Development should work...LOL.
Sent from my SPH-D700 using XDA App
DeviceManagement.apk
I have an epic 4g on rooted with cwm and cleangb. I have been irritated with the frequent system update messages I have been rec'ing lately. Yes, letting it install and then pulling the battery works fine. But I have also been looking for a way to stop the update service from running in my phone. Here's what I did:
I checked Titanium Backup ( free version ) and found "System Updates" in the list of apps under the backup/restore tab. The list wasn't sorted so I had to scroll and carefully scan each app-name to find it. Then I started to uninstall it, but I cancelled when I was prompted whether or not to uninstall DeviceManagement.apk. Now that I know the apk, I don't need to uninstall, I can rename, right? Then I went to root-explorer and browsed to /system/app. Then I hit the button to mount r/w; then I renamed DeviceManagement.apk to DeviceManagement.apk.bak. Rebooted and checked menu -> settings -> Applications to see if System Updates was running. And it's not.
Hopefully this means no more firmware updates... time will tell
hope this helps someone else out there
-disc-
Why not just edit the build.prop as suggested? Can you still update PRL? I think you will get a network error.
Just a quick update, I'm still getting update notices. So renaming the .apk def did not work.
Re: build.props
I'm totally ignorant on how to do this. Ill re-read this post from the beginning. I must have missed it.
Thanks to all,
Disc
Sent from my SPH-D700 using Tapatalk
discodan7700 said:
Just a quick update, I'm still getting update notices. So renaming the .apk def did not work.
Re: build.props
I'm totally ignorant on how to do this. Ill re-read this post from the beginning. I must have missed it.
Thanks to all,
Disc
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
With something like root explorer you just long press on build.prop , choose edit text, change all EI22 instances to EL30 and all 2.3.5 to 2.3.6, save and exit then reboot.
Why the hell would this annoying pop-up repeatedly come up in the first place... so much for the "users" right to custom ROMS. They always have to sneak some b.s. in to annoy the XDA community. Theres a conspiracy going on at Samsung {-_-}
RealTic said:
Why the hell would this annoying pop-up repeatedly come up in the first place... so much for the "users" right to custom ROMS. They always have to sneak some b.s. in to annoy the XDA community. Theres a conspiracy going on at Samsung {-_-}
Click to expand...
Click to collapse
I think it is because they consider it a security update to remove CIQ.
Sent from my SPH-D700 using xda premium
Hi,
I finally got back to this. As previously stated, renaming devicemanagement.apk didn't do anything regarding the autoupdate notification. I was indeed nolonger able to do a prl or profile update via home-screen -> menu -> settings -> about phone -> updates. Not only that, but, I got a little foolhardy renaming stuff in /system/app when I started getting the update notices. Long story short, I've gone back thru, re-renamed everything back from .bak to .apk with rootexplorer, and I'm still not getting my vmail downloaded to my phone.
Back on track now... as suggested, I used rootexplorer to edit /system/build.prop. only 2 instances needed to be updated. 1 from EI22 to EL30, and one more a few lines down from that, updating 2.3.5 to 2.3.6. Hopefully this will quiet the autoupdate gremlins.
Sent from my SPH-D700 using Tapatalk
Update: rebooted phone, and I still had the update to el30 in my notifications. I suspect that since the update was auto-downloaded pre-updating build.prop that I would continue to get update nags till I did the "go ahead and install update / pull battery" trick one last time.
So I did that one last time hoping that the update will nolonger auto-download since build.prop references the current versions.
Thanks for everyone's help. Hope someone else finds it useful.
-disc-
Sent from my SPH-D700 using Tapatalk
Uh-oh, rebooted my phone today and was greeted with an auto-update nastygram. Ill recheck my build.prop. to see if I missed anything. If not, I think there's an adb method described earlier in this thread. Ill try that and report back.
Sent from my SPH-D700 using Tapatalk
Sending from my phone.
Problem #1: I'm running RandomRom EI22 and I've done every step to prevent the System Update message, however it's still popping up. Definitely made sure I erased the systemupdate apk and everything else. What other methods are there to make it stop being such a nuisance?
Problem #2: I uninstalled regular Swype and installed the beta, ever since the original kept asking for a system update. After installing the beta, it worked fine. Now everytime I try, it keeps saying "Try again".
Volknochi said:
Sending from my phone.
Problem #1: I'm running RandomRom EI22 and I've done every step to prevent the System Update message, however it's still popping up. Definitely made sure I erased the systemupdate apk and everything else. What other methods are there to make it stop being such a nuisance?
Problem #2: I uninstalled regular Swype and installed the beta, ever since the original kept asking for a system update. After installing the beta, it worked fine. Now everytime I try, it keeps saying "Try again".
Click to expand...
Click to collapse
Do a search here on "FOTAKill.apk" - that was the only thing that helped me on both my phone and my wife's - but we are on Froyo so this might not work for you.
With that being said, all of what you tried has been suggested for Froyo users also, but didn't work - so give it a try. Sometimes the search on XDA doesn't seem to work well for me - so what I do is use Google, and in the search terms I type "XDA FOTAKill.apk"
You have to edit your build.prop to say 2.3.6 and EL30 in all places where it says EI22 and 2.3.5. Then reboot.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
You have to edit your build.prop to say 2.3.6 and EL30 in all places where it says EI22 and 2.3.5. Then reboot.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Okay.....so how do I go about doing that?
Volknochi said:
Okay.....so how do I go about doing that?
Click to expand...
Click to collapse
With Root Explorer. Edit build.prop in system directory.
Sent from my SPH-D700 using xda premium
EDIT: I did the trick of allowing it to do an update, then I let it reboot, it goes to the "Triangle !" mode, wiped Dalvik and rebooted, and so far, it hasn't popped up yet.
Now to fix Swype...
Volknochi said:
EDIT: I did the trick of allowing it to do an update, then I let it reboot, it goes to the "Triangle !" mode, wiped Dalvik and rebooted, and so far, it hasn't popped up yet.
Now to fix Swype...
Click to expand...
Click to collapse
It will be back within a week.
Sent from my SPH-D700 using xda premium
If it'll be back within a week, then does that mean that there's no way of getting rid of that update message?
Volknochi said:
If it'll be back within a week, then does that mean that there's no way of getting rid of that update message?
Click to expand...
Click to collapse
I mentioned what has to be done before. Build.prop has to be edited.
Sorry, thought I mentioned that I did. My fault.
Yes, I did edit the build.prop file through Root Explorer, per your advice. Even after I did the final editing (missed a couple), the message still popped up. But, that's when I did the cache clearing and it didn't pop up again upon reboot.
Volknochi said:
Sorry, thought I mentioned that I did. My fault.
Yes, I did edit the build.prop file through Root Explorer, per your advice. Even after I did the final editing (missed a couple), the message still popped up. But, that's when I did the cache clearing and it didn't pop up again upon reboot.
Click to expand...
Click to collapse
Ok, that makes sense because the message was still in your phone's queue.
Sent from my SPH-D700 using xda premium
If you are on a MTD rom, someone in another thread suggested going back to regular swype. You can get the appropo files from the Starsky ROM, this is one of the few MTD roms that uses swype still, and the only files that I found work.
http://forum.xda-developers.com/showthread.php?t=1242335
system/app/swype.apk
system/lib/swypecore.so
I pushed using Root Explorer and got mine working again
The 'Android Update to EL30' is not removed by uninstalling system updates.apk that apk is meant to provision your Epic to Sprint. The Update Notification is caused by the 'Google Framework' Service. There may be ways to fool it, such as the buildprop edit suggested.
Sent from my piece of **** SPH-M910 using xda premium while my CM9 Alpha 4 Epic is resting in my pocket. (Very Handy) it's like having a spare battery but better.
I am getting ready to root my SGS3, and so I went to update the latest PRL and stuff before doing it. When in the system update section, there is no longer an option (that I could find) to turn off Sprint pushed updates. I don't want to lose root or have to re-root every time Sprint pushes out an update.
Does anyone know how to turn it off? Am I just missing something really obvious? On Gingerbread, there was a select box for "allow automatic updating", but I don't see anything like that on ICS 4.0.4. (at least, not the Sprint ROM).
A little help?
You should be fine. On my epic touch, you would get an update notification and then you would have to accept or deny it.
Sent from my SPH-L710 using Tapatalk 2
anyone know how to stop this?
i'm tired of getting this update notification when i know it won't install
FOTAkill. Hasn't been tested on the SGS3 afaik, so use at your own risk. Worked great on the S2, OG EVO, & EVO 3D for me & others. Must be rooted, might not work with odex'ed ROMs.
http://www.4shared.com/android/sPxFH5oh/FOTAKill.html
Sent from my cm_tenderloin using XDA
If you open up Titanium Backup, there's an entry called System Update. I just froze that app. Let's see if that blocks the update.
mercado79 said:
If you open up Titanium Backup, there's an entry called System Update. I just froze that app. Let's see if that blocks the update.
Click to expand...
Click to collapse
Yeah I tried that definitely doesn't work. Neither did freezing the fw app. I also deleted the file that downloaded no luck there either
---------- Post added at 07:00 PM ---------- Previous post was at 06:49 PM ----------
chconser said:
FOTAkill. Hasn't been tested on the SGS3 afaik, so use at your own risk. Worked great on the S2, OG EVO, & EVO 3D for me & others. Must be rooted, might not work with odex'ed ROMs.
http://www.4shared.com/android/sPxFH5oh/FOTAKill.html
Sent from my cm_tenderloin using XDA
Click to expand...
Click to collapse
Damn this didn't work either
knives of ice said:
Yeah I tried that definitely doesn't work. Neither did freezing the fw app. I also deleted the file that downloaded no luck there either
---------- Post added at 07:00 PM ---------- Previous post was at 06:49 PM ----------
Damn this didn't work either
Click to expand...
Click to collapse
Did you try pushing it to system & fixing permissions? Like I said, it's doubtful it will work with an odex'ed ROM.
EDIT: Don't forget to reboot.
Sent from my cm_tenderloin using XDA
Any update on this?
/system/etc/security then rename otacerts.zip to otacerts.zip.bak
Sent from my SPH-L710 using xda app-developers app
knives of ice said:
anyone know how to stop this?
i'm tired of getting this update notification when i know it won't install
Click to expand...
Click to collapse
This works for me, I kept disabling things till I found it and narrowed it down:
1. Install "system tuner" by 3c
2. Go to "Startups"
3. Scroll down to "google services framework" and tap it
4. UNCHECK anything to do with "SystemUpdateService"
update.systemupdateservice$secretcodereceiver
update.systemupdateservice$receiver
update.systemupdateservice
oingo456 said:
This works for me, I kept disabling things till I found it and narrowed it down:
1. Install "system tuner" by 3c
2. Go to "Startups"
3. Scroll down to "google services framework" and tap it
4. UNCHECK anything to do with "SystemUpdateService"
update.systemupdateservice$secretcodereceiver
update.systemupdateservice$receiver
update.systemupdateservice
Click to expand...
Click to collapse
This worked for me as well good find
suppressing upgrade notification prevents phone from sleeping
oingo456 said:
This works for me, I kept disabling things till I found it and narrowed it down:
1. Install "system tuner" by 3c
2. Go to "Startups"
3. Scroll down to "google services framework" and tap it
4. UNCHECK anything to do with "SystemUpdateService"
update.systemupdateservice$secretcodereceiver
update.systemupdateservice$receiver
update.systemupdateservice
Click to expand...
Click to collapse
I changed my mind, my advice causes problems. Although this stops the update notification, it seems to keep the phone from sleeping once you get a notification. So your battery will be OK for a week or so.. and then all of a sudden your phone will not sleep. If you undo the above, then wait a few hours, you will see the update notification pop up. Then you can accept or decline it and your phone will then be back to normal (it won't burn through the battery.)
accept it and it should take you to recovery once you get to recovery it'll ask if you want to install unknown file do not go any further just reboot the phone and the notification will temporarily go away for while
Use rom toolbox to change build.Prop file to current build number. There are 6 or so entries. Reboot....
Sent from my SPH-L710 using Tapatalk 2
jamcar said:
/system/etc/security then rename otacerts.zip to otacerts.zip.bak
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I am trying this
Hope it works
cheers:good:
redbone110 said:
I am trying this
Hope it works
cheers:good:
Click to expand...
Click to collapse
Originally Posted by jamcar View Post
/system/etc/security then rename otacerts.zip to otacerts.zip.bak
cant rename , says because the file system is read-only
nevermind clicked r/w to r/o.hehe then it worked
This will stop it with no problems
Download System tuner then select the startups menu option. Once in the startups sub menu go down to Google services framework and select it, do not un-check it just click on it and go into sub menu. Once your in un-check the update.systemupdateinstalldialog box and that should do it. only un-check that box.
Nothing like reviving an 8 month old thread . Good to know though, I've never tried it that way.
I'm happy to say there is still some life left in this thread! Thanks for the tips, guys.
Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.
My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.
Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.