Morphius Unbricking

Support
1

Hi everyone,

I have two C13 Yoga/Morphius chromebooks, and one conversion went smoothly and the other did not. I’m trying to unbrick the failed one - I’ve got a SuzyQ, I’m able to talk to the bricked computer via serial connection, etc. I’ve followed the guide, and when I run sudo flashrom -p raiden_debug_spi:target=AP -r coreboot_edk2-morphius-mrchromebox_20240908.rom, flashrom will read ok, but seems to exit without writing:

flashrom unknown on Linux 6.8.0-44-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Raiden target: 2
Found Winbond flash chip “W25Q128.W” (16384 kB, SPI) on raiden_debug_spi.

This flash part has status UNTESTED for operations: WP
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to [email protected] if any of the above operations
work correctly for you with this flash chip. Please include the flashrom log
file for all operations you tested (see the man page for details), and mention
which mainboard or programmer you tested in the subject line.
Thanks for your help!
Reading flash… done.

Anyone have any ideas?

2

Update: solved this by switching to a different recovery computer! For future reference, I was using the working Morphius chromebook running Mint, and I switched to a Debian system, and that was able to write the firmware without an issue.

3

Yeah, I find it a bit odd that Linux Mint, even if running the Debian edition, refuses to write to the BIOS for some reason. It happened for me as well on my Morphius as well as another system.

4

Can you use ``` instead of quotes for the code blocks?

```
Code
```

`inline code`

5

You may have missing udev rules or an outdated version of flashrom.

For the udev rules, the dirty way is to just run flashrom as root.

For the outdated problem, you need to get an up-to-date binary

6

Sorry, it was my first post here and to be completely honest, it’s been a while since I used a forum like this (I miss the old Internet!). I was looking for the code markup and couldn’t find it. I’ll do better in the future!

Luckily I did resolve this issue using a Debian machine. Another commenter said they had a similar issue using Mint as well.

1 Like
7

Did you run flashrom as root in any case?

If not this might really be because of udev rules