Android OS Forum banner
1 - 2 of 2 Posts

·
Android Beginner
Joined
·
17 Posts
klm22 said:
just use your favorite root file explorer and rename /system/etc/security/otacerts.zip to something else. no more ota pushes.
From what I've read, while this will stop the OTA from installing, it does so by making the downloaded update fail the cert check. This can apparently lead to the OTA being repeatedly downloaded over and over. Download, fail check, download, fail check...

I believe the actual update process is com.smithmicro, which is contained in the DmClient.apk file. The process can be frozen with Titanium, or prevented from starting by renaming or deleting DmClient.apk in /system/app using Root Explorer. This will ensure the OTA is never even downloaded in the first place.
 

·
Android Beginner
Joined
·
17 Posts
abqnm said:
Many of these ROMs are not updated frequently, if at all, so if that is all they did to block it, then the next release would require it to be updated again. Without the DM there it won't matter what the current version is. +$.02
Exactly, if all one does is change the version in the build prop, they could very easily get updated when the next official version is released if they don't re-update the version in time. For that reason, removing/renaming the otacerts.zip and the DmClient.apk are the easiest and most reliable way to prevent any future ota update.
 
1 - 2 of 2 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top