Windows 10 11 Pro 64-bit Drivers BIOS UEFI Firmware on Chromebook Chromebox CR50 Google Security Chip Protected Laptop Hardware Software Crack Hack Exploit June 2023

#chromebook #acer #spin #713w

LIST: Working DEVICES / Drivers / Windows 10 Pro 64-bit Support:

:: Intel XE Graphics Driver ::

::  ::


Running Windows requires using the UEFI Full ROM firmware; there’s no way to get it running properly via Legacy Boot Mode on the stock firmware, or older Legacy Full ROM firmware (the lone exception currently is on AMD Zen+ Chromebooks). If possible, it’s highly recommended that you upgrade your SSD when possible, as 16GB is much more limiting for Windows than it is for ChromeOS or Linux.

  • hack crack bios UEFI
  • Acer
  • Spin 713-3w

Worked PERFECT on the above hardware Images Proof of Work to follow:



Due to recent changes in ChromeOS’ security settings, you may need to use a new set of commands to run the Firmware Utility Script under ChromeOS. Running it under Linux can use the same old one-line command.
Also, you must execute these commands **as a normal/non-root user**. Running them as root will break things. DO NOT RUN ‘SUDO SU’ BEFORE RUNNING THE SCRIPT CMD BELOW.

And do note that in the script command below, it’s `-LO` (L capital O), not L zero.

To download and run this script under ChromeOS or Linux, from a terminal/shell type:

cd; curl -LO && sudo bash


and press enter.

If you encounter certificate related errors when downloading the script from ChromeOS,

then add -k to the curl command and script command to bypass SSL certificate checking as so:

cd; curl -LOk && sudo bash


and press enter.

Under ChromeOS, this script must be run from:


crosh shell:

