macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

That´s true, so we´d either have to wait for final 10.14.4 install image or I´d have to run the prelink process on a 10.14.3 machine again.
But then the result will only run correctly on a MB4,1, right? (See my assumption in my previous post).

Not said, maybe could work on any similar machine and more, for example I use an ultra-patched ext USB Mojave also on supported mac and it's still working even with legacy AppleHDA, legacy USB, patched GPU kext. But only prelinkedkernel is not suffice, many legacy kexts must be replaced also inside S/L/E , where the prelinkedkernel makes its matching verification.

We can learn much from OSX Installers or Recoveries where it's used the minimum number of Extensions (and Frameworks) to reach the GUI mode.

 

[dosdude1]

This is the same with dosdude1’s tool though right?

No, my tool has no issues running the installer on any of the machines it supports.

 

[MBP5_3]

Well, we wouldn't copy the files one-by one. We'd pkgutil --expand-full the package and then cp -R them over the system, I would imagine. I personally haven't worked up the courage to mess with it again after having to reinstall my OS last week.
[doublepost=1540270760][/doublepost]Hey everybody! This applies to very few people, but I'm going to document it since someone might come across this in the future.

I recently tried uploading code to an Arduino for the first time since installing Mojave, and, well, it didn't work. More precisely, I got this error.
View attachment 797603

stk500_recv(): programmer is not responding
stk500_getsync() attempt 1 of 10: not in sync: resp=0x00

I tried a good old ioreg.
View attachment 797604

Then, going off what I saw there, I replaced AppleUSBACM.kext from High Sierra and rebuilt the prelinkedkernel.

Solved!
View attachment 797605

And you can see a couple things are different -- it's called usbmodem411 rather than usbmodem4101 and the ioreg output is also different. Interestingly, there's a new element in the tree: IOModemSerialStreamSync. Related to the "not in sync" errors? In any case, it's working beautifully now.

View attachment 797606

Anyways, so sorry for the long post that is most likely spam to 99% of people. I hope this helps somebody, though. I am just glad to be able to program my trusty Arduino Uno again

@dosdude1 Worth adding to the patcher, deselected by default of course?

Edit: For clarity, all of this is on a MacBook7,1 that already requires replacement of IOUSBFamily and IOUSBHostFamily. Most likely, a newer system not needing these patches, will also not need this one.

Problem: Unable to upload projects to Arduino via the IDE application on Mojave for unsupported devices

This solution worked flawlessly and has saved me from dual booting El Capitan and Mojave. I wanted to elaborate on the process I used for less experience users like myself.

I used three programs to get the job done. I'm sure I could have done it all through terminal but I couldn't figure it out. Here were my steps:

1- Download high Sierra from the App Store. It's 6gb so start now.
2- Download Pacifist, KextBeast and Kext Utility
3- Once High Sierra is downloaded use Pacifist to extract the AppleUSBACM.kext file we need.
3a- In Pacifist choose the button 'open apple installers' and choose the high Sierra package
3b- Use the drop down arrows to expand 'Contents of OSInstall', 'Contents of Core.pkg', 'System', 'Library', 'Extensions' and then highlight AppleUSBACM.kext by clicking on it
3c- Click 'Extract too..." from the menu bar. Choose the desktop (KextBeast will be looking for it there)
4- Use KextBeast to insert the kext file from your desktop to your /systems/library/extension folder. Make sure AppleUSBACM.kext is the only kext file on the desktop.
5- Open kext utility. It will repair your kext folders. Once complete just close the program.
6- Reboot and enjoy your Arduino project.

Sadly I don't visit this forum unless I have an issue so if I've made an error I hope this helps enough to get you in the right direction.

 

[StrangeLoopy]

You will need to track back a few pages to see how to alter the distribution files of updates so they will install
on unsupported Macs. Page 479 #11956
[doublepost=1550475544][/doublepost]
Yep remove the Patch Updater app from Applications/ Utilities, and also remove the com.dosdude1.Patchupdater.plist from /Library/LaunchAgents. Restart your Mac and see if you keep getting prompted.

