Difference between revisions of "Installing/Preparing"

From GalliumOS Wiki
Jump to: navigation, search
(→‎Haswell)
(rewrite)
Line 1: Line 1:
 +
__NOTOC__
 +
To install a new operating system onto your ChromeOS device, you must first enable "Developer Mode". '''Some''' models also require updating firmware.
 +
 +
To determine what preparation steps your device requires, you will need to know your Hardware ID. This is available from inside ChromeOS by navigating to <code>chrome://system</code>, where it's called <code>hardware_class</code>.
 +
 +
Next, check our [[Hardware Compatibility]] page to determine your device's CPU family. For example, the Acer C720's Hardware ID is <code>PEPPY</code>, and the CPU family is <code>Haswell</code>.
 +
 +
Armed with this information, we can begin:
 +
 +
== Step 1: Enable Developer Mode ==
 +
 +
'''WARNING''': Enabling Developer Mode will erase all user data in ChromeOS. If you have locally-stored data, back it up first. Cloud data will not be lost.
 +
 +
# With device shut down, press Esc+F3(refresh)+Power
 +
# You will see a white screen saying "ChromeOS is damaged or missing" (although it is not)
 +
# Press Ctrl+D to enable Developer Mode, then follow confirmation steps
 +
# Your machine will reboot to a white screen which says "OS verification is OFF". This is developer mode.
 +
# Enable Legacy Mode booting (skip this step if updating firmware)
 +
## Press Ctrl+D to boot ChromeOS in '''D'''eveloper Mode
 +
## Configure Wi-Fi if necessary, and log in to Chrome (Guest account is fine)
 +
## Press Ctrl+Alt+T to get a ChromeOS terminal ("crosh") window
 +
## At the prompt, enter <code>shell</code>
 +
## At the <code>chronos@localhost / $</code> prompt, run the following:
 +
##* <code>sudo crossystem dev_boot_legacy=1</code>
 +
 +
== Step 2: Flash Firmware (if required or desired) ==
 +
 +
Here's where you'll need to know your Hardware ID, and CPU family.
 +
 +
* '''Sandy Bridge''' models '''require''' custom firmware (exception: LINK)
 +
* '''Bay Trail''' and '''Braswell''' models '''require''' custom firmware
 +
* '''Haswell''', '''Broadwell''', and '''Skylake''' models can ''benefit'' from custom firmware
 +
 +
Custom firmware (for many models) is available in multiple types and from multiple sources. See [[Firmware]] for more discussion.
 +
 +
=== Step 2a: Disable write-protection (if required) ===
 +
 +
Some types of updates (<code>BOOT_STUB</code> and <code>full</code>) require disabling firmware write-protection on your device. Be sure to read the [[Firmware]] page first! Write protection (WP) on ChromeOS devices is usually controlled by a screw on the motherboard, but some models also have conductive stickers, and older models sometimes have a jumper. The location and appearance of the WP screw/sticker/jumper vary between models, but in all cases you will need to open your device.
 +
 +
