Jump to content
511 posts in this topic

Recommended Posts

6 minutes ago, chris1111 said:

Thanks @laobamac_yyds Always working in Latest Tahoe Beta ✌️

 

Screenshot2025-10-13at7_01_57PM.png.46ce8eaee14011babf1ad50616757716.png

 

6 minutes ago, chris1111 said:

Thanks @laobamac_yyds Always working in Latest Tahoe Beta ✌️

 

Screenshot2025-10-13at7_01_57PM.png.46ce8eaee14011babf1ad50616757716.png

And what exactly does it mean that @laobamac_yyds OCLP works?
So, my understanding is that NOW EVERYTHING works on older Macs like my late 2013 iMac, including full graphics support, right?

Or what does this sentence actually mean?

Edited by AlfredoM
  • Confused 1
9 minutes ago, AlfredoM said:

 

And what exactly does it mean that @laobamac_yyds OCLP works?
So, my understanding is that NOW EVERYTHING works on older Macs like my late 2013 iMac, including full graphics support, right?

Or what does this sentence actually mean?

No graphics support, only USB Wifi and Audio AppleHDA

My hackintosh is support in Graphics 

AMD Radeon Pro WX 4100 4 GB

Edited by chris1111
  • Like 2
  • Thanks 1
2 minutes ago, chris1111 said:

No graphics support, only USB Wifi and Audio AppleHDA

I thought so.
Then you shouldn't write in such big, headline-like capitals that this OCLP patch works in general (although you can understand EVERYTHING).

  • Confused 2
  • Sad 1
On 9/10/2025 at 7:07 PM, laobamac_yyds said:

@KGP-iMacPro @杰利厘米

Okay, friends, I haven't been watching forums much lately.

 

Regarding the patch for the wireless network card in Tahoe, it is currently very difficult. We need to add back functions such as __os_trace_zalloc that were removed in Tahoe through dyld interception.This is a huge project, and I don't think my energy and skills are enough to complete it alone. After all, I am only one person, not a team.

 

However, I have looked at the bwn driver in FreeBSD and the bwfm driver in OpenBSD, and the latter, like itlwifi, porting bwfm seems to be a feasible solution. But doing so categorizes it as an IOEthernetController and connects it to the system through an Ethernet card, not an ADWL interface. This means that if successful, it will only have the most basic network functions like itlwm.In addition, unfortunately, bwfm only supports FullMac network cards, which means that only the BCM43602 wireless network card used by Mac can be purchased and supported by bwfm!Network cards such as BCM43224 and BCM4360 belong to SoftMac and can only be supported under the bwn (4) driver in FreeBSD. However, there is a huge difference between bwn and bwfm, and the complexity of SoftMac drivers can reach more than 1.5 times that of bwfm due to the need to handle more content that should have been handled by the network card firmware.This seems feasible, but the time required and whether it will succeed are unknown, so I need time to consider whether to proceed with this project. After all, it is not long before the Dortania team's expected time, and perhaps waiting for OCLP will be faster than transplanting bwn.

 

@laobamac_yyds, I don't know if you are aware about this ongoing thread and project

 

 

but it would be awesome if you could breathe new life into it or add additional ideas, in case you are interested..

 

All the best,

 

KGP 

 

  • Like 2
On 2025/10/16 at PM4点52分, KGP-iMacPro said:

 

@laobamac_yyds,我不知道你是否知道这个正在进行的线程和项目

 

 

但如果您有兴趣的话,如果您能为它注入新的活力或添加额外的想法,那就太棒了。

 

一切顺利,

 

克格勃 

 

Hi brother, I saw this project and successfully enabled the basic network on 43602CS, even though it's not stable.

 

Unfortunately, Apple BCMWifiCore only supports FullMac network cards, which means that patching this system extension method is absolutely not applicable to wireless network cards such as 94360,943224,94352 that are widely installed on Hackintosh.

 

I am still observing and I believe that my knowledge and efforts alone are not enough to complete the adaptation to Tahoe. But I will continue to work hard on this with Dortania until all the dust settles.

 

Best regards.

  • Like 8
  • Thanks 1
On 10/18/2025 at 4:21 AM, laobamac_yyds said:

Hi brother, I saw this project and successfully enabled the basic network on 43602CS, even though it's not stable.

 

Unfortunately, Apple BCMWifiCore only supports FullMac network cards, which means that patching this system extension method is absolutely not applicable to wireless network cards such as 94360,943224,94352 that are widely installed on Hackintosh.

 

I am still observing and I believe that my knowledge and efforts alone are not enough to complete the adaptation to Tahoe. But I will continue to work hard on this with Dortania until all the dust settles.

 

Best regards.

Everything being done here is useless unless full graphics support is provided for older iMacs, etc.
You can just stop with Project OCLP!

  • Confused 1
  • Sad 3
2 hours ago, AlfredoM said:

Everything being done here is useless unless full graphics support is provided for older iMacs, etc.
You can just stop with Project OCLP!

 

Please stop offending young, hard-working people and rather focus on improving the state of graphics for a few bugs instead of acting repetitively like a torpedo boat against ongoing projects that are highly relevant to others!

 

Cheers! 👍

 

 

Edited by KGP-iMacPro
  • Like 6
3 hours ago, KGP-iMacPro said:

 

Please stop offending young, hard-working people and rather focus on improving the state of graphics for a few bugs instead of acting repetitively like a torpedo boat against ongoing projects that are highly relevant to others!

 

Cheers! 👍

 

 

Please stop accusing me of insulting anyone again!
You're not feeling well, are you?
I'm a realist, not a dreamy optimist!

I had a bit of time again and wanted to try reinstalling the Tahoe 26.1 beta.

 

I stopped at the RC1 version of Tahoe.

Now I've noticed that after installing the 26.1 beta, nothing works: no USB, no Ethernet. What's going on? Everything worked with the RC1.

It seems that the Tahoe no longer works on a late 2013 iMac, or does anyone know what's going on?

  • Sad 1
On 10/27/2025 at 2:39 AM, AlfredoM said:

I had a bit of time again and wanted to try reinstalling the Tahoe 26.1 beta.

 

I stopped at the RC1 version of Tahoe.

Now I've noticed that after installing the 26.1 beta, nothing works: no USB, no Ethernet. What's going on? Everything worked with the RC1.

It seems that the Tahoe no longer works on a late 2013 iMac, or does anyone know what's going on?

But Tahoe will not work with 2013 Mac there should be >2019. If you had success then you had some patches like OCLP, RestrictEvents etc. May be now you lose this patches?

  • Like 2

Okay, let's talk about some digressions.

WhateverGreen is unable to properly guide the recovery mode and first OTA update of macOS Tahoe as of now.

Although there have been many modified versions of WEG, it has only been achieved by abandoning all patches for AMDSupport.kext.This is an extremely unstable approach and will directly result in WEG not being able to apply the correct connectors.

 

I found that when using BaseSystemKernelExtendes.kc as the kernel cache in the system, WhateverGreen immediately freezes at KextLog:... once it hooks AMDSupport. This affects the boot recovery mode and the second stage of OTA. But when starting the normal system, SystemKernelExtendes.kc is used, and WhateverGreen's patch for AMDSupport is working properly. What is the reason for this? Is there any difference between AMDSupport.kext in these two KCs?

 

What a strange question I haven't found the exact reason yet, do you have any ideas?

 

Best regards.

  • Like 1
On 10/28/2025 at 7:31 AM, Slice said:

But Tahoe will not work with 2013 Mac there should be >2019. If you had success then you had some patches like OCLP, RestrictEvents etc. May be now you lose this patches?

@Slice my good German friend, what you're writing is wrong!!
Why shouldn't it continue to run on an iMac late 2013 (27 inch) after Beta9 or RC1, back when I stopped using it?

I have version 26.1 25B77 running successfully.
See my screenshot. The name "MacBook Pro" is still in there by accident from the image cloned from the 2019 MacBook Pro using CCC.

Everything runs in slow motion, and otherwise, apart from graphics support, everything else works again.

And the Windows server constantly crashes as soon as you try to open a large folder or a large image.

It's definitely no fun to work with it, let alone test it. I'm continuing to use Sequoia 15.7.1 on another partition,

which runs flawlessly and is good.

I've been busy with friends and acquaintances in the last few weeks, and now, purely out of curiosity,

I've started messing around with this stupid Tahoe again.

I can't stand Tahoe anyway, especially that stupid Liquid Crystal (water) interface.

Well, you can just disable that nonsense, that's not a problem, but even without that, I don't like it at all.

iMac-Tahoe 26.1 Beta-25B77.jpg

Everythings is correct for BUILD-OCLP-Mod tahoe-test branch

Thanks @laobamac_yyds to merging my PR ✌️

 

If you want Build OCLP-Mod tahoe-test branch

If you want Build OCLP-Mod main branch

 

Edited by chris1111
  • Like 5
  • Thanks 1
2 hours ago, chris1111 said:

Everythings is correct for BUILD-OCLP-Mod tahoe-test branch

Thanks @laobamac_yyds to merging my PR ✌️

 

If you want Build OCLP-Mod tahoe-test branch

If you want Build OCLP-Mod main branch

 

You might find the information mentioned here useful for your Hackintosh, but it's irrelevant for my late 2013 iMac;

I don't need any of it.

 

The only thing I needed and successfully installed was My Kextinstaller to restore the AppleHDA.kext file.

So version 26.1 (25B77) is running perfectly, although everything is a bit slow due to the lack of graphics support

and the Wi-Fi isn't working (which I don't need anyway), but otherwise it's fine.

Hey laobamac,

 

I'm currently encountering a problem with the AutoPkg-Assets.pkg.zip generated by OCLP and I'm hoping for some expert advice or a solution.

 

Under macOS Tahoe 26.2, the AutoPkg-Assets.zip generated by OCLP appears to be incomplete and far too small (only 663 bytes). Specifically,

the package is corrupted, as all the kexts, scripts, and configuration files that AutoPkg needs to create a functional EFI package are missing.

Because of this, I cannot complete the patching process, and the creation of a bootable EFI folder fails.

 

The second problem is that I cannot find a suitable AutoPkg-Assets.pkg.zip for macOS Tahoe 26.2 on the official sources. Only the checksum (SHA-256)

for a version exists, but the corresponding download link or a release with the complete file is not available. Without these assets, working with OCLP

under the current macOS version is practically impossible.

 

My questions:

Is there an officially supported version of the AutoPkg-Assets for macOS Tahoe 26.2 that I can download?

 

If not, how can I generate a complete version of the assets myself so that AutoPkg runs correctly?

 

Is there a recommended workaround until an updated version is officially provided?

 

I would prefer not to use older assets from previous macOS versions, as there are compatibility risks involved. I hope for a detailed guide on how to

correctly obtain or generate the assets for macOS Tahoe 26.2 so that I can use OCLP fully again.

 

Please don't be concerned that everything is displayed in German. I deliberately changed the language to be able to use the tool, as I don't have

any Chinese language skills.

 

Thanks for your help!

 

 

Edit: 

Alternatively, could someone please upload the latest complete AutoPkg-Assets.pkg.zip from OCLP v3.0.0 here?

I want to install macOS Tahoe 26.2 on another partition and patch the hardware that is currently not recognized correctly

 

Bildschirmfoto 2025-11-08 um 12.00.54 AM.png

37 minutes ago, spakk said:

Hey laobamac,

 

I'm currently encountering a problem with the AutoPkg-Assets.pkg.zip generated by OCLP and I'm hoping for some expert advice or a solution.

 

Under macOS Tahoe 26.2, the AutoPkg-Assets.zip generated by OCLP appears to be incomplete and far too small (only 663 bytes). Specifically,

the package is corrupted, as all the kexts, scripts, and configuration files that AutoPkg needs to create a functional EFI package are missing.

Because of this, I cannot complete the patching process, and the creation of a bootable EFI folder fails.

 

The second problem is that I cannot find a suitable AutoPkg-Assets.pkg.zip for macOS Tahoe 26.2 on the official sources. Only the checksum (SHA-256)

