# Operation: Liberation — Reclaiming the HP Chromebook 14 G7 **Author:** Nester | Church of Malware Clergy Member and Contributor The modern Chromebook was never designed to belong to you. Locked firmware. Restricted bootloaders. Forced operating systems. A machine sold as hardware freedom while silently enforcing software obedience. The HP Chromebook 14 G7 is no exception. Beneath its clean interface and "secure" environment lies a device intentionally engineered to prevent the owner from exercising complete control over their own system. This document details the complete process of breaking those restrictions and reclaiming the hardware. **Not through exploits.** **Not through malware.** **Not through illegal intrusion.** But by understanding the machine better than the corporations who attempted to lock it down. --- ## Phase 1 — Entering Developer Mode The first barrier is ChromeOS verification. By default, the Chromebook enforces Google's trusted boot chain, preventing unsigned operating systems and firmware modifications. To move beyond these restrictions, Developer Mode must be enabled. **Initiating Recovery** 1. Power the device completely off. 2. Execute the following key combination: `ESC + Refresh` 3. Tap the **Power Button** The machine will boot into the ChromeOS recovery environment. At the recovery screen: Press `CTRL + D` You will then be prompted to disable OS verification. Confirm with: `ENTER` > **WARNING:** At this point, the Chromebook will wipe itself completely. This is intentional. ChromeOS assumes anyone attempting to gain deeper control over the machine is a threat. > **Back up your data before continuing.** The transition into Developer Mode may take several minutes. Once completed, every boot will display a warning screen stating that OS verification is disabled. **Good.** --- ## Phase 2 — Physical Access Software restrictions alone are never enough. Real control requires hardware access. Power the Chromebook down completely and remove the lower chassis. **Disassembly Procedure** - Remove all bottom screws. - Carefully separate the lower shell from the frame. Expose the motherboard. At this stage, the firmware write-protection mechanism must be disabled. --- ## Phase 3 — Neutralizing Write Protection Chromebooks include hardware-level firmware protection designed to prevent BIOS modification. Different models implement this differently. There are four common methods. ### Method 1 — Write Protect Screw Some systems use a dedicated grounding screw. Remove it completely. Write protection is now disabled. ### Method 2 — Battery Isolation Certain models temporarily disable firmware protection when operating solely from external power. **Procedure:** - Disconnect the battery. - Connect the wall charger. - Boot while battery-disconnected. ### Method 3 — Hardware Switch Some boards include a physical firmware protection switch. Toggle it into the unlocked position. ### Method 4 — Jumper Bridge Method Certain HP Chromebook 14 G7 boards utilize two unpopulated firmware jumper pads. **This was the method required in my case.** The process: - Locate the two firmware write-protection pads. - Bridge the pads together. - For permanence and reliability, the pads were soldered together directly. Once bridged, firmware restrictions were neutralized. **The device now belongs to the owner again.** --- ## Phase 4 — Reassembly After write protection has been disabled: - Reinstall the lower cover. - Replace all screws. - Power the Chromebook back on. The hardware phase is complete. Now the real work begins. --- ## Phase 5 — Accessing the ChromeOS Shell Boot into ChromeOS. Open the Crosh terminal using: `CTRL + ALT + T` Crosh is ChromeOS' limited command interface. From here, escalate into the developer shell: ```bash shell ``` Press Enter. You now have direct shell access. --- ## Phase 6 — Deploying MrChromebox Firmware Utility The stock Chromebook firmware exists to enforce Google's ecosystem. To run unrestricted operating systems, the firmware itself must be replaced. Execute the following command: ```bash cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh ``` This launches the **MrChromebox Firmware Utility**. The utility provides the ability to: - Back up stock firmware - Install custom UEFI firmware - Remove Google boot restrictions - Enable standard operating system support --- ## Phase 7 — Firmware Backup **Before altering firmware, create a backup.** Insert a removable USB drive and select the firmware backup option. Store this backup securely. If recovery is ever required, this image may be the only path back. --- ## Phase 8 — Installing Custom UEFI Firmware Inside the utility, select: `Install/Update Full ROM Firmware` This operation: - Removes stock Chromebook firmware - Replaces the locked Google boot environment - Installs a full UEFI BIOS Once complete, the Chromebook behaves like a traditional computer rather than a restricted appliance. After installation finishes: Press `P` Press `ENTER` The system powers down. --- ## Phase 9 — Preparing the Operating System Create a bootable USB installer using tools such as: - Rufus - balenaEtcher - Ventoy Load your operating system of choice onto the USB drive. Common choices include: - Ubuntu - Linux Mint - Kali Linux --- ## Phase 10 — Booting From External Media Insert the bootable USB drive into the Chromebook. Power the system on. During boot, repeatedly press: `ESC` This opens the UEFI boot menu. Navigate using the arrow keys and select the USB device. Press `Enter`. The Linux installer launches. --- ## Phase 11 — Replacing ChromeOS Once the installer appears: Select: `Try or Install` Follow the installation prompts. When asked where to install: **Select the internal drive.** > This operation completely erases ChromeOS and installs the selected Linux distribution directly onto the hardware. > **No virtualization.** > **No sandbox.** > **No restrictions.** > Just a real operating system running on hardware you own. --- ## Phase 12 — Final Boot After installation completes: - Remove the USB drive. - Reboot the system. The Chromebook now boots directly into Linux. No Google verification. No ChromeOS enforcement. No locked ecosystem. Only the operating system you selected. --- ## Conclusion The HP Chromebook 14 G7 is no longer a controlled endpoint bound to a restricted environment. Through firmware modification and custom OS deployment, the machine has been transformed into a fully open Linux system capable of development, research, customization, and unrestricted computing. **The hardware was always capable.** **The limitations were artificial.**