@plutomaniac Thanks! I assumed maybe it could be done via FWUpdate tool or FTP, because in the packed EXE from Dell is a separate ME FW and fwupdatelcl, and the same ME FW s also included in the BIOS.
So it looked to me like the FW may update itself, outside of whether or not the actual BIOS update applies the ME FW or not. And I assume as you said, that probably does not apply for V7 Upgrade >> To V8

Here is an image of what's included in the EXE if you wanted to take a quick glance, I assume you could extract and check if you wanted, so I didn't upload files or anything - orig BIOS exe here https://downloads.dell.com/FOLDER01639275M/1/MS-A10.exe
The 1176upd.bin is the same ME included in the MS-A10 BIOS itself


I extracted the ME contained within the BIOS, and compared with the ME included in the EXE package. they are same versions, but are not the same

I assumed it might not work too, but enjoying trying when it seems there might be a chance. Not many people work on, or request, Dell BIOS usually either, so it's always good challenge.

So far we've got upgraded vBIOS and microcodes, and before vBIOS or ME update even the system does appears to be booting into windows (checked via networking into running PC)
So there may be a good chance the vBIOS and ME will get it fully working. Fingers crossed


*Edit - Progress! Thanks again for your help and guidance on this Plutomaniac! It's not for me, I'm helping someone else, so I hope you don't mind offering your thoughts for a little bit so we can both help him, and maybe make this magically happen!

I went ahead with using the original BIOS bin itself as the source for v7, and latest v8 RGN download. Looks good after mod, opens in all apps properly.
But I do see a few things missing when compared with MEA, does it look OK? No "Blacklist x2" and no "Patsburg PCH Support" shown in modified BIOS MEA


These are the issues I came across while copying over settings from v7 to v8 - no errors when building outimage

1. In "Component section" - Flash Component 2 Density (greyed out, locked at 8MB, original 2MB)
a. I was able to set flash Component 1 density to correct 4MB - Does this mean I need to use the new "Descriptor" that is built too - or leave original in BIOS?

2. In "Upper Map" - unable to change VSCC Table Length (original BIOS 0x0E - in ME v8 greyed out at 0x04)

3. In "VSCC Table' - Unable to added 7x entries to match original (due to cannot add VSCC Register Value to any of the entries, even when creating new table entry)
On these, I see these are flash chips, many noted in the original descriptor, so I assumed not being able to properly add these, I should probably leave old original descriptor in place.
Is that OK, and correct thing to do? Does this cause any issue with issue 1 above?
I mean, does that #1 component section flash setting get put into the newly built descriptor, and if yes and I do not use that descriptor, will the old descriptor with different settings for that section matter in regards to using v8 ME

I'm wondering after looking at the guide, about XMP compare etc, is it possible to make the above issues go away by editing the XMP and making the changes I want so they wont be greyed out and add the VSCC register values too after adding in the table entries?
Well, did that, and the values still do not show up in FITC8 - and I see this only applies if I make and use a new FD, is this required or will the old FD left as is be OK?

@Flagers - Waiting for feedback on above thoughts, but I have final package ready now. Hopefully this will be the one!
I can easily and quickly make any needed changes regarding the ME reset/copy over, but wanted to be sure on that before uploading another package

I know for the Thinkpad T420 BIOS they were not able to correctly add Ivy Bridge support. Something with the BIOS needing to be able to select correct VBIOS on boot depending on which CPU is used.

@bankkopf - Thanks for the info. Who is "they"? Do you mean someone here, if so where is the thread?
I looked at your posts and couldn't see anything related. If it's another forum, send me link in PM, thanks. Just want to read and see what all was done, attempted, discussed etc

I've been thinking about that, since now Sandy and Ivy are one vBIOS file and when I added the SNB/IVB it kept the SNB too.
I wondered if I could/should try to remove the single Sandy entry and only have the Sandy/Ivy one.

If it was me, since I have proper recovery tools and skills I could test myself easy, but I hate to send out BIOS like that when I'd be really unsure of how that would act with his Sandy CPU.
If it failed with only that Sandy/Ivy he wouldn't be able to recover easily without knowledge in advance and tools to do that.


@plutomaniac, sorry about that XMP, I meant editing the XML manually. Thanks for your time editing that ME!
I had never done it before, and after a few tries I think I have it correct now, but will use yours in the new BIOS I will create.
I will redo myself too, so I can compare and verify if I'm getting it right yet

I already know how to add the microcodes, and have already edited and transferred in a vBIOS too. So I think we'll have this all covered now.
I sent you my final edit from tonight, but probably ME not 100% correct due to me not using FD and those VSCC settings messing with me a little too.
I'll use your ME and FD, the rest I've done 100's of times properly, except for vBIOS edit/insert (I edited following guide, used UBU to insert). RST needs updated too for Ivy, required or just "We should"?

