macOS 10.15 Catalina on Unsupported Macs

[RogueB]

Doesn't sound like nvram is actually set. try running this command in terminal:

nvram -p | grep boot-args

See if 'boot-args -no_compat_check' comes back.

if nothing is returned try setting nvram boot-args again.

When booted from the USB installation stick, and running terminal command "nvram -p | grep boot-args" it does return
'boot-args -no_compat_check'

Is there anything else that I can verify, check, or repair ?

I did try to install again, but when machine spontanenousely rebooted, I forced it boot into a "single user mode". The message on screen (much as you suspected) clearly stated that, "the software is not compatible with this computer."

****The best of luck to you in your search for suitable employer, with whom you could pursue your career; you do have a remarkable skill-set. *****

 

[Starplayr]

Has anyone tried to clone a Catalina beta2 installation using 'DriveGenius 5's clone utility?

It claims its clone utility will do a raw copy.

At the moment I do not have a spare SSD/HDD to try it on. If no one else has done this I'll get another drive and try this and (and a restore) then report back - in a day or two.

I'm working on a clone tool right now that can do that.

Recently on here we used dd, diskutil, hdiutil and asr, command line utilities. I am working on a dead simple solution for Unsupported Macs. dd can cause some issues with duplicate drive UUIDs. hdiutil and asr make new UUIDs and are also block level copies. asr can go to equal or larger size volumes too, so it's best create a very small install partition of 32gb, make a disk image from it using hdiutil and then expand then to another disk using asr. I have done some how-to's on here with it and it's not terribly hard, but in about 2 weeks, I will have a solution that will be designed for our stuff on here and it may add some pretty cool features like over the air restores.

 

[pkouame]

I'd like to thank jackluke, ASentientBot, pkouame, jhowarth, TimothyR734 and nekton1 for their input and support on my CatWoman patcher. I'm working on a much easier method in the future, but first I want to get CloneToolX up and running on about two weeks and the things it can do could potentially bypass any blockers Apple puts in our way.

Off topic: I am doing a good bit of job interviews with several Silicon Valley based prospects. I may be spending a little more time researching information. I haven't found a good fit yet, but I have had a good bit of leads, discussions, phone calls, interviews, and coding tests. I'm self taught, and I've been getting into more of the how things actually work vs. how I can creatively make it work in my head. Dealing with Engineers who currently make the decision whether you pass or fail in a few minutes can be nerve racking. I don't test well. If I can't study it first or do it on my own, it's an automatic failure. Nonetheless, I keep getting several companies who are interested in my experience, so something is bound to happen. I currently working for a start up company in Charlotte as a Software Developer, IT Manager and I used to run my own startup, NiceMac. I feel like something is about to change, I just don't know where yet. I am getting lots of interest in Automation, Workflows, Dev. Advocate / Tech Evangelism and iOS development. So wish me luck.

Anyways, I just wanted to say I really enjoyed interacting with users on here and it's great how Dosdude1 started this community of unsupported misfit Macs. We are not on an island either. And I'll continue to support this community through and through.

Catalina Beta 2 btw, runs super well on my Mac Pro 3,1. It is rock solid. I'm amazed how fast a 12 year old computer can run. For me technology has not advanced in the last 10 years. Yes we have bigger screens, 4k, but things don't seem to actually compute a whole lot faster when it comes to the "Real User Experience". For me my user experience with a combination of old and new technology runs just as good as a new Mac Book Pro. Now that new Mac Book Pro will have a much faster SSD and Memory but other than that, the RUX on a tricked out Mac Pro 3,1 is just as good.

Indeed - Good luck - re-engineering one's self is always a challenge. You've got skills man - don't let the interview process get you down. Software Engineers can be very close-minded, obtuse and set in their ways, but once you break through you're good. I'm sure you can use some of your experiences here to your advantage...

 

[TimothyR734]

This is very interesting. It looks like it's very possible to set up a simple server that the CloneToolX client can connect to and it can do a restore over the air.

That would be awesome can't wait for it and wish you the best during your interview
[doublepost=1561089883][/doublepost]

When booted from the USB installation stick, and running terminal command "nvram -p | grep boot-args" it does return
'boot-args -no_compat_check'

Is there anything else that I can verify, check, or repair ?

I did try to install again, but when machine spontanenousely rebooted, I forced it boot into a "single user mode". The message on screen (much as you suspected) clearly stated that, "the software is not compatible with this computer."

****The best of luck to you in your search for suitable employer, with whom you could pursue your career; you do have a remarkable skill-set. *****

to see if your nvram is set correctly in the terminal nvram -p

 

