• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Disable Ota Update. Is it possible?

M

Modman

Android Enthusiast
My tablet is running fine I'm in no dire need to go to jb 412.
I'm rooted and running twrp. Is there away to just disable the ota update prompts? If not where can I get a good copy of the update file to flash?
Last one failed the checksum.
 
You could try disabling it with auto starts.

Just open it, select the after startup tab
a3yryqer.jpg


And scroll down to Google services framework and find the one that handles system updates
ehane6a2.jpg

(Third one in my case, may differ for you)

And disable it.

Then clear cache and reboot
 
Lordvincent 90 said:
You could try disabling it with auto starts.

Just open it, select the after startup tab

And scroll down to Google services framework and find the one that handles system updates

(Third one in my case, may differ for you)

And disable it.

Then clear cache and reboot
Click to expand...

Where do you find this auto starts..?
 
No idea if this will work, but couldn't you just uncheck "show notifications" for Google services framework?
 
Best way to do this is to install CWM or TWRP custom recovery, OR using a root uninstaller (needs root, obviously) if you remove system apps you don't use (i.e. Chrome, YouTube, or any of the pre-installed system gapps, your update will fail "the update test").
 
He'll still get the annoying notifications that an update is available though. I think thats what most people want to disable.


In other news...We should be getting 4.2 within the next few days, I'll try to get another update zip up that doesnt check for the system apps
 
Rxpert83 said:
In other news...We should be getting 4.2 within the next few days, I'll try to get another update zip up that doesnt check for the system apps
Click to expand...

FWIW, I don't know how many folks know about the new app I released in the Market a few weeks ago, but it's an OTA .zip file verifier. It will evaluate the updater-script file (as well as notifying you of any system apps you might have frozen) to see (and show you) what issues you might encounter when you try to install said OTA.

This app can really be used before you attempt the install or even afterwards in lieu of viewing the /cache/recovery/log file to see what might have failed.

Let me know if want to know more (it's free in the Market; link is in my signature).

Cheers!
 
Sweet I'll have to check that out. I've just been editing the updater script to get rid of the checks since I have removed system apps
 
Rxpert83 said:
Sweet I'll have to check that out. I've just been editing the updater script to get rid of the checks since I have removed system apps
Click to expand...

:)

By the way, the app will actually evaluate any updater-script (edify, not amend) flashable .zip file (I just wrote it for folks that try to install and OTA and can't figure-out which asserts or other edify functions are failing).

I don't write that many flashable .zip files, but I'm guessing this might also be useful to ROM devs who want to pre-test their updater-script files (at least the non-destructive portions--my app will not execute any edify commands that actually changes anything).

I've got an app announcement thread if you have any questions that aren't applicable/appropriate here.

Cheers!
 
Might load the ota.zip verifier to try it.

Didn't know about auto starts soon enough or might have taken the easy way out.

Does anyone know if 4.2 is already rootable?

Don't want to lose root. Heads if its already rootable update.

Tails if its not use auto starts or an alternative to suppress it.

Where does the ota.zip download to by default?

I copied a user app to /system/app folder for permissions reasons.
when I no longer needed the app I deleted the .apk from /system/app. Hopefully that won't cause issues

But if it did the ota.zip verifier might be useful.

Just not sure where the ota.zip gets saved so I can check it.
 
Did this after receiving the nag message twice to ota update. Where does stock save otaupdate.zip
There was a similar service called update receiver service secret code left that one enabled. Might go reenable later wanna see if the nagging stops. Might reenable when I have time take a nandroid then update.
will that update nag go on forever when enabled? What is best app to keep root and restore it after an ota?Is anyone experiencing anything negative with the 4.2 update so far?
 
I verified the ota and found the Asus keyboard frozen. Probably from when I was playing with the keyboard unfroze with titanium and now ota passes. Another question. Can the ota in the /cache folder be flashed through twrp?
Also waiting for more people to report back no issues with update. What apps can preserve root?
 
Yes, just navigate to the zip file in twrp and you can flash it.
Supersu or ota rootkeeper are supposed to make root survive an ota. No experience with that tho, I just reroot.
 
Never tried the ota rootkeeper one but from experience the Super Su root keeper fails. When do you plan on trying the update?
 
Auto run Manager is the best. Now you can decide for yourself if and when you want an ota. For me I think the bad outweighs the good right now for 4.2. Has anyone at all successfully updated without softbricking and having to start from scratch?
 
Modman said:
Never tried the ota rootkeeper one but from experience the Super Su root keeper fails. When do you plan on trying the update?
Click to expand...

OTA Rootkeeper is great--I implemented the same root saving methodology in my Android Root Toolkit app (I use both, actually).

Modman said:
Auto run Manager is the best. Now you can decide for yourself if and when you want an ota. For me I think the bad outweighs the good right now for 4.2. Has anyone at all successfully updated without softbricking and having to start from scratch?
Click to expand...

Got my OTA update for 4.2 last night.

Root was (of course) lost for a moment, but restored it via my app. SuperSU noticed / suggested an su binary update immediately afterwards.

Worked great :).
 
