diff --git a/_drafts/2020-12-3-GalliumOS.md b/_drafts/2020-12-3-GalliumOS.md
index 7b2912c..e695a6e 100644
--- a/_drafts/2020-12-3-GalliumOS.md
+++ b/_drafts/2020-12-3-GalliumOS.md
@@ -24,16 +24,46 @@ To enable developer mode, simply press <kbd>Esc</kbd> + <kbd>Refresh</kbd> + <kb
 
 ## Write protection
 
-This step will void your device's warranty.
+This step will void your device's warranty. Chromebooks are able to handle anything you throw at them. Even if you were to delete important system files to the point the device can no longer boot, hopping in to recovery mode can reset the device to a working state. This works via ChromeOS's write protect mechanism. All important files are protected by hardware-enforced write protection. Since the process of loading a new operating system onto the device involves overwriting important system files (like the BIOS), we must physically disable write protection.
+
+Luckily, on the Acer R11, this process is very simple. Firstly, unscrew the laptop's bottom plate to expose the motherboard (some screws are hidden under rubber feet). With the backplate off, you will find a screw that looks like this:
+
+![R11 write protect screw](/assets/images/arcer_r11_screw.jpg)
+
+The screw is hard to miss, it is beside the WIFI card, an has an arrow pointing to it. Simply remove it, and put the laptop back together. You now have a fully unlocked device.
 
 ## Flashing a custom bootloader
 
+[Mr Chromebox](https://mrchromebox.tech), a well known person in the world of Chromebook modification, provides and maintains a very easy to use shell script that handles bootloader modifications automatically. To use this tool, open up the ChromeOS terminal (<kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>-></kbd>), log in with the username `chronos` (you must already be logged in to your personal Google account. This will not work from the login screen), and run:
+
+```sh
+crossystem dev_boot_usb=1 dev_boot_legacy=1
+cd; curl -LO mrchromebox.tech/firmware-util.sh
+sudo install -Dt /usr/local/bin -m 755 firmware-util.sh
+sudo firmware-util.sh
+```
+
+This will open up the `firmware-util` settings screen.
+
+![firmware-util screen](/assets/images/fwutil_cros_wp-on.png)
+
+You will want to select the `RW_LEGACY` option to load the `RW_LEGACY` / SEABIOS payload. The `UEFI` option is technically the better choice, but it will completely remove the device's ability to run ChromeOS again in the future.
+
 ### Setting fuses
 
+The `RW_LEGACY` payload only works if the laptop always has power. Once the device completely runs out of power, the boot settings are wiped from the device (not something we want). The solution is to modify the [system `gbb` fuses](https://chromium.googlesource.com/chromiumos/platform/vboot/+/master/_vboot_reference/firmware/include/gbb_header.h). This sounds complicated (and it is), but Mr Chromebox comes to the rescue again with the `GBB Flags` option in his script. *After* the `RW_LEGACY` payload has been configured, run his script again, and select `GBB Flags`.
+
 ## Installing GalliumOS
 
+On another computer, [download GalliumOS](https://galliumos.org/download) (make sure to select the `Braswell` option), and [create a bootable USB](https://wiki.galliumos.org/Installing/Creating_Bootable_USB). Plug this USB into the Chromebook, reboot, and press <kbd>Ctrl</kbd> + <kbd>L</kbd> as the warning screen pops up. This will begin the GalliumOS setup process (which is identical to that of Ubuntu).
+
 ### Enabling verbose boot
 
+It is nice to know what is happening when the device is booting. To disable the boot animation and replace it with the boot log, edit `/etc/default/grub`, and replace both the `quiet` and `splash` arguments with `noplymouth` in the `GRUB_CMDLINE_LINUX_DEFAULT` options. Next, run the following, then reboot:
+
+```sh
+sudo update-grub
+```
 
 <!--
 https://imgur.com/a/GuyYz
diff --git a/assets/images/arcer_r11_screw.jpg b/assets/images/arcer_r11_screw.jpg
new file mode 100644
index 0000000..a3957e4
Binary files /dev/null and b/assets/images/arcer_r11_screw.jpg differ
diff --git a/assets/images/fwutil_cros_wp-on.png b/assets/images/fwutil_cros_wp-on.png
new file mode 100644
index 0000000..f3ada20
Binary files /dev/null and b/assets/images/fwutil_cros_wp-on.png differ