#PROGRAMMING 25Q64FVSIG BIOS SPI UPDATE#

So I've ended up buying a CH341A USB EEPROM programmer and a SOIC8/SOP8 pin so I won't need to unsolder my chip.

#PROGRAMMING 25Q64FVSIG BIOS SPI UPDATE#

But recently Windows 10 creators upgrade has ones again bricked my laptop by trying to update my bios. Last time I asked a guy with the programmer to help me out. So I'm wondering what should the name on the file be in order to recover the bios. I've managed to get the bios chip name : winbond 25q64fvsig 1423 but it is soldered and I have no option to unsolder it for the moment. I can see that the USB drive is read by the system but still I have no progress (the only thing with is running good is the fan of the cpu) So I've registered my laptop at and I've downloaded the latest version on the bios that is N550JKAS.208 (before I've registered the laptop I've been trying with G550JKAS205 and G550JKAS204) and I'm launching my laptop with Ctrl + Home + Power.

I have exactly the same problem with my G550JK and I'm still trying to find a way to recover from a failed BIOS update (which was launched by Win10 update without me knowing). The only other hiccup was to make sure that my Pi was on before clipping into the laptop and pluggin it in. Simply pluggin in the AC power adapter is enough to power the chip. If you do this DO NOT TURN ON THE LAPTOP. So I disconnected the 3.3V connection on pin 8 for my clip, and drove it with the PSU instead. That was not enough to power the chip while it was in system. I did have to use the laptop's PSU in order to power the chip, because the Pi 3.3V can only supply 50mA. I can add more info about using the Pi with a clip as a programmer if anyone is interested. They did all have the correct 8M size when I was finished. I did an md5sum on all the images (my new bios, mikto's, and the bricked bios), they all came back with different hashes.

*** NOTE: dd uses a default 512 block size, so count and skip are multiplied by 512 to get the right distance in the files. I would try to avoid using someone else's BIOS as it likely has system specific information on it (MAC and such).Īfter I got the ROM ripped, I used 'dd' in linux to carve out the file parts that were needed.ĭd if=brickedbios of=bricked2M count=4096Ĭat bricked2M 206bios6M > recovered_image My resulting bios image is different from what Mitko posted. After much ado with my raspberry pi, and flashrom, I got the bios chip talking with a SOIC ISP clip. Thanks for this thread! It was instrumental to my recovery process.

Programming 25q64fvsig bios spi