Any device booting RW_LEGACY - can I still boot when battery runs empty?

I read this yesterday but could not find the Google bug report so I can refer you to this link.

Is it true that the dev_boot_legacy flag is battery backed?

When I boot in RW_LEGACY mode, dev_boot_legacy flag is set to 1.
And when battery runs empty this flag is flipped back to 0.

Consequence is I cannot boot into my linux partition and worse not even to chromeOS complaining “missing …”. Only remedy is a usb drive recovery.

Can you confirm this known issue with RW_LEGACY booting?

Why it is important?

As older chromebooks like my Dell 7486 has less than 65% health. On multi-dat holidays if I don’t put the charger plug into the device, it is almost certain that battery will be empty after I return home.

it’s true on a lot of older devices, but I’ve not tested it recently on newer ones. YMMV.

RW_LEGACY is for dual booting Linux + ChromeOS only. If you’ve wiped ChromeOS and installed Linux while using RWL, you’re doing it wrong and taking a risk.

If you have ChromeOS installed, then you can just re-enable the crossystem flag.

thanks again @MrChromebox.

I’m considering moving earlier to UEFI boot. Screen rotation and tablet lock works.