How to prepare your rooted Android for official OTA updates

How to prepare your rooted Android for official OTA updates

With Android L Rolling in the autumn, here are the top tips for preparing your hacked phone for the OTA upgrade.

When you root and hack your phone, you get distracted by the software manufacturer's desired setup, and in doing so, you compromise your ability to install OTA (air) updates, which manufacturers Push to keep the device up to date. Whether you physically break the installation of updates (perhaps with custom recovery) or not, installing OTA on a modified device is full of danger and is generally not recommended.
Since your device is not in the state that the manufacturer intends, trying to install you can get a non-booting system. For this reason, some manufacturers will also stop downloading updates if they find that your system has been modified for your safety.

Thankfully, modifying your device is rarely a point of return - on most devices, you can go back to a state where OTA updates will apply, or in the worst case scenario, you get your device at that point. You will be able to do this, where you want to do something when you want to update, you become disastrous, you can go back to where you started without losing any data. .

The precise process varies depending on the manufacturer of your device and is slightly on the limit on which you have modified your system. We're here to show the general steps required to update your device.

OTA compatible?

Whether you can apply the latest OTA to the manufacturer and still retain your data, depending on whether the ROM you are using is based on stock ROM or not. If it is - and if it uses standard security signatures - then you should not wipe it out. You need to erase your data for non-stock based custom ROMs.

Make backup

First of all, you have to make backups. If you have a custom recovery, you can use it to make android backups. Make sure you drag the backup completely after the device. Tools like titanium backups have changed system behavior, even if you can restore your app data.

Keep root

When you apply a manufacturer OTA, then losing the route is common. This is because the creator checks it out and activates it, but also that some OTA completely erases the system partition and then flashes. It is a good idea to check forums to confirm whether other users have maintained it or not.

Revert back

Before installing the OTA update, check the system. If the checksum does not match (for example on a modified ROM), the update will not be installed. For this reason, you need to flash your boot and system partitions in stock versions at least by using a recovery, fastboot or manufacturer tool.

Stock recovery

The process of implementing OTA updates is done by the recovery image. Most hacked devices install custom recovery, which almost always prevents OTA installs. To fix this, locate the Stock Recovery image for your device and flash it using DD, Fastboot or Creator device.

Relock bootloader

Some devices will not apply OTA updates when the bootloader is unlocked. This is another mechanism for trying and broking users to brick their devices. Most manufacturers allow you to lock the bootloader again. It is also possible to use the DD command to set the bootloader in factory state on HTC devices with S-off bits.

Remove flag

Similarly, the OTA update can detect an unlock bootloader, a taper flag can be set on some devices, indicating that system files have been modified. This can prevent OTA updates from being downloaded. Again, if the S-Off set is set, the Taper flag can be removed with the DD command.

Apply on OTA

When you are back to the custom system and recovery images and if necessary, the bootloader has been locked again, then you are ready to implement the manufacturer's OTA update. By doing this, special recovery on the progress screen - Keep an eye out for any issue to look for.

Restore for backup

Hope your device will not be a problem. Occasionally, however, a wipe may be required to run the system again, in this case you will need to restore your backup. If using android and re-flash recovery, make sure to restore only / data segmentation to avoid overwriting OTA changes.

Future proof

To make it easier to implement OTA in the future, it is a good idea to back up so that next time the OTA drops, you can return the split back to the stock position. To make it easier for your fellow users, you can also upload backups (subdivide your / data split) in a forum like XDA developers.