Anyone know how to get rid of the system updates available message. I'm rooted and running FrankenRom, but I'm still getting constant notification about the Nov system update. I created a back up and told it to install, and of course it failed, so I can't just install it. Very annoying as I get a pop up about 5 times a day asking if I want to install now or later, and thats in addition to the stupid notification bar icon.
There's about 20 threads discussing how to modify the build.prop floating around here. I would search for it. I did it and it worked perfectly.
thanks,
I figured it would be as easy as modifing some file or another but I didn't know enough to know how to ask the right question.
psycoreefer said:
Anyone know how to get rid of the system updates available message. I'm rooted and running FrankenRom, but I'm still getting constant notification about the Nov system update. I created a back up and told it to install, and of course it failed, so I can't just install it. Very annoying as I get a pop up about 5 times a day asking if I want to install now or later, and thats in addition to the stupid notification bar icon.
Click to expand...
Click to collapse
It might sound crazy.....but accept the update.
If you are running a modified recovery it will attempt to install the update up to the point where it reboots, then fail because of the altered recovery.
It won't ask you to update again after that.
Related
Update 2: Root was still acting wonky. I was getting multiple requests per app and it wasn't remembering my preference even with the box checked. I tried to allow all but it just wouldn't work at all that way. So I went to update the binaries just to be sure and I had version 3.2 while the latest (and I'm assuming stable) version is only 3.1.1. So if anyone has the problems I did, UPDATE YOUR BINARIES! That fixed everything for me.
Update: I uninstalled the Superuser apk via ES File Explorer, reinstalled it from the Play Store, and just let the phone sit while I was browsing and looking for an answer and when I went back to it Superuser opened and my root was back. I'm not sure if what I did helped but if anyone else has this problem then I can only recommend what I did. If someone can explain what I did wrong or why I lost root, that would still be helpful. If this post needs to be deleted then the mods can do so, I left it in case anyone else runs into this and searches the forums for it.
I have the At&t ion and I managed to get root on ICS on my second try. I was happy about it and decided to start flashing some zips after installing CWM so I deodexed, rebooted, and then flashed one of the status bar tweaks. When I rebooted again Superuser would force close as soon as it opened with the message "Unfortunately Superuser has stopped working". I still have root access in ES File Explorer since I granted it before Superuser stopped working. I cannot however grant any new root permissions since Superuser won't open.
I'm willing to reflash GB and start from scratch again, I'd just like to know what the reason is (was it deodexing? Flashing the zip for the status bar? Or is this just something that can happen?) so I can avoid it the next time. I'm not too excited about having to redownload all my apps for the 3rd time (I was living without root on ICS but decided to go ahead and get it) so if there's a way around it I'd like to find it. Any help is appreciated. I'll try to reply as quickly as possible, thanks guys.
I have a Sprint Samsung Galaxy Note 2 (SPH-L900). I'd like to do the update to MC2 (Currently AMA7). I was rooted but unrooted to get the update. Usually the notification icon would come up as well as a popup letting me know to install it. So far since I unrooted it has come up only once. That's ok though because I just went to Menu > Settings > System Update > Update Samsung Software and there it is all downloaded and ready to install. So I click on "Restart & Install" and it gives me a countdown letting me know that my phone is about to reboot and here is where my issue begins. When the countdown reaches 0 and says Rebooting phone it just sits there with nothing happening. I have let it sit for up to 5 minutes. I had tried to do this process when I was rooted just to see if it would work and the phone rebooted right away, tried to install and then of course error out. So now I am stuck.
1. How long should it take to reboot?
2. Is there a way to manually update to MC2 without using OTA?
3. I am actually happy at AMA7 assuming that MC2 isn't all that special, is there a way to stop the stupid popup and notification icon from showing up?
I have an LG Optimus G Pro (E980). It is rooted and Lokified. However, I am still running a debloated Stock ATT ROM. 4.1.2. Yesterday, AT&T began pushing an Update to my current Value Pack Build, with the message "Software Update is Available". with a request to select the push message to begin the update. Of course, accepting this update will result in my having to use LGFlashtools to reinstall the ATT .TOT file.
I have tried to find the [sys]elements that would kill this message, as accepting it is, ultimately inevitable. A slip of the hand and I am in for a few hours of rebuilding. I have frozen a couple of likely candidates (com.lge-fota something) and com.lge.permission something). While they have not proven to be needed for any of the uses of my phone, neither have they stopped the push message.
Does anyone know what might block this "Update is available" push message?
notifyme said:
I have an LG Optimus G Pro (E980). It is rooted and Lokified. However, I am still running a debloated Stock ATT ROM. 4.1.2. Yesterday, AT&T began pushing an Update to my current Value Pack Build, with the message "Software Update is Available". with a request to select the push message to begin the update. Of course, accepting this update will result in my having to use LGFlashtools to reinstall the ATT .TOT file.
I have tried to find the [sys]elements that would kill this message, as accepting it is, ultimately inevitable. A slip of the hand and I am in for a few hours of rebuilding. I have frozen a couple of likely candidates (com.lge-fota something) and com.lge.permission something). While they have not proven to be needed for any of the uses of my phone, neither have they stopped the push message.
Does anyone know what might block this "Update is available" push message?
Click to expand...
Click to collapse
Just freeze LGApduService 1.0. You're welcome.
jreed3786 said:
Just freeze LGApduService 1.0. You're welcome.
Click to expand...
Click to collapse
Thanks. In my case turned out to be dmclient.receiver. Could be the difference in builds. I see you have E98010P. I am still on E98010K and P was what I was trying to stop...
notifyme said:
Thanks. In my case turned out to be dmclient.receiver. Could be the difference in builds. I see you have E98010P. I am still on E98010K and P was what I was trying to stop...
Click to expand...
Click to collapse
I was WRONG. Apparently it was just freezing SoftwareUpdate 4.1.0. Or maybe both combined. Not sure, buddy! I just did the one I told you and STILL got update notification. When I froze SoftwareUpdate 4.1.0, it didn't come back.
So last night I flashed dottat's RUU (http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643) to update my phone to 4.4.3 stock. Usually when I run the stock rom, I try to get rid of all the verizon bloat garbage using root app delete and root browser. Maybe this time I got a little overzealous, because I most recently deleted two system apps: verizon location app, and the verizon cloud sync app. Before I did this, everything seemed to run fine. But after getting rid of those two, everything went haywire. Every few seconds my phone app would crash and it would give me the message that "unfortunately, com.android.phone has crashed"and the display kept flickering on and off. Also, I keep getting a poppup for an app called Phone: HBPCG Current Country" telling me I have not input my country, and asks me to select one from a blank list. After trying a few things, I went into TWRP to wipe the cache and dalvik. Fortunately, that seems to have cleared up the com.phone process from crashing every 10 seconds or so. But I still keep getting asked to select a country from "HBPCG Current Country". Has anybody experienced this or does anybody know how to stop it, maybe by deleting another service? I can't remember ever seeing a "verizon location reporting" app in 4.4.2 so I figured it was more garbage that verizon added to the ROM as needless bloat, and didn't think it would affect other phone services.
Thanks for any help on this, it's really irritating me. If I can't get it resolved I figure I might have the run the RUU again.
I should probably also mention that after wiping the caches, I got the "android is upgrading" bit when I rebooted and it said it was optimizing 67 apps. I'm not sure what that was for since I didn't flash any updates or anything, but I figure maybe recaching some system info since I ripped out so much system bloatware?
Now that santod released stock 4.4.3 debloated you should just flash that ROM instead. Sounds like less of a headache to just completely wipe and go from there.
BranC85 said:
So last night I flashed dottat's RUU (http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643) to update my phone to 4.4.3 stock. Usually when I run the stock rom, I try to get rid of all the verizon bloat garbage using root app delete and root browser. Maybe this time I got a little overzealous, because I most recently deleted two system apps: verizon location app, and the verizon cloud sync app. Before I did this, everything seemed to run fine. But after getting rid of those two, everything went haywire. Every few seconds my phone app would crash and it would give me the message that "unfortunately, com.android.phone has crashed"and the display kept flickering on and off. Also, I keep getting a poppup for an app called Phone: HBPCG Current Country" telling me I have not input my country, and asks me to select one from a blank list. After trying a few things, I went into TWRP to wipe the cache and dalvik. Fortunately, that seems to have cleared up the com.phone process from crashing every 10 seconds or so. But I still keep getting asked to select a country from "HBPCG Current Country". Has anybody experienced this or does anybody know how to stop it, maybe by deleting another service? I can't remember ever seeing a "verizon location reporting" app in 4.4.2 so I figured it was more garbage that verizon added to the ROM as needless bloat, and didn't think it would affect other phone services.
Thanks for any help on this, it's really irritating me. If I can't get it resolved I figure I might have the run the RUU again.
Click to expand...
Click to collapse
Verizon Location WAS in fact in 4.4.2, and many services of the phone depend on it and won't function without it…
Does anyone know how to keep the system update notification from appearing in Oreo? No system notifications stop it nor does anything that can be done in the Updater app stop it. All searches come back with Nougat results only and seem to be about getting rid of the file if it has been downloaded or with stopping auto-update. I have not downloaded it and stopped auto-update, I just keep hitting later and then disagree to the second prompt immediately after the first is dismissed.
I have a rooted Mate SE on Oreo. I found the same thing. To make it go away I download the updates and apply them. Then I must reinstall TWRP and rerun Magisk to get root back.
I use, https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
To do the updates.
It's quick and painless - done it 5 times now with updates.
Bevnrick said:
I have a rooted Mate SE on Oreo. I found the same thing. To make it go away I download the updates and apply them. Then I must reinstall TWRP and rerun Magisk to get root back.
I use, https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
To do the updates.
It's quick and painless - done it 5 times now with updates.
Click to expand...
Click to collapse
I appreciate the answer, and I had a feeling that just updating might be the only way. That post sure doesn't make it sound "quick and painless" to stay rooted and BL unlocked. I would definitely go through a lot if it were getting P, but I am willing to ignore the update if there is no real functional change.
Froze the EMUI System Update process with Titanium Backup. No notifications on two devices in over 24 hours with a couple of reboots included. I think that was the trick.