[Request] Dell Vostro 260 - Add Ivy Bridge support

Your own ME upgrade via FITC is pretty much the same, any differences are insignificant (mainly because the FD is almost identical). You can take my attached SPI above and just replace the BIOS region via UEFITool. RST is not important if RAID is not used. However, you do need to remove the SNB-only vBIOS as the SNB-IVB one supersedes it. For now the important thing is to see a successful post and for that you need at least ME 8, IVB CPU microcode & SNB-IVB vBIOS.

By the way, the one who should be thanking everyone for their time & work is @Flagers. Any risk is up to him and you have nothing to worry about. As long as youā€™re learning something then itā€™s great to do such time consuming things but later on you may realize that not all users who request for help show their appreciation (just one example). Unfortunately this is more common that you might think. Just a heads up.

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

FinalUpdateX3-MC-ME-vB-SNBIVB.png



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

Dell-Vostro-260-Inspiron620-BIOS-A10-Mod-Final3.zip (2.83 MB)

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

Yeah, I do use USB, but H61 doesnā€™t have native support for USB 3.0 and this dell board doesnā€™t have any usb 3 ports or controllers :frowning:

Iā€™m concerned about not properly flashing the ME Region, so I will wait for further instruction by @plutomaniac , or anybody knowledgeable about it, such as maybe @Fernando .

Ok, Iā€™m going through with the flash, Iā€™m using the GUI version of AFUFLASH.

I flashed and with the Sandy Bridge chip Iā€™m getting a beep code. :frowning:

Iā€™m getting 6 beeps which means video BIOS test error. Please tell me what I should do next

So, I switched to the ivy bridge chip, I have no video, but no beep code either

I got it to POST, but it wonā€™t boot to os. It says that there is no boot device available, but it also detects all of my hard drives.

It doesnā€™t post when I connect a display to integrated graphics

Currently running Dell ePSA, so far CPU fan has failed, system fan passed, video card passed, processor passed.

My suspicion is that ME is misconfigured, I might have to buy an SPI programmer for this one though. I canā€™t boot into any OS.

So, Iā€™m not sure if Intel ME is responsible for fan speed control, but I suspect it is. If only I can get it to boot.

Great news, I reset to defaults and then now I can boot into Windows so I can restore my BIOS back to the one provided before.

AHCI doesnā€™t work, so I have to try to boot into Windows in IDE mode.

Cannot USB boot either.

I thought you were going to wait!? Maybe itā€™s best to reflash now with FPT if you can, I assumed that would probably be @plutomaniac answer on which way to flash when I asked.
Command would be fptw -rewrite -f bios.bin followed by typing poweroff. Then let it shut down, remove power cord and CMOS battery for 30 seconds to a minute. Then put it all back and see if itā€™s better.
Or maybe fptw -greset command better, see I hoped youā€™d wait so weā€™d know for sure.

Good itā€™s booting still! So, can you see any screen at all, DOS or windows, or BIOS?

YOu can always flash from DOS, windows isnā€™t a must. So donā€™t worry about that, unless you canā€™t boot to DOS via CD or USB?

ME wouldnā€™t be misconfigured, we both made clean files and they were the same, itā€™s just not made for this system, so probably bugs and issues we may not be able to fix.
If you look at 8.1.70.1590 ME file in FITC, youā€™ll be able to see what all settings are there to address things you think might be caused by ME but I think thereā€™s probably more that we canā€™t addressā€¦ Yet maybe?

Iā€™d say wait until we are sure, can confirm ME flashed in correctly. Can you get in BIOS, if yes, can you see ME version there or no?

Well, anyways I can reflash the previous BIOS and ME region back to the PC. This time wait for further instructions :stuck_out_tongue:

Yes, lets wait, and see about advise on best way to flash fully all regions at once, so confirmed ME gets flashed in at same time, I think FPT will do that. Lots of edits above I made, so if you feel jumpy again try FPT

