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.
So is it “safe” to update MacBookPro5,2 to 10.14.5? I see some reports but they seem to suggest it works only with the dGPU.
Yes, should have no issues with 10.14.5 on that machine. I've just been thoroughly testing it on my MBP5,2 and haven't had any issues running with either GeForce 9400M or the dedicated 9600M GT.
 
  • Like
Reactions: ASentientBot
Yes, should have no issues with 10.14.5 on that machine. I've just been thoroughly testing it on my MBP5,2 and haven't had any issues running with either GeForce 9400M or the dedicated 9600M GT.
Awesome. Simply awesome.
 
There was an issue with the initial version that I didn't catch initially. Re-installing it via Patch Updater should get it working normally.

Re-installed as suggested looks good but a tad more processor intensive. Very useable, tho.

Nice work, as always.
 
Ahoy - New Legacy Video Patch v6 makes video choppy and fan ramp-up on perfect 14.3 install on Mini 3,1 had to restore orig. installation from back-up to correct.

Maybe I have different machine from yours, but if the new Video Patch includes the AppleGraphicsControl.kext then I guess the downgrade of GPUWrangler.framework is required in addition also to settle down the intensive cpu/gpu tasks.

Yes, should have no issues with 10.14.5 on that machine. I've just been thoroughly testing it on my MBP5,2 and haven't had any issues running with either GeForce 9400M or the dedicated 9600M GT.

I noticed in your last Mojave Patcher 1.3.2 you added the AppleGraphics*.kext and MCCSControl but not the GPUWrangler.framework , from my previous test downgrading to HS GPUWrangler was mandatory to support the entire AGC plugins and gmux switching.
[doublepost=1557825030][/doublepost]
From my shallow analysis seems yours added gfxshared AppleGraphicsControl.kext is taken from HighSierra because AGDCDiagnose binary is 103 kb while the Mojave one is higher in byte size and so all the others plugins core binaries, then I guess you should include also an HS GPUWrangler.framework to this for overall stability and for a proper dynamic GPU switching.
 
Last edited:
I created the Mojave Patcher on my 2012 iMac ....which then began showing the multicolored text during startup.
How does me creating a Mojave Patch on my 2012 iMac, tamper with the 2012 macOS system???? I had to CMD R and reinstall macOS on my 2012 iMac and now the booting process looks normal again. This is a little concerning to me. Has anyone else seen this?

From this new Mojave Patcher (which showed up just fine in System Preferences start disk on my 2012 iMac) I tried to boot my 2009 iMac but it still shows the folder-question.
 
I created the Mojave Patcher on my 2012 iMac ....which then began showing the multicolored text during startup.
How does me creating a Mojave Patch on my 2012 iMac, tamper with the 2012 macOS system???? I had to CMD R and reinstall macOS on my 2012 iMac and now the booting process looks normal again. This is a little concerning to me. Has anyone else seen this?

From this new Mojave Patcher (which showed up just fine in System Preferences start disk on my 2012 iMac) I tried to boot my 2009 iMac but it still shows the folder-question.

The multi-color text during startup probably was the "apfs efi boot software patch" and you should have to type "exit" to continue normal boot, but yes that's not required on a 2012 Mac, probably only on 2009 iMac.

Anyway is still a mystery why you can't type any key-commands from your iMac 2009.

I read somewhere that if the question mark folder persists, then probably is damaged the internal iMac sata ribbon cable and should be changed, but even in this case at least usb external drive should have been detected from alt-option key, that's weird.
 
Last edited:
  • Like
Reactions: avz
I would like to know, please, if the released 14.4.5 is now considered "safe and stable" on:

1. MacBook Air 3,2 (13-inch, Late 2010) with 4GB RAM, NVIDIA GeForce 320M 256 MB, Apple 128 GB SSD and APFS?

2. iMac 11,1 (27-inch, Late 2009) with 12GB RAM, ATI Radeon HD 4850 512 MB, Samsung EVO 850 1 TB SSD and APFS?

Both of these are running High Sierra.

Would there be any significant performance decrease or increase running Mojave 14.4.5 as compared to High Sierra 14.3.6 on these machines?
 
Last edited:
I created the Mojave Patcher on my 2012 iMac ....which then began showing the multicolored text during startup.
How does me creating a Mojave Patch on my 2012 iMac, tamper with the 2012 macOS system???? I had to CMD R and reinstall macOS on my 2012 iMac and now the booting process looks normal again. This is a little concerning to me. Has anyone else seen this?

