macOS 10.14 Mojave on Unsupported Macs Thread

[fintematic]

Sometimes it's good without, I personally disable every time "Check spelling and grammar" they give me many unwanted auto-correction issues (also in this thread) in typing, when using Notes, but especially handling with apple scripts in TextEdit, a disaster.
[doublepost=1537996032][/doublepost]

faulty MagicMouse1 ? Water damage ?
[doublepost=1537996426][/doublepost]

You have to replace all the 5 IOUSB***.kext from HighSierra into Mojave /S/L/E/

If you don't have more HighSierra check here: 5 IOUSB kexts by @TimothyR734

right after you must fix permissions in /S/L/E/ and rebuild the kextcache from Mojave Terminal:

sudo -s
chown -r 0:0 /S*/L*/E*
chmod -r 755 /S*/L*/E*
kextcache -i /
reboot

I replaced all the IOUSB*.kext but the isight still have glitch and it's slowly

 

[yeiyei0891]

Thanks @dosdude1 for your Patcher tool!!!. Mojave is working perfect on my Macbook 7,1 (white unibody mid-2010) with 3GB ram and it's original hard drive. I made a fresh install on monday and i was testing and works faster than high sierra the only issues i got is with the app news that magically desappeared from aplications and with the LCD color profile, colors look weird and seen too warm for that reason i'm using the generic RGB color profile that looks nicer. What can i do to fix the LCD color issue. and another thing, How can i get night shift on my mac.View attachment 789357 View attachment 789358

I have a Macook 6,1 (identical to 7,1), did you do a clean installation? I did it and later restore all aplications with Time Machine but the fan is a full speed and nothing in Activity Monitor is using the CPU.

 

[Larsvonhier]

Nope but I did a disk check and got this. I wonder if Apple did a update for APFS with the 10.14.1 as what I find is weird I have 4 EFI partition where I normally only have 2

Tried the .1 beta also, and got a weird verbose output reading "cannot mount disk1s3", whereas disk tools does not have such a volume. I suspect that there is some change in the APFS thingy, just like TimothyR734 wrote.
Went back to 10.4.0 by re-installing from USB stick, kept all user profile/data/settings. Nothing lost but some time ;-)

 

[teobilly]

I guys I have a MID 2010 iMac 27" i7 16GB with ATI Radeon HD 5750.
What problems will I have by installing this Patch on my iMac model ? can they solve? I use the iMac for work, I would not have an iMac that works badly.
Thanks

 

[macamok]

Hello everyone owners of Macbook7,1 (and I guess of any C2D Penryn Mac) with Mojave beta 4, I do have a weird issue, everything is working, except into System Preferences when I try to open some elements I got this message:

Preferences Error
"You can’t open File.prefpane because it doesn’t work on an Intel-based Mac."

Where File.prefpane is any of: Keyboard/Mouse/Trackpad


I have tried replacing them from a previous HS version but it doesn't worked, I mean they have the same behavior.

edit:
Another weird thing is when using "dark mode", opening System Preferences, the "Users & groups" and "Accessibility" panes after opened (they only) turn back in a "light mode" window, while overall is still in dark mode.

edit2:
It occurs even on a supported Mac booting from the same Mojave beta 4 external SSD, while instead booting from internal SSD Mojave beta 2 it doesn't occur.

Maybe since those are all usb input devices it's something related to the manual IOUSB*** kext patching or to Mojave beta 4? Hoping is beta 4 general issue.

Hi I have se same issue (Macbook Pro 5.5 Final Mojave release, updated from High Sierra). Did you ever solve the problem?

 

[olad]

@dosdude1 it seems like other people are interested in adding more patches, but since your code is not open sourced, they cannot. For example see:

https://github.com/julian-poidevin/MBPMid2010_GPUFix/issues/90#issuecomment-424604068

Is it possible to create a github project for your code so that other open source developers can contribute? The way that people in this forum send google drive links for patches is scary when it comes to security. There is a a lot of patches with no security peer review.

While all of us on unsupported mac hardware are using these patches at our own risk, we still deserve to know about the security of these patches.

Would it be possible to create a github project for this great work? We can discuss the problems in a much more efficient way with github issues rather than a forum which is really hard to follow each separate problem.

