Verity enablement overhaul

No change to AVB devices except for enabling on more
Verity devices have the potential to regress by not booting
No change to non-verity/avb devices
Tested working on: mata, cheeseburger, fajita

Signed-off-by: Tad <tad@spotco.us>
This commit is contained in:
Tad 2021-11-01 21:35:41 -04:00
parent 898c040ead
commit 809e03833e
15 changed files with 142 additions and 154 deletions

View file

@ -285,21 +285,7 @@ if enterAndClear "device/asus/msm8916-common"; then
rm -rf Android.bp sensors; #exact duplicate in asus/flo #XXX be careful with this
fi;
if enterAndClear "device/google/dragon"; then
enableVerity; #Resurrect dm-verity
fi;
if enterAndClear "device/huawei/angler"; then
enableVerity; #Resurrect dm-verity
fi;
if enterAndClear "device/htc/flounder"; then
enableVerity; #Resurrect dm-verity
fi;
if enterAndClear "device/lge/bullhead"; then
enableVerity; #Resurrect dm-verity
fi;
if enterAndClear "device/lge/msm8996-common"; then
sed -i '3itypeattribute hwaddrs misc_block_device_exception;' sepolicy/hwaddrs.te;
@ -307,7 +293,6 @@ fi;
if enterAndClear "device/moto/shamu"; then
#git revert --no-edit 05fb49518049440f90423341ff25d4f75f10bc0c; #restore releasetools #TODO
enableVerity; #Resurrect dm-verity
fi;
if enterAndClear "device/oneplus/oneplus2"; then