Thankfully Iā€™m back to a working state because of my discrete card which saved my life in getting the PC to post and boot again.

So, when itā€™s posting, you could go to windows? If yes, before flashing back you should have, or next time before you flash back, check in BIOS and windows to see ME version (meinfo in windows will tell you, if drivers are installed, may need to install v8 drivers now too)

Hopefully we hear back soon if FPT is best way to flash or not. Seems like it would have to be, this way didnā€™t work out so great with AFU, probably ME didnā€™t flash in properly.

Although, I do wonder about the vBIOS now, since you got that error with Sandy. Maybe I need to make other test BIOS for you, with only vBIOS update to the SNB/IVB vBIOS and see if you have same problem, if so then weā€™ll know I did that update wrong.
I have two versions with that vBIOS too, one with old sandy still in there and new SNB/IVB I donā€™t think I posted, and the last one I posted with old sandy hex edited out. I could not figure out how to get UBU to remove the old one and leave the new one only, so I had to do by hand then recheck with UBU
Wait, I did post that one too, in case you want to test when your bored (post #16 [Request] Dell Vostro 260 - Add Ivy Bridge support (2)) - Never mind, donā€™t!! It does not have ME8.
So, I could remake this one, with ME8 and leave vBIOS as it is, that would confirm our test on that vBIOS without hex edit, new snb/ivb and old sandy too.

When it posted, my BIOS setting hadnā€™t reset yet, if I enabled AHCI my disks were detected, just not bootable. Once I switched to IDE mode it booted to Windows and I flashed back. Under Sandy Bridge with Integrated Graphics I got an beep/blink code (6 beeps) which meant VBIOS Test Failure. Under Sandy Bridge with a GTX 650 Ti Boost it posted. Under Ivy Bridge with 650 Ti it gave a black screen.

Thanks for the testing info. I think main issue is probably the vBIOS, and how I tried to remove the old sandy vBIOS. Neither CPU worked integrated correct?

I will make a few new BIOS later today or tonight. One I will leave old sandy and have the new sandy/ivy combo too, that way no odd editing by me is done, only UBU inserting new.
And second BIOS I will try other way to get the new sandy/ivy in there instead of UBU, probably via GUID extract/mod w/ UEFITool or similar w/ MMtool, I didnā€™t even look at doing it that way the other day.

Weā€™ll get there I think, high hopes :slight_smile:

@Flagers Do not spam with consecutive replies before someone else has posted, use the Edit button instead.

I donā€™t use AFU at Intel systems so I donā€™t know its parameters. Itā€™s better to use FPT after making sure that your Flash Descriptor is unlocked for read/write access as thatā€™s a requirement for ME SPI region reflashing. If your FD is locked then you can either try the steps at the FD guide or better yet, use a programmer. You need to reflash the entire SPI image, not just the BIOS region. The FPT parameters can be seen via -? and thereā€™s an option to preserve MAC address as well when Intel GbE SPI region is present.

You need to eliminate failure variables. First test the SNB system with the upgraded ME 8 and stock BIOS as I explained (removal of power for 1 minute etc). That should at least work. If not, the BIOS source code is not ME 8 compatible so you should stop there. If SNB + ME8 works, update the BIOS microcode via UBU and the vBIOS via MMTool or UEFITool by replacing the previous SNB-only module.

Thanks for the reply and suggested info and methods plutomaniac! I knew I should have tried the vBIOS other ways before thinking it was OK, I guess UBU showing it OK and no errors made me think all was well.
And yes, I should have really had him confirm about FD unlocked or not, because without that he needs programmer before any progress can be made here

Can you check out that linked guide @Flagers (Section D) and upload the dumped image for me to look at, thanks! You will need the ME system tools for v7 and probably v8 for later - from this thread Intel Management Engine: Drivers, Firmware & System Tools
Flash Programming Tool is where the FPT app is located, 4 types. If you do the dump in windows with FPT you will need to install correctly matching Intel ME system drivers first (I think). Does not apply to running FPT in DOS