Introduction: ChromeBook, as a machine positioned for business and student entry, seems outdated in the current year of 2023; it is even close to extinction after its exit from the Chinese market. However, some models with special needs still offer great value for money.
As a trash enthusiast, the author often explores many "foreign garbage" on second-hand platforms. And one day, a machine called ASUS ChromeBook C302 caught my attention. Let's take a look at its configuration:
Previously, the author always thought that ChromeBook only existed on Google's Pixelbook models, just like Microsoft's Surface Pro; in fact, mainstream OEM manufacturers - such as American conscience, socialist Dai, HP, Acer, Asus, Samsung, and so on - have all released Chromebooks.
But this ASUS machine truly impressed me: excellent texture with a silver-white all-metal shell, a 360-degree flip touchscreen, and a maximum battery life of 10 hours with a weight of only 1.15 kilograms. It's the perfect combination of a lightweight laptop and a tablet! The only downside is its limited ports, with only two type-C ports, one 3.5mm headphone jack, and an SD card slot, which seems a bit insufficient. In terms of performance, the combination of Intel m3-6y30 and 8+32G can only be considered passable.
However, as a combination of touchscreen and flipbook, this price is extremely practical for use as a reader, internet device, and video player. After the exit of Amazon's Kindle from the Chinese market, the e-reader market has become chaotic, with high prices and low-end models flooding the market. The general tablet ecosystem is repetitive and expensive. If there is no gaming requirement, ChromeBook is a good choice.
So, let's see how it performs in reality. The first thing that catches the eye is the classic Chrome OS interface. Here, it is important to note that logging in requires a Google account (Gmail email). If you don't have one temporarily, you can log in using guest mode, where all operations will not be saved on the hard drive (seemingly protecting privacy). After logging in to Google, you can see its complete ecosystem, including native Play Store, Chrome browser, Gmail, and more.
So, what can you do with ChromeBook?
1. Enter developer mode and install ARM software:
Assuming you already have a Google account and have deployed OpenWrt in previous blog posts, you can now connect your Chromebook to the internet using a global proxy. Then, log in to your account, and you have completed the first step. Next, remove the back cover and unscrew the BIOS write protection screw on the motherboard. Note that when removing the back cover, there are two screws hidden under the upper foot pad, which need to be removed first before disassembling these two screws. There are no screws under the lower foot pads. As shown in the figure:
Then, open the back cover and remove the large screw shown in the figure (under the skin):
After that, put the back cover back on, hold down the Esc and "Refresh" keys on the keyboard, and then press the power button. This will put the Chromebook into "recovery" mode:
Then, simultaneously press the Ctrl and D keys on the keyboard:
Press Enter, and the system will restart. You will hear a "beep!" BIOS prompt sound.
Then, wait for Chrome OS to reset.
After the reset is complete, you will see the following interface. From now on, you need to press Ctrl+D every time you start the system:
Then, in the settings-advanced section, you can see that developer mode is enabled. Now, you can install other apps in Chrome OS.
Attached are the reader and video effects:
2. Install other systems
If you don't like Chrome OS or need a Linux environment, you can try installing other systems such as FydeOS or Manjaro. Let's take the crouton script as an example (requires a global proxy):
Here is the GitHub address of the crouton project: https://github.com/dnschneid/crouton
Since we have already entered developer mode, open the Chrome OS browser, and simultaneously press Ctrl, Alt, and T to open a command line window. Enter the command "shell" and press Enter. Then, the real command line of Linux will appear. Next, install crouton. If you downloaded crouton using Chrome OS, the file should be in the ~/Downloads directory. Execute the command:
sudo sh ~/Downloads/crouton -r list
This will list all available distribution versions. For example, Ubuntu, Debian, Kali, and so on. Then, use the command to list all available components for installation:
sudo sh crouton -t list
This includes various desktop environments such as GNOME, KDE, Xfce, LXDE, and more. We choose the lightweight LXDE:
sh crouton -r stretch -t lxde
Then, set the username, password, and so on. After the installation is complete, enter the command in the Chrome OS Linux shell:
sudo startlxde
to start Linux.
In fact, the principle of crouton is based on a technology in Linux called chroot. In a Linux system, it can switch the root directory (i.e., /) of the Linux system to an isolated and independent environment, which is a virtual root file system. Crouton utilizes this feature to switch the root directory of Chrome OS to the specified file that has another system installed. Moreover, two features will appear: Linux can enjoy the driver support of Chrome OS without worrying about driver issues, and it uses the system kernel of Chrome OS.
Due to the overly simplified kernel, some services may not run properly. In this case, we can use the second method: flashing the BIOS to install the system.
We enter the Linux shell, insert an empty USB flash drive, and enter the following command:
cd
curl -LO mrchromebox.tech/firmware-util.sh
sudo install -Dt /usr/local/bin -m 755 firmware-util.sh
sudo firmware-util.sh
After successfully starting the script, you will see the following interface:
Choose the option marked "Full ROM" and follow the prompts to back up the BIOS and flash the BIOS. Then, reboot, and you can proceed with the normal system installation process (use Rufus to write the ISO for booting).
Note: You need to delete the hard drive partitions of the ChromeBook first; it only supports UEFI boot, and the Windows driver is not complete.
Epilogue: The suitability of a device is always relative. As long as it meets the requirements, there is no need to pursue the perfection of the tool excessively.