flashing video bios windows 7 64bit? help

i want to flash the 1.03v bios for my 485m in windows 7 64bit, but i can't get nvflash or nibitor to work. can some one walk me through how to do this. any help would be great, thanks.

 

Use this nvflash version: nvflash windows 5.100.0.1 it'll work with your card.

Be sure to run "nvflash --save backup.rom" just to be safe.

Usage:

Primary Commands:

Code:

Update firmware:            nvflash [options] <filename>
Save firmware to file:      nvflash [options] --save <filename>
Compare adapter firmware:   nvflash [options] --compare <filename>
Update TV data:             nvflash [options] --tv <filename>
Display version:            nvflash [options] --version [<filename>]
Display firmware bytes:     nvflash [options] --display [bytes]
Check for supported EEPROM: nvflash [options] --check
Write protect EEPROM:       nvflash [options] --protecton
Remove write protect:       nvflash [options] --protectoff
Change soft straps:         nvflash [options] --straps=<straps>
Set IEEE 1394 GUID:         nvflash [options] --guid=<guid>
Set IEEE 1394 GUID source:  nvflash [options] --guidsource=<location>
List adapters:              nvflash [options] --list

Options:

Code:

help         ?            Display this screen.
save         b <filename> Read EEPROM and save to <filename>.
compare      k <filename> Read EEPROM and compare with <filename>.
tv           x <filename> Transfer TV data from file to EEPROM.
version      v <filename> Display file version and ~CRC32
                             (if no filename, acts on display adapter).
display      d [bytes]    Display 256 the first bytes of the EEPROM
                             (default is 256 bytes)
