Close

Register Now!

To Get More Info and Daily Reward.

Please login or register.
Pages: [1]   Go Down

Author Topic: User guide: Forum USB BIOS Flash Tool  (Read 333199 times)

0 Members and 1 Guest are viewing this topic.

StuTopic starter

  • GENERAL OF THE ARMY
  • ******
  • Offline Offline
  • Posts: 19551
  • Birmingham, UK
    • StuOnline.co.uk

Guide based on USB tool v1.17c

 


HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS



This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation.  It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation.  (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)

NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.

Symptoms that your USB key need a fix after booting from the USB key:

* Error: "No bootable partition in table"
* Blinking cursor in a top left corner and nothing happens
* "RIVER2 MSI"
* "Error loading operating system"
* "Missing operating system"
* "Disk in drive is not a bootable"
* Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual



If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
Then try with different USB key, the issue is there.


Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm




Read the three notes that follow first before you move on:


1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.


Contents of the Guide:

0. Preconditions & System Requirements
1. Basic Description of Functionality
2. Installing/Starting the tool.
3. Choosing a Preparation Method
  3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
  3.2. Method 2: Processing a BIOS File Directly
  3.3. Method 3: SureHands Live Update
  3.4. Method 4: Geometry Change

4. Selecting the USB Flash Drive for preparation
5. BIOS Settings, Booting & Flashing
 5.1. BIOS Settings to Check
  5.2. Booting from USB Flash Drive
  5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear

6. FAQ: Common Problems & Solutions
7. Version History



--------------------------------------------------

0. Preconditions & System Requirements

The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash.  The Tool is designed to work with MSI Retail Boards

Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<

Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.

The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32).  NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.

As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*

* Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.



1. Basic Description of Functionality

The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:

(1) The device will be made bootable.
(2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.

Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure.  Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.

* Excluding the Geometry Change method which will destroy all data on the USB storage device.



2. Installing/Starting the tool

Treat the forum's USB Flashing Tool like a regular application.  Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing.  Both, the installer version and the stand-alone version, do precisely the same job.  Which of the two versions you use, is solely up to you and your preferences.  The stand-alone version can be started directly by clicking on the executable file.  The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.

When you start the tool a DOS box should open up to provide you with status messages and prompts.  Do not close that box unless you want to abort the preparation procedure!

Please ensure that you connect the USB flash drive you wish to use before starting the Tool!




NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.

The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.


3. Choosing a Preparation Method

If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes.  The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:





3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)

Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board).  If you have downloaded such an archive, you should choose the first method from the option box.  

You do not need to extract the files from the BIOS archive.  The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive.  You don't have to worry about anything else.  All you have to do is to remember where you saved the ZIP or RAR file you downloaded:





3.2. Method 2: Processing a BIOS File Directly

If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box.  In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility.  If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used.  All you need to do is point the tool to the BIOS-File that is supposed to be flashed:





3.3. Method 3: SureHands Live Update

"SureHands Live Update" is the third operation method you can choose from the option box.  It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well.  If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.

Not all MSI Retail Boards are currently supported.  With every update of the USB Flashing Tool more boards will be added.  At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):


