macOS 10.14 Mojave on Unsupported Macs Thread

[0403979]

While claiming that Apple somehow optimised things under the hood and that this shows especially on semi-accelerated non OpenGL-supported systems (like the intel x3100), I understand that you won't believe it without proof. So here we go.
Shown first and last in the clip: Mojave on x3100 (MB4,1) vs. Yosemite on x3100 (MBAir1,1) in the middle part of the clip.
Example here is iTunes (current version on both machines).

https://www.facebook.com/video.php?v=1953101251425553

[doublepost=1552573159][/doublepost]@0403979
I´m aware of your concerns of having multiple prelinked kernels. Just don't see how we could completely avoid it. Imho, it would not be necessary to cover all macOS releases, but to look forward and cover the current and future 10.14.x (let's see how the game changes with 10.15 anyway).
I found that the patched installer works fine on MB4,1 (after injecting the right kernel) and on MB5,2 and on MB Air 4,1.
So it could actually be that if you find the minimum configuration (for MB4,1) it might work on all newer systems as well. I can test on a couple more machines here. The issue remains though that the installation script itself (on the USB installer volume) will have to supply different configurations for the target platforms. That's what represents the main work to be done, I´d guess...

Not having a machine to test personally is an issue (atm . I could implement multiple but that would require asking the user. Could you test the full patched os with my patcher on the 5,2? I want to see if the trackpad works. Very interesting findings on optimisation btw.

 

[avz]

Regarding the News app in macOS Mojave (10.14.3) – mine hasn't been working since the initial Mojave release, any suggestions?

Running maintenance tasks in Onyx usually help with these things. Unless I just got lucky.

 

[TimothyR734]

I applied @pkouame's vibrancy patch, on other apps the menubars have no anomalies at all but on the News app menubar, it is ugly, grey and dark on light mode. Any workaround for this? View attachment 826271

I heard from pkouame and will be working on a new hybrid patch soon
[doublepost=1552595458][/doublepost]

Sorry, I just saw this.
Not sure what comparative GLDriver file on your model that needs deletion.
Hope you were able to resolve with the suggestions from other folks on this thread.

No luck yet I think it might have to do with the backlight or possible the core brightness as I got into the desktop with 10.14.4 but after a few mins it would reboot

 

[Rami Ashqar]

Hello everybody, my mid 2009 MBP was working just fine on 10.14.3 >>> but now this has popped up from the patcher and every time I reinstall the patch it shows again after restart. So my iPhone is not connecting or charging over the USB port even though the flash desks and external hard desks work fine and my iPhone used to connect perfectly before.
P.S. > The USB cable is fine and connects my iPhone to windows PC normally.
THANK YOU

 

[Larsvonhier]

Hello everybody, my mid 2009 MBP was working just fine on 10.14.3 >>> but now this has popped up from the patcher and every time I reinstall the patch it shows again after restart. So my iPhone is not connecting or charging over the USB port even though the flash desks and external hard desks work fine and my iPhone used to connect perfectly before.
P.S. > The USB cable is fine and connects my iPhone to windows PC normally.
THANK YOU

https://www.dropbox.com/s/ys6bd9grj4evl8n/Screenshot 2019-03-14 21.50.29(2).png?dl=0

Boot your installer stick, apply patches from there for your MBP2009 and do not re-apply patches from the patch updater tool once booted to login/finder. This might help.

 

[Larsvonhier]

Anyone else notices that Siri does not work anymore on 10.14.4 b4 (and b5) ?
After invoking (with ALT-Space or icon in menu bar), the ploink sound comes, notification shifts in from top right and then before taking any sound input, Siri seems to crash?.
Same behavior here on MacBook Air 4,1, MacBook 5,2, MacBook 4,1 and MacBook Pro 5,2 (so not only C2D related, it seems).


Edit:
@0403979
Have tried the patched installer (created with your script and a 10.14.3 image).
The installer runs perfectly well on these machines:
MacBook 5,2 (incl. trackpad basic functions)
MacBook Pro 5,2
MacBook Air 4,1
MacBook Air 2,1
MacBook 7,1

but as before (no wonder without exchanged prelinked kernel) crashes on MacBook 4,1 due to
lost USB connection to external installer volume during runtime.
If kernel is changed to a suitable MB4,1 version, trackpad on MB5,2 does not work in a usable manner.

 

[16v]

Hello! I installed Mojave on my Macbook Pro Late 2008 with Mojave Patcher and everything goes perfect! Anyone knows how to " echo off " the commands and patches of the EFI SHELL SCRIPT that's shows up every time i turn on my mac ?

Regards

Had the same issue.
Answer somewhere in this smal thread! ;-)
It a really simple issue to solve:
Just go to settings and select mojave disk as boot device.
-solved!

