diff --git a/src/consts.ts b/src/consts.ts index bb385751..e976f324 100644 --- a/src/consts.ts +++ b/src/consts.ts @@ -95,14 +95,26 @@ export const SIDEBAR: Sidebar = { { text: "Errata", link: "en/release/errata" }, { text: "Differences with Fedora", link: "en/release/diff-fedora" }, ], - // Chromebook: [ - // { text: "Getting Started", link: "en/chromebook/chromebook" }, - // { text: "Getting Chromebook Edition", link: "en/chromebook/getting" }, - // { text: "Installing to a Chromebook", link: "en/chromebook/preparing" }, - // { text: "Post-Install", link: "en/chromebook/postinstall" }, - // { text: "ARM Chromebooks (Beta)", link: "en/chromebook/armbeta" }, - // { text: "Terminology", link: "en/chromebook/terminology" }, - // ], + Chromebook: [ + { text: "Getting Started", link: "en/chromebook/chromebook" }, + { text: "Getting Chromebook Edition", link: "en/chromebook/getting" }, + { text: "Installing", link: "en/chromebook/installing" }, + { + text: "Troubleshooting and FAQ", + link: "en/chromebook/faq-and-troubleshooting", + }, + { text: "ARM Chromebooks (Beta)", link: "en/chromebook/arm" }, + { text: "Terminology", link: "en/chromebook/terminology" }, + ], + + Development: [ + { + text: "Developing for Ultramarine", + link: "en/development/developing-for-ultramarine", + }, + { text: "Using Andaman", link: "en/development/anda" }, + { text: "UX Guidelines", link: "en/development/ux-guide" }, + ], }, de: { Introduction: [{ text: "Welcome", link: "de/welcome" }], diff --git a/src/content/docs/en/anywhere/chromebook.mdx b/src/content/docs/en/anywhere/chromebook.mdx index 4af4fada..eada8c65 100644 --- a/src/content/docs/en/anywhere/chromebook.mdx +++ b/src/content/docs/en/anywhere/chromebook.mdx @@ -152,7 +152,7 @@ cgpt add -i -t kernel -P 15 -T 1 -S 1 /dev/sdX 11. Done! - Once Ultramarine has been successfully installed onto your Chromebook's internal disk, rebooting will take you back to the ChromeOS recovery screen. To boot to Ultramarine, select 'Boot to Internal Disk' or press Ctrl+D +Once Ultramarine has been sucessfully installed onto your Chromebook's internal disk, rebooting will take you back to the ChromeOS recovery screen. To boot to Ultramarine, select 'Boot to Internal Disk' or press Ctrl+D ## ARM diff --git a/src/content/docs/en/chromebook/arm.mdx b/src/content/docs/en/chromebook/arm.mdx new file mode 100644 index 00000000..c57c05c2 --- /dev/null +++ b/src/content/docs/en/chromebook/arm.mdx @@ -0,0 +1,37 @@ +--- +title: ARM Chromebooks +description: "Preview images for certain ARM chromebooks" +--- + +import Alert from "../../../../components/Docs/Alert.astro"; + +NOTE - Not all ARM devices are currently supported. The images we provide are previews and may have issues, proceed at your own risk. + +# Supported Devices + +Currently supported ARM Chromebooks (a * means Fyra Labs has tested these images on a device in this family): + +Supported MediaTek series: +- [mt8195](https://wiki.postmarketos.org/wiki/MediaTek_Kompanio_1200_(MT8195)) +- *[mt8192 (Asurada)](https://wiki.postmarketos.org/wiki/Google_Asurada_Chromebook_(google-asurada)) +- [mt8186 (Corsola)](https://wiki.postmarketos.org/wiki/Google_Corsola_Chromebook_(google-corsola)) +- *[mt8183 (Kukui)](https://wiki.postmarketos.org/wiki/Google_Kukui_Chromebook_(google-kukui)) +- [mt8173C](https://wiki.postmarketos.org/wiki/MediaTek_Kompanio_500_(MT8173)) + +Supported Snapdragon series: + +- [sc7180 (Trogdor)](https://wiki.postmarketos.org/wiki/Google_Trogdor_Chromebook_(google-trogdor)) + +# Usage + +[TODO] + +# Known Issues + +- mt8183 devices may emit a loud beep for 15 seconds if not properly sleeping/shut down +- mt8192 devices may have issues with sleep +- Cellular equipped sc7180 devices cellular may not work + +#### [Next Up: Terminology →](terminology) + +#### [← Back To: Troubleshooting and FAQ](faq-and-troubleshooting) diff --git a/src/content/docs/en/chromebook/armbeta.mdx b/src/content/docs/en/chromebook/armbeta.mdx deleted file mode 100644 index 174ef8f3..00000000 --- a/src/content/docs/en/chromebook/armbeta.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: ARM Chromebook Beta Program -description: "Closed program for running our beta images for certain ARM chromebooks" ---- - -import Alert from "../../../../components/Docs/Alert.astro"; - -NOTE - Not all ARM devices are currently supported. This is a Beta program, proceed at your own risk. - -Welcome to the ARM Chromebook Beta Program! We are looking for technically-versed people to test our Ultramarine Chromebook beta images for ARM. - -This is a closed program, please join and ping @Owen in the [Discord](https://discord.com/invite/5fdPuxTg5Q) or [Matrix](https://matrix.to/#/#hub:fyralabs.com) (most prefered), or email him at owen@fyralabs.com, to apply. - -Currently supported ARM Chromebook beta devices (if you have an unsupported device and are willing to use it for image testing, let us know!): - -All Kukui (mt8183) family Chromebooks: - -| Model name/number | Codename | -| ------------------------------------------ | -------- | -| Acer Chromebook 311 (C722/C722T) | willow | -| Acer Chromebook 311 (CB311-11H/CB311-11HT) | kenzo | -| Acer Chromebook 314 (CB314-2H/CB314-2HT) | cozmo | -| Acer Chromebook Spin 311 (CP311-3H) | juniper | -| Acer Chromebook Spin 311 (R722T) | pico | -| Asus Chromebook CZ1 | cerise | -| Asus Chromebook Detachable CM3 (CM3000) | kakadu | -| Asus Chromebook Detachable CZ1 | katsu | -| Asus Chromebook Flip CM3 (CM3200, MT8183) | damu | -| Asus Chromebook Flip CZ1 | stern | -| HP Chromebook 11a | kappa | -| HP Chromebook 11MK G9 EE | esche | -| HP Chromebook x360 11MK G3 EE | burnet | -| Lenovo 100e Chromebook 2nd Gen MTK 2 | makomo | -| Lenovo 10e Chromebook Tablet | kodama | -| Lenovo IdeaPad 3 Chromebook (MT8183) | fennel14 | -| Lenovo IdeaPad Duet Chromebook | krane | -| Lenovo IdeaPad Flex 3 Chromebook (MT8183) | fennel | - -Source: https://wiki.postmarketos.org/wiki/Google_Kukui_Chromebook_(google-kukui) - -All Asurada (mt8192) family Chromebooks: - -| Model name/number | Codename | -| ------------------------------------------ | -------- | -| Acer Chromebook 514 (CB514-2H / CB514-2HT) | spherion | -| ASUS Chromebook Flip CM3 (CM3200, MT8192) | hayato | - -Source: https://wiki.postmarketos.org/wiki/Google_Asurada_Chromebook_(google-asurada) - -All Trogdor (sc7180) family Chromebooks: - -| Model name/number | Codename | -| --------------------------------------------- | ------------- | -| Acer Chromebook 511 | limozeen | -| Acer Chromebook Spin 513 | lazor | -| Dynabook Chromebook C1 | pompom | -| HP Fortis 11 G9 Q Chromebook | kingoftown | -| Libera-Merdeka Chromebook C100/C110/C120/C150 | pazquel | -| Orbic Chromebook 4G | pazquel | -| Acer Chromebook Tab 510 | quackingstick | -| HP Chromebook X2 | coachz | -| Lenovo IdeaPad Duet 3 | wormdingler | -| Lenovo IdeaPad Duet 5 | homestar | - -Source: https://wiki.postmarketos.org/wiki/Google_Trogdor_Chromebook_(google-trogdor) - -Follow-up instructions, guide, and dedicated discord channel will be provided after acceptance. diff --git a/src/content/docs/en/chromebook/chromebook.mdx b/src/content/docs/en/chromebook/chromebook.mdx index a9c544e9..fe4f1e65 100644 --- a/src/content/docs/en/chromebook/chromebook.mdx +++ b/src/content/docs/en/chromebook/chromebook.mdx @@ -7,10 +7,10 @@ import Alert from "../../../../components/Docs/Alert.astro"; ### Welcome to Ultramarine Chromebook Edition! -With the help from out friends over at the [Chrultrabook Project](https://docs.chrultrabook.com/), we built a no-hassle way to boot full Ultramarine Linux onto your Chromebook! +With the help from out friends over at the [Chrultrabook Project](https://docs.chrultrabook.com/), we built a no-hassle way to install Ultramarine onto your Chromebook! -These pages will get you everything you need to know about what Ultramarine Chromebook is, how it works, how you can install it, and even how you can help us out. +These pages will provide everything you need to know about installing and using Ultramarine on Chromebooks. -If you would like more info about Ultramarine Chromebook and it's release, take a peak at the [Release post](link) +If you would like more info about Ultramarine Chromebook and it's release, take a peak at the [Release post](https://blog.fyralabs.com/ultramarine-chromebook-edition-is-here) #### [Next Up: Getting Chromebook Edition →](getting) diff --git a/src/content/docs/en/chromebook/faq-and-troubleshooting.mdx b/src/content/docs/en/chromebook/faq-and-troubleshooting.mdx new file mode 100644 index 00000000..b7665387 --- /dev/null +++ b/src/content/docs/en/chromebook/faq-and-troubleshooting.mdx @@ -0,0 +1,97 @@ +--- +title: Troubleshooting and FAQs +description: "Troubleshooting tips and tricks, and FAQs" +--- + +import Alert from "../../../../components/Docs/Alert.astro"; + +## Troubleshooting + + + If your issue still persists after reading this page, hop into [our + chats](/en/community/community) and make a support forum post. + + +### Chromebook Fails To Boot to Internal Disk + +Assuming 'Boot to Internal Disk', or pressing Ctrl+D does not fully boot (usually only to Submarine, the boot entries screen before Ultramarine boots), the device has probably died. Plug in your Chromebook. + +### Keyboard Is Not Properly Mapped + +Try re-installing the cros-keyboard-map package. Simply run ` sudo dnf install cros-keyboard-remap`. If this does not work, try running this command: + +``` +sudo systemctl enable cros-keyboard-map +``` + +If this does not work, try running WeirdTreeThing's [keyd script](https://github.com/WeirdTreeThing/cros-keyboard-map). + +### Chromebook Audio Doesn’t Work + +This should not happen unless you have unsupported speakers, but if it does, try running WeirdTreeThing's [audio script](https://github.com/WeirdTreeThing/chromebook-linux-audio) manually. + +You may have an audio device unsupported by the audio script by default (max98357a Sound controller). If you would like to enable audio on here, run the script manually and follow the prompts to enable audio. + + + max98357a, and any other audio devices requiring ```--force-avs-install``` is + not recommended to enable, and support will not be given to damaged speakers. + If you really want to proceed, do not raise your speakers volume high or they + will get damaged. + + +### USBC/Thunderbolt Doesn’t Work + +Try restarting the systemd service: + +``` +sudo systemctl restart chromebook-usbc-fix +``` + +## FAQs + +### Why Doesn’t [Insert Hardware Feature] Work? + +All hardware should work on almost every supported Chromebook model, but some specific Chromebooks may have some missing features (ex. Drallion, Sarien, and Arcada have a Wilco (Dell Enterprise) EC, and may have missing features). + +### Is This Legal? + +Yes, it is perfectly legal. Chromebooks and ChromeOS are backed by the [Chromium Projects' ChromiumOS](https://www.chromium.org/chromium-os/}). All information on how to mod Chromebooks is on this site, and open to anyone to use. + +### Will the Installer Boot Through a USB 2.0/3.0 Adaptor/Hub? + +Yes. + +### Why Not Just Run [MrChromebox's Firmware Utility Script?](https://mrchromebox.tech/#fwscript) + +The goal here is to be as easy and safe to use as possible. It is also easier to go back to ChromeOS if you keep the stock firmware. With that being said, we fully support the use of mrchromebox's script, it has many great use cases. + +### Will This Make My Chromebook Faster? + +Ultramarine can be more lightweight then ChromeOS, but we do not guarantee a preformance gain vs ChromeOS. +If you are using an older/slower Chromebook and want to maximize performance, we reccomend using Xfce Edition. + +### Should I Buy a Chromebook Instead of a Regular Laptop Now? + +Generally, it is recommended not to, however you can get really good Chromebook deals if you know where to look. Keep in mind they will by nature be less stable, and more involved then a regular laptop. A good rule of thumb is to always have a regular laptop handy incase you need it. + +### This Installer Looks Different, What Is It? + +We are using our in-house installer [Readymade](https://github.com/FyraLabs/readymade). + +### What Is This Chrultrabook Tools App? + +An application to interact with your Chromebook's hardware, provided through Terra. +More info can be found [here](https://github.com/death7654/Chrultrabook-Tools). + +#### Known Issues + +Found an issue? [Let us know](/en/community/community) + +| Model name/number | Codename | Issue | Cause | Fix? | +| ----------------- | -------- | ----- | ----- | ---- | +| Dell Latitude 7410 Enterprise Chromebook | Drallion | No working keyboard backlight or touchscreen | Dell Wilco EC firmware | x | +| Dell Latitude 5300 2-in-1 Chromebook Enterprise | Arcada | No working keyboard backlight or touchscreen | Dell Wilco EC Firmware | x | + +#### [Next Up: ARM Chromebooks (Beta) →](armbeta) + +#### [← Back To: Installing](installing) diff --git a/src/content/docs/en/chromebook/getting.mdx b/src/content/docs/en/chromebook/getting.mdx index 3795d123..b8110aac 100644 --- a/src/content/docs/en/chromebook/getting.mdx +++ b/src/content/docs/en/chromebook/getting.mdx @@ -18,7 +18,7 @@ Ultramarine Chromebook comes in 4 variants: - **Budgie Edition**: A familiar and stylish experience with a bit of flair. - **GNOME Edition**: A simple, elegant, and intuitive desktop with a large ecosystem of apps and extensions. -Ultramarine Linux is distributed with image files available for download from [our website](https://ultramarine-linux.org/download/chromebook). +Ultramarine for Chromebooks is distributed with image files available for download from [our website](https://ultramarine-linux.org/download/chromebook). Fyra Labs cannot guarantee the safety or quality of images downloaded from @@ -62,20 +62,29 @@ CertUtil -hashfile PATH\TO\ULTRAMARINE.ISO SHA256 # Open the CHECKSUM file with Notepad and compare the checksum ``` -## Creating the Installer +## Creating the Installer on Windows, macOS, or Linux ### Download [balenaEtcher](https://www.balena.io/etcher/) to create a bootable media from the img image. ![](/assets/balenaetcher.png) -Simply select the img file, a device to use for the installer, and click flash. +After downloading Ultramarine Chromebook, select the img file, a device to use for the installer, and click flash. -#### [Next Up: Installing to a Chromebook →](preparing) +## Creating the installer on ChromeOS -#### [← Back To: Getting Started](chromebook) +### Download the [Chromebook Recovery Utility extension](https://chromewebstore.google.com/detail/chromebook-recovery-utili/pocpnlppkickgojjlmhdmidojbmbodfm) from the Chrome Web Store + +![](/assets/Chromebook-Recovery-Utility.png) -## Footnotes +1. Download the Ultramarine Chromebook image +2. Navigate to the image, and change the '.img' to '.bin' +3. Open the Chromebook Recovery Utility extension +4. Click the 'settings' icon in the top right corner, and select 'Use Local Image' +5. Navigate to and select your Ultramarine Chromebook .bin image, and select 'OPEN' +6. Insert and select the instalation media you would like to use under the dropdown +7. Select 'Continue' +8. Disregard the warning, then press 'Create now' -- The Anaconda installer is very complex and hard to work with, we are working on a new installer that is easier to use and more reliable. -- Since Fedora 37, Fedora's official support for the Pantheon desktop environment has been dropped due to compatibility issues and the Pantheon port is now maintained by the Ultramarine Linux team. This means that the Pantheon desktop environment is only available through Ultramarine Linux, or Fedora with Terra enabled. -- Ultramarine's Budgie edition provides a close to stock Budgie experience, with a custom theme. Unlike Fedora's Budgie Spin, which provides a completely custom layout and experience. +#### [Next Up: Installing →](installing) + +#### [← Back To: Getting Started](chromebook) diff --git a/src/content/docs/en/chromebook/preparing.mdx b/src/content/docs/en/chromebook/installing.mdx similarity index 61% rename from src/content/docs/en/chromebook/preparing.mdx rename to src/content/docs/en/chromebook/installing.mdx index 56f27d94..1e1bc8bd 100644 --- a/src/content/docs/en/chromebook/preparing.mdx +++ b/src/content/docs/en/chromebook/installing.mdx @@ -7,26 +7,26 @@ import Alert from "../../../../components/Docs/Alert.astro"; Before we insert the installer, we will need to do a few things with your ChromeOS device. -### 1. Back up your data (optional) +### 1. Back Up Your Data (Optional) -Step 2 will wipe all local data from your device, If you have any files you wish to save or move to Ultramarine Chromebook, back up your data off the device, either to the cloud or locally. For a small number of files, we recommend backing up to Google Drive, or another cloud storage provider. For a larger number of files, we recommend backing up to an external storage medium, such as a USB flash drive or other external drive. +Step 2 will wipe all local data from your device, If you have any files you wish to save or move to Ultramarine Chromebook, back up your data off the device, either to the cloud or locally. For a small number of files, we recommend backing up to Google Drive, or another cloud storage provider. For a larger number of files, we recommend backing up to an external storage medium, such as a USB flash drive (seperate from the one you will turn into the instaler) or other external drive. -If you choose to back up with Google Drive, you will be prompted to add your Google Drive to the Ultramarine Chromebook file explorer during setup to easily access and redownload your data. +If you choose to back up with Google Drive, you will be prompted to add your Google Drive to the Ultramarine Chromebook file manager in the GNOME, KDE, and Flagship editions during setup to easily access and redownload your data. -### 2. Enable developer mode +### 2. Enable Developer Mode Enabling developer mode will wipe your data -#### Developer mode on Chromebooks (ChromeOS laptops only): +#### Developer Mode on Chromebooks (ChromeOS Laptops Only): -1. Shut down the device, then hold Esc + ⟳ + ⏻ [power] to enter Recovery mode. +1. Shut down the device, then hold esc + ⟳ + ⏻ [power] to enter Recovery mode. 2. When you see a screen that says 'ChromeOS is missing or damaged,' press Ctrl+D. 3. You may be prompted with 'To turn OS verification off, press enter,' press Enter. 4. A screen saying 'OS verification is off, press space to re-enable' should appear, press Ctrl+D. Your system is now transitioning into Developer Mode! (This may take a few minutes) -5. After it has transitioned, press Control+D to boot back into ChromeOS as a developer. You are now ready for step 3 +5. After it has transitioned, press Ctrl+D to boot back into ChromeOS as a developer. You are now ready for step 3 -#### Developer Mode on Chromeboxes and Chromebases (ChromeOS Desktops and All-in-ones): +#### Developer Mode on Chromeboxes and Chromebases (ChromeOS Desktops and All-in-Ones): Not all monitors will work with the Chromebox OS Verification screens. This @@ -35,36 +35,44 @@ If you choose to back up with Google Drive, you will be prompted to add your Goo attempt to continue without a display. -1. Shut down the device, then insert a paper clip (SIM ejector tool works great too!) into the RECOVERY BUTTON (small hole usually near the I/O, see your hardware documentation for exact location) and reboot. You will then be greeted with the "OS Verification is turned off" screen. +1. Shut down the device, then insert a paper clip (SIM ejector tool works great too!) into the RECOVERY BUTTON (small hole usually near the ports, see your hardware documentation for exact location) and reboot. You will then be greeted with the "OS Verification is turned off" screen. 2. Plug in a keyboard and press Ctrl+D. You may be prompted with 'To turn OS verification off, press RECOVERY BUTTON,' press RECOVERY BUTTON. 3. A screen saying 'OS verification is off, press space to re-enable' should appear, press Ctrl+D. Your system is now transitioning into Developer Mode! (This may take a few minutes). -4. After it has transitioned, press Control+D to boot back into ChromeOS as a developer. You are now ready for step 3. +4. After it has transitioned, press Ctrl+D to boot back into ChromeOS as a developer. You are now ready for step 3. #### Developer Mode on ChromeOS Tablets: 1. Shut down the device, then press and hold Power+Volume-Up+Volume-Down for 3-5 seconds, then release to invoke recovery mode. This is a bit finicky, and may take a few tries, but the screen will turn white and display a screen saying "Please insert a recovery USB stick." soon after button release. -2. To boot to Developer mode, simultaneously press Volume-Up+Volume-Down, or navigate to 'Developer Options' with the volume buttons, and select it with the power button. then select 'Boot From Internal Disk using the volume buttons and power button.' +2. To boot to Developer mode, simultaneously press Volume-Up+Volume-Down, or navigate to 'Developer Options' with the volume buttons, and select it with the power button. then select 'Boot From Internal Disk' using the volume buttons and power button. Your system is now transitioning into Developer Mode! (This may take a few minutes). 3. After it has transitioned, again navigate to 'Developer Options,' then 'Boot From Internal Disk.' Plug in a keyboard, and you are now ready for step 3. If you have any problems with these steps, refer to [this guide](https://chromium.googlesource.com/chromiumos/docs/+/main/debug_buttons.md#Firmware-Keyboard-Interface) or request support in our [discord](https://discord.com/invite/5fdPuxTg5Q). -### 3. Enable USB booting +### 3. USB Booting -1. In Developer mode ChromeOS, press Ctrl+Alt+F2 [right arrow key]. -2. Type in 'Chronos' for the login (there is no password). +1. In ChromeOS Developer mode, press Ctrl+Alt+F2. +2. Type in 'chronos' for the login (there is no password, unless you set one previously. If you did, you probably know what you are doing). 3. Enter this command: ``` -enable_dev_usb_boot +sudo enable_dev_usb_boot ``` -4. You should have an output saying 'SUCCESS: Booting and self-assigned kernel from SSD/USB/SDCard slot in enabled.' Plug in your Ultramarine Chromebook installer and restart the device. If needed, press Ctrl+alt+F1 [Left arrow key] to leave the terminal. -5. The device will boot to the recovery screen. Upon reaching it, press ctrl+U> to boot from USB/SD. +4. You should have an output saying 'SUCCESS: Booting and self-assigned kernel from SSD/USB/SDCard slot is enabled.' Plug in your Ultramarine Chromebook installer and restart the device. If needed, press Ctrl+Alt+F1 to leave the terminal. +5. Restarting the device will boot to the recovery screen. Upon reaching it, press Ctrl+U> to boot from USB/SD. If on a ChromeOS tablet, use the volume keys to navigate to 'Developer Options,' select using the Power Button, then select 'Boot to External Disk.' -### 4. Boot from USB/SD +From here, you can follow the [Ultramarine install guide](/en/setup/installation/). -#### [Next Up: Post-Install →](postinstall) +Important: How to boot upon restart + +After you install, all you have to do boot to the internal disk (after a reboot or power off) from the ChromeOS Recovery Screen is either: + +- Press Ctrl+D +- Selecting 'Boot to Internal Disk' +- Just wait ~30 seconds + +#### [Next Up: Troubleshooting and FAQs →](faq-and-troubleshooting) #### [← Back To: Getting Chromebook Edition](getting) diff --git a/src/content/docs/en/chromebook/postinstall.mdx b/src/content/docs/en/chromebook/postinstall.mdx deleted file mode 100644 index 0f043330..00000000 --- a/src/content/docs/en/chromebook/postinstall.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Post-Installation -description: "Things to do after installing Ultramarine Chromebook Edition" ---- - -import Alert from "../../../../components/Docs/Alert.astro"; - -#### [Next Up: ARM Chromebooks (Beta) →](armbeta) - -#### [← Back To: Installing to a Chromebook](preparing) diff --git a/src/content/docs/en/chromebook/terminology.mdx b/src/content/docs/en/chromebook/terminology.mdx index 4a6fd3dd..1f9c03f5 100644 --- a/src/content/docs/en/chromebook/terminology.mdx +++ b/src/content/docs/en/chromebook/terminology.mdx @@ -15,7 +15,7 @@ The consumer variant of Chromium OS found on all Chrome devices. ### Write Protect (WP) -Usually refers to Firmware Write Protect (FW_WP), a feature of Chromebooks that marks a region of the ROM that holds firmware as read-only. It is possible (and rather easy) to remove the protection on most Chromebooks. [1] +Usually refers to Firmware Write Protect (FW_WP) or Hardware Write Protect. A feature of Chromebooks that marks a region of the ROM that holds firmware as read-only. It is possible (and rather easy) to remove the protection on most Chromebooks. [1] #### Cr50/Battery WP @@ -31,7 +31,7 @@ The primary implementation of write protect on older devices, a screw shorts a c ### Closed Case Debugging (CCD) -Allows people with cr50 to disable WP without opening the device. This requires a special cable called suzyQ. [1] [2] +Allows Chromebooks with cr50 to disable WP without opening the device. This requires a special device called suzyQ. Fyra Labs sells a [SuzyQ Board](https://developer.fyralabs.com/suzyqboard), or you can build one yourself. [1] [2] ### Verified Boot