Stop the OTA update and notice for root users? - Verizon Samsung Galaxy S III

OTA updates fail for me because I have done custom tweaks to my system.
With the last update before this one, it tried a few times, stopped, failed.. never tried again.
This time, it tried 2 times yesterday and failed. Which I expected.
However, I woke up to it having tried again and failed.. I thought it was over like last time.
Any idea on how I can kill this and stop it from trying to update OTA over and over? I don't want it.

you can delete the update in the cache/fota/, than freeze sdm 1.0.

zedocus16 said:
you can delete the update in the cache/fota/, than freeze sdm 1.0.
Click to expand...
Click to collapse
I had checked there before and nothing.. but this time, since I delayed the update there it was. 30.92mb of update.zip. Going to copy it to my computer and then delete it.
But, what & where is sdm 1.0?

Lock-N-Load said:
I had checked there before and nothing.. but this time, since I delayed the update there it was. 30.92mb of update.zip. Going to copy it to my computer and then delete it.
But, what & where is sdm 1.0?
Click to expand...
Click to collapse
You can find it in titanium backup... just freeze it.....no more updates
Sent from my SCH-I535 using xda app-developers app

for now.. I just deleted the update.zip... if it tries to download yet again, then I will try the sdm 1.0 freeze

Related

software update

My tbolt keeps trying to do the software update and i dont see and option to not do the auto update i dont want to loose root
Thanks for the update.
dre4402 said:
My tbolt keeps trying to do the software update and i dont see and option to not do the auto update i dont want to loose root
Click to expand...
Click to collapse
If you try to update, it should fail. Most roms are signed differently then the ota so the phone wont update...
Just open titanium backup and freeze the updater. Problem goes away completely.
DaedalusZR1 said:
Just open titanium backup and freeze the updater. Problem goes away completely.
Click to expand...
Click to collapse
What is the updater called? I have frozen updater.apk and it still keeps trying to update itself!
tomz17 said:
What is the updater called? I have frozen updater.apk and it still keeps trying to update itself!
Click to expand...
Click to collapse
That actually fixed it for me... so I'm not sure why you're getting it. :\
Why not update the ROM your using to one that uses MR2 as the base?
Yeah are you using the newest base?
Sent from my ADR6400L using XDA App
If rooted it should not update.
I've never been prompted for an update once rooted
Sent from my ADR6400L using XDA App
My wife's nephew is rooted on stock and he keeps getting the update message. Would it fail if it downloads and tries installing or is it going to break his phone? He couldn't find anything in titanium that says updater.... Any thoughts?
jv
The OTA update will never download or install. There is a way to disable the OTA update notification but I can't remember the file that needs to be edited to do so.

Not a crisis, but could use some help