A web search for "<model or hardware id> chromebook disable write-protect" will often return detailed instructions, with photos, for your model. If not, feel free to ask for help in [https://reddit.com/r/GalliumOS /r/GalliumOS] or [https://galliumos.org/irc #galliumos].
 +
 +
=== Step 2b: Update Firmware ===
 +
 +
You can update your firmware from the ChromeOS terminal, or from a running Linux system. These instructions describe the process from the ChromeOS terminal.
 +
 +
# Boot into ChromeOS by pressing Ctrl+D at the "OS verification is OFF" Developer Mode screen
 +
# Configure Wi-Fi if necessary, and log in to Chrome (Guest account is fine)
 +
# Press Ctrl+Alt+T to get a ChromeOS terminal ("crosh") window
 +
# At the prompt, enter <code>shell</code>
 +
# Decide which firmware you want to install. See [[Firmware]].
 +
# At the <code>chronos@localhost / $</code> prompt, run the command to flash your firmware. These commands are current as of this writing, but be sure to check the developer's sites for any changes.
 +
# '''Choose ''ONE'' of the following''':
 +
#* '''MrChromebox''' [http://mrchromebox.tech/ (developer's site)]
 +
#*# <code>cd; curl -OL http://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh</code>
 +
#* '''John Lewis''' [http://johnlewis.ie/ (developer's site)]
 +
#*# <code>cd; rm -f flash_chromebook_rom.sh; curl -O https://johnlewis.ie/flash_chromebook_rom.sh; sudo -E bash flash_chromebook_rom.sh</code>
 +
# Then follow the on-screen instructions to install firmware
 +
 +
== Step 3. Install GalliumOS ==
 +
 +
You are now ready to install GalliumOS from ISO (or if dual-booting, via chrx)
 +
 +
== Other options from the Developer Mode screen ==
 +
 +
The Developer Mode boot screen offers a few additional options. The most important one is Ctrl+L for Legacy Mode booting, which you will use to boot GalliumOS after installing (depending on your firmware choice). Here is the full list:
 +
 +
* Ctrl+D to boot ChromeOS in '''D'''eveloper Mode, or
 +
* Ctrl+L to boot '''L'''egacy Mode (usually used for Linux, after installing)
 +
* Ctrl+U to boot a ChromeOS (or ChromiumOS) image from USB
 +
* TAB for some boot configuration information
 +
 +
<!-- OLDSTUFF
 +
 
If you have already used Linux on your Chromebook in the past (Crouton does NOT count), you probably don't need to do this. This article will cover the very minimal requirements for making it work on each generation of Chromebook. This means we won't flash any firmware if we don't need to. If you want instructions for flashing firmware, see [[Firmware]]. Please note that this process can be very dangerous, so please carefully read everything and do not skip any steps. We are not responsible if you brick your Chromebook, even though we think it sucks that you did. Despite the fact that the Chromebook Pixel and 2015 Chromebook Pixel are Sandy Bridge and Broadwell respectively, you should use the Haswell process for both of them. We know this doesn't make any sense, but just trust us.
 
If you have already used Linux on your Chromebook in the past (Crouton does NOT count), you probably don't need to do this. This article will cover the very minimal requirements for making it work on each generation of Chromebook. This means we won't flash any firmware if we don't need to. If you want instructions for flashing firmware, see [[Firmware]]. Please note that this process can be very dangerous, so please carefully read everything and do not skip any steps. We are not responsible if you brick your Chromebook, even though we think it sucks that you did. Despite the fact that the Chromebook Pixel and 2015 Chromebook Pixel are Sandy Bridge and Broadwell respectively, you should use the Haswell process for both of them. We know this doesn't make any sense, but just trust us.
  
Line 98: Line 171:
  
 
Fully-functional firmware options are not available yet, so running GalliumOS on Braswell is not yet possible / unsupported.
 
Fully-functional firmware options are not available yet, so running GalliumOS on Braswell is not yet possible / unsupported.
 +
 +
EO_OLDSTUFF
 +
-->

Revision as of 17:31, 11 August 2016

To install a new operating system onto your ChromeOS device, you must first enable "Developer Mode". Some models also require updating firmware.

To determine what preparation steps your device requires, you will need to know your Hardware ID. This is available from inside ChromeOS by navigating to chrome://system, where it's called hardware_class.

Next, check our Hardware Compatibility page to determine your device's CPU family. For example, the Acer C720's Hardware ID is PEPPY, and the CPU family is Haswell.

Armed with this information, we can begin:

Step 1: Enable Developer Mode

WARNING: Enabling Developer Mode will erase all user data in ChromeOS. If you have locally-stored data, back it up first. Cloud data will not be lost.

  1. With device shut down, press Esc+F3(refresh)+Power
  2. You will see a white screen saying "ChromeOS is damaged or missing" (although it is not)
  3. Press Ctrl+D to enable Developer Mode, then follow confirmation steps
  4. Your machine will reboot to a white screen which says "OS verification is OFF". This is developer mode.
  5. Enable Legacy Mode booting (skip this step if updating firmware)
    1. Press Ctrl+D to boot ChromeOS in Developer Mode
    2. Configure Wi-Fi if necessary, and log in to Chrome (Guest account is fine)
    3. Press Ctrl+Alt+T to get a ChromeOS terminal ("crosh") window
    4. At the prompt, enter shell
    5. At the chronos@localhost / $ prompt, run the following:
      • sudo crossystem dev_boot_legacy=1

Step 2: Flash Firmware (if required or desired)

Here's where you'll need to know your Hardware ID, and CPU family.

  • Sandy Bridge models require custom firmware (exception: LINK)
  • Bay Trail and Braswell models require custom firmware
  • Haswell, Broadwell, and Skylake models can benefit from custom firmware

Custom firmware (for many models) is available in multiple types and from multiple sources. See Firmware for more discussion.

Step 2a: Disable write-protection (if required)

Some types of updates (BOOT_STUB and full) require disabling firmware write-protection on your device. Be sure to read the Firmware page first! Write protection (WP) on ChromeOS devices is usually controlled by a screw on the motherboard, but some models also have conductive stickers, and older models sometimes have a jumper. The location and appearance of the WP screw/sticker/jumper vary between models, but in all cases you will need to open your device.

A web search for "<model or hardware id> chromebook disable write-protect" will often return detailed instructions, with photos, for your model. If not, feel free to ask for help in /r/GalliumOS or #galliumos.

Step 2b: Update Firmware

You can update your firmware from the ChromeOS terminal, or from a running Linux system. These instructions describe the process from the ChromeOS terminal.

  1. Boot into ChromeOS by pressing Ctrl+D at the "OS verification is OFF" Developer Mode screen
  2. Configure Wi-Fi if necessary, and log in to Chrome (Guest account is fine)
  3. Press Ctrl+Alt+T to get a ChromeOS terminal ("crosh") window
  4. At the prompt, enter shell
  5. Decide which firmware you want to install. See Firmware.
  6. At the chronos@localhost / $ prompt, run the command to flash your firmware. These commands are current as of this writing, but be sure to check the developer's sites for any changes.
  7. Choose ONE of the following:
  8. Then follow the on-screen instructions to install firmware

Step 3. Install GalliumOS

You are now ready to install GalliumOS from ISO (or if dual-booting, via chrx)

Other options from the Developer Mode screen

The Developer Mode boot screen offers a few additional options. The most important one is Ctrl+L for Legacy Mode booting, which you will use to boot GalliumOS after installing (depending on your firmware choice). Here is the full list:

  • Ctrl+D to boot ChromeOS in Developer Mode, or
  • Ctrl+L to boot Legacy Mode (usually used for Linux, after installing)
  • Ctrl+U to boot a ChromeOS (or ChromiumOS) image from USB
  • TAB for some boot configuration information


Retrieved from "https://wiki.galliumos.org/index.php?title=Installing/Preparing&oldid=1045"