How do we block OTA updates on the newest update? - Droid RAZR M Q&A, Help & Troubleshooting

I've frozen Updater_4.1.2 in Titanium. I've also renamed BlurUpdater.apk and BlurUpdater.odex in System using root manager.
If I click on about phone, check for updates, it still checks for them. In the old version it would just flash something up and go back to the About Phone screen since the updater was disabled.
Any ideas?

Coronado is dead said:
I've frozen Updater_4.1.2 in Titanium. I've also renamed BlurUpdater.apk and BlurUpdater.odex in System using root manager.
If I click on about phone, check for updates, it still checks for them. In the old version it would just flash something up and go back to the About Phone screen since the updater was disabled.
Any ideas?
Click to expand...
Click to collapse
BlurUpdater is actually for updating the phone, not checking the update. I removed all blur-related services so mine won't check for update.
Try messing around with "ro.build.version.full" or other version strings in build.prop if you don't want to do that.

Can someone please clarify what's needed to be done to block the OTA update from automatically downloading/installing? Do we need to rename BlurUpdater and then freeze all Blur services? Or do we need to freeze Updater 4.1.2 as well? Both user's that replied seemed to do a couple different things, so I am wondering what actually will work? Thanks!

Related

How do you block OTA updates?

I would like to keep root and do not want to take the next ota update from big red when it drops. I was told that this would stop update
"in /system/etc/security/ change the files
otacerts.zip
cacerts.bks
to
BAKotacerts.zip
BAKcacerts.bks"
But when I tried the phone just gets stuck in a boot loop. I went back in and reversed it and the phone boots fine. Does any one know of a way I can block updates while keeping my stock rom?
root
Sent from my Incredible using XDA App
Yes, now how can I keep it with out applying a new rom?
jett2314 said:
Yes, now how can I keep it with out applying a new rom?
Click to expand...
Click to collapse
This thread, along with so many others here, has nothing to do with development.
That being said, you remove/rename the otacerts.zip file once rooted, you don't need a rom or anything.
Thank you for your reply. As previously stated I have root and have tried to rename the otacerts.zip file, but the phone would not boot after that. Do you feel that just changing otacerts.zip would work? What is the cacerts.bks used for? I'll be sure to post in the correct form next time.
jett2314 said:
Thank you for your reply. As previously stated I have root and have tried to rename the otacerts.zip file, but the phone would not boot after that. Would like to know if any one knows of a way that works to block ota updates until a rom that has every thing I need working on a daily bases comes out. I'll be sure to post in the correct form next time.
Click to expand...
Click to collapse
Actually what you said is you renamed otacerts and cacerts. The phone needs cacerts, it's how it does all the certificate checking; it doesn't need otacerts, which is to check the certificates specific to the ota releases
BossMafia2 than you for your help. I have changed the otacert.zip (mv /system/etc/security/otacerts.zip /system/etc/security/BAKotacerts.zip) with out any booting issues. I'll have to wait and see if that blocks any future updates.

Android 2.3.2 System Update

I just got a prompted notification that 2.3.2 system update is now downloaded and verified in my phone. Just need to go ahead and ok the install/update on my phone. Not sure if most or all are getting this?
Should I? LOL
more info:
"Android 2.3.2
601kb
This system update from Google contains important bug fixes."
Go for it.
This is probably the update that includes the major SMS bug fix. Samsung posted to their official twitter account that and update to address that is coming very soon.
It looks like v2.3.2 is the one.
Funny thing though, I never had problems with the SMS bug. I have sent/received SMS (2k+). And when I got the notification, I just pulled the battery off to check my S/N to register in the Samsung website. LOL
Is there any other bug/fixes with this updates other than the SMS bug?
If you're rooted, you might want to wait and see if it's safe to do it (ie., doesn't break root) unless you're confident on how to get it back. The last update screwed with Recovery and gave some people some slight grief for a short period.
Just rooted
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Just rebooted after update, seems that at least the browser got some kind of lagfix, for example www.n4g.com.
"Your system is currently up to date."
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Without thinking I chose to install it while being rooted and not backing up. After it rebooted it froze (when it couldn't find a recovery I'm guessing.) I pulled the battery, let it reboot, and I'm still 2.3.1 and rooted. Just FYI
AllGamer said:
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Click to expand...
Click to collapse
Often one have to wait untill the devs implement the update into the custom rom.
Generally once you're on a custom rom, you're best to wait for the rom dev to give you guidance.
treodoc said:
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Click to expand...
Click to collapse
Not sure without being able to open the update file and see what it actually does.
IF you're going to try it. Have a nandroid backup made of your system as it is right now, and have a copy of CWM recovery handy to reflash via fastboot.
You'll probably have to re-root if you can even get the OTA to stick (like the one post above that says it didn't...)
so, back to stock recovery before update?
swype
FYI, swype did not work after update, had to reinstall, now works fine.
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Would those of you who get it, if you have a chance, please run the logcat on your phone BEFORE updating and try to catch the url so we can get a manual link for it:
in order to extract the url for the system update, we need to run alogcat from the market, then when the update notification appears look in your logs for a url that says something like clients.google . You can install alogcat, then set filter to clients.google
Click to expand...
Click to collapse
Phantom1275 said:
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Click to expand...
Click to collapse
You can try to check in. *#*#2432546#*#*
it just says that checkin succeeded on notification bar and that's all... No updates...
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
krohnjw said:
You can try to check in. *#*#2432546#*#*
Click to expand...
Click to collapse
That's the check I have mentioned.
Still nothing. Guess I have to wait.
Trinitronik said:
it just says that checkin succeeded on notification bar and that's all... No updates...
Click to expand...
Click to collapse
It's going to roll out slowly, just like the 2.3.1 and Market updates did. I don't think all the checkins in the world will speed it up by any significant amount.
What we impatient types need is someone who is offered the update to grab the url so we can just manually download it.
Udaw said:
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
Click to expand...
Click to collapse
No one knows yet! Have to get it to see what it changes (breaks).