Thank you, this seems to have worked—I have not seen Patch Updater appear since then!

 

[0403979]

No, my tool has no issues running the installer on any of the machines it supports.

The 5,2 issue is weird but the 4,1 has the same issue on yours too, no?

 

[dosdude1]

The 5,2 issue is weird but the 4,1 has the same issue on yours too, no?

Oh, yeah, it will not boot on the MacBook4,1 due to the USB issues. If you implement the kexts used in the OSXHackers USB Beta kexts archive, that should get a USB installer to boot on the 4,1. I'm not sure how this affects other machines, though.

 

[0403979]

Oh, yeah, it will not boot on the MacBook4,1 due to the USB issues. If you implement the kexts used in the OSXHackers USB Beta kexts archive, that should get a USB installer to boot on the 4,1. I'm not sure how this affects other machines, though.

I would have to create a second prelinked kernel for every version. I don’t even have any old version of Sierra or High Sierra. I don’t how this would be feasible, especially without a test machine. As for the 5,2, all usb kexts replaced in regular Mojave are replaced in the prelinked kernel. LegacyUSB, IOUSBFamily, and IOUSBHostFamily. I have no idea what the issue is.

 

[Navigator98]

Hey guys

Been lurking this thread for many months now, but haven't had a reason to comment yet since I've only just finished repairing my old iMac 27" Late 2009 (iMac 11,1 - 2.8GHz core i7 - ATI HD 4850 - 8GB RAM - SSD).

I've been running Mojave 10.4.3 for about a week now and everything has been mostly buttery smooth (even managed to fix the light theme rendering with MiraMira's UI tweaks on Github). However, recently one, small, yet annoying over time, issue has been plaguing my machine: a few hours after booting the graphics/animations seem to take a serious hit. In short: it seems like the overall system refresh rate drops from 60hz to something around or below 30hz. I don't know how to trigger it manually, as it just seems to happen over time, but the only 'workaround' I've found so far is simply rebooting the computer.

Does anyone have a clue on what could be causing this? I know the ATI HD 4850 isn't Metal-compatible, but apart from this small issue the legacy graphics acceleration patch has been godsend for me - when everything is working as it should, animations and graphics performance are even smoother than on my 2015 13" rMBP - so for me at least, it seems like this machine could keep going for many years!

Anyway, thanks in advance for any suggestions. And many thanks to all the wonderful people literally keeping my machine alive after almost 10 years of use! Looking forward to testing 10.4.4 when it comes out.

 

[Larsvonhier]

I would have to create a second prelinked kernel for every version. I don’t even have any old version of Sierra or High Sierra. I don’t how this would be feasible, especially without a test machine. As for the 5,2, all usb kexts replaced in regular Mojave are replaced in the prelinked kernel. LegacyUSB, IOUSBFamily, and IOUSBHostFamily. I have no idea what the issue is.

When your script detects a 10.14.3 installer image - is the prelinked kernel the one I dropboxed you then and the kexts for MB 4,1 taken?

Edit:
I replaced the prelinkedkernel on the patched installer volume with the one I use on my MB 4,1.
Violá - it works now on both MacBook 5,2 (boots plus full trackpad functionality) and MacBook 4,1 (boots the installer now and works perfectly).

 

[0403979]

When your script detects a 10.14.3 installer image - is the prelinked kernel the one I dropboxed you then and the kexts for MB 4,1 taken?

Edit:
I replaced the prelinkedkernel on the patched installer volume with the one I use on my MB 4,1.
Violá - it works now on both MacBook 5,2 (boots plus full trackpad functionality) and MacBook 4,1 (boots the installer now and works perfectly).

Does the trackpad fonction correctly with my patcher on a regular install on the 5,2?

 

[jackluke]

