My phone somehow downloaded the JB 4.1.2 update and it continually asks if I want to install it. I do NOT want the update. How can I get rid of the downloaded file. I don't want to accidentally allow it to install it.
Septaric said:
My phone somehow downloaded the JB 4.1.2 update and it continually asks if I want to install it. I do NOT want the update. How can I get rid of the downloaded file. I don't want to accidentally allow it to install it.
Click to expand...
Click to collapse
If you happen to be rooted then maybe you can try freezing down some of the moto apps, just one of them at a time and rebooting, and you might find something along those lines. Perhaps its just one app that checks for the update.
Freez OTA update request
Septaric said:
My phone somehow downloaded the JB 4.1.2 update and it continually asks if I want to install it. I do NOT want the update. How can I get rid of the downloaded file. I don't want to accidentally allow it to install it.
Click to expand...
Click to collapse
If you have titanium freeze app titled Updater 4.1.1-41
Related
I keep receiving these nags from Google - apply update, apply update, apply update. I'm on a rooted phone so whenever I try to install upgrade it goes nowhere. What is the best way to install it on a rooted phone WITHOUT wiping it, or the next best thing - get rid of this nag altogether?
Thanks!
It may depend on how you rooted your phone. I used Paul 'MoDaCo' O'Brian's superboot tool to root my phone after 2.3.1, then when I installed 2.3.2 via manual zip download, I stayed rooted.
Sent from my Nexus S using XDA App
XBOHDPuKC said:
I keep receiving these nags from Google - apply update, apply update, apply update. I'm on a rooted phone so whenever I try to install upgrade it goes nowhere. What is the best way to install it on a rooted phone WITHOUT wiping it, or the next best thing - get rid of this nag altogether?
Thanks!
Click to expand...
Click to collapse
Try the instructions in this post: http://forum.xda-developers.com/showpost.php?p=10811723&postcount=30
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.
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
My phone dosent want to update because at one point I was using TB and removed chrome from my phone and installed the app version from play store. Now when I go to update, it reboots into recovery, begins installing, then fails. When I check to see wy its not updating, it gives me a long string of numbers and letters and says .. chrome.apk .. and then it says update aborted.... so I was wondering if anyone knew a way I can fix this because I have a backup of chrome when it was a system app but when I install it, it still does the same thing.
Tyler2265 said:
My phone dosent want to update because at one point I was using TB and removed chrome from my phone and installed the app version from play store. Now when I go to update, it reboots into recovery, begins installing, then fails. When I check to see wy its not updating, it gives me a long string of numbers and letters and says .. chrome.apk .. and then it says update aborted.... so I was wondering if anyone knew a way I can fix this because I have a backup of chrome when it was a system app but when I install it, it still does the same thing.
Click to expand...
Click to collapse
Try rebooting after you're done and see if it did update. A few people have reported that the update said it failed, but when they rebooted the update actually did work. If that fails, then you can just update through RSD.
RikRong said:
Try rebooting after you're done and see if it did update. A few people have reported that the update said it failed, but when they rebooted the update actually did work. If that fails, then you can just update through RSD.
Click to expand...
Click to collapse
Yea, I've tried to update it tons of times and it keeps failing because of chrome not being a system apk. I did try the option on this thread http://forum.xda-developers.com/showthread.php?p=33028928 but, realizing I was on 4.1.2, it failed again and since not using a nexus 7, I'm not sure it will work anyway. I could go with RSD but I was hoping there might be another way to fix it without wiping all the data.
Hello, I have been rooted since I got the s3 pretty much around launch. Today around lunch I noticed an update download progress so I swiped down, long-touched, and the process said SDM 1.0. It had just finished downloading and then telling me to install now/later.. I paniced and put Later and then I specified 10am tomorrow... maybe I should have killed it?
Anyway, why the heck did I get this notification? I have been rooted forever loving my Dandroid ROM... will my phone screw me over by installing 4.3 tomorrow?
I have twrp 2.4.4.0 installed and making a backup now just in case, but I'm worried that it's going to install 4.3. I have never had an OTA update since I rooted this phone.
My ROM is 4.1.2 and I like it the way it is.
pwoz said:
Hello, I have been rooted since I got the s3 pretty much around launch. Today around lunch I noticed an update download progress so I swiped down, long-touched, and the process said SDM 1.0. It had just finished downloading and then telling me to install now/later.. I paniced and put Later and then I specified 10am tomorrow... maybe I should have killed it?
Anyway, why the heck did I get this notification? I have been rooted forever loving my Dandroid ROM... will my phone screw me over by installing 4.3 tomorrow?
I have twrp 2.4.4.0 installed and making a backup now just in case, but I'm worried that it's going to install 4.3. I have never had an OTA update since I rooted this phone.
My ROM is 4.1.2 and I like it the way it is.
Click to expand...
Click to collapse
Since you're rooted, use a file explorer to navigate to /system/app and delete "sdm 1.0." Or if you have Titanium Backup, uninstall the system app "sdm 1.0" and you'll be all set. The update.zip downloaded to /cache/fota which you'll want to delete using a file explorer.
By removing "sdm 1.0" in either of these two methods, you will no longer be prompted to update and your scheduled update reminder for tomorrow won't occur. In addition, if you go to Settings/About Phone and "check for update," this will cause your settings to crash. Don't worry, this is intentional because you removed this file.
Edit: Yes, your phone will screw you over and lock your bootloader down in the process if you accept this VRUCML1 4.3 update. Just being honest!
Thanks, SlimSnoopOS!
I did the app/update removals with Root Explorer. I went to Titanium initially, but I did not see an uninstall option, just freeze or remove.. but the remove option gave me some yes/no popup to use some recovery trick and I said to myself... yea going to Root Explorer. I'm just wondering why I got this push in the first place...never got any notifications from VW/Samsung since I rooted this bugger.
pwoz said:
Thanks, SlimSnoopOS!
I did the app/update removals with Root Explorer. I went to Titanium initially, but I did not see an uninstall option, just freeze or remove.. but the remove option gave me some yes/no popup to use some recovery trick and I said to myself... yea going to Root Explorer. I'm just wondering why I got this push in the first place...never got any notifications from VW/Samsung since I rooted this bugger.
Click to expand...
Click to collapse
Hey, as long as it works! :good::good: haha If you're using a VRBMF1 4.1.2 based custom rom, then this is the first update since VRBMF1 was released last year on our S3. Alls well that ends well of course.
SlimSnoopOS said:
Hey, as long as it works! :good::good: haha If you're using a VRBMF1 4.1.2 based custom rom, then this is the first update since VRBMF1 was released last year on our S3. Alls well that ends well of course.
Click to expand...
Click to collapse
For some reason my phone has been very slow since about a day or so after my initial post. I have done nothing except delete the files. I am starting to wonder if maybe my device is just getting old... I've had it since it launched...now I'm really thinking about the S5. LOL
Anyway, just wondering if anyone has had a degradation of performance with their S3 lately... the most noticeable lag has been with Twitter and Facebook. For example, I will click someone's Twitter post to see replies or a picture that they posted with the tweet, but it takes forever for that information to load..Facebook is not as slow, but still noticeable (e.g. clicking to see comments).