Was doing the latest BIOS update and the laptop powered off. Now it powers on but is not booting or even POSTing. F2 isn't doing anything either. Is there anything I can do? PLEASE HELP!!
I have tried all those combinations of the FN keys and it isn't working. It doesn't appear to access the USB drive, I see no activity on it. Any other suggestions? Also, am I supposed to leave the file name intact along with the extension or does that need to be changed?
ive suggested all i know about this bios.. im sure we need to find other examples of sony HK1X64.fd bios recovery. no need for crisdisk as its not phoenix. if worse comes to it.. u will need SPI USB Programmer .. or u can make your own but i dont recommend it (unstable never the same reads are very common). dump a backup.bin, backup1.bin backup2.bin.. 3 times with it if u made it. compare all 3 files it made and see if they are alll the same, if they are then u should be ok to write the bios. keep a backup.bin from programmer for serial number and stuff from laptop... we pass it to the new bios .rom if all is ok.
What SPI USB Programmer do you suggest? Do they all work with all the different BIOS? What BIOS manufacture does this laptop use? It is a Sony Vaio Model # VPCEH25FM
most bios chips since 2008 are SPI in laptops. ebay USB SPI PROGRAMMER ( i like ezp2010 but its 33$) or google home made spi programmer bios code is made by Insyde
Sorry for all the questions... So I'm assuming after looking at this programmer that I will be able to pull the BIOS chip , install it in the SPI programmer, flash it, reinstall, and it will work? Is it a socket type BIOS chip on this MOBO? I don't care about the ~$35 if it will work and I can get this laptop up and running again. I just want to make sure that if I do buy it, that it "should" work.
Ah, ok so it will be a chip still on the MOBO operation? And so I would connect this so8 clip to the chip and try to get the "data" off of it to verify what flash we should use? Then if that works I can use the HK1X64.fd file and write it to the chip?
prety close.. we make backup.bin to compare to HK1X64.fd in HxD hex editor then we flash if it matches close