Hello! I’m hoping you guys have some wise words for me, because I’m at my wit’s end with this device.
I have three of these. I want to install Linux Mint on them, using MrChromebox’s guide and firmware utility script, so I can completely remove ChromeOS. I spent a week trying to open the GSC on ONE of them. Yesterday, I finally did it! But now that I’m trying to do it on the next ones, it’s not working. I thought I knew what solved it, but it turns out I was wrong.
I’ve been following MrChromebox’s guide: Disabling Firmware Write Protection | MrChromebox.tech
Specifically the section for using CCD & SuzyQable.
The things I tried yesterday, in order:
- Took the little battery inside out
- Used the method in this post: Disable firmware write protect from Linux using SuzyQ cable - #4 by mlanner
The linux device I used was another Chromebox (Chromebox 4, also Asus)
This gave me “no access”/”permission denied” style responses to everything I did. - Recovered ChromeOS via USB (inspired by VitaCell’s post in this one: HP Chromebook 15a (YAVIKS/NISSA) gsctool doesn't work - #4 by vita_cell )
Since the method they used seems quite complicated, I figured I could try something simpler; using the “Long-term support (Enterprise only)” option when creating the recovery USB.
And like a miracle, it worked!
I ran gsctool -a -o like normal, pressed the power button like normal, it left developer mode like always, and I enabled developer mode again like always, and when I got back into the VT2 terminal I started by running gsctool -a -I, and the GSC was opened! I followed the guide from there (connecting the SuzyQable to the USB-C port above the power connector and the USB-A end to the port on the backside) and everything went smoothly, just like MrChromebox’s guide described.
But then of course, I tried on the next Chromebox (same model) - used the recovery USB, then entered developer mode, ran gsctool -a -o and pressed the power button until it rebooted into verified mode, entered developer mode again, entered VT2 terminal, ran gsctool -a -I, and… it hadn’t worked. I thought it was because the battery wasn’t removed, so I removed the battery and tried again. Didn’t work. I thought it might be some magic that happened when I connected via another linux device. Didn’t work. Tried again from the Chromebox 5 itself, didn’t work.
It just keeps saying it’s locked.
Anybody have some sage advice? Some idea of what might have worked, out of all the things I tried?
Any help or words of reassurance would be greatly appreciated!
EDIT: Solved it myself! Also, I’m an idiot! My method of entering developer mode/recovery mode was my mistake. So far I’ve been following the method I got from a youtube video about turning off “meet mode” on these devices, and it said you needed to unplug the device power cable entirely, then hold the recovery button down while plugging the power cable back in, and keep holding it until you see the recovery screen. But I see that MrChromebox’s method is just.. turning the device off, then holding the recovery button while pressing the power button to turn it on. When I followed this method, I could consistently lock and unlock the GSC! I am embarrassed, and I am over the moon!
It must be that some chip on the Chromebox 5 holds the state of the CCD/GSC, and that it gets reset when you unplug the power cable entirely. Goddammit.