I had RW_LEGACY working perfectly for 3 days, but today the alternative bootloader disappeared. When I try to re-install it using the script, it doesn’t work. My script menu shows “Fw WP: Enabled” in red, even though I haven’t changed any hardware settings since it was working before.
Steps to Reproduce
Open Terminal/Crosh.
Run MrChromebox script.
Attempt to select option 1 (RW_LEGACY).
Attempt to install RW_LEGACY. > Result: The script says “RW_LEGACY failed to flash.” and I see “Fw WP: Enabled” in red at the top of the menu.
had RW_LEGACY working fine 3 days ago, but now the option is gone from the boot menu. When I try to re-install it using the script, it fails. My Hardware WP is currently Enabled.
there is no correlation or relationship of any kind between the WP status and RW_LEGACY, at all.
The firmware WP status being enabled is expected if you haven’t disabled it.
if the script fails to flash RW_LEGACY, it provides a full log as to the issue at /tmp/flashrom.log pastebin that file and link here.
I’ve tried cat /tmp/flashrom.log and the cp commands multiple times, but I keep getting ‘No such file or directory.’ > It seems the script is exiting before the log is even written. I am on telticn50 running ChromeOS v144. Since it says Invalid region specified: "RW_LEGACY", is it possible that v144 changed the FMAP? Is there a command I can run to show you my current partition layout instead?
