@Lost_N_BIOS Can you please advice wether you have any other suggestions for me?

If not I would update to the lates BIOS version and try to activate Windows alternatively.

Thanks!

@Spam00r - Very sorry! I just found this thread while looking at M92P dumps I had, and see you posted some replies I missed!

As to your question on post #15 about ME FW versions, I checked the file I sent you (in OGDump-Fixed package) and the file you originally gave me, both have ME FW version 8.1.65.1586 (you can confirm this in MEA tool)

Did you get activated? I checked the BIOS dumps you sent me, and I see this in regards to DPK, so looks like it never used DPK anyway (This is your dumped BIOS, already says No DPK in BIOS itself)
That may be from the BIOS update crash, or some interim thing is placed there and would have eventually replaced with your key if it had not crashed, I am not sure. Probably this, since it crashed mid-update and I simply fixed your BIOS by correcting a few bytes

@Lost_N_BIOS @Spam00r
Was the 10MB bios file modded?If so,run the fpt,it should get error 280.
So I am amazed that you flashed completed successfully.

@gloobox - this is old Aptio IV - probably safe to flash with AFU methods, I suggest the "Flash stock, then without reboot flash mod" method, before trying ES/GAN version
Spam00r was using flash programmer here, at first. But, this board has a 2pin service jumper, which unlocks it all, so that was also used later in this thread
So, you can put on jumper, dump BIOS, unlock FD, remove PRR lock, program back and then remove jumper and it will be all unlocked for FPT flashing provided you use that BIOS as your base moving forward it will remain unlocked.
To remove FPRR/PRR error, I posted the edit info here (may be different in your BIOS if it's not -9SKT9AA-7-2018-9sjt9ausa) - Lenovo M92P SFF, no post/video, 2 beeps.. (2)

@Lost_N_BIOS
Did you mean the services jumper is the ME_DIS jumper? (picture below)


If so,I tried many times to put on the jumper(would it be unlocked FD and removed PRR lock after putting on the jumper?)
Then I dumped BIOS,modded BIOS,flashed it back by fpt.but it still showed error 280.
The bios version is 9SKT70AUS.

Yes, that would be it @gloobox - this means Disable ME (and FD unlock) FPT error would only appear after you remove the jumper again. Please note, he mentioned you need to reboot twice with the jumper on before it's enabled.
Unless, there is some other "Service" jumper, I don't know for 100% sure, I don't have this board, only know what I see on page one (FPT Full flash confirmed at post #15) and that worked without issue @Spam00r - can you please confirm above is correct jumper

@Lost_N_BIOS
I just found an interesting thing that the whole bios I dumped by fpt was 10,485,760 bytes(command:fpt -d x.bin),but the bios I dumped by the spi programmer was 10,485,888 bytes(two bios file,one is 2,097,216 bytes,the other is 8,388,672 bytes).
I also want to mod the whole bios dumped by fpt.and split the it to 2 bios file,and flash it by the spi programmer.
And did you think anything wrong with this method?

@gloobox - Zip all that for me info a single package, so I can look at what you are seeing, and see if I can tell you why (It should all be same/same). Sometimes FPT will skip dumping a NVRAM volume in BIOS region, but it would replace that with exact same size padding instead.
Maybe (I think) your dump from programmer is wrong size due to software used or some choice made in software etc?

I have a few dumps from other users with programmer, and FPT, I checked and all are same size as expected -
10MB entire SPI dump from FPT or programmer (compiled) >> 10,485,760 bytes (A00000h)

2MB rom dump should be >> 2,097,152 bytes (200000h)
8MB rom dump should be >> 8,388,608 bytes (800000h)

It cannot be larger than those sizes for either chip, that is exact chip length and more cannot be written or dumped than that amount.

You can split it before you mod if you want, but it's not required and I suggest against that in this case due to where the split is (middle of BIOS volumes). Some tools could work with that, but it may cause corruption on recompile so I wouldn't do it that way.
Dump entire BIOS by FPT, mod it as you want, then split to flash back with programmer (or as whole with FPT) You only need to split the 10MB file if you plan to program it back with programmer.
Make sure you split at above mentioned size intervals, 8MB is first in 10MB FPT dump, 2MB last, and the split will be directly in the middle of BIOS volumes, so data will be present exactly at the cut

@Lost_N_BIOS
This link contains 10MB bios file and part of bios file and part of ME file.
I dumped them all by FPT.
http://s000.tinyupload.com/?file_id=01042046059794237776

This link just 2 bios files
http://s000.tinyupload.com/?file_id=72666155301176543479

Thanks!!!

These dumps are incorrect size as mentioned above >> LENOVO IS7XM 2 bios 9SKT70AUS
This is due to programmer/software issue, 64byte / 0x40h of FF padding added on end of each file. This is wrong, you cannot dump or write that much to these chips, so software/programmer issue

Other package contains correct sized files (FD/GbE/ME region + BIOS region) - if you split 10MB FPT file to program back, or after you edit as a whole to then program back, split at 0x800000h

@Lost_N_BIOS
Actually,I flash it back to the IS7XM mobo with the bios file of "LENOVO IS7XM 2 bios 9SKT70AUS".
It's well,with no any problem.The machine worked.

I'd try to dump it again by SPI programmer and see what would happen.

@Lost_N_BIOS
I feel so weird that I dumped it again by SPI programmer,the 8MB bios size was 8388608 byte,and 2MB bios was 2097152 byte.
But it proved that you are right.Thanks again!!!

edit:
What's more,I found something useful about flashing the bios.

Some of LENOVO H61 mobos(eg:LENOVO ciH61mi v1.0) were stuck in supporting 32nm CPU only.Someone could flash it forcibly with another brands bios which supports 22nm CPU.

Here is the link:
http://s000.tinyupload.com/?file_id=38770599935343911897

The route is:
1.Disable ME.(CHKME.exe)
2.Flash the new bios.

There is a batch processing(flash.bat) which could disable ME when running at the first time and flash the new bios when running at the second time.
What do you think about the CHKME.exe and RSTME.exe?Could it be useful for another mobos of LENOVO or even other brand's?

@gloobox - this is due to your software/dumping method, I've noticed all BIOS dumps you've sent me have same problem. Just use different software and then it will work properly.
As it was with how you were doing, it may write back in correctly, but I'd not even take that chance or waste time trying etc.

About the 32nm / 22nm thing you mentioned above, and flashing in some other brand BIOS. That may work, but wouldn't the more ideal thing be to do those same changes to the correct BIOS for that system?
I guess maybe full ME FW Major version may need updated from original system first, then do those mods, that may be why they're using some other BIOS model instead since it has the updated ME FW type.
But, since you're disabling ME FW, it may not matter, I would try that with the original model BIOS and see what is the outcome.

I don't have any opinion about chkme.exe, never heard of this. RSTME.exe never heard of either. If it's similar to ME Cleaner, not ideal way to do things, I'd prefer to use FITc when possible, and if you are disabling ME FW that can easily be done with FITx by changing one setting usually.
Ohh, I checked the download, I see now, these are OEM BIOS flashing tools. I think these are just temp ME Disable (or more likely FD Unlock/ME Disable) tools so you can flash BIOS or not via FPT, based on what I see in the batch file.
Probably only compatible with certain ME FW versions (V8) or certain chipsets. I don't see any brand checking in assembly, but text is limited there and doesn't look like much is going on, but it may be checking brand too and I don't recognize it.

Sorry I just saw your response now.

Yes I activated manually with a key.

It is possible that the BIOS never had a DPK. I never came around checking this before the BIOS crashed, as everything was running fine and Windows was activated before my troubles started.

Basically I have Installed windows once on a DPK activated Lenovo and than used that image to install it other lenovos. Actually this one M92p we are dealing in this post with still has a windows sticker, so it may be possible that this key was never embedded in the BIOS. But as I never had to eneter any key, I thought that windows took the key from the BIos. WIndows never asked me for a key up to now.

I think the windows not activated anymore came from doing too many hardware changes and not from the BIOS issues. Who nows? I ended up activating windows manually.

Also on my other Lenovos that have a DPK, WIndows gets deactivated after too many hardware changes and it does not activate itself.

I now also have a M92p that has no Sticker key and DPK. If I feel like it I will dum that units bios and flash it on the older M92p to check wether it will have DPK afterwards.

@gloobox : The jumper is the correct one and you have to reboot twice for Disable ME to work.

After the experience form this post I made FPT backups from all of my Lenovos. If something like this happens again, I will have backups. This is essential for the Lenovos as unlike with other boards, you can not just use the Bios file downloaded from the Manufacturer and flash it.

@Spam00r
Thanks!!!What is the " reboot twice " mean?
Was it the right route?
Once I short the jumper,launch the machine,enter the bios,and press "Ctrl+Alt+Del" to restart.And I should do it twice.
And then I could enter the DOS or Windows,and use FPT to flash the modded bios?