Your Mac needs a firmware update after installation [Bug]:

[divemasterjm]

Machine Model

MacBook8,1

Application Version

Latest Release

Application Variant

GUI (Graphical User Interface)

What versions of macOS are you seeing the problem on?

macOS 12, Monterey

Where does this issue happen?

Between booting macOS and Login Screen

What is the Isssue?

after selecting drive, installation starts and when finish i receive a message Your Mac needs a firmware update, nothing related with afps or volume, is after installing monterrey, and before rebooting i receive this message and cant continue, the only option i have is reboot.

Any Additional Information

No response

[Ausdauersportler]

Please use forums or Discord to trouble shoot. Please update to the latest OCLP version when installing Monterey.

[divemasterjm]

Please use forums or Discord to trouble shoot. Please update to the latest OCLP version when installing Monterey.

i've been searching before posting no one post related to my problem, the issue is when starting macos assistant i have this error, sorry but what do you mean with latest OCLP?, im using the latest OCLP GUI from yesterday

[Ausdauersportler]

OpenCore Legacy Patcher aka OCLP - the latest version is 0.3.1.
Apple introduced a new firmware check, but this has been solved a few days ago. If the latest version 0.3.1 does not solve it try the nightly builds available from the same Github download page.

[divemasterjm]

OpenCore Legacy Patcher aka OCLP - the latest version is 0.3.1. Apple introduced a new firmware check, but this has been solved a few days ago. If the latest version 0.3.1 does not solve it try the nightly builds available from the same Github download page.

the problem is that i cant boot my mac, i dont know how to solve it, btw 0.3.1 is the one i've used yesterday to create USB

[Ausdauersportler]

In worst case you always can use the internet revocery to install the latest supported macOS version, again. IMHO you should be able to boot using alt/option and select and start the still existing former macOS version. The update failed, the old installation will be still in place.
Since this is clearly trouble shooting please join Discord.

[divemasterjm]

Thanks i recover old macos version i'm on big sur latest as my mackbook 8,1 support it, i will try with the latest nightly build, now is installing again, 17 min left, we will see if i've got same error after.

[Patafil]

I have the same problem, I tried the nightly build 0.3.2, no success.

[tonybernardo]

Same issue on a MacPro3,1 running 11.6. Installation was tried with OPCL0.31

[crystall1nedev]

https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#stuck-on-your-mac-needs-a-firmware-update

[divemasterjm]

Thanks i recover old macos version i'm on big sur latest as my mackbook 8,1 support it, i will try with the latest nightly build, now is installing again, 17 min left, we will see if i've got same error after.

