Database Users

[Q] How to root NEW OTA 3.1?

Hello mates,
I am in Arizona, I just got a notice OTA to update my A500 to the new 3.1.
I downloaded the file, but did not apply the update yet. A copy of the file is now on my desktop and the file is in my /cache.
Can I root this official version if I did the update? I saw a link here for a rooted version,, but I need the official one to be rooted, like we did using Gengerbreak 1.2.
Your help is always appreciated.
Dr. Sam

Root
http://forum.xda-developers.com/showthread.php?t=1138228
Oklahoma City, OK rooted less than 5 minutes after 3.1 install.

Thank you mate for the reply. So you are confirming if I used iconiaroot very 1.2, it will root the official OTA update? Thanks.

Confirmed 3.1 + Root
Took less than 20 seconds and Root'd, life is good.
Thanks to the people who made the rooting possible.

OK folks. I tried to update but no go. After downloading the update, I am asked if I want to apply the update now or later. I clicked now. The Acer rebooted and about 10 seconds later, I get a blue bee with triangle with ! Mark in it.
My Acer is 1.141.07 (original OTA update) and roote with Gengerbreag very 1.2. Do I need to Unroot it first with gengerbread and then apply the OTA update to 3.1. And then root it with iconiaroot 1.2? Thanks to all of you.
Dr. Sam

Ramasoft said:
OK folks. I tried to update but no go. After downloading the update, I am asked if I want to apply the update now or later. I clicked now. The Acer rebooted and about 10 seconds later, I get a blue bee with triangle with ! Mark in it.
My Acer is 1.141.07 (original OTA update) and roote with Gengerbreag very 1.2. Do I need to Unroot it first with gengerbread and then apply the OTA update to 3.1. And then root it with iconiaroot 1.2? Thanks to all of you.
Dr. Sam
Click to expand...
Click to collapse
I did not remove root, only put my wpa_supplicant back to original. If you edited any files you will need to replace all system files with backups of the original's. Second try worked flawless.

T0yman said:
I did not remove root, only put my wpa_supplicant back to original. If you edited any files you will need to replace all system files with backups of the original's. Second try worked flawless.
Click to expand...
Click to collapse
I did not change anything nor I did move or freeze any files. All original but I rooted the device. Thanks for the reply and I hope to hear from others to solve this matter.

see your /cache/recovery/lasto
_log

Ramasoft said:
I did not change anything nor I did move or freeze any files. All original but I rooted the device. Thanks for the reply and I hope to hear from others to solve this matter.
Click to expand...
Click to collapse
There is a known issue with the update failing for no reason, you just have to keep retrying until it works.
Note: It's been reported by a poster here that Acer have now pulled the update and will be issuing a fix "today" to resolve this issue.

[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

Updating to 4.1.2 Whilst Keeping Root (With a Slight Twist)

Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!

jazacoop said:
Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1764794

wbbigdave said:
http://forum.xda-developers.com/showthread.php?t=1764794
Click to expand...
Click to collapse
I saw that, but it was posted back in July, and seemed smaller than the original OTA.
Nevermind... I didn't see the October update to the post further down.
Cheers!

[Q] How Do I Prevent OTA 4.3 Update

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.

Question about OTA updates

I am, unfortunately, running on MF3 firmware still and have my phone rooted and "customized" (ie I have Titanium backup blocking a few files). I'd like to be able to take the OTA update so I can update my firmware which is still pretty outdated (Android 4.2.2).
What do I need to do in order to be able to take the OTA update and what is the best way to proceed? Will the most recent FW version allow me to obtain root permissions or do I need to do something "fancy" like use survival mode in SuperUserSU?
Let me know the best way to proceed when you get the chance. Thanks!

jbrookley said:
I am, unfortunately, running on MF3 firmware still and have my phone rooted and "customized" (ie I have Titanium backup blocking a few files). I'd like to be able to take the OTA update so I can update my firmware which is still pretty outdated (Android 4.2.2).
What do I need to do in order to be able to take the OTA update and what is the best way to proceed? Will the most recent FW version allow me to obtain root permissions or do I need to do something "fancy" like use survival mode in SuperUserSU?
Let me know the best way to proceed when you get the chance. Thanks!
Click to expand...
Click to collapse
If you have modified or deleted any system files the ota will not work. The latest version, nl1, is rootable with towelroot. If the ota doesn't work then I'd flash the nb1 tar file in Odin, see the general forum, and then ota from there.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you have modified or deleted any system files the ota will not work. The latest version, nl1, is rootable with towelroot. If the ota doesn't work then I'd flash the nb1 tar file in Odin, see the general forum, and then ota from there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm sure I have at least frozen some of those files using titanium backup . . . What's the best way to handle it? Do a backup of my TB settings, unfreeze everything, then try to get the OTA update? I haven't even been prompted for an OTA in months and I'm assuming it's because I currently have root and have frozen some of those files . . . Do I need to remove root in order to get the OTA prompt or is it likely a result of me freezing files?
Thanks for your help!

jbrookley said:
I'm sure I have at least frozen some of those files using titanium backup . . . What's the best way to handle it? Do a backup of my TB settings, unfreeze everything, then try to get the OTA update? I haven't even been prompted for an OTA in months and I'm assuming it's because I currently have root and have frozen some of those files . . . Do I need to remove root in order to get the OTA prompt or is it likely a result of me freezing files?
Thanks for your help!
Click to expand...
Click to collapse
I'm not sure why you haven't gotten the prompt but it's not because of root. Try unfreezing the apps. Make a backup first
Sent from my Nexus 5 using XDA Free mobile app

jbrookley said:
I'm sure I have at least frozen some of those files using titanium backup . . . What's the best way to handle it? Do a backup of my TB settings, unfreeze everything, then try to get the OTA update? I haven't even been prompted for an OTA in months and I'm assuming it's because I currently have root and have frozen some of those files . . . Do I need to remove root in order to get the OTA prompt or is it likely a result of me freezing files?
Thanks for your help!
Click to expand...
Click to collapse
If you try to OTA with root, it will get to about 30% and then fail because the update checks for root if it's anything like the at&t update. I suggest unrooting and going back to 100% stock before trying any OTA updates.
I have posted a guide here: http://forum.xda-developers.com/galaxy-s3-att/general/how-to-restore-device-status-to-t2832880
I know it's for the GS3, but should also work on the GS4.

You guys are awesome. Sounds like this is plenty of information to get started. Thanks for your help!