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.
Found a solution to the backlight issues on the Macbook 5'2

Replace copies of AppleBacklight.kext & AppleBacklightExpert.kext in system/library/extensions, and a copy of DisplayServices.framework in system/library/PrivateFrameworks with their El Capitan counterparts. Backlight responds to keyboard controls and maintains user settings after this.

Additional note: It's possible that only one or two of these files is necessary; further testing may be necessary (though my Macbook is running stable with all three files using their El Capitan versions so far)
 
Found a solution to the backlight issues on the Macbook 5'2

Replace copies of AppleBacklight.kext & AppleBacklightExpert.kext in system/library/extensions, and a copy of DisplayServices.framework in system/library/PrivateFrameworks with their El Capitan counterparts. Backlight responds to keyboard controls and maintains user settings after this.

Additional note: It's possible that only one or two of these files is necessary; further testing may be necessary (though my Macbook is running stable with all three files using their El Capitan versions so far)
I'm pretty sure it's only displayservices. Try to put back the other 2. Also can you send me the 10.11 displayservices
 
  • Like
Reactions: Teutone
I'm pretty sure it's only displayservices. Try to put back the other 2. Also can you send me the 10.11 displayservices

It probably is, but i threw in brightness on my MacBook just in case (I know the brightness frameworks alone don't fix the issue). Like I said, more testing is probably in order to know exactly what fixes it.

Makes me wonder if theres another framework swap that can fix the mouse issues (currently missing touchpad clicks).

Anyways, here's the El Capitan framework (thank goodness for time machine)
 

Attachments

  • DisplayServices.framework.zip
    70.9 KB · Views: 275
  • Like
Reactions: elxeneize
What?

P.S. do your keyboard volume buttons work?

Yeah. They've always worked.

I can two finger scroll and use the physical mouse button, but single finger tap-to-click and dual finger right-click are non-functioning, and cannot be enabled in settings (since the trackpad registers as a standalone mouse). Ctrl+clicking is a nuisance. :(

Tried using the older AppleUSBTrackpad kext, or the AppleUSBTopCase kext from El Capitan. This did diddly squat. But seeing as it was a framework issue with the backlight and backlight keys, it makes me wonder if it's similar with the trackpad. IDK if there is a mouse framework or what it's called though (looking through PrivateFrameworks, nothing contains names relating to trackpads, mice, or pointers)
 
Yeah. They've always worked.

I can two finger scroll and use the physical mouse button, but single finger tap-to-click and dual finger right-click are non-functioning, and cannot be enabled in settings (since the trackpad registers as a standalone mouse). Ctrl+clicking is a nuisance. :(

Tried using the older AppleUSBTrackpad kext, or the AppleUSBTopCase kext from El Capitan. This did diddly squat. But seeing as it was a framework issue with the backlight and backlight keys, it makes me wonder if it's similar with the trackpad. IDK if there is a mouse framework or what it's called though (looking through PrivateFrameworks, nothing contains names relating to trackpads, mice, or pointers)
Have you tried: /System/Library/PreferencePanes/Trackpad.prefpane from 10.11.6?

Also:

Please test this:
Undo changes to brightness framework and kexts (only keep DisplayServices)
does the backlight still work?
 
Have you tried: /System/Library/PreferencePanes/Trackpad.prefpane from 10.11.6?

Also:

Please test this:
Undo changes to brightness framework and kexts (only keep DisplayServices)
does the backlight still work?

Backlight keys are completely unresponsive with Sierra backlight kexts; DisplayServices and AppleBacklight(Expert) appear to go hand in hand (makes sense.)

Using the trackpad preferences pane from El Capitan removed all my mouse settings; My mouse works but does not register in settings.
 
Backlight keys are completely unresponsive with Sierra backlight kexts; DisplayServices and AppleBacklight(Expert) appear to go hand in hand (makes sense.)

Yaaaay! :D Thank you @MisutaaUrufu! This has made my week! I don't have a copy of the El Cap kexts... could you attach them also? Would the 10.12.3 kexts work?
 
Yaaaay! :D Thank you @MisutaaUrufu! This has made my week! I don't have a copy of the El Cap kexts... could you attach them also? Would the 10.12.3 kexts work?

Here's a zip with both backlight extensions from El Capitan & the Display Services framework, sorted into appropriate folders.
 

Attachments

  • MC240LLa Backlight Framework and Extensions.zip
    108.5 KB · Views: 475
Thank you! I grabbed a 10.12.3 installer and extracted the files into their default locations with Pacifist. It works! :D :D Yaaaay!
 
Thank you! I grabbed a 10.12.3 installer and extracted the files into their default locations with Pacifist. It works! :D :D Yaaaay!
Can you upload them? Also cc @dosdude1
[doublepost=1505492101][/doublepost]
Backlight keys are completely unresponsive with Sierra backlight kexts; DisplayServices and AppleBacklight(Expert) appear to go hand in hand (makes sense.)

Using the trackpad preferences pane from El Capitan removed all my mouse settings; My mouse works but does not register in settings.
1) awesome! Can you make sure whether Applebacklight and applebacklightexpert are both needed? Sorry to be annoying about this, but I just like to make the minimum number of kext changes possible. I have a feeling only the expert is needed, based on my reverse engineering.

2) oh well. It was worth a try
 
  • Like
Reactions: dosdude1
For some reason, I stopped getting updated for this thread. Glad to see a fix has finally been found! I knew it was something to do with the AppleBacklight(Expert) kexts, looks like I was just missing DisplayServices.
 
  • Like
Reactions: parrotgeek1
For some reason, I stopped getting updated for this thread. Glad to see a fix has finally been found! I knew it was something to do with the AppleBacklight(Expert) kexts, looks like I was just missing DisplayServices.
The email notification on this forum has never really worked for me either
 
Here's a zip with both backlight extensions from El Capitan & the Display Services framework, sorted into appropriate folders.
Wow!! Cool! It's works!
First of all tried just DisplayServices and FKeys of brightness did work but very laggy
After that I'm replaced kexts and reboot..I'm stupid. Mac reboot twice and Fkeys of brightness not response
So I guessed, open Kext Utility just wait for cache rebuild and reboot and this is it! Works like a charm
Thank You man! Remained just trackpad issues
Sorry for my English

upd.. Now I found Night Shift is broken
but color temperature changing
 
  • Like
Reactions: elxeneize
Thank You man! Remained just trackpad issues
Sorry for my English

upd.. Now I found Night Shift is broken
but color temperature changing

That's strange. It's working fine for me just fine on my end. Currently using the patched CoreBrightness.framework, though I did calibrate my display colors. Did you properly replace both AppleBrightness extensions and the Display Services framework with the El Capitan copies?

Also, it's no problem in regards to your english. No need to apologize. :)
 
  • Like
Reactions: wm4g
Hi,
I've installed and successfully updated Sierra on my MacBook Pro 17 Early 2009 for many months.

But now I'm stuck in 10.12.5 version, and when I check for updates on App store I get:
The operation couldn’t be completed. (NSURLErrorDomain error -1100.)
I've rerun post install hack from my original installation dvd, and run the last swpatch.sh from dosdue1, but I still getting the same error.

I've Googled around but I can't find anything about this particular error number.
Does anyone have any clue? Thanks!


This is the log part that, I think, show the problem:
Code:
por omisión    08:50:43.621902 +0200    kernel    SandboxViolation: softwareupdated(1362) deny(1) distributed-notification-post
por omisión    08:50:43.622394 +0200    softwareupdated    *** attempt to post distributed notification 'com.apple.packagekit.clearReceiptCache' thwarted by sandboxing.

Date/Time:     Sat Sep 16 08:50:43 2017
OS Version:    16F73
Application:   softwareupdated

Backtrace:
0   CoreFoundation                      0x00007fff90bb4b9a __CFGenerateReport + 282
1   CoreFoundation                      0x00007fff90a28b78 _CFXNotificationPost + 1704
2   Foundation                          0x00007fff924eed88 -[NSDistributedNotificationCenter postNotificationName:object:userInfo:options:] + 71
3   PackageKit                          0x00007fffa0ed3fa8 +[PKReceipt(CachedReceipts) _clearCacheInOtherProcesses] + 183
4   SoftwareUpdate                      0x00007fffa2c96c8d -[SUScan _scanMain:] + 2611
5   SoftwareUpdate                      0x00007fffa2c99b99 -[SUScan performSynchronousScan] + 101
6   SoftwareUpdate                      0x00007fffa2c8f3cd __276-[SUScanController refreshAvailableProductsInForeground:limitedToChanged:evenIfConfigurationChanged:initiatedByDeviceConnection:limitedToProductKeys:forCurrentConfigurati<…>
por omisión    08:50:43.626620 +0200    storeassetd    UpdateController: OS Update scan completed (took 64.24 seconds)
por omisión    08:50:43.701879 +0200    App Store    0x10f9f9800 - DocumentLoader::startLoadingMainResource: Returning empty document (frame = 0x10f585000, main = 1)
por omisión    08:50:43.701994 +0200    App Store    Memory usage info dump at MainFrameLoadCompleted:
por omisión    08:50:43.702029 +0200    App Store      javascript_gc_heap_capacity: 65536
por omisión    08:50:43.702064 +0200    App Store      virtual_size: 3872903168
por omisión    08:50:43.702096 +0200    App Store      document_count: 1
por omisión    08:50:43.702128 +0200    App Store      pagecache_page_count: 0
por omisión    08:50:43.702160 +0200    App Store      compressed: 0
por omisión    08:50:43.702192 +0200    App Store      phys_footprint: 82391040
por omisión    08:50:43.702224 +0200    App Store      resident_size: 120647680
por omisión    08:50:43.702256 +0200    App Store      internal: 43843584
por omisión    08:50:43.702288 +0200    App Store      javascript_gc_heap_extra_memory_size: 0
 
#1
Hi guys

After a bit of help! I've got a 4GB RAM, 500GB HDD (soon to be upgraded to 8GB ram and a ~500GB SSD) MacBook 5,1 2.0Ghz, model A1278 Late 2008. These upgrades will be taking place when I have the spare cash, with the RAM upgrade coming first and the SSD probably in the new year. The 8gb RAM is around £40-60 whereas a suitable size SSD is £130+ so the RAM will probably come first and I'll keep the HD for a while..

I want to upgrade to Sierra using the Sierra patch tool - I'm just wondering if anybody else on these forums has the same laptop and has upgraded to Sierra? Did you/do you encounter any troubles with it being unstable or things stopping working etc, or with this laptop and those specs am I G2G?? :)


Would appreciate some quick replies as I'm looking to do patch the upgrade on Sunday afternoon!!



Thanks in advance
 
That's strange. It's working fine for me just fine on my end. Currently using the patched CoreBrightness.framework, though I did calibrate my display colors. Did you properly replace both AppleBrightness extensions and the Display Services framework with the El Capitan copies?

Also, it's no problem in regards to your english. No need to apologize. :)
Do you mean that you have working NightShift?
I'm just replaced the AppleBacklight.kext AppleBacklightExpert.kext and DisplayServices.framework from your post
F keys works but nightshift turn off/on without changes. So this isn't biggest problem
 
Do you mean that you have working NightShift?
I'm just replaced the AppleBacklight.kext AppleBacklightExpert.kext and DisplayServices.framework from your post
F keys works but nightshift turn off/on without changes. So this isn't biggest problem
Try 10.12.3 kexts & framework
@MisutaaUrufu
(It's always better to use the file closest to the current os version)
 
I had the same problem for a while. The root cause is softwareupdated crashing and restarting every 10 seconds because it can't load SUVMMFaker.dylib.

There are two steps I took to solve this:

1) First, make sure the file is not quarantined by running:
Code:
sudo xattr -d com.apple.quarantine /usr/local/lib/SUVMMFaker.dylib

2) Second, make sure that your /usr/local/lib/ folder has the same permissions as /usr/local/
In my case, /usr/load/lib/ did not have the proper permissions, it was drwx------ instead of drwxr-xr-x
Code:
sudo chmod 755 /usr/load/lib/

Maybe only step 2 was needed, but it can't hurt to remove the quarantine extended attributes.

After this, restart the software update daemon manually or just re-run
Code:
sudo ./swupatch.sh

Things should be working OK after following these steps. Hope it helps!

Oh. My. God. @SaitoKoreano you are a SAINT! This has worked for me as well. I can confirm my permissions were not set in step #2 and that was the issue.

Also @mskblackbelt Thank you for quoting my original post alerting me to recheck these forums! Page 198 was my lucky charm. :)
 
