MD4 OTA Nag

May 26, 2011
6
0
0
OK I'm perfectly happy with my phone. Rooted with stock recovery. Minus a bunch of bloatware. I mostly just rooted for titanium nandroid and adfree. I was going to go through the trouble of manually updating since the OTA will not work for me. However I my GF has the same phone but stock. She did the update to MD4 and hates the sidebar has massive battery drain and has frozen to the point of needing a battery pull (which sucks with a Otterbox Commuter). We were both super stable with MD1.

Sooo my question: How do I stop the OTA nag? I don't want the update.
 
OK I'm perfectly happy with my phone. Rooted with stock recovery. Minus a bunch of bloatware. I mostly just rooted for titanium nandroid and adfree. I was going to go through the trouble of manually updating since the OTA will not work for me. However I my GF has the same phone but stock. She did the update to MD4 and hates the sidebar has massive battery drain and has frozen to the point of needing a battery pull (which sucks with a Otterbox Commuter). We were both super stable with MD1.

Sooo my question: How do I stop the OTA nag? I don't want the update.

open your build.prop. Edit any line ending in MB1 and change MB1 to MD4 then save and reboot
 
The sidebar is easy to turn off. You can long-press the back button, which will get rid of the little tab to pull it out. Or you can do the Settings / Display and turn it off there (I think that's true on the stock ROM.) Freezing and battery drain problems are probably most easily resolved with a factory reset, unfortunately.
 
You can also bypass this by just flashing the modem/radio updates from XDA threads.

I'm running MB1 rom with the MD4 modem/radio - no issues and I get good signal with this combo.
 
That sounds like a plan. I'm a noob, and try not to get in too deep. I like to keep it simple.

The freezing should also be stopped by rebooting into recovery and wiping cache. An OTA update is like a dirty flash of a ROM. In fact, you are flashing a ROM, just allowing the carrier to do it for you. Reboot into recovery is power down. Hold volume up, home and power at the same time (I find it easiest to hold the home and volume buttons first then power) until you see the samsung logo then release. After that you get a scren with a highlighted bar that can be moved by the volume rockers and using power to accept. Scroll down to wipe cache partition. This will only take 15 seconds at most. By default it will go back to the main page with reboot highlighted. Hit power, and that should help a lot.

What happens is the old data from the previous build or ROM gets in the way of the new one. This can cause stutters, and restarts cause the OS doesn't know what else to do so it figures a restart is the best course.

This same wiping of cache is used to make flashing of new custom ROMs run with fewer hiccups.
 

Trending Posts

Forum statistics

Threads
957,622
Messages
6,973,847
Members
3,163,866
Latest member
kevinthefirebender