“These updates depend on many device-specific non-Google hardware and software providers that work with Google to provide the highest level of security and stability support,” said Peter Du, communications manager for ChromeOS. “For this reason, older Chrome devices cannot receive updates indefinitely to enable new OS and browser features.”
That's what they should be doing, but it isn't what they're going to do, unfortunately.
Kimathi Bradford, a 16-year-old Oakland tech repair intern, has looked into whether there was a way to replace the outdated Chromebook software with a non-Google brand, but it ended up being a lot of work, Kimathi said, and the open-source replacement wasn’t up to par. “It’s like the Fritos of software,” he said. “No one really wants to use it.”
Now, I'm not sure if what they tried was Linux, but I wouldn't be too surprised. The younger generations grew up with smartphones; I feel as though operating systems will become more streamlined and opaque as time goes on. I suspect we'll have to contend with the phonification of mainstream computing in the coming years.
Most Chromebook's firmware is Coreboot, but it's running a Depthcharge payload instead of UEFI (or BIOS or whatever). Mr. Chromebox maintains UEFI Coreboot payloads and install tools for a wide variety of (x86) Chromebooks, which can be used to flash a normal UEFI payload and boot normal OSes. It's strictly possible to boot normal Linux systems on a the Depthcharge payload modern Chromebooks use, but uh... here's the gentoo wiki on it, it's a substantial pain in the ass.
Sure, drop me a note with the details and I'll see if I can give you a hand. I'm not super expert in all the specifics of the Chromebook ecosystem, but I have good general computer/Unix skills and have hacked a couple so I know where to look for resources.
At a guess - they're likely selling those laptops at a loss and making the money back on (hopefully) service contracts or (probably) selling your data. As soon as you install a custom OS they won't support you (so you won't buy support) and they won't be able to sell your data.
I manage my schools IT - and when we started out a few years ago my board were pushing aggressively for Chromebooks. The service provider were talking about how they could roll out hundreds of Chromebooks at the touch of a button. When I asked about the lifespan of a Chromebook I got vague answers. I knew we would get a couple of years max out of each one so I instead pushed for much more expensive MacBooks. 5 years on and we are still using our original MacBook we got back then, with photoshop and other software.
Ironically the only way to use some old Macbooks these days is to put Chrome OS Flex on them. Apple is far more aggressive about killing off old hardware when it feels like it. You can still use them as-is of course but over time the browser and other web based apps degrade and refuse to work because of issues with TLS, CA certs (expired), discontinued backend APIs and unsupported web content APIs.
The problem comes down to education institutions. I remember when we got Chromebooks in my highschool (8 years ago) admins forgot to turn of developer mode and half the school unenrolled the Chromebook managing to bypass all restrictions. This went on for half a year until one day our school needed to run a state exam (more for measure of schools performance not as a college entrance exam or anything).
The computerized testing program required deploying a specific chrome app accessible when chrome book is logged out (can't just download from chrome web store). When they tried to push the client since half of Chromebooks were unenrolled it failed. This required the school it to recall pretty much all chrome books to manually re enroll all of them and disable developer mode (prevents unenrolling and prevents sideloading Linux).
Problem is if older Chromebooks are used for Linux in an educational environment there would be nothing stopping a student from whipping up a bootable USB and dumping another distro (bypassing restrictions). I'm also not sure if there is a enrollment mode equivalent Linux (there may be but not sure).
At least that's my two cents (not a school it admin just a memory from the past 😉).
I never really understood the need for that strickt controll of the hardware... Who cares if Linux is sideloaded or if students unenroll.
Imho I think if you need that strickt controll you are bound to get so many unnesseary issues down the line. Instead let student 6se what ever the fuck they want and for security just make sure they WiFi/ethernet is secure and locked down and any services the students need are behind a secure 2fa login. Treat any device as untrusted is more healthy for your security in the long run imo. If students need special software that they can't run on their own machines you can lend them a machine for that specific task for a specific time. Problem solved.
all 33 comments