Forum - RE: Optiplex 7010 and VPro/AMT/ME

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Optiplex 7010 and VPro/AMT/ME

Page 3 of 11 � Page 1 2 3 4 5 6 7 ... 11 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#31 | RE: Optiplex 7010 and VPro/AMT/ME datum

Mon Aug 29, 2016 1:46 am (Last edited: Mon Aug 29, 2016 1:53 am)

@jwlu

I have created a modded ME image based on your dumped SPI image. It's only the ME region so fptw -rewrite -me -f me_mod.bin and after it's successful, fptw -greset.

plutomaniac has attached files to this post

me_amt_mod_7010_jwlu.rar

reply

#32 | RE: Optiplex 7010 and VPro/AMT/ME datum

Tue Aug 30, 2016 4:32 pm

Zitat von plutomaniac im Beitrag #31
@jwlu

I have created a modded ME image based on your dumped SPI image. It's only the ME region so fptw -rewrite -me -f me_mod.bin and after it's successful, fptw -greset.

Many thanks for your help.

I did:

1) SERVICE MODE jumper ON
2) flash ME Region in clean DOS: command "fpt -rewrite -me -f me_mod.bin" - successful
3) command "fpt -greset" in DOS - result: black screen and immediately reset
4) according to information from post # 29 I turned off SERVICE MODE (jumper OFF) and once again command "fptw64.exe -greset" (in Windows) - result: no errors and delayed correct system restart
5) clean CMOS (jumper RTCRST ON)
6) !!!success!!!: CTRL+P and MEBx activated and works correctly - BIG thank you Plutomaniac

I noticied two small 'problems':

Problem 1:
MEInfoWin64.exe run without any errors:

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

Intel(R) Manageability and Security Application code versions:

BIOS Version: A21
MEBx Version: 8.0.0.0072
Gbe Version: 1.3
VendorID: 8086
PCH Version: 4
FW Version: 8.1.70.1590
UNS Version: Not Available
LMS Version: 9.5.10.1628
MEI Driver Version: 9.5.15.1730
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available

FW Capabilities: 0x0DFE5C47

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

Intel(R) AMT State: Enabled
CPU Upgrade State: Not Upgradable
Cryptography Support: 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
SPI Flash ID #1: C22017
SPI Flash ID VSCC #1: 20052005
SPI Flash ID #2: C22016
SPI Flash ID VSCC #2: 20052005
SPI Flash BIOS VSCC: 20052005
BIOS boot State: Post Boot
OEM Id: 68853622-eed3-4e83-8a86-6cde315f6b78
Link Status: Link up
System UUID: 03000200-0400-0500-0006-000700080009
IPv4 Address: 172.29.19.115
IPv6 Enablement: Disabled
Privacy/Security Level: Default
Configuration state: Completed
Provisioning Mode: PKI
Capability Licensing Service: Enabled
Capability Licensing Service Status: Permit info not available
OEM Tag: 0x00000000
Slot 1 Board Manufacturer: Unused
Slot 2 System Assembler: Unused
Slot 3 Reserved: Unused
M3 Autotest: Disabled
Wireless Micro-code Mismatch: No
Wireless Micro-code ID in Firmware: 0x0082
Wireless LAN in Firmware: Intel(R) Centrino(R) Ultimate-N 6205
Wireless Hardware ID: No Intel WLAN card installed
Wireless LAN Hardware: No Intel WLAN card installed
Localized Language: Polish
Independent Firmware Recovery: Disabled

- but MEManuf reports errors :

Zitat

MEManufWin64.exe

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

Error 9328: Internal error

Error 9296: MEManuf Test Failed

- MEManuf in verbose mode:

Zitat

MEManufWin64.exe -verbose

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

FW Status Register1: 0x1E000245
FW Status Register2: 0x68000106

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

Get FWU info command...done

Get FWU version command...done

Get FWU feature state command...done

Get ME FWU platform type command...done

Get ME FWU feature capability command...done
Feature enablement is 0xDFE5C47
gFeatureAvailability value is 0x1

