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.

0403979

Cancelled
Original poster
Jun 11, 2018
1,402
1,734
Let me clean the libraryvalidation script, nvram and preboot boot.plist and report.
To be clear, all this does is adds the boot-args back to the NVRAM. Not sure if it works without already entering them into NVRAM prior to booting.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,060
To be clear, all this does is adds the boot-args back to the NVRAM. Not sure if it works without already entering them into NVRAM prior to booting.

I have tried this:

- sudo nvram boot-args=""
- removed the ASentientBot com.apple.libraryvalidation.plist
- cleared the Preboot com.apple.boot.plist without Kernel flags
- copied your file to this path /System/Volumes/Data/Library/LaunchDaemons/
and to this path /System/Library/LaunchDaemons/

but doesn't worked.

Nothing is added to nvram or boot-args.
 

0403979

Cancelled
Original poster
Jun 11, 2018
1,402
1,734
I have tried this:

- sudo nvram boot-args=""
- removed the ASentientBot com.apple.libraryvalidation.plist
- cleared the Preboot com.apple.boot.plist without Kernel flags
- copied your file to this path /System/Volumes/Data/Library/LaunchDaemons/
and to this path /System/Library/LaunchDaemons/

but doesn't worked.

Nothing is added to nvram or boot-args.
I just told you that the purpose of the launchdaemon is to ensure it stays in NVRAM. If it isn't in NVRAM, the system won't get far enough to run the launchdaemon
 
Last edited:

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,752
Logsden Oregon
Back to re-installing 10.15.3 as I used the launchdaemon script Julian provided the swupatch to download the update then applied the catalinaswuamfifix patch applied all but the platform check patch as was not needed to be checked in dev beta 3 got into my desktop then rebooted applied the legacy video patch rebooted got a circle with a line through it rebooted back into the patcher applied all the post install patches still got the circle with a line through it did or am reset now couldn’t get into the desktop
 

applCore

macrumors regular
May 3, 2011
192
77
I see that you're still patiently looking for audio solutions for your MP5,1. I'm running Catalina 10.15.3 on my HackPro5,1 without any problems. I was originally running with legacy NVidia graphics / DosDude and switched to a Sapphire Pulse RX580 (which required an in-place install of 10.15.3, removal of the Legacy NVidia kexts and removal of the patch updater prefpane). The upgrade was painless (I performed the upgrade from 10.14.6 and from 10.15.2 while I was testing).

Is your MP5,1 a dual-CPU model? If so, could that explain the audio issue?

Yes, I do have a dual CPU system - how can that explain the audio issue?
 
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,060
Back to re-installing 10.15.3 as I used the launchdaemon script Julian provided the swupatch to download the update then applied the catalinaswuamfifix patch applied all but the platform check patch as was not needed to be checked in dev beta 3 got into my desktop then rebooted applied the legacy video patch rebooted got a circle with a line through it rebooted back into the patcher applied all the post install patches still got the circle with a line through it did or am reset now couldn’t get into the desktop

"The circle with a line" it's because apple from 4b4 has decided with their OTA to replace the Preboot boot plist with a clean one (probably they refreshed also the APFS UUID), so follow this tip that should work, boot again from the USB Catalina Patcher, open a recovery Terminal and type exactly this (quotes and underscores included):

Code:
mount -uw /
nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
reboot

Once you are in 10.15.4b4 desktop, apply the ASentientBot new libraryvalidation script.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,060
It would have worked if I had known that I needed to apply the the first patch in the post install patches as I though it needed to be unchecked like in Dev Beta 3

It was because the post-install first patch re-replaced the Preboot boot-args with only -no_compat_check , but ASentientBot libraryvalidation after an OTA update needs anyway a first round of amfi_get_out_of_my_way=1 , I understand that a pre-patched com.apple.boot.list is useful but it follows a particular route to apply, while instead a NonVolatileRAM is quicker and can be applied from any OSX Installer, any single user mode, any legacy OSX, even from Snow Leopard, and it will be stored (until a manual PRAM reset) and work for newer macOS too when set from Leopard for example.
 

deeveedee

macrumors member
May 2, 2019
95
127
Yes, I do have a dual CPU system - how can that explain the audio issue?

I thought I had read about an audio issue related to dual-CPU on the MP5,1. However, I did a quick search and could only find this: https://forums.macrumors.com/threads/strange-audio-issue-on-mp-4-1-5-1-mojave-10-14-4.2176792/

While this thread refers to "stuttering" and not complete loss of sound, this may be helpful, as it discusses remedies that may be relevant/applicable to you as well.

EDIT: Here's another thread that refers to a case where the user needed to "clean NVRAM three times" and re-apply -no_compat_check. https://forums.macrumors.com/thread...ina-work-with-macpro5-1.2183978/post-27422749
 
