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.
Before doing so, check that your iTunes isn't already updated to current version. I bumped into this previously and started jumping through hoops then realized iTunes was updated and the App Store just was having a brain fart.
[doublepost=1477900399][/doublepost]
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.
Interesting but would this work if kext modifications are required for hardware compatibility? In other words, install Sierra on a compatible machine, swap out the drive to an unsupported machine. Isn't your method effectively the same idea? It would be cool if it would work in all cases.
 
Last edited:
Before doing so, check that your iTunes isn't already updated to current version. I bumped into this previously and started jumping through hoops then realized iTunes was updated and the App Store just was having a brain fart.
Came here to post about this. My iTunes hadn't been updated to the new version and wasn't showing up in the App Store either. Eventually downloaded it through the website. Have the AUSEnabler installed to get the updates. Any reason why iTunes wasn't showing up in the App Store?
 
Came here to post about this. My iTunes hadn't been updated to the new version and wasn't showing up in the App Store either. Eventually downloaded it through the website. Have the AUSEnabler installed to get the updates. Any reason why iTunes wasn't showing up in the App Store?
My guess is that iTunes was actually already updated. Check iTunes version to see if that is up to date.
 
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.


hello again, i did that.


1) ensure SIP is disabled (it was).

2) type in terminal: sudo kextcache -system-prelinked-kernel

3) obtain this following:
Last login: Mon Oct 31 18:54:20 on console
Limpiacristales-4:~ Alf$ sudo kextcache -system-prelinked-kernel
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
kext file:///System/Library/Extensions/ssuddrv.kext/Contents/PlugIns/ssudmtp.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RIMBBUSB.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBEHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOUSBHostFamily.kext
kext file:///System/Library/Extensions/ElmediaPlayer.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
KernelCache ID: A58E41C670957ECB9ECA30812CCB83CD
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
Limpiacristales-4:~ Alf$

4) isight is still not working :.(

5) cry.

any ideas?
 
I did and it wasn't updated. I even open and closed out of it to make sure it wasn't and still wasn't the latest version.

Same here.. I check version and it is not latest version, when iTunes starts it says "newer version available".
I updated iTunes manually.
 
I can confirm iTunes update not showing here too on App Store. I don't know if its AUSEnabler related or Apple server issue.
 
iTunes says that there is newer version available -> Ok -> App Store open -> no updates?
Going back a ways in this thread I found the solution as suggested by foxlet

Reset AUS catalog to the default Apple server using terminal. Type:
sudo softwareupdate --clear-catalog

Then open App Store and check update. You can always rerun AUSenabler again when needed.
 
Last edited:
  • Like
Reactions: Istivi Jobis
Interesting but would this work if kext modifications are required for hardware compatibility? In other words, install Sierra on a compatible machine, swap out the drive to an unsupported machine. Isn't your method effectively the same idea? It would be cool if it would work in all cases.
No, this workaround is viable on my 2008 Mac Pro since it is (almost) fully compatible with Sierra. The lone exception appears to be dropped support for the original Wi-Fi hardware, but even that can be circumvented by swapping in a combination Wi-Fi/Bluetooth BCM94360CD card.

This upgrade approach is just convenient since it doesn’t require another Sierra compatible Mac, physically removing drives, or moving machines around (in case I wanted to boot my Mac Pro into target disk mode and apply the update that way). Plus no low-level OS modifications and just one extra reboot.

If you have a 2008 Mac Pro and virtualization software that allows you to map a physical drive into a virtual machine, it is a fairly painless upgrade path.
 
Going back a ways in this thread I found the solution as suggested by foxlet

Reset AUS catalog to the default Apple server using terminal. Type:
sudo softwareupdate --clear-catalog

Then open App Store and check update. You can always rerun AUSenabler again when needed.

Thanks! I try that next time when Apple releases updates.
I think you can do this also via UI?

2016-11-01_07-56-48.jpg
 
hello again, i did that.


1) ensure SIP is disabled (it was).

2) type in terminal: sudo kextcache -system-prelinked-kernel

3) obtain this following:
Last login: Mon Oct 31 18:54:20 on console
Limpiacristales-4:~ Alf$ sudo kextcache -system-prelinked-kernel
Password:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LegacyUSBInjector.kext
kext file:///System/Library/Extensions/ssuddrv.kext/Contents/PlugIns/ssudmtp.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RIMBBUSB.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBEHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOUSBHostFamily.kext
kext file:///System/Library/Extensions/ElmediaPlayer.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
KernelCache ID: A58E41C670957ECB9ECA30812CCB83CD
symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>
Limpiacristales-4:~ Alf$

4) isight is still not working :.(

5) cry.

any ideas?

@dosdude1 this is the same thing I told you a few posts above, in your script, you can't just make /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache, you have to do the prelinkedkernel path and symlink it
[doublepost=1477986041][/doublepost]
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.
holy crap you did it

cc @dosdude1
 