Request Intel(R) ME test result command...done

ME initialization state valid
ME operation mode valid
Current operation state valid
ME error state valid
Verifying FW Status Register1...done
OEM ICC data valid and programmed correctly

Request Intel(R) ME test result command...done
vsccommn.bin was created on 04:35:50 08/08/2012 GMT
SPI Flash ID #1 ME VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xC22017) ME VSCC value checked
SPI Flash ID #1 BIOS VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xC22017) BIOS VSCC value checked
SPI Flash ID #2 ME VSCC value is 0x2005
SPI Flash ID #2 (ID: 0xC22016) ME VSCC value checked
SPI Flash ID #2 BIOS VSCC value is 0x2005
SPI Flash ID #2 (ID: 0xC22016) BIOS VSCC value checked
FPBA value is 0x800
No Intel vPro Wireless device was found

Request Intel(R) ME Full BIST test command...done

Get Intel(R) ME test data command...done
Total of 33 Intel(R) ME test result retrieved

Policy Kernel - Power Package: Live Heap Test - Passed

Common Services - LAN: Connectivity to NIC in M3 - Passed

MicroKernel - Internal Hardware Tests: Internal Hardware Tests - Passed

Policy Kernel - ME Password: Validate MEBx password - Passed
Policy Kernel - Power Package: Package 1 supported - Passed
Policy Kernel - Power Package: Default package supported - Passed

MicroKernel - Blob Manager: Set - Passed
MicroKernel - Blob Manager: Get - Passed
MicroKernel - Blob Manager: Remove - Passed

Policy Kernel - ME Configuration: Wlan Power Well - Passed
Policy Kernel - ME Configuration: PROC_MISSING - Passed
Policy Kernel - ME Configuration: M3 Power Rails Available - Passed
Policy Kernel - ME Recovery: ME Recovery mode check - Passed
Policy Kernel - Embedded Controller: Power source type - Passed
Policy Kernel - SMBus: Read byte - Passed

MCTP - General: Connectivity to 3G using SMT1 - Failed
Error 9328: Internal error
MCTP - General: Connectivity to EC using SMT3 - Passed

Common Services - General: Low power idle timeout - Passed
Common Services - Privacy Level: Valid Privacy Level settings - Passed
Common Services - EHBC State: Valid Embedded Host Based Configuration (EHBC) sta
te - Passed
Common Services - General: Vlan not enabled on mobile - Passed
Common Services - Provisioning: Both PID and PPS are set - Passed
Common Services - Provisioning: MEBX password set when PID and PPS set - Passed
Common Services - EHBC State: EHBC and Privacy Level states compatibility - Pass
ed
Common Services - LAN: Connectivity to NIC in M0 - Passed

AMT - Power: Valid LAN power well - Passed
AMT - Power: Power-package 2 supported - Passed
AMT - KVM: USBr is enabled when KVM is enabled - Passed
AMT - KVM: Compare engine - Passed
AMT - KVM: Compression engine - Passed
AMT - KVM: Sampling engine - Passed
AMT - KVM: VDM engine - Passed
AMT - USBr: Hardware - Passed

Clear Intel(R) ME test data command...done
Get EPID Group ID command...done

EPID Group ID: 963

EPID GID Check passed

Error 9296: MEManuf Test Failed

- MEManuf with skip '3G test' run without any errors:

Zitat
MEManufWin64.exe -NO3G

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

MEManuf Test Passed

-as you can see the problem is the 3G (probably 3G modem) - how to disable the "3G mode" in the AMT?

Problem 2:
- in "Event log" of WEB interface AMT each time at start computer AMT writes three events (propably one Warning and two Errors) without any detail description:

What could be the cause of these events?

reply

#33 | RE: Optiplex 7010 and VPro/AMT/ME datum

Tue Aug 30, 2016 6:44 pm

I assumed you knew about the jumper since you provided a full SPI dump so that's why I didn't mention it. At step 4, you don't need a greset again after setting the jumper back. Also, step 6 was not needed for this ME reflash.

