Dear @gorgarath and @Lost_N_BIOS , unfortunately I had absolutely no time to deal with this system unit earlier. I tried several times to upload the modified bios, but I did not succeed in searching for kvm. My current version of bios in the attachment, there seems to be everything that is needed, but kvm never appeared in the settings. Maybe I'm doing something wrong? I think I did everything according to your recommendations.

Hello guys, i've got bricked 7010 SFF (purely BIOS fault) and I'd like to reuse some of SPI dumps posted here. Question is, how to split that 12MB file into 8MB and 4MB for particular flash chips. Like first 8MB for 25Q64 and remaining 4MB for 25Q32? I'll use SPI programmer on desoldered ICs... Thanks a lot for any info.

@TomasHC
You can use "winhex" ,and split it into 2 files directly.Remember the first file is 8MB.

@TomasHC - 8MB is first as mentioned above (cut 800000h), then rest is 4MB file (400000h)

Thanks gents, both 7010s working now. Remaining question is how to change MAC and TAG (at least). Maybe how to add Windows Digital key as well. Tried to find a way, but maybe will be faster ask directly. Thanks in advance.

@TomasHC - great! You can't "Change" MAC, you can "Fix" MAC to what it's supposed to be for that system, should be on sticker somewhere, or hopefully you made a dump of BIOS chips before you did anything.
What I mean there, in case you didn't know, is you cannot use some new made up MAC, you have to use the one assigned to that system at manufacturing.
These tools will help with the Asset Tag, maybe MAC too I can't remember. I put that in at the BIOS file level myself, if you need help with that and have the proper MAC ID let em know and send me files (both files or single large one)

Dell DSTCD tools. in case these can help you redo the serials/service tags easier (Asset_A209.COM is not same as ASSET.COM, try both if one gives you issues) >>
http://s000.tinyupload.com/index.php?fil...250786477991185

Zitat von Lost_N_BIOS im Beitrag #156

---

@TomasHC - great! You can't "Change" MAC, you can "Fix" MAC to what it's supposed to be for that system, should be on sticker somewhere, or hopefully you made a dump of BIOS chips before you did anything.
What I mean there, in case you didn't know, is you cannot use some new made up MAC, you have to use the one assigned to that system at manufacturing.
These tools will help with the Asset Tag, maybe MAC too I can't remember. I put that in at the BIOS file level myself, if you need help with that and have the proper MAC ID let em know and send me files (both files or single large one)

Dell DSTCD tools. in case these can help you redo the serials/service tags easier (Asset_A209.COM is not same as ASSET.COM, try both if one gives you issues) >>
http://s000.tinyupload.com/index.php?fil...250786477991185

---

