If I have root on my device, I get OTA updates or not?
saarxee said:
If I have root on my device, I get OTA updates or not?
Click to expand...
Click to collapse
Yes you will get, but no they wont install UNTIL you remove root
And, you need the stock recovery as well + unroot.
I need to install stock firmware and It's deleted all my data?
Do i also need to have locked bootloader?Thanks.
Er, if you have a custom ROM, you might get the notification, but the install will almost surely fail; I wouldn't even try...even if it somehow installs, it'll probably just wreck your ROM.
But, er, OTA updates (if you are on stock already) don't wipe any data. But, if you are on a custom ROM and you want to get the OTA update, you'll need to flash back to stock and you should factory reset when switching ROMs (custom -> stock).
Locked or unlocked bootloader: it doesn't matter. I have an unlocked bootloader and I received the 5.0.2 update no problem.
Related
Hi,
I know this has been discussed in several ocassions, and I have read several threads but none of them answer my question.
I am wondering if I root my HTC One and keep the device with the stock rom (I only want to root for some apps that needs su) will I be able to get OTA updates?
If not, if I also do S-OFF will I be able to? Please keep in mind that I do not want to flash a custom rom, where then the answer I believe would be to unroot and apply the OTA.
Thank you
buzmay said:
Hi,
I know this has been discussed in several ocassions, and I have read several threads but none of them answer my question.
I am wondering if I root my HTC One and keep the device with the stock rom (I only want to root for some apps that needs su) will I be able to get OTA updates?
If not, if I also do S-OFF will I be able to? Please keep in mind that I do not want to flash a custom rom, where then the answer I believe would be to unroot and apply the OTA.
Thank you
Click to expand...
Click to collapse
No, and youll need a custom kernel with disabled write protection for the root to stick, which will not allow OTA's to work. if you really want root, download a custom stock rom
IINexusII said:
No, and youll need a custom kernel with disabled write protection for the root to stick, which will not allow OTA's to work. if you really want root, download a custom stock rom
Click to expand...
Click to collapse
But what about S-OFF not even with it it would work? I am confuse because I saw a guide here in XDA saying the following:
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
So is this not true?
Link to this guide:
http://forum.xda-developers.com/showthread.php?t=2265618
buzmay said:
But what about S-OFF not even with it it would work? I am confuse because I saw a guide here in XDA saying the following:
Rooting stock ROM
What you need to know before rooting stock ROM:
You can "un-root" it easily.
As long as you won't change any files on system partition, you still will be able to download and install official OTA updates.
Download Rooting Tools
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of Rooting Tools (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device. Your device has now SuperUser.apk, su binary and busybox installed.
So is this not true?
Link to this guide:
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
Having S-off won't effect OTAs but having a custom recovery will. Best to go all stock, rom and recovery to receive the OTA updates. You can root after.
Note: Do the S-off procedure before you update. If your hboot gets updated, you're outta luck.
farang4u said:
Having S-off won't effect OTAs but having a custom recovery will. Best to go all stock, rom and recovery to receive the OTA updates. You can root after.
Note: Do the S-off procedure before you update. If your hboot gets updated, you're outta luck.
Click to expand...
Click to collapse
Ok, but now for instance I do have 4.2.2 so if I root and then there is an update 4.3 then what? I am interested in being only root and being able to get the updates. So every time an OTA comes I shall unroot and then root? This option is not as optimal as I would have though it would be.
Thanks
buzmay said:
Ok, but now for instance I do have 4.2.2 so if I root and then there is an update 4.3 then what? I am interested in being only root and being able to get the updates. So every time an OTA comes I shall unroot and then root? This option is not as optimal as I would have though it would be.
Thanks
Click to expand...
Click to collapse
As long as you have a stock recovery and rom, you should be able to receive OTAs on a rooted phone. Not %100 certain though.
Note: An OTA update could break the root and other mods you made to the rom and cause some other issues.
farang4u said:
As long as you have a stock recovery and rom, you should be able to receive OTAs on a rooted phone. Not %100 certain though.
Note: An OTA update could break the root and other mods you made to the rom and cause some other issues.
Click to expand...
Click to collapse
But how can I have a stock recovery and be root? Dont I need a custome recovery to root?
buzmay said:
But how can I have a stock recovery and be root? Dont I need a custome recovery to root?
Click to expand...
Click to collapse
You need custom recovery to run the rooting process. After your system is rooted you can then flash back to the stock recovery. You should still have root access but I could be wrong. Download "Root Checker" from the play store, run it to see if your device is still rooted. You still need a stock recovery to receive OTA updates though.
The reason you need stock recovery is that you can't install an official update with custom recovery. The type of recovery you have doesn't affect root access.
The reason you have to keep your system files perfectly stock is that an OTA is a patch, meaning it doesn't necessarily replace entire files but mainly snippets of code. If the system files are not stock, it can't do this properly. So it checks /system before running and stops if things are not perfectly stock.
You can get OTAs being rooted, you just can't install them unless you have stock recovery and a fully stock rom.
If you're stock on 4.2.2 right now, you can't s-off, so don't worry about that.
You don't have to flash a custom rom, but you can flash a stock rooted rom. With OTAs, you play the cat-and-mouse game. Can I root it? Did the HBOOT update and kill current S-OFF procedures?
If 4.3 does come out, all you would have to do is wait for a few days for a dev to cook a stock rooted 4.3 rom. AT&T always lags with updates, yet I have a fully functioning 4.2.2 M7 with LTE and no AT&T bloat all thanks to the devs who cook stock rooted roms.
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
yankeesfan714 said:
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
Click to expand...
Click to collapse
I've had no issues updating OTA while rooted and unlocked. It only becomes an issue if you modify the system. You will also not be able to update OTA if you have a custom recovery installed. However, to play it completely safe it is always best to go back to stock if you are doing an OTA.
Installing a custom recovery and messing with system apps will cause an ota to fail. Unlocking and SU alone won't make it fail
Leave system apps alone and flash back to the stock recovery prior to accepting the ota.
yankeesfan714 said:
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
Click to expand...
Click to collapse
Since the OTA can only install via stock recovery, installing a custom recovery is technically the point at which you lose the ability to do an OTA update.
to quote SOME of what I put here -> http://mark.cdmaforums.com/MotoX-OTA.html
For the Motorola X, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall.
Because of #2, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
Click to expand...
Click to collapse
So any any point you deviate from stock too much, an OTA will fail to install.
(there is more info at that link)
If all you have done is unlocked the bootloader, flashed custom recovery, and installed SuperSU to root... then installed root capable apps like Adfree, Wifi Tether for root, Greenify, or others that don't mess with system files and the like, you can just flash stock recovery back on to take an OTA.
If you unlock the bootloader, flash custom recovery, and install SuperSU to root... then alter the build.prop, remove or rename the BLOAT APK's from your phone, install Xposed, etc. You'll have some work to do getting back to "stock" to take the OTA.
KidJoe said:
Since the OTA can only install via stock recovery, installing a custom recovery is technically the point at which you lose the ability to do an OTA update.
to quote SOME of what I put here -> http://mark.cdmaforums.com/MotoX-OTA.html
So any any point you deviate from stock too much, an OTA will fail to install.
(there is more info at that link)
If all you have done is unlocked the bootloader, flashed custom recovery, and installed SuperSU to root... then installed root capable apps like Adfree, Wifi Tether for root, Greenify, or others that don't mess with system files and the like, you can just flash stock recovery back on to take an OTA.
If you unlock the bootloader, flash custom recovery, and install SuperSU to root... then alter the build.prop, remove or rename the BLOAT APK's from your phone, install Xposed, etc. You'll have some work to do getting back to "stock" to take the OTA.
Click to expand...
Click to collapse
Does this also apply to moto x non-dev devices?
dmonleo said:
Does this also apply to moto x non-dev devices?
Click to expand...
Click to collapse
Yes. Every device with an unlocked bootloader is essentially a 'non official' Dev edition (although unlike the Dev edition, your warranty is void).
We always got "swappa"!
dmonleo said:
Does this also apply to moto x non-dev devices?
Click to expand...
Click to collapse
While Not Explicitly stated on -> http://mark.cdmaforums.com/MotoX-OTA.html yes, that info about the conditions for taking an OTA applies to ALL Moto X's... Dev Edition, Non-Dev Edition, Moto Maker, Retail, etc. With locked bootloader and with Unlocked Bootloader.
What @samwathegreat replied to you is very accurate. From a functional stand point, once you unlock the bootloader on a Non-Dev Edition... your phone acts as if you have a Dev Edition.. (Except your warranty is void). And it doesn't matter if you have a Rogers Wireless, Sprint, GSM Unlocked, etc... and got your code from Moto, or you had a Verizon Non-Dev or ATT or Republic wireless and got the code from the Chinese website or middleman.
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Anything else I might have missed that is important either from mistakes or just general knowledge I missed would be appreciated. Thanks and Good Night everybody!
Icon000 said:
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
Click to expand...
Click to collapse
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
Click to expand...
Click to collapse
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Click to expand...
Click to collapse
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Great explanation! :good:
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Why do you recommend flashing 4.4.4 over accepting the OTA? I still want to be able to use the additions originally provided by Motorola. I didn't seen a rom built on Moto Stock. Did I miss it?
Flash the stock 4.4.4 ROM that is for your device.
What's better...4.4.2 with patches to make it 4.4.4 (via an OTA) or just the full 4.4.4 (via the full 4.4.4 install) without the need for patching to make it 4.4.4?
Oh well...it looks like there isn't a FULL 4.4.4 for AT&T Moto X released yet....just 4.4.2. Flash the full 4.4.2 then take the OTA update to 4.4.4 and then flash TWRP to get root.
AT&T 4.4.2
http://sbf.droid-developers.org/download.php?device=0&file=849
You can just flash the system.img from the download with mfastboot to revert any changes you did (root, etc..) so that the OTA can be installed successfully. You'll just want to get fully updated before flashing an alternative recovery like TWRP.
Hello,
I would like to root my phone, but do I also have to unlock the bootloader and install a custom recovery? I don't want to install custom roms, and I want to be able to install updates from Google. The phone is also unlocked, but I'm not sure if unlocking the bootloader is a totally different thing. Basically I just want to root to get features such as the notification light and install exposed.
NOTE: This will only work on lollipop, for M preview you need a modified kernel, otherwise it won't boot!
If you only need root then use Chainfire's CF-Auto-Root (https://download.chainfire.eu/628/CF-Root/CF-Auto-Root/CF-Auto-Root-shamu-shamu-nexus6.zip).
To install root, you need to unlock the bootloader (CF-Auto-Root will do it for you if it's locked), but it will wipe you entire phone, and do a factory reset. So backup everything before you root it.
This will leave your stock recovery unchanged.
Thank you. This is exactly what I wanted.
You might want to consider installing twrp also, at least you can do a backup before you start messing around with stuff. Just rooting the phone will allow you to do everything you need /want but if you change something that makes things go south you have no reference point to return to.
Also, just to clarify: You will NOT be able to recieve OTA updates after rooting your phone. Rooting, using custom recovery, custom kernel or anything at all that tampers with the system prevents OTA updates from installing.
If any of the above has occured, the only way to be able to start updating through OTA again is to flash a factory image (or at least relevant parts of one).
Unlocking the bootloader will not affect the ability to update through OTA.
Good day all,
got a new OTA rolled in for my Droid Turbo, though I already have a clean flash from MM on this device.
The following update rolled in which failed to install per TWRP recovery (ERROR 7)
What exactly is this update?
Has to be installed with stock MM recovery, OR flash the full stock firmware, twrp version, in twrp (3020) worked for me. Don't forget to wipe caches, data unnecessary.
Einsteindks said:
Has to be installed with stock MM recovery, OR flash the full stock firmware, twrp version, in twrp (3020) worked for me. Don't forget to wipe caches, data unnecessary.
Click to expand...
Click to collapse
But I do not want to re-flash my firmware. Especially since this update is only 20+ mb it is not large enough for me to re-clean everything and restart it all. Stock recovery is the only solution?
Stock recovery only for tbe OTA. The OTA will likely fail if the ROM isn't pure stock. Flash the twrp version and wipe, and you'll only need to reload any ROM extras. Root with the beta SU after a simmered restart. It seems to like a settled ROM better. Update SU via PlayStore at restart.
M_w_B said:
But I do not want to re-flash my firmware. Especially since this update is only 20+ mb it is not large enough for me to re-clean everything and restart it all. Stock recovery is the only solution?
Click to expand...
Click to collapse
If by re-clean you mean re-delete system apps that you don't want, that will be inevitable. The OTA will not install unless system is 100% stock, and the TWRP package will reflash everything to 100% stock. So either way, if you want this update, you'll be re-deleting some system apps.
However, if you're worried about losing userdata, don't. Neither the OTA nor the TWRP package will touch that.
As for your original question of "what is the update," it's just a security patch. It updates the android security patch level to January 2017, and it makes it so phones with locked bootloaders cannot be unlocked (but it will not re-lock and already unlocked bootloader).
TheSt33v said:
If by re-clean you mean re-delete system apps that you don't want, that will be inevitable. The OTA will not install unless system is 100% stock, and the TWRP package will reflash everything to 100% stock. So either way, if you want this update, you'll be re-deleting some system apps.
However, if you're worried about losing userdata, don't. Neither the OTA nor the TWRP package will touch that.
As for your original question of "what is the update," it's just a security patch. It updates the android security patch level to January 2017, and it makes it so phones with locked bootloaders cannot be unlocked (but it will not re-lock and already unlocked bootloader).
Click to expand...
Click to collapse
Thank you for the info on the update. I will not do the effort for a patch like that.