The 3G error is almost certainly due to the fact that I disabled Intel Anti Theft Technology at the ME firmware as it has been EOL since 01/2015 and can cause problems if left activated these days. The optional (OEM dependent) 3G NIC was used for Anti Theft only. It's Enabled/Disabled settings are set at the Flash Descriptor, as seen at FW Bring Up Guide, and not ME region or MEBx control panel. From what I read, this modded Flash Descriptor (FD) will do the trick even without using the "skip 3G" option at MEManuf (which is also an acceptable workaround for someone who doesn't want to reflash for some reason). With the jumper set to ON, the FPT command you need to use is fpt -rewrite -desc -f fd_mod.bin followed by fpt -greset for good measure even though the latter is not really needed for a FD reflash.

For the reported events, I don't really have AMT experience as I've never owned a 5MB/Corporate system but these events seem normal to me. Maybe a google search will help you in this case or even better, reading the AMT MEBx and WebUI guides found at the latest ME System Tools v8.x package.

plutomaniac has attached files to this post

fd_mod_7010_jwlu.rar

reply

#34 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Sep 02, 2016 2:02 pm

@plutomaniac

I have flashed "Descriptor region" in SERVICE_MODE (only "fpt -rewrite -desc -f fd_mod.bin" without "fpt -greset") - successfull: now MEManuf passes all tests without any errors - !!!Many Thanks!!!

By the way:
- Can I use modified by you flashes (files 'me_amt_mod_7010_jwlu.rar' and 'me_amt_mod_7010_jwlu.rar') in my another 'Dell Optiplex 7010' with identical hardware and BIOS version A21? (I have compared binary original 'ME region dumps' from this two computers and they are differs in many places)

- Can I in future do update BIOS using official 'DELL bios update'? Will there be a re-lock the AMT by overwriting the ME region?

Thanks a lot

reply

#35 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Sep 02, 2016 3:56 pm (Last edited: Fri Sep 02, 2016 3:58 pm)

Perfect, I have added the extra 3G instructions at the cleanup guide as well. It's perfectly normal for two ME regions from the same model, or even same system after a few reboots, to be different in many ways as the ME is not static firmware and keeps a lot of platform/system-specific initialization data.

- In theory, yes. Only the ME region though, not the full SPI image of one system (FD+ME+BIOS). I said "in theory" because Dell customizes the ME with settings requested upon ordering of the machine, usually AMT or No-AMT but maybe other things that I do not know. If it's just a matter of AMT or No-AMT then yes, you can safely use the cleaned/configured/updated ME region on all 7010 systems you have. As a general rule of thumb, I would play it safe and always follow the Engine Initialization DATA Cleanup Guide which is exactly what I did in your case as well.

- I don't see why not. As long as the jumper is set to SERVICE_MODE, the update procedure cannot change anything at the locked regions like FD and ME. So the ME cannot be overwritten. Besides, Dell in particular almost never overwrites the ME region because they tend to use FWUpdate tool + an RGN (stock, unconfigured) ME region to update during the BIOS update. Dell must be stupid if they have a check to not allow updating because the ME is newer or whatever. Bottom line, I think you will be just fine if any new BIOS update is released for that model. If not, we are here.

reply

#36 | RE: Optiplex 7010 and VPro/AMT/ME datum

Wed Nov 09, 2016 5:46 pm

