Any changes @Lost_N_BIOS

Thanks @MixManSC & @pustekuchencake
& @gloobox - I'm surprised you didn't still have gloobox, but thanks for reply anyway! And yes, please, always dump BIOS of systems you have if you remember, you never know when it will come in handy

@MixManSC - yes, I can enable ME for you and do the NVME Mod, but I need to look at what you uploaded first, your comment of "all the different files" confused me since we only need one file here. * I see now, you meant all regions separately
But once all sorted, I'll fix a BIOS for you * Edit - I checked the files you sent, ME is enabled (permanently) as is AMT, at least on the ME FW side, looks to be in BIOS too but I did not check NVRAM yet since I see all this enabled I wanted to have you double check in BIOS/MEBx first.
KVM is disabled, that's all, except "Service advertisement and discovery" is also disabled, unsure if that matters or not but the rest I know to check and enable for these systems is already enabled and ME FW is latest version too.

@lowrck - sorry, I was offline for a bit and this thread got buried on me. Please wait, checking all this out now and will edit in reply for you both soon
What CPU do you have, the non-Ivy? So I can be sure to leave it's ucode in there (I'll update them all)

I was checking your dump, and it looks possibly corrupted, and also incorrect flashed at some point (Someone flashed in stock BIOS using programmer or FPT, missing NVRAM Volume)
Anyway, your NVRAM that remains looks corrupted. Can you please dump again using a few other software versions, and let me know which version you used previously too. What is the chip ID? If there is two, give me ID of both

I have a e5 1620 v1 in right now.

Thanks, please see my edits above, and refresh again now if you already refreshed previously
For my reference, current CPUID - 206D7

It's possible someone flashed something in the past, the dump was done with Intel me toolkit v8 and the machine was purchased second hand from an ewaste recycler. I can try another dump but I have no idea if that will help

Would it help if I wiped the nvram using the stock method and/or used toolkit v7instead @Lost_N_BIOS

So that was FPT dump, then it's not corrupt NVRAM unless due to something someone did in past, but yes, I think someone also put in BIOS incorrectly (usually to try and fix ME or recover BIOS improperly they program in stock BIOS region and that looses one of two NVRAM volumes)
No need for other FPT dump, however, yes go ahead and dump again with V7 FPT since this is V7 ME FW system, so we can rule out incorrect FPT as cause of the possible corrupt thing I was checking out. No, don't wipe NVRAM

And, since it's about time for programmer anyway, go ahead and dump each BIOS chip with your programmer, and send me those dumps, so I can confirm they are OK/Valid so you have a backup, and so we can learn what software version needs used for each in case there is any issues.
While you do that, get the ID of each chip and let me know. I assume you plan to do this conversion from FPT DOS, or maybe even windows, but I still suggest doing this with programmer since you have it and so that you'll for sure have recovery files in case anything goes wrong while we work on wrapping it all up.
Best done with programmer anyway, especially since I plan to edit the FD to unlock everything, unsure if your jumper allows the FD re-write or not?

Just ran into a major issue, the 8mb ROM is a soic16 and I don't have a clip for that. I can try a dump with me tools v7 but otherwise I'm stuck.

We can move forward with FPT alone if you want, but if anything goes wrong you may be stuck until you get a SOIC16 clip (let me know if you need link)

okay lets try this dump. if it doesn't work ill amazon a soic16 clip and itll get here tomorrow.
http://s000.tinyupload.com/index.php?fil...425458300568876

@Lost_N_BIOS the only thing that worries me is that both v7 and v8 verify the file as correct and the diff of the dump between the two is identical. keep in mind this is an updated bios since i did the first dump. this is a17 i believe.

anyways its 2am here, and im exhausted so i think ill head to bed. ill check here when i get up to see if there's any progress but zero pressure. i'm in no way in a hurry and i actually think all this is pretty cool to watch from the outside.

@Lost_N_BIOS i put in an order for a soic16 and it should come tomorrow for me, which is friday. but i did extract a copy of the bios again using fptw64.exe. the only thing im worried about is i have a ch341a based programmer just like in your pictures and i don't know if itll work for the soic16 chip. thanks for all the work your doing and i am sorry for any stress i am causing you by being impatient.

