From 3e58be1e2457a35aa6dcfd36ee9b792072c8da8a Mon Sep 17 00:00:00 2001 From: osm0sis Date: Fri, 5 Jul 2024 14:22:40 -0300 Subject: [PATCH] Correct type prop heading, add another missing prop - if sys.oem_unlock_allowed is reset to 0 before sys.boot_completed is 1 it results in a boot hang and then reboot or poweroff - even though sys.oem_unlock_allowed has been reset to 0 the act of opening Developer Options will set it back to 1 until next reboot --- module/post-fs-data.sh | 4 ++-- module/service.sh | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/module/post-fs-data.sh b/module/post-fs-data.sh index 026f678..ebf3d14 100644 --- a/module/post-fs-data.sh +++ b/module/post-fs-data.sh @@ -34,11 +34,11 @@ resetprop_if_diff ro.is_ever_orange 0 for PROP in $(resetprop | grep -oE 'ro.*.build.tags'); do resetprop_if_diff $PROP release-keys done + +# Other for PROP in $(resetprop | grep -oE 'ro.*.build.type'); do resetprop_if_diff $PROP user done - -# Other resetprop_if_diff ro.debuggable 0 resetprop_if_diff ro.force.debuggable 0 resetprop_if_diff ro.secure 1 diff --git a/module/service.sh b/module/service.sh index 4660674..3d3df2a 100644 --- a/module/service.sh +++ b/module/service.sh @@ -37,3 +37,6 @@ resetprop_if_diff vendor.boot.verifiedbootstate green resetprop_if_diff ro.boot.verifiedbootstate green resetprop_if_diff ro.boot.veritymode enforcing resetprop_if_diff vendor.boot.vbmeta.device_state locked + +# Other +resetprop_if_diff sys.oem_unlock_allowed 0