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.
Ha, I didn't even realize there was a patch installed for audio on these things. I feel dumb now.
Carry on
Yeah, it happens... I'm actually planning on releasing a new "patch integrity check" feature in Patch Updater, which will alert you if it detects a patched file has been overwritten, and that a particular set of patches need to be re-installed. That way, you won't have to worry about things like this happening after updates.
 
Same experience for me on an MBP5,3 ... OTA, reboot, re-patched with 1.2.3 (including force rebuild cache) and got the same error message: "non supported machine".

Will try later on a supported MacMini Late 2012.

@Larsvonhier, saw on the OP (which I assumed you noted) to not install or upgrade due to existing problems. What exactly are the issues? Thanks.

"
Well, as you are here in the _unsupported_ region of all things Mojave, the warning on #1 is exactly meant for those types of machines, not about a general problem with 10.14.4 on supported ones.
We seem to have run into exactly what the warning was about. Let´s see what can be done when more reports come in...
 
Well, as you are here in the _unsupported_ region of all things Mojave, the warning on #1 is exactly meant for those types of machines, not about a general problem with 10.14.4 on supported ones.
We seem to have run into exactly what the warning was about. Let´s see what can be done when more reports come in...

Thanks for the reply. I tried to update on my "mojave supported" MacMini Late 2012. Indeed it worked.

I will try again later on an "unsupported" MBAir 2011. Now to get some sleep. Good Night or perhaps Good Morning in Germany.
 
So I tried nearly everything on my MBP mid 2009, 5.3, (extended journaled).

1.Software update saying:
"Your Mac is up to date: macOS Mojave 14.2.
2.Downloaded from the regular update (delta):
"This software is not supported by your system."
3.Downloaded from Combo Update:
"This software is not supported by your system."
4.Downloaded 14.3 install.dmg over the dosdude tool and created a new USB install stick with Mojave Patcher tool 1.2.3 and trying various postinstall options:
Kernel panic.
Now I give a last try:
5.Downloading the 14.3. installer over the dosdude tool and try to install it directly, without the patched install stick.
 
Last edited:
  • Like
Reactions: TimothyR734
Thank you!

@Larsvonhier Can I convert my SSD to APFS without reinstalling the OS? I have a Windows partition! I also applied the APFS Rom Patcher. MacBook 5,1
Yes, You can. It converts only the HFS partition, not the entire disk.
[doublepost=1548421459][/doublepost]Updated here, raid0 (2 SSDs) working perfectly, updated through OTA and then applied the dosdude1 patches

Captura de Tela 2019-01-25 às 11.03.41.png
 
  • Like
Reactions: TimothyR734
Yes, You can. It converts only the HFS partition, not the entire disk.
[doublepost=1548421459][/doublepost]Updated here, raid0 (2 SSDs) working perfectly, updated through OTA and then applied the dosdude1 patches

View attachment 817999

I tried converting the disk to APFS using Disk Utility in the Recovery Partition but Edit/Convert to APFS grayed out. I am finding the other methods. I think the Windows Partition is the reason why the "Convert to APFS" grayed out.
 
  • Like
Reactions: TimothyR734
Yeah, it happens... I'm actually planning on releasing a new "patch integrity check" feature in Patch Updater, which will alert you if it detects a patched file has been overwritten, and that a particular set of patches need to be re-installed. That way, you won't have to worry about things like this happening after updates.
That is amazing!! Your ability to turn a collection of patches into a user-friendly tool never fails to impress me. Everyone knows that figuring out the hacks is tricky, but I think a lot of us underestimate the time and effort that goes into maintaining such a polished and reliable automated patcher.

Can't wait to see this feature.
 
I tried converting the disk to APFS using Disk Utility in the Recovery Partition but Edit/Convert to APFS grayed out. I am finding the other methods. I think the Windows Partition is the reason why the "Convert to APFS" grayed out.

If you have a spare external drive, the cleanest way is to clone to it, re-partition your internal as a single AFPS and then reinstall with migration from the external. This will make sure you get the same container configuration as an install on a supported machine.
 
Downloading the 14.3. installer over the dosdude tool and try to install it directly, without the patched install stick.

No way! Couldn't install 14.3
Version 14.0.18 (14018) was downloaded!
Where this dosdude link leads to?

...some hours later...

