[X3non]

I had to unlock the bootloader using identifier token (this method): https://www.hovatek.com/forum/thread-32287.html
Yes, it has a vbmeta image.

if this is the case then you actually need to generate your own custom vbmeta ; see https://www.hovatek.com/forum/thread-32664.html
then sign your patched_boot using avbtool before the device will accept the boot image ; see https://www.hovatek.com/forum/thread-32674.html

[AshLFC_01]

if this is the case then you actually need to generate your own custom vbmeta ; see https://www.hovatek.com/forum/thread-32664.html
then sign your patched_boot using avbtool before the device will accept the boot image ; see https://www.hovatek.com/forum/thread-32674.html

I see, thanks.
But when I tried to verify the contents of my vbmeta image (from https://www.hovatek.com/forum/thread-32666.html), it says that "Given image does not look like a vbmeta image."... unusual.
The size of my vbmeta image from the .pac file is around 13KB, while the tutorial has around 1MB.
I can open it in HxD and I see that the boot key is the same as the one provided by you. But all the partition names do not match (for example, I don't find any partition named dtb).

Also, my magisk patched boot image file is around 14.2MB while the stock boot image file is 35MB. Is that alright?

[X3non]

I see, thanks.
But when I tried to verify the contents of my vbmeta image (from https://www.hovatek.com/forum/thread-32666.html), it says that "Given image does not look like a vbmeta image."... unusual.
The size of my vbmeta image from the .pac file is around 13KB, while the tutorial has around 1MB.
I can open it in HxD and I see that the boot key is the same as the one provided by you. But all the partition names do not match (for example, I don't find any partition named dtb).

Also, my magisk patched boot image file is around 14.2MB while the stock boot image file is 35MB. Is that alright?

your vbmeta image, check using hex editor, does it begin with AVB*? might as well upload the vbmeta image and drop a link
the 13kb size must mean that the image wasn't padded, possibly it's not necessary for your device and there's nothing wrong with your magisk_patched_boot

[AshLFC_01]

your vbmeta image, check using hex editor, does it begin with AVB*? might as well upload the vbmeta image and drop a link
the 13kb size must mean that the image wasn't padded, possibly it's not necessary for your device and there's nothing wrong with your magisk_patched_boot

It doesn't begin with AVB, it begins with DHTB but it does have AVB further down below.
I've attached my vbmeta image.

[freshtyt]

It doesn't begin with AVB, it begins with DHTB but it does have AVB further down below.
I've attached my vbmeta image.

if you remove everything above avb0, you should be able to use info_image command

[AshLFC_01]

if you remove everything above avb0, you should be able to use info_image command

Thank you, that worked! I wonder why it obstructed the command from working?
Now, I see that my vbmeta has 7 partitions, and the keys match with those provided, albeit some of the partitions have a slightly different name. I will now try to follow the tutorial as usual.

@X3non, so would I need to add the padding now? And do I need to add this command --padding_size 16384 when generating the custom vbmeta image?

[X3non]

Thank you, that worked! I wonder why it obstructed the command from working?
Now, I see that my vbmeta has 7 partitions, and the keys match with those provided, albeit some of the partitions have a slightly different name. I will now try to follow the tutorial as usual.

@X3non, so would I need to add the padding now? And do I need to add this command --padding_size 16384 when generating the custom vbmeta image?

vbmeta image has to begin with AVB* , the DHTB sign placed at the header section makes the image unrecognizable as a vbmeta
be sure to stick with the filenames from your vbmeta

you are to add padding but not 16382, i believe you should use --padding_size 12288 ; see https://www.hovatek.com/forum/thread-326...#pid194145 for why

and lastly use the attached vbmeta_pad.py attached here rather than the one we listed @ https://www.hovatek.com/forum/thread-32664.html

[X3non]

...

i noticed that you've already downloaded the vbmeta_pad.zip ; i just modified the file, you will need to discard the previous download and redownload the file. had to make a slight modification based on the padding size for your original vbmeta

[AshLFC_01]

vbmeta image has to begin with AVB* , the DHTB sign placed at the header section makes the image unrecognizable as a vbmeta
be sure to stick with the filenames from your vbmeta
you are to add padding but not 16382, i believe you should use --padding_size 12288 ; see https://www.hovatek.com/forum/thread-326...#pid194145 for why
and lastly use the attached vbmeta_pad.py attached here rather than the one we listed @ https://www.hovatek.com/forum/thread-32664.html

I see. Yes, I'm aware of changing the filenames in the command to match mine. So, do I use the vbmeta image with the DHTB sign removed now?

i noticed that you've already downloaded the vbmeta_pad.zip ; i just modified the file, you will need to discard the previous download and redownload the file. had to make a slight modification based on the padding size for your original vbmeta

Good thing you noticed that and made sure to inform me, thanks!

[X3non]

...do I use the vbmeta image with the DHTB sign removed now?

yes