Blank Google Dev Mode Screen on AltFW (Control+L) on ATLAS after RW_LEGACY Flash

[connorpb]

Hello!

Attempting to dual boot Linux and ChromeOS using the RW_LEGACY firmware on a Pixelbook Go (ALTAS). Can download the firmware with curl (in the VT2 terminal), run it, and select 1 to install/update the RW_LEGACY firmware. It presents options to install either with SeaBIOS or edk2. I have actually tried both ways, but either way has the same result so far - apparent success, but on reboot and hitting control L on the white dev mode "OS verification is off" screen, it remains on that white Dev mode screen (with the Google branding in the header and the footer with the model number) but the message about OS verification is off disappears. Pressing Escape returns me to the "full" Dev mode screen with the "OS Verification is off" message. Otherwise they look the same. I'm unable unfortunately to get to the SeaBIOS or edk2 boot loader screens.

I haven't seen any documentation on this particular screen or issue - sorry if I missed it - I'm truly at a loss for what to do next. I haven't disabled write protection, but my understanding is that ideally I shouldn't need to.

Thank you for all your work!

[MrChromebox]

Sounds like Google may have updated the stock firmware in a way that broke RWL, given that neither payload works, and the SeaBIOS payload hasn't been updated in 5+ years. Not sure there's much I can do unfortunately

[connorpb]

Darn! If you think this will affect all ATLAS pixelbook gos, it may be worth updating the device compatibility list. No way to roll back the stock firmware to a compatible version I suppose? In any rate, thanks anyway!

[MrChromebox]

when you run my script, what does it identify as the firmware version and date on your device?

[connorpb]

Platform: Intel Kabylake
FwType: Stock ChromeOS w/ RW_LEGACY
FwVer: Google_Atlas.11827.198.0 (08/24/2021)

[MrChromebox]

ok, so not a recent change then. can you perform a USB recovery and then retry flashing RWL?