How To Stop Receiving System Update Notifications

jhayden16 · November 24th, 2011, 11:18 AM

Hi, I've seen some similar posts about this topic for different phones, so wanted to ask before following steps for a different phone.

I've got a rooted Moto Droid 1 with 2.2.2 FRG83G, and I started receiving system update notifications to get me to update to 2.2.3 FRK76. I don't want to do that since I'm rooted and all set up and happy with 2.2.2

How can I stop/ignore those system update messages that come every 15 minutes or so?

Thank you

teddyearp · November 25th, 2011, 09:25 PM

The short answer is to install a custom rom. Another way is to flash SPRecovery, as it _should_ block and/or if you allow the update, it will fail the install and not bother you anymore about it, though you _might_ have the FRK76 file on your sdcard.

And that would be nice to try to grab; the FRK76 file, so I/we can go ahead and fix it to include root and end the worries.

good luck

johnlgalt · November 28th, 2011, 03:07 PM

There is another way. If you're rooted, you can change a line in the build.prop file so it is faked into thinking you already have the frk update.

I'm on the Phandroid app right now, so i cannot find the post, but it is there. It's the same method used by ROMs to prevent updates.

johnlgalt · November 28th, 2011, 03:10 PM

Here it it's.

Quote:

Originally Posted by icecold

In case deleting the .zip file out of the cache doesn't work, this should!

To prevent the update notification, you will probably just have to change the build.prop values...

So, change...

ro.build.description=voles-user 2.2.2 FRG83G 91102 release keys
to
ro.build.description=voles-user 2.2.3 FRK76 185902 release keys

and

ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.2/FRG83G/91102:user/release-keys
to
ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.3/FRK76/185902:user/release-keys

That should take care of the update notification

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/voles/sholes/sholes:2.2.2/FRG83G/91102:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/voles/sholes/sholes:2.2.3/FRK76/185902:user/release-keys");

NOTE: This is the corrected quotation from icecold - please disregard the next post

And thanks to LNL for pointing out the discrepancy.

Lock-N-Load · November 29th, 2011, 01:09 PM

The above is partially incorrect... as I stated in the original thread

the first ones should be...

ro.build.description=voles-user 2.2.2 FRG83G 91102 release keys
to
ro.build.description=voles-user 2.2.3 FRK76 185902 release keys

that is, he incorrectly put fingerprint where it should be description in the first line to look for and edit

icecold · November 29th, 2011, 01:59 PM

Quote:

Originally Posted by Lock-N-Load

The above is partially incorrect... as I stated in the original thread

the first ones should be...

ro.build.description=voles-user 2.2.2 FRG83G 91102 release keys
to
ro.build.description=voles-user 2.2.3 FRK76 185902 release keys

that is, he incorrectly put fingerprint where it should be description in the first line to look for and edit

Actually, you gave me too much credit with Fingerprint, since I missed the "r". After seeing your correction, I have since corrected my original post...

johnlgalt · November 30th, 2011, 02:24 PM

And I have replaced the quotation with a new quotation of the corrected post

SNeitzel · December 1st, 2011, 10:45 AM

You guys got it covered!

But remember...
Do a system backup first, make a copy of /system/build.prop before you edit it, check the permissions of the corrected file after you edit and save it etc.

teddyearp · December 1st, 2011, 10:58 PM

Or some enterprising individual could grab my system template 'update.zip' type file from my collection, pull and edit the build.prop file and package it for the masses . . . . .

just saying. . . . .

guide:

http://ted.servepics.com/index.php?option=com_content&view=article&id=76:up datezip-template-files-for-theming-and-stuff&catid=29:advanced-guides&Itemid=49

XBugzx · December 2nd, 2011, 08:47 PM

Well, I did what you told me and it's still showing up on my notification bar. Although the little pop up every time I turned off my phone seems to be gone.

istolvampire · December 2nd, 2011, 10:42 PM

Quote:

Originally Posted by XBugzx

Well, I did what you told me and it's still showing up on my notification bar. Although the little pop up every time I turned off my phone seems to be gone.

Flash sprecovery from rom manager and let the update try to install. It will fail. Change the build.prop as posted here and reboot the phone. You shouldn't see it anymore.

Groid · December 11th, 2011, 11:10 AM

On my wife's droid, all the previous edits to stop getting the OTA had the ro.build.description= line ending in release-keys. This shows release keys without the hyphen. Can someone please confirm whether or not the hyphen is required or not needed? Thank you in advance.

istolvampire · December 11th, 2011, 04:31 PM

Quote:

Originally Posted by Groid

On my wife's droid, all the previous edits to stop getting the OTA had the ro.build.description= line ending in release-keys. This shows release keys without the hyphen. Can someone please confirm whether or not the hyphen is required or not needed? Thank you in advance.

The hyphen is needed. Just replace number to number. As in

2.2.2 FRG83G 91102 change to 2.2.3 FRK76 185902

And

2.2.2/FRG83G/91102 change to 2.2.3/FRK76/185902

these are the only things you need to edit on the appropriate lines

Shadownetspy · December 11th, 2011, 06:15 PM

I can't edit build.prop. It keeps giving me the "this file is read-only" error.

istolvampire · December 11th, 2011, 09:55 PM

Quote:

Originally Posted by Shadownetspy

I can't edit build.prop. It keeps giving me the "this file is read-only" error.

you have to hit the write/read button first

Football Fans: Download the 2012 Schedule App from Google Play!