Database Develop

[Q] How do I stop OTA install reminder?

Verizon rooted non-DE. The KitKat OTA downloaded but I've "snoozed" the install as I don't want to lose root/tether.
Can I freeze something in TB to get it to stop asking me to complete the install? I'm afraid I'm going to hit the wrong button one time and mistakenly take the OTA.

TwinsMom said:
Verizon rooted non-DE. The KitKat OTA downloaded but I've "snoozed" the install as I don't want to lose root/tether.
Can I freeze something in TB to get it to stop asking me to complete the install? I'm afraid I'm going to hit the wrong button one time and mistakenly take the OTA.
Click to expand...
Click to collapse
if you already downloaded it, im surprised you are not in a bootloop right now because that is typically what happens. But use tibu to freeze moto ota (or something like that) and updater (or something like that). If you can't find what im talking about in TIBU then i can look it up and give you the exact names.

jayboyyyy said:
if you already downloaded it, im surprised you are not in a bootloop right now because that is typically what happens. But use tibu to freeze moto ota (or something like that) and updater (or something like that). If you can't find what im talking about in TIBU then i can look it up and give you the exact names.
Click to expand...
Click to collapse
Thanks! I found "MotorolaOTA 1.0" and "Updater 1.0" and froze those in tibu so we'll see what happens.
On my Moto X it first downloaded the OTA then asked if I wanted to install it, giving me the usual "you will not be able to use your phone for up to xx minutes during the installation". Then it gave me the option to not install, then if I didn't install, it gave me the option of when to be reminded and a check box for "auto-install". I kept the check box UNclicked and set the reminder for later tonight. That's how I avoided the dreaded bootloop.

Also if you change it for one minute earlier you will have a whole day without getting reminded.

TwinsMom said:
Thanks! I found "MotorolaOTA 1.0" and "Updater 1.0" and froze those in tibu so we'll see what happens.
On my Moto X it first downloaded the OTA then asked if I wanted to install it, giving me the usual "you will not be able to use your phone for up to xx minutes during the installation". Then it gave me the option to not install, then if I didn't install, it gave me the option of when to be reminded and a check box for "auto-install". I kept the check box UNclicked and set the reminder for later tonight. That's how I avoided the dreaded bootloop.
Click to expand...
Click to collapse
dont reboot your phone or that thing will go into bl and automatically try to upgrade to the ota from what i have read about others.

Thanks for the help, freezing those worked fine. Gave me some time to do research on the new KitKat root method and see if it will hold native wifi tether.
Sent from my GT-P6210 using xda app-developers app

[Q] Freeze notification for OTA

Rooted non dev VZW Moto X, want to try and freeze the notification to pull the OTA. I froze "updater" in TiBu and I still get it. I also disabled notifications for framework in the apps list and I still get it. Any other suggestions?

tluley51 said:
Rooted non dev VZW Moto X, want to try and freeze the notification to pull the OTA. I froze "updater" in TiBu and I still get it. I also disabled notifications for framework in the apps list and I still get it. Any other suggestions?
Click to expand...
Click to collapse
I have XT1053 and not Verizon version. I froze MotorolaOTA 1.0 in TiBu and it took care of update notifications for me. My coworker has Verizon DE edition and it worked for him too. Is that the app that you froze?

JoeSchmoe007 said:
I have XT1053 and not Verizon version. I froze MotorolaOTA 1.0 in TiBu and it took care of update notifications for me. My coworker has Verizon DE edition and it worked for him too. Is that the app that you froze?
Click to expand...
Click to collapse
Just froze it, we shall see! Thanks!

Are there any other apps that can freeze beside TiBu? I don't have the donate version.

fury683 said:
Are there any other apps that can freeze beside TiBu? I don't have the donate version.
Click to expand...
Click to collapse
I used TiBu so can't help you. It was worth the $6 to me. But you can just download root browser and navigate to /system/priv-app then press and hold 3c_ota.apk and select rename. Rename it 3c_ota.apk.bak. Then when or if you want to take the OTA, just rename it back to 3c_ota.apk.
Also, you can use root browser to delete the OTA file from /cache. Navigate to /cache and find the OTA and then press and hold then select delete.

Hide 4.4.4 System Update?