PROBLEM SOLVED:

FORCE CACHE REBUILD was what the machine needed!
 
Last edited:
  • Like
Reactions: TimothyR734
If you have a spare external drive, the cleanest way is to clone to it, re-partition your internal as a single AFPS and then reinstall with migration from the external. This will make sure you get the same container configuration as an install on a supported machine.

Do I need to remove the Windows partition in order to convert to Apfs?
 
  • Like
Reactions: TimothyR734
does the delta update work? (the combo apparenly doesnt work at all for everyone) Or is everyone re-creating the USB

EDIT: the combo works fine. I had to unpackage the combo. Added in the 10.14.2 build number into the distribution file and patched it further by removing the macbook pro 6,2 from the unsupported list. Voila everything worked.
 
Last edited:
Thank you!

@Larsvonhier Can I convert my SSD to APFS without reinstalling the OS? I have a Windows partition! I also applied the APFS Rom Patcher. MacBook 5,1

Would you be able to share your experience in applying APFS ROM Patcher on MacBook5,1 in more detail? I am assuming you used dosdude1's APFS ROM Patcher? How easy it was? In step by step if you can.
 
Last edited:
  • Like
Reactions: TimothyR734
Had to reformat the 840 EVO SSD with 1.2.3 USB patcher to get APFS. All backups with Carbon Copy Cloner. Macbook 5,1 runs on 10.14.3.2 like new. ALL functions work w/o exception. TRIM enabled via terminal < sudo trimforce enable >.
 

Attachments

  • Screen Shot 2019-01-25 at 12.08.47 PM.png
    Screen Shot 2019-01-25 at 12.08.47 PM.png
    135.4 KB · Views: 166
So, I've been working on a backlight control patch for the CCFL-based display systems, and I think I've found a working solution... Can I get some testers before I release this via Patch Updater? Need to make sure this is 100% stable.