[dosdude1]

Just fixed the USB issues on certain systems, such as the MacBook6,1. Now, the keyboard and trackpad should work 100% perfectly! Patcher has been updated with the new changes. All that was needed was a modification to LegacyUSBInjector.kext, which I have attached.

EDIT: I've also updated my "patch pack" to include this change as well. I've also added a kext to fix nVidia MCP79/89 Ethernet controllers under Catalina.

For those of you waiting, I plan to have my full, 100% automated Catalina Patcher ready within a couple weeks.

 

[TimothyR734]

Thank you Dosdude

 

[grzegorz9141]

Ok, I'll look into this and get that resolved soon.

Catalina PartialPatcher b13 the problem still exist.

 

[dosdude1]

Catalina PartialPatcher b13 the problem still exist.

What machine, and what stage of the process? If after installed, you'll need to apply the patches using my "patch pack".

 

[grzegorz9141]

What machine, and what stage of the process? If after installed, you'll need to apply the patches using my "patch pack".

@dosdude1

Your Catalina Partial Patcher Tool does not work on machine with already installed Catalina OS.
It’s not possible to create bootable USB. After press Create Patched Installer this tool hangs on starting....
Its create volume on USB with 1,34GB data and nothing more.

I want create USB Installer using Your Catalina PartialPatcher Tool on machine MacBook Pro 2018 with already installed Catalina b1/b2.

 

[dosdude1]

I want create USB Installer using Your Catalina PartialPatcher Tool on machine MacBook Pro 2018 with already installed Catalina b1/b2.

Oh, I haven't fixed that yet.

 

[arqueox]

Just fixed the USB issues on certain systems, such as the MacBook6,1. Now, the keyboard and trackpad should work 100% perfectly! Patcher has been updated with the new changes. All that was needed was a modification to LegacyUSBInjector.kext, which I have attached.

EDIT: I've also updated my "patch pack" to include this change as well. I've also added a kext to fix nVidia MCP79/89 Ethernet controllers under Catalina.

For those of you waiting, I plan to have my full, 100% automated Catalina Patcher ready within a couple weeks.

Awesome. You are the man! Gonna have my mbp for, at least one year more. Nice.

 

[avz]

Hope you don't mind a bit of levity(?) Dogs chase after cars instinctively (If "it" is running away it's prey [among other things]). They are also territorial so if, and when, they catch the car and find it inedible, the next thing a dog is likely to to is "pee" on the tire - as in: object conquered, it's now owned.
Everyone can probably attach a different meaning to the above "innuendo," given this is an "unsupported macs" thread. Patching journey = getting an insight, from "outside the box" into programming (?)

Yes, I believe it is important to have some humor and maybe even levity in the "unsupported threads" especially. One of my favorite lines from dosdude1 is: "Just ignore it and continue." Always gets me through.

 

[indigotheory]

Just fixed the USB issues on certain systems, such as the MacBook6,1. Now, the keyboard and trackpad should work 100% perfectly! Patcher has been updated with the new changes. All that was needed was a modification to LegacyUSBInjector.kext, which I have attached.

EDIT: I've also updated my "patch pack" to include this change as well. I've also added a kext to fix nVidia MCP79/89 Ethernet controllers under Catalina.

For those of you waiting, I plan to have my full, 100% automated Catalina Patcher ready within a couple weeks.

Thank you, think I'll wait until then!

 

[Frantisekj]

I probably know that answer is no but want to be sure.
Does patched version of Catalina or Mojave activate Continuity on unsupported macs or it’s still needed to patch them separately?

 

[Althiometer]

Tried booting a PartialPatcher installer on my mbp early 2011, got multiple kernel panics, same thing on Mojave patcher
Tried booting macOS Patcher installer got 2 crashes and once no progress bar
Am I doing something wrong?

 

[PeterHolbrook]

I probably know that answer is no but want to be sure.
Does patched version of Catalina or Mojave activate Continuity on unsupported macs or it’s still needed to patch them separately?

That will depend on whether you install Mojave or Catalina from scratch or on top of a previous (High Sierra) installation. If it's from scratch, I would assume you need to use Continuity Activation Tool (CAT). However, if you simply update a previous OS where Continuity and Hand-off were working, I know from experience that you needn't do anything. They should go on working when you update.

 

[jackluke]

I guess I found a fix to make working again AirDrop (from Catalina Finder) on unsupported Catalina Mac

Premise: I have noticed that starting from Catalina, AirDrop feature requires a Bluetooth 4.0 device (internal or USB) in order to be showed in the Finder, and to detect the other Mac and iOS devices connected on the same wifi network.
While till Mojave it was still possible to find older Mac and iOS devices even without a BT 4.0 dongle.

