Let's root our Max Lumi

yokos · 01-14-2021, 07:23 AM

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.

Code:

adb devices

[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:

Code:

fastboot reboot

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!

Georg_Jurij · 01-29-2021, 01:47 PM

Quote:

Originally Posted by yokos

**I am not responsible for any damage to your device. Please take care of your actions.**

Steps to install:
[1] Current firmware version is 3.0. My Max Lumi came with it. Attached bootimage is for version 3.0.
[2] Download and install Magisk Manager on Max Lumi.
[3] Do you have installed adb and fastboot on your computer?
[4] Enable usb debugging on your Max Lumi, plug it into your computer, and run in command line to check connection.

Code:

adb devices

[5] start a bootloader session

Code:

adb reboot bootloader

[5] The bootloader of Max Lumi is unlocked by default. That's nice. Thanks Onyx. You can check it with:

Code:

fastboot flashing unlock

Hey,
my Max Lumi does not boot in Bootloader Mode, after "adb reboot bootloader" my lumi is rebooting and then only show the ONYX Logo, fastboot command does not work.

Can anyone help me?

THX

yokos · 01-29-2021, 03:17 PM

The Onyx logo is ok. That IS Bootloader mode. I will update the first post of this thread for providing clarification.

Do you get any fastboot error messages? Then post them please.
Do others fastboot commands work?

Code:

fastboot help

Code:

fastboot reboot

Georg_Jurij · 01-29-2021, 04:18 PM

Quote:

Originally Posted by yokos

The Onyx logo is ok. That IS Bootloader mode. I will update the first post of this thread for providing clarification.

Do you get any fastboot error messages? Then post them please.
Do others fastboot commands work?

Code:

fastboot help

Code:

fastboot reboot

Thanks,
It shows "waiting for any device" after reboot to bootloader.

bingo619 · 01-29-2021, 07:52 PM

Same here, waiting for device, however mine NotePro does not even reboot by adb reboot bootloader.

yokos · 01-30-2021, 06:17 AM

Quote:

Originally Posted by Georg_Jurij

Thanks,
It shows "waiting for any device" after reboot to bootloader.

It could be a missing driver problem. Adb device driver is installed, but for fastboot not. The driver changes in fastboot mode.

Georg_Jurij · 01-30-2021, 07:12 AM

Quote:

Originally Posted by yokos

It could be a missing driver problem. Adb device driver is installed, but for fastboot not. The driver changes in fastboot mode.

Now fastboot is working after is swiched to linux, but now i have the following Error:

Code:

target didn't report max-download-size
sending 'boot' (12537 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s

Georg_Jurij · 01-30-2021, 08:41 AM

Quote:

Originally Posted by Georg_Jurij

Now fastboot is working after is swiched to linux, but now i have the following Error:

Code:

target didn't report max-download-size
sending 'boot' (12537 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s

Now its working on windows and i have the same error:

Code:

fastboot: error: cannot get boot partition size

yokos · 01-30-2021, 03:16 PM

According Google some fastboot versions seem not to work with specific devices.

On Windows I have used 15 seconds ADB installer to install ADB, fastboot and generic USB driver. Version 1.4.3 should be installed on my system.

yokos · 02-28-2021, 07:28 AM

New name of app Magisk Manager is Magisk. Updating to v22.0 of app and boot image directly on Max Lumi was no problem.
Before updating you have to unhide the Magisk Manager app, when you had changed its name.

bennetto · 03-08-2021, 04:08 AM

Hello, it's possible to change the splashcreen Kernel, "Onyx" when the boox start, when the boox is root.

yokos · 03-08-2021, 07:34 AM

Quote:

Originally Posted by bennetto

Hello, it's possible to change the splashcreen Kernel, "Onyx" when the boox start, when the boox is root.

Code:

fastboot flash splash splash.img

I didn't have a look at the splash partition.

Here you can edit the boot animation, which comes after the Onyx logo.

Code:

/system/media/bootanimation.zip

yokos · 03-18-2021, 10:59 AM

Firmware version 3.1 is out. I have added a current Magisk boot image in first post.

bingo619 · 03-21-2021, 07:06 PM

Thank you very much mate.

yokos · 04-07-2021, 02:11 AM

Installing over the air a small not full update (size << 1GB) stops when you try it on a rooted device. Installation routine does a checksum test of boot image which fails of course.
You have to flash the original boot image before installing this update.
I will update the first post later.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Max Lumi - Is it possible to buy one yet anywhere?	Papered Over	Onyx Boox	15	03-12-2021 02:26 AM
Max 3 / Max Lumi: lack of physical buttons annoying?	mr_sm1th	Onyx Boox	6	12-19-2020 10:45 AM
Does the Max Lumi have a gyroscope?	mr_sm1th	Onyx Boox	1	12-18-2020 01:00 AM
Dropbox and Max Lumi	IluvToRead	Onyx Boox	4	10-18-2020 07:08 PM
max lumi reviews	whopper	Onyx Boox	27	10-14-2020 11:13 AM

01-29-2021, 03:17 PM	#3
yokos Pac-Man caught my iLiad. Posts: 807 Karma: 3595 Join Date: Apr 2006 Location: Germany; next to Baltic Sea Device: Boox Max Lumi, iRex iLiad (RIP)	The Onyx logo is ok. That IS Bootloader mode. I will update the first post of this thread for providing clarification. Do you get any fastboot error messages? Then post them please. Do others fastboot commands work? Code: fastboot help Code: fastboot reboot

01-29-2021, 07:52 PM	#5
bingo619 Member Posts: 21 Karma: 10 Join Date: Jul 2016 Device: Kindle	Same here, waiting for device, however mine NotePro does not even reboot by adb reboot bootloader.

01-30-2021, 03:16 PM	#9
yokos Pac-Man caught my iLiad. Posts: 807 Karma: 3595 Join Date: Apr 2006 Location: Germany; next to Baltic Sea Device: Boox Max Lumi, iRex iLiad (RIP)	According Google some fastboot versions seem not to work with specific devices. On Windows I have used 15 seconds ADB installer to install ADB, fastboot and generic USB driver. Version 1.4.3 should be installed on my system.

02-28-2021, 07:28 AM	#10
yokos Pac-Man caught my iLiad. Posts: 807 Karma: 3595 Join Date: Apr 2006 Location: Germany; next to Baltic Sea Device: Boox Max Lumi, iRex iLiad (RIP)	New name of app Magisk Manager is Magisk. Updating to v22.0 of app and boot image directly on Max Lumi was no problem. Before updating you have to unhide the Magisk Manager app, when you had changed its name.

03-08-2021, 04:08 AM	#11
bennetto Junior Member Posts: 1 Karma: 10 Join Date: Mar 2021 Device: Boox Max Lumi	Hello, it's possible to change the splashcreen Kernel, "Onyx" when the boox start, when the boox is root.

03-18-2021, 10:59 AM	#13
yokos Pac-Man caught my iLiad. Posts: 807 Karma: 3595 Join Date: Apr 2006 Location: Germany; next to Baltic Sea Device: Boox Max Lumi, iRex iLiad (RIP)	Firmware version 3.1 is out. I have added a current Magisk boot image in first post.

03-21-2021, 07:06 PM	#14
bingo619 Member Posts: 21 Karma: 10 Join Date: Jul 2016 Device: Kindle	Thank you very much mate.

04-07-2021, 02:11 AM	#15
yokos Pac-Man caught my iLiad. Posts: 807 Karma: 3595 Join Date: Apr 2006 Location: Germany; next to Baltic Sea Device: Boox Max Lumi, iRex iLiad (RIP)	Installing over the air a small not full update (size << 1GB) stops when you try it on a rooted device. Installation routine does a checksum test of boot image which fails of course. You have to flash the original boot image before installing this update. I will update the first post later.