Forum - RE: Latitude E6420. ME SpiLock failed after CPU change.

#31 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 1:21 pm (Last edited: Wed Mar 20, 2019 7:58 pm)

P.S. I fall in misunderstanding
I made FPT dump today, nothing were changed from yesterday, but dump different!
CH341A Programmer yesterday !Solved! !Image deleted!
CH341A Programmer today !Solved! !Image deleted!

FPT Yesterday !Solved! !Image deleted!
FPT today !Solved! !Image deleted!

So I have 4 same versions dumps from same laptop but every four lite different, What's happening?
Made FPT dump again, with 1 hour delay, it also different with other 4!

@Lost_N_BIOS
P.S.2. CPUDXE modded dump - no changes.
P.S.3. 5in1 modded dump - no changes
P.S.4! Something goes wrong, after this modded bios windows !turning of!, not shutdown, after few minutes. Dell bios reflash have not solve issue. Only hardware reflash with A07.

reply

#32 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 8:42 pm (Last edited: Sat Mar 16, 2019 8:47 pm)

@rustam2v - First dump was either modified or a broken/incorrect dump, per the issues I had that plutmaniac found the cause of, so since you say not modified then maybe you need to try other software version. What is your flash chip ID and what version of software are you using?
I'm surprised you can program that first dump back and it boots, I guess that's just luck maybe? Programmer can verify a completely blank (FF or 00) BIOS dump, so it's normal, mistakes happen sometimes, or always if given version is not best one for chip

Sorry, and never mind what I said before, I forgot and the differences are changes in NVRAM and time/dates etc, this would be normal, I was thinking more you meant actual BIOS region itself previously and forgot all about NVRAM, since you are comparing in hex not actual BIOS tools I bet it's this!

The issue plutomaniac found with dumped BIOS is odd, and shouldn't happen, it may be random or as mentioned may be due to you should use another software version instead.
Not all versions work best for any given chip, some need to use certain version and some even work better with incorrect ID selected

MEBx missing means ME is not loading as expected for these CPUs, since these are ES they may not be ME or AMT/MEBx enabled.
It's hard to say since you are not the original intended receiver of these so you wouldn't know what's enabled/disable/missing, some ES do not have certain functions that final production silicon have.

Due to that, I think disable ME next would be a good test!

Be sure you're running the MEInfoWin from Admin command prompt, it says that at end, maybe you need to get into windows instead of DOS if you are using DOS.
Definitely don't use Power Shell, here is how to run Admin command prompt. Select the folder that immediately contains MEInfoWin.exe, hold shift and press right click, choose open command window here (Not power shell).
if you are stuck on Win10 crap where this is now removed, here's how to get it back
https://www.windowscentral.com/how-add-c...creators-update
https://www.windowscentral.com/add-open-...menu-windows-10
https://www.laptopmag.com/articles/open-...ator-privileges

~~How did the tests of the two BIOS I sent in post #29 go, any changes with either, or all same?~~
Sorry, I missed your last reply until this posted! Thanks for report back! FPT dump differences are due to NVRAM changes and other normal things, sorry for any confusion I caused there.
When you first mentioned I thought you meant actual BIOS setup region/module, which wont change, no need to keep comparing like you are this isn't how you'd see what I thought you meant anyway.
Since both BIOS fail, yes, program back other BIOS instead, sorry I could not solve the issue like that Did you test them with ES CPU?
I asked because you mentioned windows shutting down, and I thought you couldn't boot windows, so wanted to be sure you check both of these BIOS with ES CPU to see if it boots past ME stuck location previously.

plutomaniac is best person to look at the MEInfo stuff, I don't see any immediate issue. I do see AMT link down, and two "invalid signatures" So maybe there is ME programming issues

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#33 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 9:30 pm (Last edited: Sat Mar 16, 2019 10:18 pm)

