macOS 10.15 Catalina on Unsupported Macs

[Larsvonhier]

I definitely don't care if Apple was intentional or not, I reported on the danger from applying the Beta update which still exists. Focusing on side issues is not productive. The issue is Apple has released an update which impairs unsupported Macs, a FACT.

Ok, to be more "productive": I also installed the re-issued sec. update on a MB Air and it did not work, boot (patched and unpatched) ended both in non-login. Drive was not corrupted, still fully mountable and showed some IOUSBfamily error log outputs in verbose mode. Keyboard (internally connected to USB) did also not work, even patched.
Over-Installing the latest official build 19H15 worked as always, perhaps with a slower install process. So no poison pill here, just unsuitable / insufficient patches at the moment. Let´s see what either Apple has in store when they release a full public installer or what can be done in terms of adaptive patches then...

Now starting second attempt to build H1016 (and will save and inspect the package contents when DL is ready).

 

[K two]

Ok, to be more "productive": I also installed the re-issued sec. update on a MB Air and it did not work, boot (patched and unpatched) ended both in non-login. Drive was not corrupted, still fully mountable and showed some IOUSBfamily error log outputs in verbose mode. Keyboard (internally connected to USB) did also not work, even patched.
Over-Installing the latest official build 19H15 worked as always, perhaps with a slower install process. So no poison pill here, just unsuitable / insufficient patches at the moment. Let´s see what either Apple has in store when they release a full public installer or what can be done in terms of adaptive patches then...

Now starting second attempt to build H1016 (and will save and inspect the package contents when DL is ready).

I kept running into "diskmanagement dissenter" errors after the update was applied which pevented the drive from mounting as well as the USB patcher Terminal from mounting the updated drive. So far, the only fix here was erase the drive partition and re-install H15, then was able to get back to H524. PITA

 

[Larsvonhier]

I kept running into "diskmanagement dissenter" errors after the update was applied which pevented the drive from mounting as well as the USB patcher Terminal from mounting the updated drive. So far, the only fix here was erase the drive partition and re-install H15, then was able to get back to H524. PITA

Never happened here to my attempts of installing the H1016 build. Just ended up with an unsuitable patch canon (no login due to black screen with mouse pointer only or login screen but eternal beach ball).
I always still had a mountable boot volume that I could re-install the H15 build to again.

 

[K two]

Never happened here to my attempts of installing the H1016 build. Just ended up with an unsuitable patch canon (no login due to black screen with mouse pointer only or login screen but eternal beach ball).
I always still had a mountable boot volume that I could re-install the H15 build to again.

Could the patches be re-installed from USB? The diskmanagement dissenter errors stopped me cold until the poisoned disk was erased as HFS+ and reformatted APFS.

 

[Larsvonhier]

Could the patches be re-installed from USB? The diskmanagement dissenter errors stopped me cold until the poisoned disk was erased as HFS+ and reformatted APFS.

That's really strange - it went all smooth and re-patching from dosdude´s v1.4.4 USB stick also no problems. And I tried this on various occasions now. Never locked/scrambled my boot volume.

 

[wire_]

It would be super nice for some influencer here to take editorial responsibility for helping regular joes grok that beta updates are not something they want.

As Apple doesn't support our Macs, it's irrelevant as to whether Apple "cares" because by definition, they don't.

As to how much Apple should care, they get to decide, just like the community here gets to decide if we care about keeping older HW going. I'm grateful many do!

If you were a beta tester on a supported Mac, you have to accept that updates will break your ****, so you don't run them on installations with valuable data. And you would have a responsibility to inform developers about the problem so it gets fixed!

I have no idea how these truths got swizzled around into this sense of entitlement to run betas on unsupported configs like they are supported releases!! But presumably it's now clear this is a proper hazard.

As browbeating each other is no way forward, I'm writing this only to clarify to ordinary joes that care is required when using the Cataline OTA update fix, because "betas are probably not what you want."

To those who offer time here supporting the unsupported, thanks! And blessings to you.

