@Lost_N_BIOS Thank you for your respond and help to my problem. I used CH341A with software v1.29 to read the spi chip (25q64fv) of working unit and the broken unit. Here are the dumps and the manufacturer bios. I hope you can figure out why when I wrote the working unit dumps to broken unit spi chip, it could not work.
----------------
@Kirfve Regarding the test clip, it really depends on the nature of SOIC spi chip. You have to make sure that all clip pins can clamp the chip pins firmly. I tried several times but not successful yet so I soldered cables directly to chip pins to connect to CH341A

@Kirfve - yes, just as good as the black one, maybe a little slower to read/write. Access violation error happens with some versions of the software, and can be ignored, does not affect operation.
Probably that users green one was bad in some way? At least in my experiences they work the same, only green is a little slower.

* edit - @jsinfo2 - I also sometimes have connection issues with the clips, this is common due to cheap quality and BIOS were not really made to be accessed like this, plus it's very tiny space to connect.
Keep reclipping and you always get it. Some systems need power connected, and some need it fully removed too, all are different.

Are both of your units exact same model, and have exact same graphics cards? Hhave you ever erased the working systems BIOS and wrote it back? If you haven't, maybe your write back process is flawed and you just don't know this yet?
What is the BIOS chip ID you are trying to write to on the failing unit? If it's W25Q64FV, as I mentioned, you need to use software version 1.30 or 1.34 and W25Q64BV ID
If same chip on the working unit too, I would make a new dump with above info, and then try writing to the failed unit using that same info too. I've tested that chip a few times, above method is only way that works, at least with the general CH341A software (didn't test other software back when doing those tests)

It's not ideal way to fix BIOS on the broken system anyway, you'll have the serial, and LAN MAC ID from the other system. Serial copy may not be an issue, but with incorrect LAN ID the ethernet wont work
I can make you fixed BIOS for the non-working unit. Are you sure it's just the BIOS that failed? How do you know? How did it fail, I mean what caused the failure if you know? It may also need EC FW written to another chip

Please link me to the BIOS download package for this system, from Acer's site. I do not want it uploaded by you, and the above is not complete package anyway, this is why I always ask for manufacturer link