I have a VZW DE on 4.4.2, unlocked bootloader, rooted, no custom ROM.
Was wondering if there is any way to hide the system update prompts/notifications as I'd rather wait for a more substantial upgrade (Android L).
Using root explorer I did go to etc/security/ and renamed otacerts.zip to otacerts.zip.bak to no avail. Also, there didn't seem to be anything for me to freeze in TiBu.
Not only is this a marginal upgrade imo, I just don't want to mess with going back to stock recovery, upgrading to 4.4.4, flashing TWRP, re-root, do system tweaks (e.g. replace ugly vzw 4G Icon and bars, but first check to see if someone made one compatible to 4.4.4), research whether wifi tether from xposed module still works on 4.4.4, etc. Just plain don't have the time to do all that at the moment.
Thanks in advance!

I thought I had replied to this exact question yesterday...
use a root capable file explorer, got to /system/priv-apps and rename 3C_OTA.APK
Of course, if your phone has already downloaded the file, navigate to /cache and remove it.
Reboot after making the changes.
that has prevented getting prompted in the past.

I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began

Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X

Schaweet said:
Out of curiosity, why wouldn't you take the update?
Click to expand...
Click to collapse
I can say for my two Non-DE Verizon Moto X phones running 4.4.2 and TowelPieRoot that I'm not taking the update for root reasons first and foremost. Until the time when a 4.4.4 root method is developed, if ever, I'll remain on 4.4.2.
I appreciate the suggestions in this thread however because I'm looking to hide these notices myself.

doitinthedirt said:
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Click to expand...
Click to collapse
Thanks, all! I went ahead and renamed the odex as well. Rebooted and good to go!

Schaweet said:
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.

Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X

jamespark said:
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Click to expand...
Click to collapse
Schaweet said:
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
EDIT: I do see that you have the "Old" gravitybox installed, so this might require setting up the new version. But everything else stated is completely relevant.

I froze MotorolaOTA 1.0

samwathegreat said:
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
Click to expand...
Click to collapse
HUGE. I haven't been following any forums for several months and was not aware of this FXZ. Great to know, thanks!

Mayze23 said:
I froze MotorolaOTA 1.0
Click to expand...
Click to collapse
same

A thread already exists for this exact thing here. Please post question in Q&A in future and search before creating new threads.
Thread closed

[Q] Diable 5.1 update on rooted Pure?

I have a rooted stock ROM Pure and I want to avoid the 5.1 update for a couple of reasons.
Does anyone know how to disable the update process on these devices?
TIA

FoneWatcher said:
I have a rooted stock ROM Pure and I want to avoid the 5.1 update for a couple of reasons.
Does anyone know how to disable the update process on these devices?
TIA
Click to expand...
Click to collapse
Disable MotorolaOTA in the system apps in settings. If you're rooted, you can freeze it in the /system folder using Titanium or whatever else you use. Safest thing to do is to rename it with a .bak at the end, then when you're ready to update you just remove it and reboot.

sivarticus85 said:
Disable MotorolaOTA in the system apps in settings. If you're rooted, you can freeze it in the /system folder using Titanium or whatever else you use. Safest thing to do is to rename it with a .bak at the end, then when you're ready to update you just remove it and reboot.
Click to expand...
Click to collapse
Thanks for the reply. I froze it with Ti Backup, but I'm still able to check for updates manually and it reports normally.
Shouldn't that function be disabled if the OTA apparatus is truly disabled?
I do see in firewall a process called 'Device Management that I thought I could block MotorolaOTA from communicating, but there are other functions bundled, so I don;t want to do that.
Ideas, anyone?

FoneWatcher said:
Thanks for the reply. I froze it with Ti Backup, but I'm still able to check for updates manually and it reports normally.
Shouldn't that function be disabled if the OTA apparatus is truly disabled?
I do see in firewall a process called 'Device Management that I thought I could block MotorolaOTA from communicating, but there are other functions bundled, so I don;t want to do that.
Ideas, anyone?
Click to expand...
Click to collapse
Motorola will still be able to be communicated to, but the OTA function will be disabled, eg. no OTA will be detected. It is my understanding that blocking MororolaOTA just keeps the notification from appearing and prevents OTA downloads.

