[Help Request] Installing Tahoe on a working Sequoia Ryzentosh

jtcs95

New member
AMD OS X Member
Mar 15, 2026
4
0
1
Portugal
CPU:
7800x3d
Hello, so I have a perfectly working Sequoia build. But I have tried multiples times to install Tahoe with no success. It either bootloop on install (right after apple logo appears) or gets stuck on apple with no progress bar. (I have installed directly from Mac no success, I have made a bootable usb, no success)
I have a 7800x3d cpu, GPU AMD 6950 XT, x870e tomahawk msi, 32gb ram ddr5, no secure boot, 4g enabled...
I already have mapped USB... I am over a week trying to install.
So I decided to ask for some help of someone with more knowledge than I...

Thank you in advance
I attach my efi (I have windows too).
 

Attachments

Tahoe requise a minimalist /EFI/OC/Kexts folder when being installed. As a lot of kexts can cause unnecessary issues if present when installing Tahoe. Your current Kexts folder contents are far from minimal, it should contain only the bare essentials for your system to boot.
  • Lilu.kext
  • VirtualSMC.kext
  • AppleMCEReporterDisabler.kext
  • LucyRTL8125Ethernet.kext
  • USBMap.kext
The simplest way to deal with this issue, as you have an existing Sequoia installation and working EFI, is to disable any non-essential kexts in your config.plist, until you have Tahoe installed and running on your system. This includes NootRX.kext, as this can be one of the main culprits when issues arise during the installation of Tahoe.

OpenCore Legacy Patcher (Dortania release) isn't supported in Tahoe yet. So the OCLP kexts and block entry should be set with a MaxKernel of 24.99.99 so they aren't injected in to Tahoe.


As you have a USBMap.kext, which I assume is working correctly and has been updated to work with Tahoe.
  • That being the case you don't need USBToolBox.kext or UTBDefault.kext in your setup.
  • If that is not the case then it won't work in Tahoe either.
  • You may need to enable the Kernel > Quirks > XhciPortLimit entry to have some working USB ports.

AppleALC.kext isn't natively supported in Tahoe. Before you can use this kext you need to configure your system to inject AppleHDA.kext, which Apple removed from macOS Tahoe. AppleALC.kext won't work without AppleHDA.kext being present and active in the system.

As you are using NootRX.kext you should not be using any DeviceProperties in your config.plist, as this is another way for the kext to behave poorly in macOS.
  1. Use a custom SSDT if the fake device ID is really necessary for your Broadcom WiFi card.
  2. For your Realtek Audio codec use alcid=11 boot argument in place of the DeviceProperties entry.

Try the EFI-v1 folder on a spare USB pen drive, see if this gets your system to boot Tahoe. WiFi & BT won't be working, neither will OCLP, your RX 6950XT dGPU won't have GPU acceleration, until NootRX.kext has the MaxKernel 24.99.99 entry removed.
 

Attachments

  • Like
Reactions: jtcs95
Thanks I could boot installer thanks!
Can i get any direction on how to make Bluetooth, wifi and audio to work? I have installed ocpl 3.1.7 patched, but as soon as i enable those kexts i cant boot again to mac...
 
Is this the MSI motherboard you are using?


That motherboard has a USB Audio so you shouldn't need any kexts to get it working. The kexts that Apple provide should work with the USB device. That assumes you have created a working USBMap.kext for your system, which activates the Audio USB port with the correct Connector Type - (255) Internal.

Neither the Builtin WiFi or Bluetooth that comes with your MSI board will work in macOS, as they are Qualcomm (NCM865) WiFi & BlueTooth modules.

Best thing would be to disable the Qualcomm devices in the Bios and use a compatible Broadcom or Intel WiFi/BT card through a PCIe adapter & motherboard USB2 header port.

The Alternative is to physically remove the Qualcomm card and replace it with a compatible M.2 Broadcom or Intel WiFi/BT card. While this is the neater of the two options it is also the hardest to accomplish, now you have the motherboard installed and setup in your PC case. As to physically remove the Qualcomm card you would need to remove the LED shroud that sits over the rear ports. The screws for which are usually found on the underside of the motherboard.
 
Is this the MSI motherboard you are using?


That motherboard has a USB Audio so you shouldn't need any kexts to get it working. The kexts that Apple provide should work with the USB device. That assumes you have created a working USBMap.kext for your system, which activates the Audio USB port with the correct Connector Type - (255) Internal.

Neither the Builtin WiFi or Bluetooth that comes with your MSI board will work in macOS, as they are Qualcomm (NCM865) WiFi & BlueTooth modules.

Best thing would be to disable the Qualcomm devices in the Bios and use a compatible Broadcom or Intel WiFi/BT card through a PCIe adapter & motherboard USB2 header port.

The Alternative is to physically remove the Qualcomm card and replace it with a compatible M.2 Broadcom or Intel WiFi/BT card. While this is the neater of the two options it is also the hardest to accomplish, now you have the motherboard installed and setup in your PC case. As to physically remove the Qualcomm card you would need to remove the LED shroud that sits over the rear ports. The screws for which are usually found on the underside of the motherboard.
I have added usb Bluetooth port, i will check on audio (might have missed that port somehow).
About wifi, i have the Ax210 Intel (yes, i have replaced it). Is it compatible?
I guess i can live without it.
 
Yes, the Intel AX210NGW M.2 card is compatible with macOS, as long as you use the right kexts and application. There are some limitations when using an Intel WiFi/BT card, but aren't there always.

For the WiFi module you need to add Itlwm.kext to your /EFI/OC/Kexts folder with a corresponding entry in the config.plist. You then need to download and install the Heliport application in macOS. As the Intel WiFi module doesn’t work with the builtin Apple WiFi app when using Itlwm.kext. It is seen as an additional Ethernet interface, not as a WiFi interface.


For the Bluetooth you need these three kexts, in this order in your config.plist.
  1. IntelBluetoothFirmware.kext
  2. IntelBTPatcher.kext
  3. BlueToolFixup.kext
Plus you need to add the following entries to the NVRAM Add & Delete sub-sections in your config.plist.

Bluetooth NVRAM entries.png viewed in Corpnewt's ProperTree plist editor

Plus the Bluetooth USB port being active and set with the correct Connector Type in your USB configuration.
 

Attachments

  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.