OTA update

[silverdragon76]

ok so I woke up this morning to find a screen of an exclamation point and and android guy with his arms crossed. I don't understand or know what happened, but sometimes I do see that it wants to do an OTA update. I am wondering if this is what happened overnight. I did the battery unplug to turn it off then booted into recovery, wiped cache, and flashed by backup, re-booted and phone back up.

Is there anyway to prevent the phone from trying to install updates or what? Also, is an OTA update what probably caused the radio update? I rooted using the one click root, so it puts the firmware version back to 1.13.605.7

Also, after rooting the phone, I had wireless Tether installed, but after backup and root, when I try to run it, I get a message saying "the application Wireless Tether (process android) has stopped unexpectadly. Please try again". I had this problem with several of my apps, so I uninstalled them then re-downloaded them from the market, installed them and no problem. Seeing as the market has removed Wireless Tether from the market I cannot download that ap. Any suggestions? Would it be in my Titanium Backup folder, and if so, should I try to get it from there?

Thanks in advance.

 

[racedog]

Ok, first thing you need to do is to turn off OTA updates. I'm typing this from memory so I may have the folder off, if so, let me know and I'll get the right one. You need to have Root Explorer on your phone and using RE you go to system/etc/security and look for the file otacerts.zip and rename it to otacerts.zip.bak and you will not have to worry about the automatic updates anymore.

If you decide to go to one of the devs custom roms, those almost always have the ota updates shut off.

 

[silverdragon76]

ok, correct, but how to rename it?

 

[Cyber Warrior]

Folder path is correct... you da man

ok, correct, but how to rename it?

Long press the file name... you will have the option to rename.

 

[silverdragon76]

ok, now i get cannot rename bc is a system read-only ??? This is depressing

 

[Cyber Warrior]

ok, now i get cannot rename bc is a system read-only ??? This is depressing

When you're in Root Explorer and get to the screen with the otacerts.zip file... there's a grey box on top of the screen that says Mount R/W... press that so it reads Mount R/O and then change the file name.. afterwards change it back to Mount R/W.

 

[dougducko]

i also rooted with the one click method then loaded 2.10.605,,after loading i lost root and cannot boot into recovery mode without running first step of rooting when it reboots then when i try to load original rom it fails and says main rom is older,, so i am stuck with ginger

 

[Cyber Warrior]

Ok, first thing you need to do is to turn off OTA updates. I'm typing this from memory so I may have the folder off, if so, let me know and I'll get the right one. You need to have Root Explorer on your phone and using RE you go to system/etc/security and look for the file otacerts.zip and rename it to otacerts.zip.bak and you will not have to worry about the automatic updates anymore.

If you decide to go to one of the devs custom roms, those almost always have the ota updates shut off.

Bumping.... For Rooted users only!
[WARN]IF YOU ARE STOCK ROOTED WITH THE LEAKED GINGERBREAD UPDATE... TURN OFF THE VERIZON OTA PUSH[/WARN]

It seems a lot of people are having this issue.. turn off the OTA so you don't run into this problem.
I'll leave this in the TB general discussion for a day or two so everyone sees it.. after that it will be moved to the TB hack forum.

 

[drhere]

Sorry to resurrect an old thread, but I just rooted and I have heard different answers from other sites.
I recently rooted, and I am still running the stock ROM, I haven't altered it yet.
If vzw pushed an OTA update, would this unroot me and/or is this not recommended.

Thanks all.

 

[anthony2558]

It will unroot you.

T-Bolt using Tapatalk.

 

[recDNA]

Sorry to resurrect an old thread, but I just rooted and I have heard different answers from other sites.
I recently rooted, and I am still running the stock ROM, I haven't altered it yet.
If vzw pushed an OTA update, would this unroot me and/or is this not recommended.

Thanks all.

I'm in the same boat. Followed the directions above. Of course I wont know of it works until the next ota but it didn't brick my phone anyway!

 

[Cyber Warrior]

Sorry to resurrect an old thread, but I just rooted and I have heard different answers from other sites.
I recently rooted, and I am still running the stock ROM, I haven't altered it yet.
If vzw pushed an OTA update, would this unroot me and/or is this not recommended.

Thanks all.

Depends what you used:
From the Revolutionary Root/Unroot Guide... http://forums.androidcentral.com/th...ow-root-unroot-thunderbolt-revolutionary.html

