1. Check out our app, Forums for Android! Download and leave feedback here!

Root How do I disable OTA updates?

Discussion in 'Android Devices' started by tturner35, Nov 18, 2010.

  1. tturner35

    tturner35 Member
    Thread Starter
    5

    Mar 16, 2010
    6
    0
    5
    I'm rooted, still running stock 2.2. How do I disable OTA updates? I want to keep the current ROM.

    Thanks in advance for any help.
     

    Advertisement

  2. jasonb1985

    jasonb1985 Well-Known Member
    98

    Jan 5, 2010
    987
    67
    98
    Radio Shack
    you need to edit your build prop file so that verizon thinks you are already running the latest update. if it shows you are running the latest version, then it'll think that you really are.

    i did this on my rom and i have not seen a notification for an update yet.
     
  3. tturner35

    tturner35 Member
    Thread Starter
    5

    Mar 16, 2010
    6
    0
    5
    Ah, okay. Thanks for the quick reply! Could you give me a walkthrough on how to do this? Or point me somewhere that has one?
     
  4. jasonb1985

    jasonb1985 Well-Known Member
    98

    Jan 5, 2010
    987
    67
    98
    Radio Shack
    open /system/build.prop in Root Explorer in r/w mode, select text editor, edit the line below (change 231334 to 264707), then save it. That's all. Root Explorer makes a backup build.prop file automatically

    ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys

    Reboot twice and no more nag.
     
    mikeymcmikenson and tturner35 like this.
  5. trevolution23

    trevolution23 Member
    15

    Oct 21, 2010
    15
    0
    15
    what does it mean if that number was already changed
     
  6. tturner35

    tturner35 Member
    Thread Starter
    5

    Mar 16, 2010
    6
    0
    5
    Worked without any issues! Thanks!
     
  7. Hushling

    Hushling New Member
    5

    Jun 29, 2010
    2
    0
    5
    I have the same problem except I'm currently running on 2.1 and I'm content on using that firmware. When I looked at the numbers via Root Explorer, I have: 161494, as opposed to 231334 like you posted. Will the new number you wrote work for 2.1 as well? I greatly appreciate your help
     
  8. jasonb1985

    jasonb1985 Well-Known Member
    98

    Jan 5, 2010
    987
    67
    98
    Radio Shack
    it should.
     
  9. teacha6141

    teacha6141 Member
    15

    Apr 30, 2010
    22
    0
    15
    I have tried several times now to edit the file, each time asking me if i want to save and continue i say yes only to find after rebooting, that the file remains unchanged? in root explorer, the file also has a line above which also references the 231334 number, does that need to be changed also..??what am i doing wrong that the file remains unchanged??Thanks....
     
  10. yojoe600

    yojoe600 Well-Known Member
    143

    Apr 14, 2010
    2,188
    207
    143
    College Student
    NC
    hit save and exit.... it seems to work better!
     
  11. teacha6141

    teacha6141 Member
    15

    Apr 30, 2010
    22
    0
    15
    sorry, did exactly as you said, still file remains the same.. numbers are unchanged.could it be the ROM i have installed?? I am using the Uncommon Sense?
     
  12. Pamela

    Pamela Active Member
    15

    Aug 16, 2009
    28
    0
    15
    my phone freezes and reboots after saving and exiting out of the text file :(
     
  13. ske714

    ske714 Member
    16

    Dec 1, 2010
    21
    2
    16
    I'm sure Jason's fix is more direct, but as an alternative, I renamed this file...

    /system/etc/security/otacerts.zip

    ...and no more nags. Someone else with a custom rom said they couldn't find the file, so maybe not in your case either.
     
  14. turbomentor

    turbomentor Well-Known Member
    38

    May 14, 2010
    136
    17
    38
    Navy Pilot
    Pace FL
    I renamed this file using Root Explorer. However, I am still getting OTA nags.

    Time for the big gun: I guess it's time for a new ROM.
     
  15. ske714

    ske714 Member
    16

    Dec 1, 2010
    21
    2
    16
    Sorry, it worked for me and whoever it was I got the tip from. The only thing I can think of that may be different is that after I renamed the file, I accepted the update, knowing it would fail due to the missing bloatware it was trying to update. After it failed it never came back.

    From some of the other posts in this thread, a different rom may not stop it. Did you try editing the build.prop file as Jason suggested?

    Also note that the release of a fixed Unrevoked tool is eminent. When that happens you can just accept the update and re-root.
     

Share This Page

Loading...