Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I wrote a small dyld (in C), and added it to DYLD_INSERT_LIBRARIES section in /System/Library/LaunchDaemons/com.apple.softwareupdated.plist. It's simply patch sysctl request, to softwareupdated thinks this is a Virtual Machine (VMM). I am checked all current catalogue files and preinstall/postinstall scripts, it's seems to be the safest method. If i modify the patch to patch board id and model id, thats method fails when a firmware update comes and the installer try to update it (it's occurs boot loop, and requires a pram reset). It's works fine when i disable SIP only with the '--without debug' option. Patched kexts is also works with SIP when i sign all of the kexts with my own mac developer key.
you're a genius! when will it be released?
 
try to replace Apple_iSight.kext from 10.11.6 @dosdude1

(I am the guy with the -not detected- integrated iSight camera)

Thank you parrotgeek1 !!
I am trying to install "Apple_iSight.kext" with the app:
Kext Utility
v2.6.6
for mac OS 10.5-10.12

but i am having no success:
"The system extension "APExtFramebuffer.kext" is not compatible with this version of OS X and can’t be used."

is there any other way to install the "Apple_iSight.kext"?
----Edit---> APExtFramebuffer.kext has any relation with AirParrot (a program i used to send movies to my AppleTV). So i have deleted APExtFramebuffer.kext, and uninstall AirParrot, and then the Kext Utility v2.6.6 succeed in the instalation of the Apple_iSight.kext you gave me.
and after a restart the cam still doesn't work.


[doublepost=1477727836][/doublepost]
Did you uninstall VMWare properly? (As in, you removed ALL of its components, and didn't simply drag the application into the Trash)? Usually people not uninstalling it properly is the cause of the iSight camera continuing to not function properly.
I believe i did it right, and when i search "vmware" text in all of the archives content existing in my HD, there was only a "VMwareVMCI.kext" in the "MacHD\incompatible software" folder. (and now deleted).
if i uninstalled it in a wrong way, do you know if there is any program that could be usefull?
 
Last edited:
you're a genius! when will it be released?
Here is it! Updated it to show iMac10,1 because it's seems to be safe.

https://www.dropbox.com/sh/96tg06ys1pyem8v/AAAw0Gc4nlxK2OmXn4zFG-H6a?dl=0

I'm thinking about a small launchd script, that run only one time when the system boot up, and checks the com.apple.softwareupdated.plist about the patch. So it's not a daemon, it's only a script that checks and fix softwareupdated.plist. But i'am using my solution since beta 4, and the com.apple.softwareupdated.plist is not overwritten by any update.
 
Last edited:
(I am the guy with the -not detected- integrated iSight camera)

Thank you parrotgeek1 !!
I am trying to install "Apple_iSight.kext" with the app:
Kext Utility
v2.6.6
for mac OS 10.5-10.12

but i am having no success:
"The system extension "APExtFramebuffer.kext" is not compatible with this version of OS X and can’t be used."

is there any other way to install the "Apple_iSight.kext"?
----Edit---> APExtFramebuffer.kext has any relation with AirParrot (a program i used to send movies to my AppleTV). So i have deleted APExtFramebuffer.kext, and uninstall AirParrot, and then the Kext Utility v2.6.6 succeed in the instalation of the Apple_iSight.kext you gave me.
and after a restart the cam still doesn't work.


[doublepost=1477727836][/doublepost]
I believe i did it right, and when i search "vmware" text in all of the archives content existing in my HD, there was only a "VMwareVMCI.kext" in the "MacHD\incompatible software" folder. (and now deleted).
if i uninstalled it in a wrong way, do you know if there is any program that could be usefull?
Once you delete all VMWare-related kexts, you'll need to rebuild the kextcache. Just open Terminal and run "sudo kextcache -system-prelinked-kernel". Before you do this, ensure that SIP is disabled, or it will exclude modified kexts making your USB non-functional.
 
I also had to reset the catalog to get the I-Tunes update. It is really no big deal. I will leave it set on my default catalog until I hear of the next Sierra update. Then switch to grab it.
 
I also had to reset the catalog to get the I-Tunes update. It is really no big deal. I will leave it set on my default catalog until I hear of the next Sierra update. Then switch to grab it.
Next time just go to iTunes download on apple website and leave AUS untouched.
 
Thanks all, after I'm using the AUS I'm update to 10.12.1

Screen%20Shot%202016-10-30%20at%201.54.41%20AM.png
 
Here is it! Updated it to show iMac10,1 because it's seems to be safe.

https://www.dropbox.com/sh/96tg06ys1pyem8v/AAAw0Gc4nlxK2OmXn4zFG-H6a?dl=0

I'm thinking about a small launchd script, that run only one time when the system boot up, and checks the com.apple.softwareupdated.plist about the patch. So it's not a daemon, it's only a script that checks and fix softwareupdated.plist. But i'am using my solution since beta 4, and the com.apple.softwareupdated.plist is not overwritten by any update.
You should still do that to be safe
 
@dosdude1, How do I get your piece? Where is it at, what do I do? Please forgive me for my ignorance, Suffer the fools, lol. Now that I have time I‘d like to learn properly and become useful.

On an unrelated side note, my Mac HD had been giving me issues, and it just caused my 3Tb Seagate Ext Drive to lose it’s disk image, so I purchased a new internal HD (Seagate 2Tb) and a 5 TB Seagate to burn the data from the one that lost it’s image. I’m just about to purchase "Disk Warrior." Is there anything better? Why? All I know is the last time I had an ext HD go down (WD) It was 2 months out of warranty and they (WD’s disk recovery peeps) wanted $900. I w rote a scathing letter in Apple’s Support Community then did the same "Live" at WD, and within an hour I got a call from WD management telling me they’d gladly recover and replace my ext drive for free, thank you very much:). I don’t know much about Seagate, I assume they’re ok, Apple uses them along with WD also. Is Disk Warrior the best? IF not w ho and where? I’m trying to get this going tonight so it will copy over. I have a recovery disk partitioned in the existing HD with 10.11.5 or 10.11.6 on it. Do I just copy that to a USB drive or the new drive? I have to get all my housekeeping taken care of before Do anything with 10.12.1.
Thanks, You’re amazing, along with the other great talent here. I appreciate your expertise and wisdom, I hope I can repay you somehow.
Kev
 
Any luck with the iMac 8,1 audio fix? Or can someone show me how to properly install the El Cap kexts necessary to fix? I tried copying AppleHDA over using a kext utility app but all it did was make my iMac believe there was no audio device at all.

I also purchased a 2009 24" iMac audio board and found that the ribbon cable that connects it to the logic board is wider than that of my 2008's. So that was a no-go. :(
 
Any luck with the iMac 8,1 audio fix? Or can someone show me how to properly install the El Cap kexts necessary to fix? I tried copying AppleHDA over using a kext utility app but all it did was make my iMac believe there was no audio device at all.

I also purchased a 2009 24" iMac audio board and found that the ribbon cable that connects it to the logic board is wider than that of my 2008's. So that was a no-go. :(
I added the necessary kexts in the latest version of the post-install tool.
 
the mac sierra patcher won't unzip it says this operation is not permitted
I had the same problem. I think SIP has to be deactivated. But now having problem getting patched OS Sierra to install. Two problems- 1: installer does not bring up menu bar so utilities are unavailable. 2: installer fails.

Edit - Does Dosdude1's Sierra patcher work with 10.12.1?

Edit 2 - There is definitely something wrong. I have repeated the patch process on OS 10.12.1, made the USB installer, and it has consistently failed. I suspect the Sierra patcher does not work on OS 10.12.1. Anyone know where I can get a copy of OS 10.12?

Edit 3 - Confirmed: Patcher must be used to patch OS 10.12 and NOT OS 10.12.1. Recovery partition still not bootable.
 
Last edited:
Hello First time here, but a read most of the threads here and wanted to add my experience:

I have Three Mac Pro : 3,1 2Quad cores of 3,0Ghz with Capitan, a 4,1 flashed to 5,1 2Quad cores 2,8Ghz and 24Gigs of 1333 Ram and at Home a 4,1 Solo Quad core 2,66 16Gigas of 1066 Ram also flashed to 5,1.

First two have a Atheros Ar5bxb72 "3" antennas WiFi working great at 300Mbits/s . My Home MacPro has a BCM94321 that only works with Capitan at 130Mbits/s when booting from el Capitan HD . I Installed Sierra, downloaded from apple site, on a separated HD, When booting from Sierra my WiFi card it appears not present "no hardware," as if hardware was turned off/ or disabled :-(

GOOD News i got it back working copy the IO80211Family.kext from Capitan ( noted 5 Plugins ) and installed to Sierra (which had missing the AppleAirPortBrcm43224.kext plugin) installed with Kext Utility 2 ,a very handy tool !! rebooted and WiFi is back again !! (note a had do disable SIP from recovery via terminal)

Hope this Helps others :)

I'm a newbie here too and like Digital64, I possibly had some success getting BCM94321COEX2 working in Sierra. Great thread by the way :).

I have two Macbook Airs 2,1, I'm refurbishing. One is 1.6GHz and the other the 1.86MHz version I think. Anyway they both have BCM94321COEX2 WiFi/Bluetooth cards. The one in the 1.6 machine is an (0x14E4, 0x88) card and the other machine is an (0x14E4, 0x90) card.

When I installed your dosdude1's excellent Sierra patch in both machines, it went smoothly, but as he warns about the (0x14E4, 0x90) cards, there was no WiFi card detected in the 1.86 GHz machine. Interestingly however no adapter was detected in the (0x14E4, 0x8B) BCM4321 1.6 GHz machine either.

I skimmed around the internet and found this site. The instructions did not work for my two Sierra machines, until I found the BroadcomFix.kext file here, and installed it too using Kext Utility (version 2.5.7).

After that, I actually was able to get WiFi in Sierra using the BCM4321 for both machines, including the (0x14E4, 0x90) one, which if I understand correctly from dosdude1's page, shouldn't work. There was a problem though, initially after doing these two kext installs, Sierra crashed with a "kernel panic." The machines then both rebooted without crashing and at that point I had the WiFi service. I have attached the message from the 1.6 GHz machine, but I think the 1.86GHz one is the same, but I misplaced that file.

Essentially both errors seem to report a crash after "BSD process name corresponding to current thread: airportd Boot args: -no_compat_check." My question is, if the kernel is running a -no_compat_check when the airportd driver is loaded, can't I just stop it from making that check? What file do I need to edit to stop doing the -no_compat_check? After the crash the machines reboot without crashing again and seems to run the WiFi fine, detecting networks, accepting password, providing internet access etc. I haven't check bluetooth and I haven't rebooted maybe enough times to see if the kernel panic crash is chronic.

The OS X Yosemite WiFi Fix site's version of IO80211Family.kext contains the AppleAirPortBrcm43224.kext, that Digital64 reported is missing from Sierra's version of IO80211Family.kext. The BroadcomFix.kext is just a plist that adds <string>pci14e4,4321</string> to the list of WiFi adapters that should use the AppleAirPortBrcm43224.kext driver.

The only problem for me with this is that I looked at the BroadcomFix.kext plist file further up and it references AirPort_Brcm43xx driver not the AppleAirPortBrcm43224. Do you all think I really needed to add the BroadcomFix.kext or maybe installing the older version of IO80211Family.kext was enough, and it simply didn't work at first? I guess then if that's true, the BroadcomFix.kext only appeared to make WiFi work on my Macbook Airs and it was just coincidental. I'm attaching the BroadcomFix.kext also.

One more question, is it possible that the AppleAirPortBrcm43224.kext I installed with the Yosemite version of IO80211Family.kext is not as advanced as the El Capitan version? Could that cause by itself the kernel panic?
 

Attachments

  • BCM4321_Kernel_Panic_Error.pdf
    34.7 KB · Views: 363
  • BroadcomFix.kext.zip
    3.7 KB · Views: 172
Last edited:
  • Like
Reactions: slimmy18222
I have exact same problem ! No right click and no wireless...Wireless should be easy to fix. Come on guys, please fix the wireless BCM4321 !
This fixed the wireless BCM4321 for me in Sierra. Try:
  1. https://sites.google.com/site/osxyosemitewififix/.
  2. With Kext Utility (the 2.5.7 version worked for me), install BroadcomFix.kext from http://www.insanelymac.com/forum/topic/263533-broadcom-bcm4321-lion/#645126.
  3. Reboot. You may get a kernel panic, but after reboot it worked for me. Don't know how stable it is after that. So far only one or two crashes, over a few hours.
 
Last edited:
  • Like
Reactions: slimmy18222
I just updated my MacBookPro5,1 to macOS 10.12.1 using AUSEnabler (Thanks dosdude1!)
The problem is that it installed build 16B2555. They updated 10.12.1 to build 12B2657 and you need that or later to enable the TouchBar simulator in Xcode 8.1.
Any plans on how we could update to that new build?
 
An alternate method I have used to successfully update Sierra to 10.12.1 on my 2008 Mac Pro is to simply boot into another instance of the operating system (I use Mavericks 10.9.5) and use a virtual machine running Sierra to run the 10.12.1 update package obtained from Apple’s download website. I map the physical disk running the instance of Sierra I want to update into the virtual machine and point the installer to that volume. Once completed, modify/remove the PlatformSupport.plist file as usual, then reboot into the updated Sierra volume and you are good to go.

The nice thing about this approach is that there are no system modifications involved, it does not require disabling SIP, and it uses only Apple-sanctioned update procedures. Future software updates should work the same using combo update packages.

The Mavericks 10.9.5 volume also serves as my recovery partition, so I just deleted the non-bootable 10.12 recovery partition and returned the used space back to the Sierra partition using the ‘diskutil mergePartitions’ command.

Some details…

I’m using a recent version of VMware Fusion (8.5.0) to host the Sierra virtual machine. In the Fusion application package is a utility called vmware-rawdiskCreator that generates a .vmdk file pointing to the physical disk running the copy of Sierra targeted for the update. You have to manually edit the virtual machine .vmx configuration file to add references to this special .vmdk file. Once running, the physical disk is mapped into and is available as another volume in the virtual machine.

Also, this is just a variation of the same technique I used to bootstrap the installation of Sierra on my Mac Pro. By using a virtual machine, I was able to get a copy of Sierra installed on a physical drive that I then used to boot on my Mac Pro, eliminating the need to have access to another Sierra compatible Mac for this initial step.
 
I just updated my MacBookPro5,1 to macOS 10.12.1 using AUSEnabler (Thanks dosdude1!)
The problem is that it installed build 16B2555. They updated 10.12.1 to build 12B2657 and you need that or later to enable the TouchBar simulator in Xcode 8.1.
Any plans on how we could update to that new build?
AUSEnabler was created and is hosted by @foxlet, so he deserves full credit for that. As for the update being of a different built number, I'm not sure... I didn't realize there were 2 different versions of it.
 
I just updated my MacBookPro5,1 to macOS 10.12.1 using AUSEnabler (Thanks dosdude1!)
The problem is that it installed build 16B2555. They updated 10.12.1 to build 12B2657 and you need that or later to enable the TouchBar simulator in Xcode 8.1.
Any plans on how we could update to that new build?

Apple actually notes that to get that build, you have to manually download it.

https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html

"Note: To develop apps that use Touch Bar, you must run Xcode 8.1 on macOS 10.12.1 build 12B2657 or later. If you want to develop for Touch Bar, check your macOS build number using the system's About This Mac dialog. If you do not have macOS 12B2657 or later, install the macOS Sierra 10.12.1 Update from https://support.apple.com/kb/dl1897."
 
  • Like
Reactions: Stratus Fear
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.