I can attest that it absolutely works, in the configuration I specified, using the instructions I provided, because that is the image and exact procedure i used for my own machine.
your image bricked my computer
A point of clarification: you bricked your computer while using my image. There is a significant difference.
{A point of clarification: you bricked your computer while using my image. There is a significant difference.} OK my mistake, “that image bricked the computer” I mean “image your provide” I know is my own responsibility, not concern by any circumstance, I bought several computers same model as yours, I noted there are several p/n also, so I made some new images not interchanged between them. Just I have one issue , MAC address network are erased to all re flashed computers so built in ethernet network card does not works, since ethernet card are very cheap, no more time invested to solve that problem.
{I´ve followed your thead and worked just with a minimal differences: not de-soldered—This is not a minimal difference.} For most people, I agree is not a minimal difference but for people that works with computers or electronics components it is.
I have a couple of these Prodesk 600 G1 machines in the office that I just retired because I find them so very slow in 2025. Not only that I took the memory from one machine and doubled the other but I still find it slow. I also have a ch341A programmer and out of curiosity think I might try to flash the bios for nvme. However I also wonder if you guys feel a definitive speed bump to make it worth it? My 600 G1 came with an I5 4590 cpu. Otherwise these machines are going to the basement to collect dust.
Against an HDD…sure, from a SATA SSD not such visible bump…the rest all depends on the tasks given to such system.
EDIT: Yeah, it should be the MX25L12873F / 75F, but you also have an FDO jumper on that motherboard model, if bios region is accessible, you may try FPT tool.
Well they both run off of a SATA WD blue 500gb drive. Its takes a solid 5 minutes to boot up as it is. May try updating the rom but have no idea where the bios chip is located. Thanks.
That looks like an SPI flash chip alright. You’re in the right place.
For what it’s worth, the machine I created this BIOS for is still running as my primary web and file server, with the same NVMe drive I originally put in it. No performance complaints from me, also running an i5-4590T. Could probably use more RAM (only 8GB, 16GB would be nice) but that’s about it, even if the RAM is a little slow being DDR3L.
No issues at all, in W11, related to driver… the main issue is the correct contact to the IC itself, or some have to be desoldered, that’s why i mentioned the FDO jumper… Flash Descriptor Override (FDO)
Edit: @MeatWar Your suggestion about the FD0 jumper worked out and was able to take a dump of the rom but question remains will I be able to use FPTW64 to flash my modifications or will I have to use ysb programmer?
Anyhow previous issue I had was with driver at first and second poor contact to test bios chip which was a winbond chip. Think my clip is compatible with Prodesk 600 and will test it out time permitting if necessary.
Im sure that, by now, after you read the linked thread, you know the odds of such operation or the methods that can be tried out, in order to have permission to write in the desired SPI region(s).
This is a user side task.
I read the linked thread and I think it said something like yes, no maybe so because it all depends on manufacturer implementation and every one is different. Having an unlock FD jumper was extremely beneficial. I am a little confused though in that I looked at the dumped bios file in Uefitool and looked at the descriptor region which read that the ME regions were only ones locked for reading (possibly why I could not dump because of the ME) and the ME + FD regions locked for writing. Wonder though if thats because of the jumper in that does it alter the FD table or it unlocks the whole bios file on another level. As my bios dump contains an ME region and its suppose to be locked for reading anyhow I presume the jumper has a global effect on reading and possibly writing. Never mind that as the bios region is suppose to be unlocked for writing according to the FD analysis on Uefitool I should be able to FPTW64 -bios -f biosregion.bin which is all I need.
@kvanderlaag Ever consider upgrading the cpu to something like a 4790K? This thing is sloooow with the 4570 i5. Not that it matters for a server but if you want to go Proxmox probably the 4790k be better. They sell them for $70 on ebay.
Its never the same brand/model, this is my DM one, as MX25L12873F…
but i believe you already do know, that they’re not always equal to every motherboard…dont you???
