Slightly OT, but do the OCLP installers for Big Sur, Monterey, Ventura, Sonoma, Sequioa and soon to be Tahoe include the APFS support firmware installed by High Sierra or is it necessary to install High Sierra first to get SSD APFS support before going to the later OCLP-supported systems? Thanks for any insight. I have an old MBP 9,2 on Sierra that is giving a requires firmware update message when trying to get it to OCLP Sonoma.
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 15 Sequoia on Unsupported Macs Thread
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Isn't Sierra already supporting APFS under the hood? It's just hidden somehow and not in Disk Utility.
Maybe this helps:
macOS Sierra Patch Tool
dosdude1.com
Sorry, wrong link. That was for installing Sierra. Here are all of those.
Just a shot in the dark, but legacy 32 bit app support is as dead as a doornail at this point. That's my standard response when someone mentions Sierra/High Sierra.
To understand why that is, you might want to read this: https://eclecticlight.co/2024/08/22/dual-booting-your-mac-with-multiple-versions-of-apfs/
What are you trying to achieve exactly? For example, are there some 32 bit apps you cannot live without?
If not, do a clean install of the last supported macOS for your m/c and upgrade using OCLP from there. Holler if you need help with that.
Alternatively, freeze that Mac and keep it solely for running 32 bit apps. Use something newer for everyday use.
Last edited:
OK, so I read up on Plex's Hardware acceleration. It requires Intel QuickSync video. So, the question is, would an install of macOS via OpenCore affect this functionality? Especially if the drivers for the GPU aren't packaged with the version of macOS installed?
MacinMan, Intel Quick Sync has been around since 2011 (Sandy Bridge), so it should work ok - the GPU drivers you're referring to might be the discrete GPU (AMD or Nvidia) rather than the integrated Intel GPU which is a part of the Intel CPU in Intel Macs.
re: nekton1's MacBookPro9,2, I agree with rehkram
According to EveryMac, the last macOS that supports MacBookPro9,2 (Mid-2012 13" MacBook Pro, Ivy Bridge) is 10.15 Catalina. I'd upgrade the operating system to that before attempting anything else.
https://everymac.com/systems/apple/...re-i5-2.5-13-mid-2012-unibody-usb3-specs.html
10.14 Mojave is the last macOS to support 32-bit applications, so I'd install that on an external drive or separate partition if you need to run those 32-bit apps.
macOS has used APFS since 10.13 High Sierra (it was experimental in Sierra) and it is backwards compatible, i.e., the newest version of macOS can read older versions of APFS (and HFS volumes), but not vice versa.
re: nekton1's MacBookPro9,2, I agree with rehkram
According to EveryMac, the last macOS that supports MacBookPro9,2 (Mid-2012 13" MacBook Pro, Ivy Bridge) is 10.15 Catalina. I'd upgrade the operating system to that before attempting anything else.
https://everymac.com/systems/apple/...re-i5-2.5-13-mid-2012-unibody-usb3-specs.html
10.14 Mojave is the last macOS to support 32-bit applications, so I'd install that on an external drive or separate partition if you need to run those 32-bit apps.
macOS has used APFS since 10.13 High Sierra (it was experimental in Sierra) and it is backwards compatible, i.e., the newest version of macOS can read older versions of APFS (and HFS volumes), but not vice versa.
Claude 4 might be hallucinating but this is what it answers:
Q: Do Dortania OCLP macOS installers automatically convert HFS+ destination drive to APFS?
A: Based on the search results and current information about Dortania's OpenCore Legacy Patcher (OCLP), here's what happens with filesystem conversion:
Yes, OCLP macOS installers do automatically convert HFS+ destination drives to APFS during installation.
Here are the key details:
Monterey (and every release since Mojave) physically cannot be installed onto a drive formatted as HFS+ (Mac OS Extended (Journaled)). APFS is a requirement. Since OCLP is designed to install macOS Big Sur and later versions on unsupported Macs, APFS conversion is necessary for the installation to work.
OCLP does its own partition-formatting, even though the partition may start out as HFS+. It then re-formats it to APFS. This happens automatically during the installation process - you don't need to manually convert the drive beforehand.
The conversion process is designed to be non-destructive when upgrading, but as with any major filesystem change, having a backup is strongly recommended before proceeding with the installation.
I am trying currently to install Sequoia Final 15.6 using OCLP USB installer on to a newly HFS+ formatted SSD in the MacBook Pro 9.2. The installation started OK but seems to have stalled at 16 minutes remaining — I wonder if this is the HFS+ to APFS conversion period, or perhaps this just doesn't work. Previously, when I tried to install Catalina from a Mac OSx install image dled from Apple, I got the message that a firmware update was necessary for the install to proceed. I guess I can try creating a High Sierra USB installer too but I have a vague recollection that Apple prevented installs if the original HDD was not present. I could be wrong though.
Finally ended with:
Q: Do Dortania OCLP macOS installers automatically convert HFS+ destination drive to APFS?
A: Based on the search results and current information about Dortania's OpenCore Legacy Patcher (OCLP), here's what happens with filesystem conversion:
Yes, OCLP macOS installers do automatically convert HFS+ destination drives to APFS during installation.
Here are the key details:
Why OCLP Converts to APFS
Monterey (and every release since Mojave) physically cannot be installed onto a drive formatted as HFS+ (Mac OS Extended (Journaled)). APFS is a requirement. Since OCLP is designed to install macOS Big Sur and later versions on unsupported Macs, APFS conversion is necessary for the installation to work.
How the Conversion Works
OCLP does its own partition-formatting, even though the partition may start out as HFS+. It then re-formats it to APFS. This happens automatically during the installation process - you don't need to manually convert the drive beforehand.
Important Considerations
- Drive Recognition: Some users have reported that OCLP cannot recognize (or convert) the HFS+ file system to APFS in certain situations, particularly when trying to install on existing HFS+ volumes with data.
- Clean Installation Recommended: For best results, it's recommended to format the destination drive as APFS beforehand using Disk Utility, or allow OCLP to perform a clean installation where it handles the formatting automatically.
- SSD vs HDD: APFS is optimized for solid-state drive storage and performance may be poor on traditional spinning hard drives.
The conversion process is designed to be non-destructive when upgrading, but as with any major filesystem change, having a backup is strongly recommended before proceeding with the installation.
I am trying currently to install Sequoia Final 15.6 using OCLP USB installer on to a newly HFS+ formatted SSD in the MacBook Pro 9.2. The installation started OK but seems to have stalled at 16 minutes remaining — I wonder if this is the HFS+ to APFS conversion period, or perhaps this just doesn't work. Previously, when I tried to install Catalina from a Mac OSx install image dled from Apple, I got the message that a firmware update was necessary for the install to proceed. I guess I can try creating a High Sierra USB installer too but I have a vague recollection that Apple prevented installs if the original HDD was not present. I could be wrong though.
Finally ended with:
Attachments
Last edited: