I had success last night updating from OS 10.12.3 to 10.12.4 on a Mid 2009 Macbook (5,2), using the App Store app's "Update" option.

Though as others report here, after installing the 10.12.4 update, this Macbook model won't respond to the brightness up/down buttons on the keyboard. I installed the "Brightness" menu bar utility by bergdesign (http://bergdesign.com/brightness/), and that works fine, but @dosdude1 , is there a plan to incorporate a patch into MacOS Sierra Patcher to bring back keyboard brightness button functionality?

I'm trying to install Sierra on my 2009 Mac Mini. I upgraded via USB, it said complete. When I restarted I got the no symbol in both recovery and normal boot. When trying to boot from USB again, the loading bar freezes every time. I can't get back into it to try to fix anything (like disable SIP or try a clean install). I made a bootable disk of El Capitan just in case this went awry but that freezes as well! Sometimes I get a no symbol, sometimes the progress bar stops.

What can I do at this point? I'm totally locked out of everything.

[edit] Posted too soon but I was freaking out a bit. I let the machine just sit unplugged for an hour. When I fired it up the screen flashed a few times but I was inexplicably able to load the Sierra disk again. After disabling SIP everything booted!

Thank you so much for making this! Apple in all their wisdom requires you upgrade Sierra if you want to update Xcode, I thought this machine had become entirely useless to me.

I've tried to search in the thread, but didn't found an answer. So I would guess that it's not done, but just in case : is there a way to install Sierra on a Mac Pro rev 1,1 ? I'm following Pike on Github, but it still indicates that there is no binary available for the moment for the boot.efi.

I've tried to search in the thread, but didn't found an answer. So I would guess that it's not done, but just in case : is there a way to install Sierra on a Mac Pro rev 1,1 ? I'm following Pike on Github, but it still indicates that there is no binary available for the moment for the boot.efi.

Thank you

Click to expand...

Not possible, the Mac Pro 1,1 and 2,1 CPUs don't support SSE4.1, and cannot be upgraded to ones that do.

For the record, I have a MacbookPro5,3 on macOS Sierra 10.12.4, and the brightness buttons work just fine without having to change any options, although I do use custom kernel extensions to enable USB and Keyboard support.

My first posting was the response for problem when Macbook won't respond to the brightness up/down buttons on the keyboard (post#4527). So what I did was After unselecting “Adjust keyboard brightness in low light.” my macBook start to respond to brightness up/down buttons. After unselecting I toggle back “Adjust keyboard brightness in low light" and now this works too.

My first posting was the response for problem when Macbook won't respond to the brightness up/down buttons on the keyboard (post#4527). So what I did was After unselecting “Adjust keyboard brightness in low light.” my macBook start to respond to brightness up/down buttons. After unselecting I toggle back “Adjust keyboard brightness in low light" and now this works too.

Click to expand...

It may simply be due to a bug in the Preferences file for the keyboard after the upgrade, that Apple didn't oversee.

@Rexsa thanks for the tip! I'm glad it works for you. On a MacBook5,2 unfortunately, there's no Ambient Light Sensor, so there's no way to change that setting in the UI and sudo defaults write /Library/Preferences/com.apple.iokit.AmbientLightSensor "Automatic Keyboard Enabled" -bool false doesn't really do anything I'm guessing cause kextstat | grep com.apple.iokit.AmbientLightSensor returns nothing, however, I will try to apply @dosdude1's patch from the installer. Tried the above with an empty plist though, just to see if anything might read from it, rebooted, no joy.

So after installing 10.12.4 on this old MacPro 3.1 and getting Night Shift to work, all seemed well.
Rebooting the next day and I get a message that SIP is enabled, so boot into Recovery Disc, but alas no, directory detected. OK boot into macOS boot USB (dosdudes1 patcher) and select post install bit and selected the appropriate patches for the MacPro 3.1 including the recovery disc patch, and re boot, then boot into Recovery Disc again no joy either. Erased USB and reinstalled patcher software 4.2.3 etc, done the post install recovery disc patch but no still cannot boot to Recovery Disc. Mercy Me what a to do, what is next.

So after installing 10.12.4 on this old MacPro 3.1 and getting Night Shift to work, all seemed well.
Rebooting the next day and I get a message that SIP is disabled, so boot into Recovery Disc, but alas no,
no directory detected. OK boot into macOS boot USB (dosdudes1 patcher) and select post install bit and selected the appropriate patches for the MacPro 3.1 including the recovery disc patch, and re boot, then boot into Recovery Disc again no joy either. Erased USB and reinstalled patcher software 4.2.3 etc, done the post install recovery disc patch but no still cannot boot to Recovery Disc. mercy Me what a to do, what is next.

