The CH341A is the cheapest way into BIOS work: a small USB programmer that reads and writes almost any 25-series SPI flash chip. It is slow and has a couple of hardware quirks, but used carefully it does the job on most laptop boards. This guide walks through a complete read-and-write cycle and the mistakes that cause most failures.

What you need

  • A CH341A programmer. The common black or green boards with a ZIF socket.
  • A SOIC-8 test clip with cable, for reading in circuit.
  • A 1.8 V adapter if the chip is a 1.8 V part.
  • Software. Options include the original CH341A utility, community tools such as NeoProgrammer and AsProgrammer on Windows, and flashrom on Linux and macOS.
  • The chip's datasheet — at least to confirm voltage and size.
  • Magnification to read the marking and see pin 1.

Know the hardware quirk first

Many CH341A boards, especially the common black version, power the chip from 3.3 V but drive the data lines at about 5 V. Most 3.3 V chips tolerate it for short sessions, but it is outside specification and risky for 1.8 V chips, which must never be connected directly. Options:

  1. Use a 1.8 V adapter for any 1.8 V chip — always.
  2. Modify the programmer so the data lines run at 3.3 V (well-documented community mods exist).
  3. Buy a version that already runs the logic at 3.3 V.

When in doubt, check with a meter: measure the voltage on the clock or data pin of the socket while the software reads.

Step 1: prepare the board

  1. Disconnect the adapter and the battery. Remove the CMOS battery too if the board is out of the chassis.
  2. Find the BIOS chip with the boardview or the schematic — see What Is a Laptop BIOS Chip and Where to Find It.
  3. Read its marking and look up the datasheet: capacity, voltage, package.
  4. Note pin 1 on the chip (dot or notch) and on the clip (usually the red wire).

Step 2: connect — clip or desolder

In-circuit with a clip is convenient but the programmer also powers part of the board through the chip's VCC pin, and other devices on the SPI bus (PCH, EC) can interfere. Desoldering gives the most reliable reads. The trade-offs are covered in SOIC8 Clip vs Desoldering: Safe BIOS Chip Programming. For a first attempt, the clip is fine; if reads are inconsistent, desolder.

Attach the clip with pin 1 to pin 1, pressing straight down until all eight contacts grip. Plug the clip's other end into the programmer's 25-series side, again with pin 1 aligned. Then connect the programmer to USB.

Step 3: detect and read

  1. In the software, run "detect" or read the chip ID. The software should recognise the manufacturer and size. If not, recheck the clip.
  2. Select the correct chip model if the software asks — match capacity and family.
  3. Read the chip and save the file, for example LA-D312P_original_read1.bin.
  4. Read it again and save as read2.bin.
  5. Compare the two files. Most tools have a compare function; otherwise compare checksums. They must be identical.

If the reads differ, the connection is unreliable. Reseat the clip, shorten the cable, try lowering the speed if your software allows, or desolder the chip. Never write anything until you have two identical reads. Why this matters is explained in How to Back Up the Original BIOS Before Flashing.

Step 4: check the dump

Before replacing the content, look at your original read:

  • Is it all FF or all 00? The chip may be blank, unreadable or not connected properly.
  • Does it contain readable text such as the BIOS vendor, model name or version? Search for them in a hex editor.
  • Is it the expected size? It should exactly match the chip capacity.

Keep this file safe forever. It holds the serial number, MAC address and other data you may need to transfer to a replacement image.

Step 5: prepare the file to write

The file you write must:

  • be exactly the chip size;
  • be for the same board code and, ideally, the same revision;
  • have your board's own data restored where needed — serial numbers, MAC address, and on Intel boards often a clean ME region.

Writing a raw vendor update file almost never works; those files are packaged differently from a full chip image.

Step 6: erase, write and verify

  1. Erase the chip (most tools do this automatically before writing).
  2. Write the prepared file.
  3. Verify — the software reads the chip back and compares with the file.
  4. Do a final manual read and compare with the written file.

If erase or write fails while reads work, the chip's write protection may be active; see the status register guide in the BIOS section.

Step 7: reassemble and test

Remove the clip, reconnect the CMOS battery and the main battery or adapter, and power on. The first boot after a BIOS write can take longer than usual while settings are initialised, and the board may restart once or twice. Give it a minute before deciding it failed.

A worked example

A laptop died during a BIOS update: rails are present, the fan spins, the screen stays dark. The board uses an 8-pin SOIC chip marked 25Q128JVSQ — a 16 MB, 3.3 V part according to its datasheet.

  1. With the battery and adapter disconnected, the clip goes on pin 1 to pin 1. The software detects a 16 MB Winbond chip.
  2. Two reads produce identical files. A hex editor shows mostly valid-looking data at the start but a large block of FF in the middle where the BIOS region should be — consistent with an update interrupted while writing.
  3. A dump for the same board code is downloaded from the catalog. Before writing it, the technician copies over the board-specific data from the original read: serial number area, MAC address, and on this Intel board a clean ME region is used.
  4. The prepared file is written and verified, then read back once more and compared.
  5. The board boots on the second attempt, after one automatic restart while it initialises its settings.

The whole process took under an hour, most of it spent on step 3. That preparation is the real skill; the programmer just moves bytes.

Common errors and what they mean

SymptomLikely cause
Chip not detectedClip misaligned, pin 1 reversed, board backfeeding, wrong voltage
ID reads as FF FF FF or 00 00 00No contact or no power to the chip
Two reads differUnstable connection, interference from the board
Erase fails, read worksWrite protection bits set
Verify fails after writeUnstable connection or failing chip
Programmer gets hotShort on the clip side or the board pulling heavy current through VCC

FAQ

Can a CH341A damage my laptop board?

Used carelessly, yes: the wrong voltage, a reversed clip or writing the wrong file can all cause damage or a dead board. Following the steps above keeps the risk low.

Do I need to remove the battery to use the clip?

Yes. The board must be completely unpowered. The programmer supplies the chip itself.

Why does the software show a different chip name than my marking?

Compatible chips share IDs, and the software may list a compatible model. Check that the size and voltage match.

Can I read EC firmware with a CH341A?

If the EC uses a separate SPI chip, yes, in the same way. ECs with internal flash need different tools.

Bottom line

Check voltage and pin 1, read twice and compare, keep the original dump safe, write only a properly prepared full image, and verify. The CH341A is basic, but with that discipline it handles most laptop BIOS chips reliably. Guides on the BIOS section list dumps by board code.