MrChromebox.techMrChromebox.tech
Donate via Paypal
Give via Patreon
Get Help on the Forums
Github Repos
Donate via Paypal
Give via Patreon
Get Help on the Forums
Github Repos
  • News & Updates
  • Getting Started
  • FAQ
  • Supported Devices
  • Firmware Utility Script
  • ChromeOS Boot Modes
    • Normal Mode
    • Recovery Mode
    • Developer Mode
    • Legacy Boot Mode (aka AltFw)
  • Firmware 101
    • Firmware Types
    • Firmware Write Protect
      • Disabling FW WP
    • Flashing Firmware
    • Flashing Manually
    • Updating Firmware
    • Booting Your OS
  • Known Issues
  • Help and Support
    • Debugging / Getting Help
    • Compiling Your Own Firmware
    • Unbricking
      • With a ch341a USB Programmer
      • With a Suzy-Q Cable
  • Reverting to ChromeOS
    • Flashing Stock Firmware
    • Making a Recovery USB
    • Booting the Recovery USB

Help & Support

First and foremost, read all of the documentation here on this site (especially the FAQ), as well as the chrultrabook docs

Getting your issue resolved is largely a function of asking for help properly, and in the correct place:

  • For the quickest help with all issues related to flashing firmware, OS install/drivers, please use the chrultrabook forums

  • Issues running the Firmware Utility Script can be reported on the scripts issue tracker

  • Firmware bugs (NOT OS issues) can be reported on the firmware issue tracker

  • Website issues can be reported on the website issue tracker

  • (Archival info) Chromebox E-Z Setup Script thread on Kodi forums

  • (Archival info) Kodi Chromebox wiki page

Firmware/Device Support Requests

The firmware updates available via this site are designed to meet the needs of the broadest possible user base, for devices on which I'm able to test (or at least, have a high confidence that it will work). If there's a feature you'd like to see implemented, I'm happy to take requests if it's something that's fairly easy to implement / not determental to the wider user base. Adding support for new devices (eg, Braswell-based Chromebooks) often requires actually having hardware to debug, so if one is able to loan/donate hardware for development purposes, that will definitely speed things along.

Firmware related issues and feature requests are best handled via the firmware issue tracker.

Commerical entities looking for a custom firmware solution for their ChromeOS device(s) should just email me directly

Unbricking Service

If you've taken a wrong turn somehow and, despite the safeguards in the Firmware Utility Script, ended up with a bricked device (whether from my firmware or someone else's), and are unable to recover the device yourself, MrChromebox offers a low-cost unbricking service to anyone in the USA (or anyone who cares to cover shipping to/from really). Simply shoot me an email and we can go from there. With any luck, it might not even be bricked 😃

If your device is bricked, many times it is fairly easy to recover - see Unbricking

Last Updated:: 7/22/24, 3:18 AM
Prev
Known Issues
Next
Reverting to ChromeOS