Before start, this method: https://apple.lib.utah.edu/airdrop-how-to-enable-on-os-x-mavericks-via-ethernet/
doesn't worked on Catalina, it just enables a Finder AirDrop icon without any functionality, and more over (if worked) was only for ethernet connected Mac, not Wifi Mac/devices.


Here is how I made and understood "my fix":

First of all I observed that both on my MacBookPro2010 (i5 cpu dualGPUs) and MacBook7,1 (core2duo cpu Nvidia) the driver used for my Wifi Airport Broadcom was this: kextstat | grep AirPort

com.apple.driver.AirPort.Brcm4331

Then looking at the "Continuity Activation Tool" I understood that the allowed Wifi Broadcom driver to support AirDrop over a BT 4.0 device is this com.apple.driver.AirPort.Brcm4360

So using a couple of BT 4.0 USB dongle, with "continuityactivationtool" I have attempted to partial fix whitelisting (without touching the IOBluetooth) inside the AirPortBrcm4360 binary file the machine boardID, but it can also be done manually, open Terminal and copy/paste:

ioreg -l | grep "board-id" | awk -F\" '{print $4}'

from output get your boardID for example: Mac-F22C89C8 (MacBook7,1 mid 2010)
And opening inside IO80211Family.kext the "AirPortBrcm4360 binary exec" using an hex editor (or other method) whitelist this boardID from "ascii to hex" searching for "Mac-" in hex becomes "4d 61 63 2d".
Typically the first occurrence should be suffice, but I've swapped all the other encountered for safety and to catch any possible additional function adding only that boardID (example picture attached).
Since the older machine boardID numbers are shorter, after added your (ascii-to-hex) boardID add an octet of "00" (example picture attached).

Response: it worked!

I attach for now only a "fix" tested and working for MacBook7,1 mid 2010 , and before replacing the attached kext, from Catalina Terminal:
sudo mount -uw / ; killall Finder ; open /S*/L*/E*/IO80211Family.kext/C*/P*/

Then back to Terminal and type:
sudo chown -R 0:0 /S*/L*/E*
sudo chmod -R 755 /S*/L*/E*
sudo kextcache -i /

I attached also the non-patched AirPortBrcm4331.kext because I discovered that Wifi Airport Broadcom can use both 4331 and 4360 , in fact the "PCI Match device id" for this Broadcom wifi is present (from HighSierra, Mojave) in both the driver Info.plist : <string>pci14e4,4353</string>

So if my patch for some reason doesn't work on your machine your wifi will use the other driver, but I repeat the patch I posted is only for MacBook7,1 mid 2010.

I add also another for MacBookPro6,2 15" mid 2010 dualGPUs (in the specified folder).

The file attached allows to enable the AirDrop feature on Catalina Finder, and if you plug a Bluetooth 4.0 dongle it should work too and detect all the devices inside the same wifi network (with "discovered by Everyone" checked).

 

[iMac-Oldschool]

Just fixed the USB issues on certain systems, such as the MacBook6,1. Now, the keyboard and trackpad should work 100% perfectly! Patcher has been updated with the new changes. All that was needed was a modification to LegacyUSBInjector.kext, which I have attached.

EDIT: I've also updated my "patch pack" to include this change as well. I've also added a kext to fix nVidia MCP79/89 Ethernet controllers under Catalina.

For those of you waiting, I plan to have my full, 100% automated Catalina Patcher ready within a couple weeks.

Still unable to install on iMac8,1

dm.log file was created on target drive, but could not be uploaded. Here is the text from the Console app.

20190621-03:35:07.76438 [00616:002403] storagekitd _getNVMeSMARTData DMErr=-536870201 IntErr=-536870201=0xe00002c7 err=0xe00002c7=-536870201 retSmartStatus={

Status = "Not Supported";

}

20190621-03:35:08.73148 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s5

20190621-03:35:09.08688 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s4

20190621-03:35:09.27413 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s3

20190621-03:35:09.53881 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s2

20190621-03:35:09.67104 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s1

20190621-03:35:10.17737 [00616:002503] storagekitd _DMdeviceNameForDisk DMErr=-69880 err=-69880 out="(null)"

20190621-03:35:10.17750 [00616:002503] storagekitd DMManager(Info) deviceNameForDisk DMErr=-69880

20190621-03:35:10.19250 [00616:002503] storagekitd

20190621-03:35:10.20105 [00616:002503] storagekitd _DMsmartStatusForDisk DMErr=-69880 err=-69880 out={

Status = "Not Supported";

}

