How can I boot from USB on HP Chromebook 11 G5?

[Guy Azran]

I've recently gotten an HP Chromebook 11 G5 and am looking to boot software off a USB. However, I've been unsuccessful in all my attempts. I've tried the following (all of these were done after putting the computer in developer mode):

1. I tried going to press CTRL+L and CTRL+U as instructed in some sites, but every time the computer would beep and refresh the white recovery screen without doing anything else.

2. I then tried going into the terminal as root and type the following commands: "crossystem dev_boot_usb=1 dev_boot_legacy=1" or "crossystem dev_boot_usb=1 dev_boot_signed_only=0". Then i repreated step 1 but still the same thing happened.

Other solutions i found were either outdated or were not compatible with this chromebook.

Has anyone had this problem and know what to do?

[Mike Frysinger]

the docs for that are here:

http://dev.chromium.org/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/generic

but sounds like you've largely followed the right steps.  please run `sudo crossystem` and copy&paste the output here for us to double check.

remember that Ctrl+U for USB boot will only boot media formatted the way CrOS expects -- GPT & kernel partitions using verified boot format.  if you want to boot a typical USB disk from a distro like Ubuntu, you need to use legacy boot (Ctrl+L) instead.

-mike

--
--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[Guy Azran]

thanks for the docs. Here is the output for crossystem:

arch                   = x86                            # Platform architecture
backup_nvram_request   = 0                              # Backup the nvram somewhere at the next boot. Cleared on success.
battery_cutoff_request = 0                              # Cut off battery and shutdown on next boot.
block_devmode          = 0                              # Block all use of developer mode
clear_tpm_owner_request = 0                              # Clear TPM owner on next boot
clear_tpm_owner_done   = 1                              # Clear TPM owner done
cros_debug             = 1                              # OS should allow debug features
dbg_reset              = 0                              # Debug reset mode request (writable)
debug_build            = 0                              # OS image built for debug features
dev_boot_usb           = 1                              # Enable developer mode boot from USB/SD (writable)
dev_boot_legacy        = 1                              # Enable developer mode boot Legacy OSes (writable)
dev_boot_signed_only   = 0                              # Enable developer mode boot only from official kernels (writable)
dev_default_boot       = disk                           # default boot from legacy or usb (writable)
devsw_boot             = 1                              # Developer switch position at boot
devsw_cur              = 1                              # Developer switch current position
disable_dev_request    = 0                              # Disable virtual dev-mode on next boot
ecfw_act               = RW                             # Active EC firmware
fmap_base              = 0xffe10000                     # Main firmware flashmap physical address
fwb_tries              = 0                              # Try firmware B count (writable)
fw_vboot2              = 0                              # 1 if firmware was selected by vboot2 or 0 otherwise
fwid                   = Google_Setzer.7287.298.0       # Active firmware ID
fwupdate_tries         = 0                              # Times to try OS firmware update (writable, inside kern_nv)

fw_tried               = A                              # Firmware tried this boot (vboot2)
fw_try_count           = 0                              # Number of times to try fw_try_next (writable)
fw_try_next            = A                              # Firmware to try next (vboot2,writable)
fw_result              = unknown                        # Firmware result this boot (vboot2,writable)
fw_prev_tried          = A                              # Firmware tried on previous boot (vboot2)
fw_prev_result         = unknown                        # Firmware result of previous boot (vboot2)
hwid                   = SETZER D3J-D2E-66A-Y7B         # Hardware ID
inside_vm              = 0                              # Running in a VM?
kern_nv                = 0x00000000                     # Non-volatile field for kernel use
kernkey_vfy            = sig                            # Type of verification done on kernel key block
loc_idx                = 0                              # Localization index for firmware screens (writable)
mainfw_act             = A                              # Active main firmware
mainfw_type            = developer                      # Active main firmware type
nvram_cleared          = 0                              # Have NV settings been lost?  Write 0 to clear
oprom_needed           = 0                              # Should we load the VGA Option ROM at boot?
phase_enforcement      = (error)                        # Board should have full security settings applied
recovery_reason        = 0                              # Recovery mode reason for current boot
recovery_request       = 0                              # Recovery mode request (writable)
recovery_subcode       = 0                              # Recovery reason subcode (writable)
recoverysw_boot        = 0                              # Recovery switch position at boot
recoverysw_cur         = (error)                        # Recovery switch current position
recoverysw_ec_boot     = 0                              # Recovery switch position at EC boot
ro_fwid                = Google_Setzer.7287.248.0       # Read-only firmware ID
sw_wpsw_boot           = 0                              # Firmware write protect software setting enabled at boot (Baytrail only)
tpm_attack             = 0                              # TPM was interrupted since this flag was cleared
tpm_fwver              = 0x00050001                     # Firmware version stored in TPM
tpm_kernver            = 0x00010001                     # Kernel version stored in TPM
tpm_rebooted           = 0                              # TPM requesting repeated reboot (vboot2)
try_ro_sync            = 0                              # try read only software sync
tried_fwb              = 0                              # Tried firmware B before A this boot
vdat_flags             = 0x00004c56                     # Flags from VbSharedData
vdat_timers            = LFS=443141160,489709160 LF=491146420,1037985360 LK=1,9116674 # Timer values from VbSharedData
wipeout_request        = 0                              # Firmware requested factory reset (wipeout)
wpsw_boot              = 1                              # Firmware write protect hardware switch position at boot
wpsw_cur               = 1                              # Firmware write protect hardware switch current position

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org

[Mike Frysinger]

that output looks fine at a glance.  i guess it comes back to what exactly are you trying to boot on the USB stick ?  some Linux distro's USB image ?  or a CrOS image ?

-mike

--
--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org

[Guy Azran]

I'm trying to boot Ubuntu 16.04 LTS 64bit.
I don't understand why this matters though because no matter what's on the USB, as long as it's bootable, I should be able to boot from it with CTRL+L on the white verification screen on boot up. Am I right?
For some reason, CTRL+L just makes it he computer beep

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org

View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org

View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Chromium OS discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

[Mike Frysinger]

you said you tried using Ctrl+U and i explained why that won't work

Ctrl+L loads SeaBIOS, if it's installed.  if it isn't installed, then you'll get a beep.  unfortunately, not all devices ship with SeaBIOS.  you might be able to find one for your device here:

  https://johnlewis.ie/custom-chromebook-firmware/rom-download/

-mike

--
--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org

View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

--
--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org

View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Chromium OS discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-discuss+unsub...@chromium.org.

[Kevin Pierce]

Hey Guy, I know this is an old issue, but your crossystem report is showing your hardware write protection is still active. It's not too difficult to remove it. Check out this guide https://ashnoxious.github.io/blog/disabling-chromebook-setzer-wp

These are the two lines at the end that are saying your hardware WP is still active (value=1)

....wpsw_boot = 1 # Firmware write protect hardware switch position at boot

....wpsw_cur = 1 # Firmware write protect hardware switch current position

Maybe someone else out there will find this useful.

[DennisLfromGA]

Kevin,

Guy is trying to boot Ubuntu on external USB media.

For that, the device needs a working SeaBIOS like Mike mentioned above.

He'll need to run a script from john.lewis or mr.chromebox to install SeaBIOS which can be done without removing the write-protect screw so there's no need to remove it.

~Denny

[Kevin Pierce]

My mistake. I read that as install from USB not booting live disk. I can verify this model works with Mr Chromebox. I tried it with the Lewis script and I got the same response OP was getting. Future crackers with this model should do Mr Chromebox full rom and send him some lovely donations.

(P.S. Lubuntu is a nice OS but I had to create a bash script to run at startup to fine tune my TouchPad.)

[Guy Azran]

(P.S. Lubuntu is a nice OS but I had to create a bash script to run at startup to fine tune my TouchPad.)

do you still have this script? my touchpad is driving me nuts as well

[Guy Azran]

For some reason i got your answer only to my gmail, so ill leave our conversation here and consider this issue closed

On Monday, February 12, 2018 at 4:59:32 PM UTC+2, DennisLfromGA wrote:

Me:

It seems like there is no script that can install a bios on this model. However, I found this script  that fully installs Ubuntu and many other distros on a new partition and allows you to legacy boot it.
All instructions are here:
https://chrx.org

This is good enough for me, even though it is not what I asked.

Thanks to everyone for your input

 

 Denny: 

You said you were trying to boot an external OS (Ubuntu) on your HP Chromebook 11 G5 (Setzer) not install a BIOS that's why I mentioned john.lewis and mr.chromebox.The Mr.Chromebox site does have scripts to install SeaBIOS and install a full rom on your (Braswell) Chromebook, see below -

Install/Update the RW_LEGACY Firmware

This option performs two simple tasks: it sets the crossystem boot flag necessary to enable Legacy Boot mode, and it installs an RW_LEGACY firmware update appropriate for the device. Users will have the option to set the default boot device (internal storage [default] or USB/SD); Haswell/Broadwell Chromebox users will also have the option to enable "headless" (no display attached) booting, which is really only useful if you're going to run the box without a display and connect remotely (eg, via ssh). Changing either of these options requires re-running this script function.

After updating the RW_LEGACY firmware, Legacy Boot Mode can be accessed via [CTRL+L] on the Developer Mode boot screen. It can also be set as the default by changing the GBB Flags via 'Set Boot Options' feature below.

Supported Devices: All Haswell, Broadwell, and Baytrail, Braswell, Skylake, ApolloLake, and Kabylake ChromeOS devices, plus the Chromebook Pixel 2013

Requires firmware write-protect disabled: NO

Install/Update Custom coreboot Firmware (Full ROM)

As this is a full replacement firmware, the script will offer users the option to back up their stock firmware on USB. Chromebox users have the option of a Legacy Boot or UEFI compatible firmware. When the Legacy Boot option is selected, users will have the option to set the default boot device (internal storage [default] or USB/SD); Haswell/Broadwell Chromebox users will also have the option to enable "headless" (no display attached) booting, as well as the option to enable PXE (Ethernet/network) booting via iPXE. If PXE support is enabled, it can also be set to be the default boot device. As before, changing any of these boot options requires re-running this script function.

Since Haswell/Broadwell/Baytrail Chromeboxes store their Ethernet MAC address in the VPD (vital product data) region of the stock firmware, the script will extract that region from the stock firmware and inject it into the new firmware ensuring the unique MAC address isn't lost. It will also persist the VPD region across firmware updates, so this is all transparent to the user.

After installing the Custom coreboot / Full ROM Firmware, your device will boot directly in UEFI (or Legacy) Mode; ChromeOS will not boot (though it will try to do so and fail, until a new OS is installed). Your ChromeOS device is now a "regular PC," and you can install the OS of your choice without any special instructions.

Supported Devices: All SandyBridge, IvyBridge, Haswell, Broadwell, Baytrail, and Braswell ChromeOS devices

Requires firmware write-protect disabled: YES

 

However, I found this script  that fully installs Ubuntu and many other distros on a new partition and allows you to legacy boot it.​

Yes, 'chrx' is another alternative that I have used but for a different purpose.

~Denny

 

Thanks Denny and everyone for your help!

 

 

[Peter Yoon]

Hi Guy,

I'm in the process of installing Ubuntu onto my HP 11 G5 EE...

Which version were you able to install onto your device?

Thanks, Peter