Posted on 08/03/2017 by Robert Foss
Before being able to write firmware data to any production Chromebook device, the Write-Protect screw has to be removed.
This post will look specifically at removing the WP screw from a Chell (HP Chromebook 13 G1) device, and verifying that it has been successfully removed.
To actually flash firmware to Chromebook machines, a device called a Servo is needed. While these devices aren't available publicly, they can be produced freely or possibly requested from Google if you are contributing code to the ChromiumOS project.
So this is what the WP screw looks like on a Chell Chromebook. This may or may not be what you will find in other devices. But if you take a close look, you will notice that the copper pad that the the screw attaches against is split into parts that are bridged by a screw being inserted.
# Go to your ChromiumOS checkout cd /opt/chromiumos # Enter dev environment cros_sdk # Set device variable export BOARD=chell # Connect to Chromebook using a Servo device sudo servod -b $BOARD & # Disable WP # This step may vary depending on the hardware of your actual Chromebook dut-control fw_wp:off sudo /usr/sbin/flashrom -p ft2232_spi:type=servo-v2 --wp-disable sudo /usr/sbin/flashrom -p ec --wp-disable
This post has been a part of work undertaken by my employer Collabora.
Panfrost, a project that delivers an open source implementation of a driver for the newest versions of the Mali family of GPUs, now includes…
Released a few months ago, the Google Pixel 3 is the first Android phone running with the mainline graphics stack. A feat that was deemed…
In an ideal world, everyone would implicitly understand that it just makes good business sense to upstream some of the modifications made…
How can we measure the comprehensiveness of a test suite? Code coverage is the standard metric used in the industry and makes intuitive…
A real-world use case of eBPF tracing to understand file access patterns in the Linux kernel and optimize large applications.
Did you know you could register your own PC, or a spare laptop collecting dust in a drawer, to get instant CI going on GitLab? Not only…