running linux mainline on arm chromebooks - for example: samsung xe303c12 and xe503c12 (snow and peach), acer c100, c101 and c201 (veyron speedy, minnie etc. and gru bob and kevin), medion s2013 and s2015 (veyron jaq, mighty etc.), acer cb5 311 (nyan big), lenovo n23, acer r13 (oak elm and hana), lenovo duet (kukui krane) and most probably many many more over time ...
I updated the postmarketOS wiki to something similar to what you have because on some old rk3288 devices the futility flash commands they had failed.
One thing you might also add is that /usr/share/vboot/bin/set_gbb_flags.sh without any arguments will print out the list of all the allowed flags, and /usr/share/vboot/bin/get_gbb_flags.sh -d -e will show you the current flags "sum" and DESCRIBE the ones that are active. You can also use this against a backup ROM so if you used flashrom -p linux_mtd -r somebackup.bin to make a backup, you can supply the path to that and run get_gbb_flags.sh to view the flags that were set when the backup was created.
https://github.com/hexdump0815/linux-mainline-on-arm-chromebooks/blob/3e5231cbdd7309b214325525ae884b9206553c03/readme.md?plain=1#L157-L163
I updated the postmarketOS wiki to something similar to what you have because on some old rk3288 devices the
futility flash
commands they had failed.One thing you might also add is that
/usr/share/vboot/bin/set_gbb_flags.sh
without any arguments will print out the list of all the allowed flags, and/usr/share/vboot/bin/get_gbb_flags.sh -d -e
will show you the current flags "sum" and DESCRIBE the ones that are active. You can also use this against a backup ROM so if you usedflashrom -p linux_mtd -r somebackup.bin
to make a backup, you can supply the path to that and runget_gbb_flags.sh
to view the flags that were set when the backup was created.