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.
Related
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
So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device
You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta
A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade
Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app
u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378
Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.
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!
I have a software update for my phone waiting to be installed. I am rooted with decent moods through xposed.
What will happen if I allow the update to install?
I want to remain rooted.
Thanks.
The short answer is it'll fail. The long answer is here: http://forum.xda-developers.com/showthread.php?t=2834027
BadKarma81 said:
The short answer is it'll fail. The long answer is here: http://forum.xda-developers.com/showthread.php?t=2834027
Click to expand...
Click to collapse
By "it'll fail", do you mean it won't take, the notice will be gone, and everything will still be working the same ad it was before I did the update (without the updates that are in the install)?
Thanks in advance. Sorry if it's did in the other, but I figured I'd ask just this one last question.
brettdacosta said:
By "it'll fail", do you mean it won't take, the notice will be gone, and everything will still be working the same ad it was before I did the update (without the updates that are in the install)?
Thanks in advance. Sorry if it's did in the other, but I figured I'd ask just this one last question.
Click to expand...
Click to collapse
The OTA update checks system files before it installs, so it would download, run a check and then just fail. If you're rooted you might just want to use something like titanium backup pro to disable the SDM.apk (the update check package) and you won't get any more notifications about it.
There is a procedure to fool OTA system in order to make it receive the OTA again. So you have a second chance to grab the filename and make a lot of people here happy
Update: Thanks to @Sleeepy2 we know this method works in the nexus 6 :good:
DISCLAIMER: It's an unharmed procedure, but be warned, you will change build.prop so anything (bad) should happen if you do it incorrectly, most probably a bootloop. If you have doubts, don't do it.
Needs to be rooted.
So if there is a brave enought one, the procedure is just to change two values of the /system/build.prop file to make it looks a previous android version for the OTA system.
For instance, If you have received to OTA to LMY47M your build.prop file will have these values:
ro.build.date.utc=1425686543
and
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
If you change these lines by the equivalent lines from another version of android, the OTA system will check the OTA availability with the other android version. So, If before receiving the OTA your android version was 5.0.1 LRX22C you can change both lines with:
ro.build.date.utc=1416527965
and
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
That are the LRX22C version lines.
Save build.prop file and reboot your nexus 6.
Once rebooted check for OTA updates (It will be checked as LMY47D) and download it, if it's not downloading yet (don't apply the OTA, just download it).
While it's downloading, or even after it's download, open a terminal emulator (for instance this one: https://play.google.com/store/apps/details?id=jackpal.androidterm) and execute these two commands (will ask for superuser permission):
su
logcat | grep zip
And wrote down the OTA link for us
When you finish just revert the build.prop changes done and delete the file /cache/update.zip (it's the OTA downloaded, and you don't need it), then reboot your system to leave it in it's normal situation.
Thank you very much in advance.
And, If you are kindly enough, you may check for the rest of OTAs from other android versions (the LMY47E OTA to LMY47M should be very useful too). Here are all known versions build.prop lines to play with:
Code:
LMY47M
ro.build.date.utc=1425686543
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
LMY47I:
ro.build.date.utc=1425442825
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47I/1767468:user/release-keys
LMY47E:
ro.build.date.utc=1424577649
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47E/1748839:user/release-keys
LMY47D:
ro.build.date.utc=1424322888
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys
LRX22C:
ro.build.date.utc=1416527965
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
LRX21O:
ro.build.date.utc=1415319727
ro.build.fingerprint=google/shamu/shamu:5.0/LRX21O/1570415:user/release-keys
LNX07M:
ro.build.date.utc=1414346119
ro.build.fingerprint=google/shamu/shamu:5.0/LNX07M/1543455:user/release-keys
-----
KXH21.6-F1.12:
ro.build.date.utc=1416355004
ro.build.fingerprint=motorola/shamu_factory/shamu:4.4.4/KXH21.6-F1.12/25:userdebug/release-keys
Most of them will give you old and known OTAs, but some will give new OTAs for all of us. And the final test build probably doesn't give any OTA
Thanks and best regards.
I changed by build.prop and rebooted and no update which I checked.
xpack90 said:
I changed by build.prop and rebooted and no update which I checked.
Click to expand...
Click to collapse
But you previously installed the LMY47M/E, no?
If yes, Please, wait several minutes and keep checking, you eventually must receive the OTA again before the rest of people.
Check too if build.prop file was correctly changed (sometimes a number is missing or something).
Thanks and best regards.
No sorry I thought this was for people who wanted the update not those who had it
xpack90 said:
No sorry I thought this was for people who wanted the update not those who had it
Click to expand...
Click to collapse
Don't worry and thanks for trying.
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Sleeepy2 said:
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Click to expand...
Click to collapse
First of all, thank you very much. Unfortunately that's one of the known OTAs.
You can see all known OTAs here:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
But as I said, thank you very much. You demonstrated the method works for Nexus 6 too
oops, yeah it is know. I didn't fully read and thought you just wanted confirmation that it works on the N6.
And yes it does
OK, I got the OTA you're looking for (47M) but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate for my data to get wiped for nothing ...
YankInDaSouth said:
OK, I got the OTA you're looking for but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate to for my data to get wiped for nothing ...
Click to expand...
Click to collapse
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
VivaErBetis said:
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
Click to expand...
Click to collapse
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
YankInDaSouth said:
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
Click to expand...
Click to collapse
Don't worry, the OTA will eventually show up, sooner or later. The real problem is our lack of patience
I've added the build.prop info for 5.1 LMY47I build. The OTA seems to be delivered for Australian users.