Contribute
Register

Cannot boot Mojave Installer or OS: Asus H370-I BIOS version 2012

Status
Not open for further replies.
Joined
Jun 19, 2017
Messages
16
Motherboard
Asus H370-I
CPU
i7-9700K
Graphics
RX580
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Desperately hoping someone can help.

Setup:
Asus H370-I motherboard
Intel i7-9700K
Samsung 970 EVO 1TB (Mojave)
Samsung 970 EVO 512GB (Windows 10)
Corsair DDR4 3000
Sapphire Pulse RX580
Broadcom WiFI card from old Mac

I have previously installed Mojave and Windows on this setup; all went relatively smoothly with minimum changes to EFI. I'd only been using it for a few days, and everything seemed to work. Yesterday however I foolishly decided to upgrade the motherboard BIOS to version 2012 (released Jan 2019). Since then I have been completely unable to boot Mojave or the MacOS Installer. Windows continues to boot without problem.

Symptoms:
Booting normally results in black screen with Apple logo. Progress bar reaches 40% at normal speed and then slows to a crawl. It does eventually reach ~100% (10 minutes ish) but just stays there.
Booting in verbose mode (photo attached) suggest it is stalling very early in the boot process. Similar messages booting the OS or the installer. I don't know it is has crashed or stalled. Single user or safe mode net the same result.

I'm guessing the message regarding APFS is misleading. The line:
AppleNVMe Assert failed: (0 != data ) ReleaseIDNode line: 5484
looks the most relevant. Searching elsewhere suggests this could either be a USB issue (USBInjectAll is used), or something else.

I have of course tried resetting the CMOS, recreating the EFI etc.

Any thoughts appreciated. EFI content attached. If I can provide any more information please let me know.
 

Attachments

  • IMG_3408.JPG
    IMG_3408.JPG
    3.1 MB · Views: 172
  • EFI 2019-02-11.zip
    3.2 MB · Views: 111
I have just attempted to boot with:
  1. The Broadcom card remove
  2. Both Samsung 970 EVO cards removed

It crashes or stalls in approx the same place, but with no messages re NVMe so I guess it is safe to rule them out.

Interesting message re nvram available. Thoughts?
 

Attachments

  • IMG_3410.JPG
    IMG_3410.JPG
    3.2 MB · Views: 128
Desperately hoping someone can help.

Setup:
Asus H370-I motherboard
Intel i7-9700K
Samsung 970 EVO 1TB (Mojave)
Samsung 970 EVO 512GB (Windows 10)
Corsair DDR4 3000
Sapphire Pulse RX580
Broadcom WiFI card from old Mac

I have previously installed Mojave and Windows on this setup; all went relatively smoothly with minimum changes to EFI. I'd only been using it for a few days, and everything seemed to work. Yesterday however I foolishly decided to upgrade the motherboard BIOS to version 2012 (released Jan 2019). Since then I have been completely unable to boot Mojave or the MacOS Installer. Windows continues to boot without problem.

Symptoms:
Booting normally results in black screen with Apple logo. Progress bar reaches 40% at normal speed and then slows to a crawl. It does eventually reach ~100% (10 minutes ish) but just stays there.
Booting in verbose mode (photo attached) suggest it is stalling very early in the boot process. Similar messages booting the OS or the installer. I don't know it is has crashed or stalled. Single user or safe mode net the same result.

I'm guessing the message regarding APFS is misleading. The line:
AppleNVMe Assert failed: (0 != data ) ReleaseIDNode line: 5484
looks the most relevant. Searching elsewhere suggests this could either be a USB issue (USBInjectAll is used), or something else.

I have of course tried resetting the CMOS, recreating the EFI etc.

Any thoughts appreciated. EFI content attached. If I can provide any more information please let me know.
  • Is this EFI from the current Mojave System Disk you cannot login?
    • Did you get the EFI through Windows?
 
The EFI is from the Installer USB. Since the problems is the same booting this as booting the OS I thought this would be sufficient.
  • This USB's EFI has some problem that can affect booting. I have uploaded the edited CloverFileTree.
  • config.plist ACPI is blank , you may need several patches
  • config.plist_Boot can be improved
  • config.plistRt VariablesCsrActiveConfig must be 0x67
  • If previous SMBIOS iMac 14, 2 worked OK, it is OK to use; or can be changed to iMac 18,1 for your H370.
 

Attachments

  • CloverFileTree_AJBaker.png
    CloverFileTree_AJBaker.png
    108.3 KB · Views: 278
cmn699, thanks for your input. I appreciate your time.

I have updated the file tree, VariablesCsrActiveConfig and SMBIOS name as per your suggestion. Lili, WhateverGreen, AppleALC and XHCI-unsupported all copied to kexts/Other.

Still a very similar problems persists. Photo attached. (NVMe and Broadcom cards inserted.)

I'll be honest, I'm not sure what you mean by ACPI may need patches and Boot can be improved. Appreciate they are sections of config.plist, but I'm not sure where to even begin identifying what may be worth changing.

While I appreciate upgrading the BIOS makes this irrelevant, I keep reminding myself that this was all working before with no changes to the config.
 

Attachments

  • IMG_3411.JPG
    IMG_3411.JPG
    2.7 MB · Views: 128
hello ajbaker, i have the same motherboard as you. I made the same mistake to update the bios version 2012. I tried everything, while my configuration worked very well. I also think that there has been a change in the bios that prevents the smooth operation. I even tried a new blank installation but the result is the same
 
hello ajbaker, i have the same motherboard as you. I made the same mistake to update the bios version 2012. I tried everything, while my configuration worked very well. I also think that there has been a change in the bios that prevents the smooth operation. I even tried a new blank installation but the result is the same

Seems we have effectively bricked our motherboards! Let this be a lesson to others. Thanks for letting me know.
 
Seems we have effectively bricked our motherboards! Let this be a lesson to others. Thanks for letting me know.

Seems we have effectively bricked our motherboards! Let this be a lesson to others. Thanks for letting me know.
VirtualSMC EFI module is broken
 
Status
Not open for further replies.
Back
Top