Not solvable for this machine 'cause it is a desktop computer using mobile CPU.
Detailed reason is written here: https://github.com/ShikiSuen/GB-BNi7HG4-950-macOS-10.13
May I confirm whether installing BCM94352Z to Lenovo ThinkPad T470 (incl. ThinkPad XXV) requires bypassing the whitelist from the actual UEFI firmware?
You need to check this comment on the GitHub:
https://github.com/Piker-Alpha/ssdtPRGen.sh/issues/314#issuecomment-287240938
I personally don't think it could work for BRIX because it needs a "HWP support model" in your Clover settings: e.g. MacBook9,1, MacBookPro13,1, MacBookPro13,2...
Sorry I was asking not the difference between "installing to system volume" and "installing to clover".
I was asking whether the following 4 kexts are absolutely fine to move from /System/Library/Extensions to /Library/Extensions:
BrcmFirmwareRepo.kext
BrcmPatchRAM2.kext...
I have one more question: Since I prefer to install kexts into Clover, is it okay to only install the following kexts to Clover (and leave the S/L/E intact)?:
BrcmFirmwareData.kext
BrcmPatchRAM2.kext
FakePCIID_Broadcom_WiFi.kext
FakePCIID.kext
Thanks. I suddenly realized that I messed the filename up. I should install BrcmPatchRAM2.kext in lieu of BrcmNonPatchRAM2.kext.
Update: Now my BT is fully-functional.
Update: I confirmed that the following kexts have been installed on my BRIX:
BrcmFirmwareRepo.kext
BrcmNonPatchRAM2.kext
FakePCIID_Broadcom_WiFi.kext
FakePCIID.kext
The soft-rebrand method you suggested is what I am using at this moment (Bluetooth not work. Probably sth wrong with what I did).
So, "only hard-rebrand the BCM4352 to BCM4350 or BCM4360 without any non-apple kexts" won't work, right?
Hi, I am trying to rebrand my BRCM94352Z (as the "initially" below) for the sake that macOS could natively support it.
Name Vendor Device SubVen SubDev Name
Initially 14E4 43B1 17AA 0623 BCM4352(Rev.03)
New-01 14E4 43A3 106B 0159 BCM4350 (the one...
Then there must be a disk failure. Looks like the topic could get stopped since both you and I know at least the latest version of clover and its installer behave as what you said. I apologize for making my statements too early prior to notice the file system problems.
One more thing: I use Clover v3961 since when it was released till now.
Just now I updated it to v3974 and confirmed it automatically installs the christmas and the newyear theme. This time Clover does not automatically recover these themes after manual removal.
At this point, I would rather...
I wrote the following sentence in my 1st reply to this thread:
I then made sure that there's no "newyear" or "christmas" folder there
Everything is because Clover automatically install the christmas / newyear themes everytime I remove them.
I don't know why you enjoy blaming me so much for my...
I rechecked all EFI volumes of my all internal hard drives and again confirmed what you assumed is totally wrong.
I just noticed that the newyear theme got automatically installed right after the removal of the blank christmas folder.
I duplicated the theme I preferred as doppelgangers named in...
This doesn't work on my machine. I did checked the theme folder, found a blank folder called "christmas". I then made sure that there's no "newyear" or "christmas" folder there, restart, and this G-damn Christmas theme still gets activated. Wondering what the bloody hell the developers think...
Unable to test it anymore on my side. I already sold my skull canyon out through eBay. Skull Canyon has really bad thermal design and always thermal throttling. Still thanks for your intel.
I just tried iMac 14,2 on my Brix but I still have to use CPUS=X (X=Hyperthreading cores - 1) to boot macOS Sierra.
Good thing is that I won't need AGDPFix anymore. Thanks for your suggestion.
Please remove my previous reply. I think I had messed up something. The board-id is still there, and I am still thinking of possible ways to make a clover hotfix possible.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.