Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/S-PScripts/chromebook-utilities/llms.txt

Use this file to discover all available pages before exploring further.

Many unenrollment and exploit methods only work on specific, older versions of ChromeOS. Downgrading allows you to roll back to a version that still has an unpatched vulnerability — for example, CryptoSmite requires v119 or lower, and Sh1mmer works best below v111. However, downgrading is not always possible: Google introduced kernel version locking (kernver) to restrict how far back a device can recover. Understanding your board and kernver before attempting any exploit is essential.
Downgrading performs a full recovery, wiping all local data. Additionally, not all devices can downgrade — if your kernver is too high, the recovery process will refuse to flash an older image. Getting stuck on an old version can also be a problem; you will need to prevent auto-updates after downgrading to stay on your target version.

Understanding ChromeOS Boards and Kernel Versions

Every Chromebook runs on a specific board (hardware platform). Many exploits target specific boards or version ranges, and recovery images are distributed per-board. Your board name is required to download the correct recovery image.

Most Common ChromeOS Boards

The most widely encountered boards in the community (by device count) include: dedede (81), octopus (78), nissa (45), coral (40), brya (36), volteer (18), grunt (14), zork (14), enguarde (13), jacuzzi (13), corsola (12), fizz (10), hatch (10), hana (9), nami (9), trogdor (9), brask (8), rex (6), skyrim (5), guybrush (4), kukui (4), strongbad (4), cherry (3), asurada (3), and many more.

Kernel Versions (Kernver)

Kernver is ChromeOS’s kernel version — a value stored in the TPM that locks the device to a minimum recoverable ChromeOS version. If your kernver is higher than what an exploit requires, you cannot use that exploit.
KernverChromeOS Versions
0Any
1< v112
2v112–v119
3v120–v123
4v124–v132
5v133–v137
6v138+
7< v145
If you are on Kernver 1, you can recover to any version. However, exploits labelled as Kernver 1 can only be performed below v112. Higher kernvers restrict how far back you can downgrade.
Determining your kernver:
1

Enter Recovery Mode

Hold Esc + Power + Refresh for just under a second until the recovery screen appears.
2

Press Tab

Press Tab to see system information.
3

Read the kernver

Find the line starting with TPM: — the number at the end is your kernver.
Credits: Titanium Network — docs.titaniumnetwork.org/kajigs/versions

Finding Your Board Name and Model

You need your board name to download the correct recovery image. There are several methods:
  1. Go to chrome://version/
  2. In the Platform section, look at the end — this is your board name (e.g., octopus or dedede).
  3. The Customization ID section shows your board model (e.g., phaser360 or boten).
  1. Go to chrome://system/ and wait for it to finish loading.
Board name — check any of these fields:
  • CHROMEOS_RELEASE_BOARD (board name at start)
  • CHROMEOS_RELEASE_BUILDER_PATH (board name at start)
  • CHROMEOS_RELEASE_DESCRIPTION (board name at end)
  • platform_identity_name
Board model — check any of these fields:
  • HWID (board model at start)
  • hardware_class (board model at start)
  • platform_identity_model
If chrome://system is blocked, press Ctrl + Search + I, enter anything in the description, click Continue, then click the blue “System and app info” text.
  1. Go to Google Play.
  2. Click your account in the top right → arrow next to your email → Manage accounts on this device.
  3. Click the search icon, search device, and scroll down.
  4. Look for “Device configuration for” followed by your board name.
Found by SlitheringLizard1.
  1. Open SettingsAppsAndroid Settings.
  2. Scroll to the bottom of the Android settings page.
  3. Find “About device (your board name)”.
  1. Go to chrome://connectors-internals.
  2. Find the "deviceModel" field — this is your board model.
  3. Enter the board model at cros.tech to look up your board name.
Found by HyperNut.

Finding Your ChromeOS Version

You may need to confirm your current version before deciding which downgrade target or exploit to use.
Method 1: Go to chrome://version — look for the version number (e.g., v1xx).Method 2: Open Settings → scroll to About ChromeOS — the version is listed there.Method 3: On the lock screen, press Alt + V — the version appears in the top right as “Google Chrome X”.Method 4: Go to chrome://system/ and check the CHROME VERSION, os-release VERSION, or os-release VERSION_ID fields. If chrome://system is blocked, press Ctrl + Search + I and use the System and app info link.Method 5: Go to chrome://nacl/ — the first line shows your Chrome version.

