macOS High Sierra (10.13) Unsupported Macs Thread

[datanutz]

macOS High Sierra on Unsupported Macs​

For the first time since OS X Mountain Lion (10.8) in 2012, macOS Sierra (10.12) changed the official minimum requirements needed for installation, leaving many older (but still perfectly capable) Macs behind. Now macOS High Sierra (10.13) brings a new set of updates, and older Macs that can possibly run them.

Spoiler: macOS High Sierra Official Minimum Requirements

• 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)

Note this space!

Preliminary Tested Models List:

MacBookPro5,5 (13-inch Mid 2009) - No issues
MacBookPro5,4 (15-inch Mid 2009) - No issues
MacBookPro5,3 (15-inch Mid 2009) - No issues
MacBookPro5,1 (15-inch Late 2008) - No issues
MacBook5,1 (13-inch Unibody Aluminum Late 2008) - No issues

MacPro3,1 (Early 2008) - No issues

iMac7,1 (Mid 2007 W/BCM94360CAX and SSE4 supported T9300) - Screen brightness not controllable (NightShift works with modified CoreBrightness.frameworks)

iMac9,1 (Early 2009) - Missing Screen Brightness Controls (buttons don't work either)

MacBook5,2 (Early [Mid] 2009 MacBook) - Screen brightness not controllable (buttons don't work either), volume buttons do not work, same trackpad detected as USB mouse issue

Xserve2,1 (Early 2008) - graphics are unaccelerated with the original ATI X1300 unless an upgraded graphics card e.g. Nvidia GT 120 (from a Mac Pro) is installed

Known Patching Methods:
Automatic tools that can be used to install macOS High Sierra onto an unsupported Mac.

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

[doublepost=1512329227][/doublepost]Thanks very much Dosdude, I have a MBP 5,1 and high sierra works great. I only have 2 small issues. I had to use labtick because my keyboard dimmer didn't work and my screen brightness is maxed and I can't change it. Every time I use the hot keys, the screen brightness status bar responds to commands, but the back light remains constant. I tried in preferences, but no mater where you adjust it, the bar moves to the right. Do I need to apply the patch a few more times? Other than that, it installed without a hitch. Great work!

 

[dosdude1]

[doublepost=1512329227][/doublepost]Thanks very much Dosdude, I have a MBP 5,1 and high sierra works great. I only have 2 small issues. I had to use labtick because my keyboard dimmer didn't work and my screen brightness is maxed and I can't change it. Every time I use the hot keys, the screen brightness status bar responds to commands, but the back light remains constant. I tried in preferences, but no mater where you adjust it, the bar moves to the right. Do I need to apply the patch a few more times? Other than that, it installed without a hitch. Great work!

Try applying the backlight control patch in the post-install tool. It is not installed by default on that model, as most don't need it, but it should get brightness control working on yours.

 

[datanutz]

Try applying the backlight control patch in the post-install tool. It is not installed by default on that model, as most don't need it, but it should get brightness control working on yours.

[doublepost=1512331676][/doublepost]Thanks for the quick reply, but after patching it twice, it didn't change anything. I can live with it, this machine is going to my in-laws. I don't think they would even try to adjust the brightness anyway.

 

[sejm]

[doublepost=1512331676][/doublepost]Thanks for the quick reply, but after patching it twice, it didn't change anything. I can live with it, this machine is going to my in-laws. I don't think they would even try to adjust the brightness anyway.

I don't know at all if this is your issue, but I've found on my MBP 5,2 (which doesn't need the backlight patch) that accidentally installing the patch caused the symptoms you describe. Constant max brightness, keyboard brightness keys that trigger the screen brightness overlay graphic, but don't actually adjust the brightness. I had to reinstall the three kexts that the patch swapped out, update the kernel cache, and remove the patch listing from the list of installed patches.

The patch installer saved a backup of the 3 original "files" (actually, packages; 2 kexts, and one framework) in a Bklt_Backup folder in your home directory. The kext's go back in /System/Library/Extensions/; the framework goes in /System/Library/PrivateFrameworks/. You can update the kextcache with "sudo touch /System/Library/Extensions && sudo kextcache -u /" (without quotes, of course.) And then, I edited "/Library/Application Support/High Sierra Patcher/installedPatches.plist" to remove the five lines associated with the Backlight Patch, from <key> to </dict>. Finally, a reboot finishes the job.

 

[dosdude1]

I don't know at all if this is your issue, but I've found on my MBP 5,2 (which doesn't need the backlight patch) that accidentally installing the patch caused the symptoms you describe. Constant max brightness, keyboard brightness keys that trigger the screen brightness overlay graphic, but don't actually adjust the brightness. I had to reinstall the three kexts that the patch swapped out, update the kernel cache, and remove the patch listing from the list of installed patches.

The patch installer saved a backup of the 3 original "files" (actually, packages; 2 kexts, and one framework) in a Bklt_Backup folder in your home directory. The kext's go back in /System/Library/Extensions/; the framework goes in /System/Library/PrivateFrameworks/. You can update the kextcache with "sudo touch /System/Library/Extensions && sudo kextcache -u /" (without quotes, of course.) And then, I edited "/Library/Application Support/High Sierra Patcher/installedPatches.plist" to remove the five lines associated with the Backlight Patch, from <key> to </dict>. Finally, a reboot finishes the job.

Also, I have a script here that will restore original files for you.

 

[rkrumwiede]

Has anyone tried the new Nvidia web driver or is everyone sticking to the OEM Apple driver for GTX 680 andvequivalent cards? @dosdude1 recommendations?

Thank you

 

[dosdude1]

Has anyone tried the new Nvidia web driver or is everyone sticking to the OEM Apple driver for GTX 680 andvequivalent cards? @dosdude1 recommendations?

Thank you

nVidia web driver works great. A friend of mine who's running HS on his Mac Pro 3,1 has a GTX 1050Ti installed (no boot screen, of course. He keeps a flashed 8800GT around in case he needs to re-run the post-install patch), and has no issues.

 

[Blackriton]

Has anyone tried the new Nvidia web driver or is everyone sticking to the OEM Apple driver for GTX 680 andvequivalent cards? @dosdude1 recommendations?

Thank you

I am using a MacPro 3,1 under HS with a GTX 680 Card. I didn't install the Nvidia web drivers and stood on the OEM apple ones. No issues till now. Everything is working well.

 

[mumux]

I created a new USB boot drive the other day w/ patcher v2.5 for my MacPro3,1 and it boots fine.

Thank you gages,
I tried with version 2.5 instead of the latest 2.5.1 and it worked fine. It seems that 2.5.1 has an issue with MacPro 3,1 because it didn't recognise it as supported machine.

BTW I have a Radeon R9 280x and I had to patch the AMD drivers to make it work even if the patcher warned me about not having detected a 7xxx card!

 

[hvdb]

Using @dosdude1's Patcher Tool:
Main Page/Instructions: macOS High Sierra Patcher Tool for Unsupported Macs
Download: [Direct Download][/QUOTE]
[doublepost=1512408900][/doublepost]Hi, I've tried this method but I failed. My 2009 Macbook Pro can't see my created usb as a bootable disk, it's not shown when I boot with option key. It does work when I try it on a newer MBP with High Sierra already installed. So I think the created usb should be good. Do I have to change something in my settings? Filevault is disabled.

Thanks.

 

[sumer]

Hi,
Do you need to re-patch after you apply the security update?
Thanks

 

[Guy Clark]

Guy,
I am thinking about upgrading my iMac 24" 8,1 (Early 2008) with 4GB's RAM and the 3.06 GHz Core 2 Duo CPU,
to High Sierra. It is currently on El Capitan.

I have actually already done (3) 2009 Mac Mini's Plus changed the Wifi Card in the three.
AND all three now have SSD's & 8GB's RAM, which make them run buttery smooth.

Super Thanks to Dosdude1 and everyone who provided input, feedback and resources, Of Course!!!

I was just looking for some actual feedback from a 2008 iMac 24" owner about their experience Post the upgrade.

The thing with those, is the RAM is typically ONLY 4GB's, though they can be upgraded to 6GB's

Mine is a 2008 iMac Early 24" with 4GB's RAM and the 3.06 GHz Core 2 Duo CPU. No Plans to change the drive to SSD.

which is why I seek answers to:

Does it have 4GB's RAM or 6GB's?
Does it have an SSD or the stock hard drive?
Did you change the WiFi card or are you tethering to ethernet?
(for this one, I am actually planning on ethernet to Airport Express, for Wifi)

Looking forward to these specific answers and anything else you might share, so I can decide.
Thank you

The current configuration on my iMac 24" 8,1 is 4GB RAM, 3.06GHz Core 2 Duo CPU and a 1TB Seagate Hybrid SSHD

As for the Wifi Card I was fortunate enough to have a spare Late 2009 iMac card available so I swapped it for the existing one. The stock Wifi Card on the iMac 8,1 does not work with High Sierra (at least in my case). Ethernet will work fine.

See full details of any known issues here
http://dosdude1.com/highsierra/

I thoroughly recommend making a Time Machine Backup prior to attempting the hack.

That being said following the tutorial below for me the installation went smoothly.

dosdude1 Install macOS High Sierra on an Unsupported Mac

 

[Guy Clark]

Hi,
Do you need to re-patch after you apply the security update?
Thanks

Applied the security update to my iMac 8,1 24" Early 2008 without any issues.
[doublepost=1512423166][/doublepost]

Thank you gages,
I tried with version 2.5 instead of the latest 2.5.1 and it worked fine. It seems that 2.5.1 has an issue with MacPro 3,1 because it didn't recognise it as supported machine.

BTW I have a Radeon R9 280x and I had to patch the AMD drivers to make it work even if the patcher warned me about not having detected a 7xxx card!

A list of supported machines using the patch is listed below including issues which may arise
http://dosdude1.com/highsierra/

 

[w1z]

Thank you gages,
I tried with version 2.5 instead of the latest 2.5.1 and it worked fine. It seems that 2.5.1 has an issue with MacPro 3,1 because it didn't recognise it as supported machine.

BTW I have a Radeon R9 280x and I had to patch the AMD drivers to make it work even if the patcher warned me about not having detected a 7xxx card!

Confirmed! Happened with me today while reinstalling HS on my 3,1 using v2.5.1 ... Reverted back to using v2.5 and all is well.

@dosdude1 appreciate if you could squash this bug.

 

[dosdude1]

Confirmed! Happened with me today while reinstalling HS on my 3,1 using v2.5.1 ... Reverted back to using v2.5 and all is well.

@dosdude1 appreciate if you could squash this bug.

What exactly is happening? The only change I made in that version was fixing compatibility with OS X 10.6 and 10.7.

 

[hvdb]

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

[doublepost=1512408900][/doublepost]Hi, I've tried this method but I failed. My 2009 Macbook Pro can't see my created usb as a bootable disk, it's not shown when I boot with option key. It does work when I try it on a newer MBP with High Sierra already installed. So I think the created usb should be good. Do I have to change something in my settings? Filevault is disabled.

Thanks.[/QUOTE]

It seemed to be the usb drive that caused the problem. Tried another one and that did the job. No issues so far after installation, and also got the security update without a problem. Many thanks!!!

 

[w1z]

Never mind. I tried testing again with a USB created with v2.5 and it failed too.. Turned out to be the CMOS battery was on its last stretch as the date was reset to Jan 1 2001 so I installed a new battery, set the current date/time via terminal and voila.. We are back in action.

Apologies for the false report.

 

[nigelbb]

I'm having an issue with two MacPro 4,1 models, they're both on 10.13 with the unsupported high sierra patcher, but I can't find any new updates in the app store. So I can't update them to 10.13.1, for example. I have tried reinstalling both the Patch Updater and the Software Update Patch from Patch Updater in the Utilities directory. But still, no dice.

I also couldn't install the 10.13.1 update manually from Apple, which I thought was weird.

If you have Mac Pro 4,1 systems surely the better route is to upgrade to 5,1 firmware? After that your hardware is officially supported so you can do a regular OS upgrade from the App Store.
[doublepost=1512534062][/doublepost]

Hello,

I have problems booting from USB thumb drive.
The disk is correctly created by the patcher app but when I try to boot from the USB volume I get the forbidden grey icon.
I have MacPro 3,1. It is a 1x2,8 upgraded to 2x3,0 Ghz with a Radeon R9.

Any idea?
Thank you

I have never been able to boot my 3,1 from USB. Previously I have used a Firewire disk instead.

 

[w1z]

Has anyone successfully restored from a time machine backup made under the patched HS installation on the same system?

I have spent the last couple of hours trying to restore from within the recovery partition and I keep getting a message on the tune of 'Time machine backup made on different computer' with 3 options to choose from - Startup, Install macOS, Choose another source...

The patched HS usb disk does not have restoration options included under the utilities so I am stuck now as migration assistance causes/changes some critical folders' ownership to 'Fetching' and can't be accessed.

I am starting to dread upgrading to High Sierra.. Help!

 

[dosdude1]

Has anyone successfully restored from a time machine backup made under the patched HS installation on the same system?

I have spent the last couple of hours trying to restore from within the recovery partition and I keep getting a message on the tune of 'Time machine backup made on different computer' with 3 options to choose from - Startup, Install macOS, Choose another source...

The patched HS usb disk does not have restoration options included under the utilities so I am stuck now as migration assistance causes/changes some critical folders' ownership to 'Fetching' and can't be accessed.

I am starting to dread upgrading to High Sierra.. Help!

Just install a clean copy of High Sierra using a patched installer drive, then, during the setup when it asks you to "Transfer information from another Mac", use that to select your Time Machine backup.

 

[w1z]

Just install a clean copy of High Sierra using a patched installer drive, then, during the setup when it asks you to "Transfer information from another Mac", use that to select your Time Machine backup.

I wish it was that easy.. 10.13.2 beta 6 was installed in the backup and the usb installer uses 10.13.1 for source so a warning is displayed that there could potentially be issues and surely there were. The restoration fails at some point in the process and I am back at the original restoration window I tried running the restoration again with the same results.

 

[dosdude1]

I wish it was that easy.. 10.13.2 beta 6 was installed in the backup and the usb installer uses 10.13.1 for source so a warning is displayed that there could potentially be issues and surely there were. The restoration fails at some point in the process and I am back at the original restoration window I tried running the restoration again with the same results.

In that case, you'll need to install the latest beta update, and then restore. This is one reason why I advise against running beta versions of Mac OS.

 

[w1z]

My thoughts exactly... lesson learned. Although the option to update is given in the restoration process, it fails because it's a clean install with no beta updates activated. I am now retrying migration assistant on 10.13.2 beta 6 but with a different user id/name.

I wonder why the restoration option in the recovery partition, which was created during the installation of macOS, fails with the 'backup was created on a different computer' message when it was clearly made on the same computer.

This isn't the only issue I have with HS. My windows bootcamp install is no longer bootable even though it is on a dedicated drive attached to a velocity duo x2 pcie card - was working fine under Sierra.

Anyway, if all fails then I'll rollback to Sierra and carry out a manual restoration which will be a PITA.


Update: I was able to fix the 'fetching' permissions issue. Just needed to vacate UniqueID 501, which was used by the backed up account, and then ran migration assistant. All data has been restored, phewww.

Funny thing is I just noticed 10.13.2 combo update is now available in App Store.. arghhhh!! Hate killing time like this.. One thing's for sure, no more beta crap for me.

 

[dosdude1]

My thoughts exactly... lesson learned. Although the option to update is given in the restoration process, it fails because it's a clean install with no beta updates activated. I am now retrying migration assistant on 10.13.2 beta 6 but with a different user id/name.

I wonder why the restoration option in the recovery partition, which was created during the installation of macOS, fails with the 'backup was created on a different computer' message when it was clearly made on the same computer.

This isn't the only issue I have with HS. My windows bootcamp install is no longer bootable even though it is on a dedicated drive attached to a velocity duo x2 pcie card - was working fine under Sierra.

Anyway, if all fails then I'll rollback to Sierra and carry out a manual restoration which will be a PITA.


Update: I was able to fix the 'fetching' permissions issue. Just needed to vacate UniqueID 501, which was used by the backed up account, and then ran migration assistant. All data has been restored, phewww.

Funny thing is I just noticed 10.13.2 combo update is now available in App Store.. arghhhh!! Hate killing time like this.. One thing's for sure, no more beta crap for me.

Just run "sudo softwareupdate --clear-catalog" in Terminal, that will make the beta updates stop appearing.

 

[d4gli]

Final 10.13.2 killed working my Safari, Mail & Appstore (seems to be related to all Apple Webkit Apps).
Running PRam/NVRAM Reset (Shutdown, turn on and press immediately ALT + CMD + P + R) fixed it. CSR has been reactivated; make sure to reboot recovery/usb to disable it again.