20190621-03:35:10.20115 [00616:002503] storagekitd DMManager(Info) smartStatusForDisk DMErr=-69880 out={

Status = "Not Supported";

} err=-69880

20190621-03:35:10.20212 [00616:002503] storagekitd DMManager(Info) copyDiskForPath DMErr=-69878 outDisk=(null) err=-69878

20190621-03:35:10.20270 [00616:002503] storagekitd DMManager(Info) copyDiskForPath DMErr=-69878 outDisk=(null) err=-69878

20190621-03:35:10.22548 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s5

20190621-03:35:10.99564 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s4

20190621-03:35:11.42091 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s3

20190621-03:35:11.67900 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s2

20190621-03:35:11.94119 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s1

20190621-03:35:13.53085 [00610:003b03] diskmanagementd _DMAppleRAIDBSDNameSearch DMErr=2 IntErr=2=0x2 outErr=2 outRaidUUID=(null)

20190621-03:35:13.62684 [00610:003b03] diskmanagementd _DMAppleRAIDBSDNameSearch DMErr=2 IntErr=2=0x2 outErr=2 outRaidUUID=(null)

20190621-03:35:13.91957 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5526230 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.91971 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:13.92006 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92013 [00616:002403] storagekitd DMManager(Info) diskIdentifierForDisk DMErr=-69810 out=(null) err=-69810

20190621-03:35:13.92034 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5505a10 [0x112534a20]>{id = /dev/disk24s1} BSD=disk24s1

20190621-03:35:13.92040 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:13.92062 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e543c0b0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92068 [00616:002403] storagekitd DMManager(Info) diskIdentifierForDisk DMErr=-69810 out=(null) err=-69810

20190621-03:35:13.92091 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5577850 [0x112534a20]>{id = /dev/disk24s2} BSD=disk24s2

20190621-03:35:13.92099 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:13.92154 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5508b10 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92160 [00616:002403] storagekitd DMManager(Info) diskIdentifierForDisk DMErr=-69810 out=(null) err=-69810

20190621-03:35:13.92182 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92188 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:13.92208 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92218 [00616:002403] storagekitd DMManager(Info) ioContentOfDisk DMErr=-69810 ret=(null) err=-69810

20190621-03:35:13.92239 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5496c10 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92245 [00616:002403] storagekitd DMManager(Info) ioContentOfDisk DMErr=-69810 ret=(null) err=-69810

20190621-03:35:13.92265 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92272 [00616:002403] storagekitd DMCoreStorage physicalVolumeAndLogicalVolumeGrou DMErr=-69810 outErr=-69810 pvUUID=(null) lvgUUID=(null)

20190621-03:35:13.92291 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92298 [00616:002403] storagekitd DMCoreStorage physicalVolumeAndLogicalVolumeGrou DMErr=-69810 outErr=-69810 pvUUID=(null) lvgUUID=

20190621-03:35:13.92319 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92326 [00616:002403] storagekitd DMCoreStorage logicalVolumeAndLogicalVolumeGroup DMErr=-69810 outErr=-69810 outLVUUID=(null) outLVGUUID=(null)

20190621-03:35:13.92346 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92352 [00616:002403] storagekitd DMAPFS physicalStoreUUIDForPhysicalStore DMErr=-69810 retErr=-69810 outPhysicalStoreUUID=(null)

20190621-03:35:13.92373 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92379 [00616:002403] storagekitd DMAPFS containerUUIDForContainer DMErr=-69810 retErr=-69810 outContainer(NotContainerReference)UUID=(null)

20190621-03:35:13.92399 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:13.92405 [00616:002403] storagekitd DMAPFS volumeUUIDForVolume DMErr=-69810 retErr=-69810 outVolumeUUID=(null)

20190621-03:35:13.92424 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5473cc0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:15.25908 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s1

20190621-03:35:15.30853 [00616:002503] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s1

20190621-03:35:17.28007 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s5

20190621-03:35:17.36975 [00616:002503] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s5

20190621-03:35:18.20434 [00610:003b03] diskmanagementd _DMpartitionMapSchemeForWholeDisk DMErr=-69880 err=-69880 out=-1

20190621-03:35:18.36069 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36091 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:18.36098 [00616:002403] storagekitd DMManager(Info) wholeDiskForDisk DMErr=-69810 out=0x0=(null) err=-69810

20190621-03:35:18.36132 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36138 [00616:002403] storagekitd DMCoreStorage logicalVolumeAndLogicalVolumeGroup DMErr=-69810 outErr=-69810 outLVUUID=(null) outLVGUUID=(null)