I, for one, am quite satisfied with leaving things with @dosdude1. He's done an admirable job with the patcher, he's at college, he answers (almost all) questions, provides free advice to anyone who asks, and he tells you what he is going to add. He's human, not superman, and a little patience by some would be appreciated, I think, by him. I would NOT want his software open sourced. If he thinks an idea is worthy of inclusion WITHOUT adding bloat to the patcher, then he should be the one to decide to include it or not. Anyone who thinks his FREE patcher (or any of his other software) is not inclusive enough is free to write his/her patcher on Github, and those who want will go there.

 

[jhowarth]

Tried the .1 beta also, and got a weird verbose output reading "cannot mount disk1s3", whereas disk tools does not have such a volume. I suspect that there is some change in the APFS thingy, just like TimothyR734 wrote.
Went back to 10.4.0 by re-installing from USB stick, kept all user profile/data/settings. Nothing lost but some time ;-)

IMHO, one should never trust any of this installations which involve failing boot rom updates as we can't be sure how much of the installation scripts sit on the other side of those steps.

 

[olad]

IMHO, one should never trust any of this installations which involve failing boot rom updates as we can't be sure how much of the installation scripts sit on the other side of those steps.

If memory serves me right, it wasn't until DP3 of macOS 10.13.6 that it was stable and useable on my MBP4,1. I expect that this one will go the same way...

 

[jackluke]

Hi I have se same issue (Macbook Pro 5.5 Final Mojave release, updated from High Sierra). Did you ever solve the problem?

Yes, use this file and you will fix prefpanes issues: Corebrightness fix prefpanes Mojave
(credit to @Olivia88 for discovering correlation between CoreBrightness and System Prefs)

 

[yeiyei0891]

in some menus the text looks very bad, bold and pixeled, as in chrome, can it be fixed?

 

[jackluke]

Maybe i got it from a friend. He said it is fully working. Testet with an apple system ( but he sold it) and with win 10.

But here it isnt working. Wether on apple or win 10.

Bluetooth version to old?
Or doesnt matter?
Why it says apple wireless mouse not magic mouse? Is this o.k.?

Probably faulty, BT version doesn't matter, I have MM2 working fine with BT 2.1 and BT 4.0 , but I have a doubt are you sure that yours is a MagicMouse1 ?

Check on the web MagicMouse 2 they are identical except the MM1 hasn't a lithium battery, but the design is identical, if yours is not identical to MagicMouse 2 then you don't have a MagicMouse1 but only a simple apple wireless mouse formerly Apple Mighty Mouse Bluetooth
[doublepost=1538041427][/doublepost]

Is your usb dive 8gb or 16gb because 16gb is a requirement and is it formatted extended journaled not apfs

Any macOS Installer is NOT journaled you can check it from DiskUtility.

 

[webg3]

in some menus the text looks very bad, bold and pixeled, as in chrome, can it be fixed?View attachment 789491

defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO


a few pages ago someone posted the solution, I would like people to read a little, I know the thread is long, but at least 5 pages to be able to stand.

 

[yeiyei0891]

Here is a dirty correction.

What I did was repeat the same lines with a pause, it worked.


#!/bin/bash
echo “Reduce Transparency of Menus and Finder, keep the Dock transparent.”
# Run on.
defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight
defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight

kill `ps -A | grep -w Terminal.app | grep -v grep | awk '{print $1}'`
echo "Done!"

Some submenus still look very bad, like chrome. This can not be fixed too?

Edit: the patch did not work well on the first attempt, now the text and the submenus are ok

 

[macamok]

Yes, use this file and you will fix prefpanes issues: Corebrightness fix prefpanes Mojave
(credit to @Olivia88 for discovering correlation between CoreBrightness and System Prefs)

OMG! It works. And now I also have NightShift working. Thank you so much. This community is so cool!
Do you know if this will stay in affect after software updates, or do I need to “reinstall” Corebrigtness at some point?

 

[jackluke]

Can you tell me where is that iSight patch, please? Thanks.

As it says in the OP first page of this thread iSight is hit or miss on some Macs it may or may not work I have a mid 2009 MacBook and the iSight does not work even replaced the 5 kexts from HS no luck

I'm starting to think that to those who iSight doesn't work, if they don't have a Mac natively supported till HighSierra 10.13.x, so I gamble the idea probably to make isight work they should use very legacy IOUSB*** for example from El Capitan 10.11.x.

 

[webg3]

Some submenus still look very bad, like chrome. This can not be fixed too?
View attachment 789496

Edit: the patch did not work well on the first attempt, now the text and the submenus are ok
View attachment 789498

after applying my solution, you need to quit any application and open it again.

 