for a version exists, but the corresponding download link or a release with the complete file is not available. Without these assets, working with OCLP

under the current macOS version is practically impossible.

 

My questions:

Is there an officially supported version of the AutoPkg-Assets for macOS Tahoe 26.2 that I can download?

 

If not, how can I generate a complete version of the assets myself so that AutoPkg runs correctly?

 

Is there a recommended workaround until an updated version is officially provided?

 

I would prefer not to use older assets from previous macOS versions, as there are compatibility risks involved. I hope for a detailed guide on how to

correctly obtain or generate the assets for macOS Tahoe 26.2 so that I can use OCLP fully again.

 

Please don't be concerned that everything is displayed in German. I deliberately changed the language to be able to use the tool, as I don't have

any Chinese language skills.

 

Thanks for your help!

 

 

Edit: 

Alternatively, could someone please upload the latest complete AutoPkg-Assets.pkg.zip from OCLP v3.0.0 here?

I want to install macOS Tahoe 26.2 on another partition and patch the hardware that is currently not recognized correctly

 

 

 

image.png.14935370aa4cb439db9e27979d24fe7c.png

You have to run OCLP-Mod.pkg

  • Like 1
46 minutes ago, chris1111 said:

 

 

image.png.14935370aa4cb439db9e27979d24fe7c.png

You have to run OCLP-Mod.pkg

 

Hi Chris,

 

when I double-click on "OCLP-Mod.pkg", the following error appears:

 

"The process could not be completed. (com.apple.installer.pagecontroller error -1.)
Opening "OCLP-Mod.pkg" failed."

 

This is clear evidence that the package is corrupt or incomplete. The file is only 662 bytes, whereas a reasonably complete AutoPkg-Assets.pkg should typically be around 750–800 MB.

 

Edit:

 

The problem is not related to my translation, as the original code has not been modified. The same issue occurs exactly the same with the original, unmodified OCLP-Mod version.

 

It is very likely that laobamac has withdrawn the file, as the package is still in progress. Therefore, the AutoPkg-Assets.pkg.zip cannot be downloaded properly, because the download link is currently inactive.

  • Like 2
1 hour ago, spakk said:

 

Hi Chris,

 

when I double-click on "OCLP-Mod.pkg", the following error appears:

 

"The process could not be completed. (com.apple.installer.pagecontroller error -1.)
Opening "OCLP-Mod.pkg" failed."

 

This is clear evidence that the package is corrupt or incomplete. The file is only 662 bytes, whereas a reasonably complete AutoPkg-Assets.pkg should typically be around 750–800 MB.

 

Edit:

 

The problem is not related to my translation, as the original code has not been modified. The same issue occurs exactly the same with the original, unmodified OCLP-Mod version.

 

It is very likely that laobamac has withdrawn the file, as the package is still in progress. Therefore, the AutoPkg-Assets.pkg.zip cannot be downloaded properly, because the download link is currently inactive.

If you are using my script I made an update that fixed a disk image problem, @laobamac_yyds made a commit to this.

so I recommend using the latest script available. Remove previous clone repos then use the command for Tahoe

 

Edited by chris1111
  • Like 2

Hi

It seems that the OCLP-Mod you installed does not contain PKPKG. If you are using the script compilation OCLP-Mod of @chris1111, please use the latest version.

If not, please make sure that you have downloaded the latest Pre-release and installed OCLP-Mod.pkg correctly.

  • Like 3
10 hours ago, chris1111 said:

If you are using my script I made an update that fixed a disk image problem, @laobamac_yyds made a commit to this.

so I recommend using the latest script available. Remove previous clone repos then use the command for Tahoe

 

 

It doesn’t work for me. I get the same error messages with both the original source code and the translated source code

Bildschirmfoto 2025-11-08 um 1.23.50 PM.png

Bildschirmfoto 2025-11-08 um 1.43.16 PM.png

  • Like 1

@spakk you try to download Install macOS Tahoe Beta from OCLP-Mod

As for me, my script is only for building OCLP-Mod on the tahoe-test branch.
For the rest, ask laobamac_yyds

  • Like 2
×
×
  • Create New...