Enjoy

 

[0403979]

Anyone else notices that Siri does not work anymore on 10.14.4 b4 (and b5) ?
After invoking (with ALT-Space or icon in menu bar), the ploink sound comes, notification shifts in from top right and then before taking any sound input, Siri seems to crash?.
Same behavior here on MacBook Air 4,1, MacBook 5,2, MacBook 4,1 and MacBook Pro 5,2 (so not only C2D related, it seems).


Edit:
@0403979
Have tried the patched installer (created with your script and a 10.14.3 image).
The installer runs perfectly well on these machines:
MacBook 5,2 (incl. trackpad basic functions)
MacBook Pro 5,2
MacBook Air 4,1
MacBook Air 2,1

but as before (no wonder without exchanged prelinked kernel) crashes on MacBook 4,1 due to
lost USB connection to external installer volume during runtime.
If kernel is changed to a suitable MB4,1 version, trackpad on MB5,2 does not work in a usable manner.

The MB5 trackpad dosen’t work with an MB4 kernel? By basic fonctions you mean what?

 

[jhowarth]

Running maintenance tasks in Onyx usually help with these things. Unless I just got lucky.

The problem with the Onyx approach is that it assumes that all of the essential file installations were completed before the update terminated.

 

[Larsvonhier]

The MB5 trackpad dosen’t work with an MB4 kernel? By basic fonctions you mean what?

Basic function on MB5,2: Just very, very slow mouse pointer movement. But it´s the same behavior with dosdude1´s patched installer.
With the prelinked kernel for MB4,1 I cannot move mouse pointer with trackpad on MB 5,2 in all directions, only up/down. So I´d say it is not useable in this combination.

 

[0403979]

Basic function on MB5,2: Just very, very slow mouse pointer movement. But it´s the same behavior with dosdude1´s patched installer.
With the prelinked kernel for MB4,1 I cannot move mouse pointer with trackpad on MB 5,2 in all directions, only up/down. So I´d say it is not useable in this combination.

So I would need two different kernels but both tools have the same issues on the MB5? Are you sure it’s not a hardware issue?

 

[Rami Ashqar]

Boot your installer stick, apply patches from there for your MBP2009 and do not re-apply patches from the patch updater tool once booted to login/finder. This might help.

Hi,
Thanks for the help, but I've tried so but no luck at all, is there's any other solution ?
notice, if this would help, this has occurred since the last patcher update when it added itself to the system preferences ?!

 

[Larsvonhier]

Hi,
Thanks for the help, but I've tried so but no luck at all, is there's any other solution ?
notice, if this would help, this has occurred since the last patcher update when it added itself to the system preferences ?!

What you can do is revert back to the working setup - i.e. by installing 10.14.3 again (plain over the newer system, you will not lose any data/user profiles etc.). Then update to 10.14.4 (b4 or b5) again and avoid the latest patch updater suggestion(s) for the time being. The old patch updater is still available at dosdude1´ s website, btw.
[doublepost=1552656805][/doublepost]

So I would need two different kernels but both tools have the same issues on the MB5? Are you sure it’s not a hardware issue?

Its clearly not a HW issue. And it is not top priority anyway - as the installer can be used to install the latest 10.14.3 (final) onto MB5,2. There is a trackpad/keyboard patch in the patcher tool afterwards that makes the MB5,2 pretty useable after it is applied. Its just not present in the installer setup, but no real problem...

 

[avz]

Had the same issue.
Answer somewhere in this smal thread! ;-)
It a really simple issue to solve:
Just go to settings and select mojave disk as boot device.
-solved!

Enjoy

I believe this solution assumes that the user applied APFS ROM patch first?

 

[tokiacop]

Had the same issue.
Answer somewhere in this smal thread! ;-)
It a really simple issue to solve:
Just go to settings and select mojave disk as boot device.
-solved!

Enjoy

Hi! Thanks for the answer. When you say "go to settings" you mean System Preferences/Startup Disk of the mojave system on my MAC HD?
I did it but no luck for me. I still see the "verbose mode" of the EFI SHELL every time i do a cold start of my mac and now it take 10 sec more after try this. 10 sec blackscreen / 5 sec Efi Shell and then Apple Logo. It seems that this solution don't work on my MBP 08..

 

[0403979]

