Just bricked my laptop flashing to 211.

Had the stock 205 bios and just decided to flash to 211.

Followed the steps in Hellcry's thread and the bios installed, and then my laptop shut off (as i understand it should have). Now it wont get past a black screen when i turn it back on...the fans spin, but it doesnt do anything.

I think i might cry. Couldnt of come at a worse time.

 

There are ways to blind flash in hopes of recovering. You'll need to search. How did you flash the bios? Did you use the usb stick formatted fat or fat32 booting into the bios and running the update or did you try it from Windows (while many have done so successfully, Windows bios updates have proven to be more risky)?

Cheers,

 

I formatted it in FAT32 and followed these steps:

Flashing Bios (credits to stubbornswiss):
- You need a USB stick again, but this time any will do. (it doesnt need to be bootable, but you can use the bootable one if you made it for flashing the vBios too, you dont need to format it or anything, just add the bios files onto it)
- Extract the files from the rar onto the USB stick.
- Save the Bios on a flash drive.
- When you see the Asus splash screen, press the F2 key to enter Bios.
- In the Bios, navigate to the Advanced tab.
- In Advanced tab, select "Start Easy Flash" (should already be selected), and hit enter.
- This should bring you to the Asus Tek. Easy Flash Utility page.
Under "Current Platform" you should have your current Bios.
- Navigate to the right middle pane, and select G73JhAS.209 (if you want the silenter 209 Bios) or G73JhAS.211 (if you want the cooler 211 Bios), and hit enter.
- It will ask "Do you want to update BIOS", and give you options "Yes and No".
- Select Yes, and the update will begin, and run through to completion.
- When finished, the notebook will shut down.

Blindflash? God i hope so... So annoyed!!!

 

Was the laptop plugged in? Maybe the battery died half way through the flash.

Sounds like your in trouble, just RMA it and have them flash the latest bios.

What do you see now when you power on?

 

When you call in the RMA, ask if there is a local ASP service center. This way you can drive over and hopefully have it done same-day.

 

and that;s why you use winflash

 

Using winflash is like walking a 300 foot high pipeline.

Using BIOS is like crossing the road.

I think I did the right thing in taking my chances with the second one. Slamming's case seems to be a rarity.

 

Winflash is a horrible joke...
The previous versions were actually the cause of the keyboard lights going dead - winflash caused some corruption when flashing the Bios and you lost the lights. Not to mention all the processes and services running in the background in Windows can screw the process up.

Slamming im sorry to hear you had a failed flash with easyflash, but theres sadly always a slight chance of it happening either way you do it as it is pointed out in the warnings in my thread.
Luckily, Bios flashing is officially supported (the files are hosted on the Asus support site), so you can RMA and have the techs solve the problem for you.

 

make an autoexec.bat file with the automated commands in it.
put the usb drive in the left front usb port
turn the computer on and hope for the best.
or do the same thing with a hard drive...it seems to want to read the hard drive...(speculation on your case though)

 

Blind flashing isn't going to work so well on a laptop that can't boot. You can blind-flash a botched vBIOS, but bricking with a regular BIOS flash means the computer isn't going to even POST... and if it doesn't POST, it isn't going to boot from any media.

Long story short: RMA.

 

It might be recoverable, if it's not totally trashed you might get it to boot off of CD or removable media, and use a totally automated boot environment (DOS boot with AFLASH2 and autoexec.bat) to flash the BIOS. Ken from GenTech has posted about this in other threads, see http://forum.notebookreview.com/2519525-post2.html

I have never had to do this myself, even after BIOS mods that went wrong, I've never trashed a laptop BIOS so badly that it wouldn't POST, so I can't say whether it will work. (I've trashed desktop BIOSes, but I always buy dual BIOS boards so it never matters.)

 

would like to see him try a few things before he ships off to rma. usually it's about 12 to 24 hours before he can get confirmation and drop it off to be shipped.

reason being, i couldn't find a blind flash procedure for this particular notebook. which is strange..since 300 dollar laptops can be blind flashed for vbios or regular bios.

 

Thanks guys, ill look into the suggestions made when i home form work. Heres hoping something can be done before i have to send it awy.

 

