Thanks K two but iPad not necessary. Universal Control is supported between Macs as well.
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
Hello,
I had install Sequia on an Imac 2011 and an Imac 2013. Everything is fine but when I start, on the 2011, I have the screen immediately with a password , after a wait bar and a password again and then the desktop. On the 2013, I have only a wait bar on black screen and the password one time and the desktop. Do you know why boots are différent. Thank.
I had install Sequia on an Imac 2011 and an Imac 2013. Everything is fine but when I start, on the 2011, I have the screen immediately with a password , after a wait bar and a password again and then the desktop. On the 2013, I have only a wait bar on black screen and the password one time and the desktop. Do you know why boots are différent. Thank.
Hi, I have a MBP 11,1 mid 2014 with 15.1 OCLP 2.1.0 N and a MacMini 7,1 2014 with 15.1 OCLP 2.1.0 N and Universal Control is working. The workaround is to spoof the MacMini 7,1 (to 8,1) in OCLP-->Settings-->SMBIOS-->SMBIOS Spoof Level to" Moderate" and SMBIOS Spoof Model to "Macmini8,1"--> Build and install OpenCore. You can go here for better info https://dortania.github.io/OpenCore-Legacy-Patcher/UNIVERSALCONTROL.html#blacklisted-models
Attachments
Seems to be a firmware password set on the 2011 only:
Set a firmware password on your Mac - Apple Support
When you set a firmware password, users who don't have the password can't start up from any disk other than the designated startup disk.
Is anyone successfully running 15.1 on a MBP 2012 non-retina? Specifically I'm wondering about networking issues, messages problems, and issues with preview or any other apple apps using the built in graphics manipulation tools like masking and color levels etc. TIA
New OCLP 2.1.0n ist out fixes WhatsApp crashes on effected devices - FYI
Yes WhatsApp now working, only one issue you for me if I build and install Opencore fails on OCLP 2.1n for me. I got round this by booting my Big Sur partition build and install on that then reboot into sequoia and root patch I might be unlucky with the nightly but recommend having a backup efi or second MacOS because it still lets you install the failed Build in Opencore (if your not reading the log) which results in a non booting system I also find with OCLP 2.1n I get “your Mac needs to cool down” errors in photos one of the original reasons I went back to OCLP 2.0.2 photos works much better for me on it.
Last edited:
2.1.0n running fine on my machines always good to do an nv ram reset before booting installation went also normal… but for sure it‘s a nightly on unsupported hardware always good to have backups and know what to do just in case you‘re right.
Tried three times and get this error each time—any ideas?
Failed to create macOS installer
Output: Started erase on disk5
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk5s2 as Mac OS Extended with name OCLP-Installer
Initialized /dev/rdisk5s2 as a 29 GB case-insensitive HFS Plus volume
Mounting disk
Finished erase on disk5
Copying essential files...
Copying the macOS RecoveryOS...
Making disk bootable...
Error: Erasing disk: 0%... 10%... 20%... 30%... 100%
Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle
The bless of the installer disk failed.
Seems like most things work fine so far. Preview does have an issue with the levels control. Any manipulation there seems to make the image disappear. My limited testing in other apps is good so far. I haven't noticed much difference in performance with Sonoma and I think I will live with the Preview issue for now as I do have a couple of other apps that I can use for that function when I need it.
Tried again with different USB and got the same error message:
Failed to create macOS installer
Output: Started erase on disk2
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk2s2 as Mac OS Extended with name OCLP-Installer
Initialized /dev/rdisk2s2 as a 115 GB case-insensitive HFS Plus volume
Mounting disk
Finished erase on disk2
Copying essential files...
Copying the macOS RecoveryOS...
Making disk bootable...
Error: Erasing disk: 0%... 10%... 20%... 30%... 100%
Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle
The bless of the installer disk failed.
Is there an issue with OCLP and spoofing?
Funny enough, I had the same error yesterday. I didn’t think much of it because I used disk utility to erase the whole stick and after that everything went fine using default settings.
today commit
| - Resolve macOS 15.1 (24B2083) Apple Silicon installer appearing as download option |
| - Resolve WhatsApp crashing on 15.1 |
| - Increment binaries: |
| - PatcherSupportPkg 1.8.4 - release |
Jumped the rMBP10,1 from the last beta to the release. Hit a bump in the road and struck the dreaded "hang on progress bar at 33%" and the "No Entry" sign. I think it was because I've had this machine running the betas for a while.
So I nuked the disk and used Recovery mode to install last supported macOS (Catalina). Used another (supported) Mac to build a usb installer for the rMBP10,1 with Sequoia 15.1 release & OCLP nightly on it. Inserted USB drive in rMBP, rebooted and selected it. All is good.
It was time consuming but worthwhile. It's running well now. I'll try avoiding betas for a while, and also avoid OTA updates, I think using an installer key might be better.
So I nuked the disk and used Recovery mode to install last supported macOS (Catalina). Used another (supported) Mac to build a usb installer for the rMBP10,1 with Sequoia 15.1 release & OCLP nightly on it. Inserted USB drive in rMBP, rebooted and selected it. All is good.
It was time consuming but worthwhile. It's running well now. I'll try avoiding betas for a while, and also avoid OTA updates, I think using an installer key might be better.
Did the same jump on the same Mac with no issues apart for no Safari favourites sync but other than that all good for our needs here.
Also same jump on a MBA 2010. Same iCloud Safari issue there and also no "Classic Macintosh" screensaver, which is a little bummer for older Macs as it is the screensaver that appears to use the least resources by far AFAIK. Ah well. Happy times..
Last edited:
On my rMBP10,1 I have a 1TB SSD and keep Catalina, Big Sur partitions together with Sequoia. That way I can boot say Catalina if Sequoia screws up. I also added a small 20GB HFS partition that I use as an "Installer" Drive instead of using USB.
I use Apple's instructions to download and create the bootable Installer (hint
createinstallmedia method) on that 20GB drive. Once completed I see this in OpenCore bootpicker:Then simply select and boot the "Install macOS Sequoia" partition to install over the existing Sequoia.
The install process is much quicker than installing using USB.
When there's a new update just overwrite the Installer partition with the new update by downloading the full OS and running the
createinstallmedia command.You can use OCLP to download the OS.
But OCLP will not allow you to create an Installer on anything other than a USB (shame...a big omission IMHO).
Really good idea, especially since the install proces is quicker.
Yeah I know a lot of folks do that. In fact, I used to do that, since there's plenty of room on the disk. Sort of like "collecting" different versions of macOS
Until one day the machine crashed in a smoldering heap for reasons I don't fully remember except for the fact that disk corruption was involved. Ever since then the KIS principal has been in place here.
I'll see if I can find the post I made at the time describing what happened and post the link if you're interested.
Yup there's no way around from a whole disk corruption.
That's why I have a bootable OCLP USB-SSD that I regularly use to create a clone of the rMBP.
Strictly speaking, they are APFS Containers and one HFS Partition (that I use for Installers):
In engineering it's always the things you don't know that get you. My reasoning is that, sure you can run multiple unsupported versions on your Mac using OCLP. But, and correct me if I'm wrong here, they are all using the same UEFI
So if you install a later macOS version with changes to, for example, the APFS instruction set, you are rolling the dice when you boot into an earlier version. I believe that's what happened to me but wasn't able to prove it for sure. After recovering it I sure as hell wasn't going to try and duplicate the problem just to confirm it!
So if you install a later macOS version with changes to, for example, the APFS instruction set, you are rolling the dice when you boot into an earlier version. I believe that's what happened to me but wasn't able to prove it for sure. After recovering it I sure as hell wasn't going to try and duplicate the problem just to confirm it!
OCLP nor EFI are an issue related to APFS format. OpenCore usually chooses the correct APFS driver during the boot process for the OS being booted.
Once booted, theoretically there should be no problem accessing an APFS volume formatted with different versions of macOS.
Format of the APFS volume should be universal. An analogy is printer paper size. Here in the UK, standard is A4 paper size. I can print on that paper from any type of printer since the printers know the full specification of that paper and know how to write to it.
However, when dealing with Apple, we are it's mercy. They do not necessarily specify or guarantee compatibility between different versions.
Yes you may potentially have an issue if you booted say Catalina and on the same system where you have a newer macOS (say Sequoia). Catalina APFS driver is much older than Sequoia and if Sequoia makes subtle changes to the way it formats & writes APFS volumes, there's potential for trouble.
This happened way back in High Sierra when APFS was introduced. Booting HS on the same system where say Big Sur is installed, and when it write to BS's volume it can corrupt it even though it should APFS is a "standard". It's more likely a bug in the drivers rather than change of APFS format.
But I have not seen an issue with on my rMBP when booting Catalina, Big Sur or Sequoia and each accessing each others volumes 🤞
Here's an interesting article on the subject. And you are right, we don't know what we don't know with respect to what Apple are doing at any point in time.
Dual-booting your Mac with multiple versions of APFS
What if you want to boot your Mac using two or more different versions of macOS, with different versions of APFS? Here’s how to avoid problems.
eclecticlight.co