Last edited:

hvds

macrumors 6502a
Sep 1, 2017
638
1,387
Switzerland
It was because the post-install first patch re-replaced the Preboot boot-args with only -no_compat_check , but ASentientBot libraryvalidation after an OTA update needs anyway a first round of amfi_get_out_of_my_way=1 , I understand that a pre-patched com.apple.boot.list is useful but it follows a particular route to apply, while instead a NonVolatileRAM is quicker and can be applied from any OSX Installer, any single user mode, any legacy OSX, even from Snow Leopard, and it will be stored (until a manual PRAM reset) and work for newer macOS too when set from Leopard for example.
ASentientBot's libraryvalidation plist worked fine for me, without amfi settings in NVRAM.

I did as follows (using a full installer obtained via Mojave, as OTA doesn't work on my 2009 machine on external disks):
- have a clone with 10.15.3 on my external SSD
- create/set the com.apple.security.libraryvalidation.plist to DisableLibraryValidation YES (already done in my internal SSD before cloning, will be useful throughout Catalina's life)
- install .4b3 over the external SSD, with bootable USB installer made with patcher 1.3.0 (options no APFS booter, no automatic paching)
- won't boot as no patches applied yet, but I wanted to watch what happens: the libraryvalidation plist is still intact, boot-args still only -no_compat_check
- applied all proposed patches, including platform check and legacy video card
- boots fine, despite some unimportant AMFI messages regarding CCC, seen in verbose mode
- then installed the new ASentientBot wrappers, rebuilt caches
- all fine, with transparency.

Next I'll try with automatic patching - should work as well.

EDIT: it does. Made a new bootable USB installer from .4b3 with patcher 1.3.0, automatic patching option this time, used it to install over a freshly cloned 10.15.3 external SSD. Proceeds to boot without any intervention... didn't install the newer wrappers yet, transparency is there nevertheless.
Just the Monitors system setting is not showing resolutions, nor does applying night shift with patch updater take effect. Minor things.
So com.apple.security.libraryvalidation.plist is working very well... needs to be done only once and survives system update.

Thanks @ASentientBot!

(MBP5,2 17" mid 2009, 2.8GHz T9600, 8GB, APFS ROM patch applied, Samsung SSD 840/860 EVO with APFS. Catalina 10.15.4b3)
 

Attachments

  • Bildschirmfoto 2020-03-05 um 12.44.54.png
    Bildschirmfoto 2020-03-05 um 12.44.54.png
    41.2 KB · Views: 92
  • Bildschirmfoto 2020-03-05 um 13.00.44.png
    Bildschirmfoto 2020-03-05 um 13.00.44.png
    102.5 KB · Views: 109
  • Bildschirmfoto 2020-03-05 um 13.30.10.png
    Bildschirmfoto 2020-03-05 um 13.30.10.png
    173.4 KB · Views: 113
  • IMG_3862.JPG
    IMG_3862.JPG
    558.9 KB · Views: 123
  • IMG_3863.JPG
    IMG_3863.JPG
    661.2 KB · Views: 108
Last edited:

Minh_Ton

macrumors member
May 15, 2019
64
129
Hue, Vietnam
Following @ASentientBot's post, I got the Japanese Input Method partially working by replacing these files from Mojave:

Code:
/usr/lib/libmecabra.dylib
/System/Library/Input Methods/JapaneseIM.app
/System/Library/PrivateFrameworks/TextInput.framework

Just by replacing those file, the Japanese IM worked, however after messing around with it a little bit I am still seeing some strange symbols popping up following by a crash of the JapaneseIM.... But I can still type some simple sentences in Japanese without any problems. Yay!

---------------

Edit: Got the JapaneseIM fully working by replacing one more framework (With no more crashing or "おはよ4"):
Code:
/System/Library/PrivateFrameworks/TextInputCore.framework

Hopefully this will help to fix the problems that Japanese people on unsupported Macs are encountering. Good night!
Screen Shot 2020-03-05 at 11.03.08 PM.png
 

Attachments

  • JapaneseIM.zip
    1.6 MB · Views: 62
  • libmecabra.dylib.zip
    1.9 MB · Views: 75
  • TextInput.framework.zip
    399.9 KB · Views: 87
  • TextInputCore.framework.zip
    778 KB · Views: 100
Last edited:

deeveedee

macrumors member
May 2, 2019
95
127
I was trying to diagnose a USB issue on my MBP6,2 (which turned out to be caused by Android File Transfer) and learned that Mojave and Catalina IOUSBHostFamily.kext no longer provide USB sleep / wake power IORegistry keys for MacBookPro6,2. Interestingly enough, Catalina IOUSBHostFamily.kext does still include MacPro5,1.

Does it matter that IOUSBHostFamily.kext no longer includes the USB power IORegistry keys for MacBookPro6,2 and if so, does the DosDude patcher address this? If so, I must have neglected to install one of the required patches.

Thank you.
 
Last edited:
  • Like
Reactions: ASentientBot

Pinarek

macrumors 6502
Sep 16, 2009
320
288
Germany-Berlin
With my not supported HackBook laptop, the update to the DP4 from 10.15.4 went absolutely smoothly.
I was amazed at myself.

After stage 2 of the installation, the @dosdude1 patches for video and WLAN etc. are executed by the USB stick and then boots immediately, without any deficiency. I didn't need to install a single framework or kext afterwards, everything stayed the same as in DP3. Just that only "colors" can be seen in the system settings monitor and no option for the graphics resolution "monitors". But it is not important.

That with the BIOS, which jumps back to default, is still the same since the DP2. Even changing the AppleRTC.kext from Catalina 10.15.4 DP1 and Mojave 10.14.6 did not change anything.
I suspect it's nvram problem.
The update on the HackBook was easier than with my other 2 supported Hackintosh (see my signature).
 

ASentientBot

macrumors 6502a
Jun 27, 2018
843
3,301
SkyLight.framework
Following @ASentientBot's post, I got the Japanese Input Method partially working by replacing these files from Mojave:

Code:
/usr/lib/libmecabra.dylib
/System/Library/Input Methods/JapaneseIM.app
/System/Library/PrivateFrameworks/TextInput.framework

Just by replacing those file, the Japanese IM worked, however after messing around with it a little bit I am still seeing some strange symbols popping up following by a crash of the JapaneseIM.... But I can still type some simple sentences in Japanese without any problems. Yay!

---------------

Edit: Got the JapaneseIM fully working by replacing one more framework (With no more crashing or "おはよ4"):
Code:
/System/Library/PrivateFrameworks/TextInputCore.framework

Hopefully this will help to fix the problems that Japanese people on unsupported Macs are encountering. Good night!
View attachment 897589
Nice! I never figured out a proper solution to this, despite spending quite a lot of time on it.

The other thing I played with was launching the JapaneseIM main binary under Intel SDE (which is supposed to emulate AVX) but SDE doesn't seem to work on Catalina at all. I'd guess if you can get that working, it may be the best solution.


Edit: I apologize for misreading your post and thinking it was still only partly functional; after re-reading I realize you got it fully working. Excellent job! I remember your News+ fix on Mojave, glad you are still here and still being awesome :)
 
Last edited:

MrZupp

macrumors regular
Apr 18, 2019
129
19
hey guys, sorry if I'm comming outta nowhere, but I'm having some trouble with my macbook pro late 2011, i used dosdude1's guide ( as I don't have a Lattice programmer on my hand right now, but I'm planing to buy one ) to turn off the AMD gpu, despite the fact that it's still in working condition, the machine gets super hot, reaching 60°C-70°C right after returning from sleep. Right after I bought it, I installed 10.15.3 using dosdude1's patcher, and then I replaced the thermal paste with an Arctic MX-2 paste. Any suggestions?
 
  • Like
Reactions: TimothyR734

deeveedee

macrumors member
May 2, 2019
95
127
hey guys, sorry if I'm comming outta nowhere, but I'm having some trouble with my macbook pro late 2011, i used dosdude1's guide ( as I don't have a Lattice programmer on my hand right now, but I'm planing to buy one ) to turn off the AMD gpu, despite the fact that it's still in working condition, the machine gets super hot, reaching 60°C-70°C right after returning from sleep. Right after I bought it, I installed 10.15.3 using dosdude1's patcher, and then I replaced the thermal paste with an Arctic MX-2 paste. Any suggestions?

EDIT: I just re-read your question and while my response below is still a possibility, I am not familiar with the thermal solution for your MBP. Did you measure the operating temp before you replaced the "thermal paste?" Is it possible that what you are referring to as the old "thermal paste" was actually a thermal pad (had a non-zero thickness) that you removed and replaced with MX-2?

------------------------------------------------------

I lowered my MBP6,2 temps by disabling Spotlight searches and changing Display Accessibility properties as listed below. Try these and if they lower CPU/GPU temps for you, decide which you want to keep / discard based on your preferences.
  • System Preferences > Spotlight > Search Results: Uncheck all options
  • System Preferences > Spotlight > Privacy: Add all Volumes
  • System Preferences > Accessibility > Display: Check "Reduce motion"
  • System Preferences > Accessibility > Display: Check "Reduce transparency"
 
Last edited:

Minh_Ton

macrumors member
May 15, 2019
64
129
Hue, Vietnam
Nice! I never figured out a proper solution to this, despite spending quite a lot of time on it.

The other thing I played with was launching the JapaneseIM main binary under Intel SDE (which is supposed to emulate AVX) but SDE doesn't seem to work on Catalina at all. I'd guess if you can get that working, it may be the best solution.


Edit: I apologize for misreading your post and thinking it was still only partly functional; after re-reading I realize you got it fully working. Excellent job! I remember your News+ fix on Mojave, glad you are still here and still being awesome :)

You can also have the Korean keyboard (or any languages resemble the Chinese language) to work just by replacing those frameworks and lib file, and the Keyboard-IM app in /System/Library/Input Methods/

For example, I replaced the KoreanIM in /System/Library/Input Methods/ and it worked flawlessly without issue (despite knowing nothing about Korean here).

-----------------

Edit: Discovered that just replacing the two frameworks in /System/Library/PrivateFrameworks/ is enough to fix those keyboard input issues. No need to replace the input method file in /System/Library/Input Methods/ or the lib file.

-----------------

IMPORTANT EDIT: I found out that this fix causes some missing symbols errors in /System/iOSSupport/System/Library/PrivateFrameworks/UIKitCore.framework/Versions/A/UIKitCore, which prevents Home, News, Voice Memos,... and other Catalyst app to crash.

Crash log:

Code:
Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x4] Symbol missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Symbol not found: _OBJC_CLASS_$_TIAnalyticsEventSpec
  Referenced from: /System/iOSSupport/System/Library/PrivateFrameworks/UIKitCore.framework/Versions/A/UIKitCore (which was built for Mac OS X 13.1)
  Expected in: /System/Library/PrivateFrameworks/TextInput.framework/TextInput
 in /System/iOSSupport/System/Library/PrivateFrameworks/UIKitCore.framework/Versions/A/UIKitCore