Click to expand...

I think you mean you got a message that SIP is enabled? Disabling SIP is the correct procedure to load unsigned kexts.

I think you mean you got a message that SIP is enabled? Disabling SIP is the correct procedure to load unsigned kexts.

Click to expand...

Yes absolutely I meant enabled, I will edit.
But what I really need to know is why I cannot boot to my recovery disc even though I have gone to the post install screen and checked the recovery disc patch.

I have noticed that by rebooting to my Yosemite disc and in Disk Utility mounting the Recovery Disc for Sierra
and reading the platform support plist that it is the standard set of Sierra board IDs and Macs.

I'm curious if anyone else is having difficulties with the Sierra installation process. I had not caught the noted incompatibility with the current release, but I went back and downloaded the 10.12.2 install file from the link, and followed the instructions closely.

However the result for me is always the same. When I select the USB stick as the boot drive I just get about 5 minutes of an Apple logo, no progress bar, then eventually a reboot that just returns me to my desktop.

At this stage I've tried it with 2 USB sticks, and probably 3 versions of the Sierra install disks, but I can never even get the USB stick to boot.

Any suggestions on what could be my mistake, or something that might be causing issues?

I'm having trouble with the installer on my Early 2009 Mac Pro (4,1). Downloaded the patch, created the boot USB stick, used this week's Sierra release.

When I try to boot off the USB stick I get a long linger on the Apple logo screen (no progress bar under it), but after ~5 min the screen goes black and the computer simply reboots. Nothing launches. I end up back on my 10.11.6 desktop.

I'd tried it over the weekend and got the same result (though there were some suspicious error messages last time in the patcher log; this time I verified the log was clean of errors). That used a different USB stick, and the previous Sierra release.

My boot disk is a 3rd party SSD, and I do note one weirdness in the storage info display: it says the USB stick is HFS+, not Journaled HFS+ (which is what I specified when I wiped it in Disk Utility). Could that somehow be the problem? Any suggestions thankfully welcomed.

I'm curious if anyone else is having difficulties with the Sierra installation process. I had not caught the noted incompatibility with the current release, but I went back and downloaded the 10.12.2 install file from the link, and followed the instructions closely.

However the result for me is always the same. When I select the USB stick as the boot drive I just get about 5 minutes of an Apple logo, no progress bar, then eventually a reboot that just returns me to my desktop.

At this stage I've tried it with 2 USB sticks, and probably 3 versions of the Sierra install disks, but I can never even get the USB stick to boot.

Any suggestions on what could be my mistake, or something that might be causing issues?

As an aside, it would be nice to have a way to update @dosdude1's Post-Install app on the 10.12 install media from the Patcher app without having to create a whole new disk. Fortunately, I didn't need to boot into the USB stick to fix anything, but I spent a good while trying to figure out how to update the Post Install app on that sucker just in case. Man… why does Apple make things so complicated anymore?

As an aside, it would be nice to have a way to update @dosdude1's Post-Install app on the 10.12 install media from the Patcher app without having to create a whole new disk. Fortunately, I didn't need to boot into the USB stick to fix anything, but I spent a good while trying to figure out how to update the Post Install app on that sucker just in case. Man… why does Apple make things so complicated anymore?

Click to expand...

You can just copy it from the Resources folder of the latest macOS Sierra Patcher... Just right click on the Sierra Patcher App, click "Show Package Contents", go to Contents, Resources, and copy the macOS Post Install app to /Applications/Utilities of your patched Sierra USB drive.

You can just copy it from the Resources folder of the latest macOS Sierra Patcher... Just right click on the Sierra Patcher App, click "Show Package Contents", go to Contents, Resources, and copy the macOS Post Install app to /Applications/Utilities of your patched Sierra USB drive.

Click to expand...

Hi, the installer stick is not booting with the original sierra installer from apple. Only with the sierra installer from your mega download link. Thats what I do not like. The sierra installer should be working with the original apple file. Otherwise it could be patched from anybody and thats always a big risk. Waiting for your answer.

MacRumors attracts a broad audience
of both consumers and professionals interested in
the latest technologies and products. We also boast an active community focused on
purchasing decisions and technical aspects of the iPhone, iPod, iPad, and Mac platforms.