Some users like to keep their phones running the most official and stock system. Sadly, current Superuser installation process is a little bit more complicated then it was in the past (f.g. su binary needs to be running as a daemon). Flashing official SuperSu package makes OTA updates for the particular device impossible to be installed, because every OTA package during the installation process checks the integrity (with SHA-1) of each file on the system partition. Current SuperUser packages are modifying at least one file on the system partition: system/etc/install_recovery.sh. With that modified file, OTA installation will fail and you won't be able to update your device with the latest software. Additionally, SuperUser access is not always enough. It's good to have adb secure disabled and this can be done in the ramdisk inside boot.img.
Device rooted with the above method should have no problems installing latest official OTA update because:
a) OTA update checks for files integrity, but it doesn't check if any extra files were added to the system partition
b) OTA update doesn't check the integrity of the boot.img, so you can even flash a custom kernel if you want
Device rooted with the above method should have no problems installing latest official OTA update because:
a) OTA update checks for files integrity, but it doesn't check if any extra files were added to the system partition
b) OTA update doesn't check the integrity of the boot.img, so you can even flash a custom kernel if you want
Keep in mind that once you change or remove any file from the system partition you won't be able to receive OTA updates. You can only add new files, but you can't modify/remove existing ones.
Details:
- boot.img source: 4.16.401.10
- Target device: HTC One M8 (0P6B10000)
- Target device OS version: 4.16.401.10
Included in the package:
- Latest SuperSu app (Superuser.apk) and binaries (su, daemonsu)
- Proper init.d script to run daemonsu binary as a daemon
- Special wp_mod.ko kernel module to disable HTC system RW protection
- Proper init.d script to insert the wp_mod.ko module into the kernel
- Busybox
- Sysrw/sysro binaries
Custom boot image:
- Disabled ro.adb.secure and ro.secure
- Disabled USB debugging icon on statusbar
- Enabled USB debugging by default
- Init.d support
- Removed trigger command to execute install_recovery.sh to prevent stock recovery from being re-installed after each system reboot
Installation guide (bootloader has to be unlocked)
- Extract the downloaded .rar package (boot.img, stock_recovery.img, Root_and_BusyBox.zip and Read_Me.txt)
- Flash custom recovery of your choice
- Flash boot.img using fastboot flash boot boot.img command in the fastboot mode
- Flash Root_and_BusyBox.zip package in the custom recovery
- Flash stock_recovery.img using fastboot flash recovery stock_recovery.img command in the fastboot mode
- Reboot the device
Credits:
Chainfire for the SuperSu
flar2 for the wp_mod.ko module
XDA:DevDB Information
[GUIDE] How to add root access & and keep official OTA updates | 4.16.401.10, Tool/Utility for the HTC One (M8)
Contributors
mike1986.
Version Information
Status: Stable
Created 2014-05-18
Last Updated 2015-02-28
Last edited: