I have my phone rooted, but I was wondering if Verizon can send anything down to unroot it.
If yes, what can I freeze to prevent OTA updates? Also, if we are unable to load custom ROMs ever, for whatever reasons, would that mean we would be stuck with this build of 4.3 because Verizon could take away root with an update? Thanks.
cooch said:
I have my phone rooted, but I was wondering if Verizon can send anything down to unroot it.
If yes, what can I freeze to prevent OTA updates? Also, if we are unable to load custom ROMs ever, for whatever reasons, would that mean we would be stuck with this build of 4.3 because Verizon could take away root with an update? Thanks.
Click to expand...
Click to collapse
From what I've read freezing SDM 1.0 should block OTA updates.
cooch said:
I have my phone rooted, but I was wondering if Verizon can send anything down to unroot it.
If yes, what can I freeze to prevent OTA updates? Also, if we are unable to load custom ROMs ever, for whatever reasons, would that mean we would be stuck with this build of 4.3 because Verizon could take away root with an update? Thanks.
Click to expand...
Click to collapse
Yes, more likely than not a OTA would take away root. However.. Verizon can't push a OTA onto your phone. yes it downloads it, and notifies you but dow not install unless you accept it to install.
You can freeze SDM to prevent this notifcation from showing up and from phone for checking on updates.
I say again though, Verizon does not force your phone to flash the OTA's, you must always accept the OTA.
+1
and go ahead and freeze sdm1.0...and more then likely Verizon will have the next update patch root.
droidstyle said:
+1
and go ahead and freeze sdm1.0...and more then likely Verizon will have the next update patch root.
Click to expand...
Click to collapse
I'm sure they will, I just hope we have a recovery by then
Related
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
Hello everyone. I was wondering if this would work:
Root, remove all bloatware, and then unroot and get OTA update. Will my phone, after OTA, remain without Bloatware?
The short answer is - no.
The longer answer is - you won't get the update unless you flash it manually as PD15IMG (which wipes and reformats everything anyway).
Jack_R1 said:
The short answer is - no.
The longer answer is - you won't get the update unless you flash it manually as PD15IMG (which wipes and reformats everything anyway).
Click to expand...
Click to collapse
what I mean is to root the phone, remove the apps like Asphalt, friend streem, etc. Then unroot it and wait till I get stock OTA
I think friend stream is removable but I may be wrong
No. Once you get the official OTA you will be subject to all the T-mobile bloatware. If you really want the stock gingerbread ROM, there is a rooted version with and without the new radio in the development forums.
You can get rid of the bloatware or you can have the gb update, but you cant do both until an exploit to root the update comes out.
AntonJart said:
what I mean is to root the phone, remove the apps like Asphalt, friend streem, etc. Then unroot it and wait till I get stock OTA
Click to expand...
Click to collapse
I understood what you've meant, and the answer doesn't change - no, you can't do it, the OTA will bring EVERYTHING on the system back to stock or won't work at all.
Jack_R1 said:
I understood what you've meant, and the answer doesn't change - no, you can't do it, the OTA will bring EVERYTHING on the system back to stock or won't work at all.
Click to expand...
Click to collapse
thats bad
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.
Should I wait to unlock and root if I want to get Marshmallow or is there a way to get it unlocked and rooted?
I would think as long as you do not stray from the stock software you would still get the OTA update. I do not think unlocking the bootloader and simply rooting the phone would prevent the OTA but I could be wrong.
campbellc1052 said:
I would think as long as you do not stray from the stock software you would still get the OTA update. I do not think unlocking the bootloader and simply rooting the phone would prevent the OTA but I could be wrong.
Click to expand...
Click to collapse
Would rooting and then updating break something though? I thought I may have read that somewhere on here.
I just looked into it a little bit more and I think as long as you do not flash a non-stock recovery image you should just be able to disable any system modifications such as xposed and unroot and the update would come through. You can probably find more information on this on google or the moto forums.
Im sure the devs will capture the OTA and make a flashable version, that's usually what happens. It usually doesnt take more than a day after the OTA to do it.
My plan is to wait until after Marshmallow is out before unlocking the bootloader if rooting. Since we have a unlock available we don't have to worry about updates breaking exploits so I am in no rush. The phone is pretty amazing even without root. Once Marsh is out I will test drive a bit and go from there. It could take a week before a dev drops the update or it could take hours... you never know.
Hmmmmm well I'm unlocked and rooted with TWRP..
But there is a Back to Stock zip..
So once Marshmallow comes out ,I'll just go back to Stock and take the OTA...
ttkyles said:
Hmmmmm well I'm unlocked and rooted with TWRP..
But there is a Back to Stock zip..
So once Marshmallow comes out ,I'll just go back to Stock and take the OTA...
Click to expand...
Click to collapse
Yeah, if you have already done it I'm sure someone can assist in getting you the files needed. Even if a dev can walk me through I don't mind pulling it for you. Maybe there will be a back to stock using the marshmallow image then just reroot after installing twrp and you are good to go
campbellc1052 said:
I just looked into it a little bit more and I think as long as you do not flash a non-stock recovery image you should just be able to disable any system modifications such as xposed and unroot and the update would come through. You can probably find more information on this on google or the moto forums.
Click to expand...
Click to collapse
Root breaks the ability to take an OTA, even using the supersu unroot feature the OTA will fail. The only way to take an OTA is to flash a fully stock system and recovery.
BladeRunner said:
Root breaks the ability to take an OTA, even using the supersu unroot feature the OTA will fail. The only way to take an OTA is to flash a fully stock system and recovery.
Click to expand...
Click to collapse
From what I understand it's not so much root that affects the ability to take an OTA it is the bootloader flag and recovery image. Also I think that while a new OTA would completely overwrite the system directory, since we can unlock bootloader, you can just re-flash SuperSU without issue.
I have to say that I'm a bit confused because Motorola have stated that unlocking the bootloader won't affect OTA updates here - https://motorola-global-portal.cust...tail/a_id/91999/p/1449,8620/kw/bootloader OTA
Can anyone clear this up for sure? I'd say a custom recovery would definitely affect them but not just unlocking the bootloader.
skttrbrain said:
I have to say that I'm a bit confused because Motorola have stated that unlocking the bootloader won't affect OTA updates here - https://motorola-global-portal.cust...tail/a_id/91999/p/1449,8620/kw/bootloader OTA
Can anyone clear this up for sure? I'd say a custom recovery would definitely affect them but not just unlocking the bootloader.
Click to expand...
Click to collapse
That's right...unlocking the bootloader alone won't stop an OTA. The custom recovery will be the issue. Basically if you're rooted and running TWRP all you have to do is follow the instructions in the Return To Stock thread and you're good to go for an OTA. Its a pretty simple process.
I was wondering if unlocking bootloader only without any custom recovery or rooting may stop the OTA updates, I'm receiving my MXPE xt1557 in 2 weeks and need to unlock it first thing, or should I wait for the update then unlock?
Kareem Safwat said:
I was wondering if unlocking bootloader only without any custom recovery or rooting may stop the OTA updates, I'm receiving my MXPE xt1557 in 2 weeks and need to unlock it first thing, or should I wait for the update then unlock?
Click to expand...
Click to collapse
As long as you don't install a custom recovery or modify /system you should still be able to apply an OTA. However, it is typically simplest to let your firmware update before you start making modifications. That just removes any chance for potential complications.
jason2678 said:
As long as you don't install a custom recovery or modify /system you should still be able to apply an OTA. However, it is typically simplest to let your firmware update before you start making modifications. That just removes any chance for potential complications.
Click to expand...
Click to collapse
Thanks a lot, it's just that I am not sure if the MM OTA update will be available when I receive it or not, and I want to unlock once I receive it so I don't have to restore my data again after unlock if I did it later.
I seem to recall mine automatically prompted for the MM update within 24 hours of unboxing, and you can force it to check for updates in Settings -> About -> System updates.
jason2678 said:
I seem to recall mine automatically prompted for the MM update within 24 hours of unboxing, and you can force it to check for updates in Settings -> About -> System updates.
Click to expand...
Click to collapse
Great news, thanks a lot.
Definitely true. I had TWRP on here and taking the OTA caused a boot loop. I ended up going back to stock to take the update. Then I flashed TWRP.
Sent from my XT1575 using XDA Free mobile app