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.
I also struggled with this NSURLErrorDomain Error -1100, however a quite simple solution is given on dosdude1 his site:

Open terminal and run: sudo softwareupdate --clear-catalog

Run the script that can be downloaded here.

Updates will be found normally.
 
Last edited:
I'm having problems getting this to work on my Mac Pro 3,1 (running 10.12.5, patched dosdude version). Had no problems updating so far through the app store, 10.12.6 however, is not showing up.

1. Tried the script: failed due to insufficient right (I think because SIP is enabled – can't boot to recovery because of unsupported/non-efi graphic card). So I booted to my secondary harddrive and was able to run the script and modify the LauncherDaemon on my primary harddrive. However, the App Store still shows no updates.
2. I tried AUSenabler but still nothing shows up inside the app store (tried all channels).
3. Downloaded the Comboupdate. Installing it without modifying the Distribution will of course quit right away like this:

(Software not supported by your system)
bildschirmfoto2017-08-01um23.0.png


However...even after modifying the Distribution file by adding my board (Mac-F42C88C8) and removing my model from the unsupported list, I get an error.

I can start the installation, however, it notifies me with:

This package is not compatible with your version of macOS and may fail...try anyway?

bildschirmfoto2017-08-01um23.1.png


If I continue, it seems to actually run through but then fails with an error message.

bildschirmfoto2017-08-01um23.2.png


Any ideas? :-(
 
You probably have SIP enabled. Disable it and it will fly past that error. Worked for me.
(I have the same mac pro upgrading from 10.12.5 and got the same message. Ignoring the error doesn't work...)

NOTE: I had to re-boot with an old OS on a stick in Terminal to disable SIP since my recovery partition wasn't working : "csrutil disable" and reboot.
While you're at it, modify the platform plist on your recovery partition (make sure you mount the right volume!)

Good luck.
 
You probably have SIP enabled. Disable it and it will fly past that error. Worked for me.
(I have the same mac pro upgrading from 10.12.5 and got the same message. Ignoring the error doesn't work...)

NOTE: I had to re-boot with an old OS on a stick in Terminal to disable SIP since my recovery partition wasn't working : "csrutil disable" and reboot.
While you're at it, modify the platform plist on your recovery partition (make sure you mount the right volume!)

Good luck.

Thank you very much for pointing me into the right direction. After disabling SIP, I was able to install as you mentioned.

:)

sys.png


Thank you also for the hint about the platform plist, so I got my recovery partition working again as well.

By the way: if you have a full backup of your system disk available, you can use this instead of the USB stick. Just boot into it, use diskutil to check where the recovery partition of your (primary) disk resides, mount it, modify the file and reboot with primary disk. Seems obvious, but sometimes you overlook the simple things. ;)

Edit: also, after disabling SIP, I was also able to run the swupatch.sh script without errors. However, app store never showed any updates (seed or apple production catalog), so I used the modified combo update.

Edit2: booting into recovery partition does indeed work with my non-supported graphics card as well. Once it's loaded, you will see it, just like OSX you simply won't see anything in boot. I just didn't reach that point because I got the "not allowed icon", where my graphic card is not showing anything. Just wanted to clarify this as it's easy to get into this situation with a mac pro and a non-standard graphics card.
 
Last edited:
macOS Sierra on unsupported Macs
View attachment 637083
Introduction

For the first time since OS X Mountain Lion (10.8) in 2012, macOS Sierra (10.12) has changed the official minimum requirements needed for installation, leaving many older (but still perfectly capable) Macs behind.

  • MacBook (late 2009 or later)
  • iMac (late 2009 or later)
  • MacBook Air (2010 or later)
  • MacBook Pro (2010 or later)
  • Mac mini (2010 or later)
  • Mac Pro (2010 or later)

This is a thread for people to discuss and offer solutions for newly unsupported Macs in macOS Sierra. This post will be updated with solutions as they become available.

macOS History

OS X Snow Leopard (10.6) was the first version of OS X with support for 64-bit kernels, allowing booting with either a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely in OS X Mountain Lion (10.8), EFI32 Macs no longer had an Apple-supported mechanism to boot newer versions of OS X.

OS X El Capitan (10.11) includes SIP (System Integrity Protection/Rootless). It makes sure that system files and their permissions are automatically protected, and also updated during Software Updates. The Repair Permissions function is no longer available and access to system files that need to be changed may require disabling it.

Known Issues:
  • macOS Sierra dropped support for Wi-Fi cards (BCM4321) used in most 2008 and some 2009 Macs. A hardware upgrade is required to get Wi-Fi functionality on those models.
  • iMac8,1 - Volume control for the Built-In Audio device may work improperly or not at all.
  • Macbook5,2 - The trackpad is not configurable, it is detected as a regular mouse instead.
Models Tested:

kb3QFjw.png


Older Legacy Macs not in this table (including the MacBook2,1, MacBook3,1 and iMac5,1) can install Mountain Lion (10.8), Mavericks (10.9), and Yosemite (10.10) with MacPostFactor or OS X Extractor (noted in the spoiler below), but are not supported by OS X El Capitan (10.11) or later.

MacPro1,1 and 2,1 can run OS X El Capitan with the methods noted in the spoiler below, but are currently not supported by macOS Sierra due to a lack of SSE 4 support (the CPU can be upgraded but its firmware does not support newer SSE 4-compatible CPUs).

Legacy Development Files:

Kexts:
Legacy USB Injector Kext
OS X Extractor - Beta USB Kexts.zip (depreciated)

PlatformSupport.plist / InstallableMachines.plist:
Download Zip


Known Patching Methods (the important bit):
Automatic tools that can be used to install macOS Sierra onto an unsupported Mac.

Using @dosdude1's Patcher Tool:
Main Page/Instructions: MacOS Sierra Patcher Tool for Unsupported Macs
Download: [Direct Download]


Enabling Updates:
Sierra does not allow updating to minor versions (such as 10.12.1) without modification.

Using @foxlet's AUSEnabler:
Main Page: AUSEnabler - FurCode
Download: [Direct Download]

Using dylib injection to fake out system checks (@Czo patch). Download script and execute
Download: https://gist.github.com/anonymous/5129cdb72d19a5eee68383c88082bd43
Download: http://dosdude1.com/sierra/swupatch.sh.zip
Source: https://www.dropbox.com/sh/96tg06ys1pyem8v/AAAw0Gc4nlxK2OmXn4zFG-H6a?dl=0

Other OS patching threads:

macOS Sierra (10.12)
2006/2007 Mac Pro (1,1/2,1) and macOS Sierra - Mr. Zarniwoop

OS X El Capitan (10.11)
OS X El Capitan on Unsupported Macs - TMRJIJ
2006/2007 Mac Pro (1,1/2,1) and El Capitan - Mr. Zarniwoop


OS X Yosemite (10.10)
OS X Yosemite on Unsupported Macs - TMRJIJ
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite - Mr. Zarniwoop

OS X Mavericks (10.9)
[Guide] Installing 10.9 Mavericks on older Macs. - HackerWayne
Mac Pro 2,1 and OS X Mavericks - 5050

OS X Mountain Lion (10.8)
Success! Install 10.8 on old unsupported Mac - HackerWayne
[doublepost=1501717493][/doublepost]I have an early 2008 17" macbook pro 4,1. Just install 10.12.6. Everything seems to work well except the brightness do not work. Anyone else had this problem?
 
I also struggled with this NSURLErrorDomain Error -1100, however a quite simple solution is given on dosdude1 his site:

Open terminal and run: sudo softwareupdate --clear-catalog

Run the script that can be downloaded here.

Updates will be found normally.

Thank you kyeldo that Terminal command removed the error message.
 
Thank you very much for pointing me into the right direction. After disabling SIP, I was able to install as you mentioned.

:)

sys.png


Thank you also for the hint about the platform plist, so I got my recovery partition working again as well.

By the way: if you have a full backup of your system disk available, you can use this instead of the USB stick. Just boot into it, use diskutil to check where the recovery partition of your (primary) disk resides, mount it, modify the file and reboot with primary disk. Seems obvious, but sometimes you overlook the simple things. ;)

