How to root your Boox e-reader with Magisk: the complete guide

Rooting a Boox device gives you full control over the underlying Android system. Unlike a Kindle or Kobo, Boox devices run a mostly-stock Android build (typically Android 11 or 12, depending on model), which means standard Android rooting techniques apply. Here’s the complete walkthrough using Magisk — the systemless root framework that preserves SafetyNet and OTA compatibility as much as possible.

What you’ll need

A Boox device with an unlocked bootloader (most Boox models ship bootloader-unlocked — check by running adb reboot bootloader; if you see the fastboot screen, you’re unlocked)
A computer with ADB and fastboot installed (platform-tools from Google)
The exact firmware ZIP for your device model and current version (download from Boox’s firmware page — you must match the version currently installed)
The Magisk APK (download the latest stable from the official GitHub)

Step 1: Get the stock boot image

Extract the firmware ZIP you downloaded. Inside, you’ll find an update.zip — extract that too. Look for boot.img. This is the stock boot partition image for your current firmware version. If the firmware is packaged as a .upx file (Boox’s encrypted format), you’ll need the Boox Decryption Tool to unpack it. Place boot.img on your Boox device’s internal storage.

Step 2: Patch the boot image with Magisk

Install the Magisk APK on your Boox device (sideload via adb install Magisk-vXX.X.apk or transfer the APK over USB and install from the file manager). Open Magisk, tap “Install” next to “Magisk” at the top, select “Select and Patch a File”, and choose the boot.img you transferred. Magisk will process it and output a patched image — typically magisk_patched_XXXXX.img in the Downloads folder. Copy this file back to your computer.

Step 3: Flash the patched boot image via fastboot

Reboot your Boox into fastboot mode:

adb reboot bootloader

Once in fastboot (you’ll see the Boox logo with “fastboot mode” text), flash the patched boot image:

fastboot flash boot magisk_patched_XXXXX.img
fastboot reboot

Warning: Some Boox models use an A/B partition scheme. Check with fastboot getvar current-slot to see if you on slot a or b, and append _a or _b to the partition name: fastboot flash boot_a magisk_patched.img.

After reboot, open Magisk. The app should show “Installed” with the version number. You’re rooted.

What you can do with root

Once rooted, the possibilities expand dramatically:

Remove Boox bloatware systemlessly

Use the De-Bloater Magisk module (install via Magisk’s Modules tab) or manually debloat with pm disable commands. Common candidates on Boox devices include the Chinese app store, the preloaded browser, and the Boox “Push” notification service — all of which run in the background and drain battery. You can also install App Manager from F-Droid to freeze or uninstall system apps with a GUI, much cleaner for beginners.

System-wide ad blocking with AdAway

Install AdAway (available on F-Droid) and enable systemless hosts in Magisk settings. AdAway rewrites the system hosts file to block ad and tracker domains across every app, including the built-in NeoBrowser and any sideloaded reading apps. On e-ink, where every network request costs battery, this is a meaningful power saving.

CPU overclocking and governor tuning

Boox devices throttle the CPU aggressively to preserve battery. With root, you can install Kernel Adiutor or Franco Kernel Manager to switch from the conservative powersave governor to ondemand or interactive, reducing app-launch latency by 30–50%. Don’t go overboard — sustained high clocks on a passively cooled e-reader will generate heat and drain the battery quickly. A modest overclock (1.6 GHz → 1.8 GHz on a Snapdragon 662, for example) is the sweet spot for snappier PDF zooming without thermal issues.

Tasker for reading-mode automation

Install Tasker and grant it root access. Automate things like: disable Wi-Fi and Bluetooth when the reading app opens, switch to inverted screen mode at night (if you have a Boox with BSR), or launch a specific app when the magnetic sleep cover is opened (via the hall sensor trigger accessible as a system intent). Root lets Tasker toggle aeroplane mode, kill processes, and adjust system animations — all without the janky workarounds the non-root version requires.

The risks

OTA updates will unroot your device. When a firmware update arrives, you’ll need to re-extract the new boot image, patch it, and flash again. If you take an OTA without restoring the stock boot image first, the update may fail or soft-brick. Use Magisk’s “Uninstall → Restore Images” before applying any OTA, then re-patch and re-flash the new boot image after the update completes.
Warranty is technically void. Boox doesn’t explicitly lock bootloaders or block root, but their support may refuse service if they identify a rooted device. That said, Boox hardware issues (screen, battery, USB port) are almost never root-related, and you can always flash the stock firmware to return to a clean state before sending it in.
A bad boot image flash can soft-brick the device. If you flash the wrong boot image, the device may boot-loop. Fix this by booting back into fastboot (adb won’t work; use the hardware key combo: hold power + volume down for 15 seconds) and flashing the correct stock boot.img. Keep the stock image backed up on your computer — you’ll thank yourself later.
Rooted devices can’t run banking apps or certain DRM services without additional Magisk modules (Universal SafetyNet Fix, MagiskHide Props Config). On an e-reader this is rarely an issue, but if you use the Kindle or Kobo Android apps with DRM’d books, they may refuse to open. Magisk’s built-in Zygisk + DenyList (configure in Magisk settings) handles this for most reading apps — add the app to the DenyList and enable “Enforce DenyList.”

Rooting a Boox is a medium-risk, high-reward project. If you’re comfortable with the command line and have an hour to spare, the payoff — a cleaner, faster, more private reading device — is well worth it.