Hi Chris I have been trying to install both packages but result is the same for my 9470m no dsdt found in efi folder so I cannot boot into bigsur or Monterey The installation log shows no patchmatic found
/MYPatcher: line 25: ./patchmatic: No such file or directory
/MYPatcher: line 29: ./iasl: No such file or directory
Apr 22 11:10:39 MacBook-Air package_script_service[1328]: ./postinstall: ./MYPatcher: line 36: ./iasl: No such file or directory
Apr 22 11:10:39 MacBook-Air package_script_service[1328]: ./postinstall: ./MYPatcher: line 44: ./iasl: No such file or directory

Any ideas why is doing this this is both with clover and oc...

Good afternoon,

In my HP EliteBook 2570P I had an Atheros AR9280 working well in Big Sur, but in Monterey is out totally, so I tried to buy this BCM943224HMS that I read here is compatible with Monterey, but after doing a lot of tries, I only could get it working through Big Sur, but with a modification, deleting into AirPortBrcmFixUp.kext the 94360 injector from Plugins folder.

And after that in Big Sur 11.6.6 is working perfectly, but I read here acidanthera/bugtracker#1929 that there is a problem with Monterey 12.1+ related with the BCM 94360, I tried a lot of kexts and modifications, so in the previous link, I tried some debug files, and the option "brcmfx-delay=(15000 | 27000 | 30000)". Nothing of that solves the problem.

But I read that on Monterey 12.0.1 is working the card (94360), so I create a 12.0.1 installer, and after booting up the recovery, voila, the WiFi is working fine (my 943224HMS), installation of 12.0.1 too, but I also got working WiFi in Monterey 12.3.1 but only in the recovery, not in the 12.3.1 installed, here the system crash after reading the kext, and gets into a KP, and I stuck here.

I always follow yours guides, I read that you recommend this card for our HP Ivy Bridge laptops, and so, I bought this (14e4:4353), but it works up to 12.0.1, and after putting the AirPortBrcmFixUp.kext in 12.1+ results into a KP, so I understood the problem was the same as in the 94360 (14e4:43a0). The curious case is that with 12.3.1 recovery boots without any problem and WiFi at recovery works perfectly, but in a 12.3.1 installation that is the problem.

Also I know that with 94360 (14e4:43a0) and 12.1+ there is a bug from Apple side.

PD: I´m "asdesoso" from InsanelyMac, that in the past I gave some feedback about your installers for EliteBook and ProBook.

Thank you very much.

Cheers.

..

.

Hello :),
i really appreciate this magnificent project, thanks Chris!
I found an issue on my 2170p (3427u, 8GB DDR3, HD4000) with the Cpu Req on Intel Power Gadget, which remain to max frequency all the time, even if Power Management seem to be OK.
This cause an higher watt consumption in idle than Catalina / Windows.

monterey details

Catalina Details

I tried both OC and Clover versions. With these last updates, now also OC work as same as Clover (previously the CPU remain locked at 1,7Ghz), so now both have same issue, above descripted. In any case Clover version is far more stable than OC, which occasionaly reboot itself.
I can't figure it out.
Catalina EFI is based on Clover 5103, found on a chinese site (i cannot remember the name, but if you need i will share the zip).

Bye,
Paolo.

Hi Chris,
Do you know if BCM943228HMB will work on HP ProBook 4440s and Monterey?

Feature request? Could you make a video tutorial on how to convert Clover EFI to OC EFI from elitebook users who installed Monterey using the clover package creator.

I have a perfectly working Monterey on my elitebook and I used the clover package creator to install it. Now I want to change the bootloader to OC without having to reinstall Monterey. Perhaps you could make a video, or a README on how to accomplish this?

A table in the readme would be helpful to inform about what OS version can be put on the USB from what running OS version. That would save some users (like me...) some fruitless tries.

Columns: OS version to install on USB;
rows: OS version the Install Media HP Laptop Clover.app runs in;
cells: " ✔︎ " or " ✖︎ ".

In main.scpt, you could shorten the code and eliminate a user interaction (with its own possibility of user error). Let the user directly chose what they want on the USB ("... your Install OS X.app or Install macOS.app ...").

Then read its version from Finder info and do an if-then for the few differences between ≤10.12 and ≥10.13 (estimated time, and a shell script argument).

Before:

--If 10.9 to 10.12
		display dialog "\nmacOS 10.12\nChoose the location of your Install macOS.app\n" with icon note buttons {"Quit", "Continue"} cancel button "Quit" default button {"Continue"}
...
		set progress description to "Create Install Media\n======================================\nInstallation time 15 to 20 min on a standard USB key\n3 to 5 min on a Disk Ext HD\n======================================\n"
...
		set cmd to "sudo \"" & OSXInstaller & "Contents/Resources/createinstallmedia\" --volume /Volumes/Install-Media --applicationpath \"" & OSXInstaller & "\" --nointeraction "

and:

--If 10.13 to Ventura 13
		display dialog "\nYour choice is 10.13 to Ventura 13\nChoose your Install OS X.app \nFrom macOS High Sierra to macOS Ventura" with icon note buttons {"Quit", "Continue"} cancel button "Quit" default button {"Continue"}
...
		set progress description to "Create Install Media\n======================================\nInstallation time 15 to 25 min on a standard USB key\n3 to 5 min on a Disk Ext HD\n======================================\n"
...
		set cmd to "sudo \"" & OSXInstaller & "Contents/Resources/createinstallmedia\" --volume /Volumes/Install-Media --nointeraction "

After, (not checked for errors):

display dialog "Choose the location of the OS version you want to install (the \"Install macOS.app\" or \"Install OS X.app\"\n" with icon note buttons {"Quit", "Continue"} cancel button "Quit" default button {"Continue"}

if 10.9 to 10.12 then set Params to {20, " --applicationpath \"" & OSXInstaller & "\""}
if 10.13 to 13 then set Params to  {25, ""}
else stop script
...
set progress description to "Create Install Media\n======================================\nInstallation time 15 to " & item 1 of Params & " min on a standard USB key\n3 to 5 min on a Disk Ext HD\n======================================\n"
...
set cmd to "sudo \"" & OSXInstaller & "Contents/Resources/createinstallmedia\" --volume /Volumes/Install-Media" & item 2 of Params & " --nointeraction "

This would also make modifications for future changes easier, just add a branch to the if statement.

The CC Clover throws an error, when it tries to build a USB from a macOS installer that was downloaded and build with gibmacOS.

Tried with
Ventura 13.0.1 (22A400)
Big Sur 11.7.1 (20G918)
Monterey 12.6.1 (21G217)