[SOLVED] HP d530 CMT microcode addition

[DeathBringer]

Using FLASHBIN.EXE from 786D1, FLSH.CPU and original Rom.bin from 786D2 on a DOS-bootable floppy disk.

786D2? Try name BLUEFI20.22C and 7B2_0244.bin for Rom.bin

Is there any way to convert ROM.BIN to "BLUEFI" lite version to use with FLSHLITE? Or insert ROM into ROMPAQ (guessing not due to signing)?

I don't know...

[Towncivilian]

New error with Rom.bin renamed to BLUEFI20.22C: "Error! Product id doesn't match filename in file BLUEFI20.22C"
I have been trying 7B2_0244.bin in all previous attempts without success.

Flashbin.exe: 786D1
FLSH.CPU: 786B2
Rom.bin: 786B2 original renamed to BLUEFI20.22C
Processor is original CPU that came with computer

[DeathBringer]

Last chance experiment:
Flashbin.exe: 786D1
FLSH.CPU: 786D1
Rom.bin: 786B2 original renamed to 7D1_0161.bin and 7B2_0244.bin

[Towncivilian]

No luck. So, if 786D1 FLASHBIN + 786B2 FLSH.CPU complains about product ID not matching the filename in BLUEFI20.22C, how can I find out my product's actual ID to hex edit the file to match?

786D1 FLSH.CPU always resulted in no valid drivers and stopped the keyboard from working, so I think we must use FLSH.CPU from 786B2 always.

[DeathBringer]

As result - 786B2 FLSH.CPU uses compressed format of BIOS (e.g. BLUEFI20.22C) and can't use uncompressed version (Rom.bin).
786D1 FLSH.CPU is incompatible with your motherboard...

[DeathBringer]

Did you tried to use 786B BIOS Family Processor Microcode Update with new CPU?

[Towncivilian]

I did, that didn't help.

Hex edit HPQFlash.exe from SP40411 at offset 10B6 (bytes 75 11), change 75 to EB. Signature check is bypassed and I was able to flash successfully from within Windows after creating a new CAB file containing the modified ROM.bin and same ROM.sig. Many thanks to my colleague arc_ for finding that solution in about 10 minutes.
Note that this fix only bypasses error 6 "BAD_ROM_SIGNATURE"; any other errors will still throw.

[DeathBringer]

....

To rebuild ROM.CAB use this tool: CABPACK http://www.larshederer.homepage.t-online.de/cabpack.htm
(chose MSZIP compression type)

To flash, use a patched HPQFLASH from here: http://forums.mydigitallife.info/threads...s?p=111460&viewfull=1#post111460
...

WINDOWS FLASHING NEW release 07-oct-2010
You need this patched HPQFlash version 4.30.10.2 and CABPACK to rebuild the ROM.cab (chose MSZIP compression type)

[Towncivilian]

Looks like that should work as well, thanks for the links.

My modified BIOS with proper microcode for my P4 Extreme Edition 3.2ghz chip is flashed and it works, no microcode error during POST anymore.

Thank you for your assistance, DeathBringer!

[apolander]

I did, that didn't help.

Hex edit HPQFlash.exe from SP40411 at offset 10B6 (bytes 75 11), change 75 to EB. Signature check is bypassed and I was able to flash successfully from within Windows after creating a new CAB file containing the modified ROM.bin and same ROM.sig. Many thanks to my colleague arc_ for finding that solution in about 10 minutes.
Note that this fix only bypasses error 6 "BAD_ROM_SIGNATURE"; any other errors will still throw.

Hello Towncivilian

I have HP PC same as yours (HP d530) and after upgrade the cpu have microcode error problem.

I have try to update the bios to 2.50 but still "Microcode update error" during POST.

Can you share your modified BIOS with proper microcode to me or let me know how to modify it.

Thanks !