AMD based boards:
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
K8N Diamond Plus (MS-7220, PCB 1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
K9A Platinum (MS-7280, PCB 1.0)
K9A2 Platinum (MS-7376, PCB 1.0)
K9A2 CF-F (MS-7388, PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
K9VGM-V (MS-7253, PCB1.0)
K9N2GM-F V2 (MS-7509, PCB 1.0)
K9N Neo V2 / V3 (MS-7369, PCB 1.1)
K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
K9N2 Diamond (MS-7375, PCB 1.1)
K9N2 SLI Platinum (MS-7374, PCB 1.1)
K9N2 Zilent (MS-7374, PCB 1.1)
K9N2 Neo-F (MS-7511, PCB 1.1)
DKA790GX Platinum (MS-7550, PCB 1.1)
790FX-GD70 (MS-7577, PCB 1.0)
790GX-G65 (MS-7576, PCB 1.0)

Intel based boards
HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
X48 Platinum (MS-7353, PCB 1.0)
X38 Diamond Plus
X38 Diamond (MS-7353, PCB 1.0)
X38 Platinum (MS-7353, PCB 1.0)
EFINITY-FP (MS-7395(E), PCB 1.0)
P35 Neo Combo-F (MS-7365, PCB 1.0)
P35 Neo2 Series (MS-7345, PCB 1.1)
P35 Platinum (MS-7345, PCB 1.1)
P35 Neo-F (MS-7360, PCB 1.0)
G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
P965 Platinum (MS-7238, PCB 1.1)
975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
P7N SLI Platinum (MS-7380, PCB 1.0)
P7N2 Diamond (MS-7523 PCB 1.0)
P7N Diamond (MS-7510, PCB 1.0)
P7N SLI Platinum (MS-7380, PCB 1.0)
P6N Diamond (MS-7320, PCB 1.0)
P6N SLI Platinum (MS-7350, PCB 1.0)
P6N SLI-FI (MS-7350 PCB 2.0)
P6N SLI V2 (MS-7346 PCB 1.0)
ECLIPSE SLI (MS-7520, PCB 1.0)
ECLIPSE Plus (MS-7566, PCB 1.0)
P35 Neo3-F (MS-7395, PCB 1.0)



After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard.  It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:

Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.



When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash.  SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:



Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist.  If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment.  That message is part of a prediction feature that tries to determine future BIOS Releases.  If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.



3.4 Geometry Change

If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:



Select your drive then let the tool do it's business.



Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.

NOTE: This method will destroy ALL data on the USB storage device!
NOTE: This method is available in v1.17 and beyond.




4. Selecting the USB Flash Drive for preparation

When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:



Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it.  This can happen in rare cases, but it is usually no problem.

The tool will check the selected drive and will provide you with status messages.  If everything is okay, the message should look like this:



The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing.  If the procedure was successful, you will get the following message in the DOS box:





5. BIOS-Settings, Booting & Flashing

If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:


5.1. BIOS Settings to Check

Check USB-related Options in BIOS:

- USB Controller
- USB 2.0 Controller
- USB Legacy Support
- USB Storage Support
- Boot from other devices
- etc.


Not all of these options may be found in BIOS and the precise name may vary as well.  Just make sure you checked for such options and that they are enabled (if present).

Another option you should check for is "Boot Sector Protection".  If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.

@all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.


5.2. Booting from USB Flash Drive

To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu.  From here, you can select you drive directly without having to adjust the boot sequence in BIOS.  Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).

* Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.

Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.


5.3. Flashing Procedure/Running MemTest86+

As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.

The flashing procedure will automatically be initiated from there.  You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash.  A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts.  You do not need to enter any commands in DOS.  All you have to do is acknowledge the information on the screen by pressing a key.

The flash itself will only take a couple of seconds (20-30s at the most).  If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU.  Read the >>Clear CMOS Guide<< for further information.  

After clearing CMOS you have completed the BIOS-Flash.  :biggthumbsup:


Guide created by Jack The Newbie and the forum team :hat tip:
Logged
Former moderator and admin, 2004-2012

StuTopic starter

  • GENERAL OF THE ARMY
  • ******
  • Offline Offline
  • Posts: 19551
  • Birmingham, UK
    • StuOnline.co.uk
FAQ: MSI HQ USB BIOS Flash Tool
« Reply #1 on: 13-August-09, 13:09:26 »

6. FAQ: Common Problems & Solutions

->Q: My USB Flash Drive does neither appear in BIOS nor in the BIOS Boot Menu. What can I do?

A: Try disabling "Quickboot" in BIOS.  Your system might need more time to initialize your drive. If that doesn't help, your stick may be incompatible or defective.  Retry with a different device.


->Q: My computer crashes during the current BIOS version backup. Why does this happen?

A: The backup process is like a stability test while also backing up your BIOS. This means your machine isn't stable; do NOT attempt to flash again. Go back to the start of the guide and verify that your machine passes the requirements.


->Q: My computer locks up when the BIOS update has started and shows "Problem erasing flash0000000 (0%)" . Why does this happen?

A: This means your machine isn't stable; do NOT attempt to flash again. Go back to the start of the guide and verify that your machine passes the requirements.



->Q: I pointed to BIOS archive file(or BIOS file), but I received the message "ERROR 654" or "ERROR 1220" ?

A: Follow instructions on the screen, if problem remains place BIOS archive or BIOS file in C:\ then retry. Or use "Live Update Sure Hands" instead.


->Q: When I tell the system to boot from my USB Flash Drive nothing happens or I get an error message telling me there is no operating system. What can I do?

A:If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect.
If you are Vista user, you can use Build in Tool Feature "Geometry adjustment" ("Fix My USB Key") and follow instructions once done re-run the MSI Forum HQ USB Flashing Tool and let's prepare your USB key.
For non Vista users, reformat your USB Flash drive with >>this tool<< and re-run the MSI Forum HQ USB Flashing Tool.
For future usage you can skip this step, it need to be done only once if your stick needs adjustment.



->Q: Can I use Tool in "Safe Mode"?

A: Yes you can, Tool is fully functional in "Safe Mode".


->Q: When I use "Live Update Sure Hands" the Tool locks up while checking for latest bios version?

A: Some 3th party application is blocking your outgoing request and Tool is waiting for results and that causes the hang.
Reboot computer and boot with "Safe Mode with Network Support" or "Directory Services Restore Mode" and then retry.



->Q: I've booted from the USB key then it said "BIOS update complete", but after reboot BIOS version remains unchanged?

A: * Go to BIOS and ensure that "Boot Sector Protection" is Disabled, then boot from USB drive again. Read this topic to make sure you're correctly identifying your BIOS version. 


->Q: During Tool preparation progress I receive a message "No matches found". What does mean?

A: Ignore it, its a normal message when extra information is not present.


->Q: Can I prepare USB stick in another mainboard?

A: * If you want to use method 3 it will not be possible, since Tool will detect different MSI board which uses a corresponding different BIOS.
    * If your other mainboard is retail MSI, yes you can.



->Q:  During Tool preparation progress I've received "LogicalDisk not defined" and "WMIC is not recognized".  What does mean?

A: Ignore it, you are running XP Home Edition where WMIC is not present, Tool will detect that and will use alternative system automatically.


->Q: Can I use MP3 Player to flash my BIOS?

A: Yes you can use whatever you have, however some devices are picky and they may not boot properly but depends on your BIOS as to how it will handle them too.
But it is safe to have a try, Tool preserve data on the target drive.



->Q: When I start the Tool I receive "The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application."?

A: To resolve please follow the instructions here: http://support.microsoft.com/kb/324767


->Q: Can I use the Tool under "Virtual Machines"?

A: No you can't, Tool doesn't work with Virtual Machines. You will receive wrong CRC notification and Tool will refuse to run.


->Q: In Windows Vista, using the 'Fix my USB key' option gives the error message: "Error opening file udrgd.001", followed by a second message "Error in line number 1: ADR $1C6. Can't go to address $1C6".

A: It seems that this is due to privilege problems on Vista. If you right-click the flashing tool and select "Run as Administrator", then it works just fine.
Logged
Former moderator and admin, 2004-2012

StuTopic starter

  • GENERAL OF THE ARMY
  • ******
  • Offline Offline
  • Posts: 19551
  • Birmingham, UK
    • StuOnline.co.uk

7. Version History

1.13
   - fixed bug where target device unable to boot property in specified conditions.
   - minor changes.


1.13a
   - added support/compatibility for any 64bit Microsoft OS


1.13b
   -fixed false possitive issue reported by "Avast!" which claimed that our Tool is a Win32:Trojan-gen. {Other}


1.13c:

- fixed false positive wave which confusing most of AV software. (all AV do not report any problems anymore)
- fixed 3 minor bugs:
       * after finished work the tool do not quit normal as expected and hang instead, that happend in x32bit OS only when used has been asked for reboot and answered with "No". e.g. in described specified case.
       * 4th mainboard filter report positive results in some Biostart mainboard and this cause tool to false ID some Biostar board as MSI one.
       * added missing drive letter as USB key choice ("I")


1.13d

 -fixed issue with Symantec AV false ID as "unknown virus".
 -cosmetic changes: one message appear early when asking for USB key drive letter to input and in same time user has been asked to locate BIOS file, and may confuse user. corrected.


1.14
 
- when user must choice the BIOS file archive, after that the Tool will investigate user choice and if its invalid(filename of path name) will notice user about it and to retry with newest selection, instead to terminate without notice.

- adding a new way of USB Drive device parameters detection system which boost detection speed up to 500% on the large storage's or heavy fragmented volumes.The current way of detection will be used for backup option and will be activated only when the 1st detection got a failure. e.g. the current existing procedure just in case will be used as backup option, but will be activated only if the 1st one got a failure. also added a bar indicator of % completed task

-- adding Auto Detection system for USB Drives connected to the system, but the tool will not perform at his own based on the result. reason for that is that user may have more than one USB key connected in same time, or user may preffer to use some other storage with FAT or FAT32(not USB one, which is also supported by the Tool). The detection will be only as recommendation and to be more comfortable and easy when user need to choice the USB drive letter

- adding feature about user to point directly to the BIOS file. it will be usefull when user flashing Beta BIOS or just got BIOS file only.
The Tool will examine user choice and will auto determinate what kind of BIOS is it and will take care about it with corespond further actions.
Also if user choice some other file which is not a BIOS file the Tool will know that and will notice the user that the file inserted is everythink else but not a
valid BIOS file.

- improved user interface with Gui Mode

- improved user dialog in x64bit OS, and Vista.

- improved compatibility when working in restricted accounts.


1.14a

Minor changes


1.15a.

*  Added Build-In BIOS Live Update Feature, named as "SureHands".  The Tool will ID the exactly user board and PCB version and will provide choice to user for do you want to use this feature. after is done the Tool will list all existing BIOS versions for his board, not only the latest one like LiveUpdate do. because users often should go back to the some older version to solve some problem.(the newest one is not always best). so user will have choice which one to pickup. depend of user choice the Tool will do everything automatically.
Also the Tool will automatically check for latest Beta BIOS available for his board and will record the results in user desktop in file betabios.txt
That is informative info only, the Tool will not provide any option to download any betas. only will check for latest Beta BIOS which exist for user's board.
If user have interest to some betas he will be redirected to Contact to MSI Tech for more info about it.
Here is the list of supported boards by SureHands for now(later in time can be added more...):

975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
K8N Diamond Plus( MS-7220, PCB 1.0)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
P35 Neo Combo-F  ((MS-7365, PCB 1.0))
P35 Neo2 Series  ((MS-7345, PCB 1.1))
P35 Platinum  ((MS-7345, PCB 1.1))
P35 Neo-F  ((MS-7360, PCB 1.0))
P6N Diamond ((MS-7320, (PCB 1.0)))
P6N SLI Platinum MS-7350 (PCB 1.0)
P6N SLI-FI  MS-7350 (PCB 2.0)
P6N SLI V2 MS-7346, (PCB 1.0)
P965 Platinum MS-7238, (PCB 1.1)
K9A Platinum MS-7280, (PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0 )
K9VGM-V (MS-7253, PCB1.0)
K9N Platinum  & K9N SLI Platinum(MS-7250, PCB1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)

* Also the Tool has a prediction system which will be able to locate the BIOSes which has not been released yet when the Tool version is out.
In that way it will remove the needs of Tool to be selfupdated to be actual. e.g. the Tool will be up to date at any time for desired board without needs program to be updated 1st.
This feature will works even if MSI web is down for some reason(maintenance for example), and also it will provide all BIOS choices even if they are not available for manual download from MSI web page.
In a fact the user just need to pickup desired BIOS version and that is.... everythink will be done automataically and prepared to the USB key.(the flash will remain in a same way e.g. via pure DOS, reboot PC and boot from the USB key)
OS Compatible for SureHands: all kind of Microsoft OS 32 or 64 bit


1.15d:


* Fixed cosmetic bug: SureHands LU wrong shows P965 Platinum as P6N SLI V2
* Few Minor cosmetic changes.
* Fixed bug: SureHands LU in Vista ignore user choice, and auto pickup latest BIOS version for user board.
* SureHands LU: BIOS range extended for K9A Platinum, P965 Platinum, P35 Platinum/Neo2 Series, P6N SLI V2, P35 Neo Combo.
* Newest board supported by SureHands LU:

K9A2 Platinum
X38 Diamond Plus
X38 Diamond
X38 Platinum
K9A2 CF-F

* added support for RAR archives, Tool now can proceed RAR files along with ZIP.(downloaded from here ftp://duser:duser@66.232.110.239/ for example)


1.16:

* Fixed bug in section W22CR2L7, condition 14 may receive error message "Can't perform requested operation" in Vista x64
/* The issue is minor can come in the specified condition in very very rare case, only when target drive is "W" */
* Live Update Sure Hands:
- BIOS range extended for P35 Neo-F
- BIOS range extended for P6N SLI Platinum
- BIOS range extended for P6N SLI-FI
- Handle improved for P6N SLI Platinum and P6N SLI-FI
- Added support for X48 Platinum
- Handle improved for X38 Diamond Plus/Diamond/Platinum and X48 Platinum

* Improved method for output redirection
* Shows basic info at start-up with MSI mainboard model and PCB version to the user.
* Better filter for flasher detection with new sections added for most precision operation
* Improved compatibility with older flashers
* Added prevention against BIOS refuse to save(keep) settings after BIOS update, which can happend in rare case
(Note: That issue can occur with all kind of BIOS flashing methods: MSI Live Update, Afuwin, Recovery procedure, DOS flashing. It has nothing to do with the Tool, its not bug in a Tool or something. And to be resolved, second reflash is necessary.
The Tool will prevent this issue to come)
* Added verbose message that BIOS update is completed and notice user that he can reboot computer now
* Added detection if MSI want to use specific flasher's switches for specific mainboard and BIOS, they will be applied automatically and override default tool mode.
(That means improvement for notebook BIOS flash)
[Installer only update] * Added user information instruction screen during setup installation
[Installer only update] * Added forgotten shortcut to executable Tool file in a StartMenu Program folder "MSIHQ USB Bootable Tool and BIOS Helper"


1.17:

* Method 3 Sure Hands {

Added support for:
* P7N Diamond (MS-7510, PCB 1.0) /* BIOS range 1.0 - 1.9 */
* P7N SLI Platinum (MS-7380, PCB 1.0) /* BIOS range 1.0 - 1.9 */
* P7N2 Diamond (MS-7523, PCB 1.0) BIOS Range 1.0 - 1.9
* EFINITY-FP (MS-7395(E), PCB 1.0) {Using EFI BIOS} /* BIOS range 1.0 - 1.9 */
* K9N2 Diamond (MS-7375, PCB 1.1)  BIOS Range 2.0 - 2.9
* K9N2 SLI Platinum (MS-7374, PCB 1.0) BIOS Range 3.0 - 3.9
* K9N2 Zilent (MS-7374, PCB 1.0) BIOS Range 3.0 - 3.9
* G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2) BIOS Range 1.4 - 1.9
* K9N Neo V2 / V3 (MS-7369, PCB 1.1) BIOS Range 2.0 - 2.9
* K9N2GM-F V2 (MS-7509, PCB 1.0) BIOS Range  1.0 - 1.9
* HydroGenX48C & X48C Platinum(MS-7353, PCB 3.0) BIOS Range 7.0 - 7.9
* Removed remark "(May not exist yet)" {Global}

}

* Added support for EFI BIOS based boards for Methods 1,2,3
* Added support for 16Mbit BIOS for Method 2
* 2nd Flasher for Method 2 updated to meet the new requirements
* Improved MSI OEM Mainboard detection
* Added verification if the user is trying to use the wrong Tool mode.
* Added detection for exFAT(Introduced and supported since SP1{March 2k8} for Vista)
* Added restriction for non MSI Mainboard in 64 bit OS too.
* Added USB key Geometry adjustment option. (Experimental feature for Vista only, NOTE: All data on the desired USB storage will be lost during operation. Use this option if you have troubles booting from USB Key)
 {
- Checking for Vista.
- Checking for Administrative rights.
- Added strong verification for USB key geometry adjustment.
- Forcing USB storage as HDD Emulation for compatibility purpose.
}
* Keyboard LEDs now blinking by specified way while work is in progress.
* Instruction update, after BIOS update is finished procedure is halted with instruction to verify the screen for failure message. If such exist. There is instruction to do not reboot or shutdown PC and instruction to roll back to the old BIOS{Which Tool auto make backup before performing update}
* Added support for Phoenix BIOS used in Server boards for regular condition. (When capture switches filter is inactive)

* Beta BIOS query updated.
* Added support for Memtest86+, to check memory for basic failures which can harm the BIOS update.

Details:

Tool will auto install Memtest86+ from http://www.memtest.org/ to the USB key when active Internet connection is available.
After booting from the USB key, the user will meet a screen to choose between:

1. Run Memtest86+
2. Proceed with BIOS update


1.17a:

Fixed the false positive alert "Trojan-Proxy.Win32.Horst.ail"


1.17b:

* Packer replaced to avoid future false positive AV alerts
* Few Cosmetic changes.


1.17c:

* Fixed bug in newest feature "Fix USB key", Path not defined
* Added support for 32Mbit BIOS for Method 2
* Removed time counter after booting from USB key, waiting for user input instead


1.17d:

* Beta BIOS query updated
* Download module updated
* Mode 3 {Live Update}, add-ed support for DKA790GX Platinum (MS-7550, PCB 1.1), BIOS range 1.0 - 1.9
* System Info query at start-up updated ==>  {Mainboard Model, Mainboard PCB, Installed BIOS Version{new} and BIOS Date{new}}
* Minor fixes

1.17e:

* Live Update P35 Neo-F/P35 Neo-FI/G33 Neo-F , Mode 3 Prediction range extended 1.09 - 1.F0
{601-7360-010,601-7360-020,601-7360-030}
* Improved administrative rights detection for Mode 4 under Vista.{x86,x64}

1.17g:

* Minor changes.
* Add-ed self check function and self auto update feature.


1.17h:

* Memtest synchronization update, 2.01 ==> 2.11 (22/12/2008) {Tool will auto download and install Memtest 2.11 instead 2.01}


1.17j:

* Changed self update server


1.17k:

* Download engine updated.
Mode 3 Live Update:
* Add ECLIPSE SLI (MS-7520, PCB 1.0) BIOS range 1.2 - 1.B0
* Add 790FX-GD70 (MS-7577, PCB 1.xx) BIOS range 1.0 - 1.9
* Add 790GX-G65 (MS-7576, PCB 1.xx) BIOS range 1.0 - 1.9


 1.17k0e:

* Fixed incorrect year
* Mode 2, second flasher updated to v4.28b0.1
* Mode 3, fixed issue unable to detect as supported mainboard Eclipse SLI


 1.17k0f:

* Minor changes
* Download engine updated
* Mode 3, fixed duplicate BIOS 1.3 appear for Eclipse SLI, 790FX-GD70 and 790GX-G65


1.17s:

* Minor changes
* Fixed error in download engine.
* Improved compatibility with Windows 7


1.17v:

* Minor changes
* Add-ed MSI Notebooks detection:

* Add-ed AC Main Power detection for MSI's notebooks:

If MSI Notebook is detected by the Tool,
it will perform check to ensure that AC Main Power is connected,
if its not it will make co-respond notice and will wait user to connect the AC Main Power,
else will refuse to continue, until user connect the AC Main Power or Exit:

* Once/when AC Main Power is detected,
Tool will make an reminder and notice about EC Reset that need to be done after BIOS update for notebooks:




New features has been tested on XP, Vista and Windows 7

1.17x:

* Mode 3 Live Update:
{
- Fixed detection issue with K9N2 SLI Platinum / K9N2 Zilent. Tool were expecting non existing PCB version.
- Improved detection for DKA790GX Platinum and DKA790GX due MSI BIOS Engineer's error.
Affected BIOS version 1.2:
/* Wrongly typed mainboard name by some MSI BIOS Engineer. */}
Also Tool now will expect further syntax errors by MSI BIOS Engineer{s} and will auto correct the name.
}
* Add-ed Auto Recovery if BIOS update fail.
{
Tool will perform two auto BIOS recovery attempts by using last known working BIOS which Tool auto take backup before perform the BIOS update,
if BIOS update failure is detected and will left control to the user if both attempts fails too for further attempts.
}


