Contribute
Register

Help with first build of hackintosh stuck at apple logo with the following errors and warnings

Status
Not open for further replies.
Thanks for the detailed response. Here is the newly updated clover according to your instructions and the bios settings.
190514040307.jpg
190514040405.jpg
190514040506.jpg
190514040647.jpg
190514040659.jpg
190514040729.jpg
190514041126.jpg
190514041133.jpg
190514041424.jpg
 

Attachments

  • CLOVER.zip
    3.9 MB · Views: 53
Update

Referring to

I try to replace the ApfsDriverLoader-64.efi in Clover/drivers64UEFI with this attachment to solve the error BlockSize: 512LegacyApfsContainerScan: Block device not supportedSuccess
 

Attachments

  • ApfsDriverLoader-64.efi
    11.8 KB · Views: 55
Update

The 512LegacyApfsContainerScan: Block device not supportedSuccess error seems to be gone. However, it is stuck at the same place at the loading bar and then reboot. This shows the content in the verbose mode.View attachment 405634View attachment 405635View attachment 405636View attachment 405637View attachment 405638View attachment 405639View attachment 405640
  • I have not checked all your uploaded BIOS screen shots in detail. But the Boot Configuration _Boot Option Priorities caught my attention of Samsung SSD 970 EVO Plus 5000 as boot Options # 3.
    • This I suspect is your Target for ,macOSMojave 10.14.4 Installation [probably it contains Windows also per verbose boot screen referring to NTFS]
  • I have never used Samsung SSD 970 EVO Plus 5000 but I have read a few posts that say it is not compatible with macOSMojave.
  • I have also seen reports of issues with Radeon VII as Graphics in Mojave
    • Please verify these hardware issues by searching for successful macOSMojave installation using this Graphics and NVME-M2 SSD first, before going on with installation.
  • There are other issues in your uploaded CLOVER Folder and questions on BIOS choice
    • but, until you select compatible hardware for macOSMojave, discussing problems with CLOVER or other parts of uploaded BIOS are not relevant.
 
Thanks for your reply.
I am actually installing the macOSMojave 10.14.4 in the Toshiba 1TB SATA3 Desktop Hard Disk but not the Samsung SSD 970 EVO Plus 5000.
I have heard that MacOS beta 10.14.5 can fully support Radeon VII which i assume is what I should try now.
Looking forward to your reply
 
Thanks for your reply.
I am actually installing the macOSMojave 10.14.4 in the Toshiba 1TB SATA3 Desktop Hard Disk but not the Samsung SSD 970 EVO Plus 5000.
I have heard that MacOS beta 10.14.5 can fully support Radeon VII which i assume is what I should try now.
Looking forward to your reply

  • Do you already have Windows 10 installed on that Toshiba 1TB ?
    • Whatever disk you install macOSMojave (which has the Clover Efi bootloader that is a common Bootloader for Mac, Windows, Linux from BIOS to CBM screen) on, must be made the FIRST boot Device in Boot Options after installation.

  • At the time of installation make your macOSMojave Installer UEFI USB disk as Boot Option #1.
    • Disable other disks from Boot Option Priorities List until macOS Install is completed.
  • You cannot have a combination of Windows 10 on Legacy Boot Mode and macOS Mojave on UEFI Mode.
    • In that case Mojave may be a No Show in CBM screen.

  • Even with Mojave 10.14.5 Beta, the folks who have installed a lot of Hackintosh and tweak a lot to fix problems seem to have a tough time.
  • Since I don't have Radeon VII PCIE Graphics , I cannot try and simulate problems and fixes to help.
    • You are on your own or someone who has more experience will read this post and come to your help.
 

Attachments

  • 1.BIOS_Boot Option Priorities.png
    1.BIOS_Boot Option Priorities.png
    256.6 KB · Views: 47
  • 2.Verbose boot .png
    2.Verbose boot .png
    264.7 KB · Views: 52
Samsung EVO + is not compatible. I picked one up for testIng and the only way to get it to not panic was to format in fat32.
Thank you for your information. However, as I try to install it in the hard drive, I assume it should not be a problem.
 
Status
Not open for further replies.
Back
Top