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.
redheeler said:
macOS Sierra on unsupported Macs
View attachment 637083​
Introduction

For the first time since OS X 10.8 Mountain Lion in 2012, macOS 10.12 Sierra has changed the official minimum requirement to run it, leaving some 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)

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


Apple History

OS X 10.6 Snow Leopard was the first OS X version with optional support for a 64-bit kernel, allowing booting either with 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 from OS X, starting with OS X 10.8 Mountain Lion, EFI32 Macs no longer had an Apple-supported mechanism to boot newer OS X versions.
OS X 10.11 El Capitan includes System Intergrity Protection (Rootless security). It makes sure that System file permissions are automatically protected, and updated during Software Updates. The Repair Permissions function is no longer available and access to system files that we need to use in this thread may be locked.
Older Macs that lost support in macOS Sierra have an USB related issue that prevents the built-in USB as well as the thereon connected Input Devices and Bluetooth from working.

Models Tested:

View attachment 636161

The support for legacy Macs include iMac 5,1; MacBook 2,1 and MacBook 3,1 that could install Mountain Lion, Mavericks, Yosemite with MacPostFactor or OS X Extractor (in the spoiler below) have been dropped in OS X 10.11 El Capitain. Mac Pro 1,1 and 2,1, while able to update to El Capitan with the methods in the spoiler below, are currently not supported by macOS Sierra.

Current Development Files

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

PlatformSupport.plist / InstallableMachines.plist:
Download Zip

Quick Test Guide:

Using @dosdude1's patch tool:

1. Download the tool here.

2. Follow the instructions here: MacOS Sierra Patcher Tool for Unsupported Macs

Using @parrotgeek1's script:

1. Use a supported Mac to install the macOS Sierra beta onto a disk. This is easily done with a USB enclosure or a USB thumb drive for testing.

2. Plug the disk into a Mac and run @parrotgeek1's script. Select your Sierra drive as the target volume.

3. Replace the PlatformSupport.plist in /System/Library/CoreServices/ with the one attached to this post.

4. Plug your Sierra disk into an "Unsupported" Mac and boot it up as usual. Voila.


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
Click to expand...
Is there a way to download the public beta using an unsupported Mac? I have a Mac mini (Early 2009) with El Capitan, and it won't let me download even though it l
redheeler said:
macOS Sierra on unsupported Macs
View attachment 637083​
Introduction

For the first time since OS X 10.8 Mountain Lion in 2012, macOS 10.12 Sierra has changed the official minimum requirement to run it, leaving some 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)

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


Apple History

OS X 10.6 Snow Leopard was the first OS X version with optional support for a 64-bit kernel, allowing booting either with 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 from OS X, starting with OS X 10.8 Mountain Lion, EFI32 Macs no longer had an Apple-supported mechanism to boot newer OS X versions.
OS X 10.11 El Capitan includes System Intergrity Protection (Rootless security). It makes sure that System file permissions are automatically protected, and updated during Software Updates. The Repair Permissions function is no longer available and access to system files that we need to use in this thread may be locked.
Older Macs that lost support in macOS Sierra have an USB related issue that prevents the built-in USB as well as the thereon connected Input Devices and Bluetooth from working.

Models Tested:

View attachment 636161

The support for legacy Macs include iMac 5,1; MacBook 2,1 and MacBook 3,1 that could install Mountain Lion, Mavericks, Yosemite with MacPostFactor or OS X Extractor (in the spoiler below) have been dropped in OS X 10.11 El Capitain. Mac Pro 1,1 and 2,1, while able to update to El Capitan with the methods in the spoiler below, are currently not supported by macOS Sierra.

Current Development Files

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

PlatformSupport.plist / InstallableMachines.plist:
Download Zip

Quick Test Guide:

Using @dosdude1's patch tool:

1. Download the tool here.

2. Follow the instructions here: MacOS Sierra Patcher Tool for Unsupported Macs

Using @parrotgeek1's script:

1. Use a supported Mac to install the macOS Sierra beta onto a disk. This is easily done with a USB enclosure or a USB thumb drive for testing.

