macOS Sierra 10.12.4 (16E195) - Final Release - Updated

Hi,

just updated !

All fine here, i have only re-applied the Toleda Patch to AppleHDA for Alc 889 and VGA patch to Intel HD3000.

No Night Shift ... at the moment .

I'm looking for a solution ...

 

Hint : easy solution ---> i have changed my smbios.plist from iMac12,1 to iMac13,1 --> now night shift is enabled ...

 

BTW : we could use F.lux - free app on not supported macs

https://justgetflux.com

udpate just now. does the apple loading status bar, gets to the end... black screen. no change for 10 minutes.

 

HD6870... wonder if it's the issue. going to do some further testing.

 

HD6870 here too, and same experience from a fresh 10.12.2 install onwards.

It's random, the OS does boot behind the black screen. I restart it with the keyboard when it happens.

It's a pity...

Maybe in the next macOS version, we'll see good news about this.

 

I hope 

well we should .7 was major .8 was minor .9 was minor .10 was major .11 minor .12 minor so .13 should be major and if it turns into 11.0 that will be over the top

Big like for 10.12.4, a pregnancy of almost 9 monthsbut was born good!

working Night Shift  Credit Goes to pikeralpha

 

https://pikeralpha.wordpress.com/2017/01/30/4398/

Very nice your wallpaper, share with us! 

No luck here.

 

After the upgrade my hackintosh takes several minutes to boot to finally give a completely yellow screen. Used Carbon Copy Cloner to restore to 10.12.3.

 

I'm using a AMD Radeon HD 7750 with a custom kext in Clover.  

Very nice your wallpaper, share with us! 

scientific space planet galaxy stars

scientific_space_planet_galaxy_stars.jpg.zip

For those booting to a black screen..   just just HDMI cable in than disconnect...   work for me.

Upgraded my machine yesterday, the only post installation I had done is to rerun Toleda's script to fix the audio. Also edited Clover config to MacPro6,1 to enable night shift.

Somehow I feel this version is snappier than before.

HD6870 here too, and same experience from a fresh 10.12.2 install onwards.

It's random, the OS does boot behind the black screen. I restart it with the keyboard when it happens.

 

 

Hi,

just updated !

All fine here, i have only re-applied the Toleda Patch to AppleHDA for Alc 889 and VGA patch to Intel HD3000.

No Night Shift ... at the moment .

I'm looking for a solution ...

 

Hint : easy solution ---> i have changed my smbios.plist from iMac12,1 to iMac13,1 --> now night shift is enabled ...

 

BTW : we could use F.lux - free app on not supported macs

https://justgetflux.com

 

 

For those booting to a black screen..   just just HDMI cable in than disconnect...   work for me.

No Web-Drive.

System Software Overview:

System Version: macOS 10.12.4 (16E195)

 Kernel Version: Darwin 16.5.0

Boot Volume: Mac

Boot Mode: Normal

User Name:

Secure Virtual Memory: Enabled

System Integrity Protection: Enabled

 

 

all ok

 

 

Someone with Intel HD 4000 got Night Shift working?

I don't know if injection of FakeCPUID is still needed.  Will check when Darwin sources are released.

Followup: Apple released the xnu sources to Darwin 16.5. There's no mention of kabylake, so faking CPUID to skylake still necessary in 10.12.4

Someone with Intel HD 4000 got Night Shift working?

 

Works fine here on my laptop (using MBP9,1). Didn't have to do anything.

 

HD6870 here too, and same experience from a fresh 10.12.2 install onwards.

It's random, the OS does boot behind the black screen. I restart it with the keyboard when it happens.

 

indeed, it is booting beyond the black screen because it goes out of verbose mode console and into the black screen when booting -v, so we know it's not crashing.

 

are you saying you got it to boot to a regular log-in screen after many attempts?

 

 

For those booting to a black screen..   just just HDMI cable in than disconnect...   work for me.

 

so just plug in an HDMI cable and then disconnect?

Works fine here on my laptop (using MBP9,1). Didn't have to do anything.

Nice to know!

 

Now I feel more tranquil to upgrade to Sierra soon...

 

Thank you so much Riley 

For those booting to a black screen..   just just HDMI cable in than disconnect...   work for me.

 

tried this, did not work for me. I am using DVI for display.

 

