• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Got rid of the OTA update nag

stevejobs

Lurker
Oct 17, 2010
8
8
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
 
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


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.
 
Upvote 0
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


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..
 
Upvote 0
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?
 
Upvote 0
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.


hmm i guess i should try this method?
im on SR vanilla also. king kernel bfs #3
 
Upvote 0
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



Stevejobs: will this work with the stock ROM? Thanks?
 
Upvote 0
Stevejobs: will this work with the stock ROM? Thanks?

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):

if you press-hold the build.prop in Root Explorer you can "Open in Text Editor". The only thing that needs changed is the six digit number: "FRF91/XXXXXX:user..." replace that six digit number with 264707, save and exit, reboot. My notification was still up after I rebooted, however after tapping on it and hitting back, I got it to go away.

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.

Based on my luck, no. My rom is stock, just rooted and still naggin me

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.
 
Upvote 0
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

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.
 
Upvote 0
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.

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.
 
Upvote 0
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

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?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones