Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS Tahoe 26 on Unsupported Macs Discussion

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.
TOM1211 said:
Use OCAuxiaryTools to update things (if you use you do at your own risk)
Click to expand...
Anyone who uses OpenCore or OCLP always does so at their own risk – even with the tools. ;)

I know OCAT - I used it before.

Now I use OpCore-Simplify-main to create a device-specific OpenCore bootloader, which has always been bootable.
This is how I installed macOS 26 Tahoe on my Hackintosh.

But the iMac 14.3 Late 2013 isn't a Hackintosh, it's a real Mac.

So I'd like to know where @Oxygen-X1 got it from, So I'd like to know where @Oxygen-X1 got it from, because he seems to have a version that allows macOS Tahoe on the iMac 14.3.
 
  • Like
Reactions: Oxygen-X1
LuckyOldMan said:
Anyone who uses OpenCore or OCLP always does so at their own risk – even with the tools. ;)

I know OCAT - I used it before.

Now I use OpCore-Simplify-main to create a device-specific OpenCore bootloader, which has always been bootable.
This is how I installed macOS 26 Tahoe on my Hackintosh.

But the iMac 14.3 Late 2013 isn't a Hackintosh, it's a real Mac.

So I'd like to know where @Oxygen-X1 got it from, So I'd like to know where @Oxygen-X1 got it from, because he seems to have a version that allows macOS Tahoe on the iMac 14.3.
Click to expand...
I have OC 1.0.5 from the OCLP 3.0.0 nightly package.
So when you open the package, click on Open Core Install in the top left corner. See screenshot (images look so crappy without graphics support).
 

Attachments

  • OCLP-3.0.0n.jpg
    OCLP-3.0.0n.jpg
    82.6 KB · Views: 35
TOM1211 said:
I’m confused thought they had actually used it given previous posts.
Looking at the OCLP mod it installs a driver/usb extension that chris1111 is relying on wonder if there’s a work around.
Click to expand...
No, I only tried it for the first time yesterday with WiFi-USB and my TP Link device.

I didn't need it, because Ethernet works perfectly on the late 2013 iMac.

Just yesterday I discovered that it doesn't work on Tahoe Beta 3. God only
knows why it doesn't work; it works perfectly on Squoia.

And since both OCLP patches, neither from Dortania nor from laobamac,
won't run due to the missing metallib.pkg, I can't use WiFi-USB.
 
Oxygen-X1 said:
I have OC 1.0.5 from the OCLP 3.0.0 nightly package. So when you open the package, click on Open Core Install in the top left corner .....
Click to expand...
So it's OCLP 3.0.0-Nightly, as I thought.

I didn't do anything different all the time I used OCLP in the past than what you're recommending when I created my OCLP 3.0.0n-Stick or these in the earlier days.
And of course, the OCLP 3.0.0n has the OpenCore.efi from the regular OpenCore 1.0.5. OpenCore was and is the origin of OCLP.

You're still using the OpenCore Legacy Patcher 3.0.0-Nightly, not the regular OpenCore 1.0.5 for Hackintoshes.
 
  • Like
Reactions: ronton3 and Oxygen-X1
LuckyOldMan said:
So it's OCLP 3.0.0-Nightly, as I thought.

I didn't do anything different all the time I used OCLP in the past than what you're recommending when I created my OCLP 3.0.0n-Stick or these in the earlier days.
And of course, the OCLP 3.0.0n has the OpenCore.efi from the regular OpenCore 1.0.5. OpenCore was and is the origin of OCLP.

You're still using the OpenCore Legacy Patcher 3.0.0-Nightly, not the regular OpenCore 1.0.5 for Hackintoshes.
Click to expand...
Right Lucky.... Not this for Hackis !!!!!
 
  • Like
Reactions: LuckyOldMan
LuckyOldMan said:
Anyone who uses OpenCore or OCLP always does so at their own risk – even with the tools. ;)

I know OCAT - I used it before.

Now I use OpCore-Simplify-main to create a device-specific OpenCore bootloader, which has always been bootable.
This is how I installed macOS 26 Tahoe on my Hackintosh.

But the iMac 14.3 Late 2013 isn't a Hackintosh, it's a real Mac.

So I'd like to know where @Oxygen-X1 got it from, So I'd like to know where @Oxygen-X1 got it from, because he seems to have a version that allows macOS Tahoe on the iMac 14.3.
Click to expand...

But OCAT allows you to sync opencore latest version.? e.g 1.0.5 ( I mean that’s how I did it).
 
  • Like
Reactions: Oxygen-X1
If you have a real Mac, use Open Core Legacy Patcher (OCLP) to build/generate your Open Core EFI. There really is no reason to use anything else to generate your real Mac's Open Core EFI (for booting macOS on unsupported Macs) unless you're a masochist.

In my opinion, it is unfortunate that the Devs named it 'Open Core Legacy Patcher.' Including 'Open Core' in the product name only creates confusion. It is two tools in one: 1) it is an EFI builder and 2) it is a root patcher (restoring macOS frameworks that are required to support older Macs).

OCLP 3.0.0 builds the EFI (needed to boot macOS on unsupported Macs) using Open Core 1.0.5 drivers and config.plist. OCLP adds kexts (created by Acidanthera and Dortania) to the Open Core EFI that are injected by Open Core during the boot cycle.

The talk about 'pure Open Core' and 'no need for OCLP' (in the context of a real, unsupported Mac) is just confusing and in my opinion, wrong.
 
Last edited:
  • Like
Reactions: olad, Portiere, Pri-est and 6 others
deeveedee said:
If you have a real Mac, use Open Core Legacy Patcher (OCLP) to build/generate your Open Core EFI. There really is no reason to use anything else to generate your real Mac's Open Core EFI (for booting macOS on unsupported Macs) unless you're a masochist.

In my opinion, it is unfortunate that the Devs named it 'Open Core Legacy Patcher.' Including 'Open Core' in the product name only creates confusion. It is two tools in one: 1) it is an EFI builder and 2) it is a root patcher (restoring frameworks that are required to support older Macs).

OCLP 3.0.0 builds the EFI (needed to boot macOS on unsupported Macs) using Open Core 1.0.5 drivers and config.plist. OCLP adds kexts (created by Acidanthera and Dortania) to the Open Core EFI that are injected by Open Core during the boot cycle.

The talk about 'pure Open Core' and 'no need for OCLP' is just confusing and in my opinion, wrong.
Click to expand...
Yes you have absolute right!
 
  • Like
Reactions: ronton3
deeveedee said:
If you have a real Mac, use Open Core Legacy Patcher (OCLP) to build/generate your Open Core EFI. There really is no reason to use anything else to generate your real Mac's Open Core EFI (for booting macOS on unsupported Macs) unless you're a masochist.

In my opinion, it is unfortunate that the Devs named it 'Open Core Legacy Patcher.' Including 'Open Core' in the product name only creates confusion. It is two tools in one: 1) it is an EFI builder and 2) it is a root patcher (restoring macOS frameworks that are required to support older Macs).

OCLP 3.0.0 builds the EFI (needed to boot macOS on unsupported Macs) using Open Core 1.0.5 drivers and config.plist. OCLP adds kexts (created by Acidanthera and Dortania) to the Open Core EFI that are injected by Open Core during the boot cycle.

The talk about 'pure Open Core' and 'no need for OCLP' (in the context of a real, unsupported Mac) is just confusing and in my opinion, wrong.
Click to expand...

This explanation helps a lot with the confusion and understanding. Thank you
 
  • Like
Reactions: Oxygen-X1
Oxygen-X1 said:
Theo Problem HERE ist....more User write Here over Hackintosb !
Here ist a Forum for original Macs think i.
Click to expand...
There will be more real Mac users when OCLP 3.0.0 'officially' supports macOS Tahoe. Most of the OCLP users won't even attempt to install macOS Tahoe on their unsupported Macs until OCLP 3.0.0 is declared 'ready' by the Devs.
 
  • Like
Reactions: olad, paalb, macpro_mid2014 and 4 others
deeveedee said:
There will be more real Mac users when OCLP 3.0.0 'officially' supports macOS Tahoe. Most of the OCLP users won't even attempt to install macOS Tahoe on their unsupported Macs until OCLP 3.0.0 is declared 'ready' by the Devs.
Click to expand...
Yes, it's a shame that more users aren't as willing to experiment as I am.

But I'm currently satisfied with the state of my late 2013 iMac (27-inch).
Bluetooth, Ethernet, sound, and USB all work.

It's not really fun to do anything with it without full graphics support from
my NVidia Kepler graphics card, but as a retiree, I enjoy experimenting.

