[SOLVED] Can't Install Mojave Security Update 2019-001 10.14.6

[asharkey]

Hello,

Anyone else having issues with the latest security update 2019-001 10.14.6 for Mojave?

Have never had issues updating since 10.14.2 in the past. But this once gets stuck on these last 4 lines:
"
Adding AGDP mode validate property
iMac.local com.apple.xpc.launchd[1] (org.ntp.sntp.188) <Warning>: Servuce exited with abnormal code: 1
considerRebuildOfPrelinkedKernel com.apple.nke.webcontentfilter trigger reguild
Forcing CS_RUNTIME for entitlement: com.apple.rootless.install iMac.Local com.apple.xpc.launchd[1] (com.apple.displaypolicyd.200) <Warning>: Service exited with abnormal code: 1
"

The only way to boot is to force shutdown and overide boot from the system volume and bypass the Mac OS Install volume.

Doing a bit of research from similar issues with users and security updates most boot problems are caused/resolved by fixing:

Location of Kexts (virtualsmc in Clover's "/kexts/Other/", latest kexts installed with ##### in L/E/ with cache updated by Kext utility)
The Injection of Kexts (i've tried both detect and inject = yes)
Mismatched Kext (fakesmc + virtual smc both in use, which they are not)
A bad config.plist (works booting the normal system voluem, i've attached)
A graphic injector issue (currently using iMac18,3 + RX580 with the UHD630 in a headless state)
Multiple Drivers Folder - The old clover /driversuefi64/ folder present and conflicting with the latest /drivers/uefi/ folder (only /drivers/uefi/ present)

The only thing that is different from this update than previous updates is that I transitioned to VirtualSMC from previously using FAKESMC/ FAKESMCsensors kexts with previous Mojave releases.

I uninstalled the FAKESMC and all the sensors kexts using terminal and the following command and can confirm they are not present in the Clover "other folder" or the /L/E/ folder.
sudo rm -rf /Library/Extensions/".....".kext

After transitiong to VirtualSMC I did read with the readme that the VirtualSmc.efi should be placed in the /drivers/UEFI/ folder in clover. So I have added that to the EFI/CLOVER/DRIVERS/UEFI/ folder manually. Can anyone confirm if this is necessary?

I've attached my config.plist file and screenshots of the verbose readout stalling as well.

Any guidance would be great!


KEXTS I'VE INSTALLED IN /L/E/:
WhateverGreen.kext
VirtualSMC.kext
USBInjectAll.kext
SMCSuperIO.kext
SMCProcessor.kext
Lilu.kext
IntelMausiEthernet.kext
BrcmPatchRAM3.kext
BrcmFirmwareRepo.kext
BrcmBluetoothInjector.kext
AppleALC.kext
AirportBrcmFixup.kext

configNOSN.plist

Edited December 6, 2019 by valueimagery

[ntsmkfob]

You may be getting the mismatched kexts msg because Fakesmc is still in the cache. Rebuild your cache to remove it completely.

[asharkey]

Thanks for the reply @ntsmkfob I believe i have rebuilt my cache using both KextUtility and the following command in terminal sudo kextcache -i /

 

Is there another way to do so?

[asharkey]

I do notice another common error:

updated VERBOSE READING (attached)

com.apple.xpc.launchd.domain.system

<error>: Could not read path: path = /Library/LaunchDaemons, error=2: No suchfile or directory

<error>: Failed to bootstrap path: path = /Library/LaunchDaemons, error=2: No suchfile or directory

<error>: assertion failed: 18G1012: launchd + 205994 [BBD445B6-FBA9-3A9C-828F-A112F63E2080]: 0X9

<warning> Endpoint has been activated through legacy launch(3) APIs. Okease switch to XPC or bootstrap_check_in()

 

I've checked my system library and root library folders and there is LaunchDaemons folder present, so not sure why that error would be populating, unless the file needed is not there?

 

[asharkey]

Okay so I've reverted to completing formating the APFS system drive.  Created a FAT partition with a mojave installer disk utility and then Made it a APFS again.  Cloned my CCC working clone to the new parition.  Boots fine, no issues, actually faster.

 

But i still can't update to this latest security update.

 

@PMheart I found this thread from January where someone had a simliar issue with "kextd stall[1], (240s): 'AppleACPICPU'" updating Mojave when they never an issue before which required a patch that eventually an updated Clover bootloader fixed.  Is this 10.14.6 2019 security release something similiar that would require a clover update?

 

 

Edited November 30, 2019 by valueimagery