How To Unroot
The revolutionary method of rooting uses a sneeky hboot exploit and replaces your stock 1.04.0000 or 1.05.0000 bootloader with a modified permanent hboot. It not only gives you all the same fastboot flash abilities as the original engineering bootloader, but it very effectively blocks other hboots from overwriting it. It's good... as you will remain s-off if you accidentally flash a full RUU, or accept an OTA... but makes it a little trickier to remove.
____________________________________________________________
All other root methods... accept an OTA and you will lose root.

 

[paulmiller82]

Bumping.... For Rooted users only!
[WARN]IF YOU ARE STOCK ROOTED WITH THE LEAKED GINGERBREAD UPDATE... TURN OFF THE VERIZON OTA PUSH[/WARN]

It seems a lot of people are having this issue.. turn off the OTA so you don't run into this problem.
I'll leave this in the TB general discussion for a day or two so everyone sees it.. after that it will be moved to the TB hack forum.

What if we have the OTA that Verizon pushed and then rooted? should I turn off OTA?

Oh nvm guess it helps to read the thread! Answer is right above my post.

 

[Cyber Warrior]

What if we have the OTA that Verizon pushed and then rooted? should I turn off OTA?

Oh nvm guess it helps to read the thread! Answer is right above my post.

A lot of members were running into problems when the GB update hit while rooted and running stock but that was with a different rooting method. Personally I haven't seen what happens with Revolutionary and receiving OTAs. Supposedly you have nothing to worry about. If you want to play it safe and turn it off.. its as simple as renaming the file. If you're running a custom ROM.. then you're also fine.

 

[OptimusNotPrime]

A lot of members were running into problems when the GB update hit while rooted and running stock but that was with a different rooting method. Personally I haven't seen what happens with Revolutionary and receiving OTAs. Supposedly you have nothing to worry about. If you want to play it safe and turn it off.. its as simple as renaming the file. If you're running a custom ROM.. then you're also fine.

Yeah also i would like to mention you can do this with Es File explorer. Just click the root option under settings Allow SU. Go to the file and just rename it otacerts.zip.bak I did this even though I'm running a custom rom just to make sure!

 

[worwig]

A lot of members were running into problems when the GB update hit while rooted and running stock but that was with a different rooting method. Personally I haven't seen what happens with Revolutionary and receiving OTAs. Supposedly you have nothing to worry about. If you want to play it safe and turn it off.. its as simple as renaming the file. If you're running a custom ROM.. then you're also fine.

Not to be dense......Oops, to late, I'm dense......:'(
Do you mean rename any OTA file after it is sent?

Stock GB, rooted using Revolutionary.

 

[stratejaket]

I'm pretty sure what they are talking about is once you rename otacerts.zip to otacerts.zip.bak. It will stop your phone from receiving any OTA files period.

 

[Cyber Warrior]

I'm pretty sure what they are talking about is once you rename otacerts.zip to otacerts.zip.bak. It will stop your phone from receiving any OTA files period.

Correct... The directions are on the first page. Its not the OTA that you're renaming... Its the system file (otacerts) that Verizon uses to check what version is on your phone when pushing out updates. Remove the .bak extension and you will receive updates again.... But once you're rooted you can just use the leaked RUUs (updates) from the developers waaay ahead of time before Verizon ever releases anything. One of the perks of being rooted.

 

[drhere]

Depends what you used:
From the Revolutionary Root/Unroot Guide... http://forums.androidcentral.com/th...ow-root-unroot-thunderbolt-revolutionary.html

How To Unroot
The revolutionary method of rooting uses a sneeky hboot exploit and replaces your stock 1.04.0000 or 1.05.0000 bootloader with a modified permanent hboot. It not only gives you all the same fastboot flash abilities as the original engineering bootloader, but it very effectively blocks other hboots from overwriting it. It's good... as you will remain s-off if you accidentally flash a full RUU, or accept an OTA... but makes it a little trickier to remove.
____________________________________________________________
All other root methods... accept an OTA and you will lose root.

Thanks for the info, I used Revolutionary. I am currently stock and I just rooted a little less than a week ago, and I haven't had the time to try out custom ROMs.
I am looking at custom ROMs, so I will hopefully be trying other ROMs soon.

 

[devveldogg]

Thanks for the info, I used Revolutionary. I am currently stock and I just rooted a little less than a week ago, and I haven't had the time to try out custom ROMs.
I am looking at custom ROMs, so I will hopefully be trying other ROMs soon.

I too am new to rooting, and have BAMF forever 1.07 and absolutely love it!