I tried "Grow FV" and some other options without result on that Z370 board. But at the end mod was done, thanks to Serg008 and his this post. All window size issues looks like a try to add dpi-dependent window size, but something gone wrong if run on Win7 and default dpi settings. While played with phoenixtool also noticed it may not run from LiveCD windows - just because it use some latest .NET features. If possible, please look on this too, because possibility to run from LiveCD environment can be useful sometimes - for example, to make mod done before OS was installed, or to make it from LiveCD environment if current OS is stripped or broken in some ways.
Hi, may i ask a question about an old dell server? I tried to mod dell poweredge 1950 Gen 2 Bios version 2.7.0 to support cpus from gen 3 1950 server. (Same Bios file and confirmed working) Both the windows and the linux versions of the flash tools are uploading the new bios successfully. But when the server reboots to apply the new bios i get the error "BIOS Update Attempt Failed!" Is there anything i did wrong? Up and downgrades with original hdr files are working fine. regards
Maybe it use some sort of image digital signature or CRC. You can update ucodes by dumping image and flashing it back via HW programmer, or just look for a method to update only microcodes (for some vendors exists tools to do that, or look for downloads like "microcode patch" and make own new one).
Hello. I am new to flashing bios in general, so I apologize for my lack of knowledge. I came here to your tool thread from a link back at bios-mods, as I am trying to recover my laptop from a bad bios update. My Laptop is a Lenovo Ideapad 320 14-isk Type 80XG. According to the label attached to it, it was manufactured this May 2017. The motherboard of my laptop houses an EFI/Insyde bios (filename is BIOS.fd, which I extracted from an executable I downloaded from my laptop model's page), and I understand that the BIOS.fd is what I needed to flash recover my Laptop's bios via USB drive. Since the recovery method requires using your tool to determine how I should rename the BIOS.fd file, I used the phoenixtool.exe included. I selected the 'Module' method, since it seemed to be the less risky out of the three. However, when I clicked 'go', the process went on for a moment before an error pop up reading 'Insufficient space to manipulate modules' appear every time. Going by that, should I change the method to 'Code' or 'Dynamic' for it to work, or are there other things I should do to make the process successful?
Bug in v2.73: need scroll window for access buttons "Go", "Advanced", "Verify" PS: OS = W7 x64, classic theme.