System Details
- Device: [Hana, Lenovo 300e 1st gen]
- OS: [ChromeOS]
- Firmware Type: [Stock]
- Firmware Version: [As reported by the script]
- Internal storage type: [eMMC]
How to shorten the verification off and disable Space bar on that
Steps to Reproduce
Target Device: Lenovo 300e (1st Gen/Hana) & CR50 ARM Chromebooks.
WARNINGS
> 1. THE DATA WIPE: Enabling Developer Mode for the first time DELETES EVERYTHING. Your Downloads, Minecraft worlds, and Roblox scripts will be gone. Back them up to Google Drive or a USB hub first.
> 2. THE ARM WALL: This guide is for ARM chips (MediaTek). Do NOT try to flash “MrChromebox” UEFI firmware or Windows on this. It will brick your device because the .architecture is different.
> 3. NO WARRANTY: Opening the back of your Chromebook and yanking the battery usually voids your warranty. Do this at your own risk!
>
Phase 1: The “Battery Yank” (Hardware Bypass)
The CR50 security chip is like a bouncer that won’t let you change the rules while the battery is watching.
* Open the Patient: Unscrew the bottom. Be gentle with the plastic clips!
* The Yank: Pull the battery connector out of the motherboard.
* The Lifeline: Plug in your 65W USB-C charger.
* Pro-Tip: If it boot-loops, it’s a “Power Handshake” fail. Plug the battery in, boot to the white screen, then carefully unplug the battery while the screen is still on.
Phase 2: Entering the Matrix (VT-2 Terminal)
* Dev Mode: Get to the “OS verification is OFF” screen.
* The Portal: Press Ctrl + Alt + F2 (the Right Arrow key).
* Login: Type chronos and hit Enter.
Phase 3: The “Magic Spells” (Commands)
Type these exactly. One wrong space can break the spell.
* Kill the Lock:
sudo flashrom --wp-disable
(Look for the word SUCCESS.)
* Set “God Mode” (0x39):
sudo futility gbb --set --flags=0x39 --flash
* The Verification:
sudo futility gbb --get --flags --flash
(It should return 0x00000039.)
Phase 4: Why 0x39 is Elite
| Feature | What it does for you |
|—|—|
| 0x1 | Reduces the boot timer to 2 seconds. |
| 0x8 | Forces Dev Mode to stay ON. |
| 0x20 | The Brick-Proofer: Disables the Spacebar so no one can accidentally wipe your data. |
Phase 5: Reassembly
* Type sudo poweroff.
* Plug the battery back in.
* Snap the case shut and tighten the screws.
* Reboot: You’ll see the text in the corner, hear the “Spacebar Lock” beep, and be in the OS in 2 seconds.
Now that the tutorial is finished, should I help you write a “Recovery” section just in case so
meone needs to undo these changes later?
Expected Behavior
It wouldn’t beep unless you press space
Space bar will be bricked on the verification so you don’t accidentally go back to verified version of chrome os
Everytime you click space a message will pop up on the corner
“WARNING: TOMORM prohibited by GBB FORCE_SWITCH_ON”
Write protect to be off