<< Solved >> ASUS TUF Z390M PRO - Installation siezes at apfs module init.

[HackinMax]

I've been at it all day. And, I am finally asking for help.

Installation from Unibeast freezes at apfs module after Broadcom card initialization

I have tried several options found in z390 threads and others.
I have disconnected all SATA drives leaving just the M.2 (PCIe) drive in.
I have used a Linux LIVE drive to completely erase the NVMe... again
I have tried several 'working' EFI folders from this board.
I have swapped out my PowerColor RX570 Red Dragon with a Sapphire RX580 Pulse to see if that was the problem... It wasn't.
I have disconnected my BCM94360CS2 (PCIe X1 adapter) because that should be the next thing the system initializes.
I have recreated the Unibeast stick from scratch and tried again
I have downloaded and updated Lilu.kext, WhateverGreen.kext, AppleALC.kext, IntelMausixxx.kext and every other kext I could update and, placed them in the .../Other folder in the EFI
I have tried several aptio and emu drivers. none of them made any difference.
I have confirmed BIOS settings several times. And, have deleted the Secure Boot keys (only way to disable SB on this thing)

I have scoured the forum But, have not stumbled on the solution.

This system is intended to be a Media Server and backup box for... well everything actually. So, the dGPU is not strictly necessary. I just threw it in there because the iGPU wasn't in the mood to cooperate.

System:
ASUS TUF Z390M Pro
i7 8700K
Ballistix Sport 32GB (2x16Gb)
EVO 970 250Gb (Not plus, Not Pro)
6x WD Red 6Tb *EFRX* Series
Power Color RX570 Red Dragon 8Gb @16x in BIOS
BCM94360CS2 on a PCIex1 adapter card
Corsair H850x PSU

Any assistance appreciated... I would like to avoid turning it into an Amahi server if possible.

[EDIT: removed defective EFI to prevent misunderstandings]

[EDIT 7/10/2019: Through many hours of trial and error, I have finally been rewarded by seeing that wonderful grey screen with "Install MacOS Mojave" emblazoned upon it.

Once I can confirm a successful install, I will be posting the actual Unibeast EFI that finally got it this far.

 

[P1LGRIM]

One thing that immediately stands out is that you have HFSPlus-64.efi and VBoxHfs-64.efi which both do the same job.
You should choose one and delete the other.

Suggest try OsxAptioFix2Drv-free2000.efi - See nickwoodhams.com
May require XHCI-unsupported.kext in /EFI/CLOVER/kexts/Other/. (Click Download repository).
May require a USB Port Limit patch.
May require slide=0 boot flag.

 

[HackinMax]

One thing that immediately stands out is that you have HFSPlus-64.efi and VBoxHfs-64.efi which both do the same job.
You should choose one and delete the other.

Suggest try OsxAptioFix2Drv-free2000.efi - See nickwoodhams.com
May require XHCI-unsupported.kext in /EFI/CLOVER/kexts/Other/. (Click Download repository).
May require a USB Port Limit patch.
May require slide=0 boot flag.

Thank you very much. I am running through these suggestions now. Will update afterwards.

 

[HackinMax]

I just got through running through several combinations.
First, I removed HFSPlus-64.efi... Leaving VBoxHfs-64.efi in place.

A) Replaced aptio fixes with OsxAptioFix2Drv-free2000.efi
B) Tried all three current variations of @PMHeart 's Port limit patches.
C) Inserted slide=0 into boot flags

Tried 'C' alone with previous EFI
Tried 'A' and 'C' together
Tried 'A' ALone with previous EFI
Tried 'A', 'B' and, 'C' all together

Hang still occurs at the same 'place' in the boot process.

Now... I am unable to locate XHCI-unsupported.kext. Maybe I am not looking/searching for the right strings. The link above takes me to Rehabman 's repository for USBInjectAll... But, it doesn't lead me to the XHCI-unsupported.kext download. Could you further advise on acquiring this? This time, I actually READ the instructions you wrote... Got it now. will test after work today.


Also, is it possible this problem is connected to the fact that Linux was previously installed on the SSD?
I used 'Disks' from inside Ubuntu to completely wipe it to free space before attempting an install of MacOS.

 

[P1LGRIM]

Tried all three current variations of @PMHeart 's Port limit patches.

They are not "variations", all are required (but probably won't have any impact at this stage).

Also, is it possible this problem is connected to the fact that Linux was previously installed on the SSD?
I used 'Disks' from inside Ubuntu to completely wipe it to free space before attempting an install of MacOS.

Not very likely.

Make sure that Clover is updated.

 

[HackinMax]

They are not "variations", all are required (but probably won't have any impact at this stage).

I did NOT know that. Thanks.

Make sure that Clover is updated.

Unfortunately, I have had extremely poor luck with Clover updates. I can only get update to the Clover version in the latest version of multibeast.

Never has a Clover update by any other means, not ended in absolute tears for me. So, I truly hope that will NOT be necessary. I still have one of my hacks (MasterZee) that is booting to a "prohibited" symbol due to an attempted Clover update. I managed to get two others to boot again with the original boot loader. So, I will not attempt again until a definitive guide is available to show me what I am doing wrong.

I will try this one again with all three Port Limit patches enabled.

thanks for the clarification.

 

[P1LGRIM]

I will try this one again with all three Port Limit patches enabled.

Four.

I have had extremely poor luck with Clover updates

Luck plays no part.
Earlier versions of Clover noticed what you had previously installed and updated those settings but lately it only updates those items that you select and may delete items that you do not, particularly memory fix drivers.
This leads to problems the next time that you boot.
The moral is : Make sure that you note all of your current items before you update and afterwards check that they are still present before you reboot.

Most people only need :
ApfsDriverLoader-64.efi (or apfs.efi)
AptioMemoryFix-64.efi
FSInject-64.efi
HFSPlus.efi (or vboxhfs-64-efi)

The good news is that each time that you update Clover a copy of your /EFI folder is saved to your system disk in /EFI-Backups. If you have problems following an update you can get back to where you started from by replacing the /EFI folder on the EFI partition with the one from your latest backup.

 

[HackinMax]

I just RE-read @MacMan 's TUF z390 Build guide.

I finally absorbed the fact that he specifically states that the Z390 PRO does not have any USB2.0 connectors - except on the MB-Headers... Well, coincidentally, the Z390M PRO has the same setup - USB2.0 is only available from the mb headers.

This is likely the major problem standing in the way. (?)

Also, in the same post, @MacMan states that...

if you use UEFI version 2203 or later the system will hang during the boot of macOS at apfs_module_start:1393. @mattystonnie has created a patch that fixes this.

I've attached the patch file ASUS_ACPI in a .zip file that you can install using plistbuddy in Terminal after unzipping.

Well, that's exactly where this install is hanging up. So...
In a fit of morbid curiosity, I applied the ASUS-ACPI patch to my (DSDT) config.plist. Of course, it was for a different board. The boot locked at "...Random Seed". So, I removed it.

I will need to go buy a USB 2.0 backplane unit tomorrow to test this theory.

 

[P1LGRIM]

I will need to go buy a USB 2.0 backplane unit tomorrow to test this theory.

It may work if you plug a USB 2 hub into a USB 3 port (worth a try if you have one).

 

[HackinMax]

It may work if you plug a USB 2 hub into a USB 3 port (worth a try if you have one).

Thanks. I'll try that.

...

Well, the one I have isn't even recognized.

Since the lack of USB 2.0 is the elephant in the room. I will need to go purchase that USB backplane tomorrow. If that doesn't work. I don't know what else I can possibly do.