Does Rooting and/or reflashing prevent the next OTA update? - Droid Incredible General

There is allegedly a new OTA update on the way, enabling 720p video, among other things.
Will rooting or rooting+recovery reflash prevent the phone from updating? If it doesn't, would I have to re-root the phone after the update?

pieter3d said:
There is allegedly a new OTA update on the way, enabling 720p video, among other things.
Will rooting or rooting+recovery reflash prevent the phone from updating? If it doesn't, would I have to re-root the phone after the update?
Click to expand...
Click to collapse
If I was you, I would simply wait for the OTA to come out and let our AMAZING DEVS get a crack at it and download the rooted version.

I would love to have the 720p and new boot animation and mobile hotspot. But i would rather have root than any of those. Already have wireless tether. But love the new boot animation....hmm. what to do.... can't wait i have a feeling once the DInc gets stocked back up and they can advertise it we will get alot of devs behind it bc the droid x supposedly has a encrypted bootloader. Not looking so good for those who were ready to drop the DInc.
Sent from my ADR6300 using XDA App

This update is supposed to include wireless N, 720p video, wireless tethering, and the droid eye boot animation. Since I already have the wireless tether app for my rooted Inc, I'm wondering what would happen if I accepted to receive this OTA update? Anyway, I agree that having root supersedes all of these features, so I will wait for the download. My question is, about how long does it usually take from the time the OTA update is released until the dev's have it ripped and ready for us to download? Thanks!

Droid Eye Boot Animation
Here is a link to directions on applying the boot animation to a rooted phone.
forum.xda-developers.com/showpost.php?p=6943967&postcount=1

It has something to do with a file called otacerts.zip in etc/security
I think the Certinstaller.odex in system/app has something to do with it do...
I'm not sure what needs to be done with them, but when modified it will block OTA

dont rename the otacerts.zip. it will kill your battery life constantly checking itself over and over.

OK I've been told to just wait for the official ota froyo update before I root. And that if I root before that I wont get the update sent to me. But I've also been told that if I wait for the official ota update I wont be able to use unrevoked forever.
please help me!!! I'm so confused. and I've looked everywhere else and I keep getting different answers.

BigNate said:
OK I've been told to just wait for the official ota froyo update before I root. And that if I root before that I wont get the update sent to me. But I've also been told that if I wait for the official ota update I wont be able to use unrevoked forever.
please help me!!! I'm so confused. and I've looked everywhere else and I keep getting different answers.
Click to expand...
Click to collapse
It's not that you won't be able to use unrevoked-forever, it's that you won't have a way to flash a custom recovery system to the phone to actually FLASH the forever file.
I recommend the following since it seems you want an official update as opposed to the RUU.
1. Perform the unrEVOked root
2. Flash unrEVOked forever
3. Flash the Stock Recovery back to the phone.
4. Hurry up and wait for the OTA.
5. Upon receiving the OTA, install. You will lose your root privileges. No worries!
6. After installing the OTA, flash ClockworkMod back to your phone
7. Use ClockworkMod to flash a root payload file (contains su and Superuser.apk)
8. Bask in Rooted/Official 2.2 Froyo goodness.
From my research, the OTA MUST have the stock recovery to install. What you will have done here is provided an "Official" platform for the OTA to download, check signatures, and install all while having S-OFF. As long as S-OFF is invoked, you can continue to replace the recovery from ClockworkMod to Stock Recovery (Android 2e) whenever you need to.
S-OFF is what makes this all possible, God Bless the bastards at unrEVOked, would like to take 'em to Peter Luger's one day!

Ok thanks man haha. I've only had this phone for two day and I rooted as soon as I got it. But then unrooted because I was that I wouldn't get froyo.
And yes thank you UNREVOKED FOREVER and, also thank rdmerck for telling me I was completely lost.
Sent from my ADR6300 using XDA App

Related

Droid incredible update