Edit: also, after disabling SIP, I was also able to run the swupatch.sh script without errors. However, app store never showed any updates (seed or apple production catalog), so I used the modified combo update.

Edit2: booting into recovery partition does indeed work with my non-supported graphics card as well. Once it's loaded, you will see it, just like OSX you simply won't see anything in boot. I just didn't reach that point because I got the "not allowed icon", where my graphic card is not showing anything. Just wanted to clarify this as it's easy to get into this situation with a mac pro and a non-standard graphics card.

Great! Our old workhorses are standing up pretty well. HS has quite a few performance fixes that may help us squeeze more cycles out of our old Xeons! We're probably a year away from new pros, so 10.13 will be the last OS on my box. You can switch to 10.13 Unsupported to keep up...Good luck.
 
[doublepost=1501717493][/doublepost]I have an early 2008 17" macbook pro 4,1. Just install 10.12.6. Everything seems to work well except the brightness do not work. Anyone else had this problem?
Yes, macbook early 2009. 10.12.6 installed fine with dosdude patch. Laptop screen brightness low and no response from system when trying to brighten. Also connected to HDMI external monitor. This works good but brightness seems to be locked at ok bright level. Also occasional delay to connect to external resuming from sleep mode.
 
So I'm going to be installing a New Battery in my 2009 MBP 13" pretty soon, I know this will require me to re-disable SID but will I be able to boot into the recovery partition to do so even after replacing the battery? Thanks.
 