This is for any machines that have a display that uses a CCFL backlight, which includes:
  • MacBook5,2
  • iMac7,1
  • iMac8,1
  • iMac9,1
  • MacBookPro4,1 (17" model only)
To install, just download and extract the attached ZIP, then run the following in Terminal:

Code:
cd /path/to/bkltpatch10.14.2
./install.sh

Once complete, reboot the system. If it works, you should now have backlight brightness control!

WARNING: There is a chance this may cause a kernel panic. If so, all files removed/edited/replaced are backed up to ~/Bklt_Backup, and can be restored in singleuser mode.

ANOTHER GREAT RESULT !!! Mojave updated from Mojave 10.14.2 to 10.14.3 using macOS's Software Update

Updated my 17 Early 2008 MacBook Pro model A1261 MacBookPro4,1 from Mojave 10.14.2 to 10.14.3 using macOS's Software Update (my Mojave container had already been converted from HFS to APFS). REBOOTED from macOS Mojave Patcher on USB

Ran DosDude1's AMAZING macOS Mojave Patcher 1.2.3 to reapply patches. REBOOTED from MacBook Pro SSD

Ran DosDude1's AWESOME "backlight control patch for the CCFL-based display systems" in Terminal to re-enable my MBP's CCFL-based backlight brightness and F1 & F2 controls. REBOOTED from MacBook Pro SSD

Mojave 10.14.3 running PERFECTLY !!!

Only wish is the "backlight control patch for the CCFL-based display systems" could run as part of your next macOS Mojave Patcher version instead of having to be run separately... Especially for non-Terminal users like me.

AGAIN THANKS SO MUCH FOR ALL YOUR HARD WORK !!!

 

Attachments

  • macOS 10.14.3 on 17" MBP4,1.png
    macOS 10.14.3 on 17" MBP4,1.png
    104.8 KB · Views: 151
Last edited:
Managed to get my MacBook 4,1 (white early 2008) controlled by remote keyboard and mouse running on 10.14.3 beta.
Recap: Have not yet made progress with the broken USB (internal/external) functionality, still fumbling around with the 10.10.5 kexts to no avail.
As I´ve been very curious about finally seeing performance on such an un-accelerated machine (GPU), I tried some different approach:
- booted the 4,1s internal drive on a machine that Mojave works on
- installed Teleport 1.2.2 (special Mojave build)
- set Auto-Login to prevent password entry
- added Teleport to user login startup items and set Teleport to auto-accept incoming remote requests
then
rebooted the MB 4,1 with this setup, connected my 17" MB Pro, started Teleport there also and hooked up both machines per ethernet cable.

The result is astonishing. The x3100 intel GPU is fully recognized, full frame buffer (144MB) is used and at least the normal GUI/window/dock/side panel stuff is absolutely fluid. Lauchpad is much slower as it heavily relies on accelerated GPU usage, but once onscreen it is still usable.

See screenshot as a proof of concept - I hope that it triggers some more enthusiasm in the patcher community now (help greatly appreciated for more ideas what could be done to get onboard USB controller working...)

View attachment 816204

Edit: Anyone interested in the Mojave build of Teleport: Link here https://github.com/abyssoft/teleport/files/2414046/teleport_1.2.2.zip

Pretty nice ! I have bought a beautifull black Macbook4,1 to do the test. I am trying to boot on the mojave (patched) setup disk but i alzays ends up with a forbiden sign. I have added my boardid and model in the platformsupport.plist of the key but it still doesn't boot. Did someone know why ? Thanks ;)
 
  • Like
Reactions: TimothyR734
Would you be able to share your experience in applying APFS ROM Patcher on MacBook5,1 in more detail? I am assuming you used dosdude1's APFS ROM Patcher? How easy it was? In step by step if you can.

1, turn off the machine and wait for 15 seconds
2, press and hold the power button until the sleep indicator flash 3 times fast, 3 times slow, 3 times fast.
3, After booting into the OS, run the APFS ROM PATCHER app.
[doublepost=1548458788][/doublepost]
Are you using the Mojave Disk Utility while booted under the patched Mojave installer from a usb key?

Yes, of course. I tried using the Disk Utility in the Recovery Partition and the boot usb but both grayed out. I think I have to remove the Windows Partition.
 
  • Like
Reactions: TimothyR734 and avz
1, turn off the machine and wait for 15 seconds
2, press and hold the power button until the sleep indicator flash 3 times fast, 3 times slow, 3 times fast.
3, After booting into the OS, run the APFS ROM PATCHER app.
[doublepost=1548458788][/doublepost]

Yes, of course. I tried using the Disk Utility in the Recovery Partition and the boot usb but both grayed out. I think I have to remove the Windows Partition.

Considering that they still haven't updated the Bootcamp utility under Windows to recognize APFS partitions as a valid startup device, it isn't surprising.
 
  • Like
Reactions: TimothyR734
Pretty nice ! I have bought a beautifull black Macbook4,1 to do the test. I am trying to boot on the mojave (patched) setup disk but i alzays ends up with a forbiden sign. I have added my boardid and model in the platformsupport.plist of the key but it still doesn't boot. Did someone know why ? Thanks ;)
Don't mess with PlatformSupport.plist files. Just add -no_compat_check to boot flags in /L*/Preferences/SystemConfiguration/com.apple.Boot.plist
 
1, turn off the machine and wait for 15 seconds
2, press and hold the power button until the sleep indicator flash 3 times fast, 3 times slow, 3 times fast.
3, After booting into the OS, run the APFS ROM PATCHER app.

Thanks for this info!
After the step 3 when you run the APFS ROM PATCHER did you have to select a particular version from the drop down menu or the patcher does this selection automatically for your particular Mac model? If you had to select, what did you select? Cheers!
 
  • Like
Reactions: TimothyR734
Just a question regarding what is actually patched by the @dosdude1 tool - I have used it three times:
1: 10.14.0 install - obviously it went without a hitch. I set up a virtual Ethernet interface (I use it for VPN separation) and it all worked correctly.
2: 10.14.0 -> 10.14.2 - I upgraded the OS in full using a patched 10.14.2 USB, applied the post-install patches. I had to manually re-add my virtual Ethernet interface, as it was gone from the Network Preferences. Also, the physical Ethernet interface was reset to DHCP instead of the previously selected manual configuration.
3: 10.14.2 -> 10.14.3 - I applied the OTA upgrade, rebooted from a patched 10.14.3 USB and applied the post-install patches. Again, my virtual Ethernet interface was gone and I had to re-add it, however, the physical interface kept the manual IP configuration.

I am not sure if it is the Mac OS installer that resets the interfaces or is it what the patches do?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.