BTW. Maybe it could be useful for developers to have the edid files from not-working configurations to analyze.
If i am not mistaken, the edid create saves the edid-HDMI-A-1.bin file to /storage/.config/firmware/edid/ folder (and also edid-HDMI-A-2.bin for devices with two HDMI ports like RPi 4B etc.).
And it's possible to look what's there with:
edid-decode /storage/.config/firmware/edid/edid-HDMI-A-1.bin
I'm happy to receive edid files that cause a problem, but I think most issues are due to a lack of edid file.
If the hdmi cable is missing hotplug, SCL or SDA lines (which cheap cables can do to save costs),
then we can't read the edid.
This issue can also be caused by the Argon One case which does a similar thing with cable extenders.
Less common is a fault on display (worth trying different hdmi inputs, or a different display).
You can run:
edid-decode /sys/devices/platform/gpu/drm/card?/card?-HDMI-A-1/edid
on a booted system (ssh in if display is blank). If you get lots of info about modes supported, then you have an edid.
If you get an error, then we can't read the edid, and the only solution (apart from fixing the underlying issue) is editing config files.
I think the simplest change to get a picture without an edid would be to add to end of cmdline.txt:
video=HDMI-A-1:1920x1080@60D
(or some other resolution you know the display supports).
But note, without an edid, kodi won't know the range of refresh rates supported (for "adjust display refresh rate to match video"), and CEC and audio passthrough are unlikely to work fully.