iATKOS | United Kingdom

Guide Step by Step: Understanding the Problem : Your PC is not recognizing the drive with macOS Catalina as bootable. The drive is formatted as APFS (Case Sensitive), but shows as “bootable: no” in macOS Utilities. Bootable Flag and APFS Formatting : The issue may relate to the drive not being flagged as bootable. APFS (Case Sensitive) format is correct, but the bootable flag needs to be set. Verify Boot Mode Compatibility : Ensure that your BIOS/UEFI settings are compatible with your macOS installation. If Catalina was installed in UEFI mode, ensure that your BIOS is set to UEFI, not Legacy or CSM. Use OpenCore Configurator for EFI Partition : Follow the advice of Goodcitizen177. Use OpenCore Configurator to access and modify the EFI partition on your SSD. Copy the EFI folder from your installation USB (which has a working bootloader) to the EFI partition of your SSD. Making the Drive Bootable : Boot into macOS Recovery or use a bootable macOS USB. Open Terminal from the Utilities men...

Guida Passo Passo: Identificare il Problema: Verifica il messaggio di errore o la problematica specifica che si verifica all'avvio. Ciò potrebbe indicare se il problema è relativo al BIOS, al bootloader o alla configurazione del disco. Configurazione del BIOS: Accedi al BIOS del tuo computer premendo il tasto appropriato durante il processo di avvio (di solito F2, F10, DEL o ESC). Controlla l'ordine di boot per assicurarti che il disco giusto sia impostato come prima opzione di avvio. Verifica dei Dischi: Assicurati che tutti i dischi siano riconosciuti correttamente nel BIOS. Se un disco non viene rilevato, verifica i cavi di connessione e l'alimentazione o prova a collegarlo a una porta diversa. Riparazione del Bootloader di Windows: Se Windows non si avvia, potrebbe essere necessario riparare il bootloader. Crea un supporto di installazione di Windows 11 e usa gli strumenti di ripristino per riparare il bootloader. Questo può includere comandi come bootrec /fixmbr , boot...

The error message WaitSecsForNotBusy: : 3905:Port 0 PxTFD: 0x150 typically points to an issue related to the storage controller or the communication between the motherboard and the storage device. When installing macOS on a Hackintosh, especially with AMD CPUs like your Ryzen 7 5800X, it's important to ensure that the EFI configuration is correctly set up for AMD systems, as they require specific patches and adjustments. Here are some troubleshooting steps you can take: Verify AHCI Mode : Ensure that your BIOS is set to AHCI mode for SATA operation. This is necessary for macOS to communicate correctly with your drives. Check Storage Kexts : Ensure you have the appropriate kexts for your storage controller. For AMD systems, you might need third-party kexts that support the controller on your ROG STRIX B550-F motherboard. Update BIOS : Make sure your motherboard's BIOS is updated to the latest version, as this can resolve compatibility issues. Correct SSDT and DSDT Patches : Mak...

The message "Forcing CS_RUNTIME for entitlement: com.apple.private.security.kext-management" is typically related to issues with kernel extension (kext) management in Hackintosh setups, particularly when using OpenCore as a bootloader. In the context of your MSI MPG Z490 GAMING EDGE WIFI with an Intel Core i7-10700k, here's a troubleshooting guide: Troubleshooting Steps: Ensure Correct Kext Versions : Verify that all your kexts are up to date and compatible with the version of macOS you are trying to run. Proper Kext Ordering : In your OpenCore config.plist , ensure that the kexts are loaded in the correct order. For example, Lilu.kext should be loaded before WhateverGreen.kext , and VirtualSMC.kext should be loaded before any other SMC-related kexts. Verify SIP Settings : Make sure that System Integrity Protection (SIP) settings are correctly configured in your config.plist . Incorrect SIP settings can cause issues with kext loading. Review Secure Boot Settings : In so...

GUIDE STEP BY STEP: Back Up Your System: Before proceeding with any changes, ensure you have a complete backup of your system. Access the Boot Loader Configuration File: Navigate to the root directory of your system drive. Locate the /Extra folder. Modify org.chameleon.Boot.plist: Inside the /Extra folder, find the org.chameleon.Boot.plist file. Open it with a plain text editor like TextEdit or nano. Edit SMBIOS Properties: Look for the SMBIOS section within the plist file. If you cannot find it, you may need to add it manually. Specify the SMproductname with a Mac model that closely matches your hardware configuration. Set SMbiosversion , SMfamily , and other relevant keys to match your actual CPU details. Adjusting Frequency and Core Information: Add or edit CPU Frequency and Core Count properties if available. The exact keys can vary, so you might need to look up the Chameleon documentation for precise naming. Save the Changes: After making the necessary edits, save the file...

