readeryer.blogg.se - Flash programming tool intel

I’m not sure if it validates the signature and if it unlocks all regions. I didn’t try this, but I assume it will load a BIOS file from the root of FAT32 storage device or optical disk drive attached by USB/SATA. Pin pad BBR - according an internet search results this is a boot block recovery for a crisis situation. There were two pairs of (un?)documented pinheads and one (un?)documented pair of pin pads on a board. “Pinmod”) shorting, pressing Win++ or Win+B while powering up, setting a variables from a DXE “Setup” driver using a EFI shell - none of these attempts were succeeded. Later, after making a full dump, I’ve discovered, that BIOS region is locked for writing: I was trying to flash my full original dump.įlash Descriptors region with unlocked variables flashing, HDA_SDO/GPIO33 (a.k.a.

Since both MMTool and UEFITool were generating image files with some discrepancies and senior members of the forum were telling me that they don’t see any problems - I’ve decided that I need to dump the whole SPI flash image for a backup purpose in a worst case scenario, not only some specific regions of a flash memory.įlash Programming Tool was used for that but it won’t succeed to read a ME region unless you unlock it.

I’ve lost so much time playing around, that at the end of the day it was easier to build a complete flash image for me from several pieces. Maybe ME region could be updated only by HP DOS update tool provided with the BIOS file or even only under Windows using their Windows tool from the same package.

BIOS update file provided by HP contains ME region as well as expected BIOS region but while flashing it using a HP UEFI flash menu invoked by pressing Esc - ME region stays intact in spite of an unlocked write-unprotected ME region, I don’t know why.

Original BIOS file is signed by HP, so HP user tools won’t flash a modified BIOS it because of the signature mismatch unless you’ll find out how to generate the proper signature: you may need a quantum computer for that in case HP uses a strong signature.

UEFITool was corrupting both a ZeroVector and a Checksum of this BIOS region root filesystem.įlash Image Tool was reordering a ME/BIOS/(empty)PDR regions while building an image.

MMTool Aptio was corrupting a pad file thus was thrown away. (FIT) and Flash Programming Tool (FPT) (DOS variant under FreeDOS 1.3 Live CD) from ME System Tools v8 r3, WinMerge for ME DATA comparison, Hex Editor Neo Professional for hex comparison and corrections.

I was trying first to integrate a NVMe module, then since I’ve already dig down, I’ve decided to upgrade the ME as well.ħ tools were used for that: UEFITool 0.28.0, UEFITool NE A59, Flash Image Tool v8. I’ll just leave it here in case something will be looking for the same. HP Compaq Elite 8300 SFF, Intel Q77 Express, BIOS K01 v03.08