[Guide] HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch (10.11)

[Krazy-Killa]

@RehabMan in your sample ProBook configs the "10.10.2+ 5Ghz US FCC, the-darkvoid" is set with MatchOS only to 10.10.x and 10.11.x. Shouldn't the MatchOS value include 10.12.x too since it's named "10.10.2+"?

If I recall the 5GHz patch is no longer needed for 10.12, but a different patch is indeed required which is the next patch in the list.

            <dict>
                <key>Comment</key>
                <string>10.10.2+ 5Ghz US FCC, the-darkvoid</string>
                <key>Find</key>
                <data>
                QYP8/3QsSA==
                </data>
                <key>MatchOS</key>
                <string>10.10.x,10.11.x</string>
                <key>Name</key>
                <string>com.apple.driver.AirPort.Brcm4360</string>
                <key>Replace</key>
                <data>
                ZscGVVPrKw==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>AirPortBrcm4360 - fcvo, 10.12.x (credit the-darkvoid)</string>
                <key>Find</key>
                <data>
                gflSqgAAdSk=
                </data>
                <key>MatchOS</key>
                <string>10.12.x</string>
                <key>Name</key>
                <string>com.apple.driver.AirPort.Brcm4360</string>
                <key>Replace</key>
                <data>
                gflSqgAAZpA=
                </data>
            </dict>

 

[philip_petev]

That patch is still needed, especially if you live outside USA and want to use your country's WiFi regulatory.

 

[RehabMan]

@RehabMan in your sample ProBook configs the "10.10.2+ 5Ghz US FCC, the-darkvoid" is set with MatchOS only to 10.10.x and 10.11.x. Shouldn't the MatchOS value include 10.12.x too since it's named "10.10.2+"?

Different patches for 10.10/10.11 vs. 10.12.
No 5ghz patch required for 10.12.
10.12 has 'fcvo' patch instead.

 

[RehabMan]

I too have had this problem in the past as well. I don't recall if I ever found a suitable solution, I just stopped putting it to sleep that way. The only consistent sleep wake pattern that works for me is to unplug from power source and put to sleep via menu then close lid after the leds start flashing in sleep mode. When returning to a power source I have to wake it up before plugging in the power cord or it never detects the power cord plugged in.

So the problem only occurs on AC power?
Make sure you're testing with current BIOS and current githib content.

 

[RehabMan]

That patch is still needed, especially if you live outside USA and want to use your country's WiFi regulatory.

The repo does not provide patches for non-US regions.
That is something an individual must do themselves.

 

[the_chiefgeek]

So the problem only occurs on AC power?
Make sure you're testing with current BIOS and current githib content.

Hmm. I was never able to narrow down to exact steps that trigger it.

I have the latest bios and latest github repo (looks like it has already been updated to BATT-G4), I hit F4 at boot. I tried to reproduce any odd sleep behavior and it is working fine right now.

 

[philip_petev]

The repo does not provide patches for non-US regions.
That is something an individual must do themselves.

I know, that's why I modified it to match my country (BG). So, this one is actually optional for 10.12.x...

 

[RehabMan]

Hmm. I was never able to narrow down to exact steps that trigger it.

I have the latest bios and latest github repo (looks like it has already been updated to BATT-G4), I hit F4 at boot. I tried to reproduce any odd sleep behavior and it is working fine right now.

So your problem is intermittent and not reproducible currently...
Which seems a bit different from what @philip_petev is reporting.

 

[RehabMan]

So, this one is actually optional for 10.12.x...

I removed the US one for 10.12 when I noticed it seemed to have no effect for me.

 

[VioletDragon]

Does anyone on here have any problems with instant reboot after sleep after rebooting from Windows 10 back into macOS. The funny Ethernet problem is also caused by rebooting out of Windows 10. Doing a EC Reset seems to fix this until i boot back into Windows 10.