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
I'm intrigued in rooting my Nexus 7, but I also love google's stock android, no extra bloatware and apps makes me a happy camper, and thats why I waited for a Nexus tablet in the first place. Here's my question:
Is it possible to root the Nexus 7, get superuser permissions, change DPI settings, etc.... while retaining stock android (no flashing or different roms) so that whenever an OTA gets released, the device still lets you install the updated without giving any problems?
jakeellis01 said:
I'm intrigued in rooting my Nexus 7, but I also love google's stock android, no extra bloatware and apps makes me a happy camper, and thats why I waited for a Nexus tablet in the first place. Here's my question:
Is it possible to root the Nexus 7, get superuser permissions, change DPI settings, etc.... while retaining stock android (no flashing or different roms) so that whenever an OTA gets released, the device still lets you install the updated without giving any problems?
Click to expand...
Click to collapse
Yeah, you can root and get su permissions without changing stock. You need to use this to get OTA and still keep root: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
I'm not sure if the DPI would revert back to the original settings when updated, but it's something to try.
Also, if you remove any of the apk's under the system folders, you will not be able to update. The update checks to see if they are all there before it starts installing.
great..... do you think the device would still be rooted after an official OTA?
Don't see why not. You would need to run OTA root keeper again, to re enable root. If you read the description in play, it tells you that it temporarily disables root so that it hides it from the OTA update
Anyone actually try this yet? I had OTA Rootkeeper on my razr and it didn't work sometimes.
Dawg5 said:
Anyone actually try this yet? I had OTA Rootkeeper on my razr and it didn't work sometimes.
Click to expand...
Click to collapse
I haven't tried it yet. I let mine update before I rooted it.
Have head mixed reports on here, most say it works and some say it doesn't. You just have to take the chance.
If it does not save, its very easy to root again using a toolkit so it's not a big problem......
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.
hey guys this is my first android device il be getting it in a few days and my question is if I install OUYA-StockPlus will i be able to update my OUYA though the console or will I have to block updates and only update though a new flash when a new version of stock plus comes out?
Updates are blocked in this rom because the OTA updates overwrite CWM recovery and remove root. I wouldn't expect a new rom for every Ouya update either, only the updates that make major changes.
Also, since this is your first Android device, be very careful. As of right now there is no way to restore your device if you overwrite your kernel. It is also a real pain if you lose access to adb.
What if say someone else started your ouya and installed the update without knowing that they weren't supposed to would it corrupt it or would the ota install as its supposed to and you would just lose root and your rom. Im just wondering cuz I have already installed the playstore and the update blocker but i was just wondering what would happen if for some reason an update were to be installed would i be stuck in a loop and have to restore manually or would the ota install and just overwrite my cwm and just be like it was never there. I seen posts explaining what will happen but they're very vague and it seems as if the people asking messed up in the first place.
huckjam said:
What if say someone else started your ouya and installed the update without knowing that they weren't supposed to would it corrupt it or would the ota install as its supposed to and you would just lose root and your rom. Im just wondering cuz I have already installed the playstore and the update blocker but i was just wondering what would happen if for some reason an update were to be installed would i be stuck in a loop and have to restore manually or would the ota install and just overwrite my cwm and just be like it was never there. I seen posts explaining what will happen but they're very vague and it seems as if the people asking messed up in the first place.
Click to expand...
Click to collapse
The Dev of the StockPlus ROM actually physically removed the OUYA updater, so it's not possible for it to be updated that way. The only way to update StockPlus is by you downloading the .zip file of the new version and installing it manually through CWM, so there's no danger of anything happening automatically or without your say so.
DroidXero said:
The Dev of the StockPlus ROM actually physically removed the OUYA updater, so it's not possible for it to be updated that way. The only way to update StockPlus is by you downloading the .zip file of the new version and installing it manually through CWM, so there's no danger of anything happening automatically or without your say so.
Click to expand...
Click to collapse
Very nice that's kinda what i figured thanks for the clear answer!
It has come to light that a new update has been released for the Prime version stock ROM. This update is called V6.6 (duh), and the update replaces the preloader. Some people have reported bootloops, one has gotten a brick, and I am all but certain that Amazon is trying to patch the preloader to remove any chance of rooting or converting to OEM ever again. It also replaces the boot image, which we believe is a way to re-lock the bootloader, or possibly even make fastboot ignore the unlocked status. This could also destroy your ability to root, run TWRP, or run any custom ROM ever again. If you are on the Prime stock ROM, DO NOT take the OTA to V6.6. It's really not worth it for the security patch. I also encourage all users of V6.1, V6.4, or V6.5 to go ahead and convert your phone to the non-Prime variant while you have the chance. Amazon is known for jamming updates down people's throats so I would not be surprised if they have a way of installing that update without your approval.
The conversion guide is here: http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
There is some discussion about the OTA in the last few pages of the general discussion thread here: http://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-t3418354/post68565531#post68565531
We can use this thread to further dissect and discuss the update.
The boot img can lock the Bootloader.
Thanks for the warning. I would have taken it as I think V6.5 was a good update and improved performance (at the expense of battery life).
DarkBlood. said:
The boot img can lock the Bootloader.
Click to expand...
Click to collapse
No, but some kernel/ramdisk shenanigans could lock it at boot.
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
With the fire tablet they disabled the preloader and changed the pid
ColtonDRG said:
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
Click to expand...
Click to collapse
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
DarkBlood. said:
With the fire tablet they disabled the preloader and changed the pid
Click to expand...
Click to collapse
You cannot simply "disable" the preloader. We discussed what exactly Amazon did with the Fire a little bit in the private hangout the other day. The bottom line is that we still don't know exactly what shenanigans Amazon is up to, or what tricks they have up their sleeve. Knowing Amazon, it can't be good for us.
jacewt said:
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
Click to expand...
Click to collapse
It has the August security patch and some things that lock things down. Nothing else that I'm aware of.
bionictoothpick said:
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
Click to expand...
Click to collapse
If you unlocked your bootloader (fastboot style) via one of the methods before, you should still be able to gain root. If not, you are probably hosed, at least for now. Weather or not you will end up regretting that is up to you, but I certainly would.
kal250 said:
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
Click to expand...
Click to collapse
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
ColtonDRG said:
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
Click to expand...
Click to collapse
Fortunately, I had OTA blocked and as I said the other day when i get downtime(hopefully Sunday), I'm back to OEM, to hell with security patches!!
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
The zip is available in https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
Go for it, but I'm not interested in taking any of Amazon's **** either way.
As @DarkBlood. said, the zip file is mirrored on https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
ariesgodofwar said:
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
Click to expand...
Click to collapse
A handful of people around here actually got their phone bootlooped just after taking the upgrade straight from 6.5 to 6.6. At first I figured it was a fluke because their phones were altered, but at this point it's getting very suspicious (almost like it's a hit or miss thing for everyone, even those that haven't touched anything). I hope this doesn't damage the device's reputation too bad, and Amazon better get their **** together. Chopping off their nose in spite of their face. I guess I shouldn't be surprised at this point. This is Amazon we're talking about here.
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
If the zip can be modified, can we inject the 6.1 preloader and bootloader into the 6.6 OTA and modify it to run over current 6.6 installs allowing those who have been locked to at least unlock themselves?? I'm not savy enough to try....