Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.12 Sierra Unsupported Macs Thread

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.
evertjr said:
Thank you for the fast response! How about other app updates from Mac App Store? Will also come from AUS server or this only apply for system updates?
Click to expand...

That's my server, actually. As noted before, Mac App Store transactions (those that require purchasing or activating Apps) run on StoreFoundation, and are handled by a different repository than SoftwareUpdate. AUSEnabler has nothing to do with it, and has no effect on it.

In terms of updates, AUSEnabler packages still come from Apple's own delivery network; only checks related to machine eligibility are changed by the custom server so that it shows up in the App Store's Update pane and the SoftwareUpdate daemon.
 
Last edited:
fischersd said:
Yep, it dropped at 1pm ET. If you've done the AUSenabler patch, it should just show up. (remember, Apple phases in availability of updates across apple ID's to try to even out the hit on the servers).

@dosdude1 - if you are going to update your tool, the dist file is 031-85264
Edit: Whoops...wrong one...sec. 031-84974 looks right.
If not, should just have post #1 pointing to foxlet's updater.

Hmm. Ok, there's a bunch that they updated today that are doing the same checks - just found another one under q/031-86699.

Yep, that's the one (031-86699) - it nets the 10.12.1 update.
Click to expand...

There's two versions of the 10.12.1 package, 031-86699 (production) and 031-86698 (marked for seed). Content-wise they are identical, but have different update procedures. This might or might not be a problem during updating.
 
fischersd said:
Yep, it dropped at 1pm ET. If you've done the AUSenabler patch, it should just show up. (remember, Apple phases in availability of updates across apple ID's to try to even out the hit on the servers).

@dosdude1 - if you are going to update your tool, the dist file is 031-85264
Edit: Whoops...wrong one...sec. 031-84974 looks right.
If not, should just have post #1 pointing to foxlet's updater.

Hmm. Ok, there's a bunch that they updated today that are doing the same checks - just found another one under q/031-86699.

Yep, that's the one (031-86699) - it nets the 10.12.1 update.
Click to expand...
I'm discontinuing that tool, as AUSEnabler is a much better solution.
 
foxlet said:
That's my server, actually. As noted before, Mac App Store transactions (those that require purchasing or activating Apps) run on StoreFoundation, and are handled by a different repository than SoftwareUpdate. AUSEnabler has nothing to do with it, and has no effect on it.

In terms of updates, AUSEnabler packages still come from Apple's own delivery network; only checks related to machine eligibility are changed by the custom server so that it shows up in the App Store's Update pane and the SoftwareUpdate daemon.
Click to expand...

Thank you very much for the response. I just updated to 10.12.1 using this method and it went perfectly. Thank you and @dosdude1 for working on this. Theres any place to donate to you guys?
 
evertjr said:
TI just updated to 10.12.1 using this method and it went perfectly.
Click to expand...
What hardware?

I'd suggest 10.12.1 updaters posting of success or failure be sure to please post machine model info so we can keep an accurate measure of any issues.

I'm looking at the 10.12.1 update on my macbookpro5,5, thanks to AUSEnabler, but not sure I want to be the guinea pig. @dosdude1, any words of wisdom on updating? Will we need to run a Post-Install after the update and before 10.12.1 boot from the Recovery Partition or USB in order to boot successfully?
 
Last edited:
I updated and am now at the unable to boot sign as the PlatformSupport.plist file is updated in this update.

Booting into installer to change this file again.
Pretty sad when we can update hacks with less effort.
 
ScooterComputer said:
What hardware?

I'd suggest 10.12.1 updaters posting of success or failure be sure to post machine model info so we can keep an accurate measure of any issues.

I'm looking at the 10.12.1 update on my macbookpro5,5, thanks to AUSEnabler, but not sure I want to be the guinea pig. @dosdude1, any words of wisdom on updating? Will we need to run a Post-Install after the update and before 10.12.1 boot from the Recovery Partition or USB in order to boot successfully?
Click to expand...
I don't see any reason not to. It should install fine with no issues, but worst comes to worst, all you'll need to do is run the post-install patch.
 
  • Like