[L Caputo]

I, for one, am quite satisfied with leaving things with @dosdude1. He's done an admirable job with the patcher, he's at college, he answers (almost all) questions, provides free advice to anyone who asks, and he tells you what he is going to add. He's human, not superman, and a little patience by some would be appreciated, I think, by him. I would NOT want his software open sourced. If he thinks an idea is worthy of inclusion WITHOUT adding bloat to the patcher, then he should be the one to decide to include it or not. Anyone who thinks his FREE patcher (or any of his other software) is not inclusive enough is free to write his/her patcher on Github, and those who want will go there.

Totally agree with you dosdude1 has done more than enough to keep our Macs moving forward, so it would be nice if people stopped demanding he fix this and include that, he has a life out with these pages and am sure things will be addressed in time.
I came to these unsupported pages when my Mac was excluded from Sierra and I don't remember the unsupported Sierra and High Sierra pages having so many people unduly demanding fixes. We are very lucky there are people like dosdude1 and the many others who also contribute their time and expertise to help others without financial gain, I think we should all applaud them for their selfless behaviour. And give them a break.

 

[fintematic]

I'm starting to think that to those who iSight doesn't work, if they don't have a Mac natively supported till HighSierra 10.13.x, so I gamble the idea probably to make isight work they should use very legacy IOUSB*** for example from El Capitan 10.11.x.

Uhm i can try. Do you know where i can find these files?

 

[yeiyei0891]

after applying my solution, you need to quit any application and open it again.

but i have to apply that command in terminal every boot? Sorry but i don`t speak english very well and it's difficult for me to read and understand every post. I am applying the Lightmode v3 script on boot but still some texts look bad.

 

[jackluke]

defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO


a few pages ago someone posted the solution, I would like people to read a little, I know the thread is long, but at least 5 pages to be able to stand.

Yes, I've tried and it will render the overall Finder menu fonts thinner, but I prefer to use the standard "bolded" one. I advise to the others that this is not the "Use LCD font smoothing when available", but is another font smoothing hidden feature lets say mainly for Retina screens.

To restore Mojave defaults I've done from Terminal: defaults delete -g CGFontRenderingFontSmoothingDisabled

 

[webg3]

but i have to apply that command in terminal every boot? Sorry but i don`t speak english very well and it's difficult for me to read and understand every post. I am applying the Lightmode v3 script on boot but still some texts look bad.
View attachment 789511 View attachment 789512

LightMode only fixes the transparency problems of Finder and Menu, does not fix fonts.

 

[yeiyei0891]

LightMode only fixes the transparency problems of Finder and Menu, does not fix fonts.

This command fixed that, but then i'll have to apply this command in terminal in every boot? is not possible do it with a similir script like Lightmode?

 

[webg3]

This command fixed that, but then i'll have to apply this command in terminal in every boot? is not possible do it with a similir script like Lightmode?

I thought that when I rebooted it would keep the configuration of these fonts.

Just add the command in LightMode (open it with the Text Editor)
[doublepost=1538047590][/doublepost]Final Cut Pro X gains official eGPU support in macOS Mojave

 

[Starplayr]

It didn't last long I rebooted after installing 10.14.1 now stuck on the apple logo , tried booting into my external hdd with 10.14 it gets stuck my usb Mojave patcher can't boot into I think I am sol

Wait for the real updater. I am sure the developer ones now are unstable.
[doublepost=1538048181][/doublepost]

The same here ! Any solution ?

There’s really no sense in installing developer betas at this point. We were lucky the previews and betas before the GM were so stable. More than likely Apple is trying new things out in the developer betas and will be unstable.

 

[smokesletsgo]

Totally agree with you dosdude1 has done more than enough to keep our Macs moving forward, so it would be nice if people stopped demanding he fix this and include that, he has a life out with these pages and am sure things will be addressed in time.
I came to these unsupported pages when my Mac was excluded from Sierra and I don't remember the unsupported Sierra and High Sierra pages having so many people unduly demanding fixes. We are very lucky there are people like dosdude1 and the many others who also contribute their time and expertise to help others without financial gain, I think we should all applaud them for their selfless behaviour. And give them a break.

You both aren't making any sense. Just some emotional rambling. Of course everyone is gratefull for someone giving effort and doing this but going opensource would be a godsend for this project. Not only it would take the load off the pioneer dosdude1 but also it would speed things up, provide transparency etc. Can't see any disadvantages.