1.17x9:

* Minor changes.
* Limit selfupdate check to once per day.



1.18:

* Fixed small bug non functionality related
* New style icons for Installer and Stand Alone versions
                           
* Mode 3, Live Update
   - Add support for  Eclipse Plus (MS-7566, PCB 1.0) BIOS Range 1.2 - 1.B0


1.18a:


* Mode 3, Live Update
   - Add support for  P35 Neo3-F (MS-7395, PCB 1.0) BIOS Range 1.4 - 1.D0
   - Fixed detection issue for EFINITY-FP and EFI BIOS range extended to 1.4 - 1.D0
   - [MS-7395, PCB 1.0] splited to two ver, depend of BIOS types used {Normal/EFI}
   - Updated EFINITY-FP Beta BIOS query search arguments

1.18b:

* Add new feature USB Drive Geometry Adjust for XP   /* Beta */


1.18c:


* Several fixes about newest feature "Fix key for XP".


1.18d:


* Fixed BIOS backup creation issue


1.18e:


* Updated beta BIOS query [sync update]
* Mode 3 Live Update[SureHands] ==> Fixed detection issue for P6N SLI-FI when onboard is installed BIOS V2.7
* Mode 2, Second flasher updated from v4.28b0.1 ==>  v4.31

1.18f:


