Jump to content

[Pre Release] macOS Tahoe 26.1

Anto65

By Anto65,
in New Releases and Updates

 Share
246 posts in this topic

Recommended Posts

johnnyl
johnnyl
Posted
Posted
14 minutes ago, Anto65 said:

macOS Tahoe 26.1  ( 25B5042k )

 

Full Installer

https://swcdn.apple.com/content/downloads/62/37/082-91384-A_0BMCHXL7GY/4snmpwei4sxl2lqru0tjgn6k63t3t1bpi3/InstallAssistant.pkg

 

Thanks Anto65. That's what I've been waiting for bro.

Vasya Katanyan
Vasya Katanyan
Posted
Posted
On 9/23/2025 at 10:04 AM, kaoskinkae said:

I have verified that it is necessary to install both kernels, the one from the beta itself and the 79m where the AppleHDA is included.

Kernel Debug Kit 26 build 25B5042k Latest

Kernel Debug Kit 26.0 build 25A5279m

Done. Kernel Debug Kit 26 build 25B5042k Latest too.

https://developer.apple.com/download/all/?q=Kernel%20Debug%20Kit

kaoskinkae
kaoskinkae
Posted
Posted

There's still no news on when the issue of installing or updating Tahoe on our system will be resolved. As we know, since we're using beta 1, it first lacked Polaris support, and then we lost AppleHDA.kext audio support.

 

As we know, in order to install or update the system, both the betas as I mentioned, as well as the official version and beta 26.1, it's necessary that the WhateverGreen.kext be disabled on the first reboot. After that, the update or installation can be completed with the kext enabled.

 

My question is: Is this problem related only to the WhateverGreen.kext or is it involved in Lilu.kext or OpenCore? I still don't see that the issue has been resolved. A modified kext was released here, but it didn't work correctly.

 

image.png.905b3fe3cdd559c4cd9fc7441e70158c.png

  • Like 3
28862886
28862886
Posted
Posted
18 hours ago, kaoskinkae said:

There's still no news on when the issue of installing or updating Tahoe on our system will be resolved. As we know, since we're using beta 1, it first lacked Polaris support, and then we lost AppleHDA.kext audio support.

 

As we know, in order to install or update the system, both the betas as I mentioned, as well as the official version and beta 26.1, it's necessary that the WhateverGreen.kext be disabled on the first reboot. After that, the update or installation can be completed with the kext enabled.

 

My question is: Is this problem related only to the WhateverGreen.kext or is it involved in Lilu.kext or OpenCore? I still don't see that the issue has been resolved. A modified kext was released here, but it didn't work correctly.

 

image.png.905b3fe3cdd559c4cd9fc7441e70158c.png

i think this is you looking for,WhateverGreen.kext supported from first install stage to the end no need disabled or boot arg,

 

kaoskinkae
kaoskinkae
Posted
Posted
3 hours ago, 28862886 said:

i think this is you looking for,WhateverGreen.kext supported from first install stage to the end no need disabled or boot arg,

 

But this is not a solution, it is a park and it no longer works.

  • Like 1
fabiosun
fabiosun
Posted
Posted
1 hour ago, kaoskinkae said:

But this is not a solution, it is a park and it no longer works.

What do you mean?

It is working but acidanthera devs said the merge cant be done for now due some problem for lilu compatibility..

I use it till a better solution will be found

  • Like 4
kaoskinkae
kaoskinkae
Posted
Posted (edited)
7 minutes ago, fabiosun said:

¿Qué quieres decir?

Está funcionando, pero los desarrolladores de Acidanthera dijeron que la fusión no se puede realizar por ahora debido a algunos problemas de compatibilidad con Lilu.

Lo usaré hasta que se encuentre una mejor solución.

I will try it in the next available beta and prepare an informative video on my channel.  Thank you for pointing out what I asked, which is also a problem related to lilu.kext.

Edited by kaoskinkae
  • Like 2
mnfesq
mnfesq
Posted
Posted (edited)
On 9/23/2025 at 8:45 AM, johnnyl said:

Don't know what happened. The installation to 26.1 went ok but after OCMOD did its thing and restarted Ive been stuck in a boot loop. Anyone got any tips about this?

 