Last edited:
I just finished installing Sierra 10.12.5 to my late 2008 MacBook Pro (5,1) previously I was using the latest El Capitan, but I'm experiencing an App Store hang whenever I click "Store" from the top menu and installing/updating apps always indicates "a minute remaining" and does nothing. I believe the issue is similar to that of @jrwil and @Czo from February, but his issue was never resolved. Everything else seems to be working just fine so far.

Any thoughts?

SIP is disabled. When I try to run "softwareupdate -l" in Terminal it never finishes. Something I found in the Console log that could be related(?). Tried rebooting several times. Should I try to reapply the USB patch again?

Process: softwareupdated [4985]
Path: /System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated
Identifier: softwareupdated
Version: 977.5
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: softwareupdated [4985]
User ID: 200

Date/Time: 2017-08-07 22:59:33.892 -0700
OS Version: Mac OS X 10.12.5 (16F73)
Report Version: 12
Anonymous UUID: 17E53B66-4DA6-C226-3EBF-8C27A264EAA0


Time Awake Since Boot: 12000 seconds

System Integrity Protection: disabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: DYLD, [0x9] <unknown>

Application Specific Information:
dyld: launch, loading dependent libraries
DYLD_INSERT_LIBRARIES=/usr/local/lib/SUVMMFaker.dylib

Dyld Error Message:
could not load inserted library '/usr/local/lib/SUVMMFaker.dylib' because no suitable image found. Did find:
/usr/local/lib/SUVMMFaker.dylib: stat() failed with errno=13

Binary Images:
0x1057fe000 - 0x1057fffff softwareupdated (977.5) <73030CB2-A818-3A18-A4F5-48A2B543CAEC> /System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated
0x1090f1000 - 0x10912edc7 dyld (433.5) <322C06B7-8878-311D-888C-C8FD2CA96FF3> /usr/lib/dyld

EDIT: I tried to run the post install patcher again with Force Cache Rebuild with no luck. When running the requested commands upon rebooting with Force, this was my console output:

sudo kextcache -system-prelinked-kernel
String/URL conversion failure.
KernelCache ID: C276E1E928C344DE78F2BCF143D06275
String/URL conversion failure.

EDIT2: I can see SUVMMFaker.dylib in the proper location and load/unload it, but I'm really not sure what is going wrong. :( Is there any other way to update once high sierra comes out for example?

Really appreciate the help, fellas.
 
