Hi. I am rooted, have installed a few root apps (Lightflow, AdAway) but made no other changes (no custom recovery, have not disabled encryption...)
I wish to take an OTA update. I understand that OTA won't succeed if I have made modifications. Is it sufficient to do a full unroute in SuperSu? Or will the OTA still fail? Anyone have experience? Thanks!
kjnangre said:
Hi. I am rooted, have installed a few root apps (Lightflow, AdAway) but made no other changes (no custom recovery, have not disabled encryption...)
I wish to take an OTA update. I understand that OTA won't succeed if I have made modifications. Is is sufficient to do a full unroute in SuperSu? Or is will the OTA still fail? Anyone have experience? Thanks!
Click to expand...
Click to collapse
You will need to be "out of the box" stock for OTA to flash.
You don't have to wait for an OTA. You can manually flash the stock image and skip the wipe user data part.
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.
Noob question: Will root and custom recovery break stock ROM?
NoobER question: How about play store updates?
xtalks said:
Noob question: Will root and custom recovery break stock ROM?
NoobER question: How about play store updates?
Click to expand...
Click to collapse
you need stock recovery to install ota updates
unlocking the bootloader will wipe /data/preload content and you'll be unable to install ota (except if you restore the content of that folder)
any modification to /system files will also prevent ota to install.
root and custom recovery will not prevent playstore updates.
Thanks @alray
Follow up question though, will it say that I have an OTA update in settings/about but won't be able to install it or totally no notifications?
xtalks said:
Thanks @alray
Follow up question though, will it say that I have an OTA update in settings/about but won't be able to install it or totally no notifications?
Click to expand...
Click to collapse
you'll still have notification and you'll also be able to download the ota but it will fail if you are using a custom recovery. It can also fail with stock recovery if some files were modified or deleted in /system or in /data/preload. you'll see a red triangle with an exclamation mark inside : ota install failed
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.
I am using a rooted moto g 2014. I have an ota update notification. how to install the the ota update? I'm using twrp 2.8.6.0 custom recovery.
You need to go back to stock recovery to install the updates. However the update might fail on a rooted phone and you might need to unroot it. Also you need to remove rooted apps like xposed to have a successful OTA. For a smooth OTA, I would suggest you move back to stock ROM and recovery and then OTA update.
pank.dhnd said:
You need to go back to stock recovery to install the updates. However the update might fail on a rooted phone and you might need to unroot it. Also you need to remove rooted apps like xposed to have a successful OTA. For a smooth OTA, I would suggest you move back to stock ROM and recovery and then OTA update.
Click to expand...
Click to collapse
Share the process plz... (in details)
Here is the post to flash the stock recovery and firmware
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
Make sure you back up your data before you perform the procedure. Also for being safe side, back up all the contents of your internal memory.
Good luck
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.