Hello how about Optiplex 9020.. Having same issue can`t access vpro. Is any solutions ?

Thanks

reply

#37 | RE: Optiplex 7010 and VPro/AMT/ME datum

Thu Nov 17, 2016 5:58 pm

HI, plutomaniac
my PC is DELL T3610, INTEL AMT disabled,i want enable it and Clean the Engine Initialized DATA section ,but it's very difficult for me.
i do this fptw64 -d myspi_17.rom and fptw64 -d me_17.rom -me
could you help me ?
sorry for my poor english.
thank you!
files URL:https://pan.baidu.com/s/1kVHe6Cv

reply

#38 | RE: Optiplex 7010 and VPro/AMT/ME datum

Thu Nov 17, 2016 6:26 pm (Last edited: Thu Nov 17, 2016 6:27 pm)

@manjaki

Attach your full SPI image dump after setting the ME Service jumper. Check the rest of the thread for instructions, if you don't know about the jumper.

@ gltianya

Try the following SPI image. Flash with "fptw -f myspi_17_fix.bin" followed by "fptw -greset" command. After system reset, check if it works and report back either way. Also, avoid Baidu as it's extremely slow for everyone outside China. Try attaching instead.

plutomaniac has attached files to this post

reply

#39 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Nov 18, 2016 7:07 am (Last edited: Fri Nov 18, 2016 12:48 pm)

thank you for your help,
i downloaded myspi_17_fix.part1.rar and part2, and unpack it ,then i use fitc open it, found BIOS Region.bin size (6172KB) big than before (6144KB). I don't understand what it means. Add something in BIOS Region?
are you sure it's 6172KB , not 6144KB? I'm worried that the main board may be hung up。

reply

#40 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Nov 18, 2016 3:40 pm (Last edited: Fri Nov 18, 2016 3:41 pm)

The fixed ME is 0x7000 smaller in size compared to the original one. In order to keep the total SPI image size the same, FITC decided to place the extra padding at the start of the BIOS region and make it's size larger at the Flash Descriptor as well. Personally, I prefer to add the padding at the end of the ME and I was under the impression that FITC was doing that as well. I think both are ok, there won't be any issue with the BIOS. Regardless, I have included a 2nd fix at the archive below with the extra padding at the end of the ME and not at the start of the BIOS region.

@CodeRush Quick question: it is ok to have the extra padding at the start of the BIOS, right?

plutomaniac has attached files to this post

reply

#41 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Nov 18, 2016 4:46 pm (Last edited: Fri Nov 18, 2016 4:47 pm)

@plutomaniac
thank you very much, i use fix2(FF at ME), it's very Perfect. but i don't login mebx ,what 's the password? thank you again and again.
mymeinfo below.one before,and other is fix2.

gltianya has attached files to this post

mymeinfo2.rar

reply

#42 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Nov 18, 2016 4:59 pm

Yeap, it looks perfect. The default Intel MEBx password is "admin".

reply

#43 | RE: Optiplex 7010 and VPro/AMT/ME datum

Fri Nov 18, 2016 5:08 pm

thank you for your reply, I use google search what's Intel MEBX default password, found password is "admin",then i reboot my pc to try it.is right. and you give me the password very quick,You are very kind, I am very grateful.

reply

#44 | RE: Optiplex 7010 and VPro/AMT/ME datum

Mon Nov 21, 2016 8:54 pm

So, for what its worth, I just performed this procedure on my Linux based T1700. FITC works well under Wine, and I used flashrom while in maintenance mode to dump the old flash for FITC, and write the new flash back.

reply

#45 | RE: Optiplex 7010 and VPro/AMT/ME datum

Thu Dec 29, 2016 12:01 pm (Last edited: Thu Dec 29, 2016 1:12 pm)

Hi Plutomaniac,

I have a Optiplex 9010 and updated the Dell official release BIOS A25(O9010A25.exe). I can use CTRL+P enter MEBx menu and make some setting.
but i found some problems, my problems below. i think (1) and (2) caused by 3G same as jwlu. i use FITC to view my dump ME and SPI. I have no idea to change which parameters to disable Anti-Theft and 3G.
Can you help? Thanks in advance!

1) MEManufWin.exe show communication error(SERVICE_MODE on and off)
2) MEInfoWin.exe show communication error(SERVICE_MODE on)
3) When i set the remote PC to reboot to ISO image(IDE Redirect), VNCViewer+ always show "Waiting Up to 8 Minutes For KVM FW.....". even the MSDOS71.iso file only 1.5Mb.

minibug has attached files to this post

reply

Beginner questions about BIOS and IME on Thinkpad T460 � � ME N/A at Z97 ASUS Maximus Hero VII

Page 3 of 11 � Page 1 2 3 4 5 6 7 ... 11 Page �

Please enter a reason for warning.