After successfully installing Linux Mint Cinnamon on a Chromebook, the device boots into "Developer Mode" instead of Linux

How can make it boot directly into Linux? I don’t want to go to the BIOS Boot Manager every time to boot Linux.

I installed RW_LEGACY firmware and once I was inside Linux, I clicked on the desktop icon “Install Limux Mint” and chose “Erase disk and install Linux Mint”.

Acer Chromebook 514 CB514-1WT

The disk is not gonna help. Erasing the disk UNINSTALLS ChromeOS, but keeps the firmware, which is necessary. You can’t remove the firmware screen, but you can shorten time out (it will show less time). Run ChromeOS if you can, remove write protection, press Ctrl + Alt + ->, login as chronos and type the following. “cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh” Press 3 after loading, and type the number corresponding to Short (2 sec) Legacy Firmware. Now it will by default boot to Linux instead of ChromeOS.

RW_LEGACY is for dual booting ChromeOS + Linux. If installing just Linux, you should use the UEFI Full ROM firmware

Alright. So I understand I got two options But I can’t run ChromeOS to run that firmware script again, I only see this on the image and CTRL+ALT+> doesn’t work

Haha! You NEED to boot to ChromeOS first, pressing the Ctrl + D keys or pressing Boot from internal disk. Otherwise the solution ain’t working. Unfortunately this may mean recovery. Translation=You will have to do this all over again. Sorry :frowning:

Or otherwise just keep clicking Ctrl + L on startup, should work.

SMH. you run it from Linux

That CTRL+L tip takes me to Linux and that’s just fine. I can live with instead of going through the menus every time to boot. I really don’t want to do this firmware stuff again. I might try something else instead of Linus Mint next time. Guys, I’m a total noob and I will probably look back at this some day and laugh. Thanks for your help :crazy_face:

then just use the script to set the firmware flags to default legacy boot and short boot delay

Error. Hardware write-protect enabled, cannot set Boot Options / GBB Flags

seems pretty self-explanatory, no?

Since you’re using RW_LEGACY to boot Linux against recommendations, just be aware that at some point the flag to enable legacy boot might get cleared (battery drained, system error) leaving you unable to boot any OS, and necessitating a ChromeOS recovery which will wipe your existing setup.

If you want to run Linux, disable WP and flash the correct firmware.