Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
anyone help? I cannot do any installation or upgrade right now. no matter which version...
I can only boot to Mojave in my external SSD.
Boot to Catalina patch USB, Mojave USB installation disk, Recovery partition all are in same situation.
Is it any problem with the EFI or Boot partition?
NVRAM reset, SIP enable, SMC reset all tried...
You might boot into the Catalina Patcher after you disable SIP click on the Apple logo the start up disk click on the one you installed Catalina on
 
  • Like
Reactions: jackluke
Tried all of those instructions, but still not working. I did upgrade it from Mojave, so not a clean install. I can do a clean install unless there is something else I can do.

Upgrade from Mojave is good no need to do a Catalina clean install, before trying other check these steps:

- Do you have a working Catalina AirDrop required before Continuity ? (Test it with an iOS device if can detect the Catalina AirDrop and viceversa, set both "Allow Discovered by Everyone")

- do you have SIP disabled ? (check from Catalina Terminal with csrutil status )

- Do you have placed in that script YOURBOARDIDNUMBERS your exact board-id that should be "Mac-942459F5819B171B" ? (check or attach the file on Desktop Continuitycheck.txt if is present with your board-id the ContinuitySupport = 1; )

from Terminal copy/paste this:
Code:
defaults read "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist" > ~/Desktop/Continuitycheck.txt
 
Last edited:
Upgrade from Mojave is good no need to do a Catalina clean install, before trying other check these steps:

- Do you have a working Catalina AirDrop required before Continuity ? (Test it with an iOS device if can detect the Catalina AirDrop and viceversa, set both "Allow Discovered by Everyone")

- do you have SIP disabled ? (check from Catalina Terminal with csrutil status )

- Do you have placed in that script YOURBOARDIDNUMBERS your exact board-id that should be "Mac-942459F5819B171B" ? (check or attach the file on Desktop Continuitycheck.txt if is present with your board-id the ContinuitySupport = 1; )

from Terminal copy/paste this:
Code:
defaults read "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist" > ~/Desktop/Continuitycheck.txt
It´s a good idea to change the SysterParameters.plist before, of course. To do it in Catalina is a pain in the ass.
 
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.
 
Last edited:
@jackluke & @dosdude1, regarding posts 6,982 & 7,009.

Unless I've misread the information provided, it seems significant progress has been made towards restoring functionality to the Software Update pane (in System Preferences) on machines not supported by Catalina. I suppose I'll probably have to re-read the instructions regarding the boot loop in "OTA stage 3", as I haven't tried the Software Update procedure yet on an old iMac 7,1 with an upgraded processor. I was wondering, is the situation described in the previous posts considered to be definitive, or nearly so, or can further progress be expected from @jackluke, @dosdude1 or perhaps others? Specifically, is it realistic to expect that an automated process will be implemented that will fully restore functionality the the Software Update pane? If so, when do you foresee that such a process might be available?
 
  • Like
Reactions: jackluke
@jackluke & @dosdude1, regarding posts 6,982 & 7,009.

Unless I've misread the information provided, it seems significant progress has been made towards restoring functionality to the Software Update pane (in System Preferences) on machines not supported by Catalina. I suppose I'll probably have to re-read the instructions regarding the boot loop in "OTA stage 3", as I haven't tried the Software Update procedure yet on an old iMac 7,1 with an upgraded processor. I was wondering, is the situation described in the previous posts considered to be definitive, or nearly so, or can further progress be expected from @jackluke, @dosdude1 or perhaps others? Specifically, is it realistic to expect that an automated process will be implemented that will fully restore functionality the the Software Update pane? If so, when do you foresee that such a process might be available?

Not yet definitive, however @TimothyR734 before me already tested succesfully that method on an unsupported iMac9,1 (the model with Penryn C2D, Nvidia Tesla and legacy USB host so similar to yours), I only warned people who want attempt in preview the manual method, that haven't to worry about some possible bootlooping (due to telemetry.plugin copied back from the OTA and IOSurface if the Video Patches are applied before the OTA stage3 completes) that is fixable and no personal data are affected.

So if you want you might try the manual method that will work anyway, @dosdude1 will develop on an automated script, however since the 10.15.2 is close to release, you can wait and opt this round to update with standard procedure that is making a full Catalina USB installer/patcher.
 
Last edited:
hello

I have Mac pro 5.1 to with update the wi-fi / BT card a Brodcom BCM94360CD with WI-Fi AC and BT 4.
Untile same time ago, with Mojave + Continuity Activation Tool and manual modifications to the SystemParameters.plist file, everything worked perfectly.
After upgrading to Catalina with macOS Catalina Patcher no works the unlocking after stop with Apple Watch (4).
With it I can unlock Notes, Panels and enter passes for other things but the Mac doesn't restart after the stope, I must insert the pass by hand. First with Mojave it worked.