@Lost_N_BIOS DOS, Unix, BSD, my friendship with x86 starts with x88 ))) above 30 years ago. So well remember time when DOS & unix was only OS for PC. It will not problem to run any utilities from DOS or Uefi shell.
Of course I run Meinfowin64 from cmd (not PS) as admin. Log.text attached to latest post on 2nd page. But after me info -verbose something goescwrong, execution halts, after processe braking (Ctrl c) all Intel utilities stop functioning and became asking admin rights. Until reboot. Then I found, that windows unexpected turns off. Of course, I've test with ES CPU also, no changes
Now I reflashed with original A07, and looks like functioning normal, so I'll provide you correct Me info logs shortly.
EON EN25Q16
EON EN25Q64

reply

#34 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 10:20 pm

Thanks for the info. Yes, please run the MEInfo from DOS if windows continues to give you issues. And for those MEInfo's, these should be run with non-ES CPU, so the health of ME can be determined without ES CPU possibly causing any issues

Thanks for CHIP ID's, which software version are you using?

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#35 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 10:31 pm (Last edited: Sat Mar 16, 2019 10:45 pm)

I can't run Meinfo with with ES Cpu, because no chance to boot any environment, excluding BIOS Setup )))
With Meinfo situation same as before, -verbose half during execution, then any of Intel ME utilities become asking administrative right )))
Error 9470: Fail to load driver (PCI access for Windows)
Tool needs to run with an administrator privilege account.

Until reboot

C:\IntelTools\Windows64>meinfowin64 -fwsts

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

FW Status Register1: 0x1E000245
FW Status Register2: 0x70000006

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: Valid OEM data, ICC programmed

C:\IntelTools\Windows64>meinfowin64 -verbose

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