Hi all, I managed to install Sierra on my early 2009 iMac (24", the model with no issues). Running AUSenabler, I installed manually iTunes update while Sierra 10.12.1 update installed from the app store. I shut down yesterday, today the system don't start, with deny icon on the screen, i.e. no valid boot system folder. My machine is old and maybe the hard disk is corrupted, but I ask if the 10.12.1 update may have damaged something. Now I'm reinstalling but will not do any update to test the system for some days.
 
Hello everybody! Neither iTunes latest version nor MacOS 10.12.2 (released yesterday) show up in the App Store using AUSEnabler. Does anyone know why?
 
Hi all, I managed to install Sierra on my early 2009 iMac (24", the model with no issues). Running AUSenabler, I installed manually iTunes update while Sierra 10.12.1 update installed from the app store. I shut down yesterday, today the system don't start, with deny icon on the screen, i.e. no valid boot system folder. My machine is old and maybe the hard disk is corrupted, but I ask if the 10.12.1 update may have damaged something. Now I'm reinstalling but will not do any update to test the system for some days.

sorry if I answer in Italian.....

Ciao....
Fabietto79....

A quanto pare è normale che succeda, lo notato aggiornando sia la versione "Developer " che la versione " Normale " .

L'aggiornamento va a ripristinare i file " PrelinkedKernel & PlatformSupport.plist " inoltre mi sono ritrovato con " SIP " abilitato...... Risolto in codesto modo :

Riavvia con la " Patch " di dosdude1, disabilita " SiP " via terminale, riavvia con la "Patch" il sistema dopo di che vai a sostituire i due file, io utilizzo i file di "EL Capitan"......

Si riavvia normalmente........

nice day.......
 
sorry if I answer in Italian.....

Ciao....
Fabietto79....

A quanto pare è normale che succeda, lo notato aggiornando sia la versione "Developer " che la versione " Normale " .

L'aggiornamento va a ripristinare i file " PrelinkedKernel & PlatformSupport.plist " inoltre mi sono ritrovato con " SIP " abilitato...... Risolto in codesto modo :

Riavvia con la " Patch " di dosdude1, disabilita " SiP " via terminale, riavvia con la "Patch" il sistema dopo di che vai a sostituire i due file, io utilizzo i file di "EL Capitan"......

Si riavvia normalmente........

nice day.......
Grazie x la risposta in italiano! Capito, comunque ho reinstallato e lo lascio così senza aggiornare per il momento, devo verificare se il mio disco mi sta abbandonando o no. Buona giornata e grazie ancora
 
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.

Wait, so this would work with a Mac Mini 2009 with stock BCM4321 wifi card?
 
@dosdude1 this is the same thing I told you a few posts above, in your script, you can't just make /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache, you have to do the prelinkedkernel path and symlink it
[doublepost=1477986041][/doublepost]
holy crap you did it

cc @dosdude1
I need to do some testing with this method, because it seems to be relatively unstable, causing random kernel panics. I'll see if I can manage to get it working reliably, though, and if so, I'll add it to my patch tool. And my script of my post-install tool does rebuild prelinkedkernel before rebooting.
 
@dosdude1, is there any way to apply the recovery partition patch after turning FileVault back on again?

background of my question:

I ran your patcher after an upgrade and install but forgot to apply the recovery partition patch (since it was not checked by default). Then I turned FileVault back on, so I can no longer see the partitions - and patch them - when booting from the usb stick with the modified installer on it. I tried the following: booting into my regular system, mount Recovery HD using terminal, run your macOS Post Install.app and make it patch the mounted Recovery HD. While the patch states that the process was completed successfully, I still cannot boot from it (crossed out circle when booting with [cmd]+[r]).

However, I want to create a functioning recovery partition with your macOS Post Install.app on it, so that I can - should that ever become necessary after an update - repatch my regular system partition. How do I do that without going through the tedious process of turning FileVault off and back on again (which takes forever on my MacBook Pro 5,5 and generates an entirely new recovery key, which I'd have to redistribute to safe locations - again)?
 
@dosdude1, is there any way to apply the recovery partition patch after turning FileVault back on again?

background of my question:

I ran your patcher after an upgrade and install but forgot to apply the recovery partition patch (since it was not checked by default). Then I turned FileVault back on, so I can no longer see the partitions - and patch them - when booting from the usb stick with the modified installer on it. I tried the following: booting into my regular system, mount Recovery HD using terminal, run your macOS Post Install.app and make it patch the mounted Recovery HD. While the patch states that the process was completed successfully, I still cannot boot from it (crossed out circle when booting with [cmd]+[r]).

However, I want to create a functioning recovery partition with your macOS Post Install.app on it, so that I can - should that ever become necessary after an update - repatch my regular system partition. How do I do that without going through the tedious process of turning FileVault off and back on again (which takes forever on my MacBook Pro 5,5 and generates an entirely new recovery key, which I'd have to redistribute to safe locations - again)?
Just follow the directions here to unlock your volume from Terminal, and then run the post-install patch. http://apple.stackexchange.com/ques...mount-an-encrypted-disk-from-the-command-line
 
Hello everybody! Neither iTunes latest version nor MacOS 10.12.2 (released yesterday) show up in the App Store using AUSEnabler. Does anyone know why?

iTunes update only showed up when reseted to default Apple catalog. About the beta update, are you using Seed branch or Production?
 
@dosdude1 the update showed up on my mid 2009 MacBook Pro today. I did the update and it rebooted a couple of times to apply and now it takes a little more time to boot up, when it gets to the login screen my touchpad or keyboard dont work anymore. Has anyone else got this issue and acfix?
 
@dosdude1 the update showed up on my mid 2009 MacBook Pro today. I did the update and it rebooted a couple of times to apply and now it takes a little more time to boot up, when it gets to the login screen my touchpad or keyboard dont work anymore. Has anyone else got this issue and acfix?
Boot to USB installer and run post-install found in the "Utilities" section of the menu bar.
[doublepost=1478048184][/doublepost]
Hello everybody! Neither iTunes latest version nor MacOS 10.12.2 (released yesterday) show up in the App Store using AUSEnabler. Does anyone know why?
macOS 10.12.2 isn't yet available. Try resetting Catalog option using AUSEnabler. Then run MAS to check for iTunes update. Worked for me.
 
Last edited:
@dosdude1 the update showed up on my mid 2009 MacBook Pro today. I did the update and it rebooted a couple of times to apply and now it takes a little more time to boot up, when it gets to the login screen my touchpad or keyboard dont work anymore. Has anyone else got this issue and acfix?
You need to re-run my post-install tool and ensure that SIP is disabled.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.