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

soypherpunk · 12-04-2025, 03:30 PM

Hi everyone!

I'm a bit new here, but I'm not particularly new to rooting/installing new firmware, jailbreaking, etc. but this Boox Note 2 is giving me hell.

For context, I've been attempting to flash Magisk to the device and I feel completely stuck. I followed the guides here and here (along with many on reddit and private blogs) but with only marginal success.

To wit, I've gotten adb and fastboot (already had them, actually) on a linux box, and was able to successfully decrypt and extract my firmware using this API link (which I confirmed was the correct firmware version I had installed on my device) and the DeBoox.py script.

After this, I pushed the boot.img and Magisk (versions 30.6, 28,27,26.4 for reasons that will become clear shortly) and attempted to run the Magisk application on the boot.img file which produces output. However, when trying "fastboot boot magisk_image.img" I got a series of puzzling results with no correct behavior, and to make it worse, the bad behavior isn't present when running "fastboot boot boot.img" on the clean image from the factory firmware from the DeBoox step.

According to the two linked guides, it is apparently possible to patch the boot.img using Magisk despite these devices not using the ramdisk by default, so this is the strategy I've been trying (I also tried using TWRP, which I was able to flash to recovery, but never able to access). However, each one of these attempts have failed, seemingly due to a discrepancy in how Magisk modifies the files between versions. For example, the most recent version (30.6) apparently causes malformed header information in the boot.img file and fastboot outright refuses to try to boot it. When trying the other versions of Magisk, fastboot will successfully send the files, but won't boot the device and gives me either Booting FAILED (status read failed) or Booting FAILED (cannot send after transport endpoint shutdown).

This indicates (to my novice brain) that magisk is causing the issue....maybe. But I have no earthly idea how to address it, nor move forward with rooting my device.

Thus, I humbly ask for this forum's collective wisdom in addressing my issue. If there is any additional information required to begin addressing the problem, please let me know and I'll be happy to provide it.

Thank you all in advance for any help you're willing to provide, I greatly appreciate it.

Warmest Regards,
Soypherpunk

12-04-2025, 03:30 PM	#1
soypherpunk Junior Member Posts: 5 Karma: 10 Join Date: Dec 2025 Device: Boox Note 2	Trying to root a Boox Note 2, stuck at fastboot boot image.img. Could use some help. Hi everyone! I'm a bit new here, but I'm not particularly new to rooting/installing new firmware, jailbreaking, etc. but this Boox Note 2 is giving me hell. For context, I've been attempting to flash Magisk to the device and I feel completely stuck. I followed the guides here and here (along with many on reddit and private blogs) but with only marginal success. To wit, I've gotten adb and fastboot (already had them, actually) on a linux box, and was able to successfully decrypt and extract my firmware using this API link (which I confirmed was the correct firmware version I had installed on my device) and the DeBoox.py script. After this, I pushed the boot.img and Magisk (versions 30.6, 28,27,26.4 for reasons that will become clear shortly) and attempted to run the Magisk application on the boot.img file which produces output. However, when trying "fastboot boot magisk_image.img" I got a series of puzzling results with no correct behavior, and to make it worse, the bad behavior isn't present when running "fastboot boot boot.img" on the clean image from the factory firmware from the DeBoox step. According to the two linked guides, it is apparently possible to patch the boot.img using Magisk despite these devices not using the ramdisk by default, so this is the strategy I've been trying (I also tried using TWRP, which I was able to flash to recovery, but never able to access). However, each one of these attempts have failed, seemingly due to a discrepancy in how Magisk modifies the files between versions. For example, the most recent version (30.6) apparently causes malformed header information in the boot.img file and fastboot outright refuses to try to boot it. When trying the other versions of Magisk, fastboot will successfully send the files, but won't boot the device and gives me either Booting FAILED (status read failed) or Booting FAILED (cannot send after transport endpoint shutdown). This indicates (to my novice brain) that magisk is causing the issue....maybe. But I have no earthly idea how to address it, nor move forward with rooting my device. Thus, I humbly ask for this forum's collective wisdom in addressing my issue. If there is any additional information required to begin addressing the problem, please let me know and I'll be happy to provide it. Thank you all in advance for any help you're willing to provide, I greatly appreciate it. Warmest Regards, Soypherpunk