How to stop FRG83D OTA update notification?


Last Updated:

  1. Unicorn512

    Unicorn512 Well-Known Member This Topic's Starter

    Joined:
    Jan 21, 2010
    Messages:
    141
    Likes Received:
    11
    I started receiving the OTA update notification for FRG83D today and I really don't want to install it, since my DROID is rooted and overclocked and running very nicely.

    A similar thing happened a couple of months ago and one post

    http://androidforums.com/droid-all-things-root/179578-how-do-i-prevent-ota-updates.html

    explained how to update the build.prop file to stop the notifications.

    Does anyone know what the correct replacement string for FRG83D should be? I want to redo this same fix, but need all the right info.
     

    Advertisement
  2. drewcam

    drewcam Member

    Joined:
    Mar 21, 2010
    Messages:
    7
    Likes Received:
    0
    Many people who are rooted have this problem. Im on BB v4, waiting on a response to see what the fix is.

     
  3. Unicorn512

    Unicorn512 Well-Known Member This Topic's Starter

    Joined:
    Jan 21, 2010
    Messages:
    141
    Likes Received:
    11
    I don't need this answered anymore, since I bit the bullet and installed Peter Alfonso's Rooted and Odexed version of FRG83D.
     
  4. Lock-N-Load

    Lock-N-Load Well-Known Member

    Joined:
    Feb 8, 2010
    Messages:
    2,309
    Likes Received:
    195
    would still be nice to have the answer though nevertheless.. my guess based on some Goggling could be:

    ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.1/FRG83/60505:user/release-keys
     
  5. Unicorn512

    Unicorn512 Well-Known Member This Topic's Starter

    Joined:
    Jan 21, 2010
    Messages:
    141
    Likes Received:
    11
    I looked at the build.prop file on my updated ROM and your guess appears to be correct. That is the string I see now, and I am not getting OTA update notices anymore.
     
  6. Lock-N-Load

    Lock-N-Load Well-Known Member

    Joined:
    Feb 8, 2010
    Messages:
    2,309
    Likes Received:
    195
    great! so what did I win? :D
     
    Psychokitty likes this.
  7. Unicorn512

    Unicorn512 Well-Known Member This Topic's Starter

    Joined:
    Jan 21, 2010
    Messages:
    141
    Likes Received:
    11
    Only the gratitude of anyone who decides go down the path I started on and just update the build.prop file. That definitely would have been faster than what I wound up doing.

    While I appreciate being at a more current level than FRG01, I really don't see any difference in performance, battery life, or function over what I had before. But my needs are simple, so others may find big benefits being at FRG83.

    Now I can get back to doing the stuff I want to do, instead of spending hours trying to solve a computer problem.

    I just thank God for these forums, since I got all the answers I needed within a couple of days.

    :)
     
  8. GirLuvsDroid

    GirLuvsDroid Well-Known Member

    Joined:
    Jan 5, 2010
    Messages:
    1,307
    Likes Received:
    515
    I believe the correct info to stop the FRG83D OTA update is:

    ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.1/FRG83D/75603:user/release-keys

    and

    ro.build.description=voles-user 2.2.1 FRG83D 75603 release-keys
     
    Tugdaturtle likes this.
  9. kratos

    kratos Back on my throne!!! VIP Member

    Joined:
    Mar 2, 2010
    Messages:
    1,678
    Likes Received:
    430
    Sorry. I forgot to update this thread too. I posted the proper info in the How to Force thread.

    This is the correct info that needs to be in your build.prop file.

    Kratos
     
    Tugdaturtle likes this.
  10. Lock-N-Load

    Lock-N-Load Well-Known Member

    Joined:
    Feb 8, 2010
    Messages:
    2,309
    Likes Received:
    195
    ohhh damn.. that "75603" was the piece I was worried about. thought I had deduced it correct.. shoot
     
  11. Tugdaturtle

    Tugdaturtle Well-Known Member

    Joined:
    Aug 4, 2010
    Messages:
    166
    Likes Received:
    13

    Thanks for helping me update the notification cause i am still on BBv.4 and it is no long poping up
     
  12. twistedlim

    twistedlim Well-Known Member

    Joined:
    Jun 9, 2010
    Messages:
    804
    Likes Received:
    80
    It is helpful. I have wondered back to stock FRG22D and as soon as I did I got the notification. I tried a couple of FRG83D stock roms but they don't seem as smooth as the FRG22D and I am driving myself crazy with custom roms. Time to sit back and relax with ol' realiable.
     
  13. gwdavies

    gwdavies New Member

    Joined:
    Feb 19, 2010
    Messages:
    1
    Likes Received:
    1
    As GirlLuvsDroid correctly posted that you need to alter the build.prop file as follows:

    "ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.1/FRG83D/75603:user/release-keys

    and

    ro.build.description=voles-user 2.2.1 FRG83D 75603 release-keys "


    I altered, saved & rebooted... only to have the same problem with the OTA nagging me to update ever 5 minutes.

    The problem is that if you accidentally click to update, you can screw up your root and even your phone (PS, that happened to me last time I accidentally clicked to receive the OTA update when I was rooted back in August - luckily I was able to unroot enough to send the phone back... won't do that again!!!)

    Anyway, I decided to also alter the build info at the top of the build.prop file in the system menu and after opening in text editor and start on the third line by altering the lines as follows:

    ro.build.id=FRG22D
    To >>> ro.build.id=FRG83D

    ro.build.display.id=FRG22D
    To >>> ro.build.display.id=FRG83D

    ro.build.version.incremental=50454
    To >>> ro.build.version.incremental=75603

    And then skip a couple of lines down to...

    ro.build.version.release=2.2
    TO >>> ro.build.version.release=2.2.1

    I didn't change the build date... I left that at Fri Aug 13... etc.

    And that seemed to do it. For some reason it was OK to keep the old build date.

    Since I updated as above and rebooted, it seems to have fooled the OTA to stop trying to update. :D
     
    teddyearp likes this.

Share This Page

Loading...