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 used AUS to grab .2 and its smooth as glass on my MB 5,2. I've played with it all afternoon. Why can't this machine just be supported? I do have a SSD and 8GB ram but still. This thing aint dead yet....
I agree. It is REALLY annoying that Apple intentionally blocked hardware that can run OS 10.12 "Sierra". Literally all that is missing is a few .kext files and including the boardID in the distribution file inside the OS.pkg. I have no issue with pulling machines that simply could not have run the OS but Apple actively blocked capable machines.

I wish someone with an Apple Dev license would volunteer to get the unsupported .kexts signed by Apple. It would solve some of the problems.
 
actually Sierra ONLY allow Windows 10 installations on Bootcamp. I also have a mid 2009 pro and it shows windows 10 on bootcamp assistant, so you may give it a try, I think it will work fine.

Thanks evertjr. To clarify, have you installed the patch to get Sierra going on your Mac (2009)?
 
Mac Pro 2008 updated successfully to 10.12.2.
I run AUSEnabler again and then update was downloadable via AppStore.
 
Dosdude1 i have a question. I have successfully updated Sierra to version 10.12.2 but i also want to create a bootable USB with your latest patcher on a macOS Sierra 10.12.2 installer. Does it work? Thanks in advance.
 
Last edited:
Mac Pro 2008 updated successfully to 10.12.2.
I run AUSEnabler again and then update was downloadable via AppStore.
It dosen't work for me.... I can't get this AUSenabler to work... Can someone pls help me? I'm still running the macOS 10.12 beta (16A304a) on my Aluminium MacBook 13-inch, Late 2008!!!!
 
It dosen't work for me.... I can't get this AUSenabler to work... Can someone pls help me? I'm still running the macOS 10.12 beta (16A304a) on my Aluminium MacBook 13-inch, Late 2008!!!!
You can't update to a final version from a beta with the App Store. You need to re-install using a final installer.
[doublepost=1481729273][/doublepost]
Dosdude1 i have a question. I have successfully updated Sierra to version 10.12.2 but i also want to create a bootable USB with your latest patcher on a macOS Sierra 10.12.2 installer. Does it work? Thanks in advance.
I'm not sure yet, due to the limited Internet connection I'm on right now, I haven't had time to download a copy and test it. Give it a try yourself, and just let me know whether or not it works.
 
  • Like
Reactions: pleiadian
You can't update to a final version from a beta with the App Store. You need to re-install using a final installer.
[doublepost=1481729273][/doublepost]
I'm not sure yet, due to the limited Internet connection I'm on right now, I haven't had time to download a copy and test it. Give it a try yourself, and just let me know whether or not it works.
Can I install it to my current version, or I have to make a clean install?
 
Can I install it to my current version, or I have to make a clean install?
You should be able to just install it over top your current install. Just select the volume containing it during the install without erasing it in Disk Utility.
 
Thanks evertjr. To clarify, have you installed the patch to get Sierra going on your Mac (2009)?

Yes, I installed Sierra using dosdude1 tool and have been using since 10.12.1 without any issues, actually it runs quite better than el capitan. Just make sure you disable SIP before anything.
 