@lowrck - It's not about what FPT says is valid, even a hardware flash programmer can dump an invalid dump (all FF or all 00) and say it's valid / verified.
This is probably either their (Dell) mistake or previous owner flashed in BIOS incorrectly. It may be fine, not corrupted and just "looks" that way to me, but the missing volume is not correct and is not part of what I wanted to check as this would be the same (still missing) no matter how you dump it.

Comparing both dumps, they are not the same, but this could be due to time changes, dates, checksums, NVRAM variables updating between first and second dump etc.
Both still look like they have corrupted NVRAM volume (what remains there anyway), one NVRAM volume is missing and other is corrupted/invalid - however this may be how it normally looks for this system, I'd have to have some other T3600 dump to compare.....
Off to check my storage for a T3600 dump = None - But, I did look around forum and found one to compare with!
And theirs looks same, so this either means this is normal/how Dell does it on this system (it's not like this, and proper on T3610), or both yours and his computers have been recover/flashed in the same incorrect manner (which is possible, maybe more than we'd imagine too)
But, I think we can ignore this for now Especially since you wont be using this NVRAM anyway on the other system, I could transfer over, but it's tedious and some of the data in there may not match/cause issues etc. You will loose service tag and asset tag, but those can be put back in later with Dell tools if you want.

Yes, CH341A works with the SOIC16 clip same as the SOIC8 clip, provided you ordered a proper SOIC16 clip like this one - https://www.ebay.com/itm/332156943251

I am so buried in threads here, years behind, so your not putting any stress or pressure on me, I get to threads and post a reply when I get there, I can't go any faster, can only go as fast as I go
Please edit your posts if you want to add more info and no one else has replied yet, thanks

Put on jumper, boot to DOS or windows and use FPT >> FPTw.exe -f lowrckT3610M1.bin
http://s000.tinyupload.com/index.php?fil...762864281614556

Well I have good news and not as good news. The system still posts but it freezes at the Dell symbol. And bad news is the one I ordered is 16 pin to 16pinn. I'll just have to make some jumper wires for it.

Order a cable like I showed, or look at some images of that one and maybe others on ebay, so you can see how to cut and resolder the wires.

Did it flash the entire BIOS, no errors in FPT and it look like it wrote all 12MB? If yes, shut down system, remove 8/24 pin power cables, short power on pins for few seconds or hold in power on button for few seconds, then short CMOS Pins for 1 minute or remove battery.
Leave it like that, with no power connected, and all power drained for one minute, then put it back and try again. This will reset the ME State, in case this is what's causing the issue. If this does not help, either FPT did not write entire BIOS, or these boards are not as similar as you think.
This is still with the older original CPU correct?

Looks like you might be right about them not being close enough, any chance you could tell me how to seperate the backup file into two pieces so I can reflash it to at least have a functioning desktop?

@Lost_N_BIOS just did several resets and yep im still running into the same issue. Thanks for trying I guess I'm just dumb. Thanks for all the help

@Lost_N_BIOS i got really lucky and my clip came with both a direct 16pin to 16pin and a 16 pin to 8 pin adapter. i used my dump of the 4mb bios to find the start and end point to create a split bios recovery fileset. if anyone wants it post here or dm me for a copy. it should both help you restore a t3600 and enable intel amt.

@lowrck - Sorry, I assumed you knew how to do that. It may not work, ME and FD is on the 8MB chip which you already programmed in, but if that ME FW works with your T3600 BIOS then you don't even need the T3610 BIOS region, but I suspect some of the differences are at the ME FW settings/layout too.
But you can try and see what happens. Nice that your clip came with 8 Pin dip adapter too!

So are you recovered now, or do you still need split T3600 files? If you want to try some things, half this or that, and see if you can get it working please send me dump from each chip and label each file as the size of the chip.
Then I'll send you some mix-match files to try (ME FW from T36100 with BIOS region of T3600, ME FW original with BIOS region of T3610) so we can see if it works either way of those in order to maybe see if we can figure out what is the issue.
If not, I can also manually redo the ME FW as a test, with T3610 BIOS region and use the T3600 specific settings into the updated ME FW.

I got it recovered. Luckily I made a dump of the 4mb ROM before I flashed it, but we can flash the me region from the t3610 and see if it still boots. I don't yet have an ivy bridge chip to test with but I can... Aquire one soon.

And now i have an easy recovery good set.