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.
The prohibitory sign is caused by macOS detecting you have an invalid model (one that is not in /System/Library/CoreServices/PlatformSupport.plist). The methods around that are to skip model verification using a kernel flag, or adding the model to the file (which can get overwritten with updates as seen in your situation).

Note that you also add any kernel extensions and support files if those were overwritten too.

Thx for your help.

However I found a different and very simple route to the solution.
I booted from the partition with OSX El Capitan, mounted the external harddisk with macOS Sierra, and with CarbonCopyCloner I then could repair the macOS Sierra Recovery Partition.

Repairing of the Recovery Partition took less then a minute (6 files where copied) and now the macOS Recovery partition on the internal harddisk is bootable and all tools on it are available.
 
Still haven't installed Sierra but heres a detailed dump from El Capitan of a Macbook white 5,2 It may be useful for anyone who has Sierra and wants to investigate the Trackpad not being loaded correctly issue. Just search for "trackpad" . The product id is 0x229.


Use this terminal command on Sierra to do the same. It dumps the info to your home directory with the desired filename:
system_profiler -detailLevel full >> filename.txt


Areas to investigate:
System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBEHCIPCI.kext/Contents/Info.plist
contains references to this Macbook 5,1 and Macbook 5,2 in El Capitan which would probably be removed in Sierra. There may be other potential cases. The attached dump may provide clues

The Trackpad System Preferences pane is now 5mb in size in Sierra which is down from over 237mb in El Capitan. I checked this from a friends Macbook pro. All the resources and maybe other things have been moved elsewhere.

EDIT:
If you look here:
/System/Library/Extensions/AppleUSBTopCase.kext/Contents/PlugIns/AppleUSBTrackpad.kext/Contents/Info.plist you will see loads of references to older Mac's trackpads such as Fountain GIS. When looking at Linux source code (found here: https://github.com/spotify/linux/blob/master/drivers/input/mouse/appletouch.c) for Apple trackpads they look like references to older Macbooks and Powerbooks.
I wonder if AppleUSBTrackpad.kext is being loaded because of one of these.
 

Attachments

  • Macbook 5,2.txt
    2 MB · Views: 2,335
Last edited:
Is there an 'official' place we can record the success of the patch so that a matrix can be built with results for each system type and subtype?

Here's the upgrade status for my mid-2009 17" MBPro with this base config:

Model Name: MacBook Pro
Model Identifier: MacBookPro5,2
Processor Name: Intel Core 2 Duo
Processor Speed: 3.06 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 6 MB
Memory: 8 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP52.008E.B05
SMC Version (system): 1.42f4

Upgrade using the 'dosdude1' Sierra patch and Sierra Update patch went through as advertised through to PB6. Worked very slick.

Issues:

o Computer sleep not working when the lid is closed, fans working harder than under El Capitan.
- This seems to have been cured with an SMC reset.
o "Bluetooth: not available" with the internal hardware, works OK with a Bluetooth USB dongle.
o The white power light is not lit during normal operation, but flashes normally in computer sleep.

In general, performance seems about the same as El Capitan.
The sharing of Desktop and Documents folders is great, the reason why I went ahead with this patch.
 
Solved the Bluetooth problem. Bluetooth diagnostics report showed a missing library, I copied one from an El Capitan system. The file is:

/System/Library/PrivateFrameworks/PlatformHardwareManagement.framework

Power light still doesn't work though.
 
Solved the Bluetooth problem. Bluetooth diagnostics report showed a missing library, I copied one from an El Capitan system. The file is:

/System/Library/PrivateFrameworks/PlatformHardwareManagement.framework