4.5.91 OTA "not available"???

I was not planning on installing it but i am wondering why the phone is not even finding it.
I'm on 1.83, locked BL, rooted (gingerbreak), a few mods like sideloading, tethering, webtop, etc. And a few frozen sys apps that i did unfreeze but still not finding the update?
Have you tried the SD card option?
http://www.motorola.com/Support/US-EN/Atrix Upgrade/Atrix-Gingerbread-Update
gnahc79 said:
Have you tried the SD card option?
http://www.motorola.com/Support/US-EN/Atrix Upgrade/Atrix-Gingerbread-Update
Click to expand...
Click to collapse
I realize i have different options, just confused as to the simple OTA is not working. I heard that if the files are modded and so on that update will not install, but my phone is not finding an update period.
Are you on WIFI? I believe it is required.
demens13 said:
I realize i have different options, just confused as to the simple OTA is not working. I heard that if the files are modded and so on that update will not install, but my phone is not finding an update period.
Click to expand...
Click to collapse
No idea.
Using the official SD card option is equivalent to downloading the OTA through your phone. It's the same image file from moto. Better IMO if you've modded your phone and if you need to retry the update. With the download through your phone route I think the update file needs to be re-downloaded if the update fails for whatever reason. With the SD card route the update image stays on your sd card after reboot/update failure. Be sure to delete it after the update is applied as stated in the instructions.
I had a similar issue as well. When checking for updates my device reported "check for update was not available at this time" whether or not the update was actually available. In order to get it to come up I had to go to settings, data manager, data delivery, social applications and then uncheck sync over wifi only. I'm not sure why this mattered but after I restarted the phone and checked for updates it found it.
Hope this helps.
jruweaver said:
Are you on WIFI? I believe it is required.
Click to expand...
Click to collapse
DING
"Not available" is the error you get when the phone is not on Wi-Fi and you attempt to check for updates.

[info] new ota 6.2.2/6.3 update from amazon and how to prevent

