Optiplex 9020 and AMT/ME

9020 SFF i7-4790 3.6GHz

@frankiekat i7-4790 3.6GHz should be vpro capable (if it’s not the ‘K’ version- but since you wrote 3.6GHz…)

Post bios and/or me region you created?

@lfb6 as a new user to this forum it is unfortunately not allowing me to post external links yet. I can try again next week… :confused:

It’s BIOS version A25 and used the 9.1.45.3000_5MB_PRD_RGN.bin as the Me Region replacement.

This particular 9020 has the sticker inside the case that says “3 ME Disabled”. Is it still possible to enable AMT in this case?

Thanks!

fk

@frankiekat There are several threads in this forum that describe activating Dells with "3 ME Disabled"

For sharing files- mega.nz is often used, most mail providers offer to share files, shouldn’t be a problem, normally.

@lfb6 I did upload to mega.nz, but the forum software/rules won’t let a new registrant post external links in a message for the first 7 days (understandable I suppose). That said, the (short) link is tinyurl.com slash y65y5n6q.

I’ll do some more searching for the other threads for “3 ME Disabled”.

Thanks,

fk

@frankiekat Which settnigs did you change? In your dump AMT is effectively disabled- see pictures comparing a 9.1 ME with working AMT (on top) and your dump at the bottom.

pic 1 - Service advertisement … Don’t think it’s relevant, but this might be bios dependant, should leave it unchanged.
pic 1 - Manageability application enable/ disable is greyed out, but becomes active when enabling AMT
pic 2 - AMT idle timeout is the time AMT waits until it goes to sleep when machine/ OS entering S* sleep.

amt1.jpg

amt2.jpg

@lfb6 yes, that finally did the trick. I must have somehow missed changing those "Featured Supported" in the instructions, but doing that did finally restore the MBEx functionality. I had to re-flash the BIOS with the OEM because something went wrong and it was giving me an "Vesa unsupported video card" error, but after that it seems to be working fine.

Thank you for all of the tips and help!

fk

Nice! Glad it worked

Hello, Ive recently use this forum tutorial, after flashing outimage.bin and restart my optiplex 9020 wont turn on. It orange light without blinking. Pllease help.

Post / attach outimage.bin and the original dump.

this is the link to original dump and outimage

Thank You

You worked on a ME region only- how did you flash it back?

using this command “fptw64 -f outimage.bin” after restart, remove battery, power and service jumper. it stuck on orange light on power button.

last time I remember there are green message that say xx something identical

can this be fixed?

You certainly got a ‘size mismatch’ warning and disregarded it.

fptw64 doesn’t care what it writes where. It compares what it was supposed to write with the content of the chip after flash and gives a ‘task accomplished’ if both are identical. But you overwrote you flash descriptor with the ME thus successfully bricking your system.

You need a CH341a programmer (and possibly a SOIC8 clip and maybe a 1.8V adapter) to flash back your backup.

Thanks lfb6,

where is the chip position that needs to be flashed?

How would I know? I don’t own such a device.

Search the forum and the web, if unsure make a detailed and sharp pic and attach.

Is the chip with spi_1 and spi_2 & spi_3 label on it?

Might be. What’s written on / what’s the type of the chips?

Mxic mx25L6473E on labeled spi_2&spi3
Mxic mx25L3273E on labeled spi_1

Good picture :+1:

Seems to be the right chips, a 32 MBit and a 64 MBit 3V spi. You need a CH341 programmer and a SOIC8 clip to read them. There’s a lot written how to do that in the forum- for example:

Placing the clip is a pain in the beginning. You need two 100% identical reads of every chip to be sure that your dumps are valid. Compare with HxD or if you prefer to work with checksums: Check in addition the structure with UEFIToolNE (Files with all ‘FF’ do have e nice looking checksum, too)

If you can’t read you possibly can’t write- so it’s useful to read first to be sure that the handling of clip and program is OK (even if you’re sure you have already a valid backup and are sure that the chip content isn’t useful any longer).