For real work, I have my MBPro 2019 (16-inch) in desktop mode with a Samsung 4K monitor.
 
  • Like
Reactions: LuckyOldMan, hvds and ronton3
I attempted to do something differently
I tried to install MacbookPro15,2 which is in the grey area because it's neither supported by Tahoe nor supported by OCLP.
As explained by the devs of OCLP, T2 Macs have issues with OpenCore. But on this device it boots fine and detects the SSD. The only issue is the WiFi not working under OpenCore despite the WiFi driver having native support in Sequoia.
The farthest I've get is to install Sequoia on another volume first, then use OCLP to boot into the Tahoe recovery drive.
The process stops midway with Operation not permitted.
I'm guessing this could be related to the SSD or the upgrade progress being problematic.

I cannot fresh install Tahoe on an empty volume because the Tahoe Recovery under OpenCore wouldn't modify APFS volumes or mount empty volumes without macOS installed on them.

What should I try next? Install from another Mac via Target Disk Mode? or else?
My plan is to install onto the disk then boot with -no_compat_check
 
deeveedee said:
In my opinion, it is unfortunate that the Devs named it 'Open Core Legacy Patcher.' Including 'Open Core' in the product name only creates confusion.
Click to expand...
Yes and no: anyone who has worked intensively with the two tools knows the differences.

I've been using OpenCore since the beginning – until then, Clover was the right tool.
The same applies to OpenCore Legacy Patcher – here, the difference is already evident in the naming: OpenCore is a bootloader for Hackintoshes, whereas OpenCore Legacy Patcher has a slightly different objective: it enables unsupported Macs to continue to be used beyond their macOS limitations.

When I read OC 1.5.1, I know it's about a Hackintosh, OCLP 2.4.0 or OCLP 3.0.0 are about real, but unsupported Macs.

deeveedee said:
The talk about 'pure Open Core' and 'no need for OCLP' (in the context of a real, unsupported Mac) is just confusing and in my opinion, wrong.
Click to expand...

There's a good reason why I'm explicitly talking about pure Open Core and OCLP in this thread, and you shouldn't have missed it.

Because it wasn't me who wrote in connection with an unsupported Mac..."In my experience, you do NOT need OCLP (Dortania) 3.0.0n, nor do you need OCLP Mod 2.4.0... All based on my original iMac late 2013. ...but @Oxygen-X1 (see #351).

To avoid any confusion, I discussed it with him beforehand in a private message and later here in the thread.

To better emphasize the differences between OpenCore & OCLP, I added the aforementioned attributes 'pure OC'.

It turned out that he meant OCLP 2.4.0/3.0.0 when he spoke of OC 1.5.0.

By the way: we wouldn't even need to have this discussion about "pure OC" & "OCLP" here if it would only be about unsupported Macs and no Hackintoshes, as the thread title "macOS Tahoe 26 on Unsupported Macs Discussion" suggests.

In my opinion, this confusion has arisen because both Hackintosh and real Mac problems have been discussed here in one thread. The topics should be divided.
The causes and recommendations for solving the problem can be different. What works for a Hackintosh may not work for a real Mac, and vice versa.

As I said before: How is a less experienced forum user supposed to differentiate between the two?
 
  • Like
Reactions: olad, Oxygen-X1 and ronton3
mikezang said:
When I downloaded MacOS 26 Beta 3 and extracted it by OCLP 3.0.0n, I got error as below, what can I do next?View attachment 2528543
Click to expand...
You‘ve built 3.0.0 from source?
In that case in terminal cd to privileged_helper and do make debug, then install 3.0.0 again. OCLP doesn‘t have privilege to do much unless built by its developers. Debug bypasses some security to still work.
It‘s somewhere in the docs.
 
  • Like
Reactions: sinbad21
  • Like
Reactions: olad and Oxygen-X1
hvds said:
You‘ve built 3.0.0 from source?
In that case in terminal cd to privileged_helper and do make debug, then install 3.0.0 again. OCLP doesn‘t have privilege to do much unless built by its developers. Debug bypasses some security to still work.
It‘s somewhere in the docs.
Click to expand...
I am not good at built OCLP 3.0.0 from source, can you tell me more detail do make debug, then install 3.0.0 again?
I just clone source and run it by python OpenCore-Patcher-GUI.command
 
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