05-12-2018, 10:39 AM
So I’ve done some research and apparently it’s a known problem with chrome books that if the battery dies the only OS available is the chrome OS (which is no longer on this chromebook 
)
From wiki.archlinux site:
Warning: If you do not set the GBB flags then your system might become corrupted on empty battery, resetting dev_boot_usb dev_boot_legacy to their default values, forcing you to recover Chrome OS and wiping your Arch Linux installation on the internal storage, though it might be possible to modify Chrome OS recovery image to set these values again [7].
Warning: If you do not disable the write protection before setting the GBB flags you endanger wiping out the RW-LEGACY part of the firmware (i.e. SeaBIOS) and your system might not boot (should be recoverable with Chrome OS recovery media). Updated versions of set_gbb_flags.sh will not let you set the GBB flags without disabling the write protection.
I found this article on reddit which helped a lot:
https://www.reddit.com/r/chromeos/commen..._ran_flat/
So I will fiddle around with it soon as I have another chromebook (Acer) that I left in SA on which I performed the same steps and given that I did not go further to set seabios as the default I believe if I understand correctly I will return to the same issue with it.
I know have to find out how I can get a copy of the chrome OS...gratis ideally as it once existed on both these chromebooks.
)From wiki.archlinux site:
Warning: If you do not set the GBB flags then your system might become corrupted on empty battery, resetting dev_boot_usb dev_boot_legacy to their default values, forcing you to recover Chrome OS and wiping your Arch Linux installation on the internal storage, though it might be possible to modify Chrome OS recovery image to set these values again [7].
Warning: If you do not disable the write protection before setting the GBB flags you endanger wiping out the RW-LEGACY part of the firmware (i.e. SeaBIOS) and your system might not boot (should be recoverable with Chrome OS recovery media). Updated versions of set_gbb_flags.sh will not let you set the GBB flags without disabling the write protection.
I found this article on reddit which helped a lot:
https://www.reddit.com/r/chromeos/commen..._ran_flat/
So I will fiddle around with it soon as I have another chromebook (Acer) that I left in SA on which I performed the same steps and given that I did not go further to set seabios as the default I believe if I understand correctly I will return to the same issue with it.
I know have to find out how I can get a copy of the chrome OS...gratis ideally as it once existed on both these chromebooks.