3 ms·

You have to be able to put the device in developer mode to load non-google signed OS images. I'm not sure it's mandated that this be possible for every device

You have to be able to put the device in developer mode to load non-google signed OS images. I'm not sure it's mandated that this be possible for every device so I would absolutely do some research to make sure the device I'm about to buy allows developer mode. On old/early chromebooks you had to physically open them (voiding the warranty) and remove a special screw to enable developer mode for example. Also even when you have developer mode enabled the stock chromebook firmware is a little annoying and won't boot until you press ctrl-d on the keyboard to confirm you agree to booting an unsigned image. There is no way to disable this behavior and it happens every single boot whether you want it or not. The Mr. Chromebox firmware this article mentions has to be flashed to a device to remove this annoyance and make the device boot like regular laptops.

Aaron2222 3y ago
I think you have developer mode confused with the firmware write-protect switch. As far as I'm aware, every Chromebook has allowed enabling developer mode without opening the device. Disabling the firmware write-protect (which does let you disable the ctrl-d requirement, and is what you need to do to install the UEFI firmware this guide refers to) used to require opening the device (to either remove a screw or flip a switch), but can now be done over CCD (closed case debugging) using the appropriate cable, as well as by opening the device.
jacquesm 3y ago
> On old/early chromebooks you had to physically open them (voiding the warranty) and remove a special screw to enable developer mode for example. Same for some chromeboxes, usually the screw is pretty easy to spot, look near the corners and near the ssd.
Octoth0rpe 3y ago
> You have to be able to put the device in developer mode to load non-google signed OS images. Yes, but what kernel is running before you do this? answer: linux.

Aaron2222 3y ago

I think you have developer mode confused with the firmware write-protect switch. As far as I'm aware, every Chromebook has allowed enabling developer mode without opening the device. Disabling the firmware write-protect (which does let you disable the ctrl-d requirement, and is what you need to do to install the UEFI firmware this guide refers to) used to require opening the device (to either remove a screw or flip a switch), but can now be done over CCD (closed case debugging) using the appropriate cable, as well as by opening the device.

jacquesm 3y ago

> On old/early chromebooks you had to physically open them (voiding the warranty) and remove a special screw to enable developer mode for example. Same for some chromeboxes, usually the screw is pretty easy to spot, look near the corners and near the ssd.

Octoth0rpe 3y ago

> You have to be able to put the device in developer mode to load non-google signed OS images. Yes, but what kernel is running before you do this? answer: linux.