MobileRead Forums - View Single Post

diabl0w · 09-25-2019, 06:37 AM

**I am not responsible for any damage to your device, and I am sure this probably voids your warranty**

** UPDATE (11/2023): just a heads up for anyone bcuz this can be confusing if you dont know about it: Boox Max 3 runs android 9 and system.img contains init and boot.img contains kernel only. magisk works by patching the boot.img's ramdisk so that magisk runs during boot. for devices like ours that dont have ramdisk in boot.img, normally this means magisk has to run from recovery.img instead, which does have ramdisk. and so when you update magisk from the app, it will patch the recovery.img and so to have root you have to boot into android via recovery mode and booting normal way would be unrooted. this is a huge pain in the ass if you want to just use your device like a normal rooted device. however, unlike most other devices built this way, Max 3 will actually initialize ramdisk if you put one in boot.img. for some reason that i am unsure why, magisk will patch boot.img if you flash via recovery mode but it will patch recovery,img if done thru magisk app. TLDR; install/update magisk via recovery mode or directly patching boot.img, dont do it via the magisk app

** UPDATE (12/2020): ive updated the OP to better reflect the current state of our devices (December 2020), which is in a much more stable state now. ive also updated flash instructions. If you are reading the thread to get info, the first few pages of the thread are mostly old and irrelevant. With some help from CaptainThrowback on #twrp IRC, I was able to build a version of TWRP on our device. Let me know if you experience any issues **

Steps to install:
1) On computer, download magisk (from https://github.com/topjohnwu/Magisk) and TWRP (from my AndroidFileHost link below)
2) rename magisk.apk to magisk.zip and transfer to your device
3) make sure you have "adb" and "fastboot" installed on your computer, use google if you don't know
4) enable usb debugging on your device, plug it into your computer, and run "adb reboot bootloader" from the command line
6) ensure your bootloader is unlocked ("fastboot flashing unlock")
7) flash twrp ("fastboot flash recovery twrp.img") and reboot to system
8) Boot into recovery (instructions below) and flash magisk.zip

AndroidFileHost: https://www.androidfilehost.com/?w=files&flid=307038

To boot into recovery mode:
Turn your device completely off (make sure your not plugged in to charger), then hold the home button, then while holding the home button plug your device into charger... wait until you see splash screen and release home button. Unlikely, but if this doesnt work and you bought your device a long time ago, you may have an old BL version and need to take a newer OTA update

Taking OTA's:
1) you should be able to take OTA via TWRP, just use adb to set the correct fingerprint via "resetprop ro.build.fingerprint *proper fingerprint*" inside TWRP and then flash the update.zip in /data/local/assets

*** We now have TWRP and any bootloop issues you run into are recoverable through TWRP, just use google ***

09-25-2019, 06:37 AM	#1
diabl0w Connoisseur Posts: 87 Karma: 527 Join Date: Sep 2019 Device: Max3	Max 3 Rooted I am not responsible for any damage to your device, and I am sure this probably voids your warranty UPDATE (11/2023): just a heads up for anyone bcuz this can be confusing if you dont know about it: Boox Max 3 runs android 9 and system.img contains init and boot.img contains kernel only. magisk works by patching the boot.img's ramdisk so that magisk runs during boot. for devices like ours that dont have ramdisk in boot.img, normally this means magisk has to run from recovery.img instead, which does have ramdisk. and so when you update magisk from the app, it will patch the recovery.img and so to have root you have to boot into android via recovery mode and booting normal way would be unrooted. this is a huge pain in the ass if you want to just use your device like a normal rooted device. however, unlike most other devices built this way, Max 3 will actually initialize ramdisk if you put one in boot.img. for some reason that i am unsure why, magisk will patch boot.img if you flash via recovery mode but it will patch recovery,img if done thru magisk app. TLDR; install/update magisk via recovery mode or directly patching boot.img, dont do it via the magisk app UPDATE (12/2020): ive updated the OP to better reflect the current state of our devices (December 2020), which is in a much more stable state now. ive also updated flash instructions. If you are reading the thread to get info, the first few pages of the thread are mostly old and irrelevant. With some help from CaptainThrowback on #twrp IRC, I was able to build a version of TWRP on our device. Let me know if you experience any issues ** Steps to install: 1) On computer, download magisk (from https://github.com/topjohnwu/Magisk) and TWRP (from my AndroidFileHost link below) 2) rename magisk.apk to magisk.zip and transfer to your device 3) make sure you have "adb" and "fastboot" installed on your computer, use google if you don't know 4) enable usb debugging on your device, plug it into your computer, and run "adb reboot bootloader" from the command line 6) ensure your bootloader is unlocked ("fastboot flashing unlock") 7) flash twrp ("fastboot flash recovery twrp.img") and reboot to system 8) Boot into recovery (instructions below) and flash magisk.zip AndroidFileHost: https://www.androidfilehost.com/?w=files&flid=307038 To boot into recovery mode: Turn your device completely off (make sure your not plugged in to charger), then hold the home button, then while holding the home button plug your device into charger... wait until you see splash screen and release home button. Unlikely, but if this doesnt work and you bought your device a long time ago, you may have an old BL version and need to take a newer OTA update Taking OTA's: 1) you should be able to take OTA via TWRP, just use adb to set the correct fingerprint via "resetprop ro.build.fingerprint proper fingerprint" inside TWRP and then flash the update.zip in /data/local/assets * We now have TWRP and any bootloop issues you run into are recoverable through TWRP, just use google * Last edited by diabl0w; 12-22-2023 at 12:49 AM.