So after reading that the 2.3.6 update should not cause loss of root (i used zergrush oneclick), I decided to go ahead and do it OTA.
Unfortunately I was on a conference call for work and forgot to unfreeze the apps I had previously frozen with TiBu.
Started the update, it got to 75% and then said "update failed" and restarted. Everything seems fine.
I went into TiBu, unfroze everything and went back to update. I checked for the update and it is saying I am up-to-date, and to check back in 24 hours, but the phone is still on 2.3.5.
Any thoughts on how to force it tonight (or later if it does not want to do it on it's own)
Figured I would ask first before messing around anymore.
Yes push menu settings date and time uncheck automatic and change your date to a day from now manually then u can get the update
silver03wrx said:
Yes push menu settings date and time uncheck automatic and change your date to a day from now manually then u can get the update
Click to expand...
Click to collapse
Thanks for the quick answer.
Unfortunately, while that did allow me to check again for updates, it is still saying my phone is up to date, despite showing as being on 2.3.5
I don't think the TiBu frozen apps prevented the OTA update... I was rooted using SuperOneClick 2.2 on 2.3.5. I did the OTA 2.3.6 update with 18 apps frozen with TiBu and it updated fine... I retained root... 18 apps still frozen... LauncherPro and all my widgits still functional. We're you on stock Recovery?
Sent from my SAMSUNG-SGH-I727 using XDA App
Vaguely embarrassed but I think so? I have a new kid so much less time to play with phones.
Took a stock phone, rooted with zergrush, added super user so I could use TiBu to freeze bloat and some of the advanced juice defender and widget locker capabilities and that is it.
Sent from my SAMSUNG-SGH-I727 using XDA App
Any solution for this yet?
I did the same thing, had mulitple apps and services frozen. I keep getting the already updated message.
Sent from my SAMSUNG-SGH-I727 using xda premium
[/COLOR]http://api.viglink.com/api/click?fo...us/mNUNsVbYm&jsonp=vglnk_jsonp_13221191523521
HERE PEOPLE 2.3.6 flashable zip uploaded by mikeyinid
mikeyinid said:
OK, here it is. But, after I was about halfway through the upload, I remembered I puller some stuff out. The main thing I was concerned with is the visual voicemail.apk. Hope you guys can get it from the market like we can on tmobile. Anyhow, here is the rooted 2.3.6 rom. Please, after first boot, go back into recovery and fix permissions.
Click to expand...
Click to collapse

Need Help, Updating Fails 2.3.6

Don't know what went wrong, but every time I try to update to 2.3.6 I get an error image and then it reboots. Done this 5 times and its driving me crazy
J94w said:
Don't know what went wrong, but every time I try to update to 2.3.6 I get an error image and then it reboots. Done this 5 times and its driving me crazy
Click to expand...
Click to collapse
Are you rooted? If so what modifications have you done?
Have you uninstalled any of the stock bloatware, even if it was uninstallable without root? The update requires all bloatware to be installed.
J94w said:
Don't know what went wrong, but every time I try to update to 2.3.6 I get an error image and then it reboots. Done this 5 times and its driving me crazy
Click to expand...
Click to collapse
Seriously people, search before you post!! We have covered this at least 10 times!Anyways, If you have deleted any of the AT&T bloatware the update will fail. It is STRONGLY recommend that you flash the fkz's to get back to stock before you apply the update, especially if you have rooted and performed any mods. Just be sure to re-root and apply the 4ever root mod to keep root over the OTA.
Or just wait for lfaber to make something awesome with it!
Thanks, I just now stumbled on the other thread's also saying the same thing my bad. And also another question why is the bloatware so important?
J94w said:
Thanks, I just now stumbled on the other thread's also saying the same thing my bad. And also another question why is the bloatware so important?
Click to expand...
Click to collapse
It's not that it's important... it's that the update file is filled with a bunch of patches, some of which are for the bloatware, and so if the bloatware isn't there the patches don't install and the update won't begin (it checks everything at first.)
Oh ok thanks
It's not working for me too . I removed alot of the bloatware yes any solution beside restoring fxz ?
Sent from my MB865 using XDA App
alcatel444 said:
It's not working for me too . I removed alot of the bloatware yes any solution beside restoring fxz ?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Sadly not...
you can just wait for custom ROMs to be based off of 2.3.6 and flash them... this update really isn't very major.
How can I tell if it's even trying to update. I manually started the update about 4 hours ago, but it doesn't look like anything is downloading. When I click on system update again, it says an update is currently being downloaded, but according to 3G watchdog, my wi-fi usage isn't changing. If I turn off wi-fi, it says the download will resume when wi-fi is back on, but the percentage is at 0%, and when I turn wi-fi back on, it stays at 0%.
If it's going to error out, does it not say something? I'm not getting any indication that it failed. Is there not a progress bar in notifications or anything? At first, I figured the server was just busy, but after 4 hours, something should have downloaded by now, right?
stedean said:
How can I tell if it's even trying to update. I manually started the update about 4 hours ago, but it doesn't look like anything is downloading. When I click on system update again, it says an update is currently being downloaded, but according to 3G watchdog, my wi-fi usage isn't changing. If I turn off wi-fi, it says the download will resume when wi-fi is back on, but the percentage is at 0%, and when I turn wi-fi back on, it stays at 0%.
If it's going to error out, does it not say something? I'm not getting any indication that it failed. Is there not a progress bar in notifications or anything? At first, I figured the server was just busy, but after 4 hours, something should have downloaded by now, right?
Click to expand...
Click to collapse
A reboot can't hurt.
Ok i had issues upgrading to 2.3.6 tonight.. I realized i had stupidly uninstalled YahooContacts.apk and FMRadioService.apk... As we know Titanium can't restore these. However what I did do was this:
open /cache/recover/last_log in a text viewer
scroll to the bottom, it will tell you what is causing the installer to fail.
Mine i could clearly see it couldn't find FMRadioService.apk I took the .gz file from the titanium backup directory, un-gzipped it, renamed the .apk to FMRadioService.apk and placed it in /system/app I then re-tried the update, it failed again, repeated with YahooContacts.apk
and viola... all was well..
-t
I tried that. The progress bar that was stuck at 0% went away after reboot, but it's still not downloading anything, as far as I can tell. That's why I was wondering if there is any kind of progress bar normally.
I'm thinking that, since I'm at work, our wi-fi is blocking it. I can't get it to download over 3G, so I guess I'll wait until the morning, when I'm home.
BTW, if your phone dies ("Battery Low - Cannot program" message) while trying a rollback to 2.3.5 try the following procedure. It's risky but I was able to bring my Atrix 2 to live:
http://forum.xda-developers.com/showthread.php?t=892026

Stop Jellybean Update

Honest ive been searching for an hour, how do i stop the update from happening. Not permanently, hopefully like blocking the update app with Titanium like i did on my Galaxy S3. Also, the location of the already downloaded file so i can delete it. Thanks
Honestly!!?? Is this really that dumb of a question? I honestly still cant find how to block the JB update. Please anybody?
I would love to know that too. I really don't want to hit the update by mistake...
Honestly, just make sure you honestly don't click the update button. Honestly that's all there honestly is to it...honest!:laugh:
Honestly
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
After some research I found that renaming otacerts.zip (in /system/etc/security/) with a .bak at the end could prevent the update to start but the notification is still here.
I tried to stop the Firmware Update Utility in app manager, even by renaming it with a .bak in /system/app/ . The notification is still here, but it seems that the popping window is not showing. Time will tell.
I saw somewhere that renaming the fingerprint line in build.prop woud work, luring the update into thinking the firmware is already up to date, but since I never touched this file (android newbie here!) I will wait for someone more experienced in modifying that kind of things...
If you are rooted, edit your build.prop (back up your original) and then tell the tablet to update. The update will fail (red triangle) and will reboot into ICS. The notification should go away and you will have to update manually.
Ok but what to edit in build.prop?
Gamlus said:
Ok but what to edit in build.prop?
Click to expand...
Click to collapse
Check this thread in the development section. There is a tweaked build.prop that I used before my upgrade. That is what caused my OTA update to fail. BE sure to use the correct file and back up your current build.prop.
http://forum.xda-developers.com/showthread.php?t=1641219
Yes !
I didn't actually changed the whole build.prop, but I downloaded the stock JB build.prop to take the fingerprint line.
So, after a backup of my build.prop, I changed this line :
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.3.30-20120604:user/release-keys
With this one :
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.2.9-20120809:user/release-keys
And now, no more notification, after a reboot and a failed install of JB.
Thank you !
turdbogls said:
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
Click to expand...
Click to collapse
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
with my previous returned tf300: after i turned it on the first time it downloaded the ICS .30 firmware and asked me to update, i installed it. then i was curious why it did not download the JB update, so i went to check update manually, it started downloading the jb update and i had to update to jb. after a few days because of hardware problem i returned it.
my new tf300 came yesterday, and the same thing above happened, i updated to ICS .30, now i try to remind myself to not accidentally manually check for update, sounds weird, right? i see cmclient and dmclient always running but it never knows that there's a update lol. and i usually don't go to about tablet so i guess i won't do manual update accidentally.
bige914 said:
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Gam3r 4 Life said:
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Click to expand...
Click to collapse
Thanks +1
Worked for me too...
neur28 said:
Thanks +1
Worked for me too...
Click to expand...
Click to collapse
Does your stock email app work now? After freezing the DM client the stock email app gets stuck at waiting for sync.
Nevermind. I defrosted the dmclient and email still didnt work. So I rebooted. Saw the update again. So I refroze dmclient, then restored my email app and data in titanium and that fixed it.
I'm glad I helped all of you and enjoy your tablets as I am :3 screw Asus JB update we D block that yo
Sent from my HTC Ruby using xda app-developers app

[Q] Just got the VZW update. How to turn it OFF?

Ok, this morning my phone started downloading the VZW update. I'm stock-Rooted with Wallet and Google Now running. When the update was finished downloading it gave me a few minutes to accept or to defer. I chose the defer button and then it ask's me to pick a time later today to do it. How do I get out of this? I don't want to run the update.
Thanks
dbow32 said:
Ok, this morning my phone started downloading the VZW update. I'm stock-Rooted with Wallet and Google Now running. When the update was finished downloading it gave me a few minutes to accept or to defer. I chose the defer button and then it ask's me to pick a time later today to do it. How do I get out of this? I don't want to run the update.
Thanks
Click to expand...
Click to collapse
Download Titanium Backup from the Play store, run it, go to the Backup/Restore tab, scroll down to "SDM 1.0" and uninstall it. You should probably make a backup of it first just in case you ever need to get it back, but I've never read of it being used for anything other than pushing Verizon OTAs, which you will probably never want to receive if you're rooted.
If you have the paid version of Titanium Backup, you can "freeze" the app instead, but uninstalling it with the free version works too.
Thanks, I really appreciate your help
I tried freezing it before I received the update and that didn't work. Guess its somehow overridden by Verizon.
Sent from my SCH-I535 using Tapatalk 2
ef-civic said:
I tried freezing it before I received the update and that didn't work. Guess its somehow overridden by Verizon.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had to reboot after freezing it for it to stop downloading
Jacquestrapp said:
Download Titanium Backup from the Play store, run it, go to the Backup/Restore tab, scroll down to "SDM 1.0" and uninstall it. You should probably make a backup of it first just in case you ever need to get it back, but I've never read of it being used for anything other than pushing Verizon OTAs, which you will probably never want to receive if you're rooted.
If you have the paid version of Titanium Backup, you can "freeze" the app instead, but uninstalling it with the free version works too.
Click to expand...
Click to collapse
I have not received any prompts for OTA updates yet and was curious as to why that is. Apparently, some ROMS are coded without the SDM 1.0 file because I am running Clean ROM 2.5 and cannot find SDM 1.0 anywhere in the list. Another reason why Scrosler and CleanROM are boss!
mooremh said:
I have not received any prompts for OTA updates yet and was curious as to why that is. Apparently, some ROMS are coded without the SDM 1.0 file because I am running Clean ROM 2.5 and cannot find SDM 1.0 anywhere in the list. Another reason why Scrosler and CleanROM are boss!
Click to expand...
Click to collapse
Any custom ROM worth its salt should not include the SDM app, CleanROM isn't special in that regard.

Categories

Resources