OK I got lazy (or smart?) and patched the lk partition. It has the code that enables the power-on write protection from sec1-super. I changed it to sec1-tee2 and shrunk it. Then I decided I wanted boot writable, and I put sec1-lk2 and it must not have that name in the table because it just lost the entire 2nd write protection but whatever.
Here is what was write protected before:
Write Protect Groups 36-321 (Blocks 589824-5275647), Power-on Write Protection
22 589824 593919 2.0 MiB 0700 sec1
23 593920 594943 512.0 KiB 0700 efuse
24 594944 726015 64.0 MiB 0700 md1img
25 726016 758783 16.0 MiB 0700 md1dsp
26 758784 760831 1024.0 KiB 0700 spmfw
27 760832 762879 1024.0 KiB 0700 mcupmfw
28 762880 795647 16.0 MiB 0700 gz1
29 795648 828415 16.0 MiB 0700 gz2
30 828416 832511 2.0 MiB 0700 lk
31 832512 836607 2.0 MiB 0700 lk2
32 836608 885759 24.0 MiB 0700 boot
33 885760 1016831 64.0 MiB 0700 vendor_boot
34 1016832 1033215 8.0 MiB 0700 logo
35 1033216 1049599 8.0 MiB 0700 dtbo
36 1049600 1051647 1024.0 KiB 0700 vbmeta
37 1051648 1053695 1024.0 KiB 0700 vbmeta_system
38 1053696 1055743 1024.0 KiB 0700 vbmeta_vendor
39 1055744 1061887 3.0 MiB 0700 tee1
40 1061888 1081343 9.5 MiB 0700 tee2
41 1081344 5275647 2.0 GiB 0700 super
Gflip6_TF:/data/local/tmp # ./mmc writeprotect user get /dev/block/mmcblk0
Write Protect Group size in blocks/bytes: 16384/8388608
Write Protect Groups 0-1 (Blocks 0-32767), Power-on Write Protection
Write Protect Groups 2-924 (Blocks 32768-15155199), No Write Protection
Write Protect Groups 925-925 (Blocks 15155200-15171583), Permanent Write Protection
Write Protect Groups 926-931 (Blocks 15171584-15269887), No Write Protection
EDIT: File removed. Just use /vendor/bin/write_protect 0
- flashboot flash lk lk-neutron.img
- mount -o rw,remount /
- rm -rf /system/app/Chromium
- reboot. see if it's gone.