Solution: Given your MSI MAG Tomahawk B460, Intel Core i7-10700K, XFX Radeon RX 6600 XT, and 24GB RAM DDR4 setup, and the difficulties in passing through verbose mode in a Hackintosh environment, consider the following steps: Verbose Mode for Diagnosis: Booting in verbose mode is crucial for diagnosing where the process is halting. Use the boot flags -v -f to enable verbose mode and rebuild the kext caches, which is important especially if the installer has not updated them properly​​. Correct Boot Flags: The agdpmod=pikera flag is specific to AMD GPUs and helps to prevent black screen issues. debug=0x100 and keepsyms=1 are useful for debugging purposes. If they are not providing any useful output, you can temporarily remove them. The SMBIOS change from iMac20,2 to MacPro7,1 needs careful consideration. Ensure that the chosen SMBIOS is the most compatible with your hardware configuration. Graphics Compatibility: The XFX Radeon RX 6600 XT should generally be compatible, but ensure...

Adding BOOT Option for macOS on ASUS ROG STRIX X570-E Gaming Motherboard Target Audience: Intermediate users with experience navigating BIOS settings and Hackintosh installations. Solution: 1. Update BIOS: Ensure your BIOS is updated to the latest version available from ASUS. An outdated BIOS may not support certain functionalities. 2. Prepare EFI Partition: Make sure that the EFI partition on your macOS drive is correctly set up with the necessary bootloader (like Clover or OpenCore). 3. BIOS Settings: Within BIOS, disable 'Fast Boot' and 'Secure Boot'. These settings can prevent custom boot options from being added. 4. Boot from Shell: Some BIOS interfaces do not provide an option to add a custom boot path through the GUI. Instead, use an EFI shell to manually add your macOS drive as a boot option. 5. Check File System Structure: Your EFI partition should have the following structure: `/EFI/BOOT/BOOTx64.efi` and `/EFI/OC/OpenCore.efi` (for OpenCore). The BIOS looks fo...

The issue you're experiencing with being stuck on the "support.apple.com/mac/startup" screen during a Hackintosh installation could be related to several factors. Here are some troubleshooting steps based on your specific hardware (Powerx H310C motherboard) and the use of a USB 3.0 pendrive on a USB 2.0 port: Solution: Target Audience:** Intermediate to Expert Hackintosh users. 1. Check BIOS Settings:**    - Ensure that the BIOS is set to UEFI mode, not Legacy.    - Disable Secure Boot.    - Set the USB drive as the first boot device. 2. USB Port Compatibility:**    - Although using a USB 3.0 drive in a USB 2.0 port shouldn't be an issue, try using a USB 2.0 pendrive if possible.    - Alternatively, try a different USB port, preferably a USB 3.0 port if your motherboard has one. 3. Correct Boot Loader and Configuration:**    - Ensure you are using the right bootloader for your Hackintosh setup (such as Clover or OpenCore). ...

SOLUTION: Target Audience : Expert Hackintosh and Multi-OS Users Objective: Successfully add BlissOS, an Android-based OS, to the OpenCore bootloader menu alongside other operating systems. Solution Overview: Adding BlissOS to OpenCore can be tricky since Android OS bootloaders behave differently compared to traditional Linux or Windows bootloaders. Steps to Add BlissOS to OpenCore: Review OpenCore Configuration : Ensure your config.plist is set up correctly for multi-OS booting. Verify that your OpenCore version is up-to-date as newer versions might have better support for various OSes. Custom Entry for BlissOS : Create a custom entry in config.plist under the Misc section for BlissOS. Use the BlessOverride feature if necessary to point directly to the BlissOS bootloader file. Check BlissOS Installation Path : Confirm that BlissOS EFI files are correctly placed in the EFI partition. They should be in a distinct folder within the EFI partition. Partition Type and File System : Ensu...

SOLUTIONS: Target Audience: Intermediate Hackintosh Users Solution Overview: Booting into the macOS installer using only a touchscreen on a Hackintosh setup can be challenging, especially with limited USB ports. This guide provides a method to achieve this without needing a physical keyboard and without using OpenCanopy. Step-by-Step Guide: Prepare Your Bootable USB Drive : Create a macOS installer USB using a different computer, if you haven't already. Ensure the USB drive has the necessary bootloader (Clover or OpenCore) and macOS installation files. Configure Bootloader for Touchscreen : Access the bootloader configuration file (e.g., config.plist for Clover or OpenCore). Enable any touchscreen support options available. For OpenCore, this might involve enabling certain drivers or kexts that support touch input. Modify Bootloader GUI Settings : Adjust GUI settings to enlarge buttons or simplify the interface for easier touch navigation. If using Clover, modify the theme settin...

