Note: Hi from the past, everyone! This post is likely very out of date. There are new tools to replace Project Croissant, and new driver packs available for Surface products including the Go. This hasn’t been updated since February of 2019.
I’m a tablet hopper. I love the idea of a tablet, but they always seem to fall short in one way or another. I’ve had a ton of Surface devices, iPads, and even a few Galaxy Tabs. My favorite device of all time is probably the first generation ThinkPad 10, but it’s just slow enough at this point that it’s not as fun as it once was. My current primary is a 10.5″ iPad Pro.
I do love the Surface lineup, but Windows 10 is a surprising shortcoming. Don’t get me wrong, I really like Windows 10, but from a tablet perspective, it’s a huge step back from Windows 8. Do note, however, that’s the only nice thing I’ll say about Windows 8.
What I’ve really been waiting for is a really good 10-11″ ChromeOS tablet. ChromeOS has a great core, Android support, Linux support for the apps you need, all wrapped up in easy updates and elegant consistency. Usually. The only devices in this form factor are the Acer Chromebook Tab 10, and the clone tablets that are based on that form factor. The ARM chip is somewhat anemic, but I’m mostly okay with that. My concern is the lack of supporting hardware — namely, decent cases, and nicely integrated keyboard designs. Once something comes out that fits that niche, I’m first in line.
Until then? Haxxxxx.
Enter Project Croissant. Croissant, formerly Chromefy, is a tool to convert a ChromiumOS image to a full ChromeOS image. ChromiumOS is the open source version of ChromeOS, consisting of most of what makes ChromeOS good, but missing closed source bits, including Android support. By utilizing a ChromeOS recovery image, Croissant can generate a ChromeOS image that can be installed on most anything with some reasonable driver support. Armed with this, I’m hoping to make a Surface Go, arguably one of the best form factors out there right now, a much more useful tablet for me.
What definitely doesn’t work:
- Front and Rear Cameras
- Power button to wake, but other touch events or keys seem fine
- Touch response is odd, a press event occurs even on light touches or drags
- The type cover function key icons do not correspond to their ChromeOS functionality
- Sleep still burns some battery
What really works:
- Wi-fi and bluetooth seem to work splendidly
- The stylus responds well, and the pen icon appears
- The type cover attaches and disconnects as one expects, backlight works, everything is fine
- The SD card mounts just fine
- USB-C devices work exactly as they should
- Audio output
- Lid sensor with Type Cover
To create this image, I used another machine running Linux. This can be done in a virtual machine, or using a Linux live image.
- To begin, we need to gather dependencies
- We’ll also need to grab updated firmware for wi-fi and bluetooth support within Chromium/Chrome
- With all of our dependencies gathered, we can actually create our installation image
- Uncompress each image into a directory
- Copy chromefy.sh into the same directory
- Execute chromefy to create the image, using something similar to sudo bash chromefy.sh chromiumos_image.img chromeos_11151.113.0_nocturne_recovery_stable-channel_mp.bin chromeos_11151.113.0_caroline_recovery_stable-channel_mp.bin
- Write the updated chromiumos_image.bin to a USB stick using Etcher or similar
- Upon completion, remove and reinsert the USB stick
- Insert updated firmware and configuration to our ChromeOS image
- Find the partition containing the rootfs, which may have automounted under /media/your-username/, and contains directories like ‘bin’, and ‘lib’
- Remove [path-to-rootfs]/lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
- Replace [path-to-rootfs]/lib/firmware/ath10k/QCA6174/hw3.0/board.bin with the previously downloaded file
- Replace [path-to-rootfs]/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin with the previously downloaded file
- Create [path-to-rootfs]/etc/modprobe.d/ath10k.conf and add
options ath10k_core skip_otp=yto the file
- Unmount the mounted USB filesystems
- Get your Surface Go and running
- Within Windows, go to Settings > Update and Recovery > Recovery
- Under Advanced Startup, select Restart Now
- Navigate to Troubleshoot > Advanced, and select UEFI Firmware Settings
- Under Boot Configuration, disable Secure Boot and set USB Storage to the top of the boot order
- Select Reboot to boot from USB stick
This is a bit of the test front for the image. One is able to log in and poke around a bit within the USB live image. The installation process got a little hairy, though, at least for ArnoldTheBat 72 + Eve 71. Note that the first command run will blow away the copy of Windows installed on the Surface Go. There are instructions available on the Project Croissant GitHub README for doing multiboot. As I have the 64gb Go, multiboot makes no sense for me. Also note that the 128gb Go uses SSD instead of eMMC, so the device name is going to change, likely to some derivative of /dev/nvme0n1.
- Execute /usr/sbin/chromeos-install –dst /dev/mmcblk0 –skip_postinstall
- Reboot into a live image of Linux
- Using Gparted, or similar, resize /dev/mmcblk0p3 (H-STATE) down one gigabyte
- Remove /dev/mmcblk0p12, the EFI_SYSTEM partition
- Create a new partition, 1gb, fat32, with a partition name of EFI_SYSTEM
- Right click the EFI_SYSTEM partition and then “Manage Flags”
- Select legacy_boot, boot, esp
- Open a terminal
- sudo mkdir /mnt/cros /mnt/efi
- Insert the USB stick containing your ChromeOS image
- Find the device of the USB stick, likely /dev/sdb, and replace sdx with the device found, and execute mount /dev/sdb12 /mnt/cros to mount the Chrome image’s EFI partition
- Execute mount /dev/mmcblk0p12 /mnt/efi to mount the installed EFI partition
- Execute cp -Rp /mnt/cros/* /mnt/efi/ to copy the EFI partition over
- Reboot and remove the USB stick
Welcome to your new ChromeOS installation!