macOS 10.12 Sierra Unsupported Macs Thread

[pkouame]

Hi guys!

I'm looking for a more elegant way to skip machine chek in Sierra (without editing dist files or without using any 3rd party url). Anyone knows about "/var/db/softwareupdated/productvalidations.plist"? I we found a way to skip some checks for updates (maybe). When i check SoftwareUpdate PrivateFramework with 'otool -tvV', i found some intresting things:
- method with name "loadProductValidations", that loads productvalidations.plist (if file exists) with dictionaryWithContentsOfFile
- method with name "validationOverrideForProductKey" that checks a dict about the following keys:
- pass-all-checks (boolValue)
- installation-check (string, checked for "pass")
- volume-check (string, checked for "pass")
- visible (boolValue)
- visibleOnlyForPredicate (boolValue)

But i can't figure out the right syntax for "/var/db/softwareupdated/productvalidations.plist". Anyone can help me how to debug the running softwareupdated with SoftwareUpdate privateframework?

Installation checks isn't determined by SoftwareUpdate, but rather sysctl and Apple Installer APIs.

Wow buddy! Not sure where you're going with this.

First, you definitely DON'T want to patch machdep.cpu.features. Aside from the security aspect here, almost all apps/system services etc... at one point in their life check for these cpu features to, sometimes configure themselves correctly. You would break a lot of stuff. So don't even go there.

Second is var/db/softwareupdated/productvalidations.plist even a thing? I don't have a trace of it on my system. Do you? Are there symbols in the binary you are otool'ing that point to a productvalidations.plist? Just asking...

 

[foxlet]

No, validation checks is determinated by DistributionKit.framework (this frameworks embed the JavaScriptCore.framework and calls sysctls with sysctlbyname method, i can override that checks and make fool SoftwareUpdate to beleive it's a virtulized system, but it's require to modify /System/Library/LaunchDaemons/com.apple.softwareupdated.plist, and i don't want to repatch it again and again, and i want a system with absolute minimal mods and a functioning rootless). DistributionKit being called from PackageKit and SoftwareUpdate.framework.

Softwareupdate.framework is embedded in the softwareupdated, and softwareupdated is called when user check updates via AppStore.app and/or with /usr/sbin/softwareupdate.

If you look into SoftwareUpdate.Framework (/System/Library/PrivateFrameworks/SoftwareUpdate.framework/SoftwareUpdate) with otool, you can see 'loadProductValidations' and 'validationOverrideForProductKey'. So i'm need to figure out what is the correct syntax for that plist, and boom, it's working.

Edit:
Firstly i built a kext to patch machdep.cpu.features. It's worked, and i can add VMM to it, but when the kext loaded, every app thinks about its a virtualzed OS. The main problem is in xnu, because many and many timing related stuff goes confused when see VMM on a non virtualized OS. So if i can't limit VMM to SU only, it's not a good mod.

AUS works in Rootless/SIP mode, and doesn't need any modification of macOS binaries.

I can't find the plist in question, either, and it doesn't seem to be generated by default otherwise.

 

[Czo]

Wow buddy! Not sure where you're going with this.

First, you definitely DON'T want to patch machdep.cpu.features. Aside from the security aspect here, almost all apps/system services etc... at one point in their life check for these cpu features to, sometimes configure themselves correctly. You would break a lot of stuff. So don't even go there.

Second is var/db/softwareupdated/productvalidations.plist even a thing? I don't have a trace of it on my system. Do you? Are there symbols in the binary you are otool'ing that point to a productvalidations.plist? Just asking...

I wan't to limit VMM to SU only, but currently i don't know, how to detect which process is asking that sysctl request in a kext.

That file is not exist on macs by default, but when you create it, and next time check the updates with "killall -9 softwareupdated; softwareupdate --verbose --list" as root, you can see it in /var/log/install.log. Simply run this: "otool -tvV /System/Library/PrivateFrameworks/SoftwareUpdate.framework/SoftwareUpdate" and search for "validationOverrideForProductKey" and "_loadProductValidations".

 

[RumorzGuy]

My gosh! I thought this thread was supposed to be in English!

Sorry, but the atmosphere has been so heavy here lately, I thought I'd throw in a bit of humor for those who can appreciate it.

 

[Czo]

AUS works in Rootless/SIP mode, and doesn't need any modification of macOS binaries.

It's require to modify catalog url that i don't wan't (because it's from untrusted source).

 

