System Update Message wont go away (rooted)

[wemetzger]

I received the over the air 4.1.2. When I clicked to update, it took my to custom recovery since I am rooted. I updated through that, and the recovery asked me to not flash the orginal revory and to keep rooted, which I accepted.

So, Now I have 4.1.2, which is great. I also tried my tethering app, which still worked granting super user permissions, so I assume I am still rooted.

However, I still keep getting that annoying message saying I need to update. Should I click through on it? Can I erase the file off my phone so it doesn't give me this anymore? If so, where is it?

 

[eldub1]

What ROM are you running?

 

[wemetzger]

No ROM here... plain old stock, and rooted just so I could tether. I rooted using skunkape60's instructions, and pretty sure I used Odin to get CWM.

 

[Skunkape60]

No ROM here... plain old stock, and rooted just so I could tether. I rooted using skunkape60's instructions, and pretty sure I used Odin to get CWM.

I can make you an updated build prop which will stop the update notifications. Or you could just flash the prerooted mb1 ROM and be completely updated.

 

[Ramer84015]

I can make you an updated build prop which will stop the update notifications. Or you could just flash the prerooted mb1 ROM and be completely updated.

That sounds interesting. If we are rooted, can we make a change to the build.prop file to stop any future OTA updates and then wait for you or someone else to post the update so we can flash it ourselves?

 

[Farsol]

I have a similar situation. First, thanks Skunk for the excellent assistance so far.

I am running WS v 1.2 from December. Bad timing on my part, missing 2.1 by a month. I started getting the Sprint OTA update this morning. So I used your dirty hack technique to update the radio firmware to to MB1. It was successful, but the presence of Android 4.1.1 seems to keep the Sprint Updater returning.

Should I move up to WS 2.1? If there was an easier way to update that ROM and my data, I might, but I just got it the way I like it.

Or would the custom Build suppress the notification?

Any advice?

 

[mobdad]

I have a similar situation. First, thanks Skunk for the excellent assistance so far.

I am running WS v 1.2 from December. Bad timing on my part, missing 2.1 by a month. I started getting the Sprint OTA update this morning. So I used your dirty hack technique to update the radio firmware to to MB1. It was successful, but the presence of Android 4.1.1 seems to keep the Sprint Updater returning.

Should I move up to WS 2.1? If there was an easier way to update that ROM and my data, I might, but I just got it the way I like it.

Or would the custom Build suppress the notification?

Any advice?

Like Skunk said, the OTA looks to your build.prop file. If it displays a ROM earlier than MB1 (Android v4.12), those OTA messages will keep on coming until you upgrade your custom ROM or update your build.prop file to reflect this change.

 

[Skunkape60]

I have a similar situation. First, thanks Skunk for the excellent assistance so far.

I am running WS v 1.2 from December. Bad timing on my part, missing 2.1 by a month. I started getting the Sprint OTA update this morning. So I used your dirty hack technique to update the radio firmware to to MB1. It was successful, but the presence of Android 4.1.1 seems to keep the Sprint Updater returning.

Should I move up to WS 2.1? If there was an easier way to update that ROM and my data, I might, but I just got it the way I like it.

Or would the custom Build suppress the notification?

Any advice?

Update to wicked 2.1 then flash the updated build prop that is posted in the thread. Note: the build prop is ONLY for Wicked Sensations 2.1. Do not flash it on any other ROM.

 

[Skunkape60]

That sounds interesting. If we are rooted, can we make a change to the build.prop file to stop any future OTA updates and then wait for you or someone else to post the update so we can flash it ourselves?

The custom build prop would be made to make the update think you are already on MB1. So it won't stop update notifications for any future updates (for example: MC7)

 

[wemetzger]

I flashed the MB! ROM, and everything is working fine now. Thanks alot!

 

[Farsol]

Skunk, I took your advice and went ahead upgraded to WS 2.1. Luckily with Titanium backup it was pretty seamless. I also upgraded the firmware to MB1, and used the Build prop to suppress the notices. Worked like a champ. Thanks!