Go Back   Android Forums > Android Phones > Motorola Droid > Droid - All Things Root
Droid - All Things Root Rooting, ROMS, Overclocking, etc.

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old November 24th, 2011, 11:18 AM   #1 (permalink)
New Member
Thread Author (OP)
 
Join Date: Nov 2011
Posts: 4
 
Device(s): Samsung Galaxy 10.1
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default How To Stop Receiving System Update Notifications

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

jhayden16 is offline  
Reply With Quote
sponsored links
Old November 25th, 2011, 09:25 PM   #2 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,142
 
Device(s): Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 680
Thanked 697 Times in 425 Posts
Default

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
teddyearp is offline  
Reply With Quote
Old November 28th, 2011, 03:07 PM   #3 (permalink)
Antidisestablishmentarian
 
johnlgalt's Avatar
 
Join Date: Oct 2009
Location: 3rd Rock
Gender: Male
Posts: 9,396
 
Device(s): Motorola® DROID® BIONIC®
Carrier: VZW

Thanks: 2,168
Thanked 1,918 Times in 1,362 Posts
Send a message via ICQ to johnlgalt Send a message via MSN to johnlgalt Send a message via Yahoo to johnlgalt Send a message via Skype™ to johnlgalt johnlgalt@gmail.com
Default

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.
__________________

Files for the Motorola® DROID® BIONIC®:
Motorola USB drivers v5.9.0 | Motorola RSD Lite v5.7
My DropBox Referral link
johnlgalt is offline  
Reply With Quote
Old November 28th, 2011, 03:10 PM   #4 (permalink)
Antidisestablishmentarian
 
johnlgalt's Avatar
 
Join Date: Oct 2009
Location: 3rd Rock
Gender: Male
Posts: 9,396
 
Device(s): Motorola® DROID® BIONIC®
Carrier: VZW

Thanks: 2,168
Thanked 1,918 Times in 1,362 Posts
Send a message via ICQ to johnlgalt Send a message via MSN to johnlgalt Send a message via Yahoo to johnlgalt Send a message via Skype™ to johnlgalt johnlgalt@gmail.com
Default

Here it it's.

Quote:
Originally Posted by icecold View Post
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.
johnlgalt is offline  
Last edited by johnlgalt; November 30th, 2011 at 02:25 PM. Reason: replaced with new (corrected) quotation
Reply With Quote
The Following 2 Users Say Thank You to johnlgalt For This Useful Post:
SNeitzel (December 1st, 2011), teddyearp (December 1st, 2011)
Old November 29th, 2011, 01:09 PM   #5 (permalink)
Senior Member
 
Lock-N-Load's Avatar
 
Join Date: Feb 2010
Location: WestSiiiide
Posts: 2,309
 
Device(s): Moto Droid VZW
Carrier: Not Provided

Thanks: 33
Thanked 197 Times in 151 Posts
Default

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
__________________
/** SGS3 (rooted & stock ROM) **/
/** Asus Prime TF201 (rooted & mildly OC'd) BRICKED BY THE ASUS OTA JB UPATE!**/
/** OG Droid (rooted & OC'd & all hacked up) **/
Lock-N-Load is offline  
Reply With Quote
The Following 3 Users Say Thank You to Lock-N-Load For This Useful Post:
johnlgalt (November 30th, 2011), SNeitzel (December 1st, 2011), teddyearp (December 1st, 2011)
Old November 29th, 2011, 01:59 PM   #6 (permalink)
Senior Member
 
Join Date: Dec 2009
Location: WI
Posts: 667
 
Device(s): Motorola Droid, Samsung Epic 4G, Galaxy Nexus
Carrier: Not Provided

Thanks: 26
Thanked 76 Times in 69 Posts
Default

Quote:
Originally Posted by Lock-N-Load View Post
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...
icecold is offline  
Reply With Quote
The Following 3 Users Say Thank You to icecold For This Useful Post:
johnlgalt (November 30th, 2011), SNeitzel (December 1st, 2011), teddyearp (December 1st, 2011)
Old November 30th, 2011, 02:24 PM   #7 (permalink)
Antidisestablishmentarian
 
johnlgalt's Avatar
 