[pkouame]

It's require to modify catalog url that i don't wan't (because it's from untrusted source).

Ouch! The old "untrusted source" argument...

Firstly, you've uncovered some really fascinating facts about softwareupdate by inspecting private frameworks. If by touching a productvalidation.plist in /var/db you can confirm that the softwareupdate daemon actually attaches to it. Bravo! Now, by definition private frameworks are undocumented and proprietary so the plist xml format is unknown (by us). I might suggest experimenting and adding your own xml keys either manually or with PlistBuddy, until you find something that bites. Have fun.

Second, they are called private frameworks for a reason. So I, for one, cannot/should not discuss that here, as I am actually legally bound not to. Sorry. But more power to you, and this is venturing into blackhat exploit territory. Ours may not be the thread for you. Maybe offline?

Third, as far as "untrusted" goes...Read this thread about AUS and you'll realize that the catalog is "open" for you to inspect and verify that its payload comes from "official" Apple cdn sources. I have. In fact, after swapping catalogs you can use the good old Mac App Store to pull them down (from Apple). I'll let @foxlet expand on this if he wants to...

 

[Pinarek]

Now comes in Sierra, I have installed the 10.12.1 Beta1, Beta2 not to download.
I used the AUSenabler.app and tried the 2 different options .. still no update available.

SIP is disable and in Security is no restrictions

How to load the Developer Update Beta 2 for Sierra 10.12.1 one now?

So a circus, after each beta update is nothing on which damned mac mini3,1 unsupportet Mac.

How easy it is but at Hackintosh .. since there are no problems and the Dev. Updates come immediately.

I'll throw the damned Mac mini3,1 soon in the corner.

Over and over again: no updates available .... it sucks !!! nothing works.

 

[foxlet]

Now comes in Sierra, I have installed the 10.12.1 Beta1, Beta2 not to download.
I used the AUSenabler.app and tried the 2 different options .. still no update available.

SIP is disable and in Security is no restrictions

How to load the Developer Update Beta 2 for Sierra 10.12.1 one now?

So a circus, after each beta update is nothing on which damned mac mini3,1 unsupportet Mac.

How easy it is but at Hackintosh .. since there are no problems and the Dev. Updates come immediately.

I'll throw the damned Mac mini3,1 soon in the corner.

Over and over again: no updates available .... it sucks !!! nothing works.