thanks!
because last time....i didn't have enough time to really test the blind flash theory fully.

 

If the laptop will POST, you have a better shot.

As for blind-flashing a vBIOS, works exactly the same was as people have mentioned here. Do something like download v93 from the sticky, rename the .bat to autoexec.bat, and boot from the USB stick. You do have to fly blind, but a botched vBIOS flash is easier to recover from than a botched BIOS.

 

Im back home now. Going to read up on this blind flash method now. Im not holding my breath though.

 

Pardon my ignrance but could you please explain how i make an autoexec.bat file with the automated commands in it?

 

Got your PM slamming, but like Toxictaru said, if laptop not even post then the blind flash will not work.

It doesn't looks like it's your vBIOS messed up, looks to me it's the system BIOS.

If system BIOS messed up then it will not look for any bootable device in order to do blind flash.

RMA it.

 

Damn it. Thanks Ken. I was hoping i wouldnt have to send my laptop away for a few weeks. Oh well.

 

Do you have any real arguments to back your claim instead of making a nice comparison and claiming that USER X bricked his BIOS using winflash?

It is extremely easy to claim BS without knowing anything, let me try:

Using BIOS is like walking a 300 foot high pipeline.

Using winflash is like crossing the road.

I think I did the right thing in taking my chances with the second one.

There shouldn't be much difference between the BIOS flash and winflash, one point being that the BIOS flash is very limited in space so the flasher itself should be simple enough that I doubt it checks for FS errors it just raw copies it(but if you are doing it "Right" there should be no problem", while if you fail a flash from WinFlash the BIOS is still in RAM and windows is still functional so you can attempt a reflash(a redownload even another tool!), and more importantly in both cases it's a write to the flash there is no difference unless you want to claim that the multi-tasking of windows may break your BLAH BLAH BLAH
since the floppies "disappeared" I've been flashing all my BIOSES with windows utilies, from my DELL Laptop , my PC with Asrock Motherboard till my G73JH , on the other hand I bricked my p2 400 mhz back in 1999 by flashing through DOS, does that prove anything? NOt really, but what you and all this winflash is dangerous myth is just silly, and not backed by anything, until you do a case study and actually prove that it is more dangerous, stop claiming BS. it's a myth!

 

Maybe you need to backup and do a little research on Winflash , and the bricked bios that have been made by this program. When you do this research you will find quite a few white papers from company's instructing there staff not to use this program and why.
So before you go and tell new users or ones that do not know how the tech works to use something, you might back up there work so if in goes wrong you can fix it.
There are quite a few Manufactures that will not support WinFlash and if it is used they will not cover the Warranty.

 

Then you should stop claiming its safer to flash from windows without your "study" to back you up.

Ive listed a simple fact: Asus' WinFlash utility caused corruption during flashing, and even with all the "checking" you claim it does it didnt give any error, but reported a succesful flash and what you got from it was dead keyboard backlights becouse it corrupted the KBLightsController firmware and a notice was put on the Asus support site not to use this software...
So its not as "awesome" as you make it sound.

Use whichever you like though, its not like i care what you do with your laptop, but at least follow your own advice if you go around posting it to others.

 

Just remember to use the latest version, as some issues were corrected.

 

bottom line..this laptop sucks at having ANY bios recovery options what so ever. bad flash = rma..no way around it....you would think you could boot a i3-330m/i5-430m/i7-620m and this thing would come alive and then allow you to re flash your vga...but no! that is not the case.
not sure who at the high end of gaming laptops thinks this is a wise idea to keep in place. it should be mandatory to have a crysis recovery option in place...just like most of the other lessor laptops do.

although...i hope im wrong and someone finds the way in, but right now...it's not looking good for the home team.(that would be us - )

 

didn't*
successful*
because*
I am not going to reply because it is clear that you haven't actually even read my post, else you wouldn't claim such nonsense

 

At least the "rage" part of his username is true. Have you come up with a 10 a page thesis of pro-Winflash usage for us yet?

 

thread is taking a turn for the worse!

 

that should be a waste of time, especially for the Hellcry-illiterate

 

Yar especially when there are posts here that say people lost their keyboard lights not using WinFlash