Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.14 Mojave on Unsupported Macs Thread

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.
TimothyR734 said:
yes it did download the full installer using the macOS Public beta access utility when you click the install says this update can't be installed on this machine :(
Click to expand...
Thanks for testing. Unfortunately, I think system update is behaving the same way on many machines. The beta utility's primary function is to enroll in the proper seed stream. Just like SWU utility or the command line does. Nothing fancier than that (you can inspect the beta utility's code to see that)

@dosdude1 - any thoughts on why the seed system updates aren't working anymore. They did for me from b3 to b4? Is it possible softwareupdated changed? I checked on all of my systems and Faker is both installed and active in the plist.
 
  • Like
Reactions: TimothyR734
pkouame said:
Thanks for testing. Unfortunately, I think system update is behaving the same way on many machines. The beta utility's primary function is to enroll in the proper seed stream. Just like SWU utility or the command line does. Nothing fancier than that (you can inspect the beta utility's code to see that)

@dosdude1 - any thoughts on why the seed system updates aren't working anymore. They did for me from b3 to b4? Is it possible softwareupdated changed? I checked on all of my systems and Faker is both installed and active in the plist.
Click to expand...
and you know Apple likes to switch up the catalogs to :(
 
  • Like
Reactions: visberry, jackluke and pkouame
pkouame said:
Thanks for testing. Unfortunately, I think system update is behaving the same way on many machines. The beta utility's primary function is to enroll in the proper seed stream. Just like SWU utility or the command line does. Nothing fancier than that (you can inspect the beta utility's code to see that)

@dosdude1 - any thoughts on why the seed system updates aren't working anymore. They did for me from b3 to b4? Is it possible softwareupdated changed? I checked on all of my systems and Faker is both installed and active in the plist.
Click to expand...
I tried checking for updates using the terminal on both developer and beta seeds and both said no updates are available
[doublepost=1533072103][/doublepost]
0403979 said:
@dosdude1 Do newer patchers work with older Mojave versions?
Click to expand...
I think the b12 version works as when I did my db5 update and got stuck with 2 mins left to install I used the b12 to do the post install patches I made a few new Mojave usb patchers with version 1.01 and they both get stuck on the 1st phase of the boot up
 
[QUOTE = "pkouame, Beitrag: 26305973, Mitglied: 1036080"] Danke fürs Testen. Leider denke ich, dass sich das Systemupdate auf vielen Computern genauso verhält. Die Hauptfunktion des Beta-Dienstprogramms besteht darin, den richtigen Seed-Stream zu registrieren. Genauso wie das SWU-Dienstprogramm oder die Befehlszeile. Nichts schicker als das (Sie können den Code des Beta-Dienstprogramms überprüfen, um das zu sehen)

[USER = 669685] @ dosdude1 [/ USER] - alle Gedanken darüber, warum die Aktualisierung des Seed-Systems nicht mehr funktioniert. Sie haben für mich von b3 nach b4 getan? Ist es möglich, Softwareaktualisierungen zu ändern? Ich habe alle meine Systeme überprüft und Faker ist sowohl installiert als auch aktiv im plist. [/ QUOTE]