Last edited:
A1342 combo card coax connector is slightly different than the ones on Mac Mini 3,1. It is taller and the groove for the latching/click onto securely is lower (Thus doesn't click and easily disconnects). Diameters are the same (both 2mm outer).

I had no problems with 2 early 2009 Mac Mini. However, 2 late 2009 Mac Mini's antenna coax connector can't really grab securely onto the A1342 connectors. So it appears while early 2009 Mac Mini's antenna coax connector is slightly different than late 09 Minis.

See pics below. The shorter connector is on the 09 Mac Mini combo board and the taller connector is from A1342 with Apple part number 607-7153-A (607-5952A and 607-6503A are the same).

I even tried soldering (with a high quality Hakko soldering iron+pointy tip) but the fit is so poor and wasn't successful.

Here is my post on successful early 09 Mini install for reference macOS 10.12 Sierra Unsupported Macs Thread

DSCN3329.JPG
DSCN3328.JPG
 
Last edited:
Can I make a stick from the 10.12.6 installer? If not possible, what's the latest recommended version to go with?
 
Last edited:
I followed the instruction on Page 194 to modify the package.

When I run modified.pkg I get a javascript error.
[doublepost=1502486546][/doublepost]
I followed the instruction on Page 194 to modify the package.

When I run modified.pkg I get a javascript error.

OK, found the issue, on the the Board ID line, I had to remove everything except Mac-F42C88C8
 
Hi,

Does anybody know if multitouch trackpad modification on macbook white mid 2009 non-unibody still works on el capitan/sierra/high sierra using unsupported mac installation? Do you still see multitouch option on trackpad preference? Want to modify my trackpad, to see if I can use 2 finger tap right click, pinch to zoom etc. Wondering if I did this modification it will work to have multitouch? Thanks.
 
Mac Pro 2008 updated macOS 10.12.6 via App Store.
No problems..

How did you do it, mate? Please share, I'm using a Mac Pro 2008 too, and AUSenabler says there are no updates at the moment. :(
[doublepost=1502728920][/doublepost]
Growing impatient waiting for the 10.12.6 upgrade to show up in the AUSEnabler catalog.
After reading the post above by "virk" I decided to give the upgrade a shot.
MacPro3,1 running Sierra 10.12.5., installed using dosdudes patch.
After making sure I had 2 working cloned backups I downloaded the 10.12.6 upgrade from the Apple App store and let it install.
Once the install finished the system booted up to 10.12.6 Hi-Sierra and much to my surprise appeared to run normally.
As a "just-in-case" I rebooted from the USB pen drive and re-did the post-install patches.
Much appreciation to the folks that make and maintain the hacks and patches that make all this possible.:)

View attachment 709342

How did you do it, mate? Please share, I'm using a Mac Pro 2008 too, and AUSenabler says there are no updates at the moment. :(
 
Hi guys, so I have decided to reformat and go back to El Capitan before selling my MBP (mid 2009).

I re-enabled SIP from the command line, wiped the drive and installed a fresh copy of El Capitan from a USB stick. However I find that the trackpad doesn't register clicks anymore. I can move the cursor around but can't click or double click anything.

Has anyone else run into this issue going back to El Capitan, or know of what the issue might be? I can't really sell a MBP without a properly functioning trackpad!

Is there a proper way to 'remove' a patched installation so everything goes back to standard?

Cheers
 
Last edited:
Hi folks,

I patched my 2009 MBP months ago and everything was working fine until recently, where there's only ever one app showing with an update in the App Store, and when I click Update, the App Store just hangs.

I've tried the various fixes in this thread, running the various scripts, deleting caches, etc. but no luck.

Any ideas where to go next?

thanks!
 
Yes, macbook early 2009. 10.12.6 installed fine with dosdude patch. Laptop screen brightness low and no response from system when trying to brighten. Also connected to HDMI external monitor. This works good but brightness seems to be locked at ok bright level. Also occasional delay to connect to external resuming from sleep mode.

I've also run into the brightness issue on three different iMac 9,1 (20" from Early 2009) models in recent weeks. The computer won't respond to brightness changes either from the keyboard or from the Display system preference.
 
I've also run into the brightness issue on three different iMac 9,1 (20" from Early 2009) models in recent weeks. The computer won't respond to brightness changes either from the keyboard or from the Display system preference.

Brightness Slider is decent app for overcoming this, I used it on my 5,2
 
Hello to all,
i wanted to install sierra on my imac 9.1. I followed the dosdude's instructions to create the installer from usb. The procedure is fine, but when I boot from the usb drive, the prohibition symbol appears and can not proceed with the installation. Where did I go wrong?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.