compatibility check: verify as many ROMs and devices as possible

[cfig]

We want to know how many device ROMs can be edited with this tool, which helps new comers.
If you use this tool for your debugging work or hacking, please kindly drop a comment.

[Surendrajat]

Confirmed working with Oppo K3(CPH1955) recovery.img (with some tricks - to get recovery.img out from boot.img using a bsdiff patch under system because didn't work with boot.img)

[cfig]

@Surendrajat Thanks for the kindness! This helps others.

[cfig]

Hi @Surendrajat , could you provide more info such as its Android version details?

Device Model	Manufacturer	Compatible	Android Version	Note
Pixel 3 (blueline)	Google	Y	Q preview (qpp2.190228.023, 2019)
Nexus 9 (volantis/flounder)	HTC	Y(with some tricks)	7.1.1 (N9F27M, Oct 2017)	[tricks]
K3 (CPH1955)	OPPO	Y (recovery.img)	???	[tricks]

[Surendrajat]

Absolutely. Pie it is.
I will open a PR for tricks about how to get recovery.img.

[Surendrajat]

@cfig Done #32

[eebssk1]

Xiaomi Redmi K30 4g(phoenix[n]) (LOS-like ROM android10 )boot.img with vbmeta.img modification works.

[cfig]

Xiaomi Redmi K30 4g(phoenix[n]) (LOS-like ROM)boot.img with vbmeta.img modification works.

Thank you! It would be better if you can provide more info like Android Version, download links of stock images(or 3rd party images).

[mariodantas]

Worked with Topway TS10 firmware (Android10)
China car Android headunit

Does not work after image patched with magisk but I think this is out of scope here

[eebssk1]

Worked with Topway TS10 firmware (Android10)
China car Android headunit

Does not work after image patched with magisk but I think this is out of scope here

Magisk directly patch the kernel to force load the ramdisk. It's not very recommended to modify magisk patched image with these tool. Modify the original image and then install magisk if possible.

[mariodantas]

Worked with Topway TS10 firmware (Android10)
China car Android headunit
Does not work after image patched with magisk but I think this is out of scope here

Magisk directly patch the kernel to force load the ramdisk. It's not very recommended to modify magisk patched image with these tool. Modify the original image and then install magisk if possible.

Thanks for the tip

[mariodantas]

In fact I wasn't trying to modify the patched image, I was trying to understand why I had an error (like the one in the attached PNG below) with the magisk patched image, it seems like Magisk is not doing the job supposed to be done correctly:

The test was done because my unit don't boot with magisk patched image

[eebssk1]

In fact I wasn't trying to modify the patched image, I was trying to understand why I had an error (like the one in the attached PNG below) with the magisk patched image, it seems like Magisk is not doing the job supposed to be done correctly:

The test was done because my unit don't boot with magisk patched image

Because magisk modifies the content so the signature will no longer match.However this should'nt happen as magisk resign the image with its own key..

Maybe signature in vbmeta is not changed when resigning,whch causes the error.Maybe you can open a issue at magisk repo for this..