2. Plug the disk into a Mac and run @parrotgeek1's script. Select your Sierra drive as the target volume.

3. Replace the PlatformSupport.plist in /System/Library/CoreServices/ with the one attached to this post.

4. Plug your Sierra disk into an "Unsupported" Mac and boot it up as usual. Voila.


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
Click to expand...
Is there a way to download the public beta using an unsupported Mac? I have a Mac mini (Early 2009) with El Capitan, and it won't let me download even though it let me redeem the code to download. Thanks!
 
dsmith0429 said:
Is there a way to download the public beta using an unsupported Mac? I have a Mac mini (Early 2009) with El Capitan, and it won't let me download even though it l

Is there a way to download the public beta using an unsupported Mac? I have a Mac mini (Early 2009) with El Capitan, and it won't let me download even though it let me redeem the code to download. Thanks!
Click to expand...
PM me your email address and I can send you a link.
 
  • Like
Reactions: franmeri
Will the tool be updated or should we manually update the dist file with the above instructions?
 
Greetings everyone! On my mac mini 3,1 (early 2009) after updating to Public Beta 5, i've noticed the following:
1. On start up my Mail app doesn't automatically open (like on previous versions)
2. Screen saver kicks in after some time, although the setting is at Never (not happening in previous versions)
It looks like settings on system preferences won't stay-save! Anyone else faced this problem with PB5. Looks like
an macOS glitch? What do you think?

Thank you in advance.
 
foxlet said:
The PB5 update product code is 031-72285 according to my server. It will be synced in a little while.
Edit: Sync is complete.
Edit 2: The catalog is the same, anyone already subscribed to the original URL will get the new update listing automatically.
ccLzal1.png
Click to expand...
Works like a charm again. Thanks!
 
Hi guys, I've been away from this thread for a little while...I'm still on DP1 and have a mid-2009 MBP. I want to switch to the PB and from there be able to run future updates via the App Store. Can somebody here bring me up to speed on the best way to do this. I started reading the rest of this thread and think I have some idea but I want to be sure. Is there any upgrade path from the DP to the PB solely using over the air updates? Or do I first need to switch to the PB using Dosdude's patcher? There is also some file I need to edit in order to have updates show up in the App Store? Thanks
 