20190621-03:35:18.36145 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36151 [00616:002403] storagekitd DMCoreStorage physicalVolumeAndLogicalVolumeGrou DMErr=-69810 outErr=-69810 pvUUID=(null) lvgUUID=(null)

20190621-03:35:18.36157 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36162 [00616:002403] storagekitd DMCoreStorage physicalVolumeAndLogicalVolumeGrou DMErr=-69810 outErr=-69810 pvUUID=(null) lvgUUID=(null)

20190621-03:35:18.36169 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36175 [00616:002403] storagekitd DMManager(Info) ioContentOfDisk DMErr=-69810 ret=(null) err=-69810

20190621-03:35:18.36181 [00616:002403] storagekitd DMManager(Info) wholeDiskForDisk DMErr=-69810 out=0x0=(null) err=-69810

20190621-03:35:18.36187 [00616:002403] storagekitd DMManager(Info) ioContentOfDisk DMErr=-69810 ret=(null) err=-69810

20190621-03:35:18.36193 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36199 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36205 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36210 [00616:002403] storagekitd DMAPFS physicalStoreUUIDForPhysicalStore DMErr=-69810 retErr=-69810 outPhysicalStoreUUID=(null)

20190621-03:35:18.36216 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36222 [00616:002403] storagekitd DMAPFS containerUUIDForContainer DMErr=-69810 retErr=-69810 outContainer(NotContainerReference)UUID=(null)

20190621-03:35:18.36228 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36234 [00616:002403] storagekitd DMAPFS volumeUUIDForVolume DMErr=-69810 retErr=-69810 outVolumeUUID=(null)

20190621-03:35:18.36239 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36245 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36283 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.36290 [00616:002403] storagekitd DMAPFS isDiskSuitableForConversionFromHFS DMErr=-69810 outErr=-69810 outSuitable=0 outWhy=0

20190621-03:35:18.71179 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskGetBSDName

20190621-03:35:18.71191 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:18.71198 [00616:002403] storagekitd DMManager(Info) wholeDiskForDisk DMErr=-69810 out=0x0=(null) err=-69810

20190621-03:35:18.71371 [00610:002107] diskmanagementd rawLaunch_block_invoke IntErr=1=0x1 waitpid(2) pid=638 ret/errno=638/35 status=0x00000000 exit=0

20190621-03:35:19.54394 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s1

20190621-03:35:19.61598 [00616:002503] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s1

20190621-03:35:20.37367 [00616:002403] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s5

20190621-03:35:20.44398 [00616:002503] storagekitd DMPartitionDisk getPartitionStartLocationForDisk IntErr=1=0x1 err getting part start disk1s5

20190621-03:35:25.82756 [00616:002403] storagekitd _getNVMeSMARTData DMErr=-536870201 IntErr=-536870201=0xe00002c7 err=0xe00002c7=-536870201 retSmartStatus={

Status = "Not Supported";

}

20190621-03:35:27.15620 [00616:002403] storagekitd _getNVMeSMARTData DMErr=-536870201 IntErr=-536870201=0xe00002c7 err=0xe00002c7=-536870201 retSmartStatus={

Status = "Not Supported";

}

20190621-03:35:28.26388 [00610:003b03] diskmanagementd _DMAppleRAIDBSDNameSearch DMErr=2 IntErr=2=0x2 outErr=2 outRaidUUID=(null)

20190621-03:35:28.34457 [00610:003b03] diskmanagementd _DMAppleRAIDBSDNameSearch DMErr=2 IntErr=2=0x2 outErr=2 outRaidUUID=(null)

20190621-03:35:28.65232 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5518710 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65249 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:28.65272 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65282 [00616:002403] storagekitd DMManager(Info) diskIdentifierForDisk DMErr=-69810 out=(null) err=-69810

20190621-03:35:28.65303 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e55306f0 [0x112534a20]>{id = /dev/disk24s1} BSD=disk24s1

20190621-03:35:28.65313 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:28.65336 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e540aae0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65347 [00616:002403] storagekitd DMManager(Info) diskIdentifierForDisk DMErr=-69810 out=(null) err=-69810

20190621-03:35:28.65367 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5505a70 [0x112534a20]>{id = /dev/disk24s2} BSD=disk24s2

20190621-03:35:28.65379 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:28.65400 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5416be0 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65412 [00616:002403] storagekitd DMManager(Info) diskIdentifierForDisk DMErr=-69810 out=(null) err=-69810

20190621-03:35:28.65433 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65445 [00616:002403] storagekitd DMManager(Info) isWholeDisk DMErr=-69810 ret=0 err=-69810