From this new Mojave Patcher (which showed up just fine in System Preferences start disk on my 2012 iMac) I tried to boot my 2009 iMac but it still shows the folder-question.

Judging by what you write you are obviously an absolute beginner(I am too by the way despite owning a Mac for 10+ years). It sounds like you don't quite understand what the patcher does and how it's created. I, myself watched the video on how to do it 20 times and read the instructions 30 times. Mojave patcher is the safest thing ever for your Mac, when you know what you are doing.
 
  • Like
Reactions: K two and bbfc
The multi-color text during startup probably was the "apfs efi boot software patch" and you should have to type "exit" to continue normal boot, but yes that's not required on a 2012 Mac, probably only on 2009 iMac.

Anyway is still a mystery why you can't type any key-commands from your iMac 2009.

I read somewhere that if the question mark folder persists, then probably is damaged the internal iMac sata ribbon cable and should be changed, but even in this case at least usb external drive should have been detected from alt-option key, that's weird.

From my limited experience I noticed that the Macs that don't support APFS natively fail to boot to anything after you format an entire HDD(SSD) as APFS. Most people never experience this issue as they almost always have a bootable HFS+ partition that they keep, so they never format an entire drive as APFS. This is the main reason why I took a risk of applying APFS ROM patch on my machine. Take it with a grain of salt though as it might be only my experience with the MacBook5,1.

I agree that it is a dead certainty that he has to replace the sata ribbon cable and maybe even SSD(as the controller might be questinable). Flashing folder with a question mark is considered to be one of the easiest faults by the buyers of the used Macs.
 
Last edited:
  • Like
Reactions: K two
I created the Mojave Patcher on my 2012 iMac ....which then began showing the multicolored text during startup.
How does me creating a Mojave Patch on my 2012 iMac, tamper with the 2012 macOS system???? I had to CMD R and reinstall macOS on my 2012 iMac and now the booting process looks normal again. This is a little concerning to me. Has anyone else seen this?

From this new Mojave Patcher (which showed up just fine in System Preferences start disk on my 2012 iMac) I tried to boot my 2009 iMac but it still shows the folder-question.

Zab - Has the '09 iMac ever been apart, the LCD removed for an HDD upgrade or replace??
 
Zab have you tried disconnecting power overnight from the iMac you are having trouble with? This has worked more than once for me with weird issues, just disconnect every cable from the back of the unit, any keyboards/mice/usb drives etc. as well as the power cord. Leave everything unplugged at least overnight. The plug up ONLY the power cord and keyboard and on the first boot make sure you hold down the ALT key and see if that doesn’t work to get you back in.
 
  • Like
Reactions: K two
Hi everybody
updated 20" iMac 8,1 Early 2008 to 10.14.5 (18F132) from .4, I re-applied the patches with "macOS Post Install.app" 1.3.1 and force rebuild cache.
iSight (with FaceTime), Siri, Chess, Flurry and News work well (still no News+)
Only F1 and F2 for backlight control do not work

Capture d’écran 2019-05-14 à 15.48.15 1.png
 
Last edited:
  • Like
Reactions: K two
I created the Mojave Patcher on my 2012 iMac ....which then began showing the multicolored text during startup.
How does me creating a Mojave Patch on my 2012 iMac, tamper with the 2012 macOS system???? I had to CMD R and reinstall macOS on my 2012 iMac and now the booting process looks normal again. This is a little concerning to me. Has anyone else seen this?

From this new Mojave Patcher (which showed up just fine in System Preferences start disk on my 2012 iMac) I tried to boot my 2009 iMac but it still shows the folder-question.
Maybe it has already been asked but can you boot the iMac in target disk mode? Just press ‘t’ and hold it down during boot. A FireWire symbol should be shown on your screen if you succeed.
 
  • Like
Reactions: K two and jackluke
I ended up doing a clean reinstall after screwing up the initial upgrade. Wonder if the script that re-enabled recovery mode will work or if a new one will be needed for 10.14.5
 
I ended up doing a clean reinstall after screwing up the initial upgrade. Wonder if the script that re-enabled recovery mode will work or if a new one will be needed for 10.14.5

It should work and it doesn't break nothing in the case doesn't wake the APFS Recovery, it's totally safe.
 
