About Catalina OTA updates, a little clarification (nothing to worry about) your personal datas are safe and user will be migrated correctly without issues
however seems that apple from 10.15.2 has a bit changed the OTA stages, they were since Mojave usually two stages, but I have counted this time let's say three, here are:
OTA stage1 : download of OTA packages and pre-installation (with the "macOS Install Data" temporary volume) showing an apple logo with a enough quick loading bar followed by a reboot
OTA stage2 : installation from "macOS Install Data" OTA volume showing an apple logo with a fast loading bar and a Catalina circle GUI logo with a slow loading bar with "
About X minutes remaining" followed by another reboot
OTA stage3 : OTA post-install script showing a 3/4 of loading bar followed by a direct boot to the GUI Mode (but in case of Core2Duo by a bootloop)
After OTA stage3 from 10.15.2 seems Apple have enhanced their "telemetry" infact a welcome screen is showed with new Analytics (that can't be refused) and new improved Siri (that can be refused).
The fact is: if you apply the dosdude1 post install patches before the OTA stage3 you will encounter a bootloop, because regardless the patches applied, the OTA stage3 uses its embedded prelinkedkernel with a stock IOSurface.kext, so the kernel panic will be due not only to the telemetry.plugin (already removed) but also to that mismatching with a IOSurface.kext patched and a stock one in OTA prelinkedkernel. (so maybe
@ASentientBot consider your new fix for keeping the stock IOSurface.kext)
In any case this is easily fixable, booting in safe mode (or with "-no_compat_check -x" in nvram ), the OTA stage3 will continue without issues, and after you can re-apply the post-install patches or using the
@ASentientBot method of rebuild kextcache from single user mode:
Code:
mount -uw /
mount -uw /System/Volumes/Data
kextcache -system-prelinked-kernel
kcditto
reboot
So to avoid any issues my advise is
let all the OTA stages and in particular the OTA stage3 to autocomplete without applying any patches, otherwise you might (or might not) encounter that described minimal issue, but very easily fixable.