same error (((

[divemasterjm]

https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#stuck-on-your-mac-needs-a-firmware-update

in my case is not a volume problem

[crystall1nedev]

dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#stuck-on-your-mac-needs-a-firmware-update

in my case is not a volume problem

The same techniques can still apply.

[divemasterjm]

dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#stuck-on-your-mac-needs-a-firmware-update

in my case is not a volume problem

The same techniques can still apply.

i started this at the beginning making a partition but didnt work, then i've tried with real macos partition and have same issue

[attaxia]

Same issue here, trying to upgrade from Big Sur. WIth 12 minutes left the screen goes black without warning, reboots, and get the following error:

[khronokernel]

Verify with mainline, firmware check is not run on spoofless systems

[divemasterjm]

Verify with mainline, firmware check is not run on spoofless systems

What do you mean? I don't understand sorry

[Ausdauersportler]

Download the latest nightly build (links are posted on main Github page) and try it and report back.

Copied from the release notes:

VMM Usage Notes

Run down on quirks users should keep in mind when using a spoofless system:

Requires macOS 11.3 or newer
For 11.2.3 and older use Minimal or higher spoofing
Certain applications may need to be re-authorized as they think the machine has been changed
Macs with upgraded AMD Polaris dGPUs will default to Minimal to ensure H.265 support
macOS Monterey Betas will not see macOS updates till 12.1 Beta is seeded
Apple issue affecting supported Virtual Machines as well, updating via InstallAssistants to get to 12.0.1 is recommended
Certain OCLP features such as CPU renaming will be non-functional due to the lack of SMBIOS spoofing
Functionality can be restored by selecting Minimal spoof (or higher) in SMBIOS settings

[Patafil]

Used nightly 0.3.2, have enabled "Moderate SMBIOS Patching", stiil the same issue on my Macbook8,1

[tonybernardo]

This issue should not be closed.

Used nightly 0.3.2, have enabled "Moderate SMBIOS Patching", stiil the same issue on my MacPro3,1

[segaddict]

same here, on macpro 3.1 and 5.1, error message "Your Mac needs a firmware update" at first start after installation.
I tried the proposed solutions but does not work
same USB key, same Install monterey.app
does not work on the 2 macpro but works perfectly on macbook pro 11.1

[crystall1nedev]

@Patafil @tonybernardo Because you both did it wrong. @khronokernel said:

Verify with mainline, firmware check is not run on spoofless systems

You need to disable SMBIOS spoofing. Currently the GUI is not capable of this, so you need to grab the TUI version of the latest build.

1. Open the TUI .app
2. Press 4 to enter the Patcher Settings menu.
3. Press 3 to enter the SMBIOS submenu, then 1 to enter the SMBIOS spoof level submenu.
4. Press 0 to change the spoof level to None. This will disable SMBIOS spoofing, and it should work correctly.

[tonybernardo]

@Patafil @tonybernardo Because you both did it wrong. @khronokernel said:

Verify with mainline, firmware check is not run on spoofless systems

You need to disable SMBIOS spoofing. Currently the GUI is not capable of this, so you need to grab the TUI version of the latest build.

1. Open the TUI .app
2. Press 4 to enter the Patcher Settings menu.
3. Press 3 to enter the SMBIOS submenu, then 1 to enter the SMBIOS spoof level submenu.
4. Press 0 to change the spoof level to None. This will disable SMBIOS spoofing, and it should work correctly.

This setting does not exist. There's only minimal, moderate, or advanced.

[tonybernardo]

[Patafil]

@Patafil @tonybernardo Because you both did it wrong. @khronokernel said:

Verify with mainline, firmware check is not run on spoofless systems

You need to disable SMBIOS spoofing. Currently the GUI is not capable of this, so you need to grab the TUI version of the latest build.

1. Open the TUI .app
2. Press 4 to enter the Patcher Settings menu.
3. Press 3 to enter the SMBIOS submenu, then 1 to enter the SMBIOS spoof level submenu.
4. Press 0 to change the spoof level to None. This will disable SMBIOS spoofing, and it should work correctly.

I tried before without touching the SMSBIOS spoofing and had the same issue. Enabling or changing it didn’t helped.

[segaddict]

@Patafil @tonybernardo Because you both did it wrong. @khronokernel said:

Verify with mainline, firmware check is not run on spoofless systems

You need to disable SMBIOS spoofing. Currently the GUI is not capable of this, so you need to grab the TUI version of the latest build.

1. Open the TUI .app

2. Press `4` to enter the Patcher Settings menu.

3. Press `3` to enter the SMBIOS submenu, then `1` to enter the SMBIOS spoof level submenu.

4. Press `0` to change the spoof level to `None`. This will disable SMBIOS spoofing, and it should work correctly.

thank, it gave me the way, (I was using the GUI version)
patcher settings:
-security settings:
disable SIP
-SMBIOS settings:
spoof level: moderate
It works !

[divemasterjm]

@Patafil @tonybernardo Because you both did it wrong. @khronokernel said:

Verify with mainline, firmware check is not run on spoofless systems

You need to disable SMBIOS spoofing. Currently the GUI is not capable of this, so you need to grab the TUI version of the latest build.

1. Open the TUI .app

2. Press `4` to enter the Patcher Settings menu.

3. Press `3` to enter the SMBIOS submenu, then `1` to enter the SMBIOS spoof level submenu.

4. Press `0` to change the spoof level to `None`. This will disable SMBIOS spoofing, and it should work correctly.

thank, it gave me the way, (I was using the GUI version) patcher settings: -security settings: disable SIP -SMBIOS settings: spoof level: moderate It works !

it worked also for me.
Thanks!!!!!

[Patafil]

@Patafil @tonybernardo Because you both did it wrong. @khronokernel said:

Verify with mainline, firmware check is not run on spoofless systems

You need to disable SMBIOS spoofing. Currently the GUI is not capable of this, so you need to grab the TUI version of the latest build.

1. Open the TUI .app

2. Press `4` to enter the Patcher Settings menu.

3. Press `3` to enter the SMBIOS submenu, then `1` to enter the SMBIOS spoof level submenu.

4. Press `0` to change the spoof level to `None`. This will disable SMBIOS spoofing, and it should work correctly.

thank, it gave me the way, (I was using the GUI version) patcher settings: -security settings: disable SIP -SMBIOS settings: spoof level: moderate It works !

it worked also for me. Thanks!!!!!

But with what settings? One writes to disable SMBIOS spoofing (which was disabled in the first place), the other to enable it with spoof level: moderate.

[divemasterjm]

Moderate and sip off

[Patafil]

Moderate and sip off

Thank you