@Lost_N_BIOS I followed your advice and tried with 1.30 and 1.40. The results with 1.30 were very unreliable (verifying never worked) but 1.40 was an improvement, although not perfect. So this is what I did:
* 1 - With the motherboard disconnected from the PSU I read the contents of the BIOS, verified them and save them to a backup: 1_4_before.bin
* 2 - I disconnected the clip, removed the Programmer from the USB and waited for an hour.
* 3 - I reconnected the programmer and the clip, opened 1_4_before.bin and did a verification, the result was successful.
* 4 - Once again remove the clip and the programmer, but this time also connected the motherboard to the PSU.
* 5 - I booted up the motherboard, waited for a few seconds, shut it down and kept the power button pressed for a few seconds.
* 6 - Reconnected the programmer and the clip and tried to verify 1_4_before.bin once again: this time it was unsuccessful
* 7 - So, I read the BIOS, created a new backup 1_4_after.bin and compared it to 1_4_before.bin using Beyond Compare: there was a difference of 11KB out of 16MB.
* 8 - To try a different approach I repeated the steps 4 to 6, but this time I removed the RAM module and the mSata SSD. This time I opened and verified 1_4_after.binā¦ and it worked!
So, as you can see, for the first time I managed to get a consistent backup between boots. But I am still suspicious about its validity.
Answering your question, my BIOS is not corrupted. It is working as expected and I can boot up the OS without issues. What I am trying to do is to unlock some of the BIOS options using AMI BCPEdit. Is it possible to dump the BIOS using some application in the target machine so I can compare it to my latest backup performed with the programmer?
I uploaded both backups to https://www.sendspace.com/file/yqmqgr
Thanks a lot for your help!!
So, following on my last question, I downloaded AMI AFU for Aptio V to backup the BIOS from Windows. I used command: AFUWINX64 .\afu.bin /O . The result is a file of size 6M, instead of 16MB (size of the chip) No idea why the size is different.
Attachment for the backup created with AFU: https://www.sendspace.com/file/djuvlb
Probably NVRAM variable at time/date/checksum etc changing between steps 5-6, no need for that anyway. At step 8, maybe something related to those was changing in NVRAM, bootup times, boot order, power on count etc.
Software dump and programmer dump are always going to be different, mainly due to what all they will dump out for you, but also in regards to the stuff you found I mentioned above and you noticed in your testing.
Your AFU output is what I meant, sometimes you are locked out of certain regions of the BIOS with certain tools (Or with any/all tools), so in those cases you will only get a BIOS region dump, or ME dump, or ME+BIOS region dump, etc.
I checked the 6MB file and itās only the BIOS region. This maybe is due to how AFU works, Iām not sure, I never use it all that often.
In your dumps I see you have the FD fully unlocked, so you should be able to read/write entire BIOS with FPT (Intel Flash Programming Tool). This is what I would use to dump, then edit, then reflash, no need for programmer now that your FD is unlocked.
FPT is in Flash Programming Tools folder in the Intel System Tools package here in section C, you need v11
Intel Management Engine: Drivers, Firmware & System Tools
FPTw -d BIOSDump.bin << Dumps entire BIOS
FPTw -bios -d BIOSRegion.bin << Dumps BIOS region only (Main BIOS, contains the modules that you edit with AMIBCP)
FPTw -f BIOSname.bin << Flash entire BIOS
FPTw -bios -f BIOSname.bin <<< Flash BIOS region only
For safety, and for now, since you are only making AMIBCP changes, I would suggest doing the -bios region only, that way you do not touch Intel ME, since itās not being updated right now anyway.
Have anyone idea what is going on when reading Winbond 25Q128FV everything is fine. When Verifying reading it always have a error at 50%, same after write verify. Erase is OK it is turning every bit turn into āFFā.
Mobo: Asus ROG STRIX X99 GAMING
@raun0 - Try software version 1.29, I tested that exact chip for someone already here - Xeon E3-1240 v5 working with MSI Z170-A PC MATE but with bios reset on boot (3)
Many versions of the software in this package I put together, but for this exact chip I only tested 1.29 that day so I know it works - https://www.sendspace.com/file/gtcmvd
Hi guys, there is an alternative software for the CH341A
http://remont-aud.net/load/programmy/ch3ā¦23/13-1-0-64842 or https://4pda.ru/forum/index.php?showtopic=884713
Registration for download is required, good luck
Update Link:
https://www.mdclab.it/lab.html
Hi @gyrator
I like also to have more succes when programming on-circuit 
I would like to follow youre tip but to be sure about the wiring:
will the 3.3v on pin 4 and 8 be parallel ? so it is "powering" the chip but also the programmer ?
Or do I just power only the chip.
thanks in advance
@jeroenvtec
Well in my case I did not disconnect the 4 & 8 pins (from the test clip ribbon connector on the CH341 reader) so yes, it would have been powered in parallel. Some current supplied by the CH341A and supplemental current supplied by my DC power supply. I suspect that was why the DC power supply only need to provide about 600mA, the CH341A was probably providing another ~500mA or so. If I had modified the ribbon connector board to isolate those pins I couldāve just powered the 3.3V bus entirely from the DC power supply but I wasnāt looking to do any destructive modifications to my test clip or CH341A though, I just wanted a quick verification.
I shoved solid-core 24AWG telco cross-connect wires into the chip clamp at the locations that correspond to pins 4 & 8, and then inserted that ribbon connector board right alongside and clamped the thing down. The 24AWG telco wire is about the same thickness as the pin legs on that ribbon connector adapter board that came with my CH341A so when the clamp was closed neither would be loose. Then I used alligator clips on leads from my DC power supply to connect it to those telco wires. I powered up the CH341A and measured voltage. Then powered the DC power supply and turned V-hold to 3.3V and slowly raised current until voltage reached 3.3V. I had no problems reading the chip at that point, other than the test clip is VERY tempermental. You need to place it JUST right on those low-profile chips, they donāt make very good contact with the pin legs.
Your driver is not working (canāt install). Iāve used an old version Wootever had shared before with your flashrom 1.0 and it is working.
Here is the archive attached if anyone want to use it.
Flashrom_1.0_Windows.zip (259 KB)
I decided to register here so I could thank you all for the various alternatives for get the USB programmer to work.
I had a dead ASUS ROG GL552WV laptop and suspected the BIOS chip, because nothing else made sense. I got the Black USB programmer, and reading here, started to worry that Iād have to mod it to get it working, because it read the new chip I bought just fine, but I was getting all zeroes from the one on the board. This was using the CH341A.exe in Windows 7. I tried the flashrom for Windows, but it didnāt like something and wouldnāt work. So I went back to Ubuntu and tried flashrom there. It said No chip detected.
At that point, I was out of ideas, but something about voltage drops that was mentioned made me think I needed to supply power. So I got the laptop battery pack and plugged it in to the motherboard (which was out of the case since the BIOS chip is on the bottom), and tried flashrom again. This time it saw the chip!
I read the chip to a file twice, and the two files were the same. Then I wrote the data from the chip I had bought to the one on the board, and it verified. I put the pieces together enough to boot the computer and WOW that logo looked good! It took me into the BIOS because I had no disk drives attached. I shut down and put the computer together and Iām typing this on it.
So thank you, thank you, thank you. Using the 5volt programmer on a 3.3volt chip did not hurt it. Programming a chip while on the motherboard was possible once I attached the battery pack.
Now I wonder if Iāve done harm because I didnāt copy any MAC address or Serial number or UUID or anything from my old chip. I have no idea where to find those or how they are used. Is it just for Windows? I run Ubuntu on this computer and itās running fine.
@joyously - Do you have a backup from your old chip? If not, and you have not wrote over the old chip, make a backup from it and send me the file, I can get you those details. You may need to program them in again, but possibly it can be done via software.
Serial number and UUID are used for windows activation, and LAN MAC ID is used for LAN via Ethernet, without that your Ethernet wont work properly. If itās working now, then the LAN MAC ID is still there.
Yes, I have the backup (two in fact) of the old chip, but I did overwrite it (and could do so again).
Are there certain parts of a BIOS chip that are not writable? Or did mine work because Iām not using Windows? Iām using the wireless card to connect to my phoneās hotspot to be online. Is that considered Ethernet? There is no LAN here to test.
Iāll see if I can figure out how to send you a private message with the file.
@joyously - Ethernet LAN is the port on side or back of your laptop that you would connect Ethernet cable to wired to modem or router etc. I assume your internet is working now because you are using Wireless, which does not use the Ethernet or LAN MAC ID etc.
If you connect a cable to your router or modem, then that is what would probably not be working.
Yes, without flash programmer certain parts are not writable without FD manipulation previously or other methods. With programmer you can write 100% of the chip.
Checking PM now, did you send old original backup, and a new current backup? If not, please send both, so I can use old to get details and use new to put details back into, for you to reprogram.
I checked PM, only one file, need current backup as well please.
@mooms - thanks, but for this BIOS that does not work, details must be located and copied over manually
@joyously - Apologies for the delay! Here is two BIOS, one with 2nd padding only reinserted (This contains some system specific details), and second BIOS with 2nd padding + entire NVRAM volume reinserted (This would contain all original system details now).
http://s000.tinyupload.com/index.php?filā¦473715360738314
The second one may fail, if the original BIOS issue was a corrupted NVRAM entry or some other saved setting wrong in there. Program them on with programmer, and I would go ahead and try second one first in case itās fine, then youāll be all back to original details.
If that fails, I can try to copy out only the system specifics, but in this case due to failure that could take many individual tests.
I tried the second one and the first time, it failed to verify. I wrote it again and it verified. Then when I tried to boot (no drives), it flashed the green LED twice. I realized I had no memory. I put in one stick and it showed the BIOS, although it continued to flash the green LED four times. At this point, I noticed that the programmer had worked even though I forgot to hook the battery to the motherboard, so that theory is a little less clear.
The settings in the BIOS were set to have Secure Boot enabled, which I had never used. I donāt know if thatās a default, but it wasnāt set that way when I wrote the other version to the chip.
I guess itās workingā¦Iām going to put the computer back together again now. Thank you!
Failed to verify, verify what? Ohh, you mean with programmer, sounds like you need to get your method more stable, maybe pick better version of software?
Redo the programming if you think you need battery connected, otherwise it may not be properly written (Iāve seen verified fully 00 and FF writes and reads). Obviously some of itās there if it booted though 
I did not change any settings, reload optimized defaults and see if itās same, if it is then thatās the default, change it to whatever you want and all will be fine. Sounds like itās all working good now then, great!
Windows should now activate properly, and your Ethernet LAN will work too if you ever plug anything into it. Youāre welcome, and hop back in here any time if you need some help with BIOS edits!
Hey there,
I have replaced the motherboard of my ZBook 15 G1 with a new motherboard. Unfortunately I made a pretty stupid move and locked the manufacture programming mode before I realized I had to configure Intels AMT / V-Pro settingā¦therefor my machine is not in commited state.
So I decided to buy a CH341A (https://www.amazon.com/dp/B077ZBBMHN)and hook it up to the board to the Winbond 25Q128FVSQ. I removed RAM, HDD, DVD, front USB lights, card reader, main+cmos battery and tried to get a bios dump using software V 1.18, 1.29, 1.40. Non of them was able to detect or read the chip.
As this was my first attempt of dealing with a bios programmer I decided to try it with an defective ZBook 15 G2 board (pretty the same layout, same Winbond chip) and I was able to detect/read/verify it properlyā¦
Any hints what Im doing wrong?
Thank you!
Try with system plugged in, also before that try with CMOS and main battery installed too if you had not already tested with those left in previously. Try version 1.30, included in this package - https://www.sendspace.com/file/gtcmvd
And also try BV instead of FV when you do chip detect, that may not be necessary, or may not help, just something to try as I know this is required for W25QF64FV
And since this if your first round with the programmer, double check and ensure that you have everything connected securely and to the correct places
Here is a good guide with lots of images on how it all should be connected, thanks @junjo - https://www.bios-mods.com/forum/Thread-Gā¦341A-programmer
Using the power cord the chip was finally recognized and readable. Nevertheless I had to use version 1.18 to verify it because 1.29/1.30 always failed at 50%.
Lets see if I can work it out and somehow unlock mpm to get my AMT/V-Pro setting right. I believe mazzif wrote something about deleting the UUID would unlock the mpm.
Thank you very much for your assistance!