macos sequoia support (15.x)

[TK50P]

Will it added for macos 15.x?

[jzrodriguez98]

itlwm + Helliport works in Sequoia. Are you asking about Airportitlwm kext?

[TK50P]

Yes, I meant Airportitlwm

[arg0WAK]

and Bluetooth firmware.

[jzrodriguez98]

and Bluetooth firmware.

Have you tried this one for Bluetooth in Sequoia?

https://github.com/OpenIntelWireless/IntelBluetoothFirmware/actions/runs/10912951904

[Daasin]

Isn't this like the third duplicate now? Seems like it'd make it less likely to be helpful if all the voices are split across multiple issues

[dvision1979]

Check here for bluetooth on Sequoia:
https://elitemacx86.com/threads/how-to-fix-intel-wifi-and-bluetooth-on-macos-sequoia-and-later.2066/#-step-4-add-bluetooth-parameters
Works like a charm.

[AOE33]

Yes, I meant Airportitlwm

yes, it's work now! Via fake device id as brcm native wifi-bt card and then patch OCLP for IOSkywalkFamily.kext IOSkywalkFamilyLegacy.kext
see this

[chteow]

yes, Airportitlwm now work with the workaround that provided by @sughero. <- Thanks :)
@zxystd might want to add this temporary workaround to README.

Attached the screenshot of some complain about airplay after patch with workaround.
Not sure whether it useful for fixing the Airportitlwm.kext.

[dvision1979]

Hi @chteow ,
Where is the workaround, can you share a link?
Does it work on normal Hackintosh or only in OCLP?

[chteow]

Hi @chteow , Where is the workaround, can you share a link? Does it work on normal Hackintosh or only in OCLP?

It working on OCLP, Workaround

[vanyasem]

Duplicate of #1009

[Mishaal9]

sequoia.txt
For anyone who has problems with audio, bluetooth and wifi not working. Tried on Skylake (spoofed to Kabylake as needed).

[Daasin]

Duplicate of #1009

@vanyasem Which itself is a duplicate of 983. Everything seems to be off-topic too :/

[FotoFotoCheck]

please stop with this type of topic. THERE'S NO SEQUOIA SUPPORT ATM AND THIS IS A ISSUE GITHUB NOT A REQUEST BOARD.
so, please, post only issue related. And NO, sequoia not supporting is NOT issue.

[AOE33]

Yes, I meant Airportitlwm

yes, it's work now! Via fake device id as brcm native wifi-bt card and then patch OCLP for IOSkywalkFamily.kext IOSkywalkFamilyLegacy.kext see this
Metod writelln by @sughero work at Sequoia 15.1

[adrianyujs]

Need real kext for Sequoia :)

[sughero]

Yes, I meant Airportitlwm

yes, it's work now! Via fake device id as brcm native wifi-bt card and then patch OCLP for IOSkywalkFamily.kext IOSkywalkFamilyLegacy.kext see this
Metod writelln by @sughero work at Sequoia 15.1

I keep getting credits for something I just quoted.
Anyways the magic is still working on Sonoma 15.1.
You need to remove the "#" in order to trick OCLP and let it think you have a Broadcom. As with the update all root patches are undone. Once you removed the comment and rebooted OCLP will ask you to patch your kext, let it do the job, put "#" to comment back that section and don't forget to clear your NVRAM in order to get Bluetooth working again.
Be aware that this "trick" is far from beeing the perfect solution.
If you haven't done it and have some concerns about security, you probably want to use Helix app with itlwm.kext instead.
In this way you would keep full SIP (ie 0000000) enabled instead of lowering to 03080000 as shown with the following command:

Nerone:~ david$ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
Nerone:~ david$

I point it out as, even though this seems an elegant way to get Wi-Fi working it requires your system loads an unsigned kext to work, on the other side if you use itlwm.kext with Heliport you have an alternative to the "native" macOS wi-fi but on the other side your system is completely protected with SIP fully enabled.

[Tinnci]

Yes, I meant Airportitlwm是的，我的意思是 Airportitlwm

yes, it's work now! Via fake device id as brcm native wifi-bt card and then patch OCLP for IOSkywalkFamily.kext IOSkywalkFamilyLegacy.kext see this是的，现在开始工作了！通过假设备 ID 作为 brcm 本机 wifi-bt 卡，然后为 IOSkywalkFamily.kext 修补 OCLP IOSkywalkFamilyLegacy.kext请参阅此
Metod writelln by @sughero work at Sequoia 15.1Metod writelln by @sughero在 Sequoia 15.1 工作