Oh, yeah, it will not boot on the MacBook4,1 due to the USB issues. If you implement the kexts used in the OSXHackers USB Beta kexts archive, that should get a USB installer to boot on the 4,1. I'm not sure how this affects other machines, though.

They still work and I'd say are safe to use even on your Mojave Patcher, did tested the same ones on an ext usb drive I used to boot MBA1,1 for another reason.
[doublepost=1552418395][/doublepost]

When your script detects a 10.14.3 installer image - is the prelinked kernel the one I dropboxed you then and the kexts for MB 4,1 taken?

Edit:
I replaced the prelinkedkernel on the patched installer volume with the one I use on my MB 4,1.
Violá - it works now on both MacBook 5,2 (boots plus full trackpad functionality) and MacBook 4,1 (boots the installer now and works perfectly).

Confirmed, used your dropbox prelinkedkernel I assume build over 10.14.4 b3 expressly for MB4,1 , and it still boot the Mojave Installer 10.14.2 on an ext USB with all the usb input devices responsive.

 

[DaniloGeekDude]

Yes, I have all of the above and currently am in Beta 4. Upgrading to Beta 5 shortly.

Finally had the time to do the update.



Steps:

• OTA
• Did the download and update via Terminal with this shell command --- sudo sh -c "softwareupdate -ia && reboot"
• Rebooted to USB Mojave Patcher, and ran post install.
• Rebooted to USB Mojave Patcher again and via it's terminal, deleted /S/L/E/AppleIntelHD3000GraphicsGLDriver.bundle.
• Rebooted to my main Mojave partition and ran @dosdude1's 10.14.4accel script.

Now have the latest beta 5 with graphics acceleration.

 

[rayd8or]

Back in late 2018 I tried to upgrade my 2011 iMac 27" i7 to Mojave and it was virtually unusable graphics wise. I knew the 5xxx and 6xxx graphic cards would be no good but had a go anyway. Since reverted to High Sierra. However, my wife's 2011 MacBook Pro developed the GPU failure so I thought I might as well give it a shot. On first attempt it would only boot in Safe Mode. I re-installed Mojave but unchecked Legacy Video Drivers, booted into Safe Mode and ran dGPU disabler by dosdude1. Rebooted normally and voila!!! Works perfectly except for brightness and Sleep not working at all.Enabled Night Shift from the Patcher and makes the MacBook very usable. Thanks to all for the great work!! If the sleep and brightness worked it would be perfect....
I've since tried all the kext removal techniques seen in this forum to resolve these issues - to no avail. Maybe one day a fix will come along but it's been beyond my skills to try and sort it so far.

 

[TimothyR734]

Finally had the time to do the update.

View attachment 826073

Steps:

• OTA
• Did the download and update via Terminal with this shell command --- sudo sh -c "softwareupdate -ia && reboot"
• Rebooted to USB Mojave Patcher, and ran post install.
• Rebooted to USB Mojave Patcher again and via it's terminal, deleted /S/L/E/AppleIntelHD3000GraphicsGLDriver.bundle.
• Rebooted to my main Mojave partition and ran @dosdude1's 10.14.4accel script.

Now have the latest beta 5 with graphics acceleration.

I have a iMac 9,1 Nvidia 9400 gnu which one should I delete out via the terminal and what is the terminal command to delete the bundle thank you

 

[Larsvonhier]

I have a iMac 9,1 Nvidia 9400 gnu which one should I delete out via the terminal and what is the terminal command to delete the bundle thank you

Get dosdude1’s 10.14.4 accel patch and run the script in it - again, see page #1 for link.
If you do it manually, remove the tesla kext via terminal (the other two do not bother your gnu ;-)

 

[jackluke]

I have a iMac 9,1 Nvidia 9400 gnu which one should I delete out via the terminal and what is the terminal command to delete the bundle thank you

If you want be sure just before accepting the update to 10.14.4 beta5, open Mojave Terminal and copy/paste this:

sudo rm -R /System/Library/Extensions/GeForce*.*

but it's almost a bootloop, because the beta5 will re-install the Geforce*.* (Non-Tesla) and will update the OpenGL and GPUsupport frameworks making the system unsupported, while the "Mojave Post-Install" will install again the Geforce*.* (Tesla) but you still can't reach the GUI mode.
So you should not select from Post-Install the "Video-Patch", then you can reach the GUI mode applying the 10.14.4accel patch, and return to Post-Install installing the "Video Patch".

I think we are close to final 10.14.4 , you should wait that dosdude1 adds the 10.14.4accel patch to his Mojave Patcher.

 

[swamprock]

When your script detects a 10.14.3 installer image - is the prelinked kernel the one I dropboxed you then and the kexts for MB 4,1 taken?

Edit:
I replaced the prelinkedkernel on the patched installer volume with the one I use on my MB 4,1.
Violá - it works now on both MacBook 5,2 (boots plus full trackpad functionality) and MacBook 4,1 (boots the installer now and works perfectly).

Very cool! I'll have to give this a shot on my 4,1. Hacked El Cap runs pretty good with an SSD and 6gb of RAM, considering no video acceleration. I wonder how Mojave would compare.

 

[Sveto]

Back in late 2018 I tried to upgrade my 2011 iMac 27" i7 to Mojave and it was virtually unusable graphics wise. I knew the 5xxx and 6xxx graphic cards would be no good but had a go anyway. Since reverted to High Sierra. However, my wife's 2011 MacBook Pro developed the GPU failure so I thought I might as well give it a shot. On first attempt it would only boot in Safe Mode. I re-installed Mojave but unchecked Legacy Video Drivers, booted into Safe Mode and ran dGPU disabler by dosdude1. Rebooted normally and voila!!! Works perfectly except for brightness and Sleep not working at all.Enabled Night Shift from the Patcher and makes the MacBook very usable. Thanks to all for the great work!! If the sleep and brightness worked it would be perfect....
I've since tried all the kext removal techniques seen in this forum to resolve these issues - to no avail. Maybe one day a fix will come along but it's been beyond my skills to try and sort it so far.

Why don't you repair your failed Nvidia GPU? There is a magnificent video by @dosdude1, but for your model you have to check out the other video as well (by that swearing tech guy) in order to see where the same cap is located (I think on the opposite side of the board). The correct cap part you can purchase in amazon on the following address:
https://www.amazon.com/gp/product/B00MMYOXN2/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

 

[dosdude1]

Why don't you repair your failed Nvidia GPU? There is a magnificent video by @dosdude1, but for your model you have to check out the other video as well (by that swearing tech guy) in order to see where the same cap is located (I think on the opposite side of the board). The correct cap part you can purchase in amazon on the following address:
https://www.amazon.com/gp/product/B00MMYOXN2/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

On the 2011 models, unfortunately, the GPU itself is actually the issue. And, to add insult to injury, AMD never actually made a revised version of the chipset those 2011 machines use, meaning that EVEN IF the GPU chipset were replaced, it would still fail again and have the same problems. I've tried it myself. The only thing you can do to permanently repair these is to bypass the gMux (graphics switching) IC, permanently bypassing the dedicated GPU, and running off Intel HD Graphics only.

 

[rayd8or]

Why don't you repair your failed Nvidia GPU? There is a magnificent video by @dosdude1, but for your model you have to check out the other video as well (by that swearing tech guy) in order to see where the same cap is located (I think on the opposite side of the board). The correct cap part you can purchase in amazon on the following address:
https://www.amazon.com/gp/product/B00MMYOXN2/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

No Nvidia cards in either my iMac or MacBook Pro - all AMD.

 

[Larsvonhier]

Very cool! I'll have to give this a shot on my 4,1. Hacked El Cap runs pretty good with an SSD and 6gb of RAM, considering no video acceleration. I wonder how Mojave would compare.