Alright here we go. I've been sent the new new update and I want to install it. I have s-off so I can always reroot which I know how to do. Buuuut I need to find the stock recovery for froyo. Or if it doesnt change I just need stock recovery. Any help locating it will be loved. Thank you all very much!
sent from IOslvr
I got the update this morning and my phone is still rooted. Please clarify what you mean and I will see what I can do .
Sent from my ADR6300 using XDA App
Like install stock recovery so I can install the update then go back to being rooted.
sent from my sexy housemaid
I need the stock recovery image link so I can install it through boot loader.
sent from Ioslver
not sure. the RUU?
Here you go:
Applying November 2010 OTA to STOCK 2.2/FroYo rooted Incredible
Undereducated noob with rooted stock rom
I rooted my Incredible using Unrevoked so I could use free wifi tether and kept the stock rom. Unfortunately, because I am a noob and didn't know the ramifications or have all the info I needed (it's hard to filter and process all the info from searching the subject on Google), I deleted a couple of apks (before finding info saying to move them) in my attempt to eliminate some bloatware. I got nervous about it and stopped before deleting much, but don't remember which apks I did delete (I did a manual update at 4am while very tired). Now Verizon has pushed the Nov OTA to my phone and I have been pushing "Install Later" since. Think I still have s-off.
Can I allow the phone to do the update? I really don't care about retaining root or not, and can uninstall the wifi tether, superuser, etc, do the update and wait for Unrevoked to catch up so I can reroot (if necessary?) and reinstall wifi tether later. I have also seen that the RUU is out there, but as I understand, it wipes the phone and I'd really like to avoid that. I have seen the instructions posted earlier in the thread about "Installing OTA to rooted Android" but am lost when reading them. Plus the instructions and info I gathered when researching rooting my phone are being held hostage by my Chrome bookmarks (had to quit using Chrome, but that's another story).

[Q] Latest OTA won't install.

I got the latest OTA (3.70.651.1) and went to install it. It'll restart the phone and start the progress bar, but at ~25% or so it'll go to this screen:
i.imgur.com/qs7rt.jpg (sorry, can't post an outside link due to being a new user)
I have the stock rom with unrevoked. Any ideas why it won't install? I tried to search but found nothing.
You wanna lose your root? Why you loading the OTA? Grab a rooted 3.7 rom from here and load it!
dkd711 said:
You wanna lose your root? Why you loading the OTA? Grab a rooted 3.7 rom from here and load it!
Click to expand...
Click to collapse
+1 couldn't have said it better
I thought the latest unrevoked (the one just released) worked with this OTA?
your trying to take a difficult path for an easy process, there is no benefit to installing the OTA when you are already rooted and can install that software quickly and easily without needing to install ota then rooting again, if your wanting the stock sprint rom 3.70 I can post a link, if you are wanting your radio/pri/wimax upgraded I can post a link for that too,
does your phone boot into your rom our does it go straight to the android guy with the red triangle and exclamation mark?
My phone boots normally now.. it's just when I try to apply the OTA that it does that.
I dunno.. it seems simpler to install the OTA and just do unrevoked again. It's what I've done all along and it's worked up until now.
You don't want to do that, even if unrevoked 3.3 works. ( it does I rooted late night with it ) Just pull a rooted Rom here, besides the update is not so great. Not much new a game, Swype, and Blockbuster. Nothing to write home about.
Sent from my PC36100 using XDA App

[Q] OTA Gingerbread update

So I use an Samsung Epic, however my friend uses a Droid X with the OTA update on it. From what I've read it seems the only way to root is phone would be to flash his phone back to a earlier version that already has root then update via Boot strap. Is this the only method? Or is it possible to get Bootstrap to work on his OTAed phone and then flash the Update over top of it. Or even just to flash the .zip of the rooted version of the OTA through the stock recovery by renaming it Update.zip? I just would like to know. I wanted to give him root because he is currently having issues with his keyboard and phone slowing down due to the bloatware on it.
metalblaster said:
So I use an Samsung Epic, however my friend uses a Droid X with the OTA update on it. From what I've read it seems the only way to root is phone would be to flash his phone back to a earlier version that already has root then update via Boot strap. Is this the only method? Or is it possible to get Bootstrap to work on his OTAed phone and then flash the Update over top of it. Or even just to flash the .zip of the rooted version of the OTA through the stock recovery by renaming it Update.zip? I just would like to know. I wanted to give him root because he is currently having issues with his keyboard and phone slowing down due to the bloatware on it.
Click to expand...
Click to collapse
Yeah I believe he is going to sbf back to froyo then root then install the 2 part 596 GB rooted version (you can get it from multiple places -try Team Black Hat's app) then he should be good to go.

[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.

[Q] rooted LG G2 update OTA

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.

Categories

Resources