Thanks Sedolous, that was the question but I read your last post about 10.12.3 update just when I was ready to try your fix. Hope you (or some other smart dude) can figure out a solution.
Got a tip for us?
Let us know
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
- Thread starter redheeler
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Me, too now; same process. And no problems with iTunes updates as described by others
Guys, I can't update any of my apps through the App Store. It hangs before eventually crashing. I'm on an early 2008 iMac. I've tried using AUSEnabler to change the catalog, but it has no effect. Have any of you experienced this problem, and how did you solve it? Thanks.
A question for dosdude1 (and perhaps Sedulous):
(First off, I'm sorry to go "lazy internet", since I'm pretty sure this has already been answered in the 170 pages of the thread. But I couldn't find the answer, so I figured I'd just ask.)
After the USB stick with the Sierra installer is created, and after the Pre-Install stuff is run against it, how does it differ from a bone-stock DiskMakerX install USB, particularly to do with what actually gets installed on the target Mac during the "normal" install process (as in, beyond the Post-Install Tool being copied to the installer stick)?
The reason I ask: I typically carry Mavericks and Sierra installer sticks around with me, to do upgrades on Macs for users; downloading 4+GB installers in my area of the woods isn't a quick process, so having the sticks are a time-saver. I'm hesitant to use the Sierra stick on Sierra-supported Macs if any deep OS internals are being changed (Hackintosh kexts being installed, etc), even if they –should not– cause problems, because if they –should– eventually cause problems (Apple decides to crack down, say) I'd be on the hook for redoing work to fix that. And some angry customers. OTOH, I'm pretty familiar with the Installer, not my first time at the rodeo, so to speak, helping users overcome Apple's false limitations. In previous projects we always worked to get the Installer to a point of "vanilla" as possible.
MY understanding, currently, is that you're just "fixing" the Installer volume to get it to boot on unsupported Macs, and then only modifying what hardware the Installer is willing to perform the install on… beyond that, after actual installation and reboot, the target volume is a "vanilla" Sierra install up until the Post-Install tool is run against it. Am I correct?
If I am correct, I'd suggest you add a blurb on the OP about that. There are a lot of us who carry consolidated installer drives, and knowing that the install generated is vanilla would be helpful. Without having to wade through 170 pages of thread. Thanks!
(First off, I'm sorry to go "lazy internet", since I'm pretty sure this has already been answered in the 170 pages of the thread. But I couldn't find the answer, so I figured I'd just ask.)
After the USB stick with the Sierra installer is created, and after the Pre-Install stuff is run against it, how does it differ from a bone-stock DiskMakerX install USB, particularly to do with what actually gets installed on the target Mac during the "normal" install process (as in, beyond the Post-Install Tool being copied to the installer stick)?
The reason I ask: I typically carry Mavericks and Sierra installer sticks around with me, to do upgrades on Macs for users; downloading 4+GB installers in my area of the woods isn't a quick process, so having the sticks are a time-saver. I'm hesitant to use the Sierra stick on Sierra-supported Macs if any deep OS internals are being changed (Hackintosh kexts being installed, etc), even if they –should not– cause problems, because if they –should– eventually cause problems (Apple decides to crack down, say) I'd be on the hook for redoing work to fix that. And some angry customers. OTOH, I'm pretty familiar with the Installer, not my first time at the rodeo, so to speak, helping users overcome Apple's false limitations. In previous projects we always worked to get the Installer to a point of "vanilla" as possible.
MY understanding, currently, is that you're just "fixing" the Installer volume to get it to boot on unsupported Macs, and then only modifying what hardware the Installer is willing to perform the install on… beyond that, after actual installation and reboot, the target volume is a "vanilla" Sierra install up until the Post-Install tool is run against it. Am I correct?
If I am correct, I'd suggest you add a blurb on the OP about that. There are a lot of us who carry consolidated installer drives, and knowing that the install generated is vanilla would be helpful. Without having to wade through 170 pages of thread. Thanks!
AUSenabler only change system software updates, not the regular app store feeds. What is non working exactly?
Maybe you installed the patch by me and enabled SIP? Check SIP!
[doublepost=1486053794][/doublepost]
Yes. Without the post install patch, it's a vanilla installation.
Can u check Console.app? Maybe some relevant messages can be spotted there when the beachball starting.
The only thing that looks relevant is this line, which the Console reports over and over, even when the App Store is not launched:
Feb 2 22:48:13 vpn com.apple.xpc.launchd[1] (com.apple.softwareupdated): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
The VPN reference is because I have Mac OS Server running on this machine.
Show me the outputs of the following terminal commands:
Code:
csrutil status
Code:
cat /System/Library/LaunchDaemons/com.apple.softwareupdated.plistSystem Integrity Protection status: disabled.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.apple.softwareupdated</string>
<key>ProgramArguments</key>
<array>
<string>/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated</string>
</array>
<key>UserName</key>
<string>_softwareupdate</string>
<key>EnablePressuredExit</key>
<true/>
<key>POSIXSpawnType</key>
<string>Adaptive</string>
<key>MachServices</key>
<dict>
<key>com.apple.softwareupdated</key>
<true/>
</dict>
<key>LaunchEvents</key>
<dict>
<key>com.apple.notifyd.matching</key>
<dict>
<key>ManualBackgroundTrigger</key>
<dict>
<key>Notification</key>
<string>com.apple.SoftwareUpdate.TriggerBackgroundCheck</string>
</dict>
<key>CheckForCatalogChange</key>
<dict>
<key>Notification</key>
<string>com.apple.SoftwareUpdate.CheckForCatalogChange</string>
</dict>
</dict>
<key>com.apple.xpc.activity</key>
<dict>
<key>com.apple.SoftwareUpdate.Activity</key>
<dict>
<key>Repeating</key>
<true/>
<key>Interval</key>
<integer>21600</integer>
<key>Priority</key>
<string>Maintenance</string>
<key>PowerNap</key>
<true/>
</dict>
</dict>
</dict>
<key>EnvironmentVariables</key>
<dict>
<!--Uncomment these keys to enable malloc debugging-->
<!--<key>MallocScribble</key>-->
<!--<string>1</string>-->
<!--<key>MallocStackLogging</key>-->
<!--<string>1</string>-->
<!--<key>MallocErrorAbort</key>-->
<!--<string>1</string>-->
<!--<key>MallocCheckHeapEach</key>-->
<!--<string>500</string>-->
<!--<key>MALLOC_LOG_FILE</key>-->
<!--<string>/var/log/softwareupdated_malloc.log</string>-->
<!--<key>DYLD_INSERT_LIBRARIES</key>-->
<!--<string>/usr/lib/libgmalloc.dylib</string>-->
<!--<key>NSZombieEnabled</key>-->
<!--<string>YES</string>-->
<key>DYLD_INSERT_LIBRARIES</key>
<string>/usr/local/lib/SUVMMFaker.dylib</string>
</dict>
</dict>
</plist>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.apple.softwareupdated</string>
<key>ProgramArguments</key>
<array>
<string>/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated</string>
</array>
<key>UserName</key>
<string>_softwareupdate</string>
<key>EnablePressuredExit</key>
<true/>
<key>POSIXSpawnType</key>
<string>Adaptive</string>
<key>MachServices</key>
<dict>
<key>com.apple.softwareupdated</key>
<true/>
</dict>
<key>LaunchEvents</key>
<dict>
<key>com.apple.notifyd.matching</key>
<dict>
<key>ManualBackgroundTrigger</key>
<dict>
<key>Notification</key>
<string>com.apple.SoftwareUpdate.TriggerBackgroundCheck</string>
</dict>
<key>CheckForCatalogChange</key>
<dict>
<key>Notification</key>
<string>com.apple.SoftwareUpdate.CheckForCatalogChange</string>
</dict>
</dict>
<key>com.apple.xpc.activity</key>
<dict>
<key>com.apple.SoftwareUpdate.Activity</key>
<dict>
<key>Repeating</key>
<true/>
<key>Interval</key>
<integer>21600</integer>
<key>Priority</key>
<string>Maintenance</string>
<key>PowerNap</key>
<true/>
</dict>
</dict>
</dict>
<key>EnvironmentVariables</key>
<dict>
<!--Uncomment these keys to enable malloc debugging-->
<!--<key>MallocScribble</key>-->
<!--<string>1</string>-->
<!--<key>MallocStackLogging</key>-->
<!--<string>1</string>-->
<!--<key>MallocErrorAbort</key>-->
<!--<string>1</string>-->
<!--<key>MallocCheckHeapEach</key>-->
<!--<string>500</string>-->
<!--<key>MALLOC_LOG_FILE</key>-->
<!--<string>/var/log/softwareupdated_malloc.log</string>-->
<!--<key>DYLD_INSERT_LIBRARIES</key>-->
<!--<string>/usr/lib/libgmalloc.dylib</string>-->
<!--<key>NSZombieEnabled</key>-->
<!--<string>YES</string>-->
<key>DYLD_INSERT_LIBRARIES</key>
<string>/usr/local/lib/SUVMMFaker.dylib</string>
</dict>
</dict>
</plist>
as root:
Code:
launchctl load /System/Library/LaunchDaemons/com.apple.softwareupdated.plistand after this, repeat the ps -ef line
please try again but replace load with unload, and then reply the load and ps lines.
So, it's seems to be loaded, but can't be run. Ok, more investigation:
Download this: https://www.dropbox.com/sh/96tg06ys1pyem8v/AAAw0Gc4nlxK2OmXn4zFG-H6a?dl=0 and unzip it. (check if it's in the Download/SUFaker directory in your home folder, if not you need to fine tune the following commands):
Code:
cd Downloads/SUFaker
/bin/bash test_dosdude.shOriginal:
szukseges malloc: 8
sysctl reply: iMac8,1
szukseges malloc: 179
sysctl reply: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 DTES64 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1
Patched:
szukseges malloc: 9
sysctl reply: iMac10,1
szukseges malloc: 4
sysctl reply: VMM
szukseges malloc: 8
sysctl reply: iMac8,1
szukseges malloc: 179
sysctl reply: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 DTES64 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1
Patched:
szukseges malloc: 9
sysctl reply: iMac10,1
szukseges malloc: 4
sysctl reply: VMM
Ok, so seems to me to the patch is workig. Try the following as root:
Code:
DYLD_INSERT_LIBRARIES=/usr/local/lib/SUVMMFaker.dylib "/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated"If you don't get back the prompt, try software update from App Store.
Thanks to everyone in the thread that made the upgrade to Sierra possible.
Wife's MacBookPro5,5 Mid 2009 running Sierra with updates no problem.
Wife's MacBookPro5,5 Mid 2009 running Sierra with updates no problem.
Last edited:
So I have seen this issue with others since i had it where the patcher says its not a valid copy of Sierra. Believe it or not the fix i found was to mount the DMG and copy the installer from the dmg. It wont recognize it until you copy it from the DMG to your mac. It doesn't explicitly state this anywhere and will save some of you a headache.
Which version did you have? 10.12.3? any of 10.12.4 developer or public beta? 10.12.2?
Currently i don't have any idea what is wrong with you. Or, if you have a working recovery, maybe you can try to wipe SIP configuration with "csrutil clear" then reboot to recovery again and run "csrutil disable" and try App Store.
Or maybe the debug log can help (close any app and windows except one terminal):
Code:
log stream --level=debugThis produces lot of line of logging information, and check the following things:
- launchctl unload then load
- launch app store, and try to install updates
Then you can disable the patch with commenting out the <key>DYLD_INSERT_LIBRARIES</key> and <string>/usr/local.....</string> line out? Commented lines are starting with <!-- and ends with --> (like the previous lines). After that launchctl unload/load and check App store.