Join Date: Oct 2009
Location: 3rd Rock
Gender: Male
Posts: 9,396
 
Device(s): Motorola® DROID® BIONIC®
Carrier: VZW

Thanks: 2,168
Thanked 1,918 Times in 1,362 Posts
Send a message via ICQ to johnlgalt Send a message via MSN to johnlgalt Send a message via Yahoo to johnlgalt Send a message via Skype™ to johnlgalt johnlgalt@gmail.com
Default

And I have replaced the quotation with a new quotation of the corrected post
johnlgalt is offline  
Reply With Quote
The Following User Says Thank You to johnlgalt For This Useful Post:
teddyearp (December 1st, 2011)
Old December 1st, 2011, 10:45 AM   #8 (permalink)
Senior Member
 
Join Date: Aug 2010
Posts: 566
 
Device(s): DrOID MAXX, Stock not Rooted (for now...); DrOID Bionic, Stock Rooted; OG DrOID, LGB 1.9
Carrier: Not Provided

Thanks: 208
Thanked 86 Times in 72 Posts
Default

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.
SNeitzel is offline  
Reply With Quote
The Following 2 Users Say Thank You to SNeitzel For This Useful Post:
johnlgalt (December 1st, 2011), teddyearp (December 1st, 2011)
Old December 1st, 2011, 10:58 PM   #9 (permalink)
A guide with guides
 
teddyearp's Avatar
 
Join Date: May 2010
Location: Randle, WA
Posts: 2,142
 
Device(s): Samsung® SCH-I515 & Motorola® XT907
Carrier: Verizon

Thanks: 680
Thanked 697 Times in 425 Posts
Default

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
teddyearp is offline  
Last edited by teddyearp; December 1st, 2011 at 11:00 PM.
Reply With Quote
The Following User Says Thank You to teddyearp For This Useful Post:
johnlgalt (December 3rd, 2011)
Old December 2nd, 2011, 08:47 PM   #10 (permalink)
New Member
 
Join Date: Dec 2011
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
XBugzx is offline  
Reply With Quote
sponsored links
Old December 2nd, 2011, 10:42 PM   #11 (permalink)
Senior Member
 
istolvampire's Avatar
 
Join Date: Nov 2009
Posts: 503
 
Device(s): droid
Carrier: Not Provided

Thanks: 72
Thanked 35 Times in 35 Posts
Default

Quote:
Originally Posted by XBugzx View Post
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.
istolvampire is offline  
Reply With Quote
The Following User Says Thank You to istolvampire For This Useful Post:
johnlgalt (December 3rd, 2011)
Old December 11th, 2011, 11:10 AM   #12 (permalink)
Member
 
Join Date: Dec 2009
Posts: 356
 
Device(s): Bionic, Nexus 7
Carrier: Verizon

Thanks: 14
Thanked 86 Times in 71 Posts
Default

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.
Groid is online now  
Reply With Quote
Old December 11th, 2011, 04:31 PM   #13 (permalink)
Senior Member
 
istolvampire's Avatar
 
Join Date: Nov 2009
Posts: 503
 
Device(s): droid
Carrier: Not Provided

Thanks: 72
Thanked 35 Times in 35 Posts
Default

Quote:
Originally Posted by Groid View Post
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
istolvampire is offline  
Last edited by istolvampire; December 11th, 2011 at 04:34 PM.
Reply With Quote
The Following User Says Thank You to istolvampire For This Useful Post:
Groid (December 12th, 2011)
Old December 11th, 2011, 06:15 PM   #14 (permalink)
New Member
 
Join Date: Dec 2011
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I can't edit build.prop. It keeps giving me the "this file is read-only" error.
Shadownetspy is offline  
Reply With Quote
Old December 11th, 2011, 09:55 PM   #15 (permalink)
Senior Member
 
istolvampire's Avatar
 
Join Date: Nov 2009
Posts: 503
 
Device(s): droid
Carrier: Not Provided

Thanks: 72
Thanked 35 Times in 35 Posts
Default

Quote:
Originally Posted by Shadownetspy View Post
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
istolvampire is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > Motorola Droid > Droid - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 07:47 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.