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
This commit is contained in:
osm0sis
2024-07-05 14:22:40 -03:00
parent 662b9c59c7
commit 3e58be1e24
2 changed files with 5 additions and 2 deletions

View File

@@ -34,11 +34,11 @@ resetprop_if_diff ro.is_ever_orange 0
for PROP in $(resetprop | grep -oE 'ro.*.build.tags'); do for PROP in $(resetprop | grep -oE 'ro.*.build.tags'); do
resetprop_if_diff $PROP release-keys resetprop_if_diff $PROP release-keys
done done
# Other
for PROP in $(resetprop | grep -oE 'ro.*.build.type'); do for PROP in $(resetprop | grep -oE 'ro.*.build.type'); do
resetprop_if_diff $PROP user resetprop_if_diff $PROP user
done done
# Other
resetprop_if_diff ro.debuggable 0 resetprop_if_diff ro.debuggable 0
resetprop_if_diff ro.force.debuggable 0 resetprop_if_diff ro.force.debuggable 0
resetprop_if_diff ro.secure 1 resetprop_if_diff ro.secure 1

View File

@@ -37,3 +37,6 @@ resetprop_if_diff vendor.boot.verifiedbootstate green
resetprop_if_diff ro.boot.verifiedbootstate green resetprop_if_diff ro.boot.verifiedbootstate green
resetprop_if_diff ro.boot.veritymode enforcing resetprop_if_diff ro.boot.veritymode enforcing
resetprop_if_diff vendor.boot.vbmeta.device_state locked resetprop_if_diff vendor.boot.vbmeta.device_state locked
# Other
resetprop_if_diff sys.oem_unlock_allowed 0