1. Check out our companion app, Forums for Android! Download from Google Play

Root Got rid of the OTA update nag

Discussion in 'Android Devices' started by stevejobs, Nov 12, 2010.

  1. stevejobs

    stevejobs Member
    Thread Starter
    6

    Oct 17, 2010
    8
    8
    6
    This is on the xda forum, though some of the suggestions for editing the build.prop file are more complicated. YMMV and you may brick your phone.

    I opened /system/build.prop in Root Explorer in r/w mode, selected text editor, edited the line below (changed 231334 to 264707), then saved 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

    Rebooted twice and no more nag.

    Edit: I'm on Skyraider 3.3.3
     

    Advertisement

  2. rocke

    rocke Member
    15

    Apr 8, 2010
    21
    0
    15

    I tried this using root explorer but when I try and open the text editor, it tells me it is a read only file and won't allow me to edit it. I also tried to edit it outside the system folder but it won't let me move that file into the system folder. Tried the same thing in Astro with the same result.

    What am I doing wrong.
     
  3. b1gg134

    b1gg134 Well-Known Member
    43

    Apr 11, 2010
    172
    25
    43
    Horseheads, NY
    you need to use r/w mode in Root Explorer.
     
  4. winstonoboogie

    winstonoboogie Well-Known Member
    16

    Apr 17, 2010
    68
    5
    16
    Thanks for this.

    Do you guys happen to know what those numbers, 231334 and 264707, refer to? I'm just wondering what exactly this changes, in case I need to revert.

    I like that Root Explorer creates a backup file.
     
  5. kjjb0204

    kjjb0204 Well-Known Member
    38

    Aug 22, 2010
    278
    23
    38
    Pretend I'm not very smart - exactly how do I access Root Explorer in r/w mode? I don't even know what root explorer is.

    Edit - never mind. I'm not very smart, but even I can do a search.....
     
  6. msjulie

    msjulie Well-Known Member
    16

    Mar 14, 2010
    87
    9
    16

    I have a stock rooted phone, used adb pull, edited the file, pushed it back (confirmed change by repulling), and even after 2 reboots the thing is nagging me. Sigh..

    Hmm..
     
  7. upther

    upther Well-Known Member
    53

    May 7, 2010
    456
    61
    53
    Micco, FL
    You don't even need to go through all that trouble. If you're rooted and using a custom rom, just click the install button. It will countdown towards a reboot and then do nothing. Just reboot manually and the nag is gone. Nothing gets installed, nothing is missing, and I still have root.
     
    mykela25 likes this.
  8. NYCNsciGuy

    NYCNsciGuy Member
    16

    Aug 16, 2010
    10
    1
    16
    Graduate Student
    New York
    I actually tried that last night upther, and my phone went nuts...the countdown stalled, I had to plug in to an outlet to reboot, and on reboot several programs were missing (after which I restored my handy nandroid backup :)

    Not sure what happened there (probably something to do with my personal ROM tweaks I'm sure!) but the above method appears to be holding so far for me after a single reboot! Btw, I'm still new to this and am very curious what the numbers I just changed actually mean? Any ideas?
     
  9. eflosd

    eflosd Active Member
    16

    May 17, 2010
    37
    2
    16

    hmm i guess i should try this method?
    im on SR vanilla also. king kernel bfs #3
     
  10. gleckie

    gleckie Member
    6

    Nov 10, 2010
    8
    1
    6


    Stevejobs: will this work with the stock ROM? Thanks?
     
  11. msjulie

    msjulie Well-Known Member
    16

    Mar 14, 2010
    87
    9
    16
    Based on my luck, no. My rom is stock, just rooted and still naggin me
     
  12. snoggish

    snoggish Member
    16

    May 14, 2010
    24
    5
    16
    Yes it does. I'm running stock 2.2, rooted using unrevoked3, s-off. I did the same thing, but an easier way (if you have Root Explorer):

    Still does the same thing as the method above, but it's less of a headache. Rebooted, it said my system was up to date, annnd I all my apps and stuff works fine.

    Even if you're rooted, your stock rom isn't up to date. That act of rooting doesn't apply updates or get rid of update notifications.
     
  13. msjulie

    msjulie Well-Known Member
    16

    Mar 14, 2010
    87
    9
    16
    Mine was a brand new 2.2 from verizon which I rooted (after my original 2.1 updated to 2.2 phone met an untimely death)

    I got rid of the nag with some adb hacking about
     
  14. hnk

    hnk Member
    5

    Nov 14, 2010
    5
    0
    5
    I'm assuming there isn't any way to get it on skyraider until it gets patched?
     
  15. gleckie

    gleckie Member
    6

    Nov 10, 2010
    8
    1
    6
    I ended up just hitting the Install button on the update notification. A reboot message appeared for a few seconds and then my home screen appeared. That was it. No more nagging update notification and all settings and apps remain unchanged.
     
  16. snoggish

    snoggish Member
    16

    May 14, 2010
    24
    5
    16
    What are you running?
     
  17. ACD168

    ACD168 Well-Known Member
    143

    Apr 30, 2010
    1,885
    162
    143
    I just tried this on SR, the first reboot it was still there, second reboot, gone. not even in the about phone check for updates anymore. nice find.
     
  18. rman18

    rman18 Active Member
    16

    Jul 11, 2010
    41
    3
    16
    New Jersey
    Probably the Sense build number.
     
  19. eflosd

    eflosd Active Member
    16

    May 17, 2010
    37
    2
    16
    i did this to and it worked!
    sr 3.0 vanilla
     
  20. hookem

    hookem Well-Known Member
    43

    Dec 21, 2009
    416
    44
    43
    TEXAS - AUSTIN
    I was trying out SR and did this too, but then couldn't get into recovery. Undid the change, nandroided back to Uncommon Sense and the noti is back on. About to go back on miui.
     
  21. ACD168

    ACD168 Well-Known Member
    143

    Apr 30, 2010
    1,885
    162
    143
    if you couldnt get into recovery howd u nandroid back?
     
  22. dscribe

    dscribe Well-Known Member
    93

    Jun 8, 2010
    818
    140
    93
    Camden, AR, USA
    I think he said he first undid the build.prop edit. Then he could get back into recovery.
     
  23. hookem

    hookem Well-Known Member
    43

    Dec 21, 2009
    416
    44
    43
    TEXAS - AUSTIN
    Deleted the edited build.prop file. Renamed the original, that Root Explorer automatically renames and saves, back to the original name.
     
  24. gleckie

    gleckie Member
    6

    Nov 10, 2010
    8
    1
    6
    Unrevoked root only. Stock everything else.
     
  25. Kubla

    Kubla Active Member
    15

    May 1, 2010
    28
    0
    15
    Construction Management
    California
    I followed the instructions above, made sure the change from 321334 to 264707 had been made, rebooted twice, then rebooted in hboot twice, but the nag is still on my phone and it acts like nothing changed.
    Has anyone had this experience and if so, how was it solved?
     

Share This Page

Loading...