I updated by doing:
1: download the standalone OS 10.12.2 update from Apple.
2: unpack .pkg in terminal (pkgutil --expand /source /destination
3: edited distribution file in text edit. Added my boardID (found list here) to supported list and removed my machine model from unsupported list. (Although it is probably easier just to change file to always return true).
4: flattened modified pkg in terminal (pkgutil --flatten /modified_source /destination)
5: double click modified .pkg and run normally.
 
Hi,

I install 10.12 on a macbook5,1 with the tool and it worked fine. I did the 10.12.1 update with AusEnabler and nothing else and it was perfect.
Yesterday I updated the same way and 10.12.2 worked until I reboot it. Then black screen. I try afterward to patch it with the tool but it told me there were no valid version of Sierra. I forced it but I dont know if it has been patched or not. Anyway still a black screen with the mouse arrow (moving with the pad). The only solution for me was to reinstall 10.12 and not doing any update...
Any solution?
Maybe the SIP activation on the second reboot. How to avoid this activation?
 
Last edited:
Hi,

I install 10.12 on a macbook5,1 with the tool and it worked fine. I did the 10.12.1 update with AusEnabler and nothing else and it was perfect.
Yesterday I updated the same way and 10.12.2 worked until I reboot it. Then black screen. I try afterward to patch it with the tool but it told me there were no valid version of Sierra. I forced it but I dont know if it has been patched or not. Anyway still a black screen with the mouse arrow (moving with the pad). The only solution for me was to reinstall 10.12 and not doing any update...
Any solution?
Maybe the SIP activation on the second reboot. How to avoid this activation?
Did you try to boot from the patched USB installer? If you can, open terminal and check SIP status (csrutil status). If SIP is enabled type 'csrutil disable'. Then run the post-install utility.
 
Did you try to boot from the patched USB installer? If you can, open terminal and check SIP status (csrutil status). If SIP is enabled type 'csrutil disable'. Then run the post-install utility.

I started on the USB Installer checking the disable status and even forced it disable. I tried to apply the patch but it said there was no recognised version of Sierra. So always a black screen.
I wonder if the disable status of SIP is the one of the USB drive and not the one of the HDD.
How can I access the HDD via the terminal and then check the SIP status on that drive?
 
I started on the USB Installer checking the disable status and even forced it disable. I tried to apply the patch but it said there was no recognised version of Sierra. So always a black screen.
I wonder if the disable status of SIP is the one of the USB drive and not the one of the HDD.
How can I access the HDD via the terminal and then check the SIP status on that drive?
No, SIP settings are stored in nvram and independent of what drive is used. The Sierra patch is applied to a Sierra installer before installing. If you used dosdude1's patcher and instructions, this will create a bootable USB installer. After installing Sierra with the patched USB installer, you have to boot to the USB installer again but from the drop-down utilities menu, select "post-install". This adds the kext files that your computer will need to operate.
 
wooooooow cool.now my WIFI on my iMac 8.1 works.THX
[doublepost=1481223612][/doublepost]

yes, but after the computer restart you do a new WIFI Connection and it works.

I have the same iMac, did you have any problem after that? Kernel panics? Thank you!
 
No, SIP settings are stored in nvram and independent of what drive is used. The Sierra patch is applied to a Sierra installer before installing. If you used dosdude1's patcher and instructions, this will create a bootable USB installer. After installing Sierra with the patched USB installer, you have to boot to the USB installer again but from the drop-down utilities menu, select "post-install". This adds the kext files that your computer will need to operate.

When I try to apply the patch with the USB drive, I've been told that "the volume does not appear to contain a valid copy of macOs Sierra"
 
I updated by doing:
1: download the standalone OS 10.12.2 update from Apple.
2: unpack .pkg in terminal (pkgutil --expand /source /destination
3: edited distribution file in text edit. Added my boardID (found list here) to supported list and removed my machine model from unsupported list. (Although it is probably easier just to change file to always return true).
4: flattened modified pkg in terminal (pkgutil --flatten /modified_source /destination)
5: double click modified .pkg and run normally.

Make all right, but when I double click modified .pkg I cann`t install in any HDD.

Sorry my English is very bad.
 
When I try to apply the patch with the USB drive, I've been told that "the volume does not appear to contain a valid copy of macOs Sierra"

Have you tried to patch a copy of a "macOS Sierra 10.12.2 installer" with the latest patch tool from dosdude1? If so then it means that using the latest patch on a macOS Sierra 10.12.2 installer doesn't work. Probably you will receive the message "not a valid copy". Too bad because if you even upgraded your system to version 10.12.2, from 10.12.1, then you're not be able to do re-patch using Post-Installer and you'll get the message "wrong version". To me upgraded to version 10.12.2 works perfectly but now i am scared if something bad happens. The only thing we can do, on that point, is to wait for an updated patch tool from dosdude1
 
Last edited:
I have a MacBook 5,1 and ausenbler wasn't showing updates. I did was sedulous said and expanded the standalone pkg from apple and added my board id and removed macbook5.1 from nonsupported on the distribution file. Got a java santax error turns out ' and ’ are not the same. Tried again have no issuses. Thanks to the community for keeping this MacBook secure and up to date when apple drops the ball
 
When I try to apply the patch with the USB drive, I've been told that "the volume does not appear to contain a valid copy of macOs Sierra"
Follow dosdude1's instructions. The patch is not "applied to the USB". Dosdude1's Sierra patcher reads from an unpatched "Install Sierra.app" and creates the patched USB media you use to boot and install Sierra.
 
I agree. It is REALLY annoying that Apple intentionally blocked hardware that can run OS 10.12 "Sierra". Literally all that is missing is a few .kext files and including the boardID in the distribution file inside the OS.pkg. I have no issue with pulling machines that simply could not have run the OS but Apple actively blocked capable machines.

I wish someone with an Apple Dev license would volunteer to get the unsupported .kexts signed by Apple. It would solve some of the problems.

I have never been on cutting edge real Macs. I built a really nice SL hackinthosh a few years back and even went to Lion with it but I just kept using my PPC macs to enjoy real Macs and the most recent Mac I have is my MB 5,2 and it does every thing I need from a Mac. Its funny how my old MB 2,1 is still holding strong with a SSD and 4GB ram on Windows 10 Pro. I have always loved these white books...
 
I have a MacBook 5,1 and ausenbler wasn't showing updates. I did was sedulous said and expanded the standalone pkg from apple and added my board id and removed macbook5.1 from nonsupported on the distribution file. Got a java santax error turns out ' and ’ are not the same. Tried again have no issuses. Thanks to the community for keeping this MacBook secure and up to date when apple drops the ball

I was unable to update my MacBook5,1 to Sierra 10.12.2 since the App Store wasn't showing any updates to my existing 10.12.1. I used AUSEnabler to 1) reset catalogs, 2) switch the seed catalog. I then observed that I could then see an update to 10.12.3 Alpha. I used AUSEnabler to then switch back to the production branch catalog. Only then was I able to finally see the 10.2.2 updater in the App Store.

Your actual mileage may vary. ;-)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.