help me please - Thanks
 
  • Like
Reactions: TimothyR734
Upgrade from Mojave is good no need to do a Catalina clean install, before trying other check these steps:

- Do you have a working Catalina AirDrop required before Continuity ? (Test it with an iOS device if can detect the Catalina AirDrop and viceversa, set both "Allow Discovered by Everyone")

- do you have SIP disabled ? (check from Catalina Terminal with csrutil status )

- Do you have placed in that script YOURBOARDIDNUMBERS your exact board-id that should be "Mac-942459F5819B171B" ? (check or attach the file on Desktop Continuitycheck.txt if is present with your board-id the ContinuitySupport = 1; )

from Terminal copy/paste this:
Code:
defaults read "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist" > ~/Desktop/Continuitycheck.txt

  • My board-id is present with ContinuitySupport = 1.
    • The only other flag it has is "DID-ProductCode" = 18973.
    • There are a multitude of other board-ids in that generated text file though, but I'm assuming they are supposed to be there.
  • Catalina AirDrop is working. But it is wonky. Not the best word, but it fits.
    • From my Mac, I cannot see my iPhone or my iPad until I try to do an AirDrop on one of them. As long as I am in the AirDrop options, the Mac sees them (kind of). Once I send the file from my iPhone or iPad, then it disappears as an option from the Mac. Here is the really wonky bit. I pull up the AirDrop menus in my iPhone, then my Mac sees my iPad, but not the iPhone. To get the iPhone to show up, I open an AirDrop menu on my iPad. As long as both the iPhone and iPad have the AirDrop share menus open, then the Mac sees both. It's as if the iPhone sends the Mac what it sees. Since the iPhone sees the iPad, it sends the Mac that option. Same thing with the iPad but in reverse. However, neither the iPhone not the iPad can see the Mac. So it is a one-way thing for me at the moment. I can send files from my Mac to my iPhone and iPad, but not the other way around. And, both iPhone and iPad have to have an active AirDrop share menu running.
  • SIP status is listed as unknown, custom configuration. But it seems to be disabled from the rest of what it says in that custom configuration:
    • Apple Internal: disabled
    • Kext Signing: disabled
    • Filesystem Protections: disabled
    • Debugging Restrictions: disabled
    • DTrace Restrictions: disabled
    • NVRAM Protections: disabled
    • BaseSystem Verification: disabled
  • I have used the CAT tool before in Mojave but it never really worked outside Messages and Phone. So it is possible I've got old settings somewhere that are conflicting with this. But I followed your instructions to replace files, so if there are conflicting settings, they shouldn't be there.
  • Also, in the interest of full disclosure, I had this Mac altered to permanently disable the discrete GPU. It went out on me early this summer and I couldn't even boot because of it. It had to be disabled by removing a resistor, I think it was. Was back to normal after that. I can't imagine continuity has anything to do with the discrete GPU, but thought I should share just in case.
Also, I read somewhere that one of the Continuity features wouldn't work without wireless AC? Do I need a dongle for AC in addition to the one for Bluetooth 4.0?

Thanks for your help.
 
  • Like
Reactions: TimothyR734
Hi,

I was able to install Mojave on my Macbook Air (4,1) without issue and it runs great. I have tried installing Catalina, but it never seems to install.

I follow the tutorial, create the USB, performed the "Reinstall of Catalina". During this process, it acts as though it is installing. Then it reboots and brings me back to the same MacOS Utilities area and acts like it never started the installation process...

I have tried a few times. I have tried by converting to AFPS, as well as doing an erase, but the results are the same. I have no issues reinstalling Mojave if I do erase.

I am unsure what else I can do. Any and all help is much appreciated.
 
  • Like
Reactions: TimothyR734
Hi,

I was able to install Mojave on my Macbook Air (4,1) without issue and it runs great. I have tried installing Catalina, but it never seems to install.

I follow the tutorial, create the USB, performed the "Reinstall of Catalina". During this process, it acts as though it is installing. Then it reboots and brings me back to the same MacOS Utilities area and acts like it never started the installation process...

I have tried a few times. I have tried by converting to AFPS, as well as doing an erase, but the results are the same. I have no issues reinstalling Mojave if I do erase.

I am unsure what else I can do. Any and all help is much appreciated.
Sounds like you don't have the latest BootROM version installed. More info is located in the "Important Info" section of the Catalina Patcher webpage.
 
Hello,

How do I fix SIRI in catalina ? When I click on it nothing happens.
[automerge]1574743994[/automerge]
Thanks will try this when I get home.
[automerge]1574474539[/automerge]

Jack Luke, quick question - have you notice Siri doesn’t work ?? That’s another issue that I am having.