20190621-03:35:28.65464 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65476 [00616:002403] storagekitd DMManager(Info) ioContentOfDisk DMErr=-69810 ret=(null) err=-69810

20190621-03:35:28.65497 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e5510640 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65508 [00616:002403] storagekitd DMManager(Info) ioContentOfDisk DMErr=-69810 ret=(null) err=-69810

20190621-03:35:28.65528 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65540 [00616:002403] storagekitd DMCoreStorage physicalVolumeAndLogicalVolumeGrou DMErr=-69810 outErr=-69810 pvUUID=(null) lvgUUID=(null)

20190621-03:35:28.65560 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65576 [00616:002403] storagekitd DMCoreStorage physicalVolumeAndLogicalVolumeGrou DMErr=-69810 outErr=-69810 pvUUID=(null) lvgUUID=

20190621-03:35:28.65623 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65630 [00616:002403] storagekitd DMCoreStorage logicalVolumeAndLogicalVolumeGroup DMErr=-69810 outErr=-69810 outLVUUID=(null) outLVGUUID=(null)

20190621-03:35:28.65650 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65661 [00616:002403] storagekitd DMAPFS physicalStoreUUIDForPhysicalStore DMErr=-69810 retErr=-69810 outPhysicalStoreUUID=(null)

20190621-03:35:28.65682 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65693 [00616:002403] storagekitd DMAPFS containerUUIDForContainer DMErr=-69810 retErr=-69810 outContainer(NotContainerReference)UUID=(null)

20190621-03:35:28.65713 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.65725 [00616:002403] storagekitd DMAPFS volumeUUIDForVolume DMErr=-69810 retErr=-69810 outVolumeUUID=(null)

20190621-03:35:28.65744 [00616:002403] storagekitd _DMUDSEncodeWithDADiskRef IntErr=1=0x1 NULL from DADiskCopyDescription; DADR=<DADisk 0x7ff4e551f210 [0x112534a20]>{id = /dev/disk24} BSD=disk24

20190621-03:35:28.82354 [00610:003b03] diskmanagementd DMToolAPFS addVolumeToContainer IntErr=-536870206=0xe00002c2 aft APFSVolumeCreate err=-536870206=0xe00002c2=Unknown error: -536870206 InOutOptRes=*** disk=disk1

20190621-03:35:28.82429 [00610:003b03] diskmanagementd DMToolAPFS addVolumeToContainer DMErr=-69624 outErr=-69624 outCreatedVolume=(uninit)

20190621-03:35:28.82436 [00610:003b03] diskmanagementd _DMUDSDecodeToDiskIdentifier IntErr=1=0x1 retBSD=(null)

20190621-03:35:28.83239 [00616:002503] storagekitd DMLocalizedUserErrorString DMErr=-69624 request for localized end-user error string; CODE: -69624 TECH/UNLOC: Unable to add a new APFS Volume to an APFS Container USER/LOC: An internal error has occurred.

 

[Minh_Ton]

I guess I found a fix to make working again AirDrop (from Catalina Finder) on unsupported Catalina Mac

Premise: I have noticed that starting from Catalina, AirDrop feature requires a Bluetooth 4.0 device (internal or USB) in order to be showed in the Finder, and to detect the other Mac and iOS devices connected on the same wifi network.
While till Mojave it was still possible to find older Mac and iOS devices even without a BT 4.0 dongle.

Before start, this method: https://apple.lib.utah.edu/airdrop-how-to-enable-on-os-x-mavericks-via-ethernet/
doesn't worked on Catalina, it just enables a Finder AirDrop icon without any functionality, and more over (if worked) was only for ethernet connected Mac, not Wifi Mac/devices.


Here is how I made and understood "my fix":

First of all I observed that both on my MacBookPro2010 (i5 cpu dualGPUs) and MacBook7,1 (core2duo cpu Nvidia) the driver used for my Wifi Airport Broadcom was this: kextstat | grep AirPort

com.apple.driver.AirPort.Brcm4331

Then looking at the "Continuity Activation Tool" I understood that the allowed Wifi Broadcom driver to support AirDrop over a BT 4.0 device is this com.apple.driver.AirPort.Brcm4360

So using a couple of BT 4.0 USB dongle, with "continuityactivationtool" I have attempted to partial fix whitelisting (without touching the IOBluetooth) inside the AirPortBrcm4360 binary file the machine boardID.

Response: it worked!

I attach for know only a "fix" for MacBook7,1 mid 2010 , and before replacing from Catalina Terminal:
sudo mount -uw / ; killall Finder ; open /S*/L*/E*/IO80211Family.kext/C*/P*/