I plugged HDMI cable in before booting, and unplugged at black screen, didn't fix.

I plugged HDMI cable in at the black screen and waited, and unplugged, didn't fix.

 

hmmmmmm

tried this, did not work for me. I am using DVI for display.

 

I plugged HDMI cable in before booting, and unplugged at black screen, didn't fix.

I plugged HDMI cable in at the black screen and waited, and unplugged, didn't fix.

 

hmmmmmm

There may be an issue with older clover bootloaders there are recommendations to upgrade to clover bootloader 4045? Or the latest in order to be able to properly inject kext fixes/injections.

 

Normally, I don't use inject ATI for my RX 480 but in 12.4 I need to in order to avoid blackscreen after boot. Maybe inject ATI will help if your not doing so now, and update clover bootloader.

 

I also noticed my AMD 5450 which used to get native support no longer does, I need to add ID to info.plist in AMD5000Controllerkext and 3000kext. It worked fine up until the 12.3 betas. It seems they have changed a lot in 12.4 it's possible the older cards that had support may need kext fixes or possibly they may need IGPU as primary boot like the newer AMD cards, hopefully not.

There may be an issue with older clover bootloaders there are recommendations to upgrade to clover bootloader 4045? Or the latest in order to be able to properly inject kext fixes/injections.

 

Normally, I don't use inject ATI for my RX 480 but in 12.4 I need to in order to avoid blackscreen after boot. Maybe inject ATI will help if your not doing so now, and update clover bootloader.

 

I also noticed my AMD 5450 which used to get native support no longer does, I need to add ID to info.plist in AMD5000Controllerkext and 3000kext. It worked fine up until the 12.3 betas. It seems they have changed a lot in 12.4 it's possible the older cards that had support may need kext fixes or possibly they may need IGPU as primary boot like the newer AMD cards, hopefully not.

 

i can access EFI from my windows install by using diskpart to mount the drive. Can I just pop the new clover CLOVERX64.efi file into the EFI\CLOVER folder and try again, or do I need to replace a lot more files?

 

 

Someone with Intel HD 4000 got Night Shift working?

Works fine for me (tested during the betas without a working NVIDIA driver).

There may be an issue with older clover bootloaders there are recommendations to upgrade to clover bootloader 4045? Or the latest in order to be able to properly inject kext fixes/injections.

 

 

I used BD Utility to create a windows bootable USB EFI drive, and then I copied my config into there along with the associated drivers, using the newest Clover 4049, and it booted fine!

 

Thanks for your advice.

 

I was concerned about updating, but now I'll just move the EFI folder I just configured over to my Local EFI folder and keep this one as a spare bootable on my desk.

I used BD Utility to create a windows bootable USB EFI drive, and then I copied my config into there along with the associated drivers, using the newest Clover 4049, and it booted fine!

 

Thanks for your advice.

 

I was concerned about updating, but now I'll just move the EFI folder I just configured over to my Local EFI folder and keep this one as a spare bootable on my desk.

 

I have found that if you run clover install twice (2X) it will load it in the EFI Backups folder on main partition.    If you check after installing clover in the EFi boot partition that the old clover folder gets moved to the EFI Backups folder.    Check to see if the Backup folder has clover 4049 if it has a lower or older version you can install again the same way and it will appear in the backups folder.    you can just delete the old one(S) that appear.    That way if you need to boot into recovery disk you have the same clover configuration.

I have found that if you run clover install twice (2X) it will load it in the EFI Backups folder on main partition.    If you check after installing clover in the EFi boot partition that the old clover folder gets moved to the EFI Backups folder.    Check to see if the Backup folder has clover 4049 if it has a lower or older version you can install again the same way and it will appear in the backups folder.    you can just delete the old one(S) that appear.    That way if you need to boot into recovery disk you have the same clover configuration.

 

I just copy the EFI partition to a secure storage on my NAS server. if I ever need to format a USB key with EFI I just prepare it in windows with an installer of some kind (in this case, BD Utility), and then overwrite the contents of the partition with the last known good configuration. I have every EFI backup from r3065 that is known working- up to the latest r4049 that I just pushed to the live EFI partition that gets booted on system start up.

 

much easier, and i don't need access to OSX or macdrive to retrieve the folder- and i know it works and exactly which version it is. I can access it from any OS or any device.