* Restore Administrative rights checking for USB Key adjust procedure №2{Mode 5} for [x86 Vista, x64 Vista]
* Add workaround solution for x64 XP hang issue
* Disable Mode 2 usage for Notebooks

1.18g:


* Enable USB key Fix ability №2 for W7[x86,x64]



1.18h:


* Optimize self update process for slow machines in Installer version
/* Stand Alone version is using different way to self update and such changes isn't necessary */
* Add new feature: EC version decoder for notebooks, shows as add-on at start-up information screen.
E.g: Mainboard, PCB, BIOS version, BIOS date, EC version{new}, EC date{new}
/* EC version and EC date will be shown For notebooks only */


1.18j:


* Fixed Admin rights detection issue for Vista/W7 for non US OS language, due language difference for geometry fix ability method 2.


1.18k:



* Fixed private case detection issues for x64bit OS
* Mode 3 Live Update[SureHands], Add support for newest MSI AMD Nvidia based AM3 boards:
   - Add support for  NF980-G65 (MS-7612, PCB 1.x) BIOS Range 1.1 - 1.A0
   - Add support for  NF750-G55 (MS-7578, PCB 1.x) BIOS Range 1.1 - 1.A0
   - Add support for  GF615M-P35|P31|P33 (MS-7597,PCB 1.x) BIOS Range 1.1 - 1.A0