Hi, appplied the patcher and it did not work, keyboard preferences did not open.
 
Last edited:
  • Like
Reactions: TimothyR734
What's up with everybody being unable to use Siri? It's working fine for me.

Screen Shot 2019-11-25 at 11.59.53 PM.png


Those of you who are having issues, please check Crash Reports in the Console app and upload anything that looks relevant.
 
What's up with everybody being unable to use Siri? It's working fine for me.

View attachment 879302

Those of you who are having issues, please check Crash Reports in the Console app and upload anything that looks relevant.

corebrghtness mod screwed it up.
[automerge]1574744962[/automerge]
corebrghtness mod screwed it up.

I think DosDude needs to add all these mods to a new release of Catalina Patcher. Also, these have crippled my keyboard preference and Siri preference tabs, just provide for us the fix for this.

"FED UP"
 
  • My board-id is present with ContinuitySupport = 1.
    • The only other flag it has is "DID-ProductCode" = 18973.
    • There are a multitude of other board-ids in that generated text file though, but I'm assuming they are supposed to be there.
  • Catalina AirDrop is working. But it is wonky. Not the best word, but it fits.
    • From my Mac, I cannot see my iPhone or my iPad until I try to do an AirDrop on one of them. As long as I am in the AirDrop options, the Mac sees them (kind of). Once I send the file from my iPhone or iPad, then it disappears as an option from the Mac. Here is the really wonky bit. I pull up the AirDrop menus in my iPhone, then my Mac sees my iPad, but not the iPhone. To get the iPhone to show up, I open an AirDrop menu on my iPad. As long as both the iPhone and iPad have the AirDrop share menus open, then the Mac sees both. It's as if the iPhone sends the Mac what it sees. Since the iPhone sees the iPad, it sends the Mac that option. Same thing with the iPad but in reverse. However, neither the iPhone not the iPad can see the Mac. So it is a one-way thing for me at the moment. I can send files from my Mac to my iPhone and iPad, but not the other way around. And, both iPhone and iPad have to have an active AirDrop share menu running.
  • SIP status is listed as unknown, custom configuration. But it seems to be disabled from the rest of what it says in that custom configuration:
    • Apple Internal: disabled
    • Kext Signing: disabled
    • Filesystem Protections: disabled
    • Debugging Restrictions: disabled
    • DTrace Restrictions: disabled
    • NVRAM Protections: disabled
    • BaseSystem Verification: disabled
  • I have used the CAT tool before in Mojave but it never really worked outside Messages and Phone. So it is possible I've got old settings somewhere that are conflicting with this. But I followed your instructions to replace files, so if there are conflicting settings, they shouldn't be there.
  • Also, in the interest of full disclosure, I had this Mac altered to permanently disable the discrete GPU. It went out on me early this summer and I couldn't even boot because of it. It had to be disabled by removing a resistor, I think it was. Was back to normal after that. I can't imagine continuity has anything to do with the discrete GPU, but thought I should share just in case.
Also, I read somewhere that one of the Continuity features wouldn't work without wireless AC? Do I need a dongle for AC in addition to the one for Bluetooth 4.0?

Thanks for your help.

for your machine do you have used the entire zip content MacBookPro8,3 AirDrop Catalina ?

If so, on Mac, on the iPhone and iPad settings you should set the AirDrop option allow discovered by Everyone.

Only "Auto Unlock" requires a 802.11ac broadcom Wifi card, the other continuity features should work, probably with that usb bt 4.0 dongle (reading the continuity activation tool code) you need some whitelisting to patch the IOBluetoothFamily.kext because inside the binary there are some Mac-ids , I'll test this, meanwhile is your board-id Mac-942459F5819B171B ?
[automerge]1574760801[/automerge]
corebrghtness mod screwed it up.
[automerge]1574744962[/automerge]


I think DosDude needs to add all these mods to a new release of Catalina Patcher. Also, these have crippled my keyboard preference and Siri preference tabs, just provide for us the fix for this.

"FED UP"

I doubt that CoreBrightness screwed it up (probably keyboard prefpane issue could be a broken battery?), anyway which version of Catalina do you have installed currently ?

So I can upload the right Catalina non-patched SiriUI.framework and CoreBrightness.framework
 
Last edited:
@dosdude1
Will the next patcher version be released around the time Catalina 15.2 is released? I would make sense, since you are struggling with the System Update issue for some time, I guess you focus on fixing it on 15.2 instead of 15.1 .
 
My MacPro3.1 works very well with PCIe adapter with realMac Card Broadcom BCM94360CD. Works natively (Wifi / BT) including Airdrop with all macOS versions.

Hi,
What is the reference of your "PCIe adapter with realMac Card Broadcom BCM94360CD"
Many thanks in advance,

Serviteur
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.