Sometimes Avast will tell you that a file you are downloading is a virus and stop it but if you scan it after downloading it locally it doesn’t report anything. Weird stuff with their web threat detection.
@SoniX
Just in case you are planning to release a new version, here is 1022-7805-8803 AMD RAID 7.0.0-00087 from HP. No EFI, unfortunately.
1022-7805-8803 AMD RAID 7.0.0-00087.rar (37.6 KB)
I think that needs to be upgraded. Version 7 is new and it is possible that what you are corrected minor errors.
Dear Sonix,
As you might or might not know, the Asus UEFI vBios updater is a crappy program that doesn’t work well.
It often just cannot get the proper update file,let alone update the graphics card. And it has this stupid restriction so that it won’t work with a non-Asus motherboard, even if you have a Asus graphics card. Amd only the top-line boards are 'supported’
Thanks to a guy on the ROG forum i have deciphered the way that the Asus UEFI vBios updater tool would find an update for Asus graphics cards.
It uses a part of the hardware id’s and crafts a URL to download the proper file. This doesn’t work because of uppercase/lowercase mixup. Find this information in the last few posts of rog.asus.com/forum/showthread.php?32906-ASUS-UEFI-vBIOS-tool-for-GTX-600-series-cards!-It-s-Here!/page17 … Sorry,you need to copy paste it…
This updating process could be automised i guess; look up hardware-id’s->craft the URL->compare firmware with available firmwares->download proper file->(make vBios backup)->flash new file with nvflash(for windows)
Would you like to create a Asus UEFI vBIOS Updater or perhaps implement this in UEFI BIOS Updater?
your link is broken
Whose link?
If you should mean IMWeasel’s, his link is not broken, but redirected by your browser’s addon.
IMweasel’s link! sorry!
Then you don’t mind an AMD RAIDXpert2-F10 7.1.0-00019 found in HP, do you?
This time only EFI.
AMD RAIDXpert2-F10 7.1.0-00019.rar (67.2 KB)
@lordkag
#Extractor4
This BIOS from Supermicro files EFI LAN Intel and Marvell AHCI are not defined, so as unknown GUID. I think that you need to search for modules not GUID, and on the content. The latest versions UBU such a search is gradually being implemented.
marvel sata efi/rom causing system to hang a little @ startup, was able to get into marvel utility "bios version : 1.0.0.1038 , Firmware : 2.3.0.1006". Flashing bios with everything but marvel update = no hang.
@SoniX
I realized that no matter how many GUIDs I add, there will always be other appearing in the wild, so I went to use UEFIFind. I have run them side by side for quite a while and the results were good. Not only the new path has found the GUIDs that were stored in the .bat, but also found some new ones. So I removed the GUID search for pretty much everything. Not surprisingly, I ended with the same patterns you used in UBU. Now I only have to find a good compromise: if I use just one pattern for each EFI, some very old or very new versions might be missed; if I use too many patterns, will catch all of them, but the script will take too long.
#Extractor5.rar (57 KB)
@SoniX
AMD is on fire lately! Here is AMD GOP 1.57.0.0.0 from this Asrock. Released on Jan - 9 - 2015, it is as fresh as it can be. A list of supported IDs is also attached.
It is also the first time I see a Godavari AGESA.
AMD GOP 1.57.0.0.0.rar (47.9 KB)
@Fernando
Insyde H2OEZE (Ease Binary Editor) Version 100.00.02.10 is leaked; can be useful for replacing OROMs in non-encrypted Insyde firmwares.
@ SoniX:
Thanks for the update.
@ all:
Within my OneDrive host folder you find the newest UBU tool v1.13, where the UBU_Upd_1.exe file has already been inserted.
Do you have to do the manual running of the "ubu_upd1" with the new version of ubu to actually update the driver inside the tool?
Does anybody know when the next release of UEFITool will most likely be? I have noticed there hasn’t been a new version release for a while.
Am I correct that the 0.20.x branch is now finished and the next release will be a completely new branch with more support added and improvements?
As soon as it be ready. Yes, 0.20 branch is finished and no new features will be added there, only bugfixes.
There are some big changes in modern UEFI images (fixed files, FFSv3, data in non-standard places, etc.) that are hard to support without a complete rewrite of the engine, that is why I’ve decided to stop adding feature and do this rewrite until it’s too late.
New engine is about 40% done now, and I hope in a month or two (it depends on my load at the main job, UEFITool is just a hobby project, you know) I can release a 0.30.0 version with the new engine integrated and some cool new features added.
I take it the new version will have even better support for Aptio V BIOS?