(01-12-2014, 12:18 AM)Republic Of Gamers Wrote: Hello!
Donovan I saw that many persons are getting this error but some of them bypass the error through the recovery method but some cant they just hear some beeps any the notebook boots normally but yesterday I bought a new acer notebook and I modded its bios and flashed it using insyde flash and I also got the error invalid firmware image and I tried the recovery procedure but it just beeped at me 4 times and booted normal so I heard of a way to change the hidden values without modding it using fptw tool but I dont know how to flash a modded bios with this tool Can you please give me some advice on using intel flash programming tool(fptw tool) to flash a modified bios so that I can get some help and also for helping others
For some reason, I slightly suspect you of being
Eternal Mangekyou's third profile. I'm almost certain your not, but your similar to him in some ways. Don't take this to seriously though, I'm just thinking out loud
Anyhow, Intel's flash programming tool is capable to dumping your entire bios chip, which consists of several regions. These regions are things like the flash descriptor, ME firmware, GPE, BIOS, etc. Usually the flash descriptor sets it so that you only have read/write access to the bios region of the chip. There are different leaked versions of this utility that support different Intel chipsets. So you'll need to get the version that supports your computer chipset. Also I think it was
Svl7 who was the first to discover that using fptw to flash the bios would bypass the invalid bios error on Acer computers.
So here's how to dump just the bios part:
Code:
fptw.exe -d output.bin -BIOS
You'll notice that the bios region contains things like the EFI global variables and serial numbers. These things aren't in the bios directly from the Acer's bios update. You can then modify the bios dump with any method you want, then to flash it:
Code:
fptw.exe -f output.bin -BIOS
Then I also encourage people to verify the flash just to make sure everything went right:
Code:
fptw.exe -VERIFY output.bin -BIOS
However a better goal would be to find out where the validation check is in the official installer is so that we won't have to rely on leaked tools