[Q] Still asking for update on 1.8.3 and gingerblur 3.5

[roughriduz]

So i have flashed back to both 1.26 and 1.57 then went OTA to 1.83 and i have also flashed 1.83 and then rooted installed gingerblur and i still have the update notification. i have looked at the build.prop and it tells me i am on 2.2.2 and at 4_1.8.3. Has anyone found out how to fix this without freezing the updater?

 

[joyo22]

So i have flashed back to both 1.26 and 1.57 then went OTA to 1.83 and i have also flashed 1.83 and then rooted installed gingerblur and i still have the update notification. i have looked at the build.prop and it tells me i am on 2.2.2 and at 4_1.8.3. Has anyone found out how to fix this without freezing the updater?

This has been discussed several times in several forums. Just freeze "Updater 2.2.2" in Titanium Backup and the message won't show again.

Search tool is your friend

 

[CaelanT]

Freezing will prevent future updates, as the updater will keep telling you to update to 4.1.83 after you thaw it before it will allow you to OTA to next update. While this may not be an issue if a sbf file comes out for the next OTA, it will be an issue if there is not one available for a while after the OTA goes beta and live.

I flash back to 4.1.26, then OTA to 4.1.57 and 4.1.83 before rooting and installing the "ROM" of choice and have not seen this issue. Most posts I have seen relating to this are after people have flashed the 4.1.83 sbf.