I fully agree with the Friend @pkouame. I have exactly the same probem with my Hackintosh MSI Z97-G43 motherboard and Intel processor i5-4570 with Intel HD4600 graphics. Update from beta3 to beta4 (i have the beta2 installed with the MBR patch for MBR and GPT patitions as hfs +) dakam the update from beta3 to beta4 without problem. Now the update to beta5 is no longer completing, my system will always be up to date. I have also tried SWupdater (version 1.0.4, etc., and everything else @pkouame has already done, it just does not show the beta5 update What has Apple changed?
I'll do one, I'll re-install the beta5 (yesterday I downloaded the full 5.86 GB version) with the OSInstaller.MBR.10.14.db5.18A347e. Solte then with beta5 to beta6 again the update does not appear, then I wait until the final and then install as hfs + again very clean. It's very bad that the updates do not work and I do not feel like reinstalling them clean.
Is there a hint yet to update the beta5 from the installed beta4?
 
  • Like
Reactions: TimothyR734
tn-xyz said:
do you mind to elaborate? do you know the specific issue that's causing incorrect transparency display?
Click to expand...
It's due to the 10.13 GPU drivers. Since those are the most modern GPU drivers for these legacy cards, it's unlikely there will be any changes with those transparency issues. Unless, of course, Apple changes something in a later release.
[doublepost=1533073402][/doublepost]
0403979 said:
@dosdude1 Do newer patchers work with older Mojave versions?
Click to expand...
No, if you want to use an older copy of the Mojave installer, you'll need to use an older version of the patcher.
 
  • Like
Reactions: TimothyR734
jackluke said:
In that specific case I was referring ONLY at the POST Night-Shift-patch, the general causes of stuck on Apple Logo progress bar could be many: SIGABRT, Invalid GPU Kext, Invalid/missing Framework/Extensions signatures, invalid prelinkedkernel, corrupted disk permissions and so on.

edit:

If you are referring after upgrading the main system, then booting from the USB Mojave Patcher, avoiding reinstalling use the "Post Install" select your machine model, then select "Force cache rebuild".
This should fix stucking on Apple logo progress bar too.

If you are referring to Night Shift, yes you can revert since the dosdude1 cbpatcher makes a backup of your current CoreBrightness.framework into /Users/YourUsername/CoreBrightness-backup/
if you read earlier posts you could revert through single user mode Terminal commands.
Click to expand...

Found the post and worked! Thanks!
 
  • Like
Reactions: jackluke and TimothyR734
I think I might be on to something since I only had the b12 version of the Mojave patcher I downloaded the newest patcher 1.02 and downloaded MacOS Mojave on my High Sierra then created the new usb patcher and tried but got stuck so went in to macOS Mohave the one I successfully upgraded to dev beta 5 downloaded version 1.01 of the patcher and downloaded macOS Mojave and created another usb patcher still no luck booting I have a copy of macOS Mojave that I downloaded using b12 of the patcher so as a curiosity clicked on get info for each 3 I downloaded of the install macOS Mojave beta's each had the same date created and modified July 11th all three same size 5.75 gb correction all 3 install macOS Mojave beta version.plist says 14.0.14
 
Last edited:
  • Like
Reactions: visberry
I just did a clean install of Mojave Developer Preview 5 on my unsupported MBP5,5. Used @dosdude1's latest Mojave Beta Install App 1.1.0. Everything went well including post install, and patch updater updates.

Then I encountered this issue on my input devices (keyboard, mouse and trackpad). When selecting the "input device" on System Preferences to change some options, I get this universal error message:

"Preferences Error ~ You can't open "input device" (all 3 above) preferences pane because it doesn't work on Intel-based Mac"

Googled any possible solutions but have not found one that works. This is my first encounter with any macOS version.

Do you guys have any recommendations/solutions?

~Mahalo~ (Thank you)!
 
  • Like
Reactions: jackluke and TimothyR734
BookEmDanno said:
I just did a clean install of Mojave Developer Preview 5 on my unsupported MBP5,5. Used @dosdude1's latest Mojave Beta Install App 1.1.0. Everything went well including post install, and patch updater updates.

Then I encountered this issue on my input devices (keyboard, mouse and trackpad). When selecting the "input device" on System Preferences to change some options, I get this universal error message:

"Preferences Error ~ You can't open "input device" (all 3 above) preferences pane because it doesn't work on Intel-based Mac"

Googled any possible solutions but have not found one that works. This is my first encounter with any macOS version.

Do you guys have any recommendations/solutions?

~Mahalo~ (Thank you)!
Click to expand...
Did you apply any pre-existing Night Shift patches NOT from Patch Updater?
 
  • Like
Reactions: TimothyR734
dosdude1 said:
Did you apply any pre-existing Night Shift patches NOT from Patch Updater?
Click to expand...

Sorry, I'm not sure "where" you mean. You mean from the Post Install on the USB drive? I did re-ran Patch Update and noticed that the version of "Night Shift Patch" is 3.

Thanks @dosdude1!

EDIT: My bad on the patcher update / night shift patch version. It's actually version 4. I have 2 partitions on this MBP5,5. (1) contains High Sierra GM (2) Mojave DP5. So when I did a spotlight search on "Patch Updater", it ran the one from High Sierra. So I re-ran the correct one (from Mojave) and noticed that Night Shift is version 4 along some others. BTW, my night patch is working.
I attempted to re-ran the macOS Post Install from my USB and did a "Force Rebuild Caches" and rebooted. Still got the same Preferences Panes errors. But, I'm not sure if this was what you asked me regarding "pre-existing Night Shift patch".

Sorry for the lengthy post.
 
Last edited:
  • Like
Reactions: jackluke
dosdude1 I tried downloading macOS Mojave beta with version 1.01 of the patcher is this correct
 

Attachments

  • IMG_0171.jpg
    IMG_0171.jpg
    316.1 KB · Views: 155
dosdude1 said:
It's due to the 10.13 GPU drivers. Since those are the most modern GPU drivers for these legacy cards, it's unlikely there will be any changes with those transparency issues. Unless, of course, Apple changes something in a later release. [/QUOTE

But what if we replace those drivers by the high Sierra? Probably it will mess with dark mode or it is possible to do so?
Click to expand...
 
Last edited:
  • Like
Reactions: TimothyR734
dosdude1 said:
It's due to the 10.13 GPU drivers. Since those are the most modern GPU drivers for these legacy cards, it's unlikely there will be any changes with those transparency issues. Unless, of course, Apple changes something in a later release.
[doublepost=1533073402][/doublepost]
No, if you want to use an older copy of the Mojave installer, you'll need to use an older version of the patcher.
Click to expand...

Are the graphics patches required to boot?
 
  • Like
Reactions: visberry and TimothyR734
when the download finished I created a usb patcher installed macOS Mojave clean install with version 1.02 and it installed 18a336e
[doublepost=1533105724][/doublepost]
0403979 said:
Are the graphics patches required to boot?
Click to expand...
if you install without the legacy video patch you might get a very dim screen no CoreBrightness
 
  • Like
Reactions: visberry
TimothyR734 said:
when the download finished I created a usb patcher installed macOS Mojave clean install with version 1.02 and it installed 18a336e
[doublepost=1533105724][/doublepost]
if you install without the legacy video patch you might get a very dim screen no CoreBrightness
Click to expand...


Someone should try it, if the transparency works then that might help us,
 
  • Like
Reactions: visberry and TimothyR734
Now it got me...

Since the update yesterday to beta 4, MBP 5.4 is booting twice.
Means startup sound, the short blackscreen then blank white screen a minute and then it starts again. Startup sound, blackscreen, applelogo macos...
 
Sorry for interrupting you guys.. Im currently facing issues with battery, my MacBook 7,1 on Mojave beta 4 is draining battery so fast. (watching youtube, browsing web etc) on Mojave lasts 1:30h.. On High Sierra is about 5hours. In monitor activity is nothing hogging cpu. Does anybody know why?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back