Mojave running great until updated Clover

[cman44]

I recently upgraded from 10.13.3 to 10.14 and it's been running for the most part good, besides some random crashing. I updated my clover today and now it will not boot. It just reboots when click on it in Clover. The only way for me to boot is through my clover on my flash drive. Any ideas?

 

[Amylowellow]

impossible to tell without any sort of error/panic message. boot in verbose mode.

 

[cman44]

Here is all it shows me in verbose https://d.pr/i/dclLpF

 

[Gigamaxx]

Here is all it shows me in verbose https://d.pr/i/dclLpF

Boot with the USB and then mount the EFI of drive and USB and drag the USB EFI folder to the drive and replace.
The new clover updates remove the OSXAptiofix drivers. When running clover use the customize tab and select aptiomemoryfix and apfsautoloader. Get rid of aptiofix and apfs files. The new setup will automatically detect the apfs file so you don’t have to update it for each update.

 

[perchard]

The same thing happened to me (I see https://d.pr/i/dclLpF in verbose mode).

I installed Mojave through the app store. Everything was working except Ethernet (which is why I updated Clover - thought it might resolve). I updated Clover (via the pkg) to the latest and can no longer boot.

cman44, which version of clover are you booting from on your flash drive? I'll try creating a USB bootable clover so I can hopefully get back in and follow Gigamaxx's recommendation.

EDIT: Looks like this might be the issue: https://www.tonymacx86.com/threads/solved-clover-update-r4586-disables-os-boot-black-screen.256050/ Will follow the recommended steps and provide an update.

EDIT2: I was having the same issue a few other posters cited at the post linked from the above edit where the shift key was not working in the clover shell, meaning drives could not be mounted (as the command to do so required a colon). I did however find the bootable USB I used to originally install High Sierra, which had an earlier version of clover (4334) on it I could use to boot into Mojave. Will try Gigamaxx's recommendation and post another update.

EDIT3: I followed the guidance from the post linked in my first edit and successfully resolved the issue, by copying the following files from the `EFI-BACKUPS/rxxxx/YYYY-MM-DD-xxxxx/EFI/CLOVER/drivers64UEFI/` folder (located in the root of the drive on which MacOS is installed) to the corresponding `drivers64UEFI` folder of my EFI drive:

1. OsxAptioFix2Drv-64.efi
2. OsxFatBinaryDrv-64.efi

Not sure if 2. was needed, but somebody else with a similar motherboard (I have an Asus ROG STRIX Z370-G Gaming, they had a Z170-gaming5) mentioned they needed it, so I copied it anyway.

I mentioned at the beginning of my post the reason for updating Clover was that my Ethernet was not working. Happy to report that updating Clover did resolve this issue.

Now the only problem is that Nvidia has not yet released, and seems unlikely to release soon, web drivers for my GTX 1080. Take a look at this thread for discussion on that matter: https://www.tonymacx86.com/threads/...mojave-10-14-not-available-workaround.260857/

I decided to pick up a Vega 64 and will be selling the 1080. One configuration of the iMac pro uses a Vega 64 (https://www.apple.com/imac-pro/specs/ - the other configuration a Vega 56) so am hopeful MacOS will provide first-class support for a while.

Thanks to everyone who contributed to finding a solution here.

 

[johnsch]

I recently upgraded from 10.13.3 to 10.14 and it's been running for the most part good, besides some random crashing. I updated my clover today and now it will not boot. It just reboots when click on it in Clover. The only way for me to boot is through my clover on my flash drive. Any ideas?

Same here. Had 10.14 working find and then I updated to latest Clover from Clover configurator (from version 4630 to 4674) and get blank black screen. Fortunately I had an earlier version on another hard drive from which I was able to boot and re-install 4630 (from Multibeast 10.4). Repeated this a second time to make sure wasn't a fluke.

 

[perchard]

cman44, I wonder if it might be worth updating the title of this post to include "End RandomSeed +++++++++++++" in the subject, to help others who might be stuck in a similar situation, and searching based on the final output of verbose mode? This is what I was searching for when looking for a solution, and just happened to find this post as it was towards the top of Mojave Desktop Support.