IMPORTANT: WE CYBROZE holds no responsibility for issues you might encounter as part of this post.
You might have come across problems when installing OTA updates to your rooted Android device, I know I have. In most instances the ROM I am using isn’t the stock ROM (along with custom recovery installed) and that is when the OTA updates* fail. OEM’s will nearly always check Android checksums match, as modified ROMs will have a different checksum to that installed by the OEM. This then leads to the well documented problem of OTA updates failing on rooted devices.
Many of my readers have encountered problems mainly with non-stock ROMs on OEM devices such as, HTC and Samsung, which block you from updating OTA or via USB. I will now show you how to prepare your rooted Android device for OTA updates:
Create a backup using a custom recovery tool. Use a tool such as Titanium to create your backup. Move the backup file on to your computer.
SuperSU includes a ‘Survival mode’ – make sure this is checked.
Next, you will need to flash your boot and system partitions back to stock version. You can do this with fastboot or recovery.
Using your stock recovery image you will need to flash this using fastboot or dd (see bootnote).
Bootloader? Some devices will not allow you to install OTA updates if the bootloader is unlocked. You can use dd to reset the bootloader back to factory mode.
Tamper flags – these are set by OEMs to detect when a system has been modded. This will also stop OTA updates. You can use dd (see How to use dd to remove tamper flag:) or Triangle Away if you use a Samsung device.
You should now have installed your custom system and recovery images as well as locked bootloader. You can now reboot the device and attempt the OTA update.
You may need to wipe the system if you experience issues. You can do this by installing your backup as mentioned above. TIP: If using a custom recovery tool, only re-flash the /data partition.
Remember, OTA updates will only work on stock versions, so it’s a good idea to backup prior to do the update. This allows you to revert the partitions back to stock.
*OTA updates will nearly always fail on a rooted device. OEMs will actively check the device for root(SU) / unlocked bootloader and of course tamper flags.
Bootnote: The dd command is very powerful. If you don’t know what you are doing, don’t use this:
How to use dd to remove tamper flag:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne ‘\x00′ | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(Copy/paste the above)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
You might have come across problems when installing OTA updates to your rooted Android device, I know I have. In most instances the ROM I am using isn’t the stock ROM (along with custom recovery installed) and that is when the OTA updates* fail. OEM’s will nearly always check Android checksums match, as modified ROMs will have a different checksum to that installed by the OEM. This then leads to the well documented problem of OTA updates failing on rooted devices.
Many of my readers have encountered problems mainly with non-stock ROMs on OEM devices such as, HTC and Samsung, which block you from updating OTA or via USB. I will now show you how to prepare your rooted Android device for OTA updates:
Create a backup using a custom recovery tool. Use a tool such as Titanium to create your backup. Move the backup file on to your computer.
SuperSU includes a ‘Survival mode’ – make sure this is checked.
Next, you will need to flash your boot and system partitions back to stock version. You can do this with fastboot or recovery.
Using your stock recovery image you will need to flash this using fastboot or dd (see bootnote).
Bootloader? Some devices will not allow you to install OTA updates if the bootloader is unlocked. You can use dd to reset the bootloader back to factory mode.
Tamper flags – these are set by OEMs to detect when a system has been modded. This will also stop OTA updates. You can use dd (see How to use dd to remove tamper flag:) or Triangle Away if you use a Samsung device.
You should now have installed your custom system and recovery images as well as locked bootloader. You can now reboot the device and attempt the OTA update.
You may need to wipe the system if you experience issues. You can do this by installing your backup as mentioned above. TIP: If using a custom recovery tool, only re-flash the /data partition.
Remember, OTA updates will only work on stock versions, so it’s a good idea to backup prior to do the update. This allows you to revert the partitions back to stock.
*OTA updates will nearly always fail on a rooted device. OEMs will actively check the device for root(SU) / unlocked bootloader and of course tamper flags.
Bootnote: The dd command is very powerful. If you don’t know what you are doing, don’t use this:
How to use dd to remove tamper flag:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne ‘\x00′ | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(Copy/paste the above)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
إرسال تعليق