The multi-color text during startup probably was the "apfs efi boot software patch" and you should have to type "exit" to continue normal boot, but yes that's not required on a 2012 Mac, probably only on 2009 iMac.

Anyway is still a mystery why you can't type any key-commands from your iMac 2009.

I read somewhere that if the question mark folder persists, then probably is damaged the internal iMac sata ribbon cable and should be changed, but even in this case at least usb external drive should have been detected from alt-option key, that's weird.
The point about the scrolling text during startup is that I was not installing the patch on the 2012 iMac. I was using the 2012 iMac only to create the Mojave Patcher for the 2009 iMac ...so how in the .... did my iMac 2012 get affected??? I was not installing anything on it. Just downloaded the patch and went through the motions of creating the USB patch installer. There should not be ANY modifications done on the host machine. That's the concerning part.

Yeah I really don't know how to get past the folder-question. I keep hoping for the miracle.
[doublepost=1557847806][/doublepost]
Judging by what you write you are obviously an absolute beginner(I am too by the way despite owning a Mac for 10+ years). It sounds like you don't quite understand what the patcher does and how it's created. I, myself watched the video on how to do it 20 times and read the instructions 30 times. Mojave patcher is the safest thing ever for your Mac, when you know what you are doing.
Then perhaps you can share how the 2012 iMac I was only using to create the Mojave Patch USB for the 2009 iMac, began showing the scrolling text during startup? Nothing was installed on the 2012 iMac, it was just the vehicle I used to create the USB Mojave Patcher. How did that get affected? I had to CMD R and reinstall the system before it went away.

The Mojave Patcher is not supposed to tamper with the machine you are using to create the installer USB.
 
The point about the scrolling text during startup is that I was not installing the patch on the 2012 iMac. I was using the 2012 iMac only to createinstallmedia for the 2009 iMac ...so how in the .... did my iMac 2012 get affected??? I was not installing anything on it. Just downloaded the patch and went through the motions of creating the USB patch installer. There should not be ANY modifications done on the host machine. That's the concerning part.

Yeah I really don't know how to get past the folder-question. I keep hoping for the miracle.

Probably when you installed the patched Mojave on your external SATA SSD, you targeted the wrong drive to where apply the Post-Install patches.

Have you tried all the USB ports available? Maybe one of them broken?

As @flygbuss suggested the only chance is to target the disk of another Mac from your iMac through a Firewire 800 cable.

But also using a firewire cable it's almost a bootloop because the 2012 Mac can boot recent osx that 2009 Mac can't.
 
Last edited:
Probably when you installed the patched Mojave on your external SATA SSD, you targeted the wrong drive to where apply the Post-Install patches.

Have you tried all the USB ports available? Maybe one of them broken?

As @flygbuss suggested the only chance is to target the disk of another Mac from your iMac through a Firewire 800 cable.
On my 2012 iMac I created the Mojave Patcher on a USB stick, hoping it would boot my 2009 iMac. So nothing was "installed" on my 2012 iMac, and I was not "installing" anything on an external drive either. I was simply creating the USB Mojave Patcher USB installer so it was ready for my 2009 iMac. This is extremely weird. The same thing happened once before when I got the 2012 iMac (because the 2009 iMac is rendered un-bootable) but at the time I was just confused about it and just did a reinstall.

How can the Mojave Patcher affect the "host machine" you are using to create the Mojave Patcher USB installer for another machine?
 
Anyone else looking at one of these?

My completely stock non-DosDude1 patched MacBook Pro (15-inch, 2017, MacBookPro14,3 Intel Core i7 3.1 GHz) restarted FIVE TIMES upgrading from 10.14.4 to 10.14.5 over the 50 minute install process. I thought it had hung up a couple of times but it eventually did a final restart and resumed working fine.

VERY surprised this still like new MacBook Pro struggled during this normal incremental update. Worried about upgrading my Early 2008 MacBookPro4,1 from 10.14.3 to 10.14.5 (I skipped 10.14.4 since almost everybody here reported it as problematic).
 
Then perhaps you can share how the 2012 iMac I was only using to create the Mojave Patch USB for the 2009 iMac, began showing the scrolling text during startup? Nothing was installed on the 2012 iMac, it was just the vehicle I used to create the USB Mojave Patcher. How did that get affected? I had to CMD R and reinstall the system before it went away.

The Mojave Patcher is not supposed to tamper with the machine you are using to create the installer USB.

