A Pixel 8
Bought unlocked rather than from a mobile network, since network branded phones often block the unlocking this requires. Check your phone before you start.
Test builds, for evaluation only
Putting OBSIDIAN on a phone replaces the operating system it came with. Everything on the phone is erased in the process. It runs on the Google Pixel 8 only, for now. Read this page before starting.
OBSIDIAN does not come on a phone. You buy a Pixel 8 and install it from your own computer. The easiest way is the browser installer: open it in Chrome, Edge or Brave, plug the phone in, and press each button in turn. The steps further down do the same thing from a command line. Either way it takes around half an hour, most of which is the phone working on its own.
Bought unlocked rather than from a mobile network, since network branded phones often block the unlocking this requires. Check your phone before you start.
Windows, macOS or Linux, running on the computer itself rather than in a virtual machine, and the USB-C cable that came with the phone. Plug straight into the computer, not into a hub or a monitor.
Room to download the 2 GB phone image and unpack it, and half an hour when you will not need the phone.
Installing erases the phone completely. Photos, messages and accounts on it are gone for good, and cannot be recovered afterwards.
The small tools that talk to the phone, fastboot and adb, come from Google as Android SDK Platform-Tools at developer.android.com/tools/releases/platform-tools. Unpack them somewhere easy to find.
Windows 10 and 11 already include a driver that works with the Pixel 8 in bootloader mode. Older versions of Windows need Google's USB driver. If flashing stops when the phone shows its fastbootd screen, Windows has not attached a driver for that mode: in Device Manager, update the Pixel 8's driver to WinUsb Device, as the browser installer page describes.
Linux needs permission to reach the phone over USB. On Debian and Ubuntu, install the package android-sdk-platform-tools-common, then unplug the phone and plug it back in.
Nothing extra is needed.
On the phone, open Settings, go to About phone, and tap Build number seven times. Go back to Settings, then System, then Developer options, and turn on OEM unlocking. The phone needs to be on Wi-Fi for this.
Turn the phone off. Hold Volume Down and press Power until a screen with a start arrow appears. Connect it to the computer.
This is what allows a different operating system to be installed, and it erases the phone. Run this from the folder with the platform tools, then use the volume buttons on the phone to choose Unlock the bootloader and press Power to confirm.
fastboot flashing unlock
Unpack the release and run the flashing script for your computer. The phone restarts several times on its own. Do not unplug it.
The first start takes a few minutes while the phone prepares its apps. Then set a screen PIN, open the chat app, and choose a username. Your keys are made on the phone at that moment.
While these are test builds, the bootloader stays unlocked and the phone shows a warning when it starts. That is expected, and it is one of the things that changes with the first proper release.
You can return the phone to Google's own software at any time. Doing so erases the phone again.
Go to flash.android.com in Chrome or Edge. It is Google's own tool for putting their software back on a Pixel.
Start the phone in bootloader mode as in step 2 above, and connect it.
Pick the latest factory image, let it wipe the phone, and choose to lock the bootloader at the end.
Test builds do not install a key of their own, so nothing more is needed today. Once release builds lock the phone with the OBSIDIAN key, you will first need to remove that key, with the bootloader unlocked, by running fastboot erase avb_custom_key.
It does everything above from a web page in Chrome, Edge or another browser built on Chromium, with the phone plugged in. It needs more free space than the command line, because the browser keeps its own copy of the unpacked image while it works. Two parts are still to come.
Open a page, plug the phone in, press a button. No developer tools to install, nothing to type.
The release is checked against its published SHA-256 as it downloads, and it is not used unless it matches.
Once release keys exist, the installer locks the bootloader at the end, so nothing else can be flashed onto the phone afterwards. The startup warning stays, but changes to a short notice showing the fingerprint of the OBSIDIAN key.
A way to confirm the phone is running genuine, unmodified OBSIDIAN rather than something that looks like it.
There is no public release yet. Phone builds are running on a Pixel 8 in testing, and the source is public for anyone who wants to build it themselves. Each release will come with the phone image, a checksum to confirm your download arrived intact, flashing scripts for Windows, macOS and Linux, and once release keys exist, the fingerprint to compare with the one the phone shows when it starts.
github.com/ObsidianOSx/ObsidianOS