That is all

 

[jowaju]

I kept running into "diskmanagement dissenter" errors after the update was applied which pevented the drive from mounting as well as the USB patcher Terminal from mounting the updated drive. So far, the only fix here was erase the drive partition and re-install H15, then was able to get back to H524. PITA

Dissenter errors in Disk Utility is almost exclusively SIP not being fully disabled. Either boot to recovery and disable it (even if it shows disabled when you check), or use the USBAPFSloader to bypass. I see this dozens of times a week, I won't even begin working on one until I've disabled SIP using csrutil disable and rebooted, it's just not worth the hassle.

You can install the USBAPFSLoader alongside your Catalina USB installer, so everything is on the same USB drive and is easy to access.

 

[makra]

As browbeating each other is no way forward, I'm writing this only to clarify to ordinary joes that care is required when using the Cataline OTA update fix, because "betas are probably not what you want."

But is there another way to get public security updates to install?

 

[K two]

Dissenter errors in Disk Utility is almost exclusively SIP not being fully disabled. Either boot to recovery and disable it (even if it shows disabled when you check), or use the USBAPFSloader to bypass. I see this dozens of times a week, I won't even begin working on one until I've disabled SIP using csrutil disable and rebooted, it's just not worth the hassle.

You can install the USBAPFSLoader alongside your Catalina USB installer, so everything is on the same USB drive and is easy to access.

An excellent suggestion, free of brow-beating and patronizing seen here, recently - seriously, THANK YOU. Apparently, a 3-bong NVRAM reset re-enables csrutil on the iMac11,2. Just now made another dual-boot H15/USBAPFSLoader3 USB for the Macs at this location. Thanks for the reminder. ?

 

[K two]

But is there another way to get public security updates to install, yes.

From the SW Update CP -

No more Betas.

 

[Ausdauersportler]

Yes, there is another way to get there... (installed Catalina 19H15 and updated to 19H524 and 19H1067 one hour ago)

​

 

[makra]

From the SW Update CP -

No more Betas.

Right now I'm on 19H1009 (the most recent time machine backup I had...). I can get Beta updates via CatalinaOTAswufix, but if I revert the CP to Defaults, no more updates show up. That's why I had begun with Beta versions in the first place, when full installers stopped.
I guess, I must have missed an important point in this thread... ? Any help?
(@Ausdauersportler Would it do to install 19H15 again and then look for updates? And: It should be a clean install, right?)

 

[wire_]

Sone thoughts:

Updates don't appear to all at precisely the same time.

For me with 19H524, the OTA fix plus SU beta reset didn't produce the available release update immediately. I closed the SU panel and opened again a bit later (30 mins) and it showed up.

If there's something beyond 19H524 it's not yet available to me on a Catalina supported Mac!

There is no reason to be obsessive about security updates. The downside of delayed security updates is usually zilch. Such updates are something to prefer, but very low risk when not immediately available.

As has been reported, fussing to get updates ASAP causes trouble.

I've read zillions of posts here and don't recall even one reporting being jacked by an unpatched security hole. But I've read quite a few saying how dorking around with system adjustments glitched out.

 

[Ausdauersportler]

Not really sure if I should post this right now, but I left the @dosdude1 way completely three month ago starting to build my own OpenCore based special config for iMac12, 2 and 11,x systems (using the @jackluke OC USB installer as a blue print and the list of extension to inject with OpenCore I got from my own system after @dosdude1 patching).

And yes, I simply installed 19H15 yesterday (fresh using the unpatched Catalina installer) and applied the 19H524 via OTA, switched then to the DeveloperSeed and did the same with the 19H1016. I had to reboot in both cases twice to get the system (nearly) fully working, recognition of the internal screen seems to be broken after first boot. But this may also be a limitation of OpenCore.

Sound is broken without patching. But I use a BT sound cube to overcome this. It is a desktop system. The users really familiar with OpenCore and building hackintosh style configs should take a look at the OCLP (OpenCore Legacy Patcher) for Big Sur and use this a a starting config.