Modman said:
Did this after receiving the nag message twice to ota update. Where does stock save otaupdate.zip
There was a similar service called update receiver service secret code left that one enabled. Might go reenable later wanna see if the nagging stops. Might reenable when I have time take a nandroid then update.
will that update nag go on forever when enabled? What is best app to keep root and restore it after an ota?Is anyone experiencing anything negative with the 4.2 update so far?
Click to expand...

Modman (or anyone else) I have tried this as well but did not get rid of the nag nor am I clear if you did. I have been hitting Install Later for the 98.18.94 update for over a month. I am currently on 98.18.78.xt907.verizon.en.US (Razr M) and it wants me to take 98.18.94. SuperSU installed, VooDooOTA and to get rid of this OTA notification I installed Autorun Manager. I disabled SystemUpdateService$Receiver and tried to clear the cache, but I was not sure what applications cache to clear (cleared Google Paly Store, Google+ and Google Play Services). I re-booted after that.

I am planning to take the OTA (when I want to and hopfully get back root with VooDoo) but wanted to make sure I know how to block it with this one.

I know this is an old post and probably my phone may seem old (and this in not in correct phone area but the search seemed like a good fit) to many, but I like it and what it does for me, so more help would be appreciated.
 
Wow that was a long time ago after like there's updates I got some major lag. Not that update didn't cause any additional issues. However after 3 successful ota's I lagged like crazy. Yes it was rerootable. By kitkat lag was so bad the update failed at that point even though ota checker was successful. The first reformat and start from scratch I did was with kitkat. Ota failed and lag was horrible so I used wugs to return to stock for fresh kitkat install. Kitkat was rerootable with wigs on nexus 7
 
I followed the steps you provided (thank you) but I still have it every 12 hours. I did not clear any Caches this time as I did not see that step.

Could it be the Razr M is different enough so this does not work?

Any Razr M owner's with vz have any luck stopping these?
 
kontinroid said:
I followed the steps you provided (thank you) but I still have it every 12 hours. I did not clear any Caches this time as I did not see that step.

Could it be the Razr M is different enough so this does not work?

Any Razr M owner's with vz have any luck stopping these?
Click to expand...

Unfortunately the process will be different, the instructions I posted are specifically for the Nexus 7, other Nexus devices may work as well.

A quick search and it would appear you may be able to freeze the updater application on your device using Titanium Backup, just search for the term
 
+1 to that. Always have a recent nandroid before you do anything involving the system. Its amazing the daft things that can put you in a bootloop and its soul destroying having to go back to a 2month old nandroid (been there. For the sake of a boot animation) :D
 
You must log in or register to reply here.
Back
Top Bottom