Power light still doesn't work though.
Is it supposed to? (me, I'm thinking this is intended behaviour). My 2008 MBP does the same thing. When the lid is open, the light isn't on. When I close the lid, the light comes on to let me know it's still on. Then if it goes to sleep, it does the slow flash.

Not sure what the point would be to having the light on when you have it open??
 
Is it supposed to? (me, I'm thinking this is intended behaviour). My 2008 MBP does the same thing. When the lid is open, the light isn't on. When I close the lid, the light comes on to let me know it's still on. Then if it goes to sleep, it does the slow flash.

Not sure what the point would be to having the light on when you have it open??
Yeah, that's what it should do. The Power LED should not be on at all times, it only comes on when the display isn't on.
 
- Yes, after checking with my wife's Mac, you're right - the light is not on during normal use. Sorry for the false alarm.

Incidentally, I forgot to mention in my original post, instead of doing a clean install as recommended by Apple and the patch developer I did an upgrade to the existing El Capitan system.
 
Still haven't installed Sierra but heres a detailed dump from El Capitan of a Macbook white 5,2 It may be useful for anyone who has Sierra and wants to investigate the Trackpad not being loaded correctly issue. Just search for "trackpad" . The product id is 0x229.

I tried replacing the .kext files in System/Library/Extensions/AppleUSBTopCase/Contents/Plugins with the files from my last clone of El Capitan before I upgraded to Sierra. Restarted, and still no control over the trackpad in my Macbook5,2.

I'm not as far along in code and such as a lot of you are, so I don't understand what all that information is about that you posted.
 
Has anyone else noticed that Bittorrent Sync is taking a lot of CPU constantly under Sierra?

This seems to have started in the last few Betas.

Using dtruss seems to show that the app is constantly polling.

EDIT: Found the answer. Apparently 2.3.8 is broken, need to use the 2.4 beta (which changes a whole bunch of other things).
 
Last edited:
I tried replacing the .kext files in System/Library/Extensions/AppleUSBTopCase/Contents/Plugins with the files from my last clone of El Capitan before I upgraded to Sierra. Restarted, and still no control over the trackpad in my Macbook5,2.

I'm not as far along in code and such as a lot of you are, so I don't understand what all that information is about that you posted.
Did you just reboot or did you use a utility (such as kext utility - http://mac.softpedia.com/get/System-Utilities/Kext-Utility.shtml) to flush and rebuild your kernel cache? (also fixes permissions too) - with you populating files in that directory, they'll be owned by YOU, not the system (root:wheel).
 
Hi,
I'm trying to update my 9,1 imac to PB6 from PB4 with @dosdude1 tool. I followed all the instructions but no success. I applied the patch, made the refresh updates and tried to reboot the system, but still show no update available.
Someone is able to make an accurate guida of all manual steps to perform to be able update?
Thank you
 
Hi,
I'm trying to update my 9,1 imac to PB6 from PB4 with @dosdude1 tool. I followed all the instructions but no success. I applied the patch, made the refresh updates and tried to reboot the system, but still show no update available.
Someone is able to make an accurate guida of all manual steps to perform to be able update?
Thank you
Yeah, what you need to do is reboot the system, open the tool, refresh updates twice, reboot again, open tool, patch desired update, refresh updates ONCE only, then check the App Store.
 
Yeah, what you need to do is reboot the system, open the tool, refresh updates twice, reboot again, open tool, patch desired update, refresh updates ONCE only, then check the App Store.

@dosdude1 I followed your instructions, but in the app store always "no update available". Please other suggestions?
Thanks
 
Here's a novel idea. You could go back to page 77 (https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/page-77) when PB6 came out and read. There's been lots of information posted...you really should use the information that's already available to troubleshoot your issue.

Ooh. Maybe you've been trying too hard and they temporarily blacklisted you? Hopefully you haven't been hammering them since you wrote that. :). (me, I would have rebooted and tried again...maybe after about an hour delay?). :)
[doublepost=1471950307][/doublepost]
So, what have you done in terms of troubleshooting?
*hint*. The message above the last one you posted was actually something you could have tried.
One page back, I posted where the .dist file is. /private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/s/031-72720
If you have that folder, then there's a .dist file for dosdude1's tool to patch. If you don't, then the software updater hasn't properly done an update.
If you monitor the folder
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager when you do a software update, you'll see when it adds updates, as you'll have folders with the current date and time when they're snatched.
Until there's a software update for dosdude1's tool to patch, you're waiting for an update from Apple's servers.

fischersd where I find the directory / private / var / folders / zz ...?
in the finder in the root there are four folders: Applications, Library, System and Users. Nowhere is / private / var / folders / zz ...
 
fischersd where I find the directory / private / var / folders / zz ...?
in the finder in the root there are four folders: Applications, Library, System and Users. Nowhere is / private / var / folders / zz ...
There's lots of hidden folders as part of your Operating System. It's intended to keep users that don't know what they're doing from causing damage and making the system unstable.

If you had opened up Finder, clicked on Go, then Go To Folder and pasted in the directory given, it would have gone there.
 
There's lots of hidden folders as part of your Operating System. It's intended to keep users that don't know what they're doing from causing damage and making the system unstable.

If you had opened up Finder, clicked on Go, then Go To Folder and pasted in the directory given, it would have gone there.

fischersd Ok. Thanks. The directory exists and also the .dist file with time in which I have launched the dosdude1 tool. So I just have to wait for the update from apple?
 
fischersd Ok. Thanks. The directory exists and also the .dist file with time in which I have launched the dosdude1 tool. So I just have to wait for the update from apple?
Ok, did dosdude1's tool ever state that the update was patched? That you have the .dist file there means that your App Store sees the update as being available, but doesn't recognize it as being applicable to your system. (that's what the tool does - it patches the .dist file so it makes the update available in the App Store).
If the only thing in that directory is the .dist file, then App Store still doesn't think the update is applicable to your system (when it does, it'll download 4 .pkm files that are needed to present and apply the update to your system).
You ARE using the latest version of his tool, right? You downloaded a new version before you started this, right?
 
Ok, did dosdude1's tool ever state that the update was patched? That you have the .dist file there means that your App Store sees the update as being available, but doesn't recognize it as being applicable to your system. (that's what the tool does - it patches the .dist file so it makes the update available in the App Store).
If the only thing in that directory is the .dist file, then App Store still doesn't think the update is applicable to your system (when it does, it'll download 4 .pkm files that are needed to present and apply the update to your system).
You ARE using the latest version of his tool, right? You downloaded a new version before you started this, right?

I'm using the latest version of the tool that I downloaded before. Once launched the patch, the tool says that patch was successfully done, in fact, the time file is when I applied the patch
 
I'm using the latest version of the tool that I downloaded before. Once launched the patch, the tool says that patch was successfully done.
That you downloaded "before". Ok, I just snagged it to check and mine is reporting as version 3.0. You can also "Patch Update" again, just to make sure the .dist file has been patched.
Were there any .pkm files in that directory?
If you click on Refresh Updates and wait a few minutes, do you get any .pkm files?

If not, you can try the manual method for getting updates. Open a terminal window and type
sudo softwareupdate --list
If it says that there's no updates available (despite the .dist file being patched) then your software updater could be in a messed up state. One suggestion to fix this posted previously was to boot up in safe mode, then in regular mode.
 
That you downloaded "before". Ok, I just snagged it to check and mine is reporting as version 3.0. You can also "Patch Update" again, just to make sure the .dist file has been patched.
Were there any .pkm files in that directory?
If you click on Refresh Updates and wait a few minutes, do you get any .pkm files?

If not, you can try the manual method for getting updates. Open a terminal window and type
sudo softwareupdate --list
If it says that there's no updates available (despite the .dist file being patched) then your software updater could be in a messed up state. One suggestion to fix this posted previously was to boot up in safe mode, then in regular mode.
The tool version is 3.0. If i try to reapply the patch, the tool says that the patch is successfully done, and when i refresh the update, i noticed that the time of the dist file didn't change. Does this mean that the file is not patched?
I followed your instructions with the terminal, but no new software available.
 
The tool version is 3.0. If i try to reapply the patch, the tool says that the patch is successfully done, and when i refresh the update, i noticed that the time of the dist file didn't change. Does this mean that the file is not patched?
I followed your instructions with the terminal, but no new software available.
"Refresh Update" really does the same thing that the command line does - it checks for updates. The advantage of doing it at the command line is that you get the feedback. The date on the .dist file should only change when you patch it.
Just for fun, I patched mine just now, so it has today's date and the time that I patched it.
So, you can either boot in safe mode (hold down the shift key while it's booting up, release when the progress bar shows below the Apple logo), then reboot into normal mode. Or, you can wait for it to show up.
 
"Refresh Update" really does the same thing that the command line does - it checks for updates. The advantage of doing it at the command line is that you get the feedback. The date on the .dist file should only change when you patch it.
Just for fun, I patched mine just now, so it has today's date and the time that I patched it.
So, you can either boot in safe mode (hold down the shift key while it's booting up, release when the progress bar shows below the Apple logo), then reboot into normal mode. Or, you can wait for it to show up.

I can't boot in safe mode, instead of the apple logo appears the prohibition sign. So my problem is that the file is not patched even though the tool says that the patch is applied successfully?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.