ac2334 said:
Hi guys, I've been away from this thread for a little while...I'm still on DP1 and have a mid-2009 MBP. I want to switch to the PB and from there be able to run future updates via the App Store. Can somebody here bring me up to speed on the best way to do this. I started reading the rest of this thread and think I have some idea but I want to be sure. Is there any upgrade path from the DP to the PB solely using over the air updates? Or do I first need to switch to the PB using Dosdude's patcher? There is also some file I need to edit in order to have updates show up in the App Store? Thanks
Click to expand...
In order to get the Public Beta, the best option would be to download a copy (I have it uploaded, just PM me your email address and I'll send you the link), and use the latest version of my patch tool to create a USB drive. Then, to install updates, you can use my Software Update Patch Tool, found here: http://dosdude1.com/sierraswupatch
 
  • Like
Reactions: NetFlyer
Patched using @dosdude1 tool to try to get PB5. No luck.

Switched all "return false" to "return true" and softwareupdate --list again, and the PB5 popped right up.

So there's definitely another check somewhere preventing Sierra from installing.
 
dlfgma said:
Patched using @dosdude1 tool to try to get PB5. No luck.

Switched all "return false" to "return true" and softwareupdate --list again, and the PB5 popped right up.

So there's definitely another check somewhere preventing Sierra from installing.
Click to expand...

I had the same and the same solution solved the problem
 
dosdude1 said:
Were you getting any error? Or did it say "Update patched successfully", but didn't show in the App Store?
Click to expand...

Sorry for jumping in the middle of the discussion but I just installed PB1 and wanted to update to PB5. Used your tool and got confirmation that it was successfully patched but it didn't appear in the App Store (tried to reload and also to restart). So I guess it is linked to what was described in the two posts above. Thanks for your help.
 
Dosdude1 thanks for the work you're doing.

Yesterday reading the post Filipe.esposito announcing the release of the PB5 giving the reference, I thought I'd update and something happened that I can not explain ......

After running a check on the "031-72285" folder in anticipation of manually make changes, I got the idea to turn on the "Patch" used to update to version PB4, surprise, I found myself in the dropdown menu updates versions "PB5 - PD5 - PD6".

I was somewhat surprised ...... I realized that the "Patch" had been made automatic for the choice of language and that each version upgrade requires a new "Patch" prepared especially ......

But this thing is normal is an expected thing ....... or is a thing that happened by chance ... ..

However I upgraded to PB5 no problems .......

**Sorry for complete info.... I got "Update patched successfully", I have show in the App Store.
never problem for download and upgrade.....***


Followed for your information a brief report in which conditions are on my
MacBook Pro 13"(mid 2009).

I am trying in a rather critical condition, 2GB of RAM, the OS Sierra ver.PB5
installed on an external HD, ram use (safari, realplayer, email, two app. fan / temperature monitoring and ram usage) by approximately 56-70% (currently I'm picking up 56-58 ° C ram use about 70%), the boot is about 35-40 sec ..

Conditions beyond belief ..... during the verifications with the "Patch" installation (used 2.6) and those to update the various versions, I noticed an improvement in hardware performance after installation of PB4.

The only things where I acted is replaced to continuous crash at startup, the files "PrelinkedKernels & PatformSupport" using those of "El Capitan", not being a computer systems analyst, but an electronic hardware.

I know something as regards computing for work and need a hobby level, trying to replace the "PrelinkedKernel" file with the ones available (previous versions of OS-X) I managed to solve the problem
https://imageshack.com/i/plWFq3Yqp

I apologize for the slowness, I wanted to inform you that, even in the limit of the conditions hardware capabilities, the s.o works pretty well without too many problems ........(Some colored pinwheel above the 90% ram usage) globally acceptable….

Thank you
a.freemason
 
Last edited:
dosdude1 said:
Were you getting any error? Or did it say "Update patched successfully", but didn't show in the App Store?
Click to expand...

Nah, softwareupdate --list just refused to show the update until I made the return changes. After which it popped right now.
 
fischersd said:
@dlfgma, @dosdude1 - that's "the rub". We likely should have not upgraded and determined which condition was being "fixed" by forcing its return code to true (there's what, about a dozen of them?)
Click to expand...
It's the Machine ID and Board ID check, both of which my tool should bypass. I may change the method that's done a little bit and release an update to the tool.
[doublepost=1471478350][/doublepost]Ok, I figured out what the issue is. When refreshing updates, it deletes the entire "..SUCatalogDataManager" directory, and rebuilds it, erasing the patched file. Going to figure out a way to prevent this and update the tool.
 
dosdude1 said:
It's the Machine ID and Board ID check, both of which my tool should bypass. I may change the method that's done a little bit and release an update to the tool.
[doublepost=1471478350][/doublepost]Ok, I figured out what the issue is. When refreshing updates, it deletes the entire "..SUCatalogDataManager" directory, and rebuilds it, erasing the patched file. Going to figure out a way to prevent this and update the tool.
Click to expand...
Are you sure about that? I edited the .dist file manually, but didn't get the update available until I changed all the return codes to true. (I didn't use the tool)
 
fischersd said:
Are you sure about that? I edited the .dist file manually, but didn't get the update available until I changed all the return codes to true. (I didn't use the tool)
Click to expand...
Yeah, do this: Run "sudo softwareupdate --list" two times in a row, and I guarantee the update will no longer appear. It seems to only do this every other time it's run.
 
dosdude1 said:
Yeah, do this: Run "sudo softwareupdate --list" two times in a row, and I guarantee the update will no longer appear. It seems to only do this every other time it's run.
Click to expand...

Heh. Can't test it now...not unless I want to format the drive and start over with PB1. :)

I had rebooted a couple of times, still the update didn't show up. Then changed all the checks to return true and it showed up a couple minutes later. Now, I thought you said in one of your posts that you were also changing one of the checks to true in your tool, no? The VMM check?

After I did the PB5 update, I put the original .dist file back, so the update wouldn't show up in software updates anymore.
 
Last edited:
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