The original contents of a laptop's BIOS chip are irreplaceable. They hold the board's serial number, network address, licence data and calibration that no downloaded file can provide. A proper backup takes ten minutes and turns every BIOS job from a gamble into a reversible operation. Skipping it is the single most common way repairers make a recoverable board unrecoverable.
What exactly you are protecting
Even a "corrupted" chip usually still holds valuable data:
- identity data — serial number, system UUID, service tag, MAC address;
- the Windows licence table on machines sold with Windows 8 or later;
- the Intel ME region in a state that matches this board;
- settings and calibration — some boards store display, battery or sensor calibration in firmware variables;
- the exact BIOS version the machine shipped or was updated to.
Once you erase the chip, all of that is gone unless you saved it. The structure of these regions is explained in What Is a Laptop BIOS Chip and Where to Find It.
The backup routine
1. Prepare
- Disconnect the adapter and the battery; the board must be completely unpowered.
- Identify the chip's part number, capacity and voltage from the marking and the datasheet.
- Use a 1.8 V adapter for 1.8 V chips.
- Attach the clip (or desolder the chip) with pin 1 aligned.
2. Read twice
Read the chip and save the file. Then read it again into a second file. Do not reuse the same buffer in the software; save each read separately.
3. Compare the reads
The two files must be identical. Compare them with your programmer software's compare function or with a checksum:
certutil -hashfile read1.bin SHA256
certutil -hashfile read2.bin SHA256
sha256sum read1.bin read2.bin
Identical hashes mean identical files. If they differ, the connection is unreliable: reseat the clip, clean the legs, shorten the cable or desolder the chip, and read again until two consecutive reads match. A third matching read is cheap insurance.
4. Check the content
A matching pair of reads can still be useless if the chip was never really read:
- All
FFor all00— the programmer did not talk to the chip, or the chip is blank or dead. - Repeating patterns throughout — often a sign of a wrong chip setting or a bad connection.
- Readable strings — open the file in a hex editor and search for the BIOS vendor name, the model or the BIOS version. Finding them is a good sign the read is real.
- Correct size — the file should equal the chip capacity exactly.
5. Name and store it
Use a name that says everything you will need later:
LA-D312P_rev1.0_SN-XXXXXX_original_2026-10-21.bin
Include the board code, revision, serial number (or job number) and date. Store it in at least two places — your job folder and a backup drive or cloud folder — and never overwrite it. Add a text note with the chip part number, the programmer used and any oddities you noticed.
Before the board dies: software backups
If the laptop still boots, you can capture extra information before opening it:
- note the serial number, model and BIOS version from the BIOS setup or the operating system;
- photograph the stickers on the bottom and on the board;
- on some platforms, vendor tools or utilities can read the BIOS region from within the operating system, though they rarely capture the whole chip.
None of these replace a programmer read, but they help you restore identity data if the chip turns out to be damaged.
Backing up the EC too
If the board has a separate SPI chip for the EC firmware, back it up the same way. ECs with internal flash need dedicated programmers, but when you have the tool, save that firmware too. A mismatched EC firmware can cause charging, keyboard or power-on problems that look like hardware faults — see EC/KBC Firmware: The Second BIOS in Your Laptop.
When the reads keep differing
Persistent differences between reads point to one of three things:
- Connection problems — the most common. Desoldering the chip usually ends them.
- Board interference — back-feeding wakes up parts of the board that fight the programmer. Isolating the chip's supply or desoldering it helps. The trade-offs are in SOIC8 Clip vs Desoldering: Safe BIOS Chip Programming.
- A failing chip — if a desoldered chip still gives different reads in a socket, it is unreliable. Save the most consistent read, note which areas differ, and replace the chip with a new one of the same type.
Example: the backup that saved the job
A technician writes a downloaded image to a laptop that would not boot. The board now powers on and shows the logo — but Windows refuses to activate, the vendor's support tool reports a different serial number and the network adapter has an address shared with another machine in the office.
Because two verified reads of the original chip were saved before writing, the fix is simple: open the original backup, copy the serial number, UUID, MAC address and licence table into the new image, write it again, verify and reboot. The laptop now behaves exactly as before the failure.
Without the backup, the technician would have had to reconstruct identity data from stickers — possible for the serial number and MAC, impossible for the licence key — and explain to the customer why their laptop's identity changed.
After writing: keep the backup
Even after a successful repair, keep the original backup. If the customer's laptop comes back months later, or the new image turns out to have a subtle problem, the original is your reference for what the board looked like before you touched it.
A one-page checklist
| Step | Done when |
|---|---|
| Board unpowered | Battery and adapter disconnected |
| Chip identified | Part number, size, voltage known |
| Two reads | Saved as separate files |
| Reads identical | Same SHA-256 hash |
| Content sane | Not blank, readable strings, correct size |
| Stored safely | Two locations, descriptive name, note |
FAQ
Is one read enough if the software says "verified"?
"Verified" after a read usually means the software checked its own buffer, not that a second independent read matches. Make two separate reads.
Do I need special software to compare reads?
No. Most programmer tools have a compare function, and every operating system has a built-in way to calculate a SHA-256 checksum, as shown above. Matching checksums are all the proof you need that two reads are identical.
Should I back up a chip that is obviously corrupted?
Yes. Corruption usually affects part of the chip. The undamaged parts — identity data, ME region, licence table — are exactly what you will want to transfer to a replacement image.
Can I share a customer's backup online?
Not without removing their personal data, and preferably not at all. Dumps contain serial numbers and other identifiers.
What if the chip cannot be read at all?
Check voltage, pin 1, clip contact and chip selection in the software. If it still fails off the board, the chip is probably dead; you will need a clean image and the identity data from the stickers.
Bottom line
Two reads, identical hashes, a sanity check on the content and two safe copies with descriptive names — that is the whole routine. It takes minutes, and it is what makes every later step in BIOS repair reversible. Keep those files for as long as you practically can: storage costs almost nothing, while a missing backup on a laptop that comes back months later costs hours. Only then move on to writing the new image.