None of the provided tools were able to change the TAG :(

@Lost_N_BIOS new member/noob here! I've got a Precision Tower 5810 that has "ME DISABLED 3" as well. I have a service jumper pin on there but when I do that it only presents UEFI option to reboot and then I am no longer in service mode. Do you have to enable legacy to boot to a usb drive or cd for this work?

Dell Optiplex 9010 ME AMT A30_AMT.bin REQUEST

I have a Dell OptiPlex 9010 the sister of the Dell OptiPlex 7010, both manufactured Mid 2012.
ME DISABLED 3.
I'm finding all the Dell Business Optiplex 's 7010 & 9010 are ME DISABLED 3 for Businesses that need a high level of security. ME Lockout 6 unknown why that was done?
AMT is a remote management feature of Intel ME.

My BIOS right now is @ A09. ME AMT will need BIOS updated to A30?

9010 is A30 18 Jul 2018 O9010A30.exe
https://www.dell.com/support/driver/en-u...?driverId=90DD2

7010 is A29 18 Jul 2018 O7010A29.exe
https://www.dell.com/support/driver/en-u...?driverId=5M70H

dell_ME_AMT_7010 contains:
A29_AMT.bin
fparts.txt
fpt.exe

I need the complete sentence by sentence details how to make an A30_AMT.bin fparts.txt fpt.exe.
Download location for Intel FIT Flash Image Tools ? And exact line description for download.
Intel Management Engine: Drivers, Firmware & System Tools
Will it be faster for somebody to make rather than explain the how to details?
Thank you.

It's mentioned to begin a new thread, for help, as this thread has been quiet?

On my phone and not going to try and look through the thread, but I'm pretty sure the links are in the first couple of pages to the threads with instructions on how to modify the BIOS files.

gorgarath,

Thanks for this!
I just successfully converted an Optiplex 7010 bios from ME lockout (6) to fully enabled, using your A29_AMT.bin file.
The only initial difficulty was in discovering that the Intel ME tools version (FPT.exe and fparts.txt) is CPU family specific. The Optiplex 7010 required FPT version 8. Other versions of the tool set return a "not compatible with this platform" error.

I was able to enable ME on an ME Lockout 6 Dell Optiplex 7010 USFF using the directions in Post #150 and using the A29_AMT.bin file provided in Post #134.

Thank you to gorgarath who had the skills and experience to understand and apply the technical information provided by Plutomaniac and Lost_N_Bios.

I downloaded a bootable image from the FreeDos site and added a folder named 7010 to the image with the fpt.exe, fparts.txt (found in the Flash Programming Tool - DOS folder of the Intel ME System Tools v8 r3 extracted folder), the A29_AMT.bin supplied by gorgarath, and O7010A29.exe (the A29 Bios update provided by Dell). However, I did not end up using the bios update file since I updated the bios from the Windows 10 environment before venturing off into FreeDos.

Upon restart when finished, Ctrl P didn't seem to work, but pressing F12 did. The Management Engine tab now appeared in the bios settings. I had to enter the default password "admin" (without quotes), then create a new password. Everything was enabled as stated.

With great pride, I grabbed a sharpie, crossed out Lockout and 6 on the sticker, and wrote Enabled and 1. I also wrote down my new ME password there, just in case I forget.

Thanks again to everyone involved!

For some reason, the FreeDos method didn't work for me on every Dell 7010 unit that I tried it on. I often got an error message indicating a write/access error.

Here is a Windows 10 x64 method that I think is easier. I have a hard drive from one of these Dell 7010s with Windows 10 Pro x64 installed on it that I connect to each unit to perform the following steps.

Steps:

1. Enable the Windows 10 administrator account. Select “Start” and type “CMD“. Right-click “Command Prompt” then choose “Run as administrator“. If prompted, enter a username and password that grants admin rights to the computer. Type: net user administrator /active:yes then press Enter. Restart the computer and click to login as Administrator.

2. Download and run O7010A29.exe (the A29 bios update supplied by Dell). Computer will reboot to perform the flashing process.

3. Download the Intel ME System Tools v8 r3 at the link provided by Lost_N_Bios in Post #126 (The link to the package is located about half-way down on the linked-to page).

4. Extract the folder, then go to the Flash Programming Tool folder and move/copy the Windows64 sub-folder to your preferred location. You may delete the rest of the Intel ME System Tools folder and its contents, unless you need it for other purposes.

5. Download the A29_AMT.bin file provided by Gorgarath in Post #134 and place it into the same Windows64 folder.

6. If you've not already done so, place a jumper on the Service Pin (it's next to Password Pin that has a blue jumper on it).

7. Now, press shift while right-clicking on the Windows64 folder. Select Open Power Shell Window here.

8. Run the commands provided by Gorgarath in post #150 one at a time, but change FPT to .\FPTw64.exe as follows:

.\FPTw64.exe -rewrite -desc -f A29_AMT.bin

.\FPTw64.exe -rewrite -me -f A29_AMT.bin

.\FPTw64.exe -greset

9. Upon reboot - F12, Intel Management Engine MBEx should appear below the bios setup option

10. The default MBEx password is admin. It will then prompt you to enter and confirm a new MBEx password.

I am sure that a more experienced user could create a script file or enable FPTw64 as a trusted application in Power Shell to eliminate the need of typing .\ before each command. I have these commands typed into a text file in the same folder from which I just copy and paste into Power Shell. The processes seem to run faster in Windows 10 than they did in DOS. I almost doubted that is was working because each took less time.