(logged in, normally or as a guest:

CTRL+ALT+T   type ‘shell’    press enter




from login screen:


login as: chronos


it cannot be run from crostini (penguin) terminal

as that is a virtualized container  & lacks the necessary access to read or modify the firmware.


Download & Execute:

Firmware Utility Script

on device with:

stock firmware and WP enabled

stock firmware and WP disabled

Full ROM firmware and WP disabled


In the screenshots above, only the script functions available for the device and current firmware are enabled (cyan text); unavailable functions are in grey. Features which require the firmware WP to be disabled are clearly labeled as such, along with the ability of that function to be used based on the current WP state.


Script Functions Explained


    • Install/Update the RW_LEGACY FirmwareThis 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.

      Requires firmware write-protect disabled: NO


    • Install/Update UEFI (Full ROM) FirmwareAs this is a full replacement firmware, the script will offer users the option to back up their stock firmware on USB (required if the script is not capable of providing a stock firmware image).

      As Chromeboxes store their Ethernet MAC address in the RO_VPD (read-only 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 UEFI (Full ROM) Firmware, your device will boot directly in UEFI Mode; ChromeOS will not be able boot. Your ChromeOS device is now a “regular PC,” and you can install the OS of your choice without any special instructions.

      Requires firmware write-protect disabled: YES


    • Set Boot Options (GBB Flags)This script function allows one to change the timeout for the Developer Mode boot screen (2s or 30s) and the default boot target (ChromeOS or Legacy Boot Mode). Setting the boot target to Legacy Boot removes the requirement of pressing [CTRL+L] at boot; instead, you must press [CTRL+D] to boot ChromeOS. This function is just a wrapper around the gbb_utility application built into ChromeOS that will read the GBB region from the stock firmware, set the GBB flags based on user input, and write it back to flash. For all options except ‘Factory Default,’ the GBB flags will also be set to force-enable legacy booting (GBB_FLAG_FORCE_DEV_BOOT_LEGACY), which overrides the crosssytem dev_boot_legacy flag, and to force-enable Developer Mode (GBB_FLAG_FORCE_DEV_SWITCH_ON), which prevents exiting Developer Mode via the spacebar (either accidentially or intentionally).

      Regardless of which default boot mode is selected, one can always override the default via keystroke: [CTRL+D] for ChromeOS Developer Mode, or [CTRL+L] for Legacy Boot Mode.

      Note: Whenever the GBB Flags are set to anything besides the Factory Default, their current value will be displayed in a small black box in the upper-left corner of the Developer Mode boot screen, along with other some other firmware/OS-related info. This is normal and no cause for alarm, though you’ll need to re-run the script and reset them to the Factory Default before exiting Developer Mode (should you want to do so).

      After setting the Boot Options / GBB flags, the boot timeout and default OS will be whatever you selected, and can be changed at any time by re-running this script function.

      Supported Devices: All ChromeOS devices running stock (or stock + RW_LEGACY) firmware

      Requires firmware write-protect disabled: YES


    • Set Hardware ID (HWID)This script function is also just a wrapper around the gbb_utility application built into ChromeOS. It will read the GBB region from the stock firmware, set the HWID based on user input, and write it back to flash. The only time this function is needed is if one flashed a generic recovery image firmware (aka a shellball ROM) from a source *other than this script* instead of restoring a backup of their own device firmware. Shellball ROMs extracted from a recovery image (or obtained from other sites/sources) have a generic HWID embedded which ChromeOS does not recognize as valid for purposes of OS and firmware updates (among other things), so it’s necessary to set a valid one. HWIDs aren’t unique, so any valid one will do.

      Note: If you restored your stock firmware using the option from this script, it is not necesary to set the HWID afterward.

      After setting a valid HWID, simply reboot and ChromeOS updates should work normally.

      Supported Devices: All ChromeOS devices running stock (or stock + RW_LEGACY) firmware

      Requires firmware write-protect disabled: YES


    • Remove ChromeOS BitmapsThis function removes the ChromeOS bitmap (image) files used to display the Developer Mode and Recovery boot screens, leaving you with a simple black screen with white terminal text — much easier on the eyes, esp when booting in a darkened environment.



      Note: ChromeOS updates might occasionally restore the missing bitmaps, so if you’re still running ChromeOS you may need to re-run this function as needed.

      Credit to Joshua Stein for bringing this to my attention via his blog which I stumbled upon somehow.

      Supported Devices: All pre-Skylake/pre-ApolloLake ChromeOS devices running stock (or stock + RW_LEGACY) firmware

      Requires firmware write-protect disabled: YES


    • Restore ChromeOS BitmapsThis script function reverses the function above 🙂

      Supported Devices: All pre-Skylake/pre-ApolloLake ChromeOS devices running stock (or stock + RW_LEGACY) firmware

      Requires firmware write-protect disabled: YES


    • Restore Stock BOOT_STUBThis script function will restore the stock BOOT_STUB for any device running a modified BOOT_STUB firmware. It will first attempt to use the built-in backup created by this script, and failing that, will download the firmware from a recovery image (a shellball ROM) and extract the stock BOOT_STUB from that. This option is only displayed on devices running BOOT_STUB firmware.

      After restoring the stock BOOT_STUB, you will need to reboot and reinstall ChromeOS from the recovery media. You can also install the RW_LEGACY firmware if you’re switching to it for some reason.

      Supported Devices: All Haswell, Broadwell, and Baytrail ChromeOS devices running modified BOOT_STUB firmware (whether installed from this script or another)

      Requires firmware write-protect disabled: YES


  • Restore Stock FirmwareThis script function will restore the stock firmware, preferably from a backed-up copy on USB. For most devices, if a user-provided backup is not available, the script will download the firmware from a recovery image (a shellball ROM). For Chromeboxes, if the current fimware contains an embedded VPD region, it will be extracted and merged before flashing. These (device-specific) shellball ROMs have been modified to include a valid hardware ID (HWID), so ChromeOS updates will work normally. Support for flashing shellball ROMs for additional devices is planned for the near future.

    After restoring the stock firmware, you will need to reboot and reinstall ChromeOS from the recovery media. After booting ChromeOS, you will need to re-run this script and reset the Boot Flags/GBB Flags in order to exit Developer Mode and fully return to stock.

    Supported Devices: All non-EOL ChromeOS devices running non-stock firmware

    Requires firmware write-protect disabled: YES

The Reboot and Power Off options are (hopefully) sufficiently self-explanitory 🙂

If running UEFI Full ROM firmware, there will be an additional option to clear the NVRAM. This will delete all bootorder entries stored in NVRAM, and they will be created again on the next boot (or next time grub is updated).


The source for the Firmware Utility Script (as well as all helper/accessory scripts)
can be found: MrChromebox/scripts



#Windows has historically been poorly supported on #ChromeOS devices, mostly due to stock #firmware that was built to do the absolute minimum to securely boot ChromeOS. With recent improvements in the #UEFI firmware, however, Windows now runs extremely well on most ChromeOS devices. The latest info on what devices are supported can be found on coolstar’s site linked below.
      • windows 10 64bit audio Drivers are tough for many laptops…

      • EMAIL security [@] Contact to discuss solutions which are not expensive


ChromeOS Firmware Utility script and Kodi E-Z Setup script:
ChromeOS Firmware Utility script and Kodi E-Z Setup script:



#BIOS Security chip






#CP713-3W #tigerlake #intel #mrchomebox



Tor |20| I2P |23| Canary






Tab 2

Tab 3

New Tab

New Tab

New Tab

Tab 2

Tab 3

UEFI firmware on ChromeOS devices offers many benefits over the older Legacy BIOS offerings:

  • Integrated firmware updates for the ChromeOS EC (Embedded Controller)
  • Better Windows support and faster Windows boot time (50%+ faster)
  • Full working HDMI audio under Windows, without any special drivers or hackery
  • Support for compressed Windows installs
  • Better support for dual/triple/quad boot scenarios
  • Ability to run macOS on (some) Core i3/i5/i7-based machines
  • Better support for USB devices at boot time (SeaBIOS was/is quite finnicky)

And a few more I’m forgetting as well.

#ChromeOS #Boot #Modes

ChromeOS has several different boot modes, which are important to understand in the context of modifying your device to run an alternate OS:

  • Normal/Verified Boot Mode
    • Can only boot Google-signed ChromeOS images
    • Full verification of firmware and OS kernel
    • No root access to the system, no ability to run Linux or boot other OSes
    • Automatically enters Recovery Mode if any step of Verified Boot fails
    • Default / out-of-the-box setting for all ChromeOS devices
  • Recovery Mode
    • User presented with Recovery Mode boot screen (white screen with ‘ChromeOS is missing or damaged’ text)
    • Boots only USB/SD with signed Google recovery image
    • Automatically entered when Verified Boot Mode fails
    • Can be manually invoked:
      On Chromebooks, via keystroke: [ESC+Refresh+Power]
      On Chromeboxes, by pressing a physical recovery button at power-on
      On Convertibles/Tablets, by pressing/holding the Power, Vol+, and Vol- buttons for 10s and then releasing
    • Allows for transition from Verified Boot Mode to Developer Mode
      On Chromebooks/Chromeboxes, via keystroke: [CTRL+D]
      On Convertibles/Tablets, via button press: Vol+/Vol- simultaneously
    • Booting recovery media on USB/SD will completely repartition/reformat internal storage and reload ChromeOS (as well as some RW firmware components)

    Note: The ChromeOS recovery process does not reset the firmware boot flags (GBB Flags), so if those are changed from the default, they will still need to be reset for factory default post-recovery.

  • Developer Mode
    • “Jailbreak” mode built-in to every ChromeOS device
    • Loosened security restrictions, allows root/shell access, ability to run Linux via crouton
    • Verified Boot (signature checking) disabled by default, but can be re-enabled
    • Enabled via [CTRL+D] on the Recovery Mode boot screen
    • Boots to the developer mode boot screen (white screen with ‘OS verification is off’ text), from which the user can select via keystroke where to boot:
         ChromeOS (in developer mode) on internal storage ( [CTRL+D] )
         ChromeOS/ChromiumOS on USB ( [CTRL+U] )
         Legacy Boot Mode ( [CTRL+L] )
    • Boot screen displays the ChromeOS device/board name in the hardware ID string (eg, PANTHER F5U-C92, which is useful to know in the context of device recovery, firmware support, or in determining what steps are required to install a given alternate OS on the device.
  • Legacy Boot Mode
    • Unsupported (by Google) method for booting alternate OSes (Linux, Windows) via the SeaBIOS firmware payload / RW_LEGACY firmware region
    • Accessed via [CTRL+L] on the developer mode boot screen
    • Requires explicit enabling in Developer Mode via command line: sudo crossystem dev_boot_legacy=1 (installing RW_LEGACY firmware via the Firmware Utility Script will set this for you)
    • Not all ChromeOS devices are capable out of the box, most require a RW_LEGACY firmware update first
    • Boots to the (black) SeaBIOS splash screen; if multiple boot devices are available, a prompt to show the boot menu will be displayed.

    Note: If you hear two beeps after pressing [CTRL+L], then either your device doesn’t have a valid Legacy Boot Mode / RW_LEGACY firmware installed, or legacy boot capability has not been been enabled via crossystem.

    Using the ChromeOS Firmware Utility Script to update your device’s RW_LEGACY firmware region will address both of these issues, as it not only provides an updated, fully functional RW_LEGACY firmware, but also sets the required boot flag.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.