sivarticus85 said:
Motorola will still be able to be communicated to, but the OTA function will be disabled, eg. no OTA will be detected. It is my understanding that blocking MororolaOTA just keeps the notification from appearing and prevents OTA downloads.
Click to expand...
Click to collapse
Thanks again - that makes sense. I'll see the rollout on my stock Pure (if I still have it and decide not to sell it) and be able to compare in real-time if it does the trick.

Disabling the system update notification

Is there anyway to disable the system update notification? For a variety of reasons I don't want to upgrade to 6.0 yet. I have root on stock debloated 5.1
Thanks.

tk424 said:
Is there anyway to disable the system update notification? For a variety of reasons I don't want to upgrade to 6.0 yet. I have root on stock debloated 5.1
Thanks.
Click to expand...
Click to collapse
I tried two rooted debloated roms that both said OTA disabled and i got the nag notification on both. Disappointing!

Same here! I myself used TB to freeze all the system apps which were supposed to trigger the OTA updates, but I still got it. I moved the update.zip from the cache directory somewhere else, so if I accidentally hit update, nothing will happen. But still a nuisance.
Anyone with an idea?

Is this a new problem? For dumb reasons I ended up having to reflash Rydah's stock rooted 5.1 image yesterday and starting mostly all over, it's a pain in the butt. I did freeze pr.adapt and update center but this notification popped up to update. I definitely do not want to update. I thought the rooted ROM blocked updates? I guess not because the notification is there. I tried disabling Google play services notifications but the notification persists.
---------- Post added at 02:36 PM ---------- Previous post was at 01:39 PM ----------
OK guys, I got rid of my notification. I used titanium backup and froze everything I could on the following list,
http://forum.xda-developers.com/tmobile-g4/help/debloat-package-list-lg-g4-t-mobile-h811-t3168181
I froze very few from the following list, still working on it after my mishap yesterday.
http://forum.xda-developers.com/g4/help/lg-g4-stock-debloater-list-g4-variants-t3167297
The notification was still there, but I decided to reboot and now the notification is gone. Hopefully it sticks. Where can I find the update.zip so I can delete it and clear up some space.

waylo said:
Same here! I myself used TB to freeze all the system apps which were supposed to trigger the OTA updates, but I still got it. I moved the update.zip from the cache directory somewhere else, so if I accidentally hit update, nothing will happen. But still a nuisance.
Anyone with an idea?
Click to expand...
Click to collapse
Where is the update.zip hiding? I too am not ready to update, but cant block it. Thanks

jhmcat said:
Where is the update.zip hiding? I too am not ready to update, but cant block it. Thanks
Click to expand...
Click to collapse
Using a root explorer, in the internal memory, go to /cache. It's about 970mb.

waylo said:
Using a root explorer, in the internal memory, go to /cache. It's about 970mb.
Click to expand...
Click to collapse
Got it moved (not deleted). Thanks!

jhmcat said:
Got it moved (not deleted). Thanks!
Click to expand...
Click to collapse
Hmm, I found it comes back from time to time. So definitely need to get to the bottom of what pulls down the update. Still don't think we've nailed the offending apk/service.

waylo said:
Hmm, I found it comes back from time to time. So definitely need to get to the bottom of what pulls down the update. Still don't think we've nailed the offending apk/service.
Click to expand...
Click to collapse
As of yesterday and last night, update.zip did not return after I froze all those apps. I wish I could've pinpointed the exact app. All I can say was I froze all those apps on the first list, and maybe line one or two from the other list and the notification was still on the screen. I rebooted because after freezing so many apps, I was worried about a boot loop. My phone booted fine and the notification was gone and it didn't come back. I just checked cache and update did not come back

Well damnit, the update.zip came back probably last night. I don't have the notification though, that is gone but I'm not happy having that file come back. If anyone at all can pinpoint the reason it comes back, please post!

mattnin said:
Well damnit, the update.zip came back probably last night. I don't have the notification though, that is gone but I'm not happy having that file come back. If anyone at all can pinpoint the reason it comes back, please post!
Click to expand...
Click to collapse
Mine came back too. Deleted the update.zip again.. but would like to disable it for sure.

You could always try moving the files, then put a same-named read only (e.g. chmod 440) file in it's place - or maybe safer yet is put a directory of the same name there.