Failed bios flash, I guess. No boot

braveheart · 25 Nov 2007 at 13:56

if you flash wrong BIOS then go download older version and then reflash to go back again and then leave until 24-36 hrs until it recover then download new BIOS then reflash then it will recover --- last time I flashed wrong BIOS in Gigabyte K8NNXP that went astray so I download 1st BIOS version (using dad PC to download) and then reflashed that came back alive and then i leave until a week later - then reflashed new one - it bounce back.

Make sure you correct BIOS version in your motherboard otherwise it can slighty damage to BIOS but sometime if can recover by using older BIOS version to come back

danzor · 25 Nov 2007 at 19:57

split said:
I dunno if this is relevant to this board or not.
I'm guessing it's a Abit IN9 32x Max.

Note http://www.abit.com.tw/faq/code.html

Postcode 9.0 (not 90)
Complete µGuru initial processAWARD BIOS take over booting job

That seems where your at, but it's possible to re-set the Guru.

How to load default for µGuru

Turn ON your PC with our µGuru™ motherboard and then turn OFF right away as one single action; repeat this action continuously for 3 times.

Has to be worth a try.

I've tried that, although I don't fully understand what it means. I've turned the machine off and on 3 times by using the switch on the motherboard, still nothing.

GhostlyPea · 25 Nov 2007 at 21:10

BUFF said:
danzor, I think that you'll find that OcUK are legally obliged to take it back in the first year.

Really? Why? he modified a product and messed it up (although not intentionally) but that should then void the warranty? Why would OCUK or any other retailler suffer costs for a customer error?

- Pea0n

Stez · 26 Nov 2007 at 07:36

Pea0n said:
Really? Why? he modified a product and messed it up (although not intentionally) but that should then void the warranty? Why would OCUK or any other retailler suffer costs for a customer error?

- Pea0n

Because it's not the users fault if he does something that the board is designed to do + detailed instructions are in most board manual's showing you how to go about it! No mention of voiding warranty's in my Asus manual :rolleyes:

Sone · 26 Nov 2007 at 08:54

some old boards had a "blind flash" either by using a floppy with autoexec set to flash or just simply putting a floppy in with a bios with the correct name.

Not seen it mentioned on any modern boards.

silent · 26 Nov 2007 at 10:25

Hornchurch said:
Use a usb flash drive, i cocked up my bios update by doing it using @bios. USB for flashing for the win.

mine flashed fine with @BIOS. mine has F4 is that the newest one available for the p35C?

GhostlyPea · 26 Nov 2007 at 13:05

Stez said:
Because it's not the users fault if he does something that the board is designed to do + detailed instructions are in most board manual's showing you how to go about it! No mention of voiding warranty's in my Asus manual

id like that to be true, however detailing the process doesnt mean it wont void a warranty. its a modification to an original product. exactly the same as OCing voids a warranty on most products even though theres alto of official documentation about it

- Pea0n

Stez · 26 Nov 2007 at 14:18

Pea0n said:
id like that to be true, however detailing the process doesnt mean it wont void a warranty. its a modification to an original product. exactly the same as OCing voids a warranty on most products even though theres alto of official documentation about it

- Pea0n

WRONG!!!

split · 26 Nov 2007 at 14:28

Sone said:
some old boards had a "blind flash" either by using a floppy with autoexec set to flash or just simply putting a floppy in with a bios with the correct name.

Not seen it mentioned on any modern boards.

Ive mentioned it before (not in this thread), but it doesn't often work.
The bootblock needs to be intact, and hes using a new BIOS chip that in theory should be OK.
Unless we have missed the obvious here, the new chip should work.

To do it blind... Driver Free Disk For BIOS Flashing from http://www.bootdisk.com/ make floppy. (first)
Bios file from here... (m622a13.zip)

Extract the contents of m622a13.zip to a folder, and copy awdflash and M622A_13.BIN to the floppy.

Open notepad...

@Echo off
cls
a:\awdflash.exe M622A_13.BIN /py /sn /cd /cp /cc /R

Save and copy that to the floppy as AUTOEXEC.BAT.
It willl say it already exist...replace...YES.

Stick floppy in machine and hope it gets as far as reading it.
If it doesn't, the boot blocks had it, tho I find it hard to believe as he has replaced the BIOS chip.

ElectroBlaster · 26 Nov 2007 at 14:35

I would hazard a guess but the board has gone awol. I wouldnt be surprised if the bios flashed fine and the board just decided to keel over to wind the OP up.

Ive flashed quite a few boards under windows so far and (touch wood) havent run into problems. But that was XPpro sp2 and not Vista.

Could it be possible that vista killed the uguru chip somehow? or the uguru has decided to go into one of its overkill settings which is making the board fail?

split · 26 Nov 2007 at 14:42

ElectroBlaster said:
Could it be possible that vista killed the uguru chip somehow? or the uguru has decided to go into one of its overkill settings which is making the board fail?

Thats what I was thinking, hence I posted above...

How to load default for µGuru

Turn ON your PC with our µGuru™ motherboard and then turn OFF right away as one single action; repeat this action continuously for 3 times.

Didn't work though

GhostlyPea · 26 Nov 2007 at 14:43

Stez said:
WRONG!!!

heres an idea, dont be childish and post a single word with caps. A second thought occurs , back this up. I dont mind being wrong, providing the other person has proof to sway the arguement and doesnt act like a jerk doing it

- Pea0n

BUFF · 26 Nov 2007 at 15:22

Pea0n said:
Really? Why? he modified a product and messed it up (although not intentionally) but that should then void the warranty? Why would OCUK or any other retailler suffer costs for a customer error?

OK, he mucked up the BIOS chip with a bad flash but he now has a new chip from abit & it's still not working, ergo there is something else wrong.
9.0. usually is related to 2 things - BIOS (corrupted, non-supported CPU etc.) or power (failing/inadequate PSU , short etc.).
In the UK the retailer is normally reponsible for handling warranty returns in the 1st year & certainly within the first 6 months when iirc if a product fails it's deemed to have been supplied as faulty & the onus is on them to prove that it wasn't.

GhostlyPea · 26 Nov 2007 at 15:34

Yes i understand that and it wasnt my point

- Pea0n

Edit: Seeing as it is more than just a flash failure here it doesnt matter about the point I was making

Stez · 26 Nov 2007 at 15:44

Pea0n said:
heres an idea, dont be childish and post a single word with caps. A second thought occurs , back this up. I dont mind being wrong, providing the other person has proof to sway the arguement and doesnt act like a jerk doing it

- Pea0n

Pea.....Off

GhostlyPea · 26 Nov 2007 at 15:46

Captain comedy there

- Pea0n

Stez · 26 Nov 2007 at 15:48

Thanks

BUFF · 26 Nov 2007 at 20:04

Pea0n said:
Yes i understand that and it wasnt my point

I understand the point that you were making & normally I would agree with you but given the circumstances here I don't think that it's valid.

GhostlyPea · 26 Nov 2007 at 20:58

Quite, but i never disagreed with that point, my point was that is the USER breaks something, the retailer has no obligation to fix it. if the PROCESS is at fault then its a manufacturing/design flaw and the retailer or product manufacturer must deal with it. My posts were based on the idea of the user messing up, not the product, along the lines of the first few posts.

- Pea0n