@snakeman - so, now you see both chips, did you mix them up before, and possible flash one to the other when you did your mod/reflash?
Both these dumps, as I said before, are incorrectly sized. I suggest you stop using whatever software you are using (Flashrom still?), it may mess up your write back and any write would fail possibly due to it trying to write more than chip can hold.
Use CH341A software in windows, you probably simply had bad connection or tried wrong version software before. What is the ID on both chips? Maybe I can test and tell you which software version works best for each, if I have them (or I can google around for you)

Here is fixed BIOS with FD Unlocked, updated ME FW, BIOS region is your originally dumped BIOS region (fixed for size). FD/ME goes into the 8MB chip, and BIOS region goes into the 4MB chip, be sure to program both back and into correct chips
You can only open the 4MB or 12MB compiled BIOS with UEFITool, other BIOS tools may be able to open either, but contents may not be displayed properly due to it would be a truncated/split BIOS File.
http://s000.tinyupload.com/index.php?fil...393494443795540

Once back and running again, you'll be able to use FPT to flash any region, you may still need to unlock BIOS and /SMI lock via grub or BIOS edit at AMITSE/SetupData Module
I disabled those by default in setup module, but not all BIOS use this, some use AMITSE/SetupData values, and others use NVRAM value, multiple tests of a single setting change would be required to find out which your BIOS is using.
If SMI/BIOS Lock still enabled, then one test done already, this one, setup edit, so that would only leave two other tests to find out which is used if this one still has those two settings enabled.

Never mind, for now, I am unable to find proper dance to do this setup module edit, no matter how it's saved, what else I remove with plans of adding back later, swap out entire volume at once, etc (I've tried 20+ things so far, using various methods and software, had to quit for now)
Anyway, no matter how I try to rebuild the BIOS will brick due to it removes a padding file directly above microcode module in that same volume. I will figure this out for you eventually so we can do the actual unlock mod, I hope, if not you'll have to do all changes you want via setup_var
If you got all your edits correct you tried to do before, and AMIBCP didn't kill the BIOS due to all I mentioned above (it would, I assume), then this was also probably an issue on your rebuilt BIOS file. You never sent it to me to check, so I can't be sure.
I assume it would have this issue too, since I haven't found a way around it yet

Once you are back up and running again, I can work on unlocking the BIOS for you, but I need those images I requested first, and if I can figure out a dance to get around loosing that padding file (let me know if you need image to show you which I mean)

@Lost_N_BIOS Thanks, I will give it a try.
I used your files With the windows software ver 1.29 same result.
I am surprised, they verify and everything,

Chips are as follows
4 mb chip MX25L3206E
8 mb chip MX25L6406E

Do you think I should try the files from Acer website? But, I will lose my ether address Windows Activation .......?

Here are the files from Acer


snakeman

@snakeman - If, you gave me a working, non-modified dump, which I think you did, and you wrote back both files I sent you to the correct chips, and it fails, then either something else is broken on the board at same time (it happens), or there is some software write issue (probably this).

No, stock BIOS should not be used for this, in any way, due to what you mentioned and more.

First, dump both chips again now with 1.30 and then send to me to check, in a single 7zip or zip/rar. Then write the files again with 1.30 instead of 1.29, with all power sources removed from the board, and be sure to erase and blank check before you write anything.

This post, the user seems to think chip needs to be removed from the board, but that shouldn't be a thing you have to do - [Guide] Using CH341A-based programmer to flash SPI EEPROM (12)
Ignore the 5V stuff they are discussing, it's not valid and does not relate to these issues anyway, only mentioning because if you see the discussion you might think it's valid info and or related (it's neither)
This 5v stuff is myth, well true in a way, internally, but none of the outputs are 5V, confirmed by this user check with DMM (and many others I've seen too).
Also, if you expand all the comments there, you'll see others writing to this same chip without issue and without removal mentioned too. Same for this guide, all writes done in place, same BIOS chips - https://www.chucknemeth.com/flash-lenovo-x230-coreboot/
They also say this one is best without power connected, so inline with what I said first below (ideal way to do all dumps/writes)
https://www.reddit.com/r/thinkpad/commen...isconnect_from/

Due to this discussion, remove the CMOS battery, remove the main battery, and remove the PSU, then try again with 1.30 after you send me the requested dumps.
Then if it still fails, try again with all three of those things connected (don't power on, just have it all installed). This should not be required, but on some systems it is the only way, try last

Another confirmed write OK and your same CHIP ID without chip removal here
[Guide] Using CH341A-based programmer to flash SPI EEPROM (20)
However, he had to use flashrom and have board power sources connected, but that's probably due to board design. This shows chip removal is not required though, and since you can ID chip with other software that also proves your OK there and don't have to use flashrom.
All boards are different when doing these things, due to how they're designed, some need power connected, some wont work with it connected, some need xxx software while others that wont work and you need to use zzz software instead.

More confirmation, I tested this exact chip before in the past too. Notice what I said about chip ID?? I'll have to check again, if you are not seeing those same things, I can't remember what was going on there, but since I mentioned those non exact ID's being detected it could be common.
Dell R720xd iDRAC BIOS recovery (2)

If you need me to retest these chips I can, but I'm not sure if I have any boards with this chip in place that are in working condition, of course that wouldn't matter I suppose, since it wouldn't be exact same as your board anyway.

** EDIT!!! - Looking around for recovery on this to see if others had issues, or if I could find use of CH341A and same chip ID on this system, no luck, but I found this which mentions a BIOS WP Protect jumper!
https://www.justanswer.com/computer/a204...f-computer.html

Please find and remove that jumper!

@Lost_N_BIOS V1.30 will not install at all, after the install I keep getting memory errors when detecting the chip. I rebooted tried many times no go.

I have a Dell XPS 8300 with the same chip "4 mb chip MX25L3206E" that will not erase or flash that's why I stopped trying on that one. Same problems as the links you pointed out to me.

At least this one erases and verifies that the flash as complete. This is truly strange. I therefore can not provide new dumps. Unkess you want the currently ones i flashed with v1.29.

First, none of these software you install, they are stand alone apps you run from the folder they are contained in. You can ignore the error you get, if it's the one I'm thinking of (Access violation I think), then detect chip

If you can't get it, then it must be the board, I can erase and flash these chips without issue. Did you see my last comment there, if's from user with your exact same system, there is a jumper stopping you

Verifying flash is complete means nothing, unless you can then close the app, open again, dump the chip, and then compare that dump in hex vs what you intended to write and it's a match.
These programs can verify a 100% FF or 00 write to a board, not always to be trusted, especially when you're running into "iffy" situations

@Lost_N_BIOS I can not find v 1.30 as a stand alone version still looking.


snakeman

@snakeman - Sorry for not linking my package, thought I already did previously
http://s000.tinyupload.com/index.php?fil...257455007472602

Did you find the jumper on the board yet?

@Lost_N_BIOS Yes I found the jumper no change.
That's the same version that i have all the errors from v 1.30 is not standalone its an install program.



snakeman