While you motherboard, CPU and discrete GPU are all compatible with the AMD Vanilla process, your Crucial NVME SSD isn't. It uses a Silicon Motion Controller, which is known to be problematic when used as a macOS Boot drive.
Do you have an alternative drive you can use for macOS, preferably one that is compatible with macOS, i.e. older Gen3 and Gen4 Western Digital or SanDisk are normally the best options for use as a macOS boot drive.
corpnewt has 99 repositories available. Follow their code on GitHub.
github.com
Have you created a Debug version of the OpenCore EFI folder? So you can obtain the MmioWhitelist entries for your system, this is essential if you are to get Tahoe running on your system.
v1.0.7 Improved XhciPortLimit compatibility with macOS Tahoe, thx @laobamac Updated builtin firmware versions for SMBIOS and the rest Migrated to edk2-stable202511
github.com
Have you created a UTBMap.kext for your USB ports with USBToolBox Tool in Windows?
the USBToolBox tool. Contribute to USBToolBox/tool development by creating an account on GitHub.
github.com
Were you aware that the AMD 800-series of motherboards can be problematic when it comes to installing macOS, specifically Tahoe, as it has some peculiar requirements when being installed.
Have you thought of installing Sequoia first and then updating to Tahoe, just to make sure your system will comfortably run macOS.
Booting Windows and macOS from the same drive isn't a great idea, especially for someone new to AMD Hackintosh setups. Also the best process for doing as you plan is to install macOS first, and then add Windows to a separate Partition on the drive. The reasoning behind this is that the EFI partition needs to be the first (hidden) partition on the drive for macOS to boot. Windows doesn't have the same requirement.
As to your UTBMap.kext, are you aware that it isn't compatible with macOS Tahoe. It will work perfectly well with Sequoia or an older version of macOS, but not with Tahoe. Apple made some changes to the naming conventions used for USB ports and connector types, which UTBMap doesn't include. Installing Sequoia for example would allow you to generate another USB kext such as USBMap.kext or USBPorts.kext that is compatible with Tahoe.
When creating an EFI for Tahoe you need to keep the /EFI/OC/Kexts folder contents to a minimum, as some non-essential kexts are known to cause boot issues and kernel panics when included in the OC setup. This includes WhateverGreen.kext / NootedRed.kext / NootRX.kext I.e. the graphics kext all of which need to either be removed or disabled before attempting to install Tahoe. They can be added back or enabled once macOS Tahoe has completed the installation.
Apple removed AppleHDA.kext from macOS Tahoe, as none of their retained Intel systems use the old Audio kext. What this means for most Hackintosh systems is that the built-in Realtek Audio Codec won't work with AppleALC.kext as would be expected. AppleHDA.kext needs to be added back in to Tahoe as a post-installation process before you will get your Audio working. USB audio codecs don't have the same issue, they will usually work out of the box (OOB) with no additional kexts required.
Nie jestem w tym do końca obeznany, ale udało mi się to kiedyś zrobić, używając innych komponentów. AM5 wydaje się być poza moim zasięgiem. Być może będę musiał poszukać pomocy z zewnątrz, żeby ktoś zbudował mój EFI i plik config.plist od początku do końca, w oparciu o wspomniane przeze mnie komponenty.
Nie jestem w tym do końca obeznany, ale udało mi się to kiedyś zrobić, używając innych komponentów. AM5 wydaje się być poza moim zasięgiem. Być może będę musiał poszukać pomocy z zewnątrz, żeby ktoś zbudował mój EFI i plik config.plist od początku do końca, w oparciu o wspomniane przeze mnie komponenty.
I'm not fully familiar with it, but I managed to do it once, using other components. The AM5 seems to be out of my reach. I may have to seek outside help so that someone builds my EFI and config.plist file from start to finish, based on the components I mentioned.
That being the case, I wish you luck on your journey. I would offer to do some of the work, but without having the system to hand I would be wasting my time, simply because it isn't a straightforward process. They will be a lot of trial and error testing and editing to get a working EFI for your AMD AM5 system, same as there was for mine and everyone else's.
W takim przypadku życzę ci powodzenia w twojej podróży. Zaoferowałbym wykonanie części pracy, ale bez systemu pod ręką marnowałbym swój czas, po prostu dlatego, że nie jest to prosty proces. Będą dużo prób i błędów testowania i edycji, aby uzyskać działający EFI dla twojego systemu AMD AM5, tak samo jak dla mojego i wszystkich innych.
I'm bringing this up again! I managed to get to the installer after a long struggle, but when I load the installer, this appears and then the installer starts normally, but I can't use the mouse and keyboard. Ugh...
That image means your Bluetooth isn’t working. You may need to use a wired mouse/keyboard or one with its own USB dongle (Logitech combo set).
Which WiFi/BT card are you using, I.e. make and model of the card is required.
How is the card mounted in your system, using the builtin M.2 connection or on an adapter card in a PCIe slot?
If a PCIe slot do you have the adapter connected to a USB motherboard header port, as the Bluetooth module won’t work without this cable being connected correctly.
If a builtin M.2 connector, have you created a custom USB configuration for your system, which includes the USB port attached to the M.2 connector?
Whichever of the two ways the Bluetooth device is connected it would need the USB header to be configured correctly as an ‘Internal’ USB port with connector type (255).
Please don’t say it works in Windows, as Windows and macOS have different requirements for the same Bluetooth device to work.
Does the mouse or keyboard work, when the system is at the 19 minutes remaining stage?
How long have you left the system, to see if the installation continues at the 19 minutes remaining stage? Sometimes the installation can appear to have stalled, but in reality it is still running the installation process in the background.
Unfortunately, the mouse doesn't respond at all, it freezes and you can't do anything at all.. I've tested it many times, 1-2 hours of waiting, the same thing.. as if it suddenly lost control of everything that was happening and the toilet came out.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
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.
