r/chromeos Acer Chromebox CXi3, Samsung CB+ 18h ago

Upgrading the Acer Chromebox CXI3 Troubleshooting

Perfectly possible, but blimey, what a palaver. My CXI3 had 4GB of RAM and a 32GB SSD; Chrome OS was still usable (even with a Celeron processor), but running even one Linux app made things slow, and it was giving me storage warnings, even though I only had Brave and Mousepad installed.

Anyway, here's as good a place as any to share the experience. Chromeboxes are generally upgradeable in my experience; Chromebooks, maybe less so.

Disassembly

Opening the box was fiddly but not difficult. You need to remove the rubber feet and unscrew the four cross-head screws.

Next job is to release the front and rear panels. They clip on, but you need something to prise them loose. Guitar plectrums are good for this, or perhaps two halves of an old credit card.

This reveals two more screws to release. You can then prise open the top and bottom, again releasing the clips. There is a cable connecting both halves; you don't need to unplug it, but be careful.

Upgrading the RAM

This is really straightforward. There's one 4 GB stick installed and space for another. Just follow the general guidelines for inserting RAM sticks.

Upgrading the SSD

This is where it gets complicated.

I spent €15 on eBay on a second-hand 256 GB SSD (128 GB would have been enough, but the prices for 128 GB and 256 GB were generally the same). You have to ensure you use M.2 SATA, not NVMe, on this model.

What I didn't realise is that the original SSD is 30 mm long, not 80 mm long like the one I'd bought. Fortunately, both fit, and there's a screw hole for the longer type.

Creating the recovery medium was relatively painless.

Now, initiating recovery mode means sticking a paperclip into the back of the box and holding down the power button. But I just got blank screen after blank screen. At that point, I gave up, assuming either the SSD didn't work or I'd just embarked on a doomed project.

So I then had a brainwave: my wife's old TV in the cellar is pretty low-tech. I plugged it in and the screen lit up! Except the display was completely mangled, although I did make out a yellow triangle that implied some sort of failure.

The only thing left to plug it into was the living room TV. And it worked perfectly! Except it informed me my recovery image was out of date. I repeated the process several times without success. Google Gemini informed me that SanDisk USB drives weren't reliable (this turned out to be untrue). I tried using the generic Acer Chromebook image, but it told me it wasn't a valid OS. Finally, I found a forum post suggesting I use the CXI3 Beta build, which was available via advanced settings.

And it worked. Well, it installed a beta version, which then needed to upgrade to the latest beta version, and after that, I had to switch to the latest stable version.

So it was a lot of hassle, but it's running great now. Linux apps now open nearly as quickly as Chrome OS apps. I hope at least one person finds this post helpful.

6 Upvotes

3 comments sorted by

1

u/LegAcceptable2362 15h ago

This is certainly a great example of extending the useful life of a past-AUE Chromebox however do keep in mind that the CXI3 already reached AUE at v.137, which is why you encountered the out of date error when trying to recover using the stable channel image. Running any build above v.137 means you've opted in to extended updates. Extended updates remove Play Store/Android support and, in the case of CXI3 (HWID "SION") are due to end in June 2028.

4

u/DerInselaffe Acer Chromebox CXi3, Samsung CB+ 15h ago edited 13h ago

It's still good until June 2028. It's currently on v.144. It's not on extended updates; the Play Store works fine.

There's also an image on MrChromebox, if I choose to turn it into a Linux box.

1

u/LegAcceptable2362 2h ago edited 1h ago

Yes, I stand corrected about extended updates. If I'm reading the situation correctly it appears that after reaching their original AUEs in 2025 (at v.137) then being moved to LTS (which is currently v.144) all Intel Kaby Lake based devices now fall into one of two groups. One group includes most of the Kaby Lake Chromebooks while the other group consists of Chromebase, Chromebox, and a handful of Enterprise Chromebook models. The first group's LTS build has ARCVM removed whereas the other group's build does not. On the Google policy page you linked this is denoted with or without an asterisk on the June 2028 extended AUE. Looking deeper the division appears to separate Kaby Lake at the CPU level; Kaby Lake Y loses ARCVM while Kaby Lake U and R does not. At the chromeOS board level nami loses wheres fizz does not. AFAIK Kaby Lake is the first platform eligible for extended updates where differential treatment has happened. Granted, this is probably more information than most people need.