Rooting Onyx Boox Air Nova C problem

[artyums]

Trying to root my Onyx Boox Air Nova C via guide:
https://www.mobileread.com/forums/sh...d.php?t=346175

There is two problems:
1) The size of extracted boot.img is 3.7 GB (Is it normal?). When Magisk trying to patch boot.img it's ended with "Failed to output to (file)..." error because the memory is out.
Have 14GB of free memory but it's not enought... (Why?!....)
So I transferred boot.img to my mobile phone (Xiaomi Mi 11) and successfully patched boot.img on it.

2) Sent my Onyx to bootloader via adb reboot bootloader command.
fastboot devices shows Onyx device.
fastboot boot magisk_patched_boot.img gives error:

terminating with uncaught exception of type STD::length_error: vector

Could you help me?

[Anghirrim]

Hey, nope it's not normal.

Can you please detail the exact commands you wrote when you dumped the boot.img?

While for the second problem, your command is not correct, you missed "flash". It's

fastboot flash boot_a yourpatchedimage.img

boot_a or boot_b of course depending on your active slot.

And don't flash your big boot.img file. It should be around 100Mo only.

[Renate]

Yes, 3.7 GB is just wrong and I don't even know how Magisk made heads or tails of it.
If you have Windows you can use imgutil.exe (in my sig) to see what you have.

C:\>imgutil /v mystery.img

fastboot boot yourimage.img

This is correct to try out an image without flashing.
There are situation where it does not work but flashing it would.

[artyums]

Originally Posted by Anghirrim

Can you please detail the exact commands you wrote when you dumped the boot.img?

All commands as said here: https://www.mobileread.com/forums/sh...d.php?t=346175

adb reboot edl
edl.exe /lq662.elf /r /pboot_b boot.img /t /v

This command gives me 3.7GB boot.img file. I'm also tried to extract boot_a and the result was the same.

---

If you have Windows you can use imgutil.exe (in my sig) to see what you have.

imgutil /v boot.img

Output:

Could not map C:\platform-tools\boot.img

[Renate]

Originally Posted by artyums

edl.exe /lq662.elf /r /pboot_b boot.img /t /v

Something screwy is going on.
Try that without the /t
I'm pretty sure that's your problem.

Didin't it give you a warning?

Try doing "edl.exe /g" and copy just the two boot_x lines

[artyums]

Originally Posted by Renate

Try that without the /t
I'm pretty sure that's your problem.

You're wizard! Thank you so much!
The problem was in "/t" key of EDL.
Without "/t" the size of "boot.img" has become ~100Mb and other procedures completed successfully.

[Renate]

Yes, for some reason it was estimating the size of image incorrectly.
Could you run "imgutil /v boot.img"
I'd like to see where it's going amuck.

Could you do me a favor?

edl.exe /r /pboot_b /c256 shortie

This will grab just a chunk of the boot image so that I can figure out what went wrong.
It should be only 131,072 bytes.