BIOS is configured to look for Storm2X64.fd BIOS On CD for recovery, so if you have the manufacturer install CD, you may be able to invoke recovery from the CD and some hotkey combo (you'd have to google brand and BIOS recovery method)
It may be possible to do it from USB too, with stock BIOS renamed that, but it's setup to look for CD for sure, so you may also be able to put on a CD if you do not have the original.

@Lost_N_BIOS Thank you for your additional info regarding the test clip.

Did you see that the dumps from working unit was corrupted?

They are same model units with same graphic cards. The chip is surely W25Q64FV.
I forgot to mention that I used software v1.29 and v1.30 to read the dump from working unit and the result bin files were identical. And after I wrote the dump to broken unit with v1.29, I did the verification too. Anyway since you have experiences that v1.30 and 1.34 are more stable, I will use them from now on. Can you share the link of v1.34 please?

Even if they are the same model with the same motherboard, is the EC FW different?

The broken unit was turned on and off repeatedly. I tested the electrical functionality and it looked fine. When I tried to write the dumps from working unit to broken unit, the laptop was always turned on but with no display. Therefore I think the possibility of bios problem is high. So I think I need to write to dump that is more specific to the broken unit with the specific information (I cannot figure out now). An unfortunately I dont have the recovery CD.

The manufacturer bios link is https://global-download.acer.com/GDFiles...BC=ACER&SC=PA_6

@jsinfo2 You soldered wires to the chip while it was still soldered on the board, and still didn't work?

@Lost_N_BIOS That is what I thought. Both uses the same IC. There is green versions with ICs that are newer than the black ones.
My test clip has a strong grip, but I only tested with 2 different devices (not desktop/notebook).
One had a cfeon qh16-104hip chip, and other had a mk 25d40btig chip. Despite the leds on both of them lit up, none of them could be read using multiple softwares.
Since they seem like "obscure" chips, I'm not that bothered. But I'm a little less confident that the programmer will work on my pc motherboard. (I cannot test it yet)

@jsinfo2 - You're welcome. No, I did not see anything immediately saying corruption on either, but I didn't dig deep due to assuming you used FV for the dumps and wanted to wait for new dumps using BV before I did anything.
that may only be critical to the writes, I forget since I tested long ago. I'd say try dump working unit again using 1.30 and BV ID, then write back to non-working using same, if that fails there is some other issue with the non-working unit, something shorted/burned out, or EC FW needs re-written as well.
EC should be same, but may vary depending on BIOS versions.

Broken unit turned on/off a lot, do you mean that is what messed it up? Here is CH341A package with 1.30 and 1.34 in there - http://s000.tinyupload.com/index.php?fil...695330485827902

Keep in mind what I mentioned, some systems need power connected, while others need it removed. So if you write and then dump, and file doesn't match, try with/without power and check again.
Be sure you use W25Q64BV to write to the FV chip, otherwise always a failed write from my testing on this chip.

@Kirfve - you'll probably have better luck in your pre-experiments if you use a desktop/laptop, or some other thing with common BIOS chips on it. Or you may just need to use correct/compatible version for those chips you mentioned, or some other software like ASProgrammer instead.

Zitat von Kirfve im Beitrag #409

---

@jsinfo2 You soldered wires to the chip while it was still soldered on the board, and still didn't work?

---

Zitat von Lost_N_BIOS im Beitrag #410

---

@jsinfo2 - You're welcome. No, I did not see anything immediately saying corruption on either, but I didn't dig deep due to assuming you used FV for the dumps and wanted to wait for new dumps using BV before I did anything.
that may only be critical to the writes, I forget since I tested long ago. I'd say try dump working unit again using 1.30 and BV ID, then write back to non-working using same, if that fails there is some other issue with the non-working unit, something shorted/burned out, or EC FW needs re-written as well.
EC should be same, but may vary depending on BIOS versions.

Broken unit turned on/off a lot, do you mean that is what messed it up? Here is CH341A package with 1.30 and 1.34 in there - http://s000.tinyupload.com/index.php?fil...695330485827902

---

Could be failed video card, or you need to also copy over the EC FW from the working board to non-working board too
Did you dump the BIOS after you wrote it and then compare to the file you wrote in hex, to make sure the write is 100% perfect? If not, check that now.

@jsinfo2, if you still have the thin wires connected to your BIOS chip, can you please tell us the voltage between pin 8 and pin 4? Thanks.

@jsinfo2 I don't have as much experience as other people in this forum but I think it's worth mentioning this.
While searching about the green CH341A, I saw that a technician got the same problem as you with the green programmer, the only difference was he desoldered the chip. The notebook would turn on but with no screen. He only got it working by writing the same bios file with another programmer (I think it was a TL866). So the problem might not be the hardware but the programmer.
Unfortunately he didn't shared the ic number (of his ch341a). I suspect it was very old tho.

@Lost_N_BIOS Yep! Thanks for the info!

@Lost_N_BIOS EC FW is located within BIOS Region or ME Region?

@Kirfve Thank you for the info

@nikey22 When we connected to programmer the voltage between Pin8-Pin4 : 3.28 V

@jsinfo2 - EC FW is on other smaller chip, 256KB-1MB chip usually, will look like BIOS chip

@Lost_N_BIOS I read you suggesting a lot that the motherboard may be powered on to get the programmer to read/write the chip. That made me curious... are you suggesting to just plug to the wall or also turning it on? Is there any danger? Wouldn't it damage the motherboard and/or the programmer?

@Kirfve - No, I never said power on any system to read/write the BIOS chip, NEVER do this!!!
What I said was some systems may need power cable and or main batter connected, not system powered on. Yes, just plugged in, not powered on. Some systems need that, others (most) do not

@Lost_N_BIOS I must have misinterpreted you then. I apologize.

So, just plug in if necessary, never power on, got it!

There is some devices that automatically power on when plugged in. Probably not a good idea to plug in those. That's something to be careful about...

@Kirfve - Yes, sorry, it's probably how I wrote it somewhere. I try to be careful and say it correctly, but maybe sometimes I forget and don't distinguish power connected vs powered on properly.

Yes, sometimes power plugged in may be required, and or main battery also if laptop. Usually not, so always try without first, until you are sure you may need to try with.
If something auto-powers on when plugged in, stop that from happening, or yes don't use this method on that device