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.

@lordkag
I think it's better search will take longer, but will be more reliable. ;)

@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.

@Fernando

Insyde H2OEZE (Ease Binary Editor) Version 100.00.02.10 is leaked; can be useful for replacing OROMs in non-encrypted Insyde firmwares.

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?

Zitat von kevindd992002 im Beitrag #101

---

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?

---

Zitat von Fernando im Beitrag #106

---

Zitat von SoniX im Beitrag #105

---

Make a new UT and maintain old...

---

What means "UT"?

---

0.30 is the new version, so it's nothing pointless here.
Speaking about AptioV support: what kind of "support" are you waiting for? What 0.20 makes wrong with AptioV?