@jhong - What is that image of, using Raymond.cc method? If you do not care about serial, UUID etc I can swap BIOS regions for you.

Or give me your serial off bottom of case, and then also the output of these two commands in command prompt, maybe then I can find in BIOS and edit into the swapped BIOS region.
wmic csproduct get uuid
wmic baseboard get serialnumber

Really Thanks

Imag file following Blog is LF1 of bios version 2.13

I just put a SPI to target haha;;

then, Command result is here

wmic csproduct get uuid
UUID
E38E744C-203A-11B2-A85C-E7074E26809C


wmic baseboard get serialnumber
SerialNumber
L1HF68Y00D0

And I have a Question...

How you make a custom bios...?

I am really wonder method

Do you recommend reference or blog?

@jhong - thanks for board detail info, will work on this for you shortly. Do you get error using 2.20 and Raymond.cc method?
Method is very involved, I do not know of any guides or blogs. I use hex editor and UEFITool. I found your serial in ME region, and within second VSS2 region (NVRAM)
Volumes must be cut/removed from the stock image, then any edits made like below, then cut/edit region replaced into dump to swap region (or individual volumes will need swapped out after).
So even without putting back in board details etc, it's not a direct swap from FL1 file to dumped BIOS region.

This info along with serial @ ME region

@1D24F0

3230465743544F315757 = 20FWCTO1WW Also @ 239000 block

53444B304A34303730392057494E = SDK0J40709 WIN

4C31484636385930304430 = L1HF68Y00D0

UUID, scrambled @ 239000 block
4C748EE33A20B211A85CE7074E26809C / 4C748EE33A20-B211-A85C-E7074E26809C

Also @2387D0 - 4C748EE33A20B211A85CE7074E26809C

For your LAN MAC ID, this will be safe always with BIOS region swap, it's outside BIOS region, but copy is stored in VSS2/NVRAM, however this probably gets written in after startup even from stock blank VSS2/NVRAM module
From GbE in main dump LAN MAC ID
C8:5B:76:5A:6F:1D
C85B765A6F1D

^^ Also found at VSS2 inside BIOS region @3738h - unicode
Additionally UUID inside VSS2 @37C5h - 4C748EE33A20B211A85CE7074E26809C

Will work on swap tonight for you

* Edit - @jhong - Here is mod BIOS, hopefully should be working! It took MANY Edits to get that swapped around proper, and even a single edit gives error in UEFITool NE parser "BG Protected Ranges Hash mistmatch - image may refuse to boot"
I see that often in edited BIOS, usually OK, but like I mentioned if Boot Guard is active and burned in on the FPF side to chipset then this or any edit will fail due to active bootguard. Remember I asked you to check, but you never provided MEInfoWin image output.
http://s000.tinyupload.com/index.php?fil...129479966720422

Now!! I am searching MEInfoWin.exe File

but I can'd find it and download ㅠㅠ

I linked you to thread, it's ME System Tools packages, see post #8

I think mabe it's not correct...


I guess rewriting SPI image is reason of the error

(edit) checking bios setup of ME Version is empty... ! hmm

MEInfoWin64.exe

Intel(R) MEInfo Version: 11.8.60.3561
Copyright(C) 2005 - 2018, Intel Corporation. All rights reserved.

Error 86: Communication error between application and Intel(R) ME module (FWU client)