Try 10.12.3 kexts & framework
@MisutaaUrufu
(It's always better to use the file closest to the current os version)

I only have access to the El Capitan copies (as of July 2017) and the Sierra 10.12.6 copies. I upgraded to 10.12.6 directly so i don't have any other copies.

Do you mean that you have working NightShift?
I'm just replaced the AppleBacklight.kext AppleBacklightExpert.kext and DisplayServices.framework from your post
F keys works but nightshift turn off/on without changes. So this isn't biggest problem

Have you patched CoreBrightness.framework using the Night Shift patch? I used the patch before downgrading the brightness extensions and display devices framework.
 
Hi,
I've installed and successfully updated Sierra on my MacBook Pro 17 Early 2009 for many months.

But now I'm stuck in 10.12.5 version, and when I check for updates on App store I get:
The operation couldn’t be completed. (NSURLErrorDomain error -1100.)
I've rerun post install hack from my original installation dvd, and run the last swpatch.sh from dosdue1, but I still getting the same error.

I've Googled around but I can't find anything about this particular error number.
Does anyone have any clue? Thanks!


This is the log part that, I think, show the problem:
Code:
por omisión    08:50:43.621902 +0200    kernel    SandboxViolation: softwareupdated(1362) deny(1) distributed-notification-post
por omisión    08:50:43.622394 +0200    softwareupdated    *** attempt to post distributed notification 'com.apple.packagekit.clearReceiptCache' thwarted by sandboxing.

Date/Time:     Sat Sep 16 08:50:43 2017
OS Version:    16F73
Application:   softwareupdated

Backtrace:
0   CoreFoundation                      0x00007fff90bb4b9a __CFGenerateReport + 282
1   CoreFoundation                      0x00007fff90a28b78 _CFXNotificationPost + 1704
2   Foundation                          0x00007fff924eed88 -[NSDistributedNotificationCenter postNotificationName:object:userInfo:options:] + 71
3   PackageKit                          0x00007fffa0ed3fa8 +[PKReceipt(CachedReceipts) _clearCacheInOtherProcesses] + 183
4   SoftwareUpdate                      0x00007fffa2c96c8d -[SUScan _scanMain:] + 2611
5   SoftwareUpdate                      0x00007fffa2c99b99 -[SUScan performSynchronousScan] + 101
6   SoftwareUpdate                      0x00007fffa2c8f3cd __276-[SUScanController refreshAvailableProductsInForeground:limitedToChanged:evenIfConfigurationChanged:initiatedByDeviceConnection:limitedToProductKeys:forCurrentConfigurati<…>
por omisión    08:50:43.626620 +0200    storeassetd    UpdateController: OS Update scan completed (took 64.24 seconds)
por omisión    08:50:43.701879 +0200    App Store    0x10f9f9800 - DocumentLoader::startLoadingMainResource: Returning empty document (frame = 0x10f585000, main = 1)
por omisión    08:50:43.701994 +0200    App Store    Memory usage info dump at MainFrameLoadCompleted:
por omisión    08:50:43.702029 +0200    App Store      javascript_gc_heap_capacity: 65536
por omisión    08:50:43.702064 +0200    App Store      virtual_size: 3872903168
por omisión    08:50:43.702096 +0200    App Store      document_count: 1
por omisión    08:50:43.702128 +0200    App Store      pagecache_page_count: 0
por omisión    08:50:43.702160 +0200    App Store      compressed: 0
por omisión    08:50:43.702192 +0200    App Store      phys_footprint: 82391040
por omisión    08:50:43.702224 +0200    App Store      resident_size: 120647680
por omisión    08:50:43.702256 +0200    App Store      internal: 43843584
por omisión    08:50:43.702288 +0200    App Store      javascript_gc_heap_extra_memory_size: 0
Run "sudo softwareupdate --clear-catalog" in Terminal, that'll fix your issue.
 
Hey guys can someone help me out? I'm trying to upgrade to Sierra on my MacBook Late 2008 unibody. I've followed all the instructions correctly, installed the Mac OS Sierra app on the USB through the patch app, turned off SIP.

Every time I try and boot from the USB I get the following screen after the Apple logo screen loads about 3/4 of the way. I've attached a pic of the stage of the process I'm up to. A quick reply would be awesome as I'm looking to sort this tonight!! :)
[doublepost=1505678351][/doublepost]
Hey guys can someone help me out? I'm trying to upgrade to Sierra on my MacBook Late 2008 unibody. I've followed all the instructions correctly, installed the Mac OS Sierra app on the USB through the patch app, turned off SIP.

Every time I try and boot from the USB I get the following screen after the Apple logo screen loads about 3/4 of the way. I've attached a pic of the stage of the process I'm up to. A quick reply would be awesome as I'm looking to sort this tonight!! :)

I can't upload a pic but it's the standard grey screen with a dark grey O symbol with a / through it. Like a STOP/NO symbol.. any ideas??
 
Last edited:
Ok, can you run the patch again, and when it completes, open Terminal and type "diskutil list". Send me a screenshot of the output.

Hi dosdude. Hopefully you're still active on these forums!

I'm trying to upgrade from El Capitan to Sierra on my MacBook 5,1 late 2008 unibody. I downloaded the latest patch and Sierra file from your website (17th Sept 2017), formatted my 32GB SanDisk Cruzer Blade as per your guide, launched the patch tool and created the USB. Twice I got the prohibited symbol, so I re-formatted, re-patched etc and 3 times I got the prohibited symbol. I turned off SIP before doing anything, then went back and enabled, disabled again and tried again before getting the prohibited sign 3 more times.

What can I do to fix this?! :-(
[doublepost=1505687046][/doublepost]@dosdude1 could it have anything to do with me having FileVault on? I am in the process of turning it off now.

Is there any other things you think could be causing the issue?
[doublepost=1505687869][/doublepost]@dosdude1 When I format the USB in disk utility with GUID partition map, it shows in CCC as "no partition map" no matter how many times I format as GUID, carbon copy cloner says it has no partition path. Could this be the problem?
[doublepost=1505690380][/doublepost]@dosdude1 FIXED! After checking in CCC the partition map was none. Read online that disk utility in El Capitan has been downgraded (this is my first Mac so haven't used other versions) so I downloaded an Old Disk Utility app, formatted in there, sure as hell CCC recognised it had a GUID map. Ran the patch, rebooted and sure enough the macOS Sierra installer opened.

... Then it said cannot complete because you're currently decrypting data, so I'm leaving it to do that overnight and will upgrade in the morning!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.