Boot looping Efi😞 i7600hq Buddy, the i7-6700HQ CPU should be working fine with your Hackintosh setup. It's probably just a minor hiccup. Here's the ultimate solution for you: Reboot in Verbose Mode: As soon as the system starts booting, hit the boot key and select the "-v" option. Watch the text closely, and you'll find the villain causing this mess. Head to EFI Folder: Open the config.plist file and scroll to the line that caused the error in verbose mode. Tweak it a bit or just delete it. You know what you're doing. BIOS Trick: Go into the BIOS and switch something on and off. Just trust your instincts; you'll find the right switch. Boot from USB: If all else fails, grab that USB stick you used to install macOS, boot from it, and do a quick repair. Piece of cake! submitted by /u/Techman989 [link] [comments] [► Source]

Hi all: I'm planning to build a machine that will be running 10.13 High Sierra. I do use a couple WinDOS programs, but not very often. So I ask: should I make my machine a dual-boot with two drives (one macOS and one WinDOS 7), or just one drive with macOS and use Parallels to run the stuff that I sometimes need? I do have a couple of concerns: I've seen that Dell machines all have a blue SATA port ("SATA 0" on each and every one) and that's always where the boot drive gets plugged in... Read more [► Source]

Hi All, I recently installed macOS Monterey and macOS Ventura to a dedicated drive on my multiboot system (Opencore 0.8.8). After installing macOS Monterey I added an APFS Volume for installing macOS Ventura but after completing it I noticed that opening Disk Utility in macOS Monterey the macOS Monterey volume appears as a System Snapshot whereas the macOS Ventura volume does not: Conversely, the same behavior occurs when opening Disk Utility in macOS Ventura... Read more [► Source]

Hi, I'm on OC 0.8.4 with monterey 12.5.1. Since I've updated my hackintosh from Big Sur, now when I boot my computer I can't launch windows from it. If I select it on the menu I have only a black screen and it freeze. If I boot my computer on the windows drive selected with the bios, windows launch normally. how can I fix that please ? [► Source]

Extreme noob, but I want to create a new bootable partition for windows AFTER all of my initial setup. I would like to use the same ssd drive, but I’m so scared I’ll break my system. I can’t figure out which guide to follow, so please can anyone help a noob out and point me in the right direction? [► Source]

Hey guys pls help me out. I cant find any linux entries in my OC bootloader. Installed hackintosh from v img(catalina). Linux installed in my 149gb partition in same drive. But cant see any option to boot in linux. Pls help. Link to all settings in my hackintosh - https://www.insanelymac.com/uploads...1-04.mp4.78bbd71aafd05c51f95ed9bb2fe3545a.mp4 0:00 1:36 [► Source]

A very common issue when multibooting macOS/OS X with Windows and Linux is that after installing the latter the computer will only boot to them. The reason for this is that Clover does not automatically add itself to the UEFI firmware boot menu that is accessible by pressing F12 or another hotkey. When no other operating systems or boot managers are present the computer will automatically start Clover from the UEFI fall back path at EFI\Boot\BootX64.efi which may be present on the menu as an... Read more [► Source]

My build has 2 separate NVME drives, one for OS X Monterey and another for Windows 10. I originally created the Windows disk using boot camp, then deleted boot camp and ran it with Parallels for the last 4 years. I updated open core and I can still boot Windows 10 from the opencors picker menu no problem. Unfortunately I can no longer boot the same partition from Parallels. I now get this error: I set it up something like this as best I can remember: Create a new VM... Read more [► Source]

Can someone post a screen shot of the files that are in their boot camped windows EFI partition please? [► Source]

I installed Windows 10 on a new SSD. I already had Catalina on its own SSD for the same system. So... If I put BOTH of those back in, I am assuming that the Windows Boot Loader and my OC EFI will leave each other alone. And, if selecting the macOS boot EFI as default in BIOS, OpenCore 'should' recognize the Windows Boot Loader...Right? But, with the required BIOS settings for Catalina and Windows being so different, how do we manage the situation without changing the BIOS settings each time? [► Source]