Reactions: ScooterComputer
ScooterComputer said:
What hardware?

I'd suggest 10.12.1 updaters posting of success or failure be sure to post machine model info so we can keep an accurate measure of any issues.

I'm looking at the 10.12.1 update on my macbookpro5,5, thanks to AUSEnabler, but not sure I want to be the guinea pig. @dosdude1, any words of wisdom on updating? Will we need to run a Post-Install after the update and before 10.12.1 boot from the Recovery Partition or USB in order to boot successfully?
Click to expand...

I'm sorry I forgot to mention my hardware. Its a macbook pro 5,5 mid 2009. No issues so far.
 
  • Like
Reactions: ScooterComputer
evertjr said:
Thank you very much for the response. I just updated to 10.12.1 using this method and it went perfectly. Thank you and @dosdude1 for working on this. Theres any place to donate to you guys?
Click to expand...

At least for AUSEnabler and the AUS, there are no donations being taken at the moment. It's also an independent project unrelated to any patcher tools.
 
Last edited:
evertjr said:
Its a macbook pro 5,5 mid 2009. No issues so far.
Click to expand...
Even better to read!

And I must apologize, evertjr, I had put a "Please" in my first incarnation of that message, but then rewrote it to include the mention of dosdude1 and inadvertently left that "Please" out. My parents raised a better-mannered man than that. ;)
 
After update reboot, no keyboard/touchpad. Had to boot from USB and run post-install forced cache update. Everything fine after that (MacBookPro 5,2).
 
Am I the only one nervous about this whole process? Not to insult Foxlet as I and everyone else greatly appreciates the time put into the tool along with dosdude1, but this scenario is the exact thing not to install and do and very easy for any malicious software to be added to your machine. Do you guys have the source code posted anywhere on these tools?
 
cashxx said:
Am I the only one nervous about this whole process? Not to insult Foxlet as I and everyone else greatly appreciates the time put into the tool along with dosdude1, but this scenario is the exact thing not to install and do and very easy for any malicious software to be added to your machine. Do you guys have the source code posted anywhere on these tools?
Click to expand...
As far as I can tell, the downloaded and installed update is from Apple and exactly the size it should be.
 
Sedulous said:
After update reboot, no keyboard/touchpad. Had to boot from USB and run post-install forced cache update. Everything fine after that (MacBookPro 5,2).
Click to expand...

did you disabled SIP? I think this issue doesn't happen if have it disabled

cashxx said:
Am I the only one nervous about this whole process? Not to insult Foxlet as I and everyone else greatly appreciates the time put into the tool along with dosdude1, but this scenario is the exact thing not to install and do and very easy for any malicious software to be added to your machine. Do you guys have the source code posted anywhere on these tools?
Click to expand...

I had my doubts too but @dosdude1 and @foxlet quickly gave me responses and If you read a few pages back you'll se theses tools work in pretty clean way. Anyway, if you're too sensitive about security you shouldn't be using unsupported software in the first place.
 
cashxx said:
Am I the only one nervous about this whole process? Not to insult Foxlet as I and everyone else greatly appreciates the time put into the tool along with dosdude1, but this scenario is the exact thing not to install and do and very easy for any malicious software to be added to your machine. Do you guys have the source code posted anywhere on these tools?
Click to expand...

There is no public source code for the server side, but the catalog is uncompressed and the AUSEnabler tool's source can be seen (to take a look, just open it with Script Editor).
 
parrotgeek1 said:
ohhh, @dosdude1 kernelcache can't be a file, when you do the kextcache in the postinstall, you have to output it to prelinkedkernel
Click to expand...

Sorry so the output is incorrect? How should I fix this symlink error from prelinkedkernel to kernelcache?

symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache"
failed 17 (File exists) <createPrelinkedKernel 2795>

May this be the cause of loosing control of keyboard and touchpad after some reboots?

Thank you
 
Last edited:
The update showed up in MAS, I opened AUSEnabler.app, switched to AUS Production branch and ran the update.
It took 15-20 min to update and everything is working just fine. No issues, MacBook 5,2 (Mid 2009).

Thank you guys for great install/update tools.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back