Jump to content
16 posts in this topic

Recommended Posts

Fast and painless sequential OTA update (1.13 GB) from macOS 26.5.1 (25F80) to macOS 26.5.2 (25F84).

 

image.png.5cccd38a8abadfb2e72be93e16b5d4e7.png

 

image.png.a7e97aaa00d8c5d0bc88779b699a304c.png

 

image.png.199fb1a4c11035014e132968e4599d21.png

 

OCLP correctly selects Kernel Debug Kit 26.5.2 build 25F84 as the direct match. It has already been released by Apple and is now also available on the Dortania KDK mirror.

 

image.png.fa57321429a29220063e4ff6a6992c79.png

 

My BCM943602CDP continues to perform amazingly with OCLP. Modern Audio, modern Wi-Fi, AirDrop, AirPlay, Screen Mirroring, Personal Hotspot, Continuity Camera and sleep/wake all continue to work flawlessly under macOS 26.5.2.

 

image.png.09ddfca89a9a6973f676fcbac5ed9420.png

 

image.png.84c3410a04f2682522416b66c2db884f.png

 

Custom drive icons also continue working flawlessly.
 

image.thumb.png.9c94c052e85ce1454be85421948f36f4.png

 

Useful context information:

a.) Universal-EFI-Folder distribution

b.) Setup and troubleshooting guidelines for OCLP/OCLP-Mod/OCLP-Plus

c.) OCLP 3.0.0 Nightly - amfipassbeta Edition

d.) OCLP-Mod

e.) OCLP-Plus

f.) WiFiPatcherPro

g.) HDAUniversal

h.) X299 Guidelines

Edited by kgp
Kernel Debug Kit 26.5.2 build 25F84 now also available at the dortania KDK mirror
  • Like 5
14 hours ago, miliuco said:

@fantomas and admins

Can you merge this thread and the one with the same name, posting by @kgp? I guess that @kgp did not noticed that there already was a thread about 26.6.

 

I was asking @fantomas via PM if he could create a new release thread for macOS 26.5.2. He replied that I could do it as well, so I created the thread. Unfortunately, @fantomas created the same thread about two minutes later without noticing mine. It was simply an unfortunate timing issue, which I also just realized some time ago. 

The best solution would be to merge the two threads. Since Fantomas has not replied to the PM for a couple of hours, I also added @Allan so one of them can take care of it.

Staff Note
Message added by fantomas,

Actually, it's my topic that was created two minutes before yours, and when I tried to merge them (by deleting mine and keeping only yours), it displayed my comment first precisely because it was created before yours.

  • Like 3
4 minutes ago, miliuco said:

@kgp

My mistake was thinking that your thread was created after @fantomas, sorry.

Anyway, I hope that admins merge the 2 threads.

 

My thread has already been merged into @fantomas’ thread. Apparently, the issue has already been resolved. :wink_anim:

  • Like 3

Smooth unattended update.  This one was a little messy, because I performed it while making pizza dough.  My HackBookPro is now christened with flour and yeast. :hysterical:

 

Disable Beta updates to get this one...

Spoiler

Screenshot2026-06-29at8_40_33PM.png.9391200e7b1ee6a17b1185ab2cf74ea8.png

 

 

Screenshot2026-06-29at9_23_41PM.png.e71591a09f68cfbe718c0548546000a8.png

Edited by deeveedee
  • Like 5

Well for me  the installation process is now becoming the same every time I update.  Everything seems to go ok and I get to my desktop and am able to move around fine.  Rebooting I get that same old screen "you have been updated to Tahoe" and that's it.  I'm now in the process of reinstalling via Recovery and eventually will use a Time Machine backup to restore my profile.

 

Sigh....

 

Cheers(I think),  Howard

  • Like 2

You all know the hassles Ive been having updating from one version to another.  I was thinking could it be a boot arg that is causing the problem?

 

Here are the ones I am currently using:

 

-igfxvesa revpatch=sbvmm -btlfxboardid brcmfx-country=#a revpatch=auto npci=0x2000 amfi_get_out_of_my_way=1

 

Are there any here that might be a red flag to anyone?

 

Thanks for any help.

 

Cheers, Howard

@Zevgoli I don't use revpatch in boot-args (I insert revpatch in NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102), so I don't know the boot-arg syntax, but I'm suspicious of having two revpatch= statements in boot-args.  The syntax that I know is revpatch=arg1,arg2 (the revpatch arguments are comma delimited).

 

Also, depending on which macOS you're running, I don't think that amfi_get_out_of_my_way=1 works any more.  I don't think you should be using it at all (I'd prefer using AMFIPass.kext if you're using it for OCLP), but that's just my preference.  If you actually need it, then you probably should be using amfi=0x80 instead.

 

Whenever you're asking questions about your config.plist, it's best to post the entire config.plist.

  • Like 1
×
×
  • Create New...