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.
Updated my 2014 MBP (running 10.12.2) without issue after 10.12.3 popped up as a 'software update' in the app store. My flashed MP 4.1 however doesn't show an update as available despite also running 10.12.2.

I did nothing to the MP other than flash to 5.1 before I installed Sierra and so am dismayed to see no update showing for this update. Can I just download the update and install it or is it not that simple? Any advice appreciated.
 
For those who want an UI to switch to AUS in order to get further Sierra updates, now exists AUSEnabler

v2lvQZg.png

After selecting a catalog, just open the App Store and update away!
*Note: The app requires a working internet connection to fetch the latest catalog URLs.

http://swdist.furcode.co/bin/AUSEnabler.zip

Hello guys. I'm trying to apply this "patch" to an Xserve 3,1. Installation went fine but I have dubt about this enabler because, after applied it, the OS does not feel any updates.
Any tip for me?
THANKS!
 
Hello guys. I'm trying to apply this "patch" to an Xserve 3,1. Installation went fine but I have dubt about this enabler because, after applied it, the OS does not feel any updates.
Any tip for me?
THANKS!

This is not necessary anymore. Use the patch from czo. And switch back to the normal update catalogue.
 
[doublepost=1485353801][/doublepost]
Hello guys. I'm trying to apply this "patch" to an Xserve 3,1. Installation went fine but I have dubt about this enabler because, after applied it, the OS does not feel any updates.
Any tip for me?
THANKS!
For use developer betas you must run:
$sudo softwareupdate --set-catalog https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz

And switch back to usual catalog:
$sudo softwareupdate --clear-catalog

Anybody can use "Night Shift" with 10.12.4 beta 1 on unsupported Macs?
 
Last edited:
[doublepost=1485353801][/doublepost]
For use developer betas you must run:
$sudo softwareupdate --set-catalog https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz

And switch back to usual catalog:
$sudo softwareupdate --clear-catalog

Anybody can use "Night Shift" with 10.12.4 beta 1 on unsupported Macs?
I found a beta access disk image online for 10.12.4 and am installing it now. So you are saying, the terminal commands would allow the latest beta to be pushed out to me without having to use the disk image I downloaded?
Ill let you know about Night Shift as soon as the install finishes
 
This is not necessary anymore. Use the patch from czo. And switch back to the normal update catalogue.
Seras ciao.
What I see is a strange behaviour: Application App Store opens the first time. He shows an update ( iTunes ), it tries to download it BUT at the end it fails.
From that moment AppStore app does not start anymore

Tips?
 
[doublepost=1485353801][/doublepost]
For use developer betas you must run:
$sudo softwareupdate --set-catalog https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz

And switch back to usual catalog:
$sudo softwareupdate --clear-catalog

Anybody can use "Night Shift" with 10.12.4 beta 1 on unsupported Macs?
Well, at least on 7,1 iMac, I see no reference to Night Shift. Im betting its a Retina display thing. Im sure there is probably a way to enable it tho
Screen Shot 2017-01-25 at 9.31.38 AM.png Screen Shot 2017-01-25 at 9.32.57 AM.png
 
I found a beta access disk image online for 10.12.4 and am installing it now. So you are saying, the terminal commands would allow the latest beta to be pushed out to me without having to use the disk image I downloaded?
Ill let you know about Night Shift as soon as the install finishes
Yes. You will get each new beta update after releasing.
 
You don't need any utility. In terminal:

Code:
sudo /usr/sbin/softwareupdate --set-catalog https://swscan.apple.com/content/catalogs/others/index-10.12seed-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

After that Dosdudes script for Czos patch.

Restart and terminal:
Code:
softwareupdate -l

Et voila Beta is there.
 
So Night Shift shows up in Display preferences for my old 23" cinema display on my hackintosh but not the 20" display on my 7,1 iMac. So its not related to retina displays. hmmm...... more digging
 
Folks, just to let everyone know, for the time being, I have abandoned using macOS Sierra on my early 2009 iMac, and I have returned to using the last build of El Capitan.

