MobileRead Forums - View Single Post - Trying to root a Boox Note 2, stuck at fastboot boot image.img. Could use some help.

soypherpunk · 12-05-2025, 04:02 PM

Okay, if I've flashed the new boot image from the update to the boot partition (which I had to do to recover the device), should the Magisk versions modified with the boot.img from the update work now?

Actually, I just tried re-modifying the boot.img file from the update with magisk with the same boot.img file being flashed to the boot partition of the device. THIS worked!!

Thus, you need to have a working boot.img on your computer, the same boot.img actually flashed to the boot partition of the device (do this anyway just in case), then you run magisk and flash the newly modified boot.img to the device again, and my issue came from the existing difference between the boot.img on my computer and the one that was already flashed on the device.

Renate, for my own edification, it seems that firmware updates don't modify the boot partition, is this correct? (Since I just ran the firmware update and confirmed the update I have was the same from the Boox API and still had the error)?

-------------------------------------------------------------------------------------------------------------------

For anyone coming after me looking for help, these are the exact steps and version numbers I used, use this guide for supplemental steps such as getting the python scripts installed, and make sure you know how to use adb and fastboot.

Update the firmware to this version for your BOOX NOTE 2 (NOT THE AIR 2, also, I can't confirm 100% this guide will work for future verisons if they are released but it likely should). If a newer version is released, use the API link from my first post in the thread.

Go to the directory where you downloaded the update.upx file.

Run the python script

python DeBooxUpx.py Note2

Unzip the update.zip file, and cd into update if it's in its own folder, otherwise continue from the directory you're currently in

Confirm the boot.img (unmodified) will work, by running the following with your tablet connected to your computer.

adb reboot bootloader
fastboot flashing unlock
fastboot boot boot.img

If this works, run the following to make sure you're working with the same boot image with Magisk:

adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot

Next, we need to get the newly flashed boot.img to the device for Magisk. First, download Magisk v 26.4 and run

adb install Magisk-v26.4.apk
adb push boot.img /storage/self/primary

Next run Magisk on this boot image which will put the result in your Download folder. DO NOT RUN THIS IN RECOVERY MODE IN MAGISK, THE NOTE 2 WILL USE A RAMDISK IF SPECIFIED IN BOOT.IMG WHICH MAGISK WILL DO IF YOU DON'T CHECK THIS OPTION!!

Now, run the adb command on the result to put it back on your device:

adb pull /storage/self/primary/Download/magisk_patched-26400_*.img (note the star is a wildcard character that matches the random string Magisk puts at the end of each attempt)

Then run

adb reboot bootloader
fastboot boot magisk_patched-26400_*.img

If this works, then you can flash the image with

adb reboot bootloader
fastboot flash boot magisk_patched-26400_*.img
fastboot reboot

I hope this helps anyone else having this issue, and this indeed confirms that the Note2 will still use a ramdisk in the boot.img if present, so don't worry about the recovery mode for this particular device on this firmware update!

12-05-2025, 04:02 PM	#8
soypherpunk Junior Member Posts: 5 Karma: 10 Join Date: Dec 2025 Device: Boox Note 2	Okay, if I've flashed the new boot image from the update to the boot partition (which I had to do to recover the device), should the Magisk versions modified with the boot.img from the update work now? Actually, I just tried re-modifying the boot.img file from the update with magisk with the same boot.img file being flashed to the boot partition of the device. THIS worked!! Thus, you need to have a working boot.img on your computer, the same boot.img actually flashed to the boot partition of the device (do this anyway just in case), then you run magisk and flash the newly modified boot.img to the device again, and my issue came from the existing difference between the boot.img on my computer and the one that was already flashed on the device. Renate, for my own edification, it seems that firmware updates don't modify the boot partition, is this correct? (Since I just ran the firmware update and confirmed the update I have was the same from the Boox API and still had the error)? ------------------------------------------------------------------------------------------------------------------- For anyone coming after me looking for help, these are the exact steps and version numbers I used, use this guide for supplemental steps such as getting the python scripts installed, and make sure you know how to use adb and fastboot. Update the firmware to this version for your BOOX NOTE 2 (NOT THE AIR 2, also, I can't confirm 100% this guide will work for future verisons if they are released but it likely should). If a newer version is released, use the API link from my first post in the thread. Go to the directory where you downloaded the update.upx file. Run the python script python DeBooxUpx.py Note2 Unzip the update.zip file, and cd into update if it's in its own folder, otherwise continue from the directory you're currently in Confirm the boot.img (unmodified) will work, by running the following with your tablet connected to your computer. adb reboot bootloader fastboot flashing unlock fastboot boot boot.img If this works, run the following to make sure you're working with the same boot image with Magisk: adb reboot bootloader fastboot flash boot boot.img fastboot reboot Next, we need to get the newly flashed boot.img to the device for Magisk. First, download Magisk v 26.4 and run adb install Magisk-v26.4.apk adb push boot.img /storage/self/primary Next run Magisk on this boot image which will put the result in your Download folder. DO NOT RUN THIS IN RECOVERY MODE IN MAGISK, THE NOTE 2 WILL USE A RAMDISK IF SPECIFIED IN BOOT.IMG WHICH MAGISK WILL DO IF YOU DON'T CHECK THIS OPTION!! Now, run the adb command on the result to put it back on your device: adb pull /storage/self/primary/Download/magisk_patched-26400_.img (note the star is a wildcard character that matches the random string Magisk puts at the end of each attempt) Then run adb reboot bootloader fastboot boot magisk_patched-26400_.img If this works, then you can flash the image with adb reboot bootloader fastboot flash boot magisk_patched-26400_*.img fastboot reboot I hope this helps anyone else having this issue, and this indeed confirms that the Note2 will still use a ramdisk in the boot.img if present, so don't worry about the recovery mode for this particular device on this firmware update!