Operation
BIOS rebuild from the manufacturer update
The BIOS is too damaged to simply fix. Upload the machine's dump and the manufacturer's official update: you get a clean BIOS, with the identity the dump holds.
Every operation is free during launch.
When to run a BIOS rebuild
- Corrupted BIOS
- Interrupted BIOS update, no longer boots
- Damaged dump (blank sectors)
Interrupted update, failed flash, bricked machine, blank sectors: serial, UUID, MAC address and Windows key are carried over from your dump. For a replacement motherboard, see "Motherboard replacement".
At a glance
- What it does
- Starts from the manufacturer's official update for the same model and carries over your machine's identity: serial number, UUID, MAC address, Windows key. For a BIOS too damaged to simply fix.
- Which machines
- Intel and AMD, one or two chips, with the manufacturer's update for that model.
- What you get
- One file per chip, and the combined image, checked before delivery.
- Good to know
- The identity is always carried over; the rest is chosen option by option. The machine's dump is required.
Rebuild: what is supported
- Intel and AMD, one or two chips, or a dump reduced to the BIOS region when the update ships the full chip.
- The update as downloaded from the manufacturer, executable, ZIP archive, ISO image, .cap capsule or raw image: this board's image is found among all those in the package.
- The machine's identity, always carried over: serial number, UUID, MAC address, Windows key, depending on what the dump holds.
- The manufacturer's ME when it is the same generation and at least as recent, otherwise the dump's: never a downgrade.
- The EC and the other regions the update does not replace stay those of the dump.
- One file per chip and the combined image; the result is re-read and checked before delivery.
What the rebuild does not do
- No rebuild without the machine's dump: it holds the machine's identity.
- It refuses an update for another board or another model, or one whose image cannot be chosen with certainty.
- It refuses an image more than 180 days older than the dump's BIOS: never a silent downgrade. Slightly older, it warns you.
- It refuses the dump itself, a re-read of the same chip or an earlier rebuild uploaded in place of the update: there would be nothing to carry over.
- It does not pick the BIOS version: it is the one in the package you upload.
- It does not move one machine's identity to another: it carries over the identity of the dump you upload.
- An internal flash is not guaranteed: program the files with a programmer.
How it goes
- 01
Upload the dump
The dump read from the machine's chip: it holds the machine's identity.
- 02
Add the update
The manufacturer's file for that model, as downloaded. It is read, never executed.
- 03
Choose what is carried over
The machine's identity, always; the rest depends on the dump and the package. Only the options that apply are offered, and each says what it changes.
- 04
Program the files
One file per chip and the combined image. 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.
Motherboard replacement
The new board keeps everything but the identity: that comes from the old board.
Intel and AMD, one or two chips, same chip sizes on both sides. Acer on Compal boards: also add the new board's EC chip dump.
Start with an upload
Create an account and upload the file: only the operations that apply are offered to you.