Are you over 18 and want to see adult content?
More Annotations
A complete backup of happilyeverafter-bridal.co.uk
Are you over 18 and want to see adult content?
Favourite Annotations
A complete backup of https://printronix.com
Are you over 18 and want to see adult content?
A complete backup of https://activegreengermany.com
Are you over 18 and want to see adult content?
A complete backup of https://management30.com
Are you over 18 and want to see adult content?
A complete backup of https://content-science.com
Are you over 18 and want to see adult content?
A complete backup of https://buyforfun.biz
Are you over 18 and want to see adult content?
A complete backup of https://wayi.com.tw
Are you over 18 and want to see adult content?
A complete backup of https://purevpn.fr
Are you over 18 and want to see adult content?
A complete backup of https://bake-neko.net
Are you over 18 and want to see adult content?
A complete backup of https://dna.land
Are you over 18 and want to see adult content?
A complete backup of https://terrycosta.com
Are you over 18 and want to see adult content?
A complete backup of https://socialworkers.org
Are you over 18 and want to see adult content?
A complete backup of https://develoeper.com
Are you over 18 and want to see adult content?
Text
through.
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
SUPPORTED DEVICES
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; Privacy MRCHROMEBOX.TECHCHROMEOS FIRMWARE UTILITY SCRIPTSUPPORTED DEVICESUNBRICKINGFIRMWARE WRITE PROTECTWIKI HOME MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKISEE MORE ON WIKI.MRCHROMEBOX.TECH FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
SUPPORTED DEVICES
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; PrivacyMRCHROMEBOX.TECH
MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKI If you've found your way here, it's likely because you updated your firmware and, despite best efforts to minimize the possibility,something went wrong. FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
SUPPORTED DEVICES
All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID). Your device's board name is what determines if it's supported or not -- not the make, model, CPU, or anything WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; Privacy MRCHROMEBOX.TECHCHROMEOS FIRMWARE UTILITY SCRIPTSUPPORTED DEVICESUNBRICKINGFIRMWARE WRITE PROTECTWIKI HOME MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKISEE MORE ON WIKI.MRCHROMEBOX.TECH FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
SUPPORTED DEVICES
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; Privacy MRCHROMEBOX.TECHCHROMEOS FIRMWARE UTILITY SCRIPTSUPPORTED DEVICESUNBRICKINGFIRMWARE WRITE PROTECTWIKI HOME MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKISEE MORE ON WIKI.MRCHROMEBOX.TECH FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
SUPPORTED DEVICES
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; PrivacyMRCHROMEBOX.TECH
MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKI If you've found your way here, it's likely because you updated your firmware and, despite best efforts to minimize the possibility,something went wrong. FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
SUPPORTED DEVICES
All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID). Your device's board name is what determines if it's supported or not -- not the make, model, CPU, or anythingMRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; Privacy MRCHROMEBOX.TECHCHROMEOS FIRMWARE UTILITY SCRIPTSUPPORTED DEVICESUNBRICKINGFIRMWARE WRITE PROTECTWIKI HOME MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKISEE MORE ON WIKI.MRCHROMEBOX.TECH FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
SUPPORTED DEVICES
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; Privacy MRCHROMEBOX.TECHCHROMEOS FIRMWARE UTILITY SCRIPTSUPPORTED DEVICESUNBRICKINGFIRMWARE WRITE PROTECTWIKI HOME MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKISEE MORE ON WIKI.MRCHROMEBOX.TECH FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
SUPPORTED DEVICES
MRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; PrivacyMRCHROMEBOX.TECH
MrChromebox.tech : Custom coreboot firmware and firmware utilities for your Chromebook/Chromebox UNBRICKING - MRCHROMEBOX WIKI If you've found your way here, it's likely because you updated your firmware and, despite best efforts to minimize the possibility,something went wrong. FIRMWARE WRITE PROTECT Firmware Write Protect on ChromeOS Devices. The firmware write protect mechanism is one of the most misunderstood aspects of ChromeOS devices; many guides/blogs/how-to's incorrectly tell users to disable it as part of whatever process they are attempting to guide the userthrough.
SUPPORTED DEVICES
All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID). Your device's board name is what determines if it's supported or not -- not the make, model, CPU, or anythingMRCHROMEBOX WIKI
MrChromebox.tech exists to provide background info on Chrome OS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your Chromebook or Chromebox, you've come to the rightplace.
WINDOWS ON CHROMEOS DEVICES A non-trivial amount of Chromebook/Chromebox users want to run Windows on their devices, rather than ChromeOS or Linux. As someone who grew up using DOS, then Windows 3.1, 95, 98, 2000, XP, 7, and now Windows 10, the scars of using Microsoft products run deep MAIN PAGE - MRCHROMEBOX WIKI This page was last modified on 11 August 2018, at 20:10. Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.; PrivacyMRCHROMEBOX.TECH
CUSTOM COREBOOT FIRMWARE AND FIRMWARE UTILITIES FOR YOUR CHROMEBOOK/CHROMEBOX* Home
* ChromeOS Boot Modes* Developer Mode
* All About Firmware * Legacy Boot and UEFI* Alternative OSes
* Firmware Utility Script * Kodi E-Z Setup Script* Supported Devices
* Services and Support* FAQ
*
GREETINGS FELLOW CHROMEOS ENTHUSIASTS! This site is designed to provide background info on ChromeOS, Developer Mode, and Legacy Boot Mode, as well as info on modifying/replacing the the firmware on your device in order to better meet your needs. If you're looking for information on how to run Linux or Windows on your ChromeOS device, you've come to the right place. It's also the home of the ChromeOS Firmware Utility Script and Kodi E-Z Setup Script, which simplify and automate many of the tasks required to run an alternate OS and/or Kodi Media Center on your Chromebook/Chromebox.LATEST UPDATES
COREBOOT 4.10 RELEASE (AND MORE)(2019.08.22)
Like this update, the coreboot 4.10 release was a bit delayed, but hopefully the result will be a nice stable release with no regressions (one can dream, anyway). The UEFI Full ROM firmware for all devices has been updated and rebuilt, with the following notable changes: - coreboot codebase updated to 4.10 release - added UEFI Full ROM firmware for NAMI and SORAKA KabylakeChroembooks
- added UEFI Full ROM firmware for all Purism Librem laptops - Fixed touchscreen function on LINK under Cloudready - Fixed tablet mode functionality on CYAN - Fixed booting issues on some CLAPPER devices - and a few more things I need to pull out of the commit list Additionally, preliminary RW_LEGACY support has been added for AMD StoneyRidge-based Chromebooks, using Tianocore as the payload. Booting from internal eMMC is not yet working, but booting from external sources works as expected. (FWIW, Ubuntu 19.04 seems fully functional OOTB on these devices,which is nice)
As usual, the full list of changes can be found on my github repos.
NVRAM? YEP, WE GOT THAT!(2018.12.30)
Since the beginning, one of the major features missing from the UEFI firmware available for ChromeOS devices (or for any devices using Tianocore as the coreboot payload) has been NVRAM to save the UEFI settings -- most notably, the boot order. I'm happy to report that's no longer an issue :). While not all settings are hooked into the NVRAM backend yet, boot order manipulation and custom boot targets are now possible, which makes things a lot easier. The UEFI Full ROM firmware for all devices has been updated and rebuilt, with the following notable changes: - coreboot codebase updated to 4.9 release - Tianocore codebase updated to current upstream master - NVRAM functional to support boot order customization - added UEFI Full ROM firmware for the Pixelbook (EVE) - added UEFI Full ROM firmware for the Acer Chromebase 24 (BUDDY) - SandyBridge/IvyBridge devices now use coreboot native graphics init(libgfxinit)
- improved VMX support for Skylake/Kabylake devices - fixed detection of internal storage for Core i-based KabylakeChromeboxes
- improved handling of write-protection on Apollolake/Kabylake devices - and a few more things I'll add as I remember them As usual, the full list of changes can be found on my github repos.
UEFI FULL ROM FIRMWARE NOW AVAILABLE FOR ALL SKYLAKE CHROMEBOOKS AND KABYLAKE CHROMEBOXES(2018.08.02)
Long overdue but hopefully worth the wait -- UEFI Full ROM firmware for Skylake Chromebooks! The target audience for this firmware is users wanting to run a standalone Linux setup on their Skylake Chromebook. While installation of Windows 10 is possible, there are still numerous issues on the firmware side and missing drivers which prevent these devices from being useful under Windows. As with previous releases, updated EC firmware is included as well. The UEFI Full ROM firmware for all devices has been updated and rebuilt, with the following notable changes: - coreboot codebase updated to 4.8 release - Tianocore codebase updated to current upstream master - updated the CPU microcode on all devices to the latest Intel recommended versions (which includes mitigations for Meltdown/Spectre) - added support for the 2018/Kabylake Chromeboxes - fixed DisplayPort outputs on Stumpy (Samsung Series 3 Chromebox) - fixed cooling fan occassionally stalling on Link (Chromebook Pixel2013)
- improved compatibility for Braswell devices with newer (4.13+) Linuxkernels
- script now double verifies Full ROM firmware flashes - script now uses the firmware flash chip's built-in write-protect functionality to protect the Full ROM firmware after flashing, which should hopefully significantly reduce any chance of bricking (not yet implemented for Skylake/Kabylake) - script no longer disables software write-protect automatically when run outside of ChromeOS As usual, the full list of changes can be found on my github repos.
UEFI FULL ROM FIRMWARE NOW AVAILABLE FOR ALL BRASWELL DEVICES (ANDSTOUT TOO!)
(2018.02.04)
It's taken a long time to get here, but it's finally happened -- UEFI Full ROM firmware for Braswell devices! Not only that, but we were able to fix many of the issues which led us to believe that we wouldn't be able to have full functionality under Windows 10 (ok almost full -- touchscreens don't work due to lack of custom drivers required, and have been disabled/hidden as a result. But everything else works, even built-in speakers/headphones). coolstar will be updating his Windows install guide shortly, which will include links to the requried drivers for touchpad and audiosupport.
Linux users will need to use a distro with kernel 4.13 or newer in order to have a functional keyboard; GalliumOS users should use thispre-release 2.2 ISO
to ensure full functionality OOTB. Braswell users don't get all the fun though, all UEFI Full ROM firmware has been updated and rebuilt, with the following notablechanges:
- coreboot codebase updated to 4.7 release - Tianocore codebase updated to current upstream master - fixed issue where available RAM limited to 2GB when UEFI firmware booted without a connected display (headless mode) - enabled keyboard backlight on boot (for devices which have it), providing early proof-of-life and eliminating need for OS driver (but still supports use of one) - updated the CPU microcode on Haswell and Broadwell devices to the latest Intel recommended versions (which do not include fixes forMeltdown/Spectre)
- added support for the Lenovo Thinkpad X131e Chromebook (Stout) - updated Legacy Boot (SeaBIOS) Full ROMs for Chromeboxes - switched to SHA-1 checksum verification on firmware downloads - and plenty of other things I'm forgetting ATM, and will add here when I remember them :) NOTE: on Braswell devices, the first boot after firmware flash will take a good 30 seconds or so (vs 10s or less on most other devices), due to RAM training being performed. This is normal, so don't panic when you reboot and get a black screen for what feels like forever - just wait and it will boot eventually :) As usual, the full list of changes can be found on my github repos.
RW_LEGACY SUPPORT ADDED FOR ALL APOLLOLAKE DEVICES! (AND THEPIXELBOOK)
(2017.12.02)
Just a quick update to add RW_LEGACY support for the newly-released ApolloLake devices (see the Devices page for supported models), as well as the new Google Pixelbook. While Legacy Boot mode is now available/functional on these devices, support in the upstream Linux kernel isn't fully there yet. While basics like the keyboard and touchpad should work in most distros with a recent (4.8+) kernel, things like the touchscreen, media keys, and suspend/resume are stilla WIP.
As usual, best compatibility is likely to be found with GalliumOS, which has issue trackers set up for both ApolloLakeand
Kabylake
platforms.
While this is a quick/small update, work continues on UEFI/Full ROM firmware for both the Braswell and Skylake platforms. We're hopeful for a holiday release :) SUPPORT ADDED FOR LINK AND LUMPY(2017.07.14)
Long overdue, we now have support for Link (Google Chromebook Pixel 2013) and Lumpy (Samung Chromebook Series 5 550). Link, having a Google Chrome-EC, also gets an updated EC firmware which improves PS2 compliance and makes it functional without any additional drivers. There's also a handful of fixes for other devices scattered in, including one for the internal microphone on Falco (HP Chromebook 14) which had been lingering on the issues list for far too long. Lastly, we've done a bunch of code cleanup, and updated all devices to the latest coreboot/Tianocore upstream sources. As usual, the full list of changes can be found on my github repos.
NEW SPLASH SCREEN ADDED; BAYTRAIL AUDIO ON WINDOWS FIXED(2017.04.09)
Gone is the brief "Start Boot Option" text - the UEFI firmware now has a proper splash screen, with the coreboot logo (a European brown hare) and a printout of the amount of system RAM. The splash will show for ~1s, during which time you can press ESC to enter the UEFI firmwaresettings.
Baytrail devices also got a handful of fixes, most notably working audio under Windows when using coolstar's Maxim audio driver. This release also fixes an issue where selecting the eMMC from the boot menu would fail to boot Windows, and an issue with going into sleep on devices with a light sensor (which isn't used/supported). The Firmware Utility Script has undergone some improvements for flashing Full ROM firmware: it now better informs users when flashing will break compatibility with the currently installed OS, provides info on any required post-install steps, removed the option of flashing Legacy Full ROM firmware for all Chromebooks, and provides stronger encouragement to use the UEFI firmware on Chromeboxes where Legacy firmware is still available. Lastly, we've done a bunch of code cleanup, updated to the latest coreboot/Tianocore upstream sources, and retested everything under the Windows 10 Creator's Update (1703). As usual, the full list of changes can be found on my github repos.
UEFI HEADLESS BOOTING IS FIXED! CTRL-ALT-DEL ADDED!(2017.03.19)
While the headless boot fix mainly affects Chromebox users, it also prevents the UEFI firmware from hanging when the display init either fails or takes longer than expected/allowed. We've also updated the EC firmware on Haswell/Broadwell/Baytrail Chromebooks to send CTRL-ALT-DEL when the left CTRL and left ALT keys are held, and backspace is pressed. This mainly benefits Windows users but is useful in many other cases as well. The EC firmware has also a fix where the keyboard could fail to init properly if the keys were pressed (read: walked on by your cat) in between the firmware loaded and Linux re-initializing the keyboard. Lastly, Baytrail devices got some tweaks to the audio device which should allow them to have functional audio under Windows once coolstar finishes writing the codec driver. After this update, Windows will identify and load the driver for the SST audio device, and will show the volume control on the taskbar, but sound will not yet be functional. Keep an eye out on /r/chrultrabook for the driver release announcement (and please don't ask when it will be done / if you can help test - we've got everything we need ATM). Linux users are unaffected; audio is working for Baytrail in GalliumOS, and should work in other distros once kernel 4.11 is released, assuming the distro's kernel is configured to load the driver. As usual, the full list of changes can be found on my github repos.
EC FIRMWARE UPDATES FOR EVERYONE! (ALMOST)(2017.02.21)
The big feature in this release is that we're now able to update not only the main system firmware, but also the firmware for the embedded controller (EC) on Chromebooks as well. This has a few immediatebenefits:
- The keyboard is now fully PS2 compliant, and should work OOTB without any special drivers on all OSes. Special drivers are still needed for the correct mapping of the media keys, but you no longer have to use an external keyboard to install Windows (eg). - Resume from suspend via opening the lid is now fixed on all Haswell Chromebooks (Falco, Leon, Peppy, and Wolf) - Adjusted the fan speeds on the HP Chromebook 14 G1 (Falco), which was a universal complaint from all owners While updating the EC firmware is something that's usually fraught with dragons, on Chromebooks it's easy and safe: the EC maintains two copies of the firmware - a read-only (RO) copy and a read-write (RW) copy. When the system boots, the main firmware checks that the version of the EC RW firmware matches what's expected; if there's a mismatch, the RW copy gets updated. Upon successful update, or if no update is needed, the EC is rebooted using the RW firwmare and system boot proceeds as normal. If there's a problem updating, then the EC uses the RO firmware and an update attempt is made again on the next reboot. All of this is completely transparent to the end user, and adds less than 0.1s to the boot time. These EC firmware updates are included for all Haswell, Broadwell, and Baytrail Chromebooks running the UEFI Full ROM firmware. Older SandyBridge/IvyBridge devices don't use Google's ChromeEC, so can't be updated. Chromeboxes don't use an EC, so this doesn't apply to them. There's also a handful of other fixes and improvements too: - UEFI firmware added for the HP Pavilion Chromebook 14 (butterfly) - Fixed an issue related to external display detection on Chromeboxes - Fixed a power-management related issue with the PCH (platform controller hub) on Broadwell devices, which should translate into slightly better battery life As usual, the full list of changes can be found on my github repo.
TWO STEPS FORWARD, ONE STEP BACK?(2017.01.27)
Despite our best efforts, it seems a few gremlins snuck into the 01/23 release, so pushing a new round of UEFI firmware to address the issuesthat popped up:
- fixed trackpad functionality on Banjo - fixed Windows Display output on Gandolf, Guado, Rikku, and Tidus - fixed touchscreen functionality on Clapper and Glimmer - increased graphics memory pre-allocation (DVMT) on Baytrail devicesfrom 64 to 128MB
- reverted Legacy Boot (SeaBIOS) Full ROM firmware to previous release to fix backlight control issue - removed Legacy Boot (SeaBIOS) Full ROM firmware for Baytrail devices, as it wasn't thoroughly tested, and really isn't necessary since BYT devices have the BOOT_STUB firmware option As usual, the full list of changes (and source code) can be found onmy github repo
.
HOLY BAYTRAIL, BATMAN!(2017.01.23)
It's been a long time coming, but we finally have proper support for all 15(!) Baytrail devices (Celeron N2xxx). All BYT devices now have UEFI Full ROM firmware, fully capable of running Windows** and Linux; Legacy (SeaBIOS) Full ROMs are also available, but most users will be better served by the UEFI firmware. Additionally, other devices received a handful of fixes andimprovements too:
- fixed VGA output on UEFI firmware for Samsung Series 3 Chromebox (STUMPY); DisplayPort still non-functional as the primary/only outputhowever
- fixed intermittent issue with UEFI pre-boot graphics init on some devices with 1080p (or higher) displays - devices with a Google Embedded Controller (EC) now boot with their updated RW firmware (vs the base RO firmware) active As usual, the full list of changes can be found on my github repo.
** Built-in audio (including the headphone jack) will not work on Baytrail devices due to lack of audio drivers from the manufacturer; this is not something we're able to hack ourselves unfortunately. HDMI audio is functional, and Bluetooth/USB audio devices will work withoutissue as well.
SO LONG, SEABIOS!
(2016.12.14)
After months of hard work, we've finally managed to extricate SeaBIOS from the UEFI firmware -- now they directly boot into the UEFI payload (Tianocore) without using SeaBIOS as a shim. This paves the way for many future improvements, like functional NVRAM for saving the UEFI settings/boot paths (hopefully). In the meantime, this release has a handful of notable fixes andimprovements:
- boot times should be another 2-3s quicker - the coreboot logo has been added to the Windows boot screen - CPU type text justification fixed in the firmware settings screen onthe Acer c710
- Virtualization (vmx / VT-x) is fixed for the Acer c710 - the Intel Management Engine (ME) has been correctly re-enabled for the Acer c710 (which should fix long resume from sleep times) - fixed reporting of battery details (make/model/serial #) forChromebooks
As usual, the full list of changes can be found on my github repo.
ANOTHER ROUND OF UEFI UPDATES(2016.12.08)
This UEFI release adds pre-OS HDMI video output for Chromebooks; previously, on many models, the firmware settings and boot manager screens were visible only on the internal display - now they should be visible on both internal and external displays. Though external displays do take a lot longer to turn on/init, so there may be a 2-3s delay defore output is visible. There are also fixes for the power LED on the Dell Chromebox 3010 (Tricky) and for the trackpad on the Dell Chromebook 13 7310 (Lulu) which previously required a kernel command-line parameter to work around a fix for the Windows trackpad driver - it should work OOTB now for all Linux distros outside of ChromiumOS/CloudReady, which doesn't include the correct driver/config (still). Also, the master display clock on Broadwell devices has been bumped back up (now that the HDMI audio issue has been resolved), which should enable 2160p60 (4K 60Hz) output on capable devices (Chromeboxes, Pixel2). MORE UEFI IMPROVEMENTS, NEW ROMS FOR HASWELL CHROMEBOXES(2016.11.27)
This UEFI release fixes some issues with backlight control for Haswell Chromebooks under Linux and OS X/MacOS, adds support for 3 new Haswell Chromebox models (Acer/McCloud, Dell/Tricky, and HP/Zako) which were previously handled by the firmware for the Asus model (Panther). Handling them separately allows for better control of the power LEDs (and their blinking state on McCloud/Tricky) and fan speeds optimizedfor each model.
Additionally, the UEFI firmware now has the option to select either internal (SSD) or external (USB/SD) storage as the preferred boot target at time of install; previously it was fixed at external. Regardless of which option is selected, the boot menu is available by hitting ESC (or any key other than Enter) while the progress bar is visible at the bottom of the screen, then selecting 'Boot Manager' from the UEFI firmware setup menu. Once we have the ability to save the firmware settings, choosing the boot priority at install time will no longer be necessary. HUGE IMPROVEMENTS IN UEFI FIRMWARE! (FOR ALL DEVICES WITH UEFIFIRMWARE)
(2016.11.17)
Thanks in no small part to the efforts of coolstar , we are now able to say goodbye to the VGA BIOS in our UEFI firmware, relying excusively on the EFI GOP driver. This fixes a whole slew of audio/video related problems, including HDMI audio under Windows (now works OOTB for all devices), Windows installer video mode/output (particularly on the SandyBridge c710), and many others. Additionally, there's a handful of other fixes as well: - Haswell Chromeboxes: fix fan spinup under Windows - All Haswell devices: increase default video memory (DVMT) from 32MB to 96MB (putting it back on par with Broadwell) - All Broadwell devices: fix HDMI audio speedup under Windows using previous 'intel_audio_enable.exe' method As usual, the full list of changes can be found on my github repo.
FULL ROM SUPPORT ADDED FOR MONROE(2016.11.07)
A device-specific Full ROM has been added for Monroe, the Haswell-based LG Chromebase. Previously, Monroe was covered under the Haswell Chromebox umbrella, but it was brought to my attention that there are enough differences to warant a separate build. Additionally, a whole slew of fixes are included for other devices aswell:
- Parrot: use correct interrupt values for SandyBridge/IvyBridge variants under Linux - Parrot: include SD/MMC drivers to support booting from SD under UEFI - Panther: add USB ACPI port definitions to improve Windows, OS Xsupport
- Haswell/Broadwell Chromeboxes: increase timeout to enter UEFI setupat boot
- a few other minor fixes that escape me Edit: also updated Stumpy (Samsung Series 3 Chromebox) to automatically power on after AC power lost, and to fix the power LED. FIX FOR SANDYBRIDGE-BASED ACER C710 (PARROT)(2016.10.20)
Shortly after the release of the Full ROM firmware for the Acer C710 (Parrot), we discovered a bug affecting the amount of RAM reported by Linux/Windows on the SandyBridge (Celeron 847U) models; it also caused some significant performance issues as well. This issue has now been corrected. IvyBridge (Celeron 1007U) models were not affected. Also, the Firmware Utility Script main menu got a minor facelift, improving readability and now fitting properly inside a standard 80x25terminal.
FULL ROM SUPPORT ADDED FOR ACER C710 (PARROT)(2016.10.15)
After several weeks of testing and debugging, support for the Acer C710 (Parrot) is finally ready. Full ROM firmware (both UEFI and Legacy boot) is available for both the SandyBridge (Celeron 847U) and IvyBridge (Celeron 1007U) variants, which supports booting both Linux and Windows (Win7 and above). There are a few outstanding issues with suspend/resume, but overall everything functions as it should. A big thanks to ReddestDream and coolstar for their efforts. As usual, the best place to get support is on the chrultrabooksubreddit .
Also, the Full ROMs (both Legacy and UEFI) for Broadwell devices have been updated with a fix for the ACPI backlight controls under Linux; the workaround of using an xorg.conf file to blacklist the ACPI controls is no longer needed. AUDIO FIX FOR AURON DEVICES(2016.09.29)
Just a quick update to the Full ROMs for Auron devices (Auron_Paine and Auron_Yuna - Acer c740/c910 respectively) which fixes an audio output issue. The 09/22 firmware introduced a bug which broke the headphone jack output, this is simply a bug fix release for that. MORE FULL ROM FIRMWARE UPDATES(2016.09.22)
Today's Full ROM updates feature improved support for ACPI S4/hibernate low-power mode. Previously, devices would enter S4/hibernate but still be using the same amout of power as S3/suspend, leading to excessive power (battery) drain. Additionally, many devices would fail to wake (consistently, or at all) when opening the lid while hibernated, requiring the use of the power button to wake. Both of those issues have been fixed for the Full ROM firmware for allsupported devices*.
* Mostly - some Acer C720 (PEPPY) users have reported lid wake not working for S4 or S5 still - issue is under investigation. And while I previously said the last update would be the final Full ROM for any supported Baytrail devices, I didn't want to leave them out of this update, so THIS will be the final one. For reals. FULL ROM FIRMWARE UPDATE FOR HSW/BDW(2016.09.18)
Today's Full ROM updates feature an updated VGA BIOS (VBIOS) for Haswell Chromebooks, which speeds up initial power on a bit (by not setting a video mode that's never used), as well as a Wifi fix for all devices using an Intel wifi card (the issue seemed to not affect most users, but there's no harm in the fix). It's also the last set of Full ROMs I'll be offering for Baytrail Chromebooks, since the current Full ROMs 1) don't offer any real advantage over the BOOT_STUB firmware, 2) introduce some minor issues, like not always powering on when the lid opens, 3) only cover a handful of Baytrail devices, and 4) never fulfilled their original goal of making the devices usable under Windows, due to lack of working trackpad/touchscreen/sound. I'll keep the code around in a separate branch in case anyone wants to build their own from my sources, but it won't be updated and I won't be distributing new builds after today (unless something happens to change the conditionsabove).
NEW SCRIPT FUNCTIONS: REMOVE/RESTORE CHROMEOS BITMAPS(2016.09.15)
Lots of people use ChromeOS in Developer Mode, and the one thing they can all agree on is that the bright white Developer Mode boot screen is a retina-searing travesty. To that end, I've added a new script function which removes the ChromeOS bitmap images used for the Developer Mode and Recovery Mode splash screens, which leaves your device with a simple and pleasant black screen with white text:becomes
If you want to restore the stock bitmaps, the Firmware Utility Script has you covered there too :) Edit: Sadly this doesn't work on Skylake Chromebooks, as they use a different method to render these bitmap images, and removing them from the firmware results in a solid white screen, not a solid black one. LEGACY AND UEFI FULL ROMS ADDED FOR ALL HASWELL/BROADWELL DEVICES(2016.09.06)
Haswell/Broadwell device owners now have the option of flashing a Full ROM with either Legacy Boot (SeaBIOS) or UEFI Boot (Tianocore). UEFI booting is needed/optimal for users who want to run Windows, OS X, or a multi-boot setup; Most Linux users will need to install a boot manager such as rEFInd since the UEFI firmware currently only looks for the default EFI boot path (EFI\BOOT\BOOTX64.EFI). GalliumOS users will want to stick with the Legacy Boot option, since GalliumOS isn't UEFI compatible yet. All Full ROMs feature improvements to the SMBIOS tables, which fixes the amount of RAM reported to the system (mainly affected Windows and OS X). Haswell/Broadwell Full ROMs also get fixes to the onboard audio, which improve the headphone jack detection/functionality, and fix the subsystem ID reported so that Windows will automatically install the correct drivers via Windows Update. Baytrail Full ROMs have been updated with a fix for battery status under Windows. SKYLAKE RW_LEGACY SUPPORT ADDED(2016.08.05)
RW_LEGACY firmware support has been added for current Skylake-based Chromebooks (CHELL, LARS, SENTRY). While these models may have included basic RW_LEGACY functionality stock, this improved version features proper video initialization in Legacy Boot Mode, resulting in the correct screen resolution being set (ie, text is more readable) and screen redraws are significantly faster (ie, instant). And, like all firmware updates offered via the Firmware Utility Script, it allows the user to set their preferred boot device in Legacy Boot Mode (either internal storage or external USB/SD). Additionally, a Full ROM firmware was added for the 2014 Dell Chromebook 11 (CANDY), and several improvements were made to the script related to eMMC controller address support for Baytraildevices.
(PRELIMINARY) BRASWELL SUPPORT ADDED(2016.07.30)
RW_LEGACY firmware support has been added for current Braswell-based Chromebooks (Celeron N3xxx models: CELES, CYAN, EDGAR, REKS, TERRA, ULTIMA). I don't have confirmation of the eMMC and SD card controller addresses for all of them (only CYAN and EDGAR so far), so eMMC/SD might not show up in the SeaBIOS boot menu for some models. In that case, drop me a line and I'll give you instructions to retrieve the firmware boot log, which will tell me the correct addresses. Unfortunately, Linux support for Braswell is still pretty spotty. I was able to boot/install GalliumOS, but the keyboard, sound, touchscreen, and a few other things didn't work yet. Wifi/BT worked fine, so an external keyboard was all I needed for it to be usable. UPDATE: another Braswell user tested Fedora 24 (Gnome, Cinnamon, MATE) and reported that the keyboard works properly, but not the trackpad (which isn't surprising, since GalliumOS uses a custom/ported ChromeOS driver for it); Ubuntu 16.04 wouldn't boot, but Mint 18 did (albeing without a working keyboard/trackpad). Also, the syslinux bootloader used for installing LibreELEC in dual-boot and external USB configurations has been updated, as well as the flashrom binary used on non-ChromeOS/ChromiumOS systems. Both were updated to add Braswell support, and didn't appear problematic on older platforms in my (albeit limited) testing here. BAYTRAIL WINDOWS UPDATE(2016.07.24)
All Baytrail Full ROMs have been updated to fix the detection/operation of emmc/SD storage controllers by Windows, so you can now install Windows onto the internal emmc (or at least access it if booting from external media). Unfortunately, the I2C bus functionality is not yet working, so an external mouse is required since the trackpad will be non-functional. Baytrail Full ROMs are currently available for ENGUARDE, GLIMMER, GNAWTY, NINJA, QUAWKS, and SWANKY. If you'd like support for your Baytrail Chromebook added, justlet me know.
Also, fixed an issue with the Firmware Utility Script's listing of available USB devices for firmware backup on ChromeOS devices with emmc internal storage (vs SSD). Previously, the first USB device wasn't being displayed as the script assumed it was the internal ssd (and therefore excluded it). A FEW BUG FIXES, PLUS CLOUDREADY SUPPORT(2016.07.20)
As is usual with changes of this magnitude, a small bug or two emerged (related to the Stock Firmware Restore functionality of the Firmware Utility Script) and were promptly fixed. Also, support has been addded for Neverware's Cloudready OS, a ChromiumOS derivative. It uses a slightly different partition layout than ChromeOS/ChromiumOS, and the scripts were not prepared for it. Clouldready is handled the same as ChromiumOS - that is, ChromeOS-specific functions are still lockedout/not available.
NEW SITE, NEW FIRMWARE, NEW SCRIPT FUNCTIONS!(2016.07.19)
Along with the revamped website, all firmware files have been rebuilt and updated using the latest sources. Plus, Full ROM firmware has been added for several BayTrail Chromebooks (ENGUARDE, GLIMMER, GNAWTY, and SWANKY) with more to come in the near future. Additionally, the Firmware Utility Script's RESTORE STOCK FIRMWARE function has been updated to support all Haswell, Broadwell, and Baytrail ChromeOS devices - even if you don't have a backup file available. The RESTORE STOCK BOOT_STUB function has likewise been updated to support all Baytrail devices, even those flashed with BOOT_STUB firmware from another party. Check out the Firmware Utility Script info page for all the details.Details
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0