I keep getting credits for something I just quoted.我不断因为我刚才引用的内容而获得积分。 Anyways the magic is still working on Sonoma 15.1.无论如何，Sonoma 15.1 的魔力仍在发挥作用。 You need to remove the "#" in order to trick OCLP and let it think you have a Broadcom. As with the update all root patches are undone. Once you removed the comment and rebooted OCLP will ask you to patch your kext, let it do the job, put "#" to comment back that section and don't forget to clear your NVRAM in order to get Bluetooth working again.您需要删除“#”才能欺骗 OCLP 并让它认为您拥有 Broadcom。与更新一样，所有根补丁都被撤消。删除注释并重新启动后，OCLP 会要求您修补 kext，让它完成工作，将“#”注释回该部分，并且不要忘记清除 NVRAM 以使蓝牙再次工作。 Be aware that this "trick" is far from beeing the perfect solution.请注意，这个“技巧”远非完美的解决方案。 If you haven't done it and have some concerns about security, you probably want to use Helix app with itlwm.kext instead.如果您还没有这样做并且对安全性有一些担忧，您可能希望将 Helix 应用程序与 itlwm.kext 结合使用。 In this way you would keep full SIP (ie 0000000) enabled instead of lowering to 03080000 as shown with the following command:通过这种方式，您将保持启用完整的 SIP（​​即 0000000），而不是降低到 03080000，如以下命令所示：

Nerone:~ david$ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
Nerone:~ david$

I point it out as, even though this seems an elegant way to get Wi-Fi working it requires your system loads an unsigned kext to work, on the other side if you use itlwm.kext with Heliport you have an alternative to the "native" macOS wi-fi but on the other side your system is completely protected with SIP fully enabled.我指出，尽管这看起来是一种让 Wi-Fi 工作的优雅方式，但它需要您的系统加载未签名的 kext 才能工作，另一方面，如果您将 itlwm.kext 与 Heliport 一起使用，您可以选择“本地” “ macOS Wi-Fi，但另一方面，您的系统通过完全启用的 SIP 受到完全保护。

is it feasible to use heliport while fixing bluetooth support? or it might also need disable SIP partially. i'm using ax210 and the bluetooth won't work.

[AOE33]

Yes, I meant Airportitlwm是的，我的意思是 Airportitlwm

yes, it's work now! Via fake device id as brcm native wifi-bt card and then patch OCLP for IOSkywalkFamily.kext IOSkywalkFamilyLegacy.kext see this是的，现在开始工作了！通过假设备 ID 作为 brcm 本机 wifi-bt 卡，然后为 IOSkywalkFamily.kext 修补 OCLP IOSkywalkFamilyLegacy.kext请参阅此
Metod writelln by @sughero work at Sequoia 15.1Metod writelln by @sughero在 Sequoia 15.1 工作

I keep getting credits for something I just quoted.我不断因为我刚才引用的内容而获得积分。 Anyways the magic is still working on Sonoma 15.1.无论如何，Sonoma 15.1 的魔力仍在发挥作用。 You need to remove the "#" in order to trick OCLP and let it think you have a Broadcom. As with the update all root patches are undone. Once you removed the comment and rebooted OCLP will ask you to patch your kext, let it do the job, put "#" to comment back that section and don't forget to clear your NVRAM in order to get Bluetooth working again.您需要删除“#”才能欺骗 OCLP 并让它认为您拥有 Broadcom。与更新一样，所有根补丁都被撤消。删除注释并重新启动后，OCLP 会要求您修补 kext，让它完成工作，将“#”注释回该部分，并且不要忘记清除 NVRAM 以使蓝牙再次工作。 Be aware that this "trick" is far from beeing the perfect solution.请注意，这个“技巧”远非完美的解决方案。 If you haven't done it and have some concerns about security, you probably want to use Helix app with itlwm.kext instead.如果您还没有这样做并且对安全性有一些担忧，您可能希望将 Helix 应用程序与 itlwm.kext 结合使用。 In this way you would keep full SIP (ie 0000000) enabled instead of lowering to 03080000 as shown with the following command:通过这种方式，您将保持启用完整的 SIP（​​即 0000000），而不是降低到 03080000，如以下命令所示：

