Using the firmware-util.sh script, I was able to flash the UEFI full firmware, and it reported success. However, I went and did a reboot (not shutdown) from ChromeOS. After that reboot, I let it sit for 3-5 minutes, and nothing ever appreared on the screen.
The only thing I can think of is even after following the instructions in the Google docs, the utility asked about unlocking something else and said if you were going to do the UEFI firmware to do that, so I said yes. However, now I’m wondering if that was the correct course of action, as I thought I already did everything needed beforehand.
I’d have to check on my device, but there may be logs about the new RO verification failing or something. Coreboot itself doesn’t output any logs by default though, so not much we can debug with that other than flashing it again. If that fails, you can flash a custom build that does output to the serial console.
Using a chip programmer and a not-very-fun-to-use WSON8 probe (5x6mm for this model), I was able to flash enough of the chip for it to boot. I then did a flashrom verifym which failed, did firmware restore (using a modified version of the firmware-util script to not check if I was on ChromeOS), and then the verify was good.
It has been restored to factory, is in its box, and it will be returned to Best Buy this evening. Definitely not the model for me.
I’m curious why you bought a new Chromebook from BestBuy for running Linux / Windows. If you’re buying new then are you really saving any money vs buying a laptop that can officially run Windows / Linux?
the issue with your inital flash aside, you could have just reflashed the UEFI firmware and all would have been fine. FROSTFLOW works fantastically under Linux.
Ah. Well, in any case I overpaid for it, so it was gonna get returned anyway. I got a Chromebook 515 Plus (OMNIGUL) for $199 refurb, which is good for this experiment…I eventually want to get Heads / Qubes on it. I did get the UEFI firmware on there, and the installer booted successfuly…so now trying to get heads to build. bzImage too big is where I am at the moment…
You can flash using the suzyQ cable OP linked in their initial post or you can use a chip programmer. I haven’t seen the board in question but most likely it has a WSON chip, either 5x6 pr 8x6 - which requires a special pogo pin adapter (unless you want to desolder the chip to flash it)
from the flashing device, open a terminal to /dev/ttyUSB1 and run the ccd open command there, and verify it’s open. then run ccd reset factory as needed on a Ti50 device.
Then flash the latest UEFI firmware, not the stock firmware, unless you’re wanting to go back to stock for some reason.