Thanks for the further guidance @plutomaniac And thank you especially for confirming my thoughts on the SNB-only vBIOS, I'll get that figured out.
I do understand this may not work of course, and I know it's always a big risk to flash modified BIOS, especially for user when I can test myself.
I've been modifying BIOS long time, but mainly only orom or microcode updates, few hex edits or fills here and there, but thanks to your guides here other more involved edits like the ME are possible.
In the past I've changed out ME without cleaning, only insert and go and never had issues, but it's good to find a guide here and do it right.

And yes, I do know sometimes people are not appreciative, even if things end up working great on their end too.
Some people are hard to please, and I know it's a lot of time to do these kind of things for us and we can only hope they are appreciated.
That thread you linked, that's highly ungrateful, can't believe he would say that "afraid to screw it up" when he already did that many times WTH!
Hopefully we see less and less people like that, it's very rude!

Thanks again for the help and tips! I'll figure out how to remove the sandy only vBIOS tonight and get this wrapped up and posted.
I think it's ready for the final test after that, if it doesn't work then there's probably nothing more we can do easily to make it work, especially on Dell BIOS.

@plutomaniac - does he need to use any special flag for AFU to make sure ME gets reflashed (ie /EC or /ECUF)?
I assume /p /b /k should be used already

Or should he use FPT and following format? And if MAC/Serial issues we can fix later?
fptw -rewrite -f bios.bin


@Flagers * Final Edit & Work on this - hopefully!

Please let us know how it works, if success finally I will repackage with the Dell AFU files and the original text about how to update (minus the first flash ME suggestion)
And if success I'll post over to Dell site, I think a few threads people wanted this update for years. Fingers crossed it works!
Please know this is untested, and BIOS recovery may be needed via solder/desolder, jumpered over with CH341A cable jumper or other jump BIOS methods (such as Nano USB adapter from ebay, w/ it's own proprietary programmer PM if need more info on that).

Dell Vostro 260 BIOS A10 - Mod @ Ivy Bridge Attempt


Updated All Previous Microcodes + Add Ivy (7x)
cpu206A1_Ver07-12-23-2009
cpu206A2_Ver27-05-02-2010
cpu206A3_Ver09-06-09-2010
cpu206A5_Ver07-07-22-2010
cpu206A6_Ver28-09-15-2010
cpu206A7_Ver2D-02-07-2018
cpu306A9_Ver1F-02-07-2018 (Add-In)

Add > New VBIOS - Single Combined SNB/IVB - v2171 / Remove old Sandy Bridge v2111

Intel ME v8.1.70.1590 - Clean Region Import + settings copy from Dell V7 to V8 >> Insert to BIOS
Thanks to Plutomaniac for his help and guidance on the ME work!

BIOS attached

Hey, I've been away and haven't been able to follow-up on the progress, I'll read all the posts thuroughly and get back to you by after I flash. I'm sorting out problems with Windows 10 not responding to m&k input after reset with data. I sure hope it will work.

I forgot to say, but thank you @Lost_N_BIOS, and @plutomaniac. Nothing would be possible without your support, I would have had no idea where to start and look.

Everyone is busy, no rush to come back as long as you get in here sometime soon so we all don't forget what's going on here.
Kidding for sure, take as much time as you want, it took a few days or so to work it all out anyway, and I'm really waiting to get one more reply from Plutomaniac about how you should flash to ensure ME is written and done correctly at the time of flashing.
So maybe you should wait to see what he says too, since this is Dell I'm not sure which would be best way to make sure full BIOS SPI image is flashed with updated ME

And you are welcome, appreciate the thanks, and I enjoyed helping you to try and get this working! Hopefully we've solved it now, that would be very cool!

Yeah, I'm really hoping to sort out this Windows 10 issue.

What's the win10 issue, I see you mentioned "m&k input after reset with data" but I'm lost on what the issue is and with what

Lol, I reset the PC through the settings menu, selecting the option to keep data as I do once every year, it resets, everything is fine, until it finished resetting and I find out that mouse and keyboard input aren't working. So I use my laptop and make recovery media and reinstall Windows, because that's the only option and I had a backup of my data I made yesterday. Coincidence? I think not!

Ohh, I gotcha, win10 reset and keep data etc. I'm still on Win7, tried 8/8/1 for a while and hated it, so assumed I'd hate 10 too. Luckily you made that backup!
I try to make one at least once a month when I can remember, because you never know when you'll need it. I use program to do it though, so don't have to deal with windows backup issues.
You'll have to try it out sometime, Macrium Reflect, it's free. I just make a complete disk image backup once a month or whenever I remember, then anytime can restore entire disk in few minutes.
You can set it to do full image creation by schedule too, instead of incremental (Or that too if you wanted). I never setup a schedule though, but have tested it before, I do it manually when I remember.

Setting up Windows again, took a really long time to install, I typically get much faster installs on other Sandy bridge systems. That's some nice advice, I'll research more about it and review my options. Thanks.

Glad you made it through smoothly. You'll also have to checkout installing from USB, if you're not already, super fast install from USB to SSD