Need AFUDOS engineering edition to flash retail ASUS BIOS on prebuilt MB

[WithAlligators]

Hey guys, have an older ASUS Essentio CM5570 775 socket prebuilt. Not my main rig, but I'd like to play around with OCing it and putting a 771 modded CPU in there and maybe use it as a MAME rig.

Even though the MB is a PQ5L-VM-EMU (as hidden by a sticker) it's got a different BIOS and won't let me flash to the retail board version that has OC features.

There is a guide here where somebody documents how they did it.

Problem is, this far down the line, I can't seem to find the "engineering edition" anywhere.

I've made DOS bootable USBs using the HP tools with WIn 98 as well as with RUFUS and FreeDOS, and using AFUDOS 2.29ES and 3.36. I always get

ERROR: Unable to open ROM file I've downloaded the 0601 BIOS multiple times from ASUS and WImsBIOS. I've tried older BIOSes as well but can't seem to get past that error.

When I run AFUDOS in DOS it lists the version used and in parentheses says ASUS v2) making me think it's an ASUS version that won't let me flash the board with a different ROM.

Can anyone help or point me towards the file I need or an alternative BIOS flasher for AMI BIOSes?

Cheers in advance

 

[Burpo]

I don't know what the file name is you're using, but for it to work, the name of bios file can not be longer than 8 characters.

This page has AMI flash utilities.

https://www.wimsbios.com/amiflasher.jsp

I would try AMI Flasher at bottom of the page..
"AMI Flasher - DOS based AMI BIOS flasher
The following AMI Flasher tools can be used on AMI BIOS Core release 6.31 or earlier.
AMI Winflash - AMI Flasher (Windows based)
The following AMI Flasher tools can be used on AMI BIOS Core release 6.31 or earlier."

 

[tcsenter]

Try going through these:

https://www.bios-mods.com/downloads/


Or here for AFUDOS 229 ES: http://cid-988b91f35a949678.skydrive.live.com/self.aspx/Public/AFUDOS229ES.zip

 

[WithAlligators]

I have shortened the BIOS name to less than 8, I should have mentioned that. I have tried with a bunch of the versions of AFUDOS you guys have linked to with various errors. With v4.33 I get an error stating that the BIOS is incompatible with AMI, which is weird. Makes me think maybe the BIOS on ASUS's site is corrupted or something?

It also seems on the newer versions of AFUDOS that the commands and syntax have changed. There is the option to put an X in there to not check ROM ID. I have zero idea if this pertains to me or even how I would type it. I have just been doing

afudos/i(rom name).ROM/pbnc/n

I assume p is program main bios, b is program boot block, n is program NVRAM, but no idea of C, or what the following N command would be.

Here is the Readme:

Usage (applies to AFUWIN, AFUDOS, AFUEFI and AFUEFI64...
for usage of AFUBSD and AFULNX see help files provided in their folders):
------------------------------------------------------------------
AFUDOS <BIOS ROM File Name> [Option 1] [Option 2]
Or
AFUDOS <Input or Output File Name> <Command>
Or
AFUDOS <Command>

BIOS ROM File Name
The mandatory field is used to specify path/filename of the BIOS ROM file with extension.

Commands
The mandatory field is used to select an operation mode.
- /O Save current ROM image to file
- /U Display ROM File's ROMID
- /S Refer to Options: /S
- /D Verification test of given ROM File without flashing BIOS.
- /OAD Refer to Options: /OAD
- /A Refer to Options: /A
- /CLNEVNLOG Refer to Options: /CLNEVNLOG
Options
The optional field used to supply more information for flashing BIOS ROM. Following lists the supported optional parameters and format:
- /Q Silent execution
- /X Don't Check ROM ID
- /CAF Compare ROM file's data with Systems is different or
not, if not then cancel related update.
- /S Display current system's ROMID
- /HOLEOUT: Save specific ROM Hole according to RomHole GUID.
NewRomHole1.BIN /HOLEOUT:GUID
- /SP Preserve Setup setting.
- /Rn Preserve SMBIOS type N during programming(n=0-255)
- /R Preserve ALL SMBIOS structure during programming
- /B Program Boot Block
- /P Program Main BIOS
- /K Program all non-critical blocks and ROM Holes.
- /N Program NVRAM
- /Kn Program n'th non-critical block or ROM Hole only(n=0-15).
- /HOLE: Update specific ROM Hole according to RomHole GUID.
NewRomHole1.BIN /HOLE:GUID
- /L Program all ROM Holes.
- /Ln Program n'th ROM Hole only(n=0-15).
- /E Securely Flash Embedded EC at Runtime
(If system supports. Can be overriden by other options)
- /OAD Delete Oem Activation key
- /A Oem Activation file
- /E Program Embedded Controller Block
- /ECUF Update EC BIOS when newer version is detected.
- /ME Program ME Entire Firmware Block.
- /MEUF Program ME Ignition Firmware Block.
- /CLNEVNLOG Clear Event Log.
- /CAPSULE Override Secure Flash policy to Capsule
- /RECOVERY Override Secure Flash policy to Recovery
- /EC Program Embedded Controller Block. (Flash Type)
- /REBOOT Reboot after programming.
- /SHUTDOWN Shutdown after programming.

Rules
- Any parameter encolsed by < > is a mandatory field.
- Any parameter enclosed by [ ] is an optional field.
- <Commands> cannot co-exist with any [Options].
- Main BIOS image is default flashing area if no any option present.
- [/REBOOT], [/X], and [/S] will enable [/P] function automatically.
- If [/B] present alone, there is only the Boot Block area to be updated.
- If [/N] present alone, there is only the NVRAM area to be updated.
- If [/E] present alone, there is only the Embedded Controller block to be updated.


Anybody?

 

[Burpo]

Did you try any WinFlash utilities?
Definitely will be easier..
Did you try AMI Flasher?

 

[tcsenter]

afudos/i(rom name).ROM/pbnc/n

Need spaces (represented here with underscore):

afudos_/i[filename].rom_/pbnc_/x

 

[vailr]

http://forums.tweaktown.com/gigabyt...ng-stability-tools-post284763.html#post284763

One of these should work:
AWARD BIOS Tools AMI (UEFI)

FPT_DOS- Z77/X79 FPT_DOS- Z87
FPT-Win64- Z87 FPT-Win32/64- Z97
FPT-Win32/64- X99 FPT-Win32/64- Z170
FPT- Flash Programming Tool v8.1.20.1309
Flash Programming Tool v8.1.40.1456 (for Intel® 7)
Flash Programming Tool v9.0.22.1467 (for Intel® 8)
Flash Programming Tool v9.1.2.1000 (for Intel® 9)
Flash Programming Tool v10.0.30.1054 (for Intel® Broadwell)
Intel® System Tools v.8.1.52.1496 (for Intel® 7)
Intel® System Tools v.9.0.21.1452 (for Intel® 8)
Intel® System Tools v.9.1.2.1000 (for Intel® 9)
Intel® System Tools v.11.0.0.1202 (for Intel® 100)
FTK- Flash ToolKit v0.11 (for Intel® 6/7)
FTK- Flash ToolKit v0.10 (for Intel® 8)
FD44Editor 0.9.1

 

[tcsenter]

FWIW, ASUS used to have a habit of using a different board or with different options in it's barebone systems and prebuilt computers even though the motherboard was denoted with the same model designation as one of it's retail boards. It wasn't just an issue of the retail board having a different BIOS. The board was often NOT the same as the retail model, had different options such as LAN or Audio chip.