-----------------

Edit: I decided to only replace /System/Library/PrivateFrameworks/TextInputCore.framework while keeping the TextInput.framework intact. With the inability to type Japanese without replacing TextInput.framework, I have to replace /System/Library/Input Methods/JapaneseIM.app as well as /usr/lib/libmecabra.dylib to make it work again.

Screen Shot 2020-03-06 at 6.13.33 AM.png
Screen Shot 2020-03-06 at 6.40.20 AM.png
 
Last edited:

trifero

macrumors 68020
May 21, 2009
2,305
1,983
hey guys, sorry if I'm comming outta nowhere, but I'm having some trouble with my macbook pro late 2011, i used dosdude1's guide ( as I don't have a Lattice programmer on my hand right now, but I'm planing to buy one ) to turn off the AMD gpu, despite the fact that it's still in working condition, the machine gets super hot, reaching 60°C-70°C right after returning from sleep. Right after I bought it, I installed 10.15.3 using dosdude1's patcher, and then I replaced the thermal paste with an Arctic MX-2 paste. Any suggestions?
I have the same Mac as yours. Well, three of them, in fact. at 40º-45º running in normal use. Did you check the fans?. Are they clean?
 
  • Like
Reactions: TimothyR734

macsba

macrumors 6502a
Jan 5, 2015
644
641
Next to my Mac.
Greetings all;

