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

Root Help with Nov. OTA update

Deweygroup

Deweygroup

Member
I just rooted last week. I'm new at this and learning as I go. I have not flashed any roms yet, just rooted. I have installed rom manager and titanium backup. My question is this. What should I do about the OTA update that started going out today. Do I need to do anything?
 
Did you get a notification for it? Generally when you are on a custom ROM you won't get the notification and even if you did try to install it then it would probably fail unless you rooted and left stock on there.
 
///tron\\\ said:
Well I am. Got an update 2 days ago.


Any ideas?
Click to expand...

to block the OTA:

you need to edit the /system/build.prop. find the line that begins with "ro.build.fingerprint" and change it to:

Code:
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys

Once rebooted, the nag might appear once more, but if you go to Settings->About phone->System updates you wil now get "your system is currently up to date".
 
Why would clockwork revocery fail an OTA. I've read on other posts that people with rooted phones have been getting the OTA if they are still on the stock ROM.
 
Flavy said:
Why would clockwork revocery fail an OTA. I've read on other posts that people with rooted phones have been getting the OTA if they are still on the stock ROM.
Click to expand...

If you are rooted, you are using a custom HBOOT.
You will still receive the OTA notification. After all, it is like a spam email that goes out to a few thousand recipients. Opting to install the update causes your phone to connect to the server and download the update payload.
But when your phone reboots (to install the update), the custom HBOOT refuses to install it.

That is, IF the update is an upgrade to the OS.
If the update is just app and/or configuration updates (which I think this one is), there is no need for the phone to reboot and for HBOOT to do its thing. So, the app upgrades WOULD get installed.
 
Ed Zachary said:
If you are rooted, you are using a custom HBOOT.
You will still receive the OTA notification. After all, it is like a spam email that goes out to a few thousand recipients. Opting to install the update causes your phone to connect to the server and download the update payload.
But when your phone reboots (to install the update), the custom HBOOT refuses to install it.

That is, IF the update is an upgrade to the OS.
If the update is just app and/or configuration updates (which I think this one is), there is no need for the phone to reboot and for HBOOT to do its thing. So, the app upgrades WOULD get installed.
Click to expand...

Gotcha.


Is this going to cause any unforeseen issues?
 
jasonb1985 said:
to block the OTA:

you need to edit the /system/build.prop. find the line that begins with "ro.build.fingerprint" and change it to:

Code:
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys

Once rebooted, the nag might appear once more, but if you go to Settings->About phone->System updates you wil now get "your system is currently up to date".
Click to expand...

Thank you! I didn't feel like jumping through all the hoops to install this OTA on a rooted phone for no meaningful gain, and this appears to have gotten rid of the update notifications. :)
 
I want the update to install on my stock rooted phone but some of the instructions seem to be missing steps that I don't know what to do and needless to say it failed. Can anyone please help. I really want these issues fixed and i love the stock Rom. Thanks for the help.
 
You must log in or register to reply here.
Back
Top Bottom