FW Status Register1: 0x1E000245
FW Status Register2: 0x70000006

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: Valid OEM data, ICC programmed

Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI

Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 23 (0x 17 ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes

Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI

Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 23 (0x 17 ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 21 (0x 15 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 11 ( 0x 0B ) found, size of 5 (0x 05 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 16 ( 0x 10 ) found, size of 15 (0x 0F ) bytes
Table Type 17 ( 0x 11 ) found, size of 28 (0x 1C ) bytes
Table Type 17 ( 0x 11 ) found, size of 28 (0x 1C ) bytes
Table Type 19 ( 0x 13 ) found, size of 15 (0x 0F ) bytes
Table Type 20 ( 0x 14 ) found, size of 19 (0x 13 ) bytes
Table Type 20 ( 0x 14 ) found, size of 19 (0x 13 ) bytes
Table Type 21 ( 0x 15 ) found, size of 7 (0x 07 ) bytes
Table Type 22 ( 0x 16 ) found, size of 26 (0x 1A ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 27 ( 0x 1B ) found, size of 12 (0x 0C ) bytes
Table Type 28 ( 0x 1C ) found, size of 20 (0x 14 ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 32 ( 0x 20 ) found, size of 20 (0x 14 ) bytes
Table Type 34 ( 0x 22 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 126 ( 0x 7E ) found, size of 26 (0x 1A ) bytes
Table Type 126 ( 0x 7E ) found, size of 26 (0x 1A ) bytes
Table Type 129 ( 0x 81 ) found, size of 8 (0x 08 ) bytes
Table Type 130 ( 0x 82 ) found, size of 20 (0x 14 ) bytes
Table Type 131 ( 0x 83 ) found, size of 64 (0x 40 ) bytes
MEBx Version found is 7.0.0.0063

Get ME FWU info command...done

Get ME FWU version command...done

Get ME FWU feature state command...done

Get ME FWU platform type command...done

Get ME FWU feature capability command...done

Get ME FWU OEM Id command...done

Error 1002: Failed to retrieve Intel (R) ME FW Version

FW Capabilities value is 0xDF65C65
Feature enablement is 0xDF65C65
Platform type is 0x1411
Intel(R) Manageability and Security Application code versions:

BIOS Version: A25
MEBx Version: 7.0.0.0063
Gbe Version: 1.3
VendorID: 8086
PCH Version: 4
FW Version: 7.1.91.3272
UNS Version: Not Available
LMS Version: Not Available
MEI Driver Version: 11.0.5.1189
Wireless Hardware Version: 2.1.71
Wireless Driver Version: 15.18.0.1

FW Capabilities: 0x0DF65C65

Intel(R) Active Management Technology - PRESENT/ENABLED
Intel(R) Standard Manageability - NOT PRESENT
Intel(R) Anti-Theft Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Intel(R) AMT State: Enabled

Get iCLS permit information command...done
Command response status indicates invalid signature

Get iCLS CPU allowed feature information command...error

Error 8203: Unexpected result in command response (Get CLS Allowed Feature Info)
Cryptography Support: Enabled
Last ME reset reason: Power up
Local FWUpdate: Enabled

Get BIOS flash lockdown status...done
BIOS Config Lock: Enabled

Get GbE flash lockdown status...done
GbE Config Lock: Enabled

Get flash master region access status...done
Host Read Access to ME: Disabled
Host Write Access to ME: Disabled
SPI Flash ID #1: 1C3017
SPI Flash ID VSCC #1: 20052005
SPI Flash ID #2: 1C3015
SPI Flash ID VSCC #2: 20052005
SPI Flash BIOS VSCC: 20052005
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000

Get Intel(R) AMT state command...done
Link Status: Link down

Get system UUID command...done
System UUID: 4c4c4544-0033-5110-8047-c8c04f465631

Get LanInterfaceSettings command for wired interface...done
MAC Address:
Get Provisioning Tls Mode command...done
d4-be-d9-40-bc-42
IPv4 Address: 0.0.0.0

Get LanInterfaceSettings command for wireless interface...done
Wireless MAC Address:
Get Provisioning Tls Mode command...done
24-77-03-87-3e-f4
Wireless IPv4 Address: 0.0.0.0

Get IPv6InterfaceStatus command for wired interface...done
Command response reports interface was disabled
IPv6 Enablement: Disabled

Get IPv6InterfaceStatus command for wireless interface...done
Command response reports interface was disabled
Wireless IPv6 Enablement: Disabled

Get privacy/security level info command...done
Privacy/Security Level: Default

Get provisioning state command...done
Configuration state: Not started

Get Provisioning Tls Mode command...done
Provisioning Mode: PKI
Capability Licensing Service: Enabled

Get iCLS permit information command...done
Command response status indicates invalid signature

Get iCLS permit information command...done
Command response status indicates invalid signature

Get iCLS CPU allowed feature information command...error

Error 8203: Unexpected result in command response (Get CLS Allowed Feature Info)

Get iCLS PCH allowed feature information command...error

Error 8203: Unexpected result in command response (Get CLS Allowed Feature Info)

Get iCLS PCH allowed feature information command...error

Error 8203: Unexpected result in command response (Get CLS Allowed Feature Info)
Get ME FWU OEM Tag command...done
OEM Tag: 0x00000000

Get System Integrator ID command...^C
C:\IntelTools\Windows64>

I'll try MEInfo from DOS or UEFI shell tomorrow

P.S.

Zitat von Lost_N_BIOS im Beitrag #32
Due to that, I think disable ME next would be a good test!

This about ME_cleanup?

reply

#36 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 10:52 pm (Last edited: Sat Mar 16, 2019 10:53 pm)

I thought so, only mentioned just in case you were able to run it somehow with the ES. Run it from DOS and see if you get same, take images with camera of output. It may be messed up, we'll have to wait until plutmaniac has a chance to see all your currently posted MEInfo outputs.

Also, ME FW is V7, you should be using V7 MEInfo tools, it looks like you are using V8, please try again with V7 instead and see if you have same issue

No, I did not mean ME Cleanup or ME Cleaner etc, I meant doing it properly via FITc, although yes you can try that but it's not what I meant.

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#37 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 10:55 pm

As i know, on Sandy Bridge and later not possible to disable ME absolutely, only AMT. Some ME components are part of platform initializasion. And I have thought about this before, and could't google any info, that some of 2nd gen. ES may come without ME. 1st gen. ES may, but for SB or later - no.

What is FITc? Show me the path.

reply

#38 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 11:03 pm

Zitat von rustam2v im Beitrag #35
..........
C:\IntelTools\Windows64>meinfowin64 -verbose
Intel(R) MEInfo Version: 8.1.56.1541
......
BIOS Version: A25
MEBx Version: 7.0.0.0063
.......
FW Version: 7.1.91.3272
.....

Wouldn't it be worth a try to use ME 7 tools? Or are ME 8 and ME 7 so close that this doesn't matter?

reply

#39 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 11:07 pm

Zitat von lfb6 im Beitrag #38
Zitat von rustam2v im Beitrag #35
..........
C:\IntelTools\Windows64>meinfowin64 -verbose
Intel(R) MEInfo Version: 8.1.56.1541
......
BIOS Version: A25
MEBx Version: 7.0.0.0063
.......
FW Version: 7.1.91.3272
.....
Wouldn't it be worth a try to use ME 7 tools? Or are ME 8 and ME 7 so close that this doesn't matter?

FK! You right! )))

reply

#40 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 11:16 pm

Lost_N_BIOS wrote it already- but I didn't re-check before posting- Sorry.

reply

#41 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sat Mar 16, 2019 11:26 pm (Last edited: Sat Mar 16, 2019 11:27 pm)

MEInfo

C:\IntelTools>meinfowin64 -fwsts

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

FW Status Register1: 0x1E000245
FW Status Register2: 0x69000006

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: Valid OEM data, ICC programmed

C:\IntelTools>MeInfoWin64 -verbose

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

Platform stepping value is 4

FW Status Register1: 0x1E000245
FW Status Register2: 0x69000006

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: Valid OEM data, ICC programmed

SMBIOS Table Data
Starting address: F2090
Table Size in Bytes: 4684 ( 0x124C )
Number of Table Entries: 107 ( 0x6B )
Virtual mapping of complete Table: 3 4kB Pages
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 23 (0x 17 ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes

SMBIOS Table Data
Starting address: F2090
Table Size in Bytes: 4684 ( 0x124C )
Number of Table Entries: 107 ( 0x6B )
Virtual mapping of complete Table: 3 4kB Pages
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 251 (0x FB ) bytes
Table Type 218 ( 0x DA ) found, size of 23 (0x 17 ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 21 (0x 15 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 11 ( 0x 0B ) found, size of 5 (0x 05 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 16 ( 0x 10 ) found, size of 15 (0x 0F ) bytes
Table Type 17 ( 0x 11 ) found, size of 28 (0x 1C ) bytes
Table Type 17 ( 0x 11 ) found, size of 28 (0x 1C ) bytes
Table Type 19 ( 0x 13 ) found, size of 15 (0x 0F ) bytes
Table Type 20 ( 0x 14 ) found, size of 19 (0x 13 ) bytes
Table Type 20 ( 0x 14 ) found, size of 19 (0x 13 ) bytes
Table Type 21 ( 0x 15 ) found, size of 7 (0x 07 ) bytes
Table Type 22 ( 0x 16 ) found, size of 26 (0x 1A ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 27 ( 0x 1B ) found, size of 12 (0x 0C ) bytes
Table Type 28 ( 0x 1C ) found, size of 20 (0x 14 ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 32 ( 0x 20 ) found, size of 20 (0x 14 ) bytes
Table Type 34 ( 0x 22 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 126 ( 0x 7E ) found, size of 26 (0x 1A ) bytes
Table Type 126 ( 0x 7E ) found, size of 26 (0x 1A ) bytes
Table Type 177 ( 0x B1 ) found, size of 12 (0x 0C ) bytes
Table Type 178 ( 0x B2 ) found, size of 76 (0x 4C ) bytes
Table Type 208 ( 0x D0 ) found, size of 16 (0x 10 ) bytes
Table Type 209 ( 0x D1 ) found, size of 12 (0x 0C ) bytes
Table Type 210 ( 0x D2 ) found, size of 12 (0x 0C ) bytes
Table Type 216 ( 0x D8 ) found, size of 9 (0x 09 ) bytes
Table Type 217 ( 0x D9 ) found, size of 8 (0x 08 ) bytes
Table Type 219 ( 0x DB ) found, size of 11 (0x 0B ) bytes
Table Type 219 ( 0x DB ) found, size of 11 (0x 0B ) bytes
Table Type 220 ( 0x DC ) found, size of 20 (0x 14 ) bytes
Table Type 221 ( 0x DD ) found, size of 19 (0x 13 ) bytes
Table Type 222 ( 0x DE ) found, size of 16 (0x 10 ) bytes
Table Type 255 ( 0x FF ) found, size of 6 (0x 06 ) bytes
Table Type 129 ( 0x 81 ) found, size of 8 (0x 08 ) bytes
Table Type 130 ( 0x 82 ) found, size of 20 (0x 14 ) bytes
Table Type 131 ( 0x 83 ) found, size of 64 (0x 40 ) bytes
MEBx Version found is 7.0.0.63

Get ME FWU info command...done

Get ME FWU version command...done

Get ME FWU feature state command...done

Get ME FWU platform type command...done

Get ME FWU feature capability command...done

Get ME FWU OEM Id command...done
FW Capabilities value is 0xDF65C65
Feature enablement is 0xDF65C65
Platform type is 0x1411
Intel(R) Manageability and Security Application code versions:

BIOS Version: A25
MEBx Version: 7.0.0.63
Gbe Version: 1.3
VendorID: 8086
PCH Version: 4
FW Version: 7.1.91.3272
UNS Version: Not Available
LMS Version: Not Available
MEI Driver Version: 11.0.5.1189
Wireless Hardware Version: 2.1.71
Wireless Driver Version: 15.18.0.1

FW Capabilities: 234249317

Intel(R) Active Management Technology - PRESENT/ENABLED
Intel(R) Standard Manageability - NOT PRESENT
Intel(R) Anti-Theft Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Intel(R) AMT State: Enabled

Get iCLS permit information command...done
Command response status indicates permit not found

Get iCLS CPU allowed feature information command...done
CPU Upgrade State: Upgrade Capable
Cryptography Support: Enabled
Last ME reset reason: Power up
Local FWUpdate: Enabled

Get flash lockdown status...done
BIOS and GbE Config Lock: Enabled

Get flash master region access status...done
Host Read Access to ME: Disabled
Host Write Access to ME: Disabled
SPI Flash ID #1: 1C3017
SPI Flash ID VSCC #1: 20052005
SPI Flash ID #2: 1C3015
SPI Flash ID VSCC #2: 20052005
SPI Flash BIOS VSCC: 20052005
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000

Get Intel(R) AMT state command...done
Link Status: Link down

Get system UUID command...done
System UUID: 4c4c4544-0033-5110-8047-c8c04f465631

Get LanInterfaceSettings command for wired interface...done
MAC Address: d4-be-d9-40-bc-42
IPv4 Address: 0.0.0.0

Get LanInterfaceSettings command for wireless interface...done
Wireless MAC Address: 24-77-03-87-3e-f4
Wireless IPv4 Address: 0.0.0.0

Get IPv6InterfaceStatus command for wired interface...done
Command response reports interface was disabled
IPv6 Enablement: Disabled

Get IPv6InterfaceStatus command for wireless interface...done
Command response reports interface was disabled
Wireless IPv6 Enablement: Disabled

Get privacy level info command...done
Privacy Level: Default

Get provisioning state command...done
Configuration state: Not started

Get Provisioning Tls Mode command...done
Provisioning Mode: PKI
Capability Licensing Service: Enabled

Get iCLS permit information command...done
Command response status indicates permit not found

Get iCLS permit information command...done
Command response status indicates permit not found

Get iCLS CPU allowed feature information command...done

Get iCLS PCH allowed feature information command...done

Get iCLS PCH allowed feature information command...done

Get iCLS PCH allowed feature information command...done

Get iCLS PCH allowed feature information command...done
Capability Licensing Service Status: Permit info not available

Get ME FWU OEM Tag command...done
OEM Tag: 0x00000000

C:\IntelTools>

reply

#42 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sun Mar 17, 2019 1:22 am (Last edited: Sun Mar 17, 2019 1:23 am)

The MEInfo log looks proper. The link will be down if AMT has not been provisioned by MEBx so that's also normal. Indeed you must use v7 tools, not v8. I would only use Flash Programming Tool from v8 if need be but it's not like you can't do your job just fine via v7. Personally I would try to remove all variables. For testing purposes only, I would use completely stock BIOS extracted from the HDR and if the ME might be causing issues, you can disable it by setting the "Reserved" (AltMEDisable) boolean at "Flash Image Tool > Descriptor Region > PCH Strap 10" from "false" to "true".

reply

#43 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sun Mar 17, 2019 6:06 am (Last edited: Sun Mar 17, 2019 6:08 am)

plutomaniac thanks for tips, and thanks for checking the ME logs too, I thought all looked OK but some I wasn't sure on and using incorrect tools/errors didn't help
We still also need to test older 206A2 microcode as well, sometimes latest/final (Since this latest is 2010) blocks ES from working too. Do you have any old copies, in case I can't find? If yes, please PM or link, thanks!
We may also need to test ME 7.0.xx enabled and disabled too, since there is something changed between 7.0 and 7.1 that Intel is wanting to block people from going back too.

@rustam2v ^^^ That is what I meant about disabling ME, via FITc, this is the Intel Flash Image Tool used to program/change ME internal settings etc.
I will build you BIOS for testing only as plutmaniac mentioned, you will loose serial, UUID during this test, but it's only to see if disable ME is the issue, or some other issues in NVRAM (Since current NVRAM will be wiped as well)

2nd gen. ES may come without ME. 1st gen. ES may, but for SB or later - no <<< You said, it contradicts itself 1st gen would be SB, Ivy second, and in any ES series for any CPU family there is often several types/versions/variants of ES as well.
And ME or any other feature can be disabled/bugged/broken for any ES, gen doesn't matter only what they enabled or not in the silicon. And any info you find on ES in regards to features/bugs/errata will be sparse since most/many using ES are supposed to be under NDA and do not often discuss things like this openly.

Here, please test this BIOS, put on by programmer, before doing this unplug all power from the board and short CMOS pins or remove battery for 1+ minute and press and hold power on button or short power on pins for 10-20 seconds, to drain all power from board.
Leave that way with all power drained for 1+ minute, this is to clear/reset ME state, I'm not sure if it's required when reprogramming with programmer etc, but since you're having ME related issues best to do it all to be sure.
Then program in this BIOS and test, this is stock A08 BIOS, region pulled from HDR, placed into your E6420_Q64+Q16_fix dump w/ FD unlocked and ME cleaned and disabled.
http://s000.tinyupload.com/index.php?fil...743596442218868

If this works, then next we enable ME and see if still working or not, then we'll know if CPU can't run ME.

** Please note ** I assumed this is 6 series chipset, Like QM67, (Not C600/X79), if this is C600 chipset system then do not use above BIOS, let me know and I will build again!

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#44 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sun Mar 17, 2019 12:58 pm (Last edited: Sun Mar 17, 2019 1:19 pm)

All utilities says QM67.
But something goes wrong with windows. It' became very unstable, and after attempt to return to restore point - only blue screen. Need to reinstall tomorrow to be sure, if this software issue or result of bios games.
By the way, this ES was installed into E6430 with Uma graphics (Ivy Bridge) - it was not start. Display dark, only led blinking. But it normal turned of, with single touch of power button, without long delay.

reply

#45 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sun Mar 17, 2019 3:04 pm

Zitat von Lost_N_BIOS im Beitrag #43
We still also need to test older 206A2 microcode as well, sometimes latest/final (Since this latest is 2010) blocks ES from working too.

Nah, 206A2 is an ES/QS CPUID so it doesn't make sense to block anything related to their operation. Well there is only another version which is the exact previous one but it's not worth your time trying it in my opinion.

Zitat von Lost_N_BIOS im Beitrag #43
We may also need to test ME 7.0.xx enabled and disabled too, since there is something changed between 7.0 and 7.1 that Intel is wanting to block people from going back too.

ME 7.1 was a different branch, at least initially. It added support for Intel Identity Protection Technology and theoretically OEMs could choose whether to keep 7.0 or use 7.1 for IPT usage. Later on they merged them into one 7.1 branch for simplicity. This is why the "Blacklist" entries at MEA show both 7.0 and 7.1 downgrade minimums. Anyway, that's beside the point. Basically you don't need to test anything ME 7.1 vs 7.0 related. For ME related things, I would either test disablement via AltMEDisable or maybe (very unlikely it'll do anything) just AMT disabling.

reply

Please enter a reason for warning.