I am unrooted and trying to find a way to keep from getting this notification. It downloaded
on its own-didnt do that with 2 previous updates. do i have to just keep ignoring it?
I have searched forums and net to no avail. btw, update and/or root not an option either.
thx for any ideas.
r, john
jb40 said:
I am unrooted and trying to find a way to keep from getting this notification. It downloaded
on its own-didnt do that with 2 previous updates. do i have to just keep ignoring it?
I have searched forums and net to no avail. btw, update and/or root not an option either.
thx for any ideas.
r, john
Click to expand...
Click to collapse
Not sure what version you're running, but you should be able to go to Setting, Applications (Applications Manager) whatever you have.
Find Samsung Update, stop it and uncheck notifications.
Sorry, I thought it was assumed. Im on ver 4.1.2
Also, the update comes from att. Greyed out in
App manager. Now what?
jb40 said:
Sorry, I thought it was assumed. Im on ver 4.1.2
Also, the update comes from att. Greyed out in
App manager. Now what?
Click to expand...
Click to collapse
With root not an option, not too sure....
I have ideas....
I'm really not sure if download has really been completed. You should have been prompted multiple times to accept the update, and the download.
Same goes for installing it, it requires multiple prompts and you must say continue.
So, the download gets saved in the /cache directory. If I'm right, and I should be, you should be able to power your phone down,
Then boot into stock recovery and clear cache which will delete the downloaded cache update file.
Boot into stock recovery (HOLD VOL UP+HOME+POWER)
Picture of stock recovery
http://galaxys2root.com/wp-content/uploads/2011/10/att-galaxys2-unroot-11-690x404.jpg
You want to choose wipe cache partition.
Then when you boot back up, race over to Settings, Applications again and stop the update service. I'd leave notifications turned on for now just to watch what the update process is attempting.
The dl started on its own. Finished too I would bet. Tried killing dl by reboot.
No joy.att must really want us to have this-I had to fetch the 2 previous updates
As I mentioned. Now I have cont/pp dialogue every 8 hrs. Process for notification is
Com.wssyncmldm -afraid to use stock recovery- I dontknow that it wont goof up
Something else-and my cache directory shows empty. (Using es explorer)
jb40 said:
The dl started on its own. Finished too I would bet. Tried killing dl by reboot.
No joy.att must really want us to have this-I had to fetch the 2 previous updates
As I mentioned. Now I have cont/pp dialogue every 8 hrs. Process for notification is
Com.wssyncmldm -afraid to use stock recovery- I dontknow that it wont goof up
Something else-and my cache directory shows empty. (Using es explorer)
Click to expand...
Click to collapse
You have to be root to really see what's in /cache.
Stock recovery really is harmless, for the most part. If you choose data/factory reset all of your installed apps (ones that you have downloaded and installed) are torched and your settings, like Google account info, mail setup etc.
Cleaning out /cache is a good thing.
Maybe someone else will stop by and have another suggestion, but since you said root is not an option, I can't think of another way right now to stop it from bugging.
Well, i suspected there was nothing i could do without root. something simple. the greyed out att update process
along with the attempt to force feed the update to me speaks volumes. to me. I've seen way too much of things i
don't like with this 4.3 silliness(improve my hardware, ok). they're going to have to do better than bug me every
8 hours to get me to install it....
thanks for the suggestions,
r, john
jb40 said:
Well, i suspected there was nothing i could do without root. something simple. the greyed out att update process
along with the attempt to force feed the update to me speaks volumes. to me. I've seen way too much of things i
don't like with this 4.3 silliness(improve my hardware, ok). they're going to have to do better than bug me every
8 hours to get me to install it....
thanks for the suggestions,
r, john
Click to expand...
Click to collapse
You are wise to avoid that locked down bootloader with Knox...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Related
Currently 35% downloaded. Is there any way to cancel the install phase? I was not prompted and cannot stop the download. I hope others aren't next, I tried various tricks when I first rooted to break my communication with the OTA update but obviously that didn't work.
Evil-Eye said:
Currently 35% downloaded. Is there any way to cancel the install phase? I was not prompted and cannot stop the download. I hope others aren't next, I tried various tricks when I first rooted to break my communication with the OTA update but obviously that didn't work.
Click to expand...
Click to collapse
Probably too late now 20 minutes later, but you could always pull the battery. That will buy you a little time. Then you could fastboot boot the recovery from the dev forum, access your phone with adb, and delete the update application apks from the system.
Quick uodate, I was able to postpone the update with the remind me later option I was given. Luckily it asked me at some point but my issue is still there, how do I get rid of this uodate pest? Renamint the ota-certs.zip file isn't enough because I did that a while ago.
I will try that when I get home. Is this system updates apk something I can get to from root explorer? I would love to end while I'm still at work.
Thanks Mills! I used Titanium backup to back the system-update.apk to my SD and then removed it from internal. The option to update disappeared in Settings. I out it back just to make sure I fixed it, the update option reappeared so I removed it again and now it's over. Thanks so much for helping me in the clutch. Felt like my phone had a bomb strapped to it. Oh and in Titanium I deleted the app data just to be safe and remove that update. Hopefully this info gets around so no one else is surprised.
Evil-Eye said:
Thanks Mills! I used Titanium backup to back the system-update.apk to my SD and then removed it from internal. The option to update disappeared in Settings. I out it back just to make sure I fixed it, the update option reappeared so I removed it again and now it's over. Thanks so much for helping me in the clutch. Felt like my phone had a bomb strapped to it. Oh and in Titanium I deleted the app data just to be safe and remove that update. Hopefully this info gets around so no one else is surprised.
Click to expand...
Click to collapse
Looks like I was wrong, the phone updated while I was busy at work and is now not turning on. With my lady at home expecting anytime I was in a catch 22, do I turn the phone off and try and help it's safety or do I do what apears to have worked. Well I had faith in what I did and now have to revert back to a crapberry. I'm calling Verizon out on this one, there is no good excuse for me to HAVE to had updated and it shouldn't be a complex procedure to say no to any updates.
Mobile Care is the app to delete or freeze on a R800x to prevent ota updating.
Thanks a MILLION for that tip markcyst. I unbricked my phone so now I will be deleting "mobile care".
how did you unbrick your phone !!! please help
This worked for me.
http://forum.xda-developers.com/showthread.php?t=1126354
nick4nick said:
how did you unbrick your phone !!! please help
Click to expand...
Click to collapse
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.
Please see the 'generic' Note 3 CF-Auto-Root thread here:
http://forum.xda-developers.com/showthread.php?t=2466423
This actual thread will become a proper CF-Auto-Root thread once I'm finished tying up all the lose ends. Please comment in this thread, but read the instructions and grab the file from the thread linked above.
--- reserved #1 ---
--- reserved #2 ---
Thanks
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
FIX looks like it was on googles servers. Back to normal but this is on stock after I odin, Ill wait on the root to see if others are still getting problems.
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
Click to expand...
Click to collapse
I was getting the above error too even after performing a device reset. I reflashed the root a second time and it is working. The only difference is I enabled USB debugging in the Developer options the second time, not sure if that really made a difference though.
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
Click to expand...
Click to collapse
Me too I p m chain fire like 15 min ago. It could be a Google issue
Sent from my SM-N900T using Tapatalk 4
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
Click to expand...
Click to collapse
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
XooLoo said:
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
Click to expand...
Click to collapse
Thanks I will give it a try
Edit: it worked Thanks a million
Sent from my SM-N900T using Tapatalk 4
Ah wow, I was getting these errors too. Thought it was unrelated and a server side issue (still might be, account specific?)
I'm writing this without reading the suggestions above but, what eventually worked for me (after removing accounts, factory reset, clearing play store data & play framework whether necessary or not)..
Went to Google dashboard (all on PC), made sure device was there, went to play.google.com (computer)-- it errored and froze, logged out, back in, worked eventually, viewed my installed apps (took like 5 minutes to load), started installing apps from there. Once that was working, it worked on my device.
The curious part was, initially, when I'd search for ANY app on play.google.com, it would show no results. Opening in incognito (not signed in), it worked fine.
XooLoo said:
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
Click to expand...
Click to collapse
Yes, had the same problem on my SM-N900T, not on either of the other two [N900/A], it took creating a new google account and also clearing the cache for google services framework, google play and uninstalling the play store update. I had to do this a couple of times, seemed to work better for me without a reboot, but this is the right path for fixing this problem.
Hope this helps,
Bob
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
bob_beringer said:
Yes, had the same problem on my SM-N900T, not on either of the other two [N900/A], it took creating a new google account and also clearing the cache for google services framework, google play and uninstalling the play store update. I had to do this a couple of times, seemed to work better for me without a reboot, but this is the right path for fixing this problem.
Hope this helps,
Bob
Click to expand...
Click to collapse
I just force stopped play store and cleared data and it worked after that.
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
How do we se our Knox status and also....does it do anything to the phone when its like that? Should we wait for a method of root that doesnt trip knox
bdorr1105 said:
How do we se our Knox status and also....
Click to expand...
Click to collapse
go to download mode .
unlockingsky said:
go to download mode .
Click to expand...
Click to collapse
If you have both Kies and Android SDK installed, go to command prompt (cmd) and go to where adb.exe is, and type:
adb reboot download
---------- Post added at 11:43 PM ---------- Previous post was at 11:43 PM ----------
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
Mine is 0x1
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
it changes it. what does knox do for the normal user? i
transitoyspace said:
it changes it. what does knox do for the normal user? i
Click to expand...
Click to collapse
None, basically it detects flash so that they can void your warranty.
zoth said:
None, basically it detects flash so that they can void your warranty.
Click to expand...
Click to collapse
it voids your samsung warranty to be exact. if you take it back to tmobile with tmobile warranty, they will still fix/replace hardware issues.
About to root for the simple fact I can not stand the headphones auto adjusting. I need it louder then normal and tired of playing music at maxed settings just to hear music and then a few songs later it acts like its supposed to. (work in a factory)
Anywho: Does this method still give you the option of having auto updates from Tmobile for bug fixes and stuff or do we need to manually keep an eye open for updates?
(coming from Rooted Stock Note 2 thats why im asking. Not big on romming)
Thank you
Are you on AT&T, rooted with CWM or TWRP recovery, and don't want to update to the new, currently un-rootable ROM, or take the chance that AT&T will push the FOTA update to your phone and attempt to install it without your knowledge? Here's one way to block it:
1. Download Autorun Manager from the Play Store.
2. Run Autorun Manager, give it SU privileges, and enter its Recommended Advanced Mode.
3. Go to Settings, check both "Show system entries" and "Enable system app disable", and return to the list of apps.
4. Scroll down to "Google Services Framework" and open it.
5. Scroll down the list until you see "com.android.gsf.update.SystemUpdateService$Receiver" (mine was at the bottom of the list). Uncheck this to Disable it.
6. Exit Autorun Manager.
That's it. FOTA updates are now blocked.
This info is available in various places here on XDA, and other places on the web. I'm just reposting it here for those that don't want to be bothered with the problems that can be caused by AT&T's pissy little update.
visionlogic said:
Are you on AT&T, rooted with CWM or TWRP recovery, and don't want to update to the new, currently un-rootable ROM, or take the chance that AT&T will push the FOTA update to your phone and attempt to install it without your knowledge? Here's one way to block it:
1. Download Autorun Manager from the Play Store.
2. Run Autorun Manager, give it SU privileges, and enter its Recommended Advanced Mode.
3. Go to Settings, check both "Show system entries" and "Enable system app disable", and return to the list of apps.
4. Scroll down to "Google Services Framework" and open it.
5. Scroll down the list until you see "com.android.gsf.update.SystemUpdateService$Receiver" (mine was at the bottom of the list). Uncheck this to Disable it.
6. Exit Autorun Manager.
That's it. FOTA updates are now blocked.
This info is available in various places here on XDA, and other places on the web. I'm just reposting it here for those that don't want to be bothered with the problems that can be caused by AT&T's pissy little update.
Click to expand...
Click to collapse
F#$K man. This is great...
I have been hit three times in a row by the latest little update from AT&T, and have each time ended with CWM Recovery loop. This is so effing wrong !! I have a post here on how to get out of the recovery loop
http://forum.xda-developers.com/showthread.php?t=2603454&page=7 post #70.
EDIT: This did not completely remove the painful notification and for somereasoon I could not delete the downloaded in "/system/cache". So I applied the update, then used adb to recover from the CWM loop and delete the Fota.img, rebooted. Then I also installed the FOTAkill.apk app here
http://forum.xda-developers.com/showthread.php?t=2249350
Now the update is dead !!
chappatti said:
F#$K man. This is great...
I have been hit three times in a row by the latest little update from AT&T, and have each time ended with CWM Recovery loop. This is so effing wrong !! I have a post here on how to get out of the recovery loop
http://forum.xda-developers.com/showthread.php?t=2603454&page=7 post #70.
Click to expand...
Click to collapse
Damn right it's WRONG! Deliberately borking folks that don't follow the master's rules. Especially those folks that have had the update pushed and automatically attempted install without their consent. Pure crap!
chappatti said:
EDIT: This did not completely remove the painful notification and for somereasoon I could not delete the downloaded in "/system/cache". So I applied the update, then used adb to recover from the CWM loop and delete the Fota.img, rebooted. Then I also installed the FOTAkill.apk app here
http://forum.xda-developers.com/showthread.php?t=2249350
Now the update is dead !!
Click to expand...
Click to collapse
Good! Whatever works for you. My own experience with Android has been that a given "cure" will not necessarily work for everyone. As for the method I mentioned above I've gone 72+ hours without any data transfer related to the update. So far, so good.
Official OTA's aren't pushed out to those using an unlocked AT&T version on other carriers right?
Update FYI - 10 days now since making the adjustment in the OP and still no indication of my phone attempting any update.
Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
UPDATE: DO NOT install the update if you don't have stock recovery. You will end up in a boot loop.
Sent from my LG-D851 using XDA Free mobile app
Lol I just created a thread myself! I am rooted and custom rom so I am totally waiting.
i just got it too, it said android update but I'm not entirely sure what it's for
InsaneJester17 said:
Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I also did, I am on sky rom and it probably won't work, but I don't want to try to install it.
Well its quite a small update at 154 mb
Installed update
Hey guys I just installed the update and it broke my root :cyclops:
Were you able to root again?
Apparently it's D85110m update. So it's updating from D85110c to m. The person that I saw that updated hadn't rooted so no clue on the rooting thing.
Count me in the group with system update notification. I got rid of it by installing xposed module GravityBox, going under status bar settings - ongoing notification blocker - Google Play services (picture looks like that of update) - reboot.
I don't know what other notifications this may block, but for now, it gets rid of that. Also of note, I would NOT take the OTA. Usually it breaks root and/or bootloops you.
HELP
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?
zcgofaster said:
Were you able to root again?
Click to expand...
Click to collapse
I haven't tried to re-root yet. I was rooted with stump root earlier. Stump root doesn't work again because it thinks that my phone is already rooted. I'm going to do some light battery tests before trying to root again, this time with purple drake.
Maybe i might restore the slimkat alpha and hide there until this gets sorted out
I decided not to update to fear my bootloader/root so I tried to extract this with file manager and kept crashing. I can only post the name of the file but above users are correct contains 10m from 10c hopefully devs can find out exactly what's in the update. b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip
thiefinthenight said:
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?
Click to expand...
Click to collapse
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667
Wonder if i could do a restore and keep wifi off so it won't download
hawkstwelve said:
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667
Click to expand...
Click to collapse
Will this reset the phone? Will I lose all data?
thiefinthenight said:
Will this reset the phone? Will I lose all data?
Click to expand...
Click to collapse
I believe so yes. But if you are truly bootlooping, I don't believe you have many (if any) other choices than wiping clean and starting fresh.
I'm all stock so I upgraded.
It is in fact D85110m
I've only had it up and running for a few minutes and I already noticed two things.
- There is a slider feature added to the lock screen to instantly open the camera.
- I didn't think the phone was sluggish or laggy out of the box but I immediately could tell it runs smoother now with transitions between screens/apps. e.g. There used to be a bit of lag when opening the Recent Apps. Not anymore.
We'll see how it goes.
The IR blaster works better for me now. I guess the update made it more powerful somehow.
if you have twrp installed or have modified /system you should not take this OTA. if on twrp things will get weird(as evidenced above..) and if removing/modding any default files in /system the zip will most likely fail.. as it checks for all original files first before the OTA update gets patched in.
as for the twrp issue.. I can only assume that it's due to the update/phone expecting stock recovery... and not getting it. there are flags set in the phone that tell the phone what mode to boot into... since you dont have stock recovery the phone is confused. check out this thread - http://forum.xda-developers.com/showthread.php?t=2451696
the fota and misc partitions are tied to this... try to zero out fota first. if that alone doesnt let you out of twrp... you may need to wipe misc. be sure to backup any partition to computer(dont just save on phone sdcard.. never know when it could get wiped..) before erasing anything.
as for this update(10m)... anyone taking it should be careful that the bootloader/downgrades have not been locked/blocked. I'll be waiting for others to take that risk first before even considering taking the ota.
*update* can confirm update is safe.. bootloader is not locked.. still rootable.
as for root... I doubt purple drake is blocked.. but is possible. I'm very sure Stump is still available as an option(tho app may need update).
if you got the update and dont want to take it.. and want the notification gone you should be able to use a file explorer to delete the update zip from the the /cache directory... as well as rename the LGFOTA.apk file in /system to LGFOTA.apk.bak.
I can also confirm that disabling OTA updates in the hidden menu works. the moment I set it back to "on" (i set mine to off day 1) and rebooted the update came in.
d851 hidden menu > wlan test > ota setting > off > reboot (if you have been notified of an available update do NOT reboot until you have deleted the ota zip first)