4 ms·
Verified boot is only enforcing on -user builds. Lineage ships -userdebug builds. Furthermore Lineage's official root addon writes to /system. You can't have a
by SubzeroCarnage 5y ago
Verified boot is only enforcing on -user builds.
Lineage ships -userdebug builds.
Furthermore Lineage's official root addon writes to /system. You can't have any additional changes to system or else verified boot won't boot.
You can't have it both ways as it stands.
That isn't to say they are incompatible, you can compile-in root support before the system hashes are generated and then you can have a locked bootloader with verified boot with root support.
But you cannot make any additional changes to /system with that root power afterwards.
- zozbot234 5y ago> But you cannot make any additional changes to /system with that root power afterwards. Not a showstopper, as modern root solutions like Magisk support "systemless" root, via file system overlays.
- SubzeroCarnage 5y agoI am not sure how systemless root interacts with verified boot. I've never tried it myself.
- commoner 5y agoInstalling Magisk requires you to patch the bootloader or recovery image, which would break verified boot: https://topjohnwu.github.io/Magisk/install.html https://topjohnwu.github.io/Magisk/install.html The only way to preserve verified boot with Magisk is for the bootloader or recovery image to have Magisk compatibility built-in prior to signing. I don't think any flavor of Android that supports verified boot is currently doing this.
- commoner 5y ago> Furthermore Lineage's official root addon writes to /system. LineageOS no longer offers an official root add-on as of December 2019. https://www.xda-developers.com/lineageos-dropping-superuser-addonsu-implementation-favor-magisk-manager/ https://www.xda-developers.com/lineageos-dropping-superuser-... The most common rooting solution is Magisk, which is systemless.