I'm rooted, and installed the version of Gingerbread that was available to incredible users a few months ago. Now, my phone is asking me to update again. However, I plan on getting the Galaxy Nexus when it comes out, and I don't want to risk breaking my phone with the official upgrade.
I have a "System update available" message in my Notification bar, and every time I unlock the phone it asks if I want to update. Is there any way, other than upgrading, to make those messages go away? I think the last time this happened with a FroYo upgrade there was a file I could modify, but I don't remember the details.
Little more info for anyone wanting to help with the build.prop edit:
Back on Froyo, these were the instructions I posted: -Open Root Explorer and make sure you're mounted as Read/Write -Navigate to /system and long press on build.prop, then select the "Open in text editor" option -Find the line that contains "FRF91/XXXXXX:user..." and replace that 6 digit number with 264707 -Then hit Menu > Save and exit -Reboot
Quote:
Originally Posted by iowabowtech
Ok guys, I checked my own build.prop from the "Stock Plus" rom and I may be able to infer the rest. If anyone wants to try (backup first), edit to this:
I think that might do the trick. If you still see the nag in the notification bar when you reboot, swipe down the bar and either try clearing it or press on it, then use the "back" button and see if that gets rid of it. I remember that happening on 2.2 but then it went away for good after that.
2 users report it working. All credit goes to iowa, of course.
The Following 4 Users Say Thank You to mmolitor87 For This Useful Post:
2 users report it working. All credit goes to iowa, of course.
And you! It did the trick for me. I waited for a day, no update nag. This DINC is gonna stay on 2.2 till I get another phone, maybe next year or something.
Mmolitor87 thank you for posting above, worked like a charm. Nag went away as soon as I changed line in root explorer. Thanks to Iowa also, I'm smiling again.
I'm gonna show my ignorance and just ask...is root explorer something from the market or is it native to the dinc? tia...I'd like to use the instructions above but am not sure how to get started...
I'm gonna show my ignorance and just ask...is root explorer something from the market or is it native to the dinc? tia...I'd like to use the instructions above but am not sure how to get started...
Root explorer is in the market (it's a paid app).
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
ok, so I'm rooted 2.2 with Virtuous ROM...I suppose I'd use info from second quote box above for latest 2.3.4 update?? Thanks....
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.3.4/GRJ22/222219:user/release-keys
Device(s): Droid Razr, BN Nook Color (running CM 7). Formerly Droid Incredible I and Samsung Behold II (POS).
Carrier: Not Provided
Thanks: 287
Thanked 595 Times in 411 Posts
Quote:
Originally Posted by droidhunter
Does it really work as well
It's how I did it.
I think this is the steps I did (this is something I only do about twice a year, so I have to figure out each time)
1. open ES File Explorer, go into menu>settings. Change home directory to / and check Root Explorer AND mount file system under root settings
2. back all the way out of the app, and load it again from the applications folder.
3. scroll down to the build.prop file, long press and select properties. Hit the change button and make sure everything in the "write" column is selected. hit ok.
4. tap on build.prop and open it in ES Note Editor, scroll down till you find the "ro.builb.fingerprint" line and edit it to match
(i just had change the numbers right before the :user/release-keys to 222219, but you're rom may be different).
5. when that's done, hit menu>save. Then exit. Restart the phone.
6. post on here about how it didn't work, and I'll try and work it through with you.
Last edited by euph_22; November 22nd, 2011 at 03:25 PM.
The Following 3 Users Say Thank You to euph_22 For This Useful Post:
Worked like a charm!!! Notice was sitin there looking at me out of reboot, but I got a lil refresh icon up top and then the notice vanished! Thanks again!!
The Following User Says Thank You to droidhunter For This Useful Post:
I'm still getting the nag. I changed it yesterday at 12:27pm. I rebooted the phone after the change. I turned the phone off last nite and still get the nag this morning.
I also would like to stop the update message. I am afraid one of my children will hit update. I need my hand held on this. I am new to root. I rooted and downgraded to 2.2. Once I get a rom, which do you suggest, how do you proceed? I have read over and over this thread but it is over my head. Thank you.
Can I do this without buying root explorer?
Last edited by krisdr; December 2nd, 2011 at 06:35 PM.
I think this is the steps I did (this is something I only do about twice a year, so I have to figure out each time)
1. open ES File Explorer, go into menu>settings. Change home directory to / and check Root Explorer AND mount file system under root settings
2. back all the way out of the app, and load it again from the applications folder.
3. scroll down to the build.prop file, long press and select properties. Hit the change button and make sure everything in the "write" column is selected. hit ok.
4. tap on build.prop and open it in ES Note Editor, scroll down till you find the "ro.builb.fingerprint" line and edit it to match
(i just had change the numbers right before the :user/release-keys to 222219, but you're rom may be different).
5. when that's done, hit menu>save. Then exit. Restart the phone.
6. post on here about how it didn't work, and I'll try and work it through with you.
Worked perfect! I have rooted but stock sense rom.
Looks like that did it although I followed a different path to edit the file. I booted into CWM, essentially following the instructions here.
I used grep to find the fingerprint line:
grep "fingerprint" build.prop
I made a back up of build.prop:
cp build.prop build.prop.bak
Then used sed to change the line:
sed -i "s!2.2/FRxxx/xxxxxx!2.3.4/GRJ22/222219!"
Then I double checked it by running the grep command again, saw the change and then rebooted. No more nag!
Device(s): Droid Razr, BN Nook Color (running CM 7). Formerly Droid Incredible I and Samsung Behold II (POS).
Carrier: Not Provided
Thanks: 287
Thanked 595 Times in 411 Posts
Quote:
Originally Posted by krisdr
What is build.prop? I have seen it on several comments?
It's a text file that stores various data about the hardware and software configuration of your phone (the build properties, hence build.prop). You're stopping the notification by changing the file to say it already HAS the update.
The Following User Says Thank You to euph_22 For This Useful Post:
Device(s): Droid Razr, BN Nook Color (running CM 7). Formerly Droid Incredible I and Samsung Behold II (POS).
Carrier: Not Provided
Thanks: 287
Thanked 595 Times in 411 Posts
Quote:
Originally Posted by krisdr
Is it possible to do it without buying root explorer? If so how?
Yes.
Quote:
Originally Posted by euph_22
It's how I did it.
I think this is the steps I did (this is something I only do about twice a year, so I have to figure out each time)
1. open ES File Explorer, go into menu>settings. Change home directory to / and check Root Explorer AND mount file system under root settings
2. back all the way out of the app, and load it again from the applications folder.
3. scroll down to the build.prop file, long press and select properties. Hit the change button and make sure everything in the "write" column is selected. hit ok.
4. tap on build.prop and open it in ES Note Editor, scroll down till you find the "ro.builb.fingerprint" line and edit it to match
(i just had change the numbers right before the :user/release-keys to 222219, but you're rom may be different).
5. when that's done, hit menu>save. Then exit. Restart the phone.
6. post on here about how it didn't work, and I'll try and work it through with you.
There you go.
Add step 0. Download ES File Explorer from market
The Following User Says Thank You to euph_22 For This Useful Post:
Well I'm having an interesting problem. Any changes I make to the build.prop do not save after a reboot. I make all the changes to the build.prop as per the instructions, reboot, and anything I changed in the build.prop has changed back to what it was before I made changes.
I am using ES File Explorer and have mounted both the system directory and the build.prop as writable. The rom I am using the stock 2.3.4 from Verizon, rooted of course. I am also still s-on. Could this be part of the problem?
__________________
Quote:
Originally Posted by Remordere
If you don't have an iPhone, you don't have a iSheep brain.
HTC Incredible + HTC Inspire 4G + Viewsonic Gtab + Galaxy Nexus = A whole lot of Ice Cream
Well I'm having an interesting problem. Any changes I make to the build.prop do not save after a reboot. I make all the changes to the build.prop as per the instructions, reboot, and anything I changed in the build.prop has changed back to what it was before I made changes.
I am using ES File Explorer and have mounted both the system directory and the build.prop as writable. The rom I am using the stock 2.3.4 from Verizon, rooted of course. I am also still s-on. Could this be part of the problem?
I think being s-on is your problem, because you don't have full access to the system folder while booted, same reason why apps like metamorph and and adblocker don't work. You'd have to do the changes through adb while booted in recovery.
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
I think being s-on is your problem, because you don't have full access to the system folder while booted, same reason why apps like metamorph and and adblocker don't work. You'd have to do the changes through adb while booted in recovery.
Oh, ok. That's what I thought.
So editing the build.prop on my computer with a text editor like wordpad, then pushing it to the system directory over ADB while in recovery should work?
So editing the build.prop on my computer with a text editor like wordpad, then pushing it to the system directory over ADB while in recovery should work?
Correct!
The Following User Says Thank You to mmolitor87 For This Useful Post:
Great! Thanks! I'll give it a try in a couple of hours. Gotta go take a final right now.
EDIT:
Changed the build.prop, pushed over ADB, works perfectly now. No more update notification. I even went in and fixed the prop where it said my phone had a 4.3" screen, deleted the line about a front camera, and I am now working on getting the Sprint market to go away. Thanks again everybody!
Last edited by incredible x4; December 5th, 2011 at 10:44 AM.
Okay, I am so new to this root thing and I am learning what seems like a new foreign language so help me here. I went to settings and opened home directory. It currently says /sdcard/. What exactly am I to change it to. Am I to put in "/"?
I am not sure what this means ...check Root Explorer AND mount file system under root settings. I think I understand the directions after that. Please forgive my noobiness. I am probably old enough to be most of ya'll's mother. I am trying though. (BIG SMILE)
Device(s): Droid Razr, BN Nook Color (running CM 7). Formerly Droid Incredible I and Samsung Behold II (POS).
Carrier: Not Provided
Thanks: 287
Thanked 595 Times in 411 Posts
Quote:
Originally Posted by krisdr
Okay, I am so new to this root thing and I am learning what seems like a new foreign language so help me here. I went to settings and opened home directory. It currently says /sdcard/. What exactly am I to change it to. Am I to put in "/"?
I am not sure what this means ...check Root Explorer AND mount file system under root settings. I think I understand the directions after that. Please forgive my noobiness. I am probably old enough to be most of ya'll's mother. I am trying though. (BIG SMILE)
open ES File Manager. Hit the menu button, and select the settings option in the pop up. The the menu that comes up, you can change the home directory option, and at the bottom of the menu there is a Root Explorer section (check both of those options).
Sorry to bring up an old post, but I've been trying the "ES File Explorer" method here to disable my update notification. I have the original Incredible, rooted with unrevolked with s-off and original rom. I can follow the instructions here, but when I get to: "3. scroll down to the build.prop file, long press and select properties." ...I do not have a "build.prop" file. The only "prop" file I have showing is the "default.prop" file. I tried using that, but evidently that's not the correct file as I couldn't find the "ro.builb.fingerprint" line. I backed out and tried changing everything back to it's original state, but the "home directory" would not accept the "/sdcard/" entry. I can type "/sdcard" but when I try to add the last "/" on it, it changes to "/card/"... in other words, it removes the "sd" part of the entry. I tried clicking the OK button, and it gives me a notice that says... "Non-existing path" "..Cannot find the path you specified. Do you want to creat it?" If I click "OK", the notice goes away and takes me back to the ES File Explorer settings. I can then check in the "home directory" and it's still at "/", no "/sdcard/". So... What do I do to find the "build.prop" file? ...and how do I get the "Home directory" back to "/sdcard/" ? ...or do I want to get it back to "/sdcard/" ? So many decisions.... Thanks!
...and why is my post not showing up with the correct spacing for paragraphs? I tried making it easy to read, but it's all cramed togather in one big paragraph!
Thanks! The "build.prop" file was in the folder called "System" ! Completed the process and the update message went away :-) But... about the Home Directory... I remember it saying "/sdcard/" and not "/system". I noticed another poster saying the same thing, that her Home Directory said "/sdcard/". Do you have any ideal why? ...and do I need to change it to "/system" ? Because at the present it only shows the "/" that I changed it to before this process of ridding myself of the update message. ...and I still haven't figured out why my posts are all cramed into one big paragraph.
Thanks! The "build.prop" file was in the folder called "System" ! Completed the process and the update message went away :-) But... about the Home Directory... I remember it saying "/sdcard/" and not "/system". I noticed another poster saying the same thing, that her Home Directory said "/sdcard/". Do you have any ideal why? ...and do I need to change it to "/system" ? Because at the present it only shows the "/" that I changed it to before this process of ridding myself of the update message. ...and I still haven't figured out why my posts are all cramed into one big paragraph.
It doesn't really matter what your home directory is, it's just a personal preference when you start up the app.
Not sure why your posts aren't formatting correctly either... Are you posting from the web or the phandroid app?
Posting from my laptop I assume on the web. Don't know what the phandroid app is . I have Java turned off in case that might be the problem. Just paranoid, I guess :-) What exactly will happen with the "Home Directory" setting of "/" ? ...and just what is the Home Directory? Inquiring minds.... Thanks again!
Last edited by connortn; April 25th, 2012 at 07:56 PM.
Posting from my laptop I assume on the web. Don't know what the phandroid app is . I have Java turned off in case that might be the problem. Just paranoid, I guess :-) What exactly will happen with the "Home Directory" setting of "/" ? ...and just what is the Home Directory? Inquiring minds.... Thanks again!
The "home directory" is just the folder the app shows you by default when you start up the app. It doesn't modify anything in the phone, it is just an app preference. It's basically the equivalent of setting your home page in your Internet browser.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
Verizon is pushing another update. Anyone know how to make the nags stop for this update?
Not sure what number to use in the file edit such as the one from last time
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.3.4/GRJ22/222219:user/release-keys
Update is 4.08.605.15 getting the notifications since yesterday.
I assume you are rooted. It is now downloaded on you phone in a zip file. I believe I found mine in phone memory cache. I just deleted the zip file. No more notifications since. Pretty sure it will come again though. It was pretty easy to find it. It's on phone memory for sure.
Found this at another forum.
Change it to: verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys
I have a non-rooted Maxx running Android version 2.3.6 and want to know if I can use this method to block the auto-download/auto-update of the newly released ICS version of the OS. If so, which numbers string of numbers should I use?
I have a non-rooted Maxx running Android version 2.3.6 and want to know if I can use this method to block the auto-download/auto-update of the newly released ICS version of the OS. If so, which numbers string of numbers should I use?
You need to be rooted to block it.... but I highly recommend updating to ICS, it greatly improves the phone.
Don't let the reported bugs scare you.
Last edited by sdrawkcab25; July 2nd, 2012 at 02:29 PM.
Thanks. So assuming I'm rooted, what sequence of numbers do I need to replace/enter?
There should be a build.prop file in your system folder. You would need to change a sequence of numbers in that file to match what the current build number is.
I don't have a rooted razr at the moment but I'll see if I can access the file without root and report back what it should read.
There should be a build.prop file in your system folder. You would need to change a sequence of numbers in that file to match what the current build number is.
I don't have a rooted razr at the moment but I'll see if I can access the file without root and report back what it should read.
Stop update notification
All credit goes to iowa, of course.
worked perfectly!