Then back to Terminal and type:
sudo chown -R 0:0 /S*/L*/E*
sudo chmod -R 755 /S*/L*/E*
sudo kextcache -i /

I attached also the non-patched AirPortBrcm4331.kext because I discovered that Wifi Airport Broadcom can use both 4331 and 4360 , in fact the "PCI Match device id" for this Broadcom wifi is present (from HighSierra, Mojave) in both the driver Info.plist : <string>pci14e4,4353</string>

So if my patch for some reason doesn't work on your machine your wifi will use the other driver, but I repeat the patch I posted is only for MacBook7,1 mid 2010.

I add also another for MacBookPro6,2 15" mid 2010 dualGPUs.

The file attached allows to enable the AirDrop feature on Catalina Finder, and if you plug a Bluetooth 4.0 dongle it should work too and detect all the devices inside the same wifi network (with "discovered by Everyone" checked).

Amazing work!

 

[pkouame]

I guess I found a fix to make working again AirDrop (from Catalina Finder) on unsupported Catalina Mac

Premise: I have noticed that starting from Catalina, AirDrop feature requires a Bluetooth 4.0 device (internal or USB) in order to be showed in the Finder, and to detect the other Mac and iOS devices connected on the same wifi network.
While till Mojave it was still possible to find older Mac and iOS devices even without a BT 4.0 dongle.

Before start, this method: https://apple.lib.utah.edu/airdrop-how-to-enable-on-os-x-mavericks-via-ethernet/
doesn't worked on Catalina, it just enables a Finder AirDrop icon without any functionality, and more over (if worked) was only for ethernet connected Mac, not Wifi Mac/devices.


Here is how I made and understood "my fix":

First of all I observed that both on my MacBookPro2010 (i5 cpu dualGPUs) and MacBook7,1 (core2duo cpu Nvidia) the driver used for my Wifi Airport Broadcom was this: kextstat | grep AirPort

com.apple.driver.AirPort.Brcm4331

Then looking at the "Continuity Activation Tool" I understood that the allowed Wifi Broadcom driver to support AirDrop over a BT 4.0 device is this com.apple.driver.AirPort.Brcm4360

So using a couple of BT 4.0 USB dongle, with "continuityactivationtool" I have attempted to partial fix whitelisting (without touching the IOBluetooth) inside the AirPortBrcm4360 binary file the machine boardID.

Response: it worked!

I attach for know only a "fix" for MacBook7,1 mid 2010 , and before replacing from Catalina Terminal:
sudo mount -uw / ; killall Finder ; open /S*/L*/E*/IO80211Family.kext/C*/P*/

Then back to Terminal and type:
sudo chown -R 0:0 /S*/L*/E*
sudo chmod -R 755 /S*/L*/E*
sudo kextcache -i /

I attached also the non-patched AirPortBrcm4331.kext because I discovered that Wifi Airport Broadcom can use both 4331 and 4360 , in fact the "PCI Match device id" for this Broadcom wifi is present (from HighSierra, Mojave) in both the driver Info.plist : <string>pci14e4,4353</string>

So if my patch for some reason doesn't work on your machine your wifi will use the other driver, but I repeat the patch I posted is only for MacBook7,1 mid 2010.

I add also another for MacBookPro6,2 15" mid 2010 dualGPUs.

The file attached allows to enable the AirDrop feature on Catalina Finder, and if you plug a Bluetooth 4.0 dongle it should work too and detect all the devices inside the same wifi network (with "discovered by Everyone" checked).

That's awesome! Great work. I rely on AirDrop a lot and couldn't stand that stupid AirDrop icon (what were they thinking!)

 

[jackluke]

Amazing work!

That's awesome! Great work. I rely on AirDrop a lot and couldn't stand that stupid AirDrop icon (what were they thinking!)

Forgot to say that I used as "wifi base kext" the IO80211Family.kext from Mojave 10.14.5 , but also a previous Mojave version (and even HighSierra) worked too using my patched files for those two machines (only this AirPortBrcm4360 is binary patched).

And if you have a "Bluetooth 4.0 dongle usb" (also a MS Windows one) it should work too discovering other devices in the same Wifi.

The iOS devices with iOS 12.x (or earlier) should be detected also without the BT 4.0 dongle plugged, probably because the internal BT 2.1 is suffice for those devices.
[doublepost=1561121090][/doublepost]AirDrop it's bidirectional working (also on an iOS 13 device), I'm using however a generic Bluetooth 4.0 dongle plugged to Mac 2010 , for now only those two machine, but maybe could work also on machine equipped with a Broadcom Wifi 0x14E4, 0x93 (or similar 0x9X)

