GA-8IG1000MK, BIOS flash gone wrong. Any recovery options left?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
GA-8IG1000MK, BIOS flash gone wrong. Any recovery options left?
Well, here's your chance to help me out for once.
Victim is an unbranded machine with an old Gigabyte GA-8IG1000MK. The BIOS flash process had to be done using Gigabyte's "@BIOS" utility in ClippyOS due to fd0 not being present at that time. I backed up the BIOS and flashed the original BIOS version to ig1000mk.fb. Rebooted OK. Taking it up to ig1000mk.fc lead to an error (exact text not saved) during flash process about "flash memory being read-only". Reboot gives one (pre-BIOS?) beep and then the process stops.
What I've done sofar:
- read the motherboard manual,
- read "fix corrupted Phoenix BIOS using Crisis Recovery Disk" texts like [0|1|2],
- read the PhoenixBIOS 4.0 user manual about the Crisis Recovery Disk procedure,
- attached an fd and used crisis-recovery-disk-creator.zip and B1800_crisis_recovery_disk.zip to create a CRD disk replacing BIOS.WPH with renamed ig1000mk.fb,
- removed CMOS battery for over 10 mins,
- shorted the CLR_CMOS switch (near CMOS battery),
- booted with the CRD disk in fd0 while holding either key combo WINKEY+B or WINKEY+ESC,
- booted a SD card with the CRD disk contents while holding key combos,
- booted with CRD disk contents on an USB stick while holding key combos some more.
PSU fan is audible as are CPU and case fans and the disks spin up too but that's about it. So now I'm wondering if I've got just a paperweight left...
If you have previous experience with fixing corrupted Phoenix BIOSes (not AMI or whatever else) then I will be grateful for the recovery options you can give. Feel free to ask for clarification if necesary. If you offer advice or pointers please ensure, for efficiency sake, that whatever you post does not duplicate what I already did.
Oh man, a bad BIOS flash is always my greatest fear, for this very reason, it can be bricked so easily. For future reference, this is why I prefer a DOS boot disk rather than flashing from Window$ or wine ... very dangerous. For Gigabyte, use the Q-Flash, it's easier and safer, they even recommend it over other methods.
In the manual I don't see any CLR_CMOS switch, only CLR_PWD for clearing the CMOS/BIOS password, so I don't think the switch will help, unless you actually have a switch labeled CLR_CMOS.
What kind of BIOS do you have, are you sure it is a Phoenix BIOS, in the manual it says it's an Award BIOS (or AMI), so I would look for guides for that specific BIOS:
For Gigabyte, use the Q-Flash, it's easier and safer, they even recommend it over other methods.
At that point the paperweight didn't have no fd. No fd means no Q-Flash AFAIK.
Quote:
Originally Posted by H_TeXMeX_H
so I don't think the switch will help, unless you actually have a switch labeled CLR_CMOS.
My paperweight actually has one.
Quote:
Originally Posted by H_TeXMeX_H
What kind of BIOS do you have, are you sure it is a Phoenix BIOS, in the manual it says it's an Award BIOS (or AMI),
Good q. The specs on the website say Award, the manual mentions Award and Phoenix and if I run 'strings -an4 *|egrep -ie "(ami|award|phoenix)"' the tools from B1800_crisis_recovery_disk.zip return .*phoenix.* and the ig1000mk.fb BIOS returns "Award BootBlock BIOS v1.0" (Phoenix bought Award long time ago) and I'm sure I got the right BIOS files as I downloaded them from the Gigabyte site. If I assert it's an Award BIOS (definately not AMI) then the biosman site (read it already) and mydigitallife both assume the floppy will be read (meaning a regular POST). Unless I'm mistaken those BIOSes don't offer Boot Block access by key combo (or other workarounds) I need since the machine doesn't go through a regular POST...
Extract the BIN file (ig1000mk.BIN) from the lha (ig1000mk.fc) inside the exe (motherboard_bios_ga-8ig1000mk(rev1.x)_fc.exe) of the BIOS you want to flash (I used 7zip), use the BIN file and the instructions above.
It says that 'Ctrl+Home' may force the computer to read the floppy.
Last edited by H_TeXMeX_H; 04-18-2010 at 11:08 AM.
If, as you say, you have an old mainborad, then the chances of recovery from a corrupted BIOS are next to zero unless the BIOS is on a plugin chip. Even then, it would be more economical to replace the board.
The clear BIOS jumper on mainboards almost always clears password, date/time, and non-default settings only. If it did wipe the whole BIOS, you'd have no way of booting.
If, during boot, you can't bring up the BIOS GUI, your paperweight analogy is likely correct.
BTW, been there; done that.
Lou
Last edited by LouRobytes; 04-18-2010 at 02:14 PM.
If, as you say, you have an old mainborad, the the chances of recovery from a corrupted BIOS are next to zero unless the BIOS is on a plugin chip. Even then, it would be more economical to replace the board.
The clear BIOS jumper on mainboards almost always clears password, date/time, and non-default settings only. If it did wipe the whole BIOS, you'd have no way of booting.
If, during boot, you can't bring up the BIOS GUI, your paperweight analogy is likely correct.
BTW, been there; done that.
Lou
That's a very real possibility, but at least try a few more things before giving up.
Even if it doesn't POST, it may still be active in the darkness, so pretend that it is still ok for now.
POST is meant to test and initialize HW. Since the BIOS doesn't execute POST it never gets to detecting any BAIDs. Since no BAIDs are detected none are selected as IPL device to boot from. No key combo I've tried leads to a floppy seek (thanks for support offered but the CTRL+HOME key combo suggestion really is AMI-only) so there's no code loaded and the Award BIOS doesn't have AMI ISA video routines built in (not that the board has ISA) and this is no DIP or PLCC. As in USS Yorktown.
Well, it depends on how messed up the BIOS is, sometimes it can still access the floppy.
If you followed the Award instructions exactly and it didn't work, then it could be that you have a bricked mobo like LouRobytes said. That's too bad, but it does happen, and that's why you have to be careful. Sorry I couldn't help more.
NOTE: The recovery process of a BIOS is very much archaic, and like black magic. If you do everything exactly as they say, there's still only a small chance of it working. If you deviate even slightly, things as simple as CLRF terminators on files, or pressing the keys in the wrong order or at the wrong time, then there is 0% chance of it working.
P.S. Make sure the RAM is ok, because the same symptoms can also come from RAM that happened to go bad at the same time as you were flashing the BIOS. Maybe PSU check would also exclude it as a cause.
Last edited by H_TeXMeX_H; 04-19-2010 at 05:55 AM.
Note I asked for people to respond who have previous experience with fixing corrupted BIOSes, not drawing conclusions (I can do that myself) nor banter (see the /General forum). If you don't have anything constructive to add that helps me (as you've done twice now) do refrain from posting.
Alright, well again, I recommend using either a DOS boot disk or Q-Flash (build-in DOS on Gigabyte mobos) next time. I've been able to recover a broken BIOS before, but I think I was lucky.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.