hallo guys
just saw that amazon is pushing the next OTA - 6.2.2
this time i could again verify this method to prevent the OTA:
i deleted /system/etc/security/otacerts.zip - watched the update downloading to the cache folder but did not install - after a reboot the update file was disappeared from the cache folder - i was registered at amazon all the time - and i'm still on 6.2.1
this worked for me - no guarantee
update: worked with 6.3 again !
I assumed the file needs to be permanently removed based your post, but I renamed them to keep them around (I am glad I did)
I did what you recommended and then I rebooted (renamed instead). Once I rebooted though, GMail would crash everytime I tried to use it and the Market said it could not connect. Once I put those files back and reboooted they worked again. So any other ideas would be appreciated.
... but I renamed them to keep them around ...
Once I put those files back and reboooted they worked again
Click to expand...
Click to collapse
yes - as i wrote - i deleted otacerts.zip (only this one) from /system/etc/security/ (renamed and moved to sdcard)
i'm using the android market without any problems
sorry had a typo with the filename !
I only see cacerts.bks and otacerts.zip. Which did you delete?
sorry it is a typo - thank you !!!
it is otacerts.zip !!!
will correct the post - again thanks !
Anyone have any details about the update? What's new?
i think it's too new for detailed information and don't know cause it did not install
but i'm shure detailed information will be availabe in the next days
as well as a pure update version as it was with 6.2.1: http://forum.xda-developers.com/showthread.php?t=1407852
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
DalekCaan said:
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
Click to expand...
Click to collapse
don't know - sorry - but for me it's the second update i survived
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
It should wipe everything.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
podspi said:
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
Click to expand...
Click to collapse
The OTA updates thus far typically overwrite the filesystem, so yes it would knock out recovery. You can use a "patched" ROM that will not touch the partition the recovery data is on.
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
jshaw49 said:
Anyone have any details about the update? What's new?
Click to expand...
Click to collapse
One thing I've noticed is that it mounts a lot faster when attached to my PC via USB. On 6.2.1, it mounted in about 10 seconds. Now it does it in less than 2.
DesDr0id said:
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
Click to expand...
Click to collapse
Thanks for this. Exactly what I was looking for (I'm fairly new to rooting).
Sent from my Kindle Fire using xda premium
Just wanted to say that I tried this, and as far as I can tell it worked like a charm. I even tempted fate by hitting 'Sync', but my Kindle refused to update (it wouldn't even attempt to download the update from device settings).
I just flashed the pre-rooted 6.2.2 update and deleted otacerts.zip, so here is hoping they didn't change something to make this not work...
i'm glad that it is working for you too ...
I just wanted to add that I have been blocking the OTA update using Droid Wall. Still running very happy on 6.2.1.
The only down side to this method is having to set permissions initially then updating Droid Wall as I install apps.
Meh. I'm not sweating this update much.
I've still got the Market, still have Swype... Sooooo far as I can tell the only thing I lost is Google Currents, which I wasn't finding much useful since the KF doesn't seem to want to let it sync while I'm not around.
Sooooo sooner or later I'll get the Burrito running again, but I'm in no rush.
FIREMOD replaces BURRITOROOT
http://forum.xda-developers.com/showpost.php?p=21595398&postcount=105
as i am fairly familiar with the rooting process I am okay with amazon pushing update OTA, but some of my friends are complaining and I have to help them root their devices again after OTA update. So if this OTACERTS.ZIP deletion actually works (without other consequences) then I will surely recommend this to my friends

[Q] Rooted Arc cannot update to .62?

Regular Arc, US unlocked version, rooted to remove some bloatware. I got a notification for the .62 update, but it always fail to install. Does it require the full suite of bloatware to exist for the update?
Mine was also rooted+bloatware removed and it updated without problems.
BUT, you will lose root if you update to .62 (at least with PC companion) + get back bloatware. If you don't have problems with current firmware, stick with it.
You will have to put all bloatware back indeed.
But when you use FOTA, you will keep your root.
azaberl said:
Mine was also rooted+bloatware removed and it updated without problems.
BUT, you will lose root if you update to .62 (at least with PC companion) + get back bloatware. If you don't have problems with current firmware, stick with it.
Click to expand...
Click to collapse
Did you update it OTA? I tried OTA, and it keeps failing.
Mitchell90 said:
You will have to put all bloatware back indeed.
But when you use FOTA, you will keep your root.
Click to expand...
Click to collapse
Do I have to put everything back? Or are there certain ones that's critical (eg. timescape) and not others (the games, links)?
pika2000 said:
Do I have to put everything back? Or are there certain ones that's critical (eg. timescape) and not others (the games, links)?
Click to expand...
Click to collapse
I don't think anyone has the answer to this particular question. I guess you should restore (almost ?) every system apps shipped with .42, since you aren't supposed to remove them.
Excelsior82 said:
I don't think anyone has the answer to this particular question. I guess you should restore (almost ?) every system apps shipped with .42, since you aren't supposed to remove them.
Click to expand...
Click to collapse
Indeed, I don't know for sure , but I guess every app that you removed from system/app directory should be restored for the update to succeed.
I done a full restore and I have done nothing but root. Ota still fails
Sent from my LT18i using Tapatalk
I have the same exact problem, mine is only rooted and I can download it but when it is installing fails....???
With my Arc on .42, I had to restore every single bloatware or file that I had moved from system/apps before it would let me update via OTA to .62 (including but not limited to WisePilot, Chinese keyboard, Let's Golf! etcetera).
But apparently, this issue isn't so in all regions as some people have reported success even with a modified system/apps folder. But if you do encounter any error, well, now you know.
Furthermore, root is preserved while updating through OTA.
Cheers, mate.

Categories

Resources