- How to use intel flash programming tool Pc#
- How to use intel flash programming tool download#
- How to use intel flash programming tool free#
If you have a laptop on Intel, then the BIOS file, which you can download from the manufacturer’s website and use for updating, most often contains an image of only the BIOS region and the EC firmware, usually stored in a separate flash chip. If you have a desktop board or laptop on AMD, then of all of the above, only the BIOS region remains. If you have a desktop board on Intel, as in our example, the resulting file will consist of several regions: a descriptor, a GbE region with an Intel integrated network card, a ME region, and a BIOS region. Consider that the manufacturer has already deleted it for you and read on. If there is no UEFI Capsule header in your BIOS file, then it is either quite old, for example for a P67 or Z68 board, or the manufacturer did not want to use it, despite Intel's insistent recommendations.
How to use intel flash programming tool free#
Therefore, if UBF is not used for firmware, feel free to cut off the 0x800 byte of the header and save the resulting file with the ROM extension. Moreover, the microcontroller implementing the firmware using the UBF technology, although it checks for the presence of this header, but does not check the certificates and flushes the modified files no worse than the original ones. When flashing with a hardware programmer, as well as with low-level utilities like the Intel Flash Programming Tool or flashrom, you just need to delete this header. Not a single byte from this two-kilobyte header is included in the BIOS chip, and this header is used only to check the validity of the file before flashing with standard ASUS utilities. In fact, nobody keeps this format in secret, it is described by the WIN_CERTIFICATE structure, familiar to PE32 + experts, the description of which can be found, for example, here, but in our case it is all not important. We don’t have the ASUS private key yet, and without it it’s impossible to sign a modified file, even knowing the format of the FW Certificate block, and breaking into RSA2048 and SHA256 is a bad thing. Immediately there is a temptation to understand thoroughly exactly how the FW Certificate and OEM Header blocks are arranged, but this is not necessary. The header size is really 0x0000001C, the total file size is really 0x00800800, the beginning of the FFS image is indeed at offset 0x800 - there is no doubt.
Open the file with a hex editor and check it for compliance with this format, in our case the title looks like this: This is a UEFI Capsule file, the format of which was described by AMI at one of the UEFI Plugfest conferences and looks like this: Unpacking the archive, we get a file of 0x800800 bytes with the extension CAP. Intel Flash Image Tool is the appropriate version, for 7-series chipsets it is version 8.xx.Hex editor to your taste, I will use HxD.To work with this file in the first part of the article we will need: As an example, it is taken because it contains all the components of the UEFI Capsule file, which I would like to talk about today. This is a typical representative of the AMI Aptio4 UEFI family with several ASUS extensions that do not greatly affect its format. The structure of EFI Firmware Volume and patches that are useful in the household will be described in the second part.Īs an example of a UEFI Capsule file, take the BIOS image for ASUS P8Z77-V version 2003. In this article we will talk about the device files UEFI Capsule and Intel Flash Image.
How to use intel flash programming tool Pc#
The release of motherboards on Intel sixth series chipsets (P67 and its brothers) brought to the mass PC market a new BIOS version - UEFI.