I won't take up all of your time with the details, but suffice it to say that I had a very nasty experience with the 10.12.1 update this morning which resulted in my keyboard, my Magic Mouse, and even my wired mouse becoming totally inoperable, so that I could not log into my active system.

I tried everything multiple times: resetting the SMC, zapping the PRAM, booting into Recovery Mode, and trying to boot into Safe Mode.

Ultimately, I had to install Mountain Lion on another external partition, and then from there reformat my internal hard drive, and do a clean install of El Capitan.

I have been at this all day working on getting everything back in order, and I am still not done yet, and I am tired.

This old iMac -- almost eight years old -- doesn't have too much time left on it, so I will be sticking with El Capitan until I can afford to purchase a new machine. Everything I have been through with Sierra on this machine just isn't worth the hassle for features which I really don't need, and which I even wouldn't use.

Thanks again to those of you who have worked so hard, and invested so much of your time, to help us get Sierra installed on our machines.

The question is, given the general age of our machines, and the problems and challenges we have had to endure, in order to get it working on our machines, is a Sierra upgrade really worth it? Looking at Apple's list of selling points for Sierra, I have come to the conclusion that at least in my case, the Sierra upgrade has not been worth it. Thus I have abandoned it, and I in fact have a peace about it.

Not only that, but because I performed a clean install of El Capitan, and also stopped using a number of apps and system enhancements, I have noticed a renewed snappiness in my machine, particularly in how fast apps load now. So again, I am pleased.

My experience with a MBP 5,2 (mid-2009) has been similar: Using @dosdude1 's tool, I managed to brick the stock HD, getting prohibited symbol and gray screen of death in all start modes. Bought new 1TB SSD HD and did clean install, following all steps (5&6). That worked, and I enjoyed Sierra with no problems...until I tried to update.

Despite running the macOS post install for my machine, and @foxlet 's app, 10.12.3 effectively locked me out of my computer, disabling trackpad and keyboard. Same scenario as last time: no start-up options available except target mode and option for boot screen. From latter, I booted using patcher and tried again, but still stuck at login. Keypad and mouse work in boot area but once that Sierra background shows up, I'm toast. Keys locked even in single user mode so can't isolate problem there. Ran repair in disk utility from boot mode and going to try again; worst case scenario, I guess I go back to El Cap too.

If I do not recover work from this last week, I think I can disagree with @RumorzGuy that this will not have been worth it even with some increased performance from clean slate. Total time suck. Still, thanks to DosDude for being so responsive by email
 
Last edited:
My experience with a MBP 5,2 (mid-2009) has been similar: Using @dosdude1 's tool, I managed to brick the stock HD, getting prohibited symbol and gray screen of death in all start modes. Bought new 1TB SSD HD and did clean install, flooring all steps (5&6). That worked, and I enjoyed Sierra with no problems...until I tried to update.

Despite running the macOS post install for my machine, and @foxlet 's app, 10.12.3 effectively locked me out of my computer, disabling trackpad and keyboard. Same scenario as last time: no start-up options available except target mode and option for boot screen. From latter, I booted using patcher and tried again, but still stuck at login. Keypad and mouse work in boot area but once that Sierra background shows up, I'm toast. Keys locked even in single user mode so can't isolate problem there. Ran repair in disk utility from boot mode and going to try again; worst case scenario, I guess I go back to El Cap too.

If I do not recover work from this last week, I think I can disagree with @RumorzGuy that this will not have been worth it even with some increased performance from clean slate. Total time suck. Still, thanks to DosDude for being so responsive by email


No! Anyone can lost thier USB if and only if SIP is re-enabled (why anyone make this?). SIP can be re-enable from single user mode or from recovery via csrutil command, or if PRAM is zapped/cleared.
 
Well, I have no a single issue with running the latest Sierra on my MB mid-2009. First update was done with AUSEnabler and the last update with @Czo script. No issues at all.
I even installed Win 7 using BootCamp
 