Nerone:~ david$ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
Nerone:~ david$

I point it out as, even though this seems an elegant way to get Wi-Fi working it requires your system loads an unsigned kext to work, on the other side if you use itlwm.kext with Heliport you have an alternative to the "native" macOS wi-fi but on the other side your system is completely protected with SIP fully enabled.我指出，尽管这看起来是一种让 Wi-Fi 工作的优雅方式，但它需要您的系统加载未签名的 kext 才能工作，另一方面，如果您将 itlwm.kext 与 Heliport 一起使用，您可以选择“本地” “ macOS Wi-Fi，但另一方面，您的系统通过完全启用的 SIP 受到完全保护。

is it feasible to use heliport while fixing bluetooth support? or it might also need disable SIP partially. i'm using ax210 and the bluetooth won't work.

heliport is only wifi client for itlwm.kext. You must find lastest BlueToolFixup.kext+IntelBluetoothFirmware.kext+IntelBTPatcher.kext adapted for Sequoia and +two parameters in NVRAM
bluetoothExternalDongleFailed 00
bluetoothInternalControllerInfo 00000000 00000000 00000000 0000

[Tinnci]

Yes, I meant Airportitlwm是的，我的意思是 Airportitlwm

yes, it's work now! Via fake device id as brcm native wifi-bt card and then patch OCLP for IOSkywalkFamily.kext IOSkywalkFamilyLegacy.kext see this是的，现在开始工作了！通过假设备 ID 作为 brcm 本机 wifi-bt 卡，然后为 IOSkywalkFamily.kext 修补 OCLP IOSkywalkFamilyLegacy.kext请参阅此
Metod writelln by @sughero work at Sequoia 15.1Metod writelln by @sughero在 Sequoia 15.1 工作

I keep getting credits for something I just quoted.我不断因为我刚才引用的内容而获得积分。 Anyways the magic is still working on Sonoma 15.1.无论如何，Sonoma 15.1 的魔力仍在发挥作用。 You need to remove the "#" in order to trick OCLP and let it think you have a Broadcom. As with the update all root patches are undone. Once you removed the comment and rebooted OCLP will ask you to patch your kext, let it do the job, put "#" to comment back that section and don't forget to clear your NVRAM in order to get Bluetooth working again.您需要删除“#”才能欺骗 OCLP 并让它认为您拥有 Broadcom。与更新一样，所有根补丁都被撤消。删除注释并重新启动后，OCLP 会要求您修补 kext，让它完成工作，将“#”注释回该部分，并且不要忘记清除 NVRAM 以使蓝牙再次工作。 Be aware that this "trick" is far from beeing the perfect solution.请注意，这个“技巧”远非完美的解决方案。 If you haven't done it and have some concerns about security, you probably want to use Helix app with itlwm.kext instead.如果您还没有这样做并且对安全性有一些担忧，您可能希望将 Helix 应用程序与 itlwm.kext 结合使用。 In this way you would keep full SIP (ie 0000000) enabled instead of lowering to 03080000 as shown with the following command:通过这种方式，您将保持启用完整的 SIP（​​即 0000000），而不是降低到 03080000，如以下命令所示：

Nerone:~ david$ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
Nerone:~ david$

I point it out as, even though this seems an elegant way to get Wi-Fi working it requires your system loads an unsigned kext to work, on the other side if you use itlwm.kext with Heliport you have an alternative to the "native" macOS wi-fi but on the other side your system is completely protected with SIP fully enabled.我指出，尽管这看起来是一种让 Wi-Fi 工作的优雅方式，但它需要您的系统加载未签名的 kext 才能工作，另一方面，如果您将 itlwm.kext 与 Heliport 一起使用，您可以选择“本地” “ macOS Wi-Fi，但另一方面，您的系统通过完全启用的 SIP 受到完全保护。

is it feasible to use heliport while fixing bluetooth support? or it might also need disable SIP partially. i'm using ax210 and the bluetooth won't work.

heliport is only wifi client for itlwm.kext. You must find lastest BlueToolFixup.kext+IntelBluetoothFirmware.kext+IntelBTPatcher.kext adapted for Sequoia and +two parameters in NVRAM bluetoothExternalDongleFailed 00 bluetoothInternalControllerInfo 00000000 00000000 00000000 0000

Problem solved! I'm really grateful. It is really helpful, kext here and your quirks solved the problem. :) Thanks again.