The seed branch has been on delay testing to make sure each update still follows the same protocol (doesn't apply to the production branch). Having a little patience can help a bit.

 

[pkouame]

The seed branch has been on delay testing to make sure each update still follows the same protocol (doesn't apply to the production branch). Having a little patience can help a bit.

Hey - was macOS_Sierra_Developer_Beta_Access_utility up for 10.12.1 beta1 ? Actually didn't notice Apple changed their distribution mechanism last week. Went direct through AUS. Caught me by surprise on beta2.
[doublepost=1475033239][/doublepost]

Now comes in Sierra, I have installed the 10.12.1 Beta1, Beta2 not to download.
I used the AUSenabler.app and tried the 2 different options .. still no update available.

SIP is disable and in Security is no restrictions

How to load the Developer Update Beta 2 for Sierra 10.12.1 one now?

So a circus, after each beta update is nothing on which damned mac mini3,1 unsupportet Mac.

How easy it is but at Hackintosh .. since there are no problems and the Dev. Updates come immediately.

I'll throw the damned Mac mini3,1 soon in the corner.

Over and over again: no updates available .... it sucks !!! nothing works.

Since you have a Hackintosh. Did u try downloading the update there and transferring to your Mac using some of the techniques on this thread?

 

[foxlet]

Hey - was macOS_Sierra_Developer_Beta_Access_utility up for 10.12.1 beta1 ? Actually didn't notice Apple changed their distribution mechanism last week. Went direct through AUS. Caught me by surprise on beta2.
[doublepost=1475033239][/doublepost]
Since you have a Hackintosh. Did u try downloading the update there and transferring to your Mac using some of the techniques on this thread?

As far as I'm aware, the utility existed for Beta 1 but only served to change catalogs to Apple's seed branch (Official and GM clean installs don't use the seed catalog by default). The AUS should already have Beta 2 live.

 

[pkouame]

Great! It's downloading now via App Store...
thx.

 

[nikhilc]

Heh. I hear ya. I picked this up to see if I can't find a fix for the trackpad preferences that people are missing.

This would be fantastic, I rolled back to El Cap on my MB5,2 because of this issue and a cursory glance at the kexts didn't seem to have simple fixes like deviceID fields to modify as the hackintosh folks seem to have done in the past.

 

[pkouame]

As far as I'm aware, the utility existed for Beta 1 but only served to change catalogs to Apple's seed branch (Official and GM clean installs don't use the seed catalog by default). The AUS should already have Beta 2 live.

Sierra 10.12.1 loaded on mbp 5,3 via AUS:

WARNING: this is a developer beta.

Enjoy.

 

[iModFrenzy]

Only if you notice issues; otherwise you should be fine without it.
[doublepost=1474983927][/doublepost]
Yeah, that WiFi card isn't supported either (didn't realize the Air card had a different Device ID). I *think* you can replace the card with the one from the 2009 White Unibody MacBook (model A1342). The connector is the same and it's electrically compatible, but I don't know if it'll actually mount inside the Air or if the antenna connectors will line up. In theory it should work, though.

Ah ah yeah I could replace the card. I can figure out the mounting. I'll do it.

Page 1 of this thread lists the results of a number of systems that have been tested. If yours is the MBA 2,1, then you have the BRCM4321 that a lot of us had (and isn't supported under Sierra).
You'll need to get a replacement wifi card with a newer BroadCom chipset.

Edit: Oops...see dosdude1 already replied (need to refresh more)
Edit2: One of the cards available on Amazon: https://www.amazon.com/BroadCom-BCM943224PCIEBT-BCM43224-Bluetooth-607-5952-B/dp/B00UL7B59C/

I actually used a MBA 2,1 wifi card to replace that card in a MBP once, good to know that they're compaitible.

Sorry for missing the first page, my bad

I'll definitely pick that up! Thanks!

 

[morooster]

My Mac Pro 3,1 is still chugging quite happily on Sierra, and so far, no problems. Unlocking with my watch even works. I haven't tested every possible app yet, but the ones I have seem to work fine. I *can* say, for those using virtualization software, that as far as I can tell, VMWare Fusion runs fine. I have a Linux VM that acts as a Windows PDC, and a couple of different Windows VMs, and all seem to operate perfectly fine. I do not have an iSight camera, though, so I don't know if Fusion would have the same issues as VirtualBox does with it or not.

And for those saying these machines are "nearing their end of life" ... I don't see how. Until I am no longer able to buy parts for them, they work fine. I may be restricted in what new stuff I can add, but that doesn't mean the old stuff suddenly ceases being useful. There's an ancient PowerPC Mac Pro at my work that still runs like a champ (now running linux doing server duties).

 

[seb.wagner]

A completely different question, if I may ask, @dosdude1? You wrote:

(...) SIP must be disabled for the modified kexts to be loaded.

(... re-enabling SIP) may cause issues while running Sierra on your unsupported machine.

What exactly could happen on a MacBook Pro 5,5 (13", mid 2009)? I'm asking because I generally like the idea of having the extra bit of security from active SIP. Therefore, I'd prefer having it turned on but I don't want to risk running into (so far: unspecified) problems with Sierra on my machine.

 

[dosdude1]

A completely different question, if I may ask, @dosdude1? You wrote:




What exactly could happen on a MacBook Pro 5,5 (13", mid 2009)? I'm asking because I generally like the idea of having the extra bit of security from active SIP. Therefore, I'd prefer having it turned on but I don't want to risk running into (so far: unspecified) problems with Sierra on my machine.

I personally see no benefit of SIP except to prevent those who don't know what they're doing from modifying system files and breaking the OS.

 

[seb.wagner]

I personally see no benefit of SIP except to prevent those who don't know what they're doing from modifying system files and breaking the OS.

Well, it's mostly the runtime protections that come with it. SIP's supposed to prevent code from being injected into applications, libraries into system binaries etc. I'd much rather have that safety system active than turned off. I will, of course, keep it off if that's needed to make Sierra run on my MacBook Pro. But if it's not necessary, then I'd like to reactivate it.

 

[pkouame]

My Mac Pro 3,1 is still chugging quite happily on Sierra, and so far, no problems. Unlocking with my watch even works. I haven't tested every possible app yet, but the ones I have seem to work fine. I *can* say, for those using virtualization software, that as far as I can tell, VMWare Fusion runs fine. I have a Linux VM that acts as a Windows PDC, and a couple of different Windows VMs, and all seem to operate perfectly fine. I do not have an iSight camera, though, so I don't know if Fusion would have the same issues as VirtualBox does with it or not.

And for those saying these machines are "nearing their end of life" ... I don't see how. Until I am no longer able to buy parts for them, they work fine. I may be restricted in what new stuff I can add, but that doesn't mean the old stuff suddenly ceases being useful. There's an ancient PowerPC Mac Pro at my work that still runs like a champ (now running linux doing server duties).

Indeed! Good news about Fusion. I think VirtualBox has some issues with Sierra. Had to uninstall to restore my iSight (and who knows what else). Also had lots of issues just installing windows 10 on vbox. May try linux or unbutu to see if that makes any difference. I think the cMPs are holding up fairly well, may even squeeze a few more years out of my pro 3,1, let's keep our fingers crossed.

 

[Pinarek]

finally came today this update the beta2 for 10.12.1 .. wonder why it has not already arrived yesterday, am yesterday soon become crazy. And I have not changed at AUSEnabler.app.

And as someone here wrote, the update from the Hackintosh just pull over on the Mac mini does not go. When I charge the Hackintosh the update it is to install in Library / update and that is a folder and 2 files. I've ever tried then copied to a USB stick and inserted in Macmini in the Library / Update and try to install, does not go. If the error message "lacks Components Setting, that this update can not be installed as a single update".

Let's see know it then works in Beta3.

 

[macsba]

Sierra 10.12.1 loaded on mbp 5,3 via AUS:

View attachment 660304
WARNING: this is a developer beta.

Enjoy.

Yay! This finally worked for me late last night. The AUS tool on a MBP 5,1 late 2008.

 

[fischersd]

Hmm. Someone said that El Cap was still available in MAS? I just took a look (want a complete set of the El Cap files to play with) and not seeing it there - is it just me or did they pull it?
(don't have it under purchases either).

Edit: n/m - found the link: https://support.apple.com/HT206886

 

[Yamcha]

My Mac Pro 3,1 is still chugging quite happily on Sierra, and so far, no problems. Unlocking with my watch even works. I haven't tested every possible app yet, but the ones I have seem to work fine. I *can* say, for those using virtualization software, that as far as I can tell, VMWare Fusion runs fine. I have a Linux VM that acts as a Windows PDC, and a couple of different Windows VMs, and all seem to operate perfectly fine. I do not have an iSight camera, though, so I don't know if Fusion would have the same issues as VirtualBox does with it or not.

And for those saying these machines are "nearing their end of life" ... I don't see how. Until I am no longer able to buy parts for them, they work fine. I may be restricted in what new stuff I can add, but that doesn't mean the old stuff suddenly ceases being useful. There's an ancient PowerPC Mac Pro at my work that still runs like a champ (now running linux doing server duties).

How did you manage to install Sierra? I've tried but my Mac Pro 3,1 but the installation just freezes and restarts after a couple minutes.. I followed the @dosdude1's guide..

Not sure If it's due to the Software Raid or another issue..

 

[harlleysathler]

Ok, so I follow dosdude1 advice and bought a WiFi/Bluetooth card from a Late 2009/Early 2010 MacBook to my Mac mini Early 2009. The dimensions of the card is very different as said before. It's about half of the size of the original and the holes are in different locations. So I cut a piece of hard plastic, same size as original card and made the three holes. Fixed the new card on this plastic piece with double sided tape, installed this assembly and reconnect the antennas and the flat cable. Everything works and now I will try it under Sierra.

It's not possible to fix the card on just one of the holes because the flat cable is a bit rigid and can't be mounted ahead of it's original position. The bluetooth antenna takes a little trouble but I could fix it.

 

[iModFrenzy]

Hmm. Someone said that El Cap was still available in MAS? I just took a look (want a complete set of the El Cap files to play with) and not seeing it there - is it just me or did they pull it?
(don't have it under purchases either).

Edit: n/m - found the link: https://support.apple.com/HT206886

I went through the process of getting dmgs,installer ESDs,etc just to come here to this link for a complete upgrade to El Cap from Snow Leopard which is what I needed

Thanks for this though, didn't think this existed haha