cfig

to unpack "vbmeta_system.img", you need to clear the directory, and leave "vbmeta_system.img" the only .img file there. The unpack result is: [json.zip](https://github.com/cfig/Android_boot_image_editor/files/6764040/json.zip) As you can see, it contains hashTree descriptor...

"really strange system_ext is tightly couple with system" --> It's redmi's choice to put system_ext info to vbmeta.img. "no need to flash a new vbmeta.img." --> I see vemta.img header...

If there is scenario that you have 3rd party images (dtbo, system, system_ext, vendor ...), but not the full source code, and you want to update vbmeta accordingly, please let...

If the goal is to boot up Android, and AVB verification disabled is accepted: Just disable it by setting flag=3; or remove the relevant entry from vbmeta json, then pack...

Run it again with debugging enabled. ``` ./gradlew unpack --scan ``` Please paste the full log and your testing "boot.img". Thanks

It's weird. BTW, have you installed jdk?

Hi @nakixii , Thanks for reporting incompatibility issues. I did a quick check of the image, it seems the image has strange value in ramdisk table entry size. Is this...

Hi @nakixii , Just tried with aosp `unpack_bootimg.py`, ``` red➜ ~/big/a/system/tools/mkbootimg git:(c6bbbe1) ✗ ./unpack_bootimg.py --boot_img ~/work/boot/vendor_boot.img --out out Traceback (most recent call last): File "/home/yu/big/a/system/tools/mkbootimg/./unpack_bootimg.py", line 563, in main() File...

Let's check the "vendor ramdisk total size" field of the image header:  The binary hex is 0x121fb803, interpret it as little endian int, we get 0x03b81f12 = 62398226 bytes...

That's good. About "ramdisk", it can be manually extracted with `mkdir temp && cd temp && cpio -iv < ../build/unzip_boot/ramdisk.img` "dtb" can be manually extracted as you have successfully done....