I found this thread and it somewhat touches on a topic I just posted about and can’t quite understand:
I do understand that the firmware script won’t unlock/disable the write-protect. However, given that I have a SuzyQ adapter/cable, I thought I’d be able to unlock the write-protect from either Chromebook itself, using “loopback”, running Ubuntu, or use another Linux laptop and connect the SuzyQ cable from that machine to my Chromebook.