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
Hi guys, after a 6 months period with HTC Wildfire S, i decided it was time to upgrade my device, so here i am, a newbie Nexus S user.
The first things i did with my new toy were unlocking the bootloader, gaining root permissions and installing CWM.
But i noticed that Market isn't updating, it's stuck to THIS version (i think it's 2.13)
Has this anything to do with root and cwm? Or it's just a matter of time and i'll eventually get the update?
Same thing with firmware: at the moment i'm running 2.3.3: looking for updates, and even using the *#*#checkin#*#* code, provided the same result: no FOTA available. Is this due to the root+cwm or i just need to wait?
I know this has already be discussed in the faq, but i find them quite confusing.
I mean, i know i could do a manual update, but i'd like to know whether if i'll ever receive a fota update or if i've lost this chance after root.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Click to expand...
Click to collapse
Thanks in advance for the answers!
There is no update due to the root, i advice you to manually update your phone to the latest version 4.0.3 using cwm, after that root again. finally you will have rooted ics on your nexus s.
uhm, you say i won't receive updates.
FAQ says most of the time i won't receive them.
THIS thread says i will receive them.
I am confused.
from what I can make sense of, it sounds like you should be getting updates. The FAQ you posted says that if you try to install one of the official OTA updates through CWM, it will fail most of the time.
i don't know how reliable that "checkin" trick is, and it may depend on your carrier as well.
if you've already rooted your device, then i would just flash one of the custom roms, you won't want to go back to the OTA after...
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
albundy2010 said:
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
Click to expand...
Click to collapse
Thats correct. It has only to do with the install. (It will fail).. if you dont get the notification for an ota i dont know whats wrong...
Sent from my Nexus S using xda premium
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
If you had 2.3.3 the update was probably the 2.3.6 and after that you would have received the 4.0.3 update....anyway from what I remember the version of the ota update is showed in the notification bar...isn't it?!
Sent from my Nexus S using XDA
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
1. I assume it was the a step up from 2.3.3 to a max of 2.3.6 as OTA updates to 4.0.3 are currently on hold due to battery drain issue
2. your OTA install is failing because you have custom recovery (CWM) but the OTA updates require the stock recovery (3e)
if you really really want to install OTA updates, you gonna have to go back to stock recovery (do a nand restore, hope you have one) then flash the OTA updates for your device
Is it a misconception that an OTA update received on your phone will not install if you have a custom recovery? I just read an article on how an update will fail if you are running a custom recovery. However, when I updated from 4.2.1 to 4.2.2.. All I did was accept the OTA update notification I got on my phone and it installed fine through the TWRP recovery I had flashed on my Nexus.
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
peedub said:
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
Click to expand...
Click to collapse
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Rizy7 said:
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Click to expand...
Click to collapse
Yes its not new info as this has been discussed before in a number of threads back when the last OTA first came out.
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
zim2dive said:
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
Click to expand...
Click to collapse
Rooting your phone does not keep you from being able to update it. If all else fails you can always download the OTA and update it through your custom recovery. Which is what a lot of people did instead of waiting for Google to push it to their phone, myself included. Also you don't have to have a custom recovery installed if you don't want to after you root the phone. You could use one of the toolkit's to root it and it will install a temporary custom recovery used just for rooting then remove it when its done. Or just flash the stock recovery image after you root if you do it another way. If you go through the process of rooting I would recommend unlocking the bootloader too while you are at it but be warned this will erase all your memory so backup first.
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.
how to do you update a rooted lg g2 over the air. everything is stock on the phone.
MAGICEA_EA said:
how to do you update a rooted lg g2 over the air. everything is stock on the phone.
Click to expand...
Click to collapse
From what I understand, you will still be able to get updates thru OTA.
hd-renegade said:
From what I understand, you will still be able to get updates thru OTA.
Click to expand...
Click to collapse
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.
So i can update rooted lg g2 over the air when a new update comes out
liorra3 said:
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.
Click to expand...
Click to collapse
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
ota
hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
Im new to this, so if you have rooted lg g2, will ota still work. Everything is stock on the phone
hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
you right.
if you use stock recovery you will get OTAs
if its stock and merely rooted then OTA should work
For the OTA to be accepted, you'll need the stock recovery for your device. Rename it to recovery.img (if it already isn't named that) and then move it to sdcard root (/sdcard).
Now, use a terminal emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en) and open a command prompt. The command we're using has two parameters. The the "if" parameter refers to your input file, in this case, this is the recovery.img file you moved to your sdcard root to flash. This could be any recovery (TWRP, CWM, stock, etc). The "of" parameter is the output file and is the actual physical path to the recovery image your device uses. At the command prompt type this:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you already have the stock recovery then all you need to do is press "Accept" or "OK" or whatever the dialog asks when it pops up letting you know about the update. I'm not sure if the stock recoveries are different for each carrier, so you'll have to find that yourself.
Edit: By the time I finished typing this I see that you already are on stock recovery, so you should be good to go
Idk mines flashed to stock and rooted
Sent from my LG-D800 using Tapatalk
Just bought a g2 and am thinking of rooting to enable the auto hide of the on screen menu buttons. So correct me if im wrong but if all i do is root, leave the stock rom and do nothing apart from root i will still get ota updates.
But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app
SuperSU Pro has an OTA survival Mode. You can try it out, it should work
o0adam0o said:
But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Try the above or remove/freeze whatever the apk your carrier uses for the OTA. There's a couple threads around with more info.
Sent from my LG-D800
Another question: (don't want to start a thread for this)
If you have custom recovery (In my case TWRP) when an OTA lands, obviously I won't be able to accept it.
I'll need to flash it through TWRP correct?
If this is the case will this simply apply as OTA's do and not delete any of my data on the phone etc?
Also is there a stock recovery I can download just to make things easier??
First time I've had a phone rooted and with recoverybefore it's update cycle is over, and Google isn't really being all that helpful
How to backup stock recovery?
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
Nice to see you here dude.. may remember me from the rocket? Anyways, i'd just skip the OTA. It's nothing life changing. I'm still stock/rooted on 10d. Waiting for bugs to get squashed on 4.4.2 before I start flashing. Rather enjoying stock for the time being. Not really sure why 10o won't take. Haven't seen anyone else mention this. The only thing that has been brought up repeatedly is bootloops in twrp after taking the 10o OTA.
m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Sent from my VS980 4G using Tapatalk
thricerocks86 said:
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Click to expand...
Click to collapse
I am still investigating. I've unrooted via Voodoo OTA Rootkeeper and a little extra housekeeping, and the Rooting Status does show "unrooted" in the About Phone section. However I still get 0x1117008 when trying to install the OTA. So perhaps the "unrooted" in About Phone may be a prerequisite, but is not sufficient for a successful OTA update. Maybe either the update is doing more checks for rooting evidence than the RCT daemon, or perhaps there is some other change that is triggering the error.