Operation
Extract from the BIOS dump
An EC chip to reprogram, a region to pull out, a sub-part to compare: whatever the chip map delimits is extracted from the dump, without changing it.
Every operation is free during launch.
When to extract from the dump
- Extract and program the EC chip
- Pull out a complete region
- Extract one or more sub-parts (ME, network…)
Dead or replaced EC chip, ME or BIOS region to recover, BIOS-only dump, comparison with another board: tick what you need in the chip's tree.
At a glance
- What it does
- Takes out of the dump, without changing it, the chip's regions, their sub-parts (UEFI volumes, ME partitions…), and the EC chip image ready to program.
- Which machines
- Intel and AMD, including a BIOS-only dump; ready-to-program EC image for ITE and ENE controllers.
- What you get
- One file, or a ZIP archive when you pick several; on two chips, each file says which chip it comes from.
- Good to know
- The EC image size comes from the dump: check it against the chip before programming.
What can be extracted from the dump
- The regions of an Intel chip, BIOS, ME, GbE, EC and the others the dump delimits, as long as they are whole and not blank.
- The zones of an AMD chip, named by their role, and the BIOS file of a BIOS-only dump.
- The sub-parts: UEFI volumes, ME partitions, the UEFI variable store, microcodes, boot block.
- The ready-to-program EC chip image for ITE and ENE controllers, when the dump establishes the chip size and where the image sits.
- For Microchip (MEC), Nuvoton and SMSC controllers, which read their program from the BIOS chip: the copy as read, with no EC chip made up.
- A two-chip board: everything is worked out on both chips together, and each file says which chip it comes from.
- Several items at once, in a ZIP archive, each named after what it is.
What the extraction does not do
- It does not change the dump and does not lock the job.
- No ready-to-program EC image when the EC maker, its chip size or where the image sits is not established by the dump.
- The EC image size comes from the dump, not from the chip fitted: compare it with the chip marking before programming.
- An EC chip dump uploaded alone has nothing to extract: it is programmed as is.
- Nothing is extracted from a dump read with swapped bytes: read the chip again.
- A blank region, or one that runs past the end of the file, is not offered.
How it goes
- 01
Upload the dump
The .bin or .rom file read with your programmer; both files for a two-chip board.
- 02
Read the sheet
In seconds and free: the machine, the chip's state, the possible operations.
- 03
Run the operation
Pick one of those the sheet offers. If the operation cannot complete, the refusal says why and no file is delivered.
- 04
Program the file
Download it and program the chip. Always keep the original dump.
What holds for every operation
Several operations, one upload
After an operation, run another on the same dump, or continue from the result. Every job keeps its history.
Two-chip BIOS
Upload both files: they are analysed together, and the result says which chip to program.
Related operations
Extract a manufacturer package
What a manufacturer update contains, file by file, in seconds.
Updates as manufacturers publish them: executables, archives, disk images, capsules.
Clear ME
PCH swapped, SSD or Wi-Fi not detected: the ME starts again as on first boot. It is not disabled.
Intel, CSME 11 to 20.
Dump analysis
Free and instant: the machine's sheet and the possible operations.
Any BIOS chip dump read with a programmer, .bin or .rom: one or two chips, plus the EC chip dump.
Start with an upload
Create an account and upload the file: only the operations that apply are offered to you.