Which program should I be using on Winbond W25Q32BV for a Dell Inspiron N5110 bios? I'm having trouble getting the chip blanked to reflash it. I either did something wrong trying to fix the corrupt bios or I'm doing something wrong flashing new data

Hello,

Which program should I be using to flash a GIGADEVICE GD25B127DSIG (25B127) chip?
This is the BIOS in my CyberpowerPC Gaming laptop (I7, RTX2070) which is a barebones Quanta NL5E with both CPU & GPU soldered on.

I have downloaded the CH341A programmers versions 1.18, 1.34, 1.38 - but none of these have the 25B127 in the chip selection list.

Any help much appreciated.

Thx,

@pipes80 For W25Q64FV use 1.30 or 1.34 and choose W25Q64BV ID - Or Colibri -

Hope this help.

I have Alienware Area 51 R2. My board bios chip is Macronix MX25L12873F. I kept on getting same error on CH341a app with the correct chip model selected. It is hard to get a firm grip of bios chip using the clip. Clip keeps losing hold and bends pin in proximity. But I managed to have it grip the chip and stand by itself repeatedly. However when try to detect chip, I always get the same “Detection Fails” error. My programmer shows up in Windows device mgr correctly. I triple checked pin 1 is oriented correctly everywhere. I do not understand why it is so hard. Is it really not getting a good contact between clip and chip, or am I missing something? Which version of ch341a should I use?

“This error(s) is caused by the bad connection of the clip or by the wrong software version”

When I use ASProgrammer app, no error and appears to “read” but reads nothing back. The app still “reads” even when clip is detached from chip. How do I use ASProgrammer to check whether my chip is detected or not?

@xps630,
just 2 days ago I used AsProgrammer_2.0.0a14 on 2 MX25L12873F in my Z97X-SOC Force and both bricked BIOS chips reflashed successfully with stock BIOS.

How do I use ASProgrammer to tell the programmer clip is having good contact with bios chip? I was worried when ASProgrammer read was all blank even though it did not say error.

Hello

I've been trying to flash a Macronix MX25L12873F chip on a Lenovo IQ2X0IH board. I aquired a bios through vinafix.com.
I tried flashing with flahrom and a CH341a programmer but flashrom detected chip "MX25L12805D" or "MX25L12835F/MX25L12845E/MX25L12865E". I selected one of those options, even though it wasn't my chip and the flashing was succesful. I tried it and it booted one time perfectley but stopped booting afterwards.
I then read on the flashrom supported hardware page that that chip was not supported. So I tried with the windows programs: Ch341a v1.34 and AsProgrammer 1.4. The chip is identified, erased, and written, but fails on verification and of course, does not load.

Any help would be appreciated.

Thank you

@santivelez Instead of posting same content twice a forum search would have served you better:

Zitat von Lost_N_BIOS im Beitrag Two Bricked laptops!!!!

---

.......
For MX25L12873F use CH341A v1.31(1.4) (CH341AFree) (This is the name of the folder), ASProgrammer 1.4 or 1.41, or CH341A v1.1.1.32
All programs/versions mentioned above are included in this package - http://s000.tinyupload.com/index.php?fil...213094641136166
.......

---

@lfb6 I did do the search and already did all of that post, as it was one of the first I found. That's why I'm posting, cause it still doesn't work. Looking for help, not complains.

Most often the clip isn't in correct position. Other (rare) options would be a defective chip or too high current drawn from board, but the latter makes normally the CH341 'disappear'. Sometimes not used pins are on 3V or ground which the CH341 doesn't like. See this post for one possibility: [GUIDE] The Beginners Guide to Using a CH341A SPI Programmer/Flasher (With Pictures!) (3) (pic in spoiler)

What do the lights on the CH341 do? One LED on when connected, the other LED on when writing in addition- or are both LEDs on already when connected?

Did you do a 'blank check' after erasing? (At least Asprogrammer has the option)

Did you check the differences in the dumps? Complete blocks not read- single errors?

Zitat von lfb6 im Beitrag #640

---

Most often the clip isn't in correct position. Other (rare) options would be a defective chip or too high current drawn from board, but the latter makes normally the CH341 'disappear'. Sometimes not used pins are on 3V or ground which the CH341 doesn't like. See this post for one possibility: [GUIDE] The Beginners Guide to Using a CH341A SPI Programmer/Flasher (With Pictures!) (3) (pic in spoiler)

What do the lights on the CH341 do? One LED on when connected, the other LED on when writing in addition- or are both LEDs on already when connected?

Did you do a 'blank check' after erasing? (At least Asprogrammer has the option)

Did you check the differences in the dumps? Complete blocks not read- single errors?

---

Zitat von santivelez im Beitrag #641

---

The clip seems to be on the right position. If flipped it will not recognize the chip.

I didn't check difference in the dumps. Don't know how to do that part.

Still trying on different versions of all the softwares and not succesful. I'll keep trying.

---

Hi guys, this is my first post. I want to express that this is a fantastic community and there is some very valuable advice here. I was wondering if anyone would be able to help me out.

My laptop doesn't boot, black screen, fan spins for few seconds then nothing, no keyboard/mouse response or light, but the power light stays on indefinitely.

I've got a W25Q64FV bios chip. I had corrupted it last year when a bios update failed, so I got the CH341A programmer, programmed it, and revived my machine.

This time my machine didn't die on a bios update, it just didn't wake up from sleep. Anyhow, I thought I'd try a re-flash of the bios just in case because this machine has a history of struggling to boot.

I'm using a stock bin file from the manufacturer to write to the chip. This is the same file that I used to revive my machine previously. I've used both asProgrammer and the Chinese software and every time I write and verify, it seems to work 100%. Even if I disconnect from the chip, close the software, then reconnect and read, the dump is 100% identical to the stock file. That's fantastic. However when I try to boot up my machine again and it fails, the next time I go to read the chip, the dump has changed!

Is this to be expected? Is the bios dump supposed to be slightly different after an attempted boot?

I think my motherboard may be dead, but I thought I'd post here just in case I'm doing something wrong on the bios front.

Certain areas of the firmware aren't static. Post original bios and read back image.

Thank you for the insight, I thought I should compare the files in a hex editor. I'll take a look myself and post the files if I'm not satisfied. I just had another lifelong tech tell me it's 99% the motherboard given the symptoms, so I might just have to accept its fate.