macOS High Sierra Public Beta 5 is Now Available

[seyedhossein]

flash beta 5 on GA-Z170X-UD5
An error occured while verifying firmware

chang smbios to 14,2
An error occured while verifying firmware


SMBIOS:

any idea?

 

[robinzon66]

flash beta 5 on GA-Z170X-UD5
An error occured while verifying firmware

chang smbios to 14,2
An error occured while verifying firmware


SMBIOS:View attachment 273100


any idea?

I have same problem. An error occurred while updating firmware during clean install.

 

[Gigamaxx]

Did you run the beta utility app? It is needed to download but it is also needed on System to be installed on.

 

[seyedhossein]

Did you run the beta utility app? It is needed to download but it is also needed on System to be installed on.

success
install macOSPublicBetaAccessUtility in beta 4
upgrade to beta 5 (download from App Store)

Thanks for help
what about fresh install beta 5
how can install macOSPublicBetaAccessUtility?!

Regards

 

[clueluzz]

I was under pressure, I just picked up a Radeon Vega 64 video card and wanted the latest drivers from High Sierra. It brought native Audio via HDMI and Displayport to the card. Only fix needed is the name, its AMD RX xxx, but thats an easy fix.

Radeon Vega 64 works OOB? Do you see the boot screen or is it black?

 

[Gigamaxx]

Radeon Vega 64 works OOB? Do you see the boot screen or is it black?

In High Sierra it is the boot screen. Its funny, even with My IGPU as primary it still gets signal, which is different from any other recent AMD cards like Polaris and Fiji etc.

Bios settings IGPU disabled the Vega starts the boot gets the drop off at initialization (black screen) 1-2 seconds then the progress bar pops back up, finishes and your in High Sierra. Just like an Nvidia card or older Radeons. No need for IGPU and it works with or without the lilukext and WhateverGreenKext. There is HDMI Audio.

 

[clueluzz]

In High Sierra it is the boot screen. Its funny, even with My IGPU as primary it still gets signal, which is different from any other recent AMD cards like Polaris and Fiji etc.

Bios settings IGPU disabled the Vega starts the boot gets the drop off at initialization (black screen) 1-2 seconds then the progress bar pops back up, finishes and your in High Sierra. Just like an Nvidia card or older Radeons. No need for IGPU and it works with or without the lilukext and WhateverGreenKext. There is HDMI Audio.

View attachment 273181View attachment 273183

Thanks! Time to hunt!

 

[Macboy123]

I have same problem. An error occurred while updating firmware during clean install.

I had the same problem with Haswell Z97X Gaming 3 Board and 14,2 iMac Retina SMBIOS.
Clover newest version 4173 (!) solved it for me, since then the firmware update error gets away, because Clover recognizes to use Firmware Version IM221........ for Beta 5 (Dev Beta 6)

The one in the screenshot in the post up to yours is much too old!

 

[OlliverAira]

In High Sierra it is the boot screen. Its funny, even with My IGPU as primary it still gets signal, which is different from any other recent AMD cards like Polaris and Fiji etc.

Bios settings IGPU disabled the Vega starts the boot gets the drop off at initialization (black screen) 1-2 seconds then the progress bar pops back up, finishes and your in High Sierra. Just like an Nvidia card or older Radeons. No need for IGPU and it works with or without the lilukext and WhateverGreenKext. There is HDMI Audio.

View attachment 273181View attachment 273183

What do you like the GPU? Colours beat Nvidia? My father bought an Apple Thunderbolt monitor for my Hackintosh, I will (probably) be running it with a Asus ThunderboltEX 3. Right now I use a GTX 1060, but since I got the monitor I might upgrade... Do you think its worth getting a VEGA 64?

Also, I will probably wait until ASUS ROG releases there Strix version since I probably will play some games like Star Wars battlefront 2 and Left 4 Dead on Windows <3

 

[Lundli]

So I finally figured it out, was stuck on "An error occurred while verifying firmware" while trying to do a clean install.. solution (for me) was to disconnect all HDs except the drive I was about to install to. After that everything went as smooth as usual.