Error 81: Internal error (Could not determine FW features information

Check ME FW version on main page of BIOS, if you do not see it, or you see ME FW NA or 0.0.0.0. then it's corrupted. Your BIOS may not show this anyway, in that case check with HWINFO64, in large window, on left, in motherboard section, expand and see ME section, then look for ME Firmware
https://www.hwinfo.com/

You need to know the ME FW first, before you know which package to download to get the proper MEinfoWin from (they are version specific), and ME drivers need to be installed too so download and install those from your motherboard page if not already installed.
So, whatever you ran above may not be correct MEInfoWin version anyway, aside from if you have drivers installed yet or not, or if ME FW is corrupted etc.

Or, you can also download this Intel Spectre/Meltdown checking tool, run it and at the bottom you will see ME FW info (May not work without ME drivers installed, unsure)
http://s000.tinyupload.com/index.php?fil...835653541375528

Never mind, I see in your original BIOS Dump, it's ME 11.8, so I think you have the correct package. Install ME drivers from Lenovo page for your system and then try again
In the end, yes, you may have corrupted ME FW - that will be fixed once you re-write any known working BIOS via programmer

I checked Intel SA tool and resulte is

engine version is 11.8.50.3425


Yes I agree with your opnion, If ME FW have corrupted, can re-write and patch to variety of method

Please re-write any known working BIOS you have and then run MEInfoWin, after install ME drivers first. Then we can check if bootguard is enabled or not.
But, since you have programmer it's really no worry, if BIOS edit is blocked due to that, you can reprogram other BIOS, so you can go ahead and program in the BIOS I modified for you above and see if it works or not.

I have a question.

If I install Intel Me version lower than 11.8 then, re-write edited bios, bios boot have problem?

If you re-write BIOS with programmer, then whatever version is in that BIOS will be the version being used, and it wont matter what is on there before. As long as you change the ME version properly, using the clean ME settings transfer guide.

I don't think you can go too low, maybe 11.6, or possibly 11.0, but I would try 11.6 first. Why do you need lower than 11.8 anyway? You never mentioned any of this until now? I could have changed to other ME in the mod BIOS I sent.

It's easy to upgrade, but it's hard to downgrade hahah

I installed Intel ME Driver and check the MEInfo

I think boot guard is disable, aren't you?

"Intel(R) Manageability and Security Application code versions:

BIOS Version R07ET79W (2.19 )
MEBx Version 11.0.0.0010
GbE Version 0.8
Vendor ID 8086
PCH Version 31
FW Version 11.8.50.3425 H
Security Version (SVN) 3
LMS Version 11.0.0.1173
MEI Driver Version 11.0.0.1172
Wireless Hardware Version 2.1.77
Wireless Driver Version 20.10.2.2

FW Capabilities 0x7DF65145

Intel(R) Active Management Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Service Advertisement & Discovery - PRESENT/ENABLED
Intel(R) Platform Trust Technology - PRESENT/DISABLED

Re-key needed False
Platform is re-key capable True
Intel(R) AMT State Enabled
AMT Global State Enabled
TLS Enabled
Last ME reset reason Global system reset
Local FWUpdate Enabled
BIOS Config Lock Enabled
GbE Config Lock Enabled
Host Read Access to ME Disabled
Host Write Access to ME Disabled
Host Read Access to EC Disabled
Host Write Access to EC Disabled
SPI Flash ID 1 EF4018
SPI Flash ID 2 Unknown
BIOS boot State Post Boot
OEM ID 4c656e6f-766f-0000-0000-000000000000
Link Status Link Down
System UUID e38e744c-203a-11b2-a85c-e7074e26809c
MAC Address c8-5b-76-5a-6f-1d
IPv4 Address 0.0.0.0
Wireless MAC Address e4-a7-a0-04-a4-57
Wireless IPv4 Address 192.168.230.12
IPv6 Enablement Disabled
Wireless IPv6 Enablement Disabled
Privacy/Security Level Default
Configuration State Completed
Provisioning Mode PKI
Capability Licensing Service Enabled
OEM Tag 0x00000000
Slot 1 Board Manufacturer 0x000017AA
Slot 2 System Assembler 0x00000000
Slot 3 Reserved 0x00000000
M3 Autotest Disabled
C-link Status Enabled
Wireless Micro-code Mismatch No
Wireless Micro-code ID in Firmware 0x24F3
Wireless LAN in Firmware Intel(R) Dual Band Wireless-AC 8260
Wireless Hardware ID 0x24F3
Wireless LAN Hardware Intel(R) Dual Band Wireless-AC 8260
Localized Language Korean
Independent Firmware Recovery Disabled
EPID Group ID 0x1FAB
LSPCON Ports None
5K Ports None
OEM Public Key Hash FPF 0000000000000000000000000000000000000000000000000000000000000000
OEM Public Key Hash ME 0000000000000000000000000000000000000000000000000000000000000000
ACM SVN FPF 0x0
KM SVN FPF 0x0
BSMM SVN FPF 0x0
GuC Encryption Key FPF 0000000000000000000000000000000000000000000000000000000000000000
GuC Encryption Key ME 0000000000000000000000000000000000000000000000000000000000000000

FPF ME
--- --
Force Boot Guard ACM Disabled Disabled
Protect BIOS Environment Disabled Disabled
CPU Debugging Enabled Enabled
BSP Initialization Enabled Enabled
Measured Boot Disabled Disabled
Verified Boot Disabled Disabled
Key Manifest ID 0x0 0x0
Enforcement Policy 0x0 0x0
PTT Enabled Enabled
PTT Lockout Override Counter 0x0
EK Revoke State Revoked
PTT RTC Clear Detection FPF 0x0
"

No, it's easy to downgrade too when you have programmer, but only to a certain extent, some BIOS you can't put super old ME into. For sure you can't go from ME 11 to ME 10 for example.

Yes, Boot Guard cannot be active on this machine now, it's not burned to FPF side
>>>>>>>>> FPF Side >>> ME Side
Measured Boot Disabled Disabled
Verified Boot Disabled Disabled

So you are OK, go ahead and test the BIOS I sent you, if it fails then either due to my modifications or some RSA type check like HP has.
If it fails, we can make a single settings change to your dumped BIOS and test to see if that also fails, then if so we'll know some RSA type security check is ran on BIOS start

Really Thanks!! Downgrade Success 2.13 ver ...

But Unfortunately.. I can't find DCI enable options of bios,

i have changed UEFI Variable of DCI enable also not operated : ( ㅠㅠㅠ
[https://gist.github.com/eiselekd/d235b52...c6b3912731ab9b2]

Then.. I am desperate..

What do you think I make a FIT IMAGE to enable DCI ...??..

Founded Material explain method that make a FIT IMAGE ..

ps. IMAGE