Thanks, I already checked ME his board uses, well at least the current available ME. That's why I said we can't use FPT, ME FW is separately installed by exe, so there's no way for us to know what ME he's currently using without a full dump from his specific machine.
He needs flash programmer to fix this, now that you've updated guide and talked with me more about it, I'm certain that is the only way to fix this.

Hi Fellows,
first of all thanks to all the work and effort you both put already on this - kudos!!!
second - do you still want me to try to dump the FD or not?
third - regarding the replacement of the BIOS chip/s, that was done by a small service i ordered on the web
fourth - i have some more machines of this type, so i can definitely take some pictures of a board
that should not have any changes at all - i will be at home tomorrow and will do it right away when i am back

You're welcome, sorry this isn't an easy fix!
You need to order a flash programmer and SOIC8 jumper test clip cable.

ok - so dumping of the FD is not needed any more - right?
how about those two peaces - do they match what you recommended with your links to ebay?
https://www.amazon.de/dp/B0713V5GGL/?col...lv_ov_lig_dp_it
https://www.amazon.de/dp/B01H938PRK/?col...lv_ov_lig_dp_it

Yes, you can check if the FD is locked, but I already assume it is. Even with unlocked FD and ME regions, there's no way to re-write the ME because it needs to be done with the FW update tool and you cannot do that due to the current FW is corrupted.
FPT program can normally write to the ME, if the ME is contained in the BIOS, but your BIOS isn't made that way so it can't be used with FPT like a normal BIOS would in this situation.

Yes, those parts at amazon will work. But since you got the black/gold programmer be careful and only leave it connected to the BIOS chip for short periods (It sends out 5v and BIOS chips use 3.3V)

sorry - took me a while to find some free time ...
dumping the FD worked - at least i did not see any error

Looks like from your image there may be two BIOS chips on this system, one 2MB and one 8MB, the 2MB one probably contains a backup ME and FD or other recovery information.
You will need to be very careful once programmer arrives to not write anything to that 2MB chip until you get a verified backup of it so we can check and ensure it gets programmed correctly when correction attempts are made.

Your dumped SPI image contains ME 8.1.0.1265, and FD is all unlocked surprisingly, so you might be able to fix this with FPT before your programmer arrives.
Did you already have ME drivers installed in these systems? If not, I suppose you probably can't anyway, just curious if maybe that had something to do with MEinfowin not being able to give you any info. Maybe not, since BIOS shows N/A, that's usually corrupted or invalid ME somehow.

Here, is updated BIOS package with settings transferred and updated version ME that target BIOS came with 8.1.72.3002. But please wait until @plutomaniac can reply on this and tell you how to use via FPT, or if you must wait to use with programmer.
Plutomaniac, this is first time I've ever seen this happen, hope you don't mind to look this over for us, thanks! See image above, two BIOS chips, that's normal and size difference normal on some systems we all know.
But upon building clean image with FIT, outimage output was three files, 10MB matching his dumped SPI above, 2MB which I assume for the other chip, and 8MB outimage too.
I assume he can probably flash 10MB outimage via FPT to fix all this, or simply flash ME via FPT to fix, but I am unsure due to never seen this type of output with FIT, so asking you to advise what to do, thanks!
Maybe all due to "generate intermediate build files" being yes on the saved outimage 10MB I see when compared XML, I set to no for the initial config save
Here is 3 file output from clean settings transferred FIT routine.
https://nofile.io/f/HpTJHtCZCTO/Lenovo-M...+ME-Powerox.zip

Thanks again Plutomaniac!

Thanks plutomaniac, I assumed so, but wanted to check before having user flash!

@powerox - please download the package above in post #23 and using the 10MB file flash via command line using FPTw from FPT from system tools package 8 r3 using this command.
fptw.exe -rewrite -me -f outimage.bin

Then before closing command prompt run
fptw.exe -greset

System will power down and reboot, then enter BIOS and see if ME version shows correctly.

Hey Guys
thx for your help ...
just to ensure i am doing the right thing - the zip from post #23 holds 3 files [outimage.bin / outimage(1).bin / outimage(2).bin]
and you want me to flash the outimage.bin file - right?

Yes, as mentioned only the 10MB outimage.bin file using the two commands outlined above. I included all three initially because I was unsure and wanted plutomaniac to be able to check if he wanted when replying.
Sorry for the confusion!

fellows - good work!!!
i followed your recommendations and the intel-me is back and works perfectly
thx for your time and support

Great news @powerox - thanks for the quick report back and we're happy to see all is working properly now!

Hi ...
me again - i flashed also the second machine ;-) which pretty worked in the same way, but now i am having two machines with the same ethernet mac address ...
is this because i used the same outimage.bin ???