1.18m:

* Mode 1 and Mode 2, Blacklisted BIOS version 1.9 for K9A2 CF-F and K9A2 Neo-F mainboards.
* Mode 3 LiveUpdate[SureHands]
 - Removed BIOS version 1.9 for K9A2 CF-F and K9A2 Neo-F mainboards.
 - Add support for BIOS version 1.A0 and prediction range extended to 1.C0 for K9A2 CF-F and K9A2 Neo-F mainboards.
* Flash boot part update
 - Improved appearance.
 - Improved user handle.
 - Award BIOS based now support both award flasher writer algorithms and flash algorithms of the current BIOS version to reprogram the Flash ROM.
/* When Award BIOS is detected, Tool will ask for user input with default recommendation, The purpose is to handle private cases issues */
 - Code optimization.
 - Build and add new modules.[BKHB_04.EXE, BKUI_T6.EXE, BK_VER.EXE]
 - Add support for Legacy <==> UEFI BIOS flash transformation and opposite.
 - Add ability to reboot when BIOS update complete, asking user to reboot machine and proceed if positive answer is received.
* Tool's W32 part synchronized with changes listed above.
* Fixed few cosmetic issues.


1.18p:


* Optimize boot part
* Mode3 Live Update[SureHands]
  -Add support for MSI Wind Netbooks models U90/U100/U100+ , BIOS Range 1D0 - 1M0

1.18r:

* Memtest86+ synchronization update to the latest version 4.0  (22/09/2009) What's new? ==> http://www.memtest.org/#change
/* Tool will download and install latest Memtest86+ version */

Taken more attention to Memtest86+ and system stability,
since people don't read much and skip the instruction without read them and Memtest86+ probably is used by few persons.{It's not there for decoration}

* Updating bootpart
 - Add new module BOOTBK.EXE
 - Add detection if user was running Memtest86+ before proceed with BIOS update attempt.
If such test wasn't been performed yet, execution will halt :stop: and will shows warning notice about the risks following by recommendation
and offer Memtest86+ execution.





1.18s:

* Fixed few bugs, non functionality related
* Improved Tool preparation performance.
* Mode3 Live Update[SureHands]
  - Changed Live Update server


1.18t:

* Updated download engine
* Mode 1, filter updated
* Mode 2, second flasher updated from 4.31 to 4.33



1.18v:

* Updated boot part
  - updated text part, minor changes
  - changed the way of backup determination to speedup process.[store up to 5 backups]
* Mode 4[Beta]
 - clean up pnp filter before exit.
 - restore system default if halt on error occur [cases: abort by user, drive query failure, drive not attached, drive validation failure{do not meet the necessary criteria to be proceed}]
* Mode 3, Live Update
 - Fixed issue MSI Wind U90/U100/U100+, unable to be detected as supported unit if current BIOS version installed is older than 1.0D
 - Add support for Big Bang-Trinergy , prediction BIOS range [1.1 - 1.A0]

Remark: Symantec/Norton user's, please update your virus definition to the latest one to fix/avoid "Suspicious.MH690.A" false detection issue.




Read this topic to download the Tool, and to post feedback and comments! https://forum-en.msi.com/index.php?topic=108079.0




Logged
Former moderator and admin, 2004-2012

Svet

  • T9246ED
  • Administrator
  • *****
  • Offline Offline
  • Posts: 73598

Version updated to 1.18x:

* Mode 3 Sure Hands, Live Update:
- Removed beta BIOS query check[global]
- Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
 add dynamic detection for future versions.
- Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
- Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
- Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
- Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
 add dynamic detection for future versions.
- Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
- Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
- Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
- Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
- Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
 add dynamic detection for future versions, prediction BIOS range extended to 1.F0
- 790GX-G65 board prediction BIOS range extended to ver: 1.D0
- 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
- Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
- Add support for 770-G45 board [p2] BIOS range A10 - AA0

* Add "Exit" option to navigation screen
* Update version info related to boot part
* Update boot part to handle newest features
* Modify Self update sequence of Installer version
* Update internal version check ID
* Mode 4 minor update
* Build and add new Tool's module for newest features
* W32 Tool's exit time part decreased by 10 seconds
* On received OS reboot user request, time delay before execution decreased by 15 seconds
* Update EC decoder
* Update start-up information screen
* Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]

Details:
Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
User can check and compare information before and after the BIOS update
Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.


F.A.Q example:
Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
So you can easy find what was your original BIOS & EC versions.
Is it OEM one or not, and the exact original BIOS & EC versions.
So you can roll back easy or if crossflashing were done to reflash to correct versions.


Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]

Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
    How i can roll back to my old BIOS version?
    The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
    And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
   
    http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739

    How i can re-flash to my original BIOS version and from where can i get it?

A: Run >>Use the MSI HQ Forum USB flasher<<,
then choose Mode 3 [Live Update{aka SureHands}]:


MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
*********************************
Mainboard:  790GX-G65 (MS-7576)       
PCB Version:  1.0
BIOS Version: V1.3
BIOS Date:  05/08/2009
*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
*********************************
Mainboard:  790GX-G65 (MS-7576)       
PCB Version:  1.0
BIOS Version: V1.6
BIOS Date:  11/30/2009
*********************************


Then choose your old BIOS version from the list:

The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:


In a list will be noticed that there is a future BIOS versions.
Some of them will be not released yet. If you pick some of those the Tool will note you:



It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment


* Add new feature "True BIOS Version Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3


Details:

Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now?  :confused2:
A: Of course not, the Tool always show accurate info.
The same as CPU-Z/Everest of whatever other Tool.
However Tool also detect EC-FW versions for notebooks:


The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
Few typical real examples of confusion:


"K9A2 CF wont flash to Bios v. 1.A !!!"  :bonk:
Hi MSI,

I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).

My questions are:

1) How to flash my MB to the version 1.A ?
2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).

Thank you for any help!!

EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.

So my third question is:
3) Is the Bios update 1.A only for version 2 of this MB?

Thx for replies!
A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear.  The fact that this message appears, shows, that there was actually something programmed to the chip.

If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.

------------------------------

The BIOS Version should be shown on the POST Status Screen and there should be a date behind it.  Please check the BIOS Date and write it down:



Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"?  Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten).  The hexadecimal notation is only used in the BIOS File Ending.  Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.

