Modding the Duokan E-Reader Pro II: Google Play, Traditional Chinese, and HyRead, Step by Step

A step-by-step guide to turning a mainland-China Duokan E-Reader Pro II (Android 11) into a reader that works in Taiwan: back up partitions, get root with Magisk, install Google Play as a system component, switch the language, swap in an e-ink-friendly launcher, and add KOReader and HyRead. Includes every command, the three traps I hit and how I got out, and a risk comparison of four approaches. A personal build log; follow it at your own risk.
Contents
- The risk, first
- What you need
- Step 1: Back up
- Step 2: Get root with Magisk
- Step 3: Install Google Play as a system component
- Step 4: Switch to Traditional Chinese
- Step 5: Use a launcher made for e-ink
- Step 6: Install reading apps
- Four approaches compared
- Tested: does HyRead open books?
- The one thing to take with you

The gentleman is not different by birth; he is simply good at making use of things.
—— Xunzi, An Exhortation to Learning (Warring States period); translation mine
This guide turns a Duokan E-Reader Pro II (Android 11) into a reader that works in Taiwan: Traditional Chinese, Google Play, a clean text-only home screen, and HyRead, the app that lets you borrow e-books with a public library card. I followed these steps on one unit in the early hours of November 22, 2026, and it took about three hours. It all works, with two conditions: back up the e-ink display partition before you touch anything, and install Google Play as a system component, because installed as a normal app its background service crashes over and over. I also tested HyRead: it opens borrowed books on the rooted device, as long as you use the current version from the Play Store.
The risk, first
Modding touches the partitions the device boots from. A mistake can leave it unable to start, and it may void the warranty. I’ve done every step below myself, but devices differ, and if something goes wrong it’s on you.
The partition to fear most is waveform. It holds how this particular e-ink panel renders grayscale and refreshes pages, calibrated per unit at the factory. A broken system can be reflashed; a broken waveform can’t be downloaded anywhere, because nobody else has yours. That’s why step one is always a backup.
What you need
adbon your computer (Google’s Platform Tools, for sending commands to the device).- Developer options on the reader (Settings → About → tap the build number repeatedly), then turn on USB debugging.
- The Magisk 31.1 APK, from its official GitHub page.
- MindTheGapps 11.0 for arm (32-bit). This device runs a 32-bit userland, so the arm64 build won’t install.
Plug in the cable and run adb devices. A serial number followed by device means you’re connected.
Step 1: Back up
- Pull all internal storage:
adb pull /sdcard/ D:/backup_sdcard/. - Back up partitions one by one, at minimum
boot_a,boot_b,vbmeta, andwaveform. - Hash each partition on the device and on the computer (a hash is a file fingerprint; change one bit and it changes). Only matching hashes count as a successful backup.
I backed up twenty partitions and checked every one before moving on. I checked waveform twice.
Step 2: Get root with Magisk
- Find the active boot slot:
adb shell getprop ro.boot.slot_suffix. Mine returned_b, soboot_bis the one to patch. - Push the
boot_bimage to the device and patch it in the Magisk app (Install → Select and Patch a File). - Pull the patched file back, write it to the same slot, and reboot.
- Write down the hash of the original
boot_b. To undo everything, you just write the original back.
Trap one: root requests from the computer are silently refused, with no prompt on screen. The log shows only su: request rejected (2000), and Magisk’s settings have no obvious option for it.
The fix: open Magisk → the Superuser tab → tap the ”+” in the top-left → pick Shell (com.android.shell). Then adb shell su -c id should return uid=0(root). This is where I lost the most time, because nothing tells you.
Step 3: Install Google Play as a system component
Trap two: don’t install the Play Store and Google Services Framework as ordinary apps. I did at first, for convenience, and the services framework crashed every few seconds because it needs system privileges. Removing them then left the system stuck on the boot animation; a cold reboot with adb reboot brought it back. My rule since: whenever you touch Google packages, cold reboot.
The right way:
- Repack MindTheGapps as a Magisk module. You can drop pieces you won’t use, like the setup wizard, Google Assistant, and text-to-speech, which saves space and removes things that can break.
- If you installed the ordinary-app version earlier, remove it first:
adb shell pm uninstall com.google.android.gms. - Install the module and reboot:
adb push gapps_module.zip /data/local/tmp/gm.zip adb shell su -c 'magisk --install-module /data/local/tmp/gm.zip' adb reboot - After boot, check that
/product/priv-appcontainsPhoneskyandPrebuiltGmsCore, and/system_ext/priv-appcontainsGoogleServicesFramework. All three present and no more crash pop-ups means you’re done.
Picking the zip inside the Magisk app left the module list empty for me; the command above worked.
Step 4: Switch to Traditional Chinese
Changing the language in Settings doesn’t stick; the system flips it back to Simplified. Set the system property with root instead:
adb shell su -c 'setprop persist.sys.locale zh-TW'
adb rebootAfter the reboot, both the interface and the Play Store are in Traditional Chinese.
Step 5: Use a launcher made for e-ink
- Install Olauncher from F-Droid, a minimalist text-list launcher, and make it the default.
- Disable the stock Duokan launcher and WeChat Reading:
adb shell pm disable-user com.duokan.einkreaderandadb shell pm disable-user com.tencent.weread.eink. Swapdisable-userforenableto undo.
Trap three: Olauncher defaults to a dark theme, so you get white text on a white e-ink background, and the home screen looks like a blank page. Long-press the home screen and switch the theme to Light.
The easiest way to set the home-screen slots is to long-press a slot and pick from the list. I kept five: HyRead, KOReader, Mihon, Play Store, and Settings, and tapped each one to confirm it opens.
Step 6: Install reading apps
This is a 32-bit environment, so always download the arm or armv7 build:
- KOReader: arm build; solid for epub and PDF, with lots of layout options.
- Readest: armv7 build; a newer interface.
- Mihon: armeabi-v7a build, for comics; pick a storage folder on first launch.
- HyRead: from the Play Store; sign in with a library card and borrow e-books for free.
Four approaches compared
| Approach | Google Play | Touches boot partitions | Risk | Who it suits |
|---|---|---|---|---|
| No mod, sideload APKs | Installs, but services keep crashing | No | Very low | People who only read local files |
| Flash a whole third-party system | Yes | Replaces everything | High; e-ink drivers may not match | Experienced flashers willing to gamble |
| Magisk + Google module (this guide) | Yes, and stable | Only the boot image, reversible | Medium; recoverable with backups | People willing to back up and follow steps |
| Skip Google, use F-Droid apps only | Not needed | Magisk step still needed | Medium | People who don’t need HyRead or Play |
I went with the third because it changes the least: the stock system stays, plus root and a bundle of Google apps, and the original boot image sits on my computer, ready to be written back.
Tested: does HyRead open books?
On the morning of November 22, I borrowed a comic with a Taoyuan Public Library card, and at first the bookshelf just sat on “Loading.” It turned out the HyRead on the device was an old 3.2.1 build I had installed from a third-party download site. After updating to 3.2.5 through the Play Store, the bookshelf loaded right away and the borrowed book paged normally. HyRead did not refuse to open books because the device has root, so no hiding setup was needed. The one thing that matters: install HyRead from the Play Store and keep it current. The full commands, plus a small tool that taps the screen by on-screen text, are on my GitHub: https://github.com/bockybocky/duokan-pro2-mod
The one thing to take with you
Before you modify anything, find the one piece that can’t be recovered if it breaks, and back up that piece on its own.
I made several mistakes that night, and the system hung on the boot screen once, but because the partition I feared most was already safe, each mistake cost minutes rather than a device. Try this today: pick something you’ve wanted to change but were afraid to break, whether a phone, a shared spreadsheet, or your home router settings. Spend five minutes writing down which part would be hardest to restore if things go wrong, back up just that part, and then go ahead.
Comments
Loading comments…