Absic, you had me... Yooooouuuuu had me..... I was so hopeful even though in my heart of hearts I knew that if I tried it the DOS way and it didn't work, why would the @BIOS version work... but I thought hey... maybe it could work... maybe I just did something wrong..... How I wish I did....
Didn't even see that page before. Based on past eperience with a previous MSI motherboard and Live Update for the BIOS, the latest version always gave trouble (Live Update 6), and the one that came with the motherboard worked (Live Update 5). The most I did for this Gigabyte board was use the motherboard download page to download the @BIOS version there and install and run. But after your recommendation I uninstalled the old @BIOS, installed the App Center, then installed the new @BIOS. Ran it, I was like in shock at just the change in UI... lolol... I thought yes.... this HAS to work lolol... but it did the same thing... it detects the board as 990FXA-UD5 Rev 3.0, but when it checks the server for the BIOS file and I have to choose the correct "Model" I only see the FB version BIOS.... It does the same thing as the last version... writes it, reboots and I still have the same BIOS version........ If I didn't know better, it moves like a Rev 3.1 where the latest BIOS IS the FB version which has the FX 9590 support....
I checked the comparison between the different revisions on Gigabyte's website, but I can't really see any difference between the Rev 3.0 and the 3.1, so I'm not sure if MAYBE it's an error during manufacture/labelling etc..... but I just so HIGHLY doubt that... I dunno what else to do... I sent in a support ticket yesterday to Gigabyte USA, but since it was Thanksgiving, I probably won't get a response 'till Monday or Tuesday... sucks... This is like THE weirdest problem I have ever had when trying to update a BIOS..... really....
Thanks for all the help and suggestions you guys have been giving me by the way, I've talked to one of my friends who has a Gigabyte board but experienced the normal HDD detection issue on a successful flash; I also talked to a local computer builder who hasn't had any such problem before.... I'm really clueless here right now.....