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

Root [Boost Mobile] How to: Stop Update Notification

mydian

Android Expert
Apr 8, 2012
1,427
679
Chicagoland
Update: To block the update notification follow the information below but use the build # L710VPUCOJ1 instead of L710VPUBMK5.


This guide was originally written for the Boost Mobile Galaxy S3 SPH-L710 (d2vmu) however if you know the correct build number you can technically use it to stop the OTA update nag for any device.

I figured there are others like me avoiding the MK5 4.3 update so I thought I would post how to stop that annoying notification once and for all. There are other methods that say to freeze this app or rename this file but both those methods mess up other things. The correct way is to modify your build.prop.

The following instructions are how to modify the build.prop manually but there also are build.prop editors you can use. However I've never really messed with any so i won't be able to provide much help if you have a problem. If you use a build.prop editor then you only need to look at steps 1, 4, 5 & 6. Please make a backup with a custom recovery first.


I am not responsible if you brick or damage your phone! I have done this mod successfully on my phone and my old phone when I wanted to block it's OTA. I can't stress enough how important it is to make a backup before modifying /system! While there are quite a few steps listed below this is a pretty simple process. Basically all you need to do is copy a file, edit 2 words (sort of), rename the old file (to create a backup), then replace it with the new edited version.

1. Boot into recovery and make a backup! This is very very important even if you are using a build.prop editor. If you modify your build.prop incorrectly you could end up stuck in a boot loop. After you make a backup restart back into Android.

2. Using your favorite root explorer (I use ES File Explorer) navigate to /system and copy your build.prop to your sdcard.

3. Open the build.prop in a text editor (I use the one built into ES File Explorer.)

4. Scroll down 10 lines or so. What you're looking for is the 2 lines after:
# Do not try to parse ro.build.description or .fingerprint
I find it easier to look for that line.

5. The 2 lines you need to edit are one right after the other:
ro.build.description=d2vmu-user 4.1.2 JZO54K L710VPAMG2 release-keys
ro.build.fingerprint=samsung/d2vmu/d2vmu:4.1.2/JZO54K/L710VPAMG2:user/release-keys
6. Next replace L710VPAMG2 with L710VPUBMK5 in both lines. When you're done it should look like this:
ro.build.description=d2vmu-user 4.1.2 JZO54K L710VPUBMK5 release-keys
ro.build.fingerprint=samsung/d2vmu/d2vmu:4.1.2/JZO54K/L710VPUBMK5:user/release-keys
7. Make sure system is mounted as writable.

8. Navigate back to /system.

9. Rename your old build.prop found in this directory to build.prop.bak (it's always good to have backup!)

10. Copy your newly modified build.prop to /system

11. Check the permissions for your new build.prop. I had to add the read permission for group and other (it should be 644).

12. Navigate to /cache and delete the OTA update. It should be a zip file with a real long file name. The file name for me ended with MG2_to_MK5_Update_FWD.zip. On my S3 it was the only zip file in that directory.

13. Make sure system is no longer mounted as writable.

14. Reboot your phone. After first boot if the OTA notification is still present just swipe it away from the notification shade (don't click on it.)

And that's it. I haven't had any update notification for 2 days now.

This should work with any rom (and any carrier) but if you're running a Sprint rom the build # you're changing may look different. Also if you have a custom rom there may already be a flashable zip to fix your build.prop. Moar & Wicked Sensations both have zips.

One other thing. Only change the build # in the 2 lines that are posted above. Changing Android version numbers or the build # in other places could cause unwanted results. For example, if you go to settings, about phone, you'll notice it still says MG2 after this fix. But Boost thinks you're on MK5. ;)

Enjoy!
 
Last edited:
I cleaned it up some so it should be easier to read. I swyped that at work using Evernote and then copied and pasted it lol.

I second that, nice tutorial for a problem that I am seeing reported by users left and right.

Thanks I saw a couple posts today asking how to block the update so that's what prompted me to do it. Especially since it's pretty easy to do.

Nice write up :D

Have you tried putting it in a flashable zip file? :thumbup:

Thanks. I thought about it, or even just posting the build.prop but that would only work for the stock rom. This fix should work for every Sprint 4.1.2 TW rom. That and I don't know how to make a flashable zip. :eek:
 
Upvote 0
I cleaned it up some so it should be easier to read. I swyped that at work on my phone using Evernote and then copied and pasted it lol.



Thanks I saw a couple posts today asking how to block the update so that's what prompted me to do it. Especially since it's pretty easy to do.



Thanks. I thought about it, or even just posting the build.prop but that would only work for the stock rom. This fix should work for every Sprint 4.1.2 TW rom. That and I don't know how to make a flashable zip. :eek:

Flashable zip creation is a skill I would like to learn as well! However, it would do a lot of people good, especially those who are more noob than expert, to get "hands-on" with some things and know more of the nuts and bolts associated with being rooted. I am no expert on the technical side, not by a long shot, but I can do all the most important things myself without a "one-click" or third-party solution that just does it for me and I hope it works without bricking my phone. At least if my phone does get screwed up I can blame myself for not following instructions, and that is the way I prefer it!
 
Upvote 0
There is also a sure fire easy way to disable the nag with a file I use that also stops the ota nag. The file is called FOTAkill.apk.

If your rooted just place this file in system/apps folder and reboot. Once rebooted it should not nag you again.

I find this way much easier to do than editing a prop file as it take a single move and a reboot. Not that the editing the prop file doesn't work, just for me, it's less work and step this way.
 
  • Like
Reactions: mydian
Upvote 0
That's strange since I have done this to my phone to stop the latest update notification and it worked fine. Did you remember to set the permissions?
I know I did something wrong. Just can't figure out what. ES file explorer showed system properties set as rwx-rwx-rwx. I must have changed this previously so I left it that way. Build.prop was set to rw-rw-rw. Just the two lines were edited with ES editor. I'll try again when I have some time but am a little nervous. This was my first soft brick.
 
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