Which Mojave patcher version are you using? If you are using the latest patcher and you are absolutely sure that you followed the instructions to the letter, then you should ask dosdude1 if something might have gone wrong with the latest patcher.

I am using Mojave patcher version 1.2.3 exclusively since 10.14.2 and have absolutely no issues with it whatsoever.
 
Yes, should have no issues with 10.14.5 on that machine. I've just been thoroughly testing it on my MBP5,2 and haven't had any issues running with either GeForce 9400M or the dedicated 9600M GT.

What about updating from 10.14.3 to 10.14.5 using Software Update on a 17" Early 2008 MacBook Pro (MacBookPro4,1) with NVIDIA GeForce 8600M GT 512 MB video card since it has the oddball CCFL backlight ???

Do I need to reapply your bkltpatch10.14.2 or is it now included in the macOS Mojave Patcher post install patches?

Backlight Patch 10.14.2 has been working flawlessly since I installed it. :cool:
 
Which Mojave patcher version are you using? If you are using the latest patcher and you are absolutely sure that you followed the instructions to the letter, then you should ask dosdude1 if something might have gone wrong with the latest patcher.

The latest version. Just did it today.

I am using Mojave patcher version 1.2.3 exclusively since 10.14.2 and have absolutely no issues with it whatsoever.
Yeah I'm a little baffled about this. How can this even happen? It's unreal. Maybe I have a virus somewhere in my system. There's also a weird problem that has persisted over several years and macOS versions and various iMacs where Finder will not show the correct total number of GB inside the user folder. The total number is way above the total sum of the content inside. I talked to Apple Support about it and they were mystified. But that is a whole other problem. But I'm beginning to feel the 'ghost in the machine' here.

The process is very simple. Download the Mojave Patcher app, go to the menu and download the Mojave Installer app, then start the process and pick the USB drive and you're done. Not too difficult. But it's so weird, this should not even be possible. I'm extremely confused about this. Just wanted to give dosdude1 a heads up.

Bigger problem though, I can't boot my 2009 iMac. NeXT step is making spiritual contact with Steve Jobs from beyond and take his advice.
 
  • Like
Reactions: olad
On my 6,2 MBP, I used system update to upgrade from 10.14.4 to 10.14.5. The installation went ahead and restarted automatically where it got stuck. I then used restarted to the startup disk created by Mojave Patcher 1.3.1 and applied patches, after restart this led to a dark screen with a small spinning gear which was also stuck in a loop.

I am now downloading the whole OS using Mojave Patcher 1.3.2, I assume it will download 10.14.5, it does not say which version it is downloading, it is over 6 GB.

It is a pain in in the neck to keep downloading the whole OS every time there is a new patcher update.

I do not know why my installation was stuck with a screen with spinning gear. The same happened when upgrading to 10.14.4, but I know that for that version a new startup disk was required. However, the docs say that for 10.14.5 that is not required... well that did not work for me.

Also, yesterday, patch updater asked to update the legacy video stuff, said it will fix random kernel panics. I updated that on 10.14.4, which broke my screen brightness. The brightness control is completely gone in system preferences and controlling brightness by keyboard does not work either. I am stuck with a dim screen. Does this get resolved after upgrading to 10.14.5?

Apple is doing a good job to make us on unsupported hardware more and more frustrated to give up and buy new hardware. Joke's on you Apple, I won't be buying another mac given the new bugs for (the completely unneeded) new keyboard and some screen nightmare. If it wasn't for security reasons, would never update from El Capitan.
 
Yeah I'm a little baffled about this. How can this even happen? It's unreal. Maybe I have a virus somewhere in my system. There's also a weird problem that has persisted over several years and macOS versions and various iMacs where Finder will not show the correct total number of GB inside the user folder. The total number is way above the total sum of the content inside. I talked to Apple Support about it and they were mystified. But that is a whole other problem. But I'm beginning to feel the 'ghost in the machine' here.

The process is very simple. Download the Mojave Patcher app, go to the menu and download the Mojave Installer app, then start the process and pick the USB drive and you're done. Not too difficult. But it's so weird, this should not even be possible. I'm extremely confused about this. Just wanted to give dosdude1 a heads up.

Bigger problem though, I can't boot my 2009 iMac. NeXT step is making spiritual contact with Steve Jobs from beyond and take his advice.

Well, looking at the results you got, the process does not seem to be simple at all. We are talking ghosts and spiritual contacts here. And yet the flashing folder with the question mark is still here.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.