It feels even a bit faster and snappier than on El Cap. Perhaps while transitioning out of OpenGL (to Metal) usage, Apple optimized things under the hood?

I can play 720p MP4 with Quicktime without frame drops.
VLC does not work (blank screen or hidden window, sound only).
IINA plays i.e. MKV files but with half frame rate or so.
What´s really great is HTML5 video (youtube i.e.) and even Amazon Prime (with Opera browser) works very well!
[doublepost=1552470099][/doublepost]mPCIe to USB connection cable came today. I’m glad that it did not arrive before I found the kext solution for USB... motivation would have been lower otherwise.

Will try this nonetheless, might come handy for future hacks in MB 4,1 and others...

Right now I‘m test-installing Mojave from a patched installer (Julian‘s script plus my prelinkedkernel) on to a spare drive in the MacBook 4,1.

Will report the outcome.
EDIT.

Installation went through fine, but upon booting first time, at 80% progress bar, system resets and
goes into boot-loop. Would have to see what's wrong and patch manually. I hoped that could be avoided. Perhaps @0403979 has more insight: Which kernel is used at install time and which modified kexts are applied? (I used option 3 - patched installer in your script).

 

[avz]

I find agree, sometimes even on a i5 dual core and accelerated graphics I get choppy 1080p videos, cloud hosting servers maybe do some kind of upscaling resolution or optimization, probably on most it's not a native 1080p when it flows smooth, the true test is when chosing 1080p videos at 60fps.

Just a random one for example:

Just wanted to share something random but interesting nevertheless. While waiting for the official 10.14.4 release I decided to put an original HDD with Snow Leopard in my MacBook5,1(as it is extremely easy to access the hard drive in this model).
I played this 1080p60fps video on youtube in ArcticFox browser and was surprised how smooth it was. All of a sudden 2.0Ghz C2D is not a bottleneck? I believe even my MBP9,2 struggles most of the time with these videos. Who would have thought that in our time and age you need a Snow Leopard for the enjoyable YouTube experience?
Maybe somebody more knowledgeable can shed some light on this: weak hardware is not a problem in itself, it is rather a hardware/software integration that makes all the difference in the world? Or am I missing something?

 

[jackluke]

Just wanted to share something random but interesting nevertheless. While waiting for the official 10.14.4 release I decided to put an original HDD with Snow Leopard in my MacBook5,1(as it is extremely easy to access the hard drive in this model).
I played this 1080p60fps video on youtube in ArcticFox browser and was surprised how smooth it was. All of a sudden 2.0Ghz C2D is not a bottleneck? I believe even my MBP9,2 struggles most of the time with these videos. Who would have thought that in our time and age you need a Snow Leopard for the enjoyable YouTube experience?
Maybe somebody more knowledgeable can shed some light on this: weak hardware is not a problem in itself, it is rather a hardware/software integration that makes all the difference in the world? Or am I missing something?

Snow Leopard was a great OSX, capable to run all the core processes and frameworks with less than half 1 Gb Ram, last "PowerPC apps" capable with Rosetta, had a media center FrontRow playable totally with apple IR remote, supporting kernel on both i386 and x64 architectures, a very agile OSX, I still keep a copy where I can on a very small partition (it fits even on 5 GB disk space) on my macs.

edit:
About the hi-res videos, I guess that Mojave in its stock Quicktime libraries has something hybrid related to Metal and residual OpenGL acceleration, so that's why rendering playback results choppy.

 

[nandor690]

I just bought a 2009 Mac Pro, upgraded firmware to 5,1. Everything works great. Just one question tho right now.
Is anybody using a R7 370 graphics card? Does it work on Mojave out of the box?
Thanks for you help!

 

[hwojtek]

I just bought a 2009 Mac Pro, upgraded firmware to 5,1. Everything works great. Just one question tho right now.
Is anybody using a R7 370 graphics card? Does it work on Mojave out of the box?

You might find it easier to post the question in a relevant forum here.