No! Anyone can lost thier USB if and only if SIP is re-enabled (why anyone make this?). SIP can be re-enable from single user mode or from recovery via csrutil command, or if PRAM is zapped/cleared.

Ahh, that makes sense, @Czo; yeah USB mice don't work either but this is a MBP so unresponsive trackpad & keyboard are the issue.

Buy yes, I think you're right—different symptom, same cause: SIP was re-enabled, though I'm not sure how. I only entered single user mode and cleared PRAM *after* I encountered problems. I know SIP was re-enabled tho because I was getting a message at startup (in Applications note, from @foxlet 's pkg?) saying so and advising that I disable/return to rootless.

At all events, I went back to @dosdude1 's square one, used patch to (re)install Sierra, disabled SIP with terminal option and rebooted. Gray screen, but reboot from post-patch option worked. @foxlet 's script still enabled, but sounds like people here are recommending switch back from AUS and download @Czo 's? Where?
 
Last edited:
Ok, maybe images will help?

1: Download OS 10.12.2 from Apple here.
2: Open the downloaded .dmg (I downloaded macosupd10.12.2.dmg). I moved mine to the Desktop first.
3: Unpack .pkg in terminal (pkgutil --expand /source /destination). In this case, I unpacked the file from my Desktop to a folder called "Modified Installer" on my Desktop. NOTE: I have edited out my username so your terminal window will have your user name where there are large blank spaces in the attached screen shot.
View attachment 678280
4: Look up your Mac model's "boardID" here. Copy the boardID.
5: Inside the "Modified Installer" folder, open the "Distribution" file with text edit. Add the boardID inside the bracket after "var boardIds = ". Be sure to use straight ' and not ’.
View attachment 678272
6: In the "Distribution" file, scroll down to "var nonSupportedModels =" and remove your Mac's model from the list.
View attachment 678273
7: Save the modified "Distribution" file.
8: Flatten the modified pkg in terminal (pkgutil --flatten /modified_source /destination). In this case, I flattened the "Modified Installer" folder on my Desktop to a .pkg named "Install 10.12.2.pkg" on my Desktop. This step may take a minute or two so wait until complete (the command prompt will return and the red close window button will not have a black dot).
View attachment 678281
9: Double click your modified .pkg and run the installer normally. If you did not follow directions, you will get error because "Distribution" file checks your machine as not supported. Go back to step 4 and try again.
View attachment 678276
[doublepost=1481869540][/doublepost]
The unmodified installer will not run on unsupported machines. But yeah, it is a good place to download updates if foxlet's AUS server isn't doing the job for you. If you have multiple machines you could consider making your own patched updater .pkg as I described above.

i'm installed macos sierra 10.12.3 using AUSEnabler2 at http://swdist.furcode.co/ ; after that upgrade, i had to use an dosdude1 usb disk with 10.12 and doing macOS post install and including 'force cache rebuild' because no mouse and keyboard run
 
  • Like
Reactions: j2048b
i'm installed macos sierra 10.12.3 using AUSEnabler2 at http://swdist.furcode.co/ ; after that upgrade, i had to use an dosdude1 usb disk with 10.12 and doing macOS post install and including 'force cache rebuild' because no mouse and keyboard run

This was my situation too with the 10.12.3 update - trackpad didn't work. Rebooted to my patched USb installation and redid the post install patch and then forced a cache rebuild. Once it rebooted everything was fine again.
 
i'm installed macos sierra 10.12.3 using AUSEnabler. Perfect!!

But i can`t updated iTunes 12.5.5. In iTunes iTunes/Update ---> Install.

Go to Appstore but don´t work!!
 
i'm installed macos sierra 10.12.3 using AUSEnabler. Perfect!!

But i can`t updated iTunes 12.5.5. In iTunes iTunes/Update ---> Install.

Go to Appstore but don´t work!!


after using ausenabler2, rerun this and select to reset catalogs. this catalog change is only to allow sierra package upgrades
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.