Is it possible to flash an OTA update with a modified build.prop?
I currently have to re-flash the system partition back to stock, apply the OTA update, and then re-edit the build.prop. Simply removing the edits from the build.prop is not sufficient.
TIA
Related
Just read if you are rooted, or have modified any system files, the update will fail. So if you go the ota route, go to stock first.
So with systemless root, as far as getting back to a state where I could receive an OTA, I would just have to have stock recovery, /system partion back to stock, and stock kernel?
I root my android phones mainly for the option to use viper4android and sometimes modify the mixer_paths.xml file to get more headphone volume.
In this process, busybox is installd and thats on the /system location right?
so if an OTA came through, I would have to have made a stock backup of the mixer_paths and replace the edited one, flash stock kernel, and uninstall busybox?
I just want to be able to tinker with my phone without having to reflash everything in between OTA's.
thanks
Or can I just flash new /system image when ota's come out? Leave data intact?
I know that I can't get OTA normally if I have any system level modifications like root or xposed installed.
However, I came across this thread which lists both, the stock firmware images and individual OTA update zips.
With the zip for OTA in hand, will flashing them on a rooted stock device cause problems?
You can install the factory images but it will be a clean install. You will have to root the phone after. You can learn how to flash those images here, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
No. You can't flash an OTA if you're modified. You must flash the factory images.
Thanks! Guess I have to download the full thing everytime.
Thanks!
I want to flash ota with twrp...i dont know the default location...need help
On my G4 (not Plus!) the OTA updates are downloaded to:
Code:
/data/data/com.motorola.ccc.ota/app_download
For example, the latest one OTA update file is called:
Code:
Blur_Version.24.24.4.athene.retail.en.US.zip
Let us know if you succeed with flashing the OTA zip. So far from what I've read - it's not possible to flash it once you modified the system partition (e.g. installed SuperSU or similar).
Don't know if flashing from TWRP is possible. https://twrp.me/faq/officialota.html
If you already changed your system partition (for example, mouting it in TWRP in r/w mode) the hash was changed and the OTA update will fail. You'll need to find a flash image and flash the system partition again to be able to update using the OTA. Remember to take note of the version you have to flash that exact version.
I rooted my phone and use magisk modules too. New update appeared, am I safe to install it OTA? Will I lose root or magisk if I update?
Tomogitarist said:
I rooted my phone and use magisk modules too. New update appeared, am I safe to install it OTA? Will I lose root or magisk if I update?
Click to expand...
Click to collapse
The update won't go through and you will encounter an installation problem error. Revert back to the stock boot.img of your security patch month (e.g. January, Feb patch) and then try the OTA and you should be able to update.
Google "how to apply OTA with Magisk" if you haven't touched the system partition. But no it is not safe, I bootlooped.
It is safe. OTA updates system partition. Magisk uses boot partition.
In other hand if you ever mounted system as read AND WRITE even if you didn't make any change to it the OTA will fail.
OTA also will fail if detects boot partition modification, what means you'll have to temporally restore boot (uninstall Magisk) to update and then reinstall it. You'll find how to in this forum.