Here is a piece of well-meant advice for now and the future:  MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version.  Why?  Because this tool is stupid and one of there most risky applications for performing a BIOS Flash.  Please uninstall it completely.

Why do I call it stupid?  I call it stupid because it does not differentiate between hexadecimal notation and decimal notation.  It will show you that "v1.A0" is available.  The it will flash it, if you allow it to do so.  Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten).  When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).

I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you.  The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).

If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
Thank you for the quick reply!!

Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.

So thank you! Problem is solved.  :biggthumbsup:

Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P

I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?



My computer does not have a floppy drive.  How do I update the BIOS?  (I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.  So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).  So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated.  Either way, I would like to manually flash it in DOS.  Is it safe to burn the setup files to CD and boot from CD into DOS?


That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.


Quote
I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).

So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.








The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
Also no more confusion:
"What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10 :confused2:
And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10? :confused2:
What's going on? :confused2:

Just run the MSIHQ USB Flash Tool and will show you all that you need to know :biggthumbsup:

Examples[with real/accurate info]:


MSI Eclipse:
BIOS version 1.9:



BIOS version 1.10:[Tool now shows both BIOS versions alias]


Report stored respective in MSIHQ_INFO.TXT at user's desktop:

MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:30:55,34
*********************************
Mainboard:  Eclipse SLI (MS-7520)
PCB Version:  1.0
BIOS Version: V1.9
BIOS Date:  09/22/2009
*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:37:25,66
*********************************
Mainboard:  Eclipse SLI (MS-7520)
PCB Version:  1.0
BIOS Version: V1.A (aka Version: V1.10)
BIOS Date:  10/27/2009
*********************************




More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :




More examples =>945GCM5-F V2 (FSB 1333) :

Report stored respective in MSIHQ_INFO.TXT at user's desktop:

MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:47:34,35
*********************************
Mainboard:  MS-7267
PCB Version:  4.0
BIOS Version: VH.9 (aka Version: V17.9)
BIOS Date:  11/20/2008
*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:52:46,26
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VH.A (aka Version: V17.10)
BIOS Date:  06/02/2009
*********************************




More examples =>780GT-E63 [N/A at MSI web yet] :







For MSI Notebooks such decoding isn't need, examples:










* Add new feature "Triple BIOS flash Recovery Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3


Details:

The feature include 3 auto prepared BIOS backups for followed purpose:
* Internal BIOS recovery:
 - In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
 - This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
* BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
* BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]



Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
Copy/paste Tool log file:


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:00:53,46
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VD.XB2 (aka Version: V13.33B2)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created  ==> A7267IMS.DX2  :biggthumbsup:

Where:
* V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:12:23,95
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VK.VB7 (aka Version: V20.31B7)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.KV7  :biggthumbsup:

Where:
* V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:18:34,46
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: V3.9
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.390  :biggthumbsup:

Where:
* V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:22:24,04
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: V8.1B9
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.819  :biggthumbsup:

Where:
* V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.819  ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:25:38,51
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: V4.E (aka Version: V4.14)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.4E0  :biggthumbsup:

Where:
* V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]



*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:28:16,62
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: V1.BB1 (aka Version: V1.11B1)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.1B1  :biggthumbsup:

Where:
* V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:31:57,78
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VI.FB5 (aka Version: V18.15B5)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.IF5  :biggthumbsup:


Where:
* V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:36:02,40
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: V7.O (aka Version: V7.24)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.7O0  :biggthumbsup:


Where:
* V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:39:11,84
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VC.8B6 (aka Version: V12.8B6)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.C86  :biggthumbsup:


Where:
* V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:49:38,46
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VG.PB6 (aka Version: V16.25B6)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.GP6  :biggthumbsup:

Where:
* V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]


*********************************
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at  7:53:17,26
*********************************
Mainboard:  945GCM5-F V2  (MS-7267)
PCB Version:  4.0
BIOS Version: VU.H (aka Version: V30.17)
BIOS Date:  06/02/2009
*********************************

Co-respond BIOS backup created ==> A7267IMS.UH0  :biggthumbsup:

Where:
* V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
Logged

Svet

  • T9246ED
  • Administrator
  • *****
  • Offline Offline
  • Posts: 73598

Version updated to 1.18z:


* Mode 3,[Sure Hands,LiveUpdate] Eclipse SLI prediction BIOS range extended to 1.J
* Mode 2,[Disabled for notebooks] Second flasher updated from ver. 4.33 to ver. 4.36
* Add a new security feature to check and ensure that target BIOS or EC-FW [or both] is not corrupted or modified by anyway compared to original input,
before attempt BIOS/EC flash. E.g to ensure that source image is authentic and not corrupted. [see * for details]
* Updated all Tool's modes to integrate the newest feature




* F.A.Q:

Q: I through that the flasher itself [From AMI/Award/ENE/Phoenix/MSI] have protection and will not flash the image if something is wrong with it,
if so what's the point of this extra check?



A: If we exclude M-Flash from the list, sure they have it.
However there are weakness places in the protection system and its not good enough:

