I just updated it to support the final release. I don't think the firmware check should affect anything, but I'll test it just to be sure.
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 High Sierra (10.13) Unsupported Macs Thread
- Thread starter foxlet
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Just finished installing HS public release on my MBP 4,1 utilizing @dosdude1's latest tool. (no apfs for me though - just a preference).
The 2012 MacMini is still labouring away (16 minutes remaining) using Apple's generic installer....funny, it started before I did on my MBP.
Kudos to all those that have worked on these tools!!!
The 2012 MacMini is still labouring away (16 minutes remaining) using Apple's generic installer....funny, it started before I did on my MBP.
Kudos to all those that have worked on these tools!!!
Yeah, these somewhat arbitrary support cutoffs sometimes irritate me to no end.Just finished installing HS public release on my MBP 4,1 utilizing @dosdude1's latest tool. (no apfs for me though - just a preference).
The 2012 MacMini is still labouring away (16 minutes remaining) using Apple's generic installer....funny, it started before I did on my MBP.
HS is fully supported on MacBook6,1.
HS is not supported on MacBookPro5,5 or MacBook5,1, unless I use dosdude1's patcher.
MacBook6,1 specs:
Core 2 Duo 2.26 GHz
DDR3 1067 MHz RAM
GeForce 9400M with 256 MB
SuperDrive
5400 rpm hard drive
MacBookPro5,5 specs:
Core 2 Duo 2.26 GHz
DDR3 1067 MHz RAM
GeForce 9400M with 256 MB
SuperDrive
5400 rpm hard drive
MacBook5,1 specs:
Core 2 Duo 2.0 Ghz
DD3 1067 MHz RAM
GeForce 9400M with 256 MB
SuperDrive
5400 rpm hard drive
See a pattern here?
Yet, two of the three machines are not supported.Just to be clear, I must first decrypt my filevault drive on the 2008 Mac Pro, before upgrading?
It's recommended, but not necessary. You can unlock the volume using Terminal after booting the installer, and it should then be accessible.
[doublepost=1506367700][/doublepost]
I think that should work.
Use the "Download macOS" option in the Tools menu of macOS High Sierra Patcher.
I have just updated to 10.13 on my iMac 2007 using dosdude1's installer, applied relevant patches, but now no audio device installed and screen brightness patch not working. Airplay is working. Any ideas?
Hi there,
I just used dosdude's patcher 2.3.1 to download the High Sierra image using Tools->Download macOS High Sierra. Now I have the 5.18 GB file, but it seems like the SHA1 checksum is different accoring to this site: https://github.com/notpeter/apple-installer-checksums#mac-osx-installers-sha1-checksums
10.13.0 (17A365)
4164f0dde7316ad745426438ef013568fe0313ba (InstallESD.dmg)
530839420356e6d77b5ff6da3a3753305da26567 (BaseSystem.dmg)
But I get:
60eaad3687c84102752a09879306b965a0a9f769 (InstallESD.dmg)
530839420356e6d77b5ff6da3a3753305da26567 (BaseSystem.dmg)
Is that intended or a bug with dosdude's tool?
I just used dosdude's patcher 2.3.1 to download the High Sierra image using Tools->Download macOS High Sierra. Now I have the 5.18 GB file, but it seems like the SHA1 checksum is different accoring to this site: https://github.com/notpeter/apple-installer-checksums#mac-osx-installers-sha1-checksums
10.13.0 (17A365)
4164f0dde7316ad745426438ef013568fe0313ba (InstallESD.dmg)
530839420356e6d77b5ff6da3a3753305da26567 (BaseSystem.dmg)
But I get:
60eaad3687c84102752a09879306b965a0a9f769 (InstallESD.dmg)
530839420356e6d77b5ff6da3a3753305da26567 (BaseSystem.dmg)
Is that intended or a bug with dosdude's tool?
The InstallESD.dmg file downloaded from the Software Update CatalogURL (which is what my tool uses to locate the files to download) is packaged differently than the one included with the App Store download (packaged inside InstallESDDmg.pkg)... That's why the SHA1 is different.
Just upgraded my 2009 Macbook Pro 13" running Sierra (installed with the last dosdude1 tool) and everything went flawlessly. Thanks again!
Got my MB 5,2 Humming right along with 10.13.0. So far so good, ran the patcher update after install and got brightness and volume working again.
Contemplating patch installation on my MacBookPro5,3. Device currently runs well with few hiccups, mostly concerned 10.11 security updates will be discontinued or obsolete soon. Laptop gets little use these days. Keep it updated to utilize a handful of apps/tasks my iPad Pro (10.5”) isn’t capable of … whittled apps down to one processor/graphic intense program, which is out-of-date but still runs well. I’m sure there are plenty of pros/cons that should be considered before making this leap. Is effort worthwhile? Input and opinions would be greatly appreciated.
El Capitan 10.11.6
MacBook Pro (15-inch, Mid 2009), MacBookPro5,3
3.06 GHz Intel Core 2 Duo
8 GB 1067 MHz DDR3
NVIDIA GeForce 9600M GT 512 MB
El Capitan 10.11.6
MacBook Pro (15-inch, Mid 2009), MacBookPro5,3
3.06 GHz Intel Core 2 Duo
8 GB 1067 MHz DDR3
NVIDIA GeForce 9600M GT 512 MB
Last edited:
From a support note: Boot Camp doesn't read from or write to APFS-formatted volumes, but is compatible with High Sierra.
https://support.apple.com/en-gb/HT208018
That's the new APFS booting implementation. Unfortunately, you cannot hide it, but it will only show at boot time. Doesn't negatively affect the system at all.