HP Envy Desktop 795-0037cb bios Corrupted

[BeemerBiker · Accepted solution]

The beep codes of 2 short and 2 long are bios problems. 

Was there a change in the beep codes after the new flash?

If interested you might try the following

Read this walkthrough on flashing a bios.  It is another OEM but it lists the tools needed

It shows a connection to a motherboard header but the device can optionally attach to the top of the bad bios.

This shows the programming connecting to the chip

list of SPI headers, the HP spi header  is usually the same as the MSI.  See if you have that SPI header else you will need to connect to the chip 

https://elmorlabs.com/forum/topic/spi-header-pinouts

Google list of SPI images some are HP

typical programming kit for bios is usually under $30

[esearle]

I ended up getting a little programmer and connected it to the chip via clamp. It was able to read the chip and it said it programmed it successfully with the bin file from HP but I now can't get the PC to boot at all so I'm guessing it's either a hardware issue with the board itself, or it's another one of the components other than the power supply. I didn't get to work on it a whole lot last night but will take another look tonight to see if I can get anything. Thanks again for the help!

[BeemerBiker]

Try one of the older bios is about all I can think of.

[esearle]

Ya I'll give that a try. I tried to download those older versions but when I open them they open a window creates some kind of executable but the window that allows my to put the bin file on a jump drive never pops up. Only the most recent version pops up the second window. Do you know why this would happen or how I can get the raw bin files?

[BeemerBiker]

---

@esearle wrote:

Ya I'll give that a try. I tried to download those older versions but when I open them they open a window creates some kind of executable but the window that allows my to put the bin file on a jump drive never pops up. Only the most recent version pops up the second window. Do you know why this would happen or how I can get the raw bin files?

---

The older  F49 popped up the second menu but it is likely another problem like you suspect

[esearle]

I gave it another try with some older bios's and was able to get the programmer to write to the bios chip. I was also able to validate that the code written to the chip matched the bin file using neoprogrammer but it still says that the bios is corrupted on start (although the PC spins to life every time I push the power button which was not true before). Pretty much the same behavior other than that so I think I'm throwing in the towel. It was fun to troubleshoot though! Although it would have been a lot more fun to see it work.... Anyways I appreciate your help here! If you think of anything else that I can try then please let me know!

Note: I was able to go back to the bios revision 30 before it didn't allow me to copy the bin files.