EDID/DisplayID Writer

[jeffeh12133]

(12-03-2024 02:54 PM)ToastyX Wrote:  

(12-03-2024 06:54 AM)zarusoba10 Wrote:  Hello
I have successfully used this software to rewrite the EDID of a live display. As another step, I would like to rewrite the internal chip of an EDID counterfeit adapter.
According to the article below, if you connect the HPD pin of the HDMI to the GND pin, you can disable the WP without destroying the exterior of the counterfeit adapter.
The WP pin activates the WP when voltage is applied, but if you connect this pin to GND, the voltage to the WP is lost and the WP is disabled.
https://blog.sharpbai.com/2022/10/%E4%BF...%E6%81%AF/

I would like to apply this with EDwrite, but if the HPD pin goes to GND, I think Windows will probably not be able to detect the device plugged into the HDMI. What do you think?

I tried blocking the HPD pin with tape with a similar EDID emulator adapter, but Windows wouldn't detect it.

is it possible to extract the current EDID data and reupload it as DisplayID data or do i need to translate the EDID data into DisplayID format before writing DisplayID data

[ToastyX]

(12-06-2024 10:56 PM)jeffeh12133 Wrote:  is it possible to extract the current EDID data and reupload it as DisplayID data or do i need to translate the EDID data into DisplayID format before writing DisplayID data

EDID and DisplayID are completely different formats. Also I haven't seen any device with DisplayID data. The buttons are there to do the right thing if it becomes available, but I haven't seen it work on anything.

[a1007398368]

Hello, my system is Windows 11, this is the error code：
GPU count: 19
GPU index: 0 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 - 17 displays
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
GPU index: 1 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 2 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 3 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 4 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 5 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 6 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 7 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 8 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 - 16 displays
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
GPU index: 9 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 10 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 11 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 12 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 13 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 14 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 15 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 16 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0002 - ADL_Display_DisplayInfo_Get failed.
GPU index: 17 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0002 (duplicate)
GPU index: 18 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0002 (duplicate)

[ToastyX]

(06-18-2025 02:28 AM)a1007398368 Wrote:  Hello, my system is Windows 11, this is the error code：

What GPU is it?

[a1007398368]

(06-18-2025 03:00 AM)ToastyX Wrote:  

(06-18-2025 02:28 AM)a1007398368 Wrote:  Hello, my system is Windows 11, this is the error code：

What GPU is it?

Hello, here's my GPU: it's a PRO DUO (Fiji).

[ToastyX]

(06-18-2025 03:40 AM)a1007398368 Wrote:  Hello, here's my GPU: it's a PRO DUO (Fiji).

Can you try installing the latest driver: https://www.amd.com/en/support/downloads...-fiji.html

[a1007398368]

(06-18-2025 09:35 PM)ToastyX Wrote:  

(06-18-2025 03:40 AM)a1007398368 Wrote:  Hello, here's my GPU: it's a PRO DUO (Fiji).

Can you try installing the latest driver: https://www.amd.com/en/support/downloads...-fiji.html

Sorry, I have updated the latest driver, but the problem still exists. However, the error code has changed:
GPU count: 18
GPU index: 0 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 - 17 displays
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
GPU index: 1 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 2 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 3 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 4 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 5 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 6 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 7 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0000 (duplicate)
GPU index: 8 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 - 16 displays
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
Display index: -1 - Read failed.
GPU index: 9 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 10 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 11 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 12 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 13 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 14 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 15 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0001 (duplicate)
GPU index: 16 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0002 - ADL_Display_DisplayInfo_Get failed.
GPU index: 17 - Path: {4d36e968-e325-11ce-bfc1-08002be10318}\0002 (duplicate)

[ToastyX]

(06-19-2025 02:49 AM)a1007398368 Wrote:  Sorry, I have updated the latest driver, but the problem still exists. However, the error code has changed:

Here is a version with the duplicate check removed: https://www.monitortests.com/EDW-test2.zip

If it still doesn't find any displays, then the driver is not working correctly because it shouldn't be returning -1 for the display indexes. Does it work if you connect the monitor to the RX 580?

[GeoffreyA]

Hello ToastyX,

Many thanks for your useful tools.

I've been having a problem which you may have insight into. It's described in more detail on Intel's Issue Tracker: https://github.com/IGCIT/Intel-GPU-Commu...ssues/1120

Basically, when I connect my 900p DVI monitor to the motherboard's HDMI port, using an HDMI-to-DVI cable, it works normally. When I connect it to an Asrock Arc B580 GPU, the BIOS displays at 640x480, much of it isn't visible, and it freezes. Windows displays correctly.

Experimenting with CRU and EDID Writer, I found that adding a detailed resolution of 1920x1080 and flashing it to the monitor solved the problem: the BIOS displayed correctly. (My monitor, while 900p natively, is able to take a 1080p signal and scale it internally.) However, it did not persist through turning off the power at the wall. I also tried a "Burn" option in the service menu, but it wouldn't persist.

I believe the problem starts with the B580's VBIOS or GOP. Seemingly, if it doesn't detect a 1080p screen at least, it defaults to 480p, which then causes an issue with the MSI motherboard's BIOS. Is there some way to flash the monitor's EDID permanently, or is asking Intel to update the VBIOS the best option?

Thank you,
Geoffrey

[ToastyX]

(07-02-2025 06:29 PM)GeoffreyA Wrote:  Experimenting with CRU and EDID Writer, I found that adding a detailed resolution of 1920x1080 and flashing it to the monitor solved the problem: the BIOS displayed correctly. (My monitor, while 900p natively, is able to take a 1080p signal and scale it internally.) However, it did not persist through turning off the power at the wall. I also tried a "Burn" option in the service menu, but it wouldn't persist.

I believe the problem starts with the B580's VBIOS or GOP. Seemingly, if it doesn't detect a 1080p screen at least, it defaults to 480p, which then causes an issue with the MSI motherboard's BIOS. Is there some way to flash the monitor's EDID permanently, or is asking Intel to update the VBIOS the best option?

Seems like the motherboard's firmware is buggy because it should at least handle 640x480 correctly without glitching like that. There could also be some issue or limitation with the B580's firmware that's causing it to fallback to 640x480.

The monitor might be flashing the EDID when powered on to fix situations where the EDID might have corrupted itself. I think the best solution is to use an EDID emulator like this:
https://www.amazon.com/dp/B0B7XJHRHB/?tag=mtests-20#ad

I don't think that emulator is writable, but you can use CRU to get the correct resolution in Windows while having 1080p supported during boot.