Limitations:
- sound remains broken even with the latest AppleALC
- only working on my (modded) iMac11,x and 12,x - had not time to check it with my old 2010 macbook, so far.

 

[makra]

For me with 19H524, the OTA fix plus SU beta reset didn't produce the available release update immediately. I closed the SU panel and opened again a bit later (30 mins) and it showed up.

If there's something beyond 19H524 it's not yet available to me on a Catalina supported Mac!

There is no reason to be obsessive about security updates.

No, I'm not obsessive with updates, but in December I thought, I needed to do something to get further than 19H15 at some stage. I'll wait for my 2012 MBP to show me further updates and see what happens on this machine. But in contrast to our patched Mojave machines I've actually never seen updates in the OTA without using CatalinaOTAswufix...

 

[telepati]

I cant Camera and Microphone permission what can I do?

 

[makra]

I cant Camera and Microphone permission what can I do?

I assume you have installed all the patches and have checked your privacy preferences?

I had problems with my camera using certain apps with some build a few weeks ago. Those apps included Zoom, Jitsi and also iMovie. Now the problems have disappeared again. But I found out, that FaceTime or PhotoBooth always worked and got the other apps going as well. So: Does FaceTime work for you?

 

[telepati]

I assume you have installed all the patches and have checked your privacy preferences?

I had problems with my camera using certain apps with some build a few weeks ago. Those apps included Zoom, Jitsi and also iMovie. Now the problems have disappeared again. But I found out, that FaceTime or PhotoBooth always worked and got the other apps going as well. So: Does FaceTime work for you?

Yes, I installed all patches. Facetime working too. Some apps like Discord and Boom3D microphone need permission but that does not show under Privacy/Microphone.

Do you have DisableLibraryValidation.kext under Library/Extensions folder?

 

[makra]

Yes, I installed all patches. Facetime working too. Some apps like Discord and Boom3D microphone need permission but that does not show under Privacy/Microphone.

Do you have DisableLibraryValidation.kext under Library/Extensions folder?

No, I don’t... And: Discord doesn't have any problems.

 

[telepati]

I don't have too. How is it look your libraryvalidation.plist under Library/Preferences;

Could you please check your boot args with nvram -p command on Terminal? Do you have any boot args?

 

[Larsvonhier]

Yes, I installed all patches. Facetime working too. Some apps like Discord and Boom3D microphone need permission but that does not show under Privacy/Microphone.

Do you have DisableLibraryValidation.kext under Library/Extensions folder?

You might have to use the tool tccplus to set those mic/cam rights manually. Worked for me in all those cases where the apps were "too dumb" to register in the appropriate way to show up in the control panel.

 

[K two]

Right now I'm on 19H1009 (the most recent time machine backup I had...). I can get Beta updates via CatalinaOTAswufix, but if I revert the CP to Defaults, no more updates show up. That's why I had begun with Beta versions in the first place, when full installers stopped.
I guess, I must have missed an important point in this thread... ? Any help?
(@Ausdauersportler Would it do to install 19H15 again and then look for updates? And: It should be a clean install, right?)

Right, H15 and up to H524 via CatalinaOTAswufix, not in Developer mode worked, here.

 

[K two]

So, when all is said and done - avoid macOS Catalina Security Update Developer Beta 2021-002 10.15.7 1.38 GB for now. Got it. ?

 

[makra]

Even I got it now - H524 running! ??

 

[borgo1971]

Hi. I'd like to know if someone has successful installed Windows 10 on an unsupported Mac updated to Catalina. Before installing Catalina, I had a full functional Windows 10 partition on my 2008 iMac, and I hold untouched the original HDD with SnowLeopard and Windows 10 partition, because I replaced it with an SSD. Now I need to get back a bootable Windows 10 partition (virtualizing is a not a possibility, with only 4GB ram), but BootCamp won't work because it says hardware is unsupported. Which could be the best steps to get back a dual booting iMac, but with macOS Catalina?