I am having the same problem but I have determined that the problem is not OCLP-Mod itself.  It's the combination of the version of OCLP-Mod you are using and the KDK that you have on your system.  If you are doing an upgrade, you are probably using a version of KDK that doesn't work with the version of OCLP-Mod you are using.  I know this because I did a fresh install of Tahoe on a test partition and then installed the most recent version of OCLP-Mod. It chose the version of KDK to install and everything worked perfectly.  I then upgraded my system partition to Tahoe 26.1 beta and installed the latest version of OCLP-Mod.  It installed a different version of KDK than the one it installed on my fresh install and I got the boot loop that you are stuck with.  You can try something but it didn't work for me.  Try this:

 

Go into recovery mode, select Utilities->Terminal

In Terminal, type:

 

mount -uw /Volumes/YourVolumeName (whatever the name you have given your partition on which you installed Tahoe)

bless --mount /Volumes/YourVolumeName --bootefi --last-sealed-snapshot

reboot

 

That might work for you depending on what type of boot loop you are having.

 

Edited by mnfesq
  • Like 2
johnnyl
johnnyl
Posted
Posted
7 hours ago, mnfesq said:

 

I am having the same problem but I have determined that the problem is not OCLP-Mod itself.  It's the combination of the version of OCLP-Mod you are using and the KDK that you have on your system.  If you are doing an upgrade, you are probably using a version of KDK that doesn't work with the version of OCLP-Mod you are using.  I know this because I did a fresh install of Tahoe on a test partition and then installed the most recent version of OCLP-Mod. It chose the version of KDK to install and everything worked perfectly.  I then upgraded my system partition to Tahoe 26.1 beta and installed the latest version of OCLP-Mod.  It installed a different version of KDK than the one it installed on my fresh install and I got the boot loop that you are stuck with.  You can try something but it didn't work for me.  Try this:

 

Go into recovery mode, select Utilities->Terminal

In Terminal, type:

 

mount -uw /Volumes/YourVolumeName (whatever the name you have given your partition on which you installed Tahoe)

bless --mount /Volumes/YourVolumeName --bootefi --last-sealed-snapshot

reboot

 

That might work for you depending on what type of boot loop you are having.

 

Thanks but I already sorted this out by reinstalling in recovery mode.

Zevgoli
Zevgoli
Posted
Posted
On 9/30/2025 at 8:09 AM, johnnyl said:

Thanks but I already sorted this out by reinstalling in recovery mode.

I had to do this for the same reason but now I am back on the desktop with potentially the same problem.  Can I go into OCLP mod and pick the correct KDK that I had before and install that?

 

Cheers, Howard 

BALDY_MAN
BALDY_MAN
Posted
Posted
On 9/28/2025 at 9:22 AM, kaoskinkae said:

But this is not a solution, it is a park and it no longer works.

you could try updated your open core to 1.0.6

using a 7.1 Mac id to install

use a gpu frame buffer for the card your using  (and not use whatever green kext)

if you wish

kaoskinkae
kaoskinkae
Posted
Posted
10 hours ago, BALDY_MAN said:

Podrías intentar actualizar tu núcleo abierto a 1.0.6

Usando un ID de Mac 7.1 para instalar

usa un frame buffer de gpu para la tarjeta que estás usando (y no uses cualquier kext verde)

Si lo deseas

In this case, if you have to modify something, it's easier to prepare a USB with the kext unchecked and then let the system boot from the computer on the last reboot. We'll wait for you to resolve the issue with WhateverGreen.kext, Lilu.kext, and Opencore 10.0.6.

Zevgoli
Zevgoli
Posted
Posted

OK.  So I tried again to update graphics with OCLP Mod and I let the app do its own thing.  This upon reboot initiated a crash and burn.  So I recovered again and got to my slow desktop.  Ive decided to delete the app and wait till the official OCLP patcher comes out.

 

Cheers, Howard

mnfesq
mnfesq
Posted
Posted
On 10/4/2025 at 6:52 AM, Zevgoli said:

OK.  So I tried again to update graphics with OCLP Mod and I let the app do its own thing.  This upon reboot initiated a crash and burn.  So I recovered again and got to my slow desktop.  Ive decided to delete the app and wait till the official OCLP patcher comes out.

 

Cheers, Howard

 

See if this helps.

 

 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...