Downgrade Methods

Standard Downgrade via Recovery Image (Anastrophe)

This is the primary method for downgrading ChromeOS using a USB recovery image flashed to the target version. It uses a built-in ChromeOS recovery feature.
Review the Kernel Versions table above before proceeding. Downgrading to a version below your kernver’s minimum range will fail.
Requirements:
  • USB thumb drive with at least 4 GB of storage (16 GB recommended)
  • A personal computer with the Chromebook Recovery Utility extension
1

Find your board name and target version

Go to chrome://version on your Chromebook and note your board name from the Platform field. Decide which older version you need for your exploit.
2

Download the recovery image

On your personal computer, go to cros.download and click Recovery Images. Press Ctrl + F and search for your board name. Download the ChromeOS version you want.
3

Flash to USB

Install the Chromebook Recovery Utility extension. Open it, click the gear icon, select “Use local image”, choose your downloaded image, plug in your USB, and follow the prompts.
4

Enter recovery mode on the Chromebook

Press Esc + Refresh + Power on your Chromebook.
5

Insert recovery USB and skip updates

Insert the recovery USB and follow the on-screen prompts. On the “checking for updates” screen, press Ctrl + Shift + E to skip the update check.
6

Complete recovery

Follow the prompts to reinstall ChromeOS. Remove the USB when done. You can erase it in the Recovery Utility (gear icon → “Erase recovery media”).
Credits: 3kh0/ext-remover, Titanium Network

Downgrade via Kernver 3 (Shimboot)

For devices on kernver 3, a different approach using Shimboot is used as the bootloader.
1

Deprovision in Sh1mmer

Boot Sh1mmer and deprovision the device first.
2

Downgrade to v100

Perform a standard downgrade to a lower version (e.g., v100). Developer mode must be enabled, or the recovery will complain the image is too old.
3

Boot Shimboot

Flash Shimboot to a USB drive or SD card, plug it in, and boot using Root X (Root A or Root B).
Shimboot functions as an alternative bootloader for ChromeOS itself, allowing boot from recovery-mode-incompatible older versions.

Internet Unrecovery (2023+ NewUI Chromebooks)

This method uses the Internet Recovery tool on newer Chromebooks to downgrade without a USB drive. It has been confirmed working on corsola-steelix (Lenovo 300e Yoga Gen 4 MTK) and similar devices. Requirements:
  • A NewUI Chromebook (corsola, nissa, or any 2023+ release date device — release date, not manufacture date)
  • Developer Mode disabled
dedede Chromebooks may also have Internet Recovery available.
1

Enter Recovery Mode with Developer Mode off

Make sure developer mode is disabled. Press Esc + Refresh + Power to enter recovery mode.
2

Open Advanced Options

Use the down arrow key to navigate to Advanced Options and press Enter.
3

Select Internet Recovery (old)

Choose “Internet Recovery (old)” — the current Internet Recovery may not work.
4

Connect to Wi-Fi and start recovery

Connect to Wi-Fi and begin the recovery process as normal. You will see a progress bar.
5

EC reset immediately

The moment the progress bar appears and the screen says “Recovering… do not power off the device”, perform an EC reset (Refresh + Power) as quickly as possible. Do not let recovery progress.
6

Let the repair complete

The device will say “Your system is repairing itself.” Allow it to complete and reboot automatically. You should now be on the ChromeOS version from before you last updated.
Credits: kilo | kxcv

Preventing Re-Upgrade After Downgrading

After downgrading, ChromeOS will attempt to auto-update back to the latest stable version. To stay on your downgraded version, you need to block automatic updates.
Staying on an old version long-term can raise flags in the Admin console (version reporting is visible to administrators). Some exploits like Fakemurk recommend periodic re-recovery to a newer version to avoid suspicion.
Use CAUB (ChromeOS Auto-Update Blocker) to prevent ChromeOS from upgrading after downgrading. See the CAUB guide for instructions.

Recovery Image Resources

ResourceURLDescription
cros.downloadcros.downloadPrimary recovery image directory by Mercury Workshop
cros.techcros.techChannel versions and recovery image browser
ChromiumDashchromiumdash.appspot.comOfficial Google serving builds reference

Build docs developers (and LLMs) love