* Not all section in the BIOS are protected [and flashers can't check them, are they good to go or not]
* From protected sections, flashers don't check all of them before flashing, but only some of them



Q: Can a corrupted BIOS to be flashed by flasher [From AMI/Award/ENE/Phoenix/MSI],
without problem?



A: Sure yes, but very depend of exact case and where exactly the corruption will strike.



Q: What is the effect of flashed corrupted BIOS or EC-FW?


A: As said above very depend of exact case, but speaking generally everything can happend.
Like unknown side issues[depend what exactly and how is corrupted]
But in most of cases the effect will be black screen[machine will no longer able to boot],
or machine can't be even turned on...[for notebooks only]




Q: Is there a different chance of vulnerability depend of firmware images if the corruption strike?


A: Yes, EFI based BIOSes and EC-FW are the most vulnerable if the corruption strike.
Which means mostly notebooks, but can happend with any other machines too just with less chance.



Q: I see in the supplied EC-FW archives and sometimes in BIOS archives supplied by MSI,
there is a CheckSum.txt file with listed checksum inside.
I can't figure how to get this number from the firmware image supplied to compare it with the number from the .txt supplied,
==>  http://eu.msi.com/index.php?func=firmwarefile&dno=8767&i=0
1651_432.zip ==> CheckSum.txt ==> "Check sum 1651EMS1.432=009FD301"
If that can done and the checksum match, can i assume that i'm secure and good to go?



A: You can use 32bit checksum generator tool to get it


However:

If that can done and the checksum match, can i assume that i'm secure and good to go?

Not really, the purpose of this checksum is for reference only and not intended for security purpose.
See the example below, let's calculate 32bit checksum for the code below:



Code: [Select]
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF43122132A53EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFF

To get the 32bit checksum for the code above, we can perform the following calculation:
(67+18+33+50+165+62)+(304[see *]x255)=77915 ==> (0001305Bh)

* ==> [count all bytes with EQU values[0xFF]  = (136-6)h]


So as you can see, the method is not good to check the image for corruption.
Because easy the same 32 bit checksum can be returned and image to be corrupted in mean time.
E.g easy authentic and corrupted images may have the same checksum,
/* Simple example you can move/rotate/swap any bytes of the code to any desired place{which will cause a corruption..},
and the checksum still will remain the same if you don't increase or decrease any values */
Both images will be flashed fine and result will be one of them[the corrupted one] will kill your machine.
In other words, this 32bit checksum do not guarantee that image is authentic and not corrupted or modified.

And the most important the vendor flasher doesn't check this checksum anyway while flash it.
So this checksum is useless in big % if its planned to be used for security purpose.



Q: How i can use the newest Tool security feature?


A: The newest Tool's feature is also full automatic and no user action is required.
You can flash the machine by the same easy way, with few clicks and and key confirmation when needs.[or to answer with "Y" or "N" if the Tool is asking for something]



Q: I want to flash the EC-FW for my notebook, but for my notebook model its separated from main system BIOS.
Does the new security feature will works in such case?



A: Yes, no problem



Q: How my image can become corrupted?


A: It can happend by many reasons:

* Corrupted FS on the target USB storage
* Faulty USB port
* Defective USB storage
* Compatibility issues between the specific USB storage and the mainboard's USB ports [will lead to IO read/write errors]
* System instability issues[memory related]
* File transfer error
* Un-authorized modification over the target firmware after preparation is complete
* Unknown factors

Example: https://forum-en.msi.com/index.php?topic=137699.0
By analyzing requested files, lucky for this case the corruption strike monitored protected BIOS section and trigger the flasher alert,
the Tool detect the failure too, and trigger internal recovery procedure too, but the backups just created before the flash was corrupted too.




Q: Does the newest security feature can safe my mainboard or notebook from bad flash?


A: Definitely yes. Test performed over MSI Wind U100:

Without Tool's newest security feature:

After preparation i've damaged the BIOS image on the USB key with sense to simulate corruption, [DO NOT TRY THIS AT HOME!!!]
then proceed with BIOS update.
Results: The image passed internal flasher protection and the image flashed without problems.
After that the Machine no longer boot, and can't even be turned ON. [Power button do nothing and has no effect]
The Machine become very well killed.
[As planned and expected]



With Tool's newest security feature:

Repeating the same steps as above, e.g:
After preparation i've damaged the BIOS image on the USB key with sense to simulate corruption, [DO NOT TRY THIS AT HOME!!!]
then proceed with BIOS update.
Results: The newest security feature detect the BIOS image corruption and abort BIOS update operation.[Refuse to flash the BIOS]
Results: Your nice MSI notebook has been saved and protected from disaster if/when the corruption strike! :biggthumbsup:











Version Updated to 1.18z3


Changes:


* Mode 3 Live Update, extent prediction BIOS range for P35 Neo2-FI, P35 Neo2-FIR, P35 Neo2-FR, P35 Platinum, G33 Platinum to 1.G
* Support Intel's flasher [target latest and future msi notebooks] + dynamic image detection for security validation
* Support ATI's VBIOS flasher + dynamic image detection for security validation



Version available via Tool's self update feature.



Version Updated to 1.18z6


Changes:

* Memtest86+ synchronization update, 4.00 ==> 4.10 [04/05/2010] What's new? ==> http://www.memtest.org/#change
/* Tool will download and install latest Memtest86+ version */

* Add warning notice message during flashing process.



Version available via Tool's self update feature.





Version Updated to 1.18z9


Changes:


* Mode 3 Live Update, add support for Big Bang-Fuzion prediction BIOS range up to version 1.A
* Updated Mode 2



Version Updated to 1.18z97:

Changes:

* Changed Tool's self update server
* Mode 2, add support for 64Mbit BIOS images[For now used on MSI's H55 Series]




Version available via Tool's self update feature.


Version Updated to 1.19:

Changes:

* Sure Hands[Live Update], Mode 3:
Range adjust for: 790FX-GD70 (MS-7577, PCB 1.0), prediction BIOS range increased to version 1.J

* Updated module [BK_IO2.EXE], improved speed and better appearance
* Updated module [Z1.EXE],
Show detected and saved current installed onboard bios version with original file name on the screen:
[in color format: xxxxxyyy.kkk]
[E.g from BIOS chip to file with original file name detected by Tool based on bios version, [Part of Tool's M-Flash recovery ready]


[Changes synchronized with VECTOR1.COM and VECTOR2.COM]



Self Update activated.



Version Updated to 1.19a:

Changes:

* SureHands LiveUpdate:
- Add support for Retail notebook MSI GT740, Prediction BIOS version range, 10C-10L
- Add support for Retail notebook MSI GT740, Prediction EC-FW version range, 4.06-4.24
Both include self detection function for security validation[MD5 self image check before flash to ensure that image is intact and not modified or corrupted compared to original source, this also will check the usb drive for corruption/malfunction]
- Add support for Retail notebook MSI GT740 Drivers[32bit & 64bit]
- Add support for Whitebook MSI GT740 Drivers only[32bit & 64bit]











Self Update activated.





Version Updated to 1.19b:

Changes:

* Support All-in-One PC BIOS Flash
* Support All-in-One PC EC Flash
* Detect and secure check and validate using MD5 the target All-in-One PC image[BIOS or EC-FW] before flash
* Add flash back to prevision BIOS option by using the internal backup. [Mode 3 after booting from USB key]




Self Update activated.




Version Updated to 1.19c:

Changes:

* Fixed issue in version 1.19b[the issue exist in this version only], Award BIOS type are flashed to the same version.
* Update Tool



Self Update activated.



Version Updated to 1.19d:

Changes:


* Add new feature for MSI's notebooks: Request a Custom BIOS/EC-FW
[This mode will appear only when tool is executed at msi's notebook,
will be not shown for desktop or other kind of msi's units]

Like "Mode 2" for desktop machines, "Point directly to MSI Beta BIOS" is N/A{not shown} for notebooks.
Now "Mode 2" "Request a Custom BIOS for my MSI Notebook" for notebooks is N/A{not shown} for desktop machines.
E.g. "Mode 2" vary depend of MSI's machine type where the tool is executed.


Self Update activated.



Version Updated to 1.19e:

Changes:


Desktop boards:

* Add Support for APTIO EFI based BIOSes, used on newest MSI's board s.1155
* Updated Mode 1 [Point to .zip, .rar BIOS archive]
  - Detect and proceed APTIO BIOSes and APTIO flashers

* Updated Mode 2 [Proceed BIOS file directly]
  - Detect, inspect and proceed APTIO AMI based MSI BIOSes and assign properly flasher
  - Included AMI's AFUDE234[certified by MSI]

* Updated Mode 3 [Live Update - Sure Hands]
   - Detect and proceed APTIO BIOSes and APTIO flashers

* Update after boot part
 - Add profile for APTIO AMI based MSI BIOSes + newest flasher for desktop boards
 - Detect and store[save] current installed APTIO EFI BIOS with original MSI's BIOS image name
 - M-Flash recovery ready [Automatically prepare the saved BIOS with original BIOS file name, ready for automatic recovery if needs]
 - Include own private backup, storage up to last 4 BIOS backups, where BACKUP.BIN is always the most recent BIOS backup.
 - Detect BIOS update failure while flashing, and perform automatic recovery attempts [up to 3]
 - Secure detect and validate target BIOS image, doing MD5 verification before proceed with BIOS flash attempt
 - Support APTIO Flash Back to Old saved BIOS by user request [Mode 3, after booting from the USB key]

Self Update activated.




Version Updated to 1.19e4:

Changes:


* Update while flashing logo with new improved one
* Update self drawing image art, moved 44% to center [+ regular ver. update per each version]
* Color coding for detected and saved BIOS with original name increased from 3 to 6,
 to make difference and to be more visible for eye:
 AMI/EFI, marketing number, chipset: Intel/AMD/Nvidia/VIA/SiS , retail model or not, Beta version or official.
/* Appear only for AMI and EFI based boards */
* Add own color for validated security result ID
* Update BK_IO2.ASM {
   - Add time halter for custom directives, to halt execution and count down for 10 seconds before resume,
   to prevent Rocket flashing, like: https://forum-en.msi.com/index.php?topic=144916.0

Hey just now i tried flashing my vbios on my gx640 using the MSI forum tool.

It completed without any errors and all that and it did say it was successful but it completed so fast i almost cant believe it.


      Apply to:  Notebooks flashing: [AMD's VBIOS, BIOS, EC-FW, BIOS & EC-FW at one], All-in-One PC and others customs
   - Add and replace with the same time halter for predefined directives to replace stop execution and waiting for input.
}

Self Update activated.



Version Updated to 1.19e5:

Changes:


 * Fine tune some of recently added features
 * Memtest86+ synchronization update in advance to version 4.20 [N/A yet],
 Tool will auto install[when internet connection is available],
  latest Memtest86+ version 4.20 [N/A yet] when its released.[expected to be released very soon]
 4.20 will support Intel Sandy Bridge and AMD Fusion

Self Update activated.



Version Updated to 1.19f:

Changes:


* Fixed issue: verification system out of sync when combined with Phoenix flash type, when are used predefined directives.
* Update bkmod.exe
* Update bk_io2.exe
* Update t9-246e.msi
* Update s14f9.exe
* Update hd.bsk


Self Update activated.




Version Updated to 1.19F1:

Changes:


* Updated sfx sound
* Updated bk_io2.exe
* Updated s14f9.exe
* Updated b4.bsk
* Updated engine.dtr
* Updated s14u6.exe
* Updated Mode 2 for desktop boards[point to BIOS directly, self detect bios type and assign proper flasher + auto protect BIOS image by MD5, this mode is N/A for notebooks]:
   - Updated both MSI's certified AMI's internal flashers [AFUDE234.EXE  &&  AFUD4310.EXE], v2.34 ==> v2.34.1 , v4.31B0 ==> v4.31B0.1 ,
   to implement custom UCP functions


Self Update activated.





Version Updated to 1.19R9:

Changes:


* Updated bk_io2.exe
* Updated s14f9.exe
* Updated engine.dtr
* Updated T9-246E.MSI
* LiveUpdate SureHands Update range to 1.G - 1.P for DKA790GX Platinum
* Fixed vairous of issues some of them cosmetic related.
* Fixed issue false bios corrutpion alert with latest UEFI BIOSes
* Fixed issue latest UEFI BIOSes are not detected as supported units under 32bit OS
* Updated secondary AMI's UEFI flasher to version v2.39b1  [Thanks to AMI and MSI]
* Patch AMI's UEFI flasher to sub version ID: v2.39b1.1 >>>|MSIHQ|<<< ,
 and implement custom enforced built-in parameters /P /B /N /S
* Fixed issue AMI's UEFI flasher when executed on AMD's UEFI machine when combined with ME DOS, hangs/lockups. [Thanks to AMI and MSI]




Self Update activated.



Version Updated to 1.20a:

Changes:


* Fixed issue Tool random hang during preparation in specified conditions under XP
* Fixed issue wrong flasher determination related to AFUD238S.exe which cause unable to flash Z** mainboards
* Mode 2: Updated secondary flasher to AFUD238S.exe


Self Update activated.



Version Updated to 1.21c:

Changes:


* Update BIOS image detection system


Self Update activated.




Version Updated to 1.22f:

Changes:


* Fixed validation warning issue that appears before flashing multiple/customized images
* Add flash in progress blinking notification when flashing multiple/customized images
* Reduce user time counter halter to 5 seconds.
* Speed up after flash image redraw by 400%


Self Update activated.



Version Updated to 1.24h:

Changes:


* Update again USB stick icon
* Fixed 2 cosmetic issues and adjust some text messages
* Code optimization
* Reduce the time given to reboot from OS when user answer with Y to reboot system from 45 to 20 sec
* Build and implement a new system to support BIOS & ME flashing


Self Update activated.




Version Updated to 1.25g:

Changes:


* Disable EC version reading for non supported NB units.
* Improve compatibility with some 3th party applications, which was causing a conflict with the tool and was unable to start.
* Modes are now named, to avoid confusion. IE: When you see instruction to Use mode 1 or mode 2, you can see them now in the menu. Not to guess who is who.
* Update BIOS raw flasher
* Add solution for MAC address lost issue when updating BIOS & ME
* Fixed issue tool unable to detect internet connection which cause to unable to self update and prevent to install memtestx86 on target storage. Root case, host check went down, its now replaced with more relative one.
* Detection file MSIHQ_INFO.TXT with board/bios/ec info is now transffered to the USB key while preparing target storage.
This would help in a case of problem, to be easy figured what went wrong. IE: We can see initial info of the user's machine BIOS info before the flash, even when user has no clue what was his older BIOS version.




Self Update activated.
NOTE: Please update to this version manually as older versions cannot update automatically to this version.

Version Updated to 1.26h:

Changes:


* Disabled self updater to fix unexpected start-up termination issue because update files was removed due server change
* Other minor improvements



Logged
Pages: [1]   Go Up