Edit 2023/12/16: I have uploaded the Magisk boot image of firmware version
2023-12-12_20-35_3.5_4687b1901.
Edit 2023/01/04: The boot images of version 2022-11-16_17-18_3.3.1_7130b19 and 2022-11-24_19-21_3.3.1_4c98746d8 are compatible. Both have same SHA256.
Edit 2022/11/18: I have added Magisk boot image for Max Lumi version 2022-11-16_17-18_3.3.1_7130b19.
Edit 2022/09/02: I have added Magisk boot image for Max Lumi version 2022-09-01_10-22_3.2.4_071fa5f.
Edit 2022/06/27: I have added Magisk boot image for Max Lumi version 2022-06-22_10-16_3.2.3_b3d86b2.
Edit 2022/05/10: I have added Magisk boot image for Max Lumi version 3.2.2 build 4cccaa4 (2022/04/28).
Edit 2022/03/31: I have added Magisk boot image for Max Lumi version 3.2.1 build 565f83b (2022/03/29).
Edit 2021/12/01: I have added Magisk boot image for Max Lumi version 3.2 build 5bccd60 (2021/11/30).
Please take care of that you have the same build before flashing boot image. On firmware v3.1 boot.img was not compatible between different builds. Users got finger touch problems.
Disclaimer:
** I am not responsible for any damage to your device. Please take care of your actions. Flashing not suitable images to partitions can brick your device. **
Edit 2021/03/18: I have added Magisk boot image for Max Lumi v. 3.1. Updating a rooted Max Lumi over the air is working. After installing a (full) firmware update you have to flash the patched boot image again.
Steps to install:
[1] Current firmware version of Max Lumi is 3.1. Attached bootimage is not suitable for other Boox devices!
[2] Download and install
Magisk Manager on Max Lumi.
Edit: current name is Magisk.
[3] Do you have installed adb, fastboot and USB drivers on your computer?
15 seconds ADB installer for Windows.
[4] Enable usb debugging on your Max Lumi. See Settings/Applications. Plug Max Lumi into your computer, accept fingerprint message and run in command line to check connection.
[5] start a bootloader session
Code:
adb reboot bootloader
Your Max Lumi will reboot and you will see the Onyx logo on screen. That's normal.
[5] The bootloader of Max Lumi is unlocked by default. That's nice. Thanks Onyx. You can check it with:
Code:
fastboot flashing unlock
[6] flash patched bootimage
Code:
fastboot flash boot your_patched_boot.img
Then your Max Lumi reboots by itself. Otherwise type:
For testing without risk, booting instead of flashing boot.img is safer option.
Code:
fastboot boot Max_Lumi_v3.0.Magisk.21.2.boot.img
[7] Start Magisk Manager and use "direct install" method to install boot image with latest magisk version.
Sample terminal session:
Code:
C:\Users\Leo\Desktop\Max Lumi>adb devices
List of devices attached
e3b2a8ed device
C:\Users\Leo\Desktop\Max Lumi>adb reboot bootloader
C:\Users\Leo\Desktop\Max Lumi>fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Users\Leo\Desktop\Max Lumi>fastboot boot Max_Lumi_v3.0.Magisk.21.2.boot.img
downloading 'boot.img'...
OKAY [ 0.276s]
booting...
OKAY [ 0.002s]
finished. total time: 0.301s
C:\Users\Leo\Desktop\Max Lumi>
Further reading:
It's a
non standard installation of Magisk, because Max Lumi has a
bootimage without ramdisk but loads this ramdisk when it is patched to bootimage.
decrypt Boox Update Upx, to get a boot image for your Boox device of encrypted firmware update.
Max 3 Rooted by diabl0w.
Booting into recovery mode: (just in case you need it)
[1] With pressed home button connect your turned off Max Lumi with USB C to a charger.
[2] You get the Onyx splash boot screen.
[3] Release the home button.
[4] LED next to power button is blue. Recovery mode starts.
[5] Select option in recovery mode with home button. Execute option with power button.
Removing bootloop caused by broken Magisk module:
Code:
adb shell
magisk --remove-modules
Screenshots:
#1 Magisk Manager on rooted Max Lumi with AdAway app in Split Screen mode
#2 & #3 Magisk Direct Install
Please use the attached files Max_Lumi_v3.1.original.boot.img.zip and Max_Lumi_v3.1.Magisk.22.0.boot.img.zip only for firmware 3.1_ad716f8.
It is not compatible with other 3.1.x builds like 3.1_0631e26 or 3.1_a207066. Otherwise you will get severe finger touch problems aka not working!