Database Users

Does Rooting and/or reflashing prevent the next OTA update?

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

new update can't root now.

i run unrevoked and nothing happens. this a new problem with the new update? this is my replacement phone anwaysy so.
anyone know anyways to root? i can't downgrade to old version. please help..

if you have s-off you just need to flash a custom recovery.
if you don't then i have no idea if the updated rom is rootable.
that would have been something to look for before upgrading
Good luck!

Having custom recovery is not the same as rooting (Superuser acess). Unfortunately, at the moment, Unrevoked won't work on the new OTA and if you install SU pack after the OTA it will just hang during boot up and you'll be in reboot hell. You can have Clockwork with the new OTA, just not root access.

downgrading to stock then s-off and upgrading work?
update. i tried downloading the super back to stock thread and the hboot says the file is older and i can't by pass it.. so hmm

I am in the same boat. Just got the phone and the f-ing salesman decided to install the OTA for me while he was setting it up. So do I return this thing in the hopes of getting one without the OTA or is it likely it will be rooted?

guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?

dadsterflip said:
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
Click to expand...
Click to collapse
Nope, can't downgrade...I'm out of ideas. Pretty pissed off actually to the point where I'm ready to take it back and get one that doesn't have the god damn OTA applied. I HATE owning devices that I don't really own.

i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box

I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary

caleris said:
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
Click to expand...
Click to collapse
press Volume Up + Power I think when you see the triangle

magneticzero said:
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
Click to expand...
Click to collapse
But???????????? This will only work if you are already s-off, correct?

blackwolf77 said:
But???????????? This will only work if you are already s-off, correct?
Click to expand...
Click to collapse
if you have clockwork mod installed with S-On and updated the ota already, you can flash unrevoked forever through clockwork recovery... that will take S-Off to off. I was messing around earlier and did that..

I am not sure how you got clockwork installed. Everytime I try it recognizes the PB31IMG and then just skips over it. It never asks about installing it.

The file name has to be PB31IMG.ZIP right? Also the LCD works different right?
SLCD PB31IMG.ZIP
Sent from my ADR6300 using XDA App

Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.

Nitrogenus said:
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Click to expand...
Click to collapse
in for answer

tried it out, didn't work. the su trick with rageagainstthecage-arm5.bin does not work.

how to see page 3

Standing by!!!!! Will it work with s-on?

It shouldn't matter s-on or off. I have the SLCD screen don't know if it will make a difference. Just FYI
Sent from my ADR6300 using XDA App

New Firmware Update

So asus put out the new firmware update. I figured i have to unroot to install it, but can I root again after updating?

Yes - be warned custom kernel's will make unrooting difficult.

ensign.fodder said:
Yes - be warned custom kernel's will make unrooting difficult.
Click to expand...
Click to collapse
i didnt have a custom ROM on it if thats what you meant, but either way for some reason it wasnt updating. i unrooted using the universal root toolkit that i used to root, but it would download the update, install like a third of the way, then stop and sit at a black screen with an exclamation mark and the android until i hard reset back to normal operation. i installed a custom ROM instead now

I didn't have to unroot. See post #111
http://forum.xda-developers.com/showthread.php?t=1332583&page=12

xneogenx said:
So asus put out the new firmware update. I figured i have to unroot to install it, but can I root again after updating?
Click to expand...
Click to collapse
In my experience with the past few updates, rooting alone doesn't prevent the update from installing; but if you install CWM while/after rooting, that DOES seem to prevent it. After removing CWM a while back, I can update file while rooted. I do have to re-apply the rooting afterward though. I use the bootable CD that someone created an ISO for and posted here a while back. Works great and reliably so far.

xneogenx said:
i didnt have a custom ROM on it if thats what you meant, but either way for some reason it wasnt updating. i unrooted using the universal root toolkit that i used to root, but it would download the update, install like a third of the way, then stop and sit at a black screen with an exclamation mark and the android until i hard reset back to normal operation. i installed a custom ROM instead now
Click to expand...
Click to collapse
I've never rooted mine and I've never put on a custom ROM, but I have the same problem. It says there is a new firmware. It downloads fine, but only installs to about 1/4 of the way before it fails with a big yellow exclamation point. I've even restored to factory defaults and it was the same.

[Q] OUYA-StockPlus and updateing

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!

Wife possibly soft bricked??

Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?

Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work

XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:

Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code

XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )

Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)

XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )

Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it