What you can do is revert back to the working setup - i.e. by installing 10.14.3 again (plain over the newer system, you will not lose any data/user profiles etc.). Then update to 10.14.4 (b4 or b5) again and avoid the latest patch updater suggestion(s) for the time being. The old patch updater is still available at dosdude1´ s website, btw.
[doublepost=1552656805][/doublepost]
Its clearly not a HW issue. And it is not top priority anyway - as the installer can be used to install the latest 10.14.3 (final) onto MB5,2. There is a trackpad/keyboard patch in the patcher tool afterwards that makes the MB5,2 pretty useable after it is applied. Its just not present in the installer setup, but no real problem...

I don’t have a trackpad patch in my patcher. I’ll look at dosdude’s version. Can you video the issue so I can better understand it?

 

[avz]

Hi! Thanks for the answer. When you say "go to settings" you mean System Preferences/Startup Disk of the mojave system on my MAC HD?
I did it but no luck for me. I still see the "verbose mode" of the EFI SHELL every time i do a cold start of my mac. It seems that this solution don't work on my MBP 08..

This is because you have not applied the APFS ROM patch. It is possible that your machine has an Nvidia chipset, Greg Hrutkay advises not to go ahead with the APFS ROM patch as you will probably brick your machine.

 

[sabankuru]

Hello, my question is, is this legal to install it on a unsupported mac? How is the comparison between hackintosh and patcher?

 

[0403979]

Hello, my question is, is this legal to install it on a unsupported mac? How is the comparison between hackintosh and patcher?

Hackintoshing, jailbreaking, and patching for unsupported macs is legal. Selling macs or iOS devices with these modifications already applied is not. Apple can come after you but not in court.

 

[Jas-Singh685]

I'm having trouble getting APFS recovery to work on my MBP 8.1 2011, I keep getting the prohibited sign. I've tried adding -no_compat_check to the com.apple.Boot.plist and it's a no-go. I tried nvram boot-args="-no_compat_check -v" too, but verbose output tells me this version of OS X is not supported on this platform! The only way I can get this to work is by using nvram boot-args="-no_compat_check kext-dev-mode=1" posted by @jackluke. Of course upon an NVRAM reset, this gets erased.

If I install using HFS+ I can add the no_compat_check to the boot.plist and it works fine as it should! (Though extremely slow) Am I doing something wrong with the APFS filesystem?

 

[tokiacop]

This is because you have not applied the APFS ROM patch. It is possible that your machine has an Nvidia chipset, Greg Hrutkay advises not to go ahead with the APFS ROM patch as you will probably brick your machine.

Hello, thank for the answers. I resolved the problem of the 15 sec (or more) of black screen at cold start. Boot the mojave patcher usb installer and run post install options, then i only choose APFS Patch and force rebuild cache. After that the time boot is normal again. I must say that with only this patch my MPB works perfect. The "verbose mode" of EFI shell is still there but at least don´t have the delay start anymore

Thanks!
Regards

 

[avz]

Hello, thank for the answers. I resolved the problem of the 15 sec (or more) of black screen at cold start. Boot the mojave patcher usb installer and run post install options, then i only choose APFS Patch and force rebuild cache. After that the time boot is normal again. I must say that with only this patch my MPB works perfect. The "verbose mode" of EFI shell is still there but at least don´t have the delay start anymore

Thanks!
Regards

I am glad that you figured out the difference between APFS patch and APFS ROM patch. Just stay with the "verbose mode" for the safety of your Mac and use only one partition to avoid confusion and long boots.

 

[Larsvonhier]

This is because you have not applied the APFS ROM patch. It is possible that your machine has an Nvidia chipset, Greg Hrutkay advises not to go ahead with the APFS ROM patch as you will probably brick your machine.

Cannot confirm this. Did the APFS ROM patch successfully on 15" and 17" MB Pro 4,1 with the NVIDIA chipset, and on other newer machines with NVIDIA as well. Nothing bricked, except MacBook Air 2,1 (which I did with the old version of the APFS ROM patch and dare not to re-do even with the newer version where you can confirm the ROM finding).

 

[16v]

I also dont have apfs rom patched and it worked for me. I asked this here too and this was the answer.

But now i patched my bootrom.

 

[avz]

Cannot confirm this. Did the APFS ROM patch successfully on 15" and 17" MB Pro 4,1 with the NVIDIA chipset, and on other newer machines with NVIDIA as well. Nothing bricked, except MacBook Air 2,1 (which I did with the old version of the APFS ROM patch and dare not to re-do even with the newer version where you can confirm the ROM finding).

Congratulations! You got off easy(and so did I). Apparently dosdude1 bricked at least one Nvidia chipset machine during his testing(as Greg mentioned in the video).