For anybody who uses CustomEDID, EDID patch is necessary. That is all I am saying.
Not really.
If the display id already in the EDID causes no problem, then nothing more need be done. It is only if brightness doesn't work, that it is worth a try to patch the id.
And there are probably a lot of people using EDID/Custom or CustomEDID when they don't need to (eg. Clover EDID detection works most of the time). And in that case, they should be encouraged to use just EDID/Inject=true, with EDID/ProductID=0x1111. It is only in the rare case that Clover cannot detect EDID that EDID/Custom with patched id must be used.
I guess finally we agreed that Clover can't inject EDID for whatever reason.
Yes, of course this would have been easier if you had stated this at the outset. But then again, this is the first time you're looking at your Clover bootlog, so we really only just now confirmed this.
This laptop btw correctly boots with Ubuntu and Windows without any EDID patch, that is why I believe that this is a bug from Clover side.
Windows and Ubuntu will not be getting EDID from BIOS/VESA. They will get it from IGPU hardware. And the drivers there probably have some additional code to work more generally than the OS X/macOS drivers do. After all, OS X/macOS only has to work with Apple hardware. It means a lot of special cases and workarounds are not present in the Apple software.
Anyway, I guess that is the way it is. I hope this knowledge can help other people who has trouble of selecting correct product id due to buggy EDID. Have a nice day/night. It is 4 AM here. Good bye.
Thanks for hanging in there to get to the bottom of it.
I can't write about something without a complete understanding...
The problem with your Clover EDID detection was the final missing chunk of information.
Note that it also would have been quicker if even in failed attempts, full "Problem Reporting" files were provided...