- Joined
- Nov 24, 2016
- Messages
- 73
- Motherboard
- VN7-791G
- CPU
- i7-4720HQ
- Graphics
- Intel 4600HD
- Mac
- Classic Mac
- Mobile Phone
I know it might mix things up...
But regarding AppleUSBMultitouch.kext.
I went through regular procedure of modifying VendorID and one of DeviceID's with no luck. There are 4 blocks of sets 2 as a pair and 2 separate (compared by DeviceID Arrey). So I modified the first pair and rest of them one at a time. No luck. It seems there might be some additional check somewhere along kext load path that prevents it to be loaded.
I found original MacBookPro 11,2 IOReg (attached) and am wondering could I use Clover to inject proper USB device or modify kext to finally load it.
Could you point me how to trace what is loading AppleUSBMultitouch.kext? Or how to trace it's rejection?
I do think the example form Clover wiki will do:
<dict>
<key>Name</key>
<string>AppleHDAController</string>
<key>Comment</key>
<string>Patch_to_not_load_this_driver</string>
<key>InfoPlistPatch</key>
<true/>
<key>Find</key>
<string>0x04020000</string>
<key>Replace</key>
<string>0x44220000</string>
</dict>
So definitely 2 such patches will be needed for DevID and VendorID at least!
But regarding AppleUSBMultitouch.kext.
I went through regular procedure of modifying VendorID and one of DeviceID's with no luck. There are 4 blocks of sets 2 as a pair and 2 separate (compared by DeviceID Arrey). So I modified the first pair and rest of them one at a time. No luck. It seems there might be some additional check somewhere along kext load path that prevents it to be loaded.
I found original MacBookPro 11,2 IOReg (attached) and am wondering could I use Clover to inject proper USB device or modify kext to finally load it.
Could you point me how to trace what is loading AppleUSBMultitouch.kext? Or how to trace it's rejection?
I do think the example form Clover wiki will do:
<dict>
<key>Name</key>
<string>AppleHDAController</string>
<key>Comment</key>
<string>Patch_to_not_load_this_driver</string>
<key>InfoPlistPatch</key>
<true/>
<key>Find</key>
<string>0x04020000</string>
<key>Replace</key>
<string>0x44220000</string>
</dict>
So definitely 2 such patches will be needed for DevID and VendorID at least!