Related
Hi, i just rooted my nexus 7, with custom recovery and unlocked bootloader. Just wanna know will i still recieve ota from google for my tablet? of i would have to relock my bootloader and flashh the stock recovery before i can recieve the ota...?
Since you have flashed a custom recovery, you'll have to flash back the original recovery in order to do a ota.
It doesn't matter if your rooted or if you have a unlocked boot loader.
BTW, You will loose root if you don't use ota keeper from the market.
Sent from my Xperia Arc
mazlano27 said:
Hi, i just rooted my nexus 7, with custom recovery and unlocked bootloader. Just wanna know will i still recieve ota from google for my tablet? of i would have to relock my bootloader and flashh the stock recovery before i can recieve the ota...?
Click to expand...
Click to collapse
First question is why would you care? Its not like there are OTA's happening all the time. there has been basically one OTA since the device first came out and most people got it as soon as they started to use their device.
Second, if you have a custom recovery, that will stop it from working.
IF you put the recovery back, the question of if you will lose Root or not really depends on the OTA type. Most OTA's are incremental, meaning they only contain the changes of the system, not the whole system. If it is an incremental, unless there is something in the OTA that seeks out and removes root, it most likely will not affect it. However, if you have made any real changes to the system (removed system programs) the OTA may fail to run as it assumes everything in a normal system is there.
IF the OTA is a full system update like what the Kindle Fire was doing for a long time, it will flush the complete system area and load a new one, that effectively removes root since when it is done, it is no longer physically there. OTA Root keeper won't help you in those cases since the entire system area get wiped. Getting root back is trivial though as hard as it was originally.
I'd tend to think that the OTA's will be incremental... and I see little need or desire by Google to be hunting down root since it is a Nexus device and it is designed to allow for that. Its not like it is a phone like device where the Wireless operator is having a cow as to whether or not you gained access... its supposed to have that kind of access.
However, it really doesn't matter. When the next OTA comes out, there will be a number of devs which will take it apart and release an update you can use with the recovery you currently have and root and will keep root just fine. these typically get released within hours that someone notices a new OTA in the wild and sometimes you can get it before you actually even have a chance to get the real OTA over the wire.
So not a real big deal. I'd just stay where you are and when one comes out watch to see what gets released to mimic it.
Note changing the state of the bootloader will wipe your device. Unlocking will wipe it and locking it will wipe it. You are best off, unlocking it and just leaving it that way.
Is it a misconception that an OTA update received on your phone will not install if you have a custom recovery? I just read an article on how an update will fail if you are running a custom recovery. However, when I updated from 4.2.1 to 4.2.2.. All I did was accept the OTA update notification I got on my phone and it installed fine through the TWRP recovery I had flashed on my Nexus.
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
peedub said:
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
Click to expand...
Click to collapse
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Rizy7 said:
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Click to expand...
Click to collapse
Yes its not new info as this has been discussed before in a number of threads back when the last OTA first came out.
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
zim2dive said:
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
Click to expand...
Click to collapse
Rooting your phone does not keep you from being able to update it. If all else fails you can always download the OTA and update it through your custom recovery. Which is what a lot of people did instead of waiting for Google to push it to their phone, myself included. Also you don't have to have a custom recovery installed if you don't want to after you root the phone. You could use one of the toolkit's to root it and it will install a temporary custom recovery used just for rooting then remove it when its done. Or just flash the stock recovery image after you root if you do it another way. If you go through the process of rooting I would recommend unlocking the bootloader too while you are at it but be warned this will erase all your memory so backup first.
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.
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.