Asrock x470 Master SLI/AC bricked after BIOS update

[Lost_N_BIOS]

Yes, start at zero always, and then you can set 16MB or 32, only half will be filled since file is 16MB. I'd go ahead and leave 32MB, that way you can erase and blank check it all, then write.

[VVictoria]

Here, please test with programmer.  I put back both NVRAM volumes from dump #6 above, into stock BIOS (37000h-77000h)
http://s000.tinyupload.com/index.php?fil...3940192783

The end is there, I missed it previously, sorry about that!  I have not used flashcat, but one thing you need to make sure of, which it can surely do, is before you write, erase entire chip then check to make sure it's blank, then write/verify.

here is a read I made erasing it to verify it was deleted.

[VVictoria]

Oh, do you think the BIOS has to be in a specific sector? I wrote to it from 0 to the end of the rom, 16 mb. If I change it to 0 to 32 mb, do you think it will somehow stretch the .bin file to cover the whole BIOS?

[VVictoria]

Yes, start at zero always, and then you can set 16MB or 32, only half will be filled since file is 16MB.  I'd go ahead and leave 32MB, that way you can erase and blank check it all, then write.

here is a read after a write using your bios

[Lost_N_BIOS]

No, it wont stretch the rom, it will just stop at end of data or re-write all the 16MB of FF's at the end half.

What is attached file above @ #12, sounds like all blank, what's point of uploading that? No need for me to check, tell your programmer to erase all, then tell it to check/verify it's all blank, then tell it to write and verify the BIOS I sent you. Then test if the board works or not
File at #14 looks good, exact copy of what I sent you + 16MB of FF at end

It may not work either, if something in your NVRAM volumes was messed up in that dump you attached, but rest is 100% stock BIOS from Asrock (Which also should have worked without any changes). So, something else might be dead on the board, and it just seemed like bad BIOS flash/happened at exact same time as bad flash by pure chance/

[VVictoria]

Just to check if it's truly empty, but the file size is so small, it seems empty! Okay now I'll test the board.

[VVictoria]

No, it wont stretch the rom, it will just stop at end of data or re-write all the 16MB of FF's at the end half.

What is attached file above @ #12, sounds like all blank, what's point of uploading that?  No need for me to check, tell your programmer to erase all, then tell it to check/verify it's all blank, then tell it to write and verify the BIOS I sent you.  Then test if the board works or not
File at #14 looks good, exact copy of what I sent you + 16MB of FF at end

It may not work either, if something in your NVRAM volumes was messed up in that dump you attached, but rest is 100% stock BIOS from Asrock (Which also should have worked without any changes).  So, something else might be dead on the board, and it just seemed like bad BIOS flash/happened at exact same time as bad flash by pure chance/

Okay, that didn't work unfortunately. The lights on my board work and the fans spin and all, like before, but it doesn't POST. I have a multi-meter, is there something else I could check? I'm also having a hard time getting the BIOS chip to be recognized now.

[Lost_N_BIOS]

Maybe this programmer isn't ideal for this chip, since it's not always recognizing it
Are you sure it's not faulty CPU, do you have another you can try? Nothing to check with multi-meter.

Does this board have a Debug LED post Code thing? If yes, what code so you see it stop on? If not, connect a case speaker, do you get any beeps, if yes what are they?

So it's running, but nothing on screen? Can you try another graphics card, older one maybe, but not too old.

Did you try writing older BIOS, before those warnings I mentioned initially? If not, try that now, download one of the earlier BIOS (instant flash version) and see if that makes any difference.

Could be many things went bad, hard to know without more hardware to test with, doesn't always mean bad BIOS flash because it happened to fail right then (good chance it was, but not always).

[VVictoria]

Maybe this programmer isn't ideal for this chip, since it's not always recognizing it
Are you sure it's not faulty CPU, do you have another you can try?  Nothing to check with multi-meter.

Does this board have a Debug LED post Code thing?  If yes, what code so you see it stop on?  If not, connect a case speaker, do you get any beeps, if yes what are they?

So it's running, but nothing on screen?  Can you try another graphics card, older one maybe, but not too old.

Did you try writing older BIOS, before those warnings I mentioned initially?  If not, try that now, download one of the earlier BIOS (instant flash version) and see if that makes any difference.

Could be many things went bad, hard to know without more hardware to test with, doesn't always mean bad BIOS flash because it happened to fail right then (good chance it was, but not always).

I'll try another, older graphics card. The CPU is relatively new and should be fine. Yes, running, nothing on the screen. The restart button also doesn't work now but I don't remember if it ever worked when booting up. Yes, I tried every BIOS version of instant flash and it didn't help. I'm still puzzled why it's a 16 megabyte BIOS file on a 32 megabyte chip though.

[VVictoria]

Maybe this programmer isn't ideal for this chip, since it's not always recognizing it
Are you sure it's not faulty CPU, do you have another you can try?  Nothing to check with multi-meter.

Does this board have a Debug LED post Code thing?  If yes, what code so you see it stop on?  If not, connect a case speaker, do you get any beeps, if yes what are they?

So it's running, but nothing on screen?  Can you try another graphics card, older one maybe, but not too old.

Did you try writing older BIOS, before those warnings I mentioned initially?  If not, try that now, download one of the earlier BIOS (instant flash version) and see if that makes any difference.

Could be many things went bad, hard to know without more hardware to test with, doesn't always mean bad BIOS flash because it happened to fail right then (good chance it was, but not always).

How did you make the BIOS file? If you used the file I gave you, there is a good chance I accidentally wrote to it partially and damaged it somehow. Maybe you could try making it with the instant flash version 1.0. I attached it here.