Some importance in this thread. From this point on, can we agree to use one of following, the Celsius or Fahrenheit scale? Not both of them. In most cases, the Celsius scale would be preferred since we have international members in this thread.

Just an idea.
 
  • Like
Reactions: TimothyR734

MrZupp

macrumors regular
Apr 18, 2019
129
19
I have the same Mac as yours. Well, three of them, in fact. at 40º-45º running in normal use. Did you check the fans?. Are they clean?
Yes, I cleaned the whole logic board and the fans with compressed air, also, in response to @deeveedee , before I measured around 65°C - 70°C idle on Catalina.
 

Dilli

macrumors 6502
Oct 21, 2019
451
428
I am facing a new issue. Videos in Photos app saved in my library plays choppy in Catalina. These videos was taken in 1080p/4k resolution on my Galaxy Note and then transferred to photos in Catalina. Never faced this issue earlier in High Sierra for same videos. I am using my iMac with upgraded Geforce Nvidia card.
Why is this issue there?
 

trifero

macrumors 68020
May 21, 2009
2,305
1,983
Yes, I cleaned the whole logic board and the fans with compressed air, also, in response to @deeveedee , before I measured around 65°C - 70°C idle on Catalina.
I suppose you applied the thermal paste correctly. Maybe you can use Istat Menu or similar to find out what is happening. Also, try install High Sierra in an external drive, Usb, and see if the problem persists
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.