check        c            Check for supported EEPROM.
protecton    w            Write protect EEPROM (only on some EEPROM's).
protectoff   r            Remove EEPROM write protect (only on some EEPROM's).
straps       m <straps>   Change soft straps.
   format is: AND Mask 0, OR Mask 0, AND Mask 1, OR Mask 1
guid         q <guid>     Set the IEEE 1394 GUID in the firmware image
                          (GUID is in the form of 16 hex digits).
guidsource   1 <location> Set the source of the IEEE 1394 GUID.
                          main       - main EEPROM image
                          dedicated  - separate serial EEPROM part
list         a            List all NVIDIA display adapters found in the system.
nolight      l            Do not light keyboard LEDs.
overridetype 5            Allow firmware and adapter PCI device ID mismatch.
overridesub  6            Allow firmware and adapter PCI subsystem ID mismatch.
reboot       y            Reboot the PC after other tasks completed.
keepstraps   g            Keep the soft straps already present in the EEPROM
                          after flashing the new image.
romstrap     j            Override the ROM strap setting to allow flashing an 
                          image when grounding the STRAP_SUB_VENDOR pin.
                          This allows flashing a corrupted or erased EEPROM.  
                          Note: Make sure there is a physical EEPROM present 
                          when using this option
index        i <index>    Force a specific device index.
fwindex      F <fw index> Index of which firmware image to use from a firmware 
                          bundle.
auto         A            When possible, run without user intervention.
silence      s <level>    Silence level:
   default  All beeps.
   #=4 (or 2)   No progress beeps.
   #=5 (or 1)   No beeps.
override     o <level>    Override safety check level:
   default  unknown EEPROM | NV adapter aborts application.
   level=1  unknown EEPROM acceptable for read operations.
   level=2  unknown NV adapter acceptable for read operations.
   level=3  Combined effect of 1,2 (cannot write to unknown EEPROM or adapter).

Use a single dash ("-") to use the single letter version of a command.
Use a double dash ("--") to use the longer descriptive version of a command.
Use equals ("=") to specify parameters, with separating commas (",").

 

Excellent good sir + rep, but im not really sure how to use it. any help. i tried to type in but every time i hit a key it just displays more commands, and then closes

 

Are you first booting from a device with nVFlash on it?

 

honestly i searched google for 10 minutes about how to use it and found nothing, so i need a step by step instruction list, because i don't understand at all what to do. from what you said, i guess you stick nvflash on a bootable disk, and possibly some other files, like the system files included, and the bios that i want to flash. then i boot it and use the commands to do the flash.

 

That's pretty much it.

Here's an extensive guide on vBIOS flashing:
NVIDIA VGA BIOS Modification/Flash/Restore Guide

 

well if its this simple can someone post step by step instructions to do it, cause im not really comfortable, doing this on the fly, i need some instructions, from someone who has done this before.

 

The version I linked is for Windows 32/64, it does NOT run from dos, you use the Windows command prompt.

To flash go to the nvflash directory in command prompt and type "nvflash biosfilename.rom" without quotes and with the actual name of your bios file.

alternatively you can make a batch file for it, just open a text editor and type in:
nvfash.exe vbios.rom

Then save this as flash.bat and put it in the same directory as nvflash, then name your bios file vbios.rom and double click the batch, it'll prompt for elevated privileges and flash the bios in a command prompt Window, if you want to make a batch file for backing up put in a text editor:
nvflash.exe --save backup.rom

save as backup.bat, hope this helps.

 

i did the second way and it beeped...?

 

What is the actual name of your bios? I doubt it is vbios.rom ?

I prefer putting nvflash and the bios onto a bootable usb flash disk and boot from it.

 

no it worked, but i had the standard bios. i need the one with the increased voltage. also the 485m isn't in nibitor

 

http://dl.dropbox.com/u/4045945/Driver/flash_vbios.bat
and
http://dl.dropbox.com/u/4045945/Driver/backup.bat

Put those in the same directory as nvflash, name your bios file to flash vbios.rom (or open it with a text editor and change vbios.rom to the name of your bios file) and double click the flash_vbios to flash it.

double click the backup batch first to make a backup named backup.rom

 

oh sorry i edited it cause i got it to work. how can i change the voltage though, its still 1.00v, nibitor isn't showing that the 485m is in the list.

 

Oh I thought you already had a voltage modded bios and just needed to flash it.

Nibitor only works on Win 74 if you boot with the disable driver signature enforcement option, hit F8 at boot and choose that, just reboot again to re-enable enforcement.

 

ok i will try that real quick and thanks for the help so far.

 

it says it can't connect to service manager and it still isn't showing the 485m. does anyone know where i can find an already modified vbios for the 485m for 1.03v?

 

I'm not sure where you can get an already modded bios but theres a guide for doing it yourself Here: Fermi bios editor guide

The guide is for Fermi Bios Editor and includes Nibitor instructions also, Fermi bios editor may be simpler however but i'm not sure if it supports the 485M but it should, you can always try, it detects my 460M's bios just fine.

 

For a 1.03V vBios look at that thread:
http://forum.notebookreview.com/sager-clevo/555871-485m-overclocking-results.html

 

is it this link from jaybee

 

hmm it says unkown device instead of 485m. same with nibitor. could it have to do with the 275.50 driver that im using. oh and i still cant find a bios that actually has the 1.03v in it they are all just stock. wow i keep looking on google and finding this thread...

 

Yes that is it. Worked for me... tested some stuff with it...

 

um i used the batch file in the nvflash folder like atmosk said, and it ran something in cmd and then beeped. does that mean its done or do i have to do it another way.

 

ahh its not flashing, i tried again and i took a print screen of the second cmd page when it popped up. it says that they dont match or something, but the bios is definantly the 1.03v one, cause i checked it in nibitor 6.03. should i just change the subsystem id to be the same as what it says?

 

Are you using Windows to flash? If so, that's likely your problem. Uninstall your video drivers completely, then reboot into a DOS prompt using a boot disk. You can download an image of a Windows 98 boot disk that you can put on a thumb drive that will dump you straight to a DOS prompt. Once you create the disk, you can copy the BIOS and flashing utility straight to it.

 

honestly im just doing what atmosk told me as i really don't know too much about bios flashing

 

I would recommend flashing it with a boot disk, too, but if it works that way in windows, too, the command line has to look like that:
nvflash -4 -5 -6 485m103.rom (or whatever you call this vbios).
Then you have to type "y" or "yes" when asked if you want to flash it although there is a mismatch. Don´t worry about the "mismatch", it´s all right.

 

ok i did it, and i think it worked do i need to restart my computer now?

 

Yes, restart it. Good luck

 

nope no good i overclocked to my previous stable max 695mhz and it crashed and artifacts... so i dunno im just gonna flash back to stock.

 

When I flashed it couple of months ago, I only gained like ~20mhz on the core when benching, but it still artifacted if I increased my gamingclock 670/1340/1640. So no reason for me to use the increased voltage.

 

ok so you think 695/1390/1800 is good

 

My card can only dream of using those clock when playing games. If my memory touches 1670 (or something), it will crash. Your card performs like a champ

 

ok well good to know, also i have the ic diamond if that helps im not sure, but it cools down really quickly.

 

ok so i want to try this again and i want to do it using a bootable usb. i have the 1.03v modded vbios and nvflash, and i have a bootable usb using windows 98 boot files.

edit: woot i got it to work, and it finally showed up in nvidia inspector!