Last resort only

Rule out everything else first. Re-seat RAM. Try different RAM. Try external display. Reset CMOS (pull the battery for 5 minutes). Try a different power adapter. Remove all peripherals. Remove the laptop battery and run on AC only. If Google reveals a common "blank screen" problem for your model, try the consensus fix before opening the chip. Reflashing from a programmer can break things in new ways if done wrong.

What you'll need

  • A CH341A USB programmer ($5–$15 on Amazon/AliExpress). Check the clones carefully — the popular "black" revision operates at 5V, which can damage 3.3V flash chips. Look for a revision that has a 3.3V jumper, or use a known-good 3.3V-only version.
  • A SOIC-8 test clip with 8 wires (often sold as a "Pomona clip"). Cheaper clips have alignment problems; expect to spend $10–$20 on a decent one.
  • AsProgrammer — open-source Windows programming app, GitHub releases. flashrom on Linux is an alternative if you prefer, but AsProgrammer is friendlier for a one-off repair.
  • The right BIOS image — see the "about BIOS files" section below.
  • Tiny Phillips screwdrivers, thin plastic spudger for the laptop case.

About BIOS files

The file the vendor ships as a "BIOS Update" for use with their own updater is not the raw chip contents. It's usually wrapped in a vendor-specific envelope that the updater tool unwraps and writes only the changed portion of the flash. A chip programmer writes the whole chip, byte for byte.

What you want is a full dump — someone else with a working machine has read the chip and posted the raw binary. Search BIOS-Mods forums, ROM.ru, or manufacturer-specific enthusiast sites for "$MODEL BIOS full dump". If the exact model isn't available, the dump from the same chassis with a different CPU/RAM SKU is often close enough because the board is identical.

For reference: the original version of this article was about an ASUS GL703GS. The BIOS chip is a Macronix MX25L12873F (3.3V, 128 Mb / 16 MB, 8-pin SOIC package). The stock 311 BIOS dump I used is somewhere on the modding forums; the direct link from the old post is long gone.

Step 1: Open the laptop

Every laptop is different — search YouTube for a disassembly video specific to your model. Key rules:

  • Machine is powered off and unplugged.
  • Disconnect the main battery connector from the motherboard before touching anything else.
  • Disconnect the CMOS (coin cell) battery too. This both removes power from the flash chip and ensures the board doesn't brown-out partway through a write.
  • Ground yourself (anti-static strap, or touch the chassis) before handling the board.

Step 2: Locate the BIOS chip

Look for a small 8-pin chip, usually near the chipset. It'll have a Macronix (MXIC) / Winbond / Micron / GigaDevice logo and a part number like MX25L12873F, W25Q128FV, or similar — the 25 part number prefix identifies the SPI flash family that CH341A can program.

Note the pin-1 indicator: a small dot or notch on one corner of the chip. Pin 1 is the reference for the test clip's orientation.

Step 3: Clip on

With the laptop fully powered down and both batteries disconnected, attach the SOIC-8 test clip to the chip. The clip's pin-1 wire (usually colored red) must align with the pin-1 dot on the chip. Plug the other end of the clip's ribbon cable into the CH341A programmer, matching the pin-1 marking on the programmer too.

Plug the CH341A into a Windows machine. Install the parallel-driver that ships with AsProgrammer before first use.

Step 4: Verify the connection

Open AsProgrammer. IC → Search, type your chip's part number, double-click to select. Then try reading a small region — if you see anything other than all-00 or all-FF, the connection is good. If you get all-00, the chip is unpowered; check the clip alignment. If all-FF, either the chip is genuinely erased (unlikely) or clip contact is poor.

Two more connection-integrity checks:

  • Protect / Unprotect the chip via AsProgrammer's IC menu. A bad connection hangs the operation; a good one completes in a fraction of a second.
  • Read IC twice in a row and compare the two dumps byte-for-byte. Intermittent connections produce different reads; a stable connection reads identically every time.

Step 5: Back up the current contents

Before you erase anything, read the chip and save the result to disk. Even if the machine is bricked, that dump tells you what's there — and if the blank you're writing turns out to be the wrong file, you have an escape.

# In AsProgrammer:
# IC menu → Read IC
# File → Save as → current-bios-backup.bin

# Verify the dump is the right size
# MX25L12873F is 16 MB, so the backup should be exactly 16777216 bytes
ls -la current-bios-backup.bin

Step 6: Erase, program, verify

  1. Erase IC — wait for "complete" in the status bar.
  2. File → Open — pick your replacement BIOS binary.
  3. Program IC — writes the file to the chip. This is the longest step (a couple of minutes for 16 MB on CH341A).
  4. Read IC — read back and compare. AsProgrammer shows a byte-for-byte hex view; the first and last non-zero bytes should match between the file you wrote and the chip contents.

Step 7: Reassemble and test

Remove the clip, reconnect the CMOS battery first, then the main battery, reassemble the case, plug in the charger, press power.

If it posts: success. Log into the machine and verify the BIOS version in dmidecode or the system info UI matches what you flashed.

If it still doesn't POST:

  • The BIOS file might be wrong for this exact SKU — different CPU/chipset variants sometimes share a board but need different firmware.
  • The chip might be physically dead (rare but happens if it was already wounded before you started). Replacement MX25L12873Fs are a few dollars on DigiKey.
  • There might be something else wrong that isn't the BIOS — a bad capacitor, a damaged chipset, a failed GPU. The programmer can't fix any of those.

A warning about vendor updater drivers

Some ASUS and other OEM BIOS update flows install a kernel driver that periodically re-flashes the chip back to the vendor's intended firmware. If you're modding a BIOS (unlocking hidden options, disabling Intel ME, etc.) and the machine keeps reverting your changes after a reboot, look in Device Manager under Firmware and remove the "BIOS Update" driver.