I downloaded a 4750G BIOS from Acer and flash failed. I tried to flash with CH341A but failed. The downloaded BIOS file in the DOS folder has a file named JE40124.ROM which is 4096KB and a file named JE40124.WPH which is 2560KB. The BIOS chip is 25PX32VE, which is 4096KB so I tried to use CH341A with JE40124.ROM but not working just black screen. Should I try the smaller WPH file or some mod needed in order to flah with CH341A? I checked the winflash folder in TEMP folder which generated a BIOS.BAK file which is 2560KB and a BIOS1.WPH file which is 4096KB. I want to flash back the backup BIOS. Can I flash this small size BIOS.BAK directly with CH341A? Should I mod this small size backp file before flash with CH341A?
The backup BIOS generated in winflash folder.
http://www.filedropper.com/biosbak
The lastes BIOS file can be downloaded below. Which has ROM and WPH files in DOS folder.
https://global-download.acer.com/GDFiles…BC=ACER&SC=PA_6
Does the small size backup BIOS file flashable with CH341A?
@wizbee - I think you need to stop messing with BIOS 
This is second thread you have in a week for help with bricked BIOS, isn’t it? 
Send me a programmer dump of bricked BIOS original contents, before you did anything to try and fix. Is that what is in your first link? I mean, dump w/ programmer before you did anything, after it bricked (Or before that would be fine too)
Never mind, I checked this file, this is not a programmer dump. And no, this is not something you put on with programmer.
Is this BIOS.BAK what was created as a backup by Winflash before/during the update process that bricked the system, like a backup it makes before it starts to update?
If yes, then here, write this with programmer, once done, dump it and compare with this file in hex editor, if you do not get exact match then the write is failed and there is some issue with how you are writing to the chip as mentioned below
http://www.filedropper.com/bakfix
Same BIOS as above + Unlocked FD
http://www.filedropper.com/bakfixfd
If you are OK with loosing serial, UUID, and probably LAN MAC ID until you can fix it, then the JE40124.ROM may be bootable provided your write to the chip is correct (ie erase first, then blank check, the open file, write/verify)
Then once done, dump what you just wrote, and compare that in hex to the file you wrote, if it’s the same, it should boot. if it’s not the same, something is wrong in your write process, wrong software or version, try something else until you get a matched dump vs what you write to chip.
Ideally this is not the correct way to do things though, and this is only a “may be bootable” not all systems can boot like that, if BIOS you download from manufacture is only partial/upgrade.
This we can only tell by comparing against a dump from the BIOS before you erase/write to it with programmer, or from another system actual BIOS dump.
Problem solved. I read from another mb with CH341A and programmed with CH341A using Winbond W25Q32BV. This BIOS chip is more compatible with CH341A, I think.
The BIOS.BAK is in winflash folder which is a sub folder of TEMP folder. I checked the BIOS update log file which shows during update some offset cannot write error. Not sure whether it is due to corrupt BIOS chip or not compatible. I changed BIOS chip which is allowed in the schematics of this mb, and it works.
So, which BIOS did you write though? I’d suggest the one I made you above, if all I asked is true there, that way it contains your serial, UUID, LAN MAC ID etc.
I am using Asprogrammer 1.4. The ST chip was identified as M25PX32. I can programm but verify always fails. So I think it is not compatible with CH341A. The BIOS.BAK is generated when the BIOS update application runs. So it is the BIOS before update. But it is smaller in size than the rom file and BIOS chip.
b.t.w. have you figured out the BIOS menu confusion of my earlier thread?
Then do not use ASProgrammer, or pick the correct ID if possible. Try normal CH341A software, maybe 1.18 or 1.30 or 1.34
http://s000.tinyupload.com/index.php?fil…257455007472602
Then, the above BIOS I made above for you should be good to go, it would be your complete original BIOS contents before the brick occurred, and would have all your board specific info it it (while the stock one would not, if you programmed that in)
I meant to unlock the FD in it too, but forgot 
I don’t know about your other thread and where we are, I haven’t made it back there yet, always buried
The BIOS I dumped from other mb that has W25Q32BV BIOS Chip. The dump linked below. I am using this dump right now.
http://www.filedropper.com/4750
B.t.w. you are right about the CH341A tools. I downloaded your uploaded tool and flash and verify progress runs smoothly with the ST BIOS chip. Care upload the FD unlock one?
You can use any of these chips with the BIOS you originally posted
EF4016 (Winbond W25Q32)
C22016 (Macronix MX25U16)
BF254A (Microchip SST25VF032B)
EF3016 (Winbond W25X32)
1F4701 (Atmel AT25DF321A)
1F4700 (Atmel AT25DF321)
207116 (Micron M25PX32)
Did you use the BIOS I made you, from post #2? It doesn’t look like it, unless you edited it again?
That BIOS from post #7 has a trashed FD VSCC table (mainly this is incorrectly edited ME FW issue), this is what controls what BIOS chips are compatible with the BIOS and how
That also is a much older outdated ME FW too compared to the original one, I would not use that BIOS at all (Lucky it boots with FD/VSCC Table like that)
Use the BIOS I posted in post #2, I just edited and reuploaded it, with unlocked FD
Is it safe to use it on the Winbond W25Q32BV? The original BIOS is using on M25PX32
Yes, that chip is the first one in the VSCC table I posted from the BIOS above.