but I guess not on older Atheros Wifi Airport.

 

[CooperBox]

Yes, I believe it is important to have some humor and maybe even levity in the "unsupported threads" especially. One of my favorite lines from dosdude1 is: "Just ignore it and continue." Always gets me through.

I just love that quote from dosdude, "Just ignore it and continue." I plan to put this into play immediately regarding my wife. If you see no more posts from me, expect the worst.......

 

[Loyd-01a]

Just fixed the USB issues on certain systems, such as the MacBook6,1. Now, the keyboard and trackpad should work 100% perfectly! Patcher has been updated with the new changes. All that was needed was a modification to LegacyUSBInjector.kext, which I have attached.

EDIT: I've also updated my "patch pack" to include this change as well. I've also added a kext to fix nVidia MCP79/89 Ethernet controllers under Catalina.

For those of you waiting, I plan to have my full, 100% automated Catalina Patcher ready within a couple weeks.

@dosdude1
Thank you always to you and to all the contributors for this wonderful work!
How can one run the script contained in your "patch pack" from a second partition containing Mojave?
Thank you
PS: as always your disinterested dedication and your modesty impose admiration

 

[Starplayr]

Just fixed the USB issues on certain systems, such as the MacBook6,1. Now, the keyboard and trackpad should work 100% perfectly! Patcher has been updated with the new changes. All that was needed was a modification to LegacyUSBInjector.kext, which I have attached.

EDIT: I've also updated my "patch pack" to include this change as well. I've also added a kext to fix nVidia MCP79/89 Ethernet controllers under Catalina.

For those of you waiting, I plan to have my full, 100% automated Catalina Patcher ready within a couple weeks.

I have found the LegacyUSBInjector.kext for other Macs to be very valuable. ParrotGeek did a really go job on it. Thank you for updating it for newer MacBookPros. It works really well with Apple's USB Kexts with Catalina on getting things like the Keyboard and Trackpad. I have had the same experience with it on the Mac Pro 3,1 with the Magic Trackpad 2 and Magic Keyboard 2 along with the C922 USB WebCam and the iPhone's screen as a Quicktime recording without the need for additional USB Kext mods includes USB Charging as well.
[doublepost=1561125053][/doublepost]

That's awesome! Great work. I rely on AirDrop a lot and couldn't stand that stupid AirDrop icon (what were they thinking!)

Interesting. I will check out to see if Air drop is working or not on my system. Everything else I have is working with my minimalistic CatWoman patch. My Magic Trackpad 2 and Magic Keyboard 2 Bluetooth work. Also my AirPods2 over bluetooth work.
[doublepost=1561125377][/doublepost]

Indeed - Good luck - re-engineering one's self is always a challenge. You've got skills man - don't let the interview process get you down. Software Engineers can be very close-minded, obtuse and set in their ways, but once you break through you're good. I'm sure you can use some of your experiences here to your advantage...

Way off topic: I have about 5 iOS Apps that I am getting ready for the AppStore now. I plan to use their source code and releases as a way to showcase my work to a prospect and use it to turn the tables. Some of my best work uses my own libraries, APIs, front and back code in Swift. Using embedded web servers to carry out tasks, so I don't have to make a lot of server calls to my server but use the same exact code server side and client side.

 

[pkouame]

I have found the LegacyUSBInjector.kext for other Macs to be very valuable. ParrotGeek did a really go job on it. Thank you for updating it for newer MacBookPros. It works really well with Apple's USB Kexts with Catalina on getting things like the Keyboard and Trackpad. I have had the same experience with it on the Mac Pro 3,1 with the Magic Trackpad 2 and Magic Keyboard 2 along with the C922 USB WebCam and the iPhone's screen as a Quicktime recording without the need for additional USB Kext mods includes USB Charging as well.
[doublepost=1561125053][/doublepost]
Interesting. I will check out to see if Air drop is working or not on my system. Everything else I have is working with my minimalistic CatWoman patch. My Magic Trackpad 2 and Magic Keyboard 2 Bluetooth work. Also my AirPods2 over bluetooth work.
[doublepost=1561125377][/doublepost]
Way off topic: I have about 5 iOS Apps that I am getting ready for the AppStore now. I plan to use their source code and releases as a way to showcase my work to a prospect and use it to turn the tables. Some of my best work uses my own libraries, APIs, front and back code in Swift. Using embedded web servers to carry out tasks, so I don't have to make a lot of server calls to my server but use the same exact code server side and client side.

That’s a great idea. I interview prospective developers a lot and their’s nothing more impressive than showcasing your work in github. Luck.