macOS 10.14 Mojave on Unsupported Macs Thread

[DaniloGeekDude]

@dosdude1,

Just saw on the front page that Public Beta 2 has been released. Will your Mojave Patcher | Tools download this latest one? I tried earlier and the "Install MacOS Beta" app still shows version 14.0.11 in the version.plist file, which I believe is still PB1.

Thanks.

 

[nekton1]

Your prayers weren't answered.

Oh dear god please Brazil win, we can't possibly have England win, they will never shut up about it, they keep reminding us at any opportunity that they won in 1966, 52 flipping years ago.

 

[snifferdogx]

So, MBP mid-2010, with SSD & 4GB RAM - Public Beta 2 won't even install. Not happy.

 

[kenau]

Your prayers weren't answered.

But my prayers, who Brazilian am, were. LoL
Brazil at this moment needs so many other things more important than a football world cup, which a world championship it is merely a dischargeable thing.
[doublepost=1530910648][/doublepost]

wait, what? Dynamic Wallpaper works now also on Dark or still only on Light?
[doublepost=1530902281][/doublepost]
press CMD + V

for what I understood, the dynamic desktop works when has a transition between day and night, or between night and day, or I'm wrong? sorry.

 

[milescortez]

Try installing the latest "trunk" build of Chromium, which likely has already been fixed for Mojave:
https://chromium.woolyss.com/

click on the top one, where "Installer" is highlighted in blue.

If it works (fixes were in fact implemented), then you can expect those fixes to make it "downstream" into Chrome stable in about 1-2 months. (!) No wonder it doesn't work on Chrome stable/Official Build...


Chromium is super extra incredibly bleeding edge and lacks the "Widevine" DRM monster (no netflix, hulu), "Pepper" Flash (so no adobe flash/shockwave) and any other proprietary code/codecs like h.264, so it will play Youtube perfectly fine (if it has been fixed for Mojave) but some other websites will break. Youtube by default uses VP9, so it is unaffected by the uninclusion of proprietary codecs.

It does not auto-update. Chrome Canary is a few days behind, so test Chromium first.
[doublepost=1530847521][/doublepost]

You betcha, just do a

find /System/Library/Frameworks -name '*.framework' and a
find /System/Library/PrivateFrameworks -name '*.framework'

on both HS and Mojave and then run a diff between the two output file lists.

(the -name is to find nested frameworks within another one, so to get a complete list)

Attachments on DP1 are broken for me, and I haven't yet updated, so if someone could run those commands on Mojave and High Sierra and /usr/bin/diff the two outputs and post that, it would be a great help.

FYI---The new Mojave Beta build also fixed the issue but I'm liking the idea of having Chrome, Canary and Chormiu . all installed to play around with. Thanks again!

 

[Starplayr]

Very good! I will try it soon ...

The only thing about VirtualBox unless it’s kext’s actually do something on the host, you don’t get additions or any Acceleration on MacOS clients. Fro me that’s s deal breaker. Parallels 13 works great with modern MacOS installs but now it’s stinks up the place with Snow Leopard Server. VMware Fusion is better at Snow Leopard Server than VB and Para.

VBox is free, but seems to more geared towards Windows clients.

 

[tn-xyz]

So, MBP mid-2010, with SSD & 4GB RAM - Public Beta 2 won't even install. Not happy.

then you did something wrong or have a patched installer that got corrupted.

 

[DaniloGeekDude]

@dosdude1,

Just saw on the front page that Public Beta 2 has been released. Will your Mojave Patcher | Tools download this latest one? I tried earlier and the "Install MacOS Beta" app still shows version 14.0.11 in the version.plist file, which I believe is still PB1.

Thanks.

I think I have the latest. I used your separate "MacOS Downloader" app to download. Looked under Contents and saw that the version on version.plist is 14.0.12. The files are dated June 29 though, so it could be Developer Beta 3 and not Public Beta 2.

Either one will work for me. Thanks again.

 

[Macbookprodude]

Offtopic rant:

It is interesting to note that the busiest and most sought after topic under the Mojave section of the forums is called "macOS 10.14 Mojave on Unsupported Macs Thread". It is easy to see why - a 2011 Mac Mini or even a 2009 i5/i7 iMac 27" are almost just as capable machines as some of the current offerings.

Somebody should really make a petition, maybe Apple will change it's mind.

Forcing hardware obsolescence through software is a bad practice, it is not environmently friendly and clearly devalues even a few year old Mac. It undermines the case to purchase a higher priced, but more lasting Mac instead of a PC. Now it seems the opposite is true: a PC is usually both less expensive, lasts longer (at least on the software side) and more versatile. Also, it is noteworthy that I can install the latest and greatest Windows on any of the unsupported Intel Macs (even those dropped by Sierra) and it will work perfectly well.

I am also quite unhappy about the fact that with each new version Mac OS there is a danger for a bunch of old applications to just break forever. Games are a prime example: on the latest Windows I can run 15 year old game and it will probably work without problems. Now when I try the same even with a few years old game (which by some strange turn of events was ported to Mac), even if it somehow starts, the OS will surely complain that the app is not optimized and will soon cease to function unless the developer does something (it won't, since it probably wasn't really profitable to port it to Mac in the first place), only because Apple decided that running a 32 bit application will not be appropriate anymore in 2019 (ohh, and OpenGL will also be removed in a few years time). I understand that Apple is always a forward looking company, but even as a longtime and loyal Mac user, I'm just getting to feel a bit too claustrophobic as the walls of Apple's pretty garden are getting ever closer around me.

Rant over. Sorry. I know I'm being stupid and unapplefanlike.

Won't happen, unless leadership steps down and new people come on who are supportive of older machines.
[doublepost=1530929778][/doublepost]Guys, I think its best to wait until someone can get inside the code and rework it somehow to fix these issues.. i still can't get Mojave on my 2011 MB Pro, but I will just replace the 2011 board with a 2012 which I can get for under 200 bucks.. then i can install it.. But really, since this is a beta. I myself would not run beta anything on my system as its not stable.. so, I think its best we wait for the final release to come out.. Then de0compile it and find out what needs to be done to get it to work on unsupported systems. Just my 2c.

 

[Czo]

[doublepost=1530905877][/doublepost]
Do you know if HS version works already?

I don't know, not checked it, but because it's patching the softwareupdated's xml reading capability, if still softwareupdated is used in Mojave, maybe it will work without any modification.

 

[DaniloGeekDude]

I think I have the latest. I used your separate "MacOS Downloader" app to download. Looked under Contents and saw that the version on version.plist is 14.0.12. The files are dated June 29 though, so it could be Developer Beta 3 and not Public Beta 2.

Either one will work for me. Thanks again.

Looks like my update was Developer Beta 3.

Took me awhile. The update seems like a fresh install and crashed towards the end. My next step was to re-run the post install patch, and created my user accounts from scratch.

Anyways I'm good to go until the next release.

 

[MarUno]

What Mac i need to try this?

 

[Larsvonhier]

I don't know, not checked it, but because it's patching the softwareupdated's xml reading capability, if still softwareupdated is used in Mojave, maybe it will work without any modification.

The modification script (found on dosdude1´s page) works fine for getting the update from Mojave beta 2 to beta 3.
Tried it yesterday and it still works even under the new/old update location in the system settings instead of app store.
[doublepost=1530949676][/doublepost]

What Mac i need to try this?

see page #1

 

[iApply]

No! Add airportatheros40 kext from 10.13. (it's inside io80211family). I've told like 6 people this...

Can you tell me how to do that? where to find the Kexts?

 

[BookEmDanno]

What Mac i need to try this?

Check out the OP on this thread.
https://forums.macrumors.com/threads/macos-10-14-mojave-on-unsupported-macs-thread.2121473/

 

[NisseA]

have anyone got this message trying to install from usb using the usb created from the tool downloaded from here?

 

[andrey_russian]

The font smoothing bug is happening to me on real retina MBP (11,1)
[doublepost=1530905669][/doublepost]
No! Add airportatheros40 kext from 10.13. (it's inside io80211family). I've told like 6 people this...
[doublepost=1530905877][/doublepost]
Do you know if HS version works already?

The font smoothing bug is happening to me on real retina MBP (11,1)
[doublepost=1530905669][/doublepost]
No! Add airportatheros40 kext from 10.13. (it's inside io80211family). I've told like 6 people this...
[doublepost=1530905877][/doublepost]
Do you know if HS version works already?

Thank you. I used airportatheros40 kext from 10.13 + kext utility. Built-in wifi adapter working now.

 

[MarUno]

I going to try in a imac5,1. I going to fire the Mac > : D

 

[Larsvonhier]

Hello I have the same Mac model I am running macos Mojave so the sound is not working. I tried many options but the problem persists. Could you help me please? Thanks

This is solved very conveniently by using dosdude1´s post install tool - just boot the installer stick once more, start post install and select MacBook Air 4,1 - or manually check "legacy audio". Do the cache refresh and reboot...

 

[andrey_russian]

Can you tell me how to do that? where to find the Kexts?

https://cloud.mail.ru/public/LnBR/gpJBWGoyM

 

[nathansz]

that’s unfortunate news about the amd drivers

really gives the impression that apple is actively exuding effort to lock out machines more capable than many of the ones they are selling now

graphics glitches aside, mojave was noticeably “snappier” on my 2011 imac than my 2012 mpb

 

[redking31591]

Looks like my update was Developer Beta 3.

View attachment 769414

Took me awhile. The update seems like a fresh install and crashed towards and I had to re-run the post install patch, and created my user accounts from scratch.

Anyways I'm good to go until the next release.

how’d you get around the crash? Did you have to completely set up macOS again?

Edit: nvm, figured it out.

 

[Larsvonhier]

In the menu when you choose the usb/harddrive ect to boot from?

Yes, in the boot selector menu it works best to hold CMD V while using the trackpad to click on the arrow icon of the desired drive

 

[TMRJIJ]

Core 2 Duo/nVidia MCP79/89/i965-based systems will kernel panic on boot. The cause of this kernel panic has yet to be determined. It is NOT caused by USB drivers or a lack of SSE4.2. It does not occur in virtual machines.

Having just bought a MBP (Late 2013), my MBP (Mid 2010) is open for testing if you need help. Just don’t know how long I’ll be available with my classes ongoing and the promotion I’m getting at work.

 

[c0c0p0ps]

The modification script (found on dosdude1´s page) works fine for getting the update from Mojave beta 2 to beta 3.

Tried it yesterday and it still works even under the new/old update location in the system settings instead of app store.

[doublepost=1530949676][/doublepost]

see page #1

Can confirm that the High Sierra update Software Update patch script is also working for the public beta - even though my 2011 MacBook Air 4,2 is not supported I still downloaded the public beta registration tool, and it then picked up beta 2 straight away!

Install went smooth as normal and rebooted to desktop no problem - As I installed to an existing APFS partition I had to run the no_compat_check in terminal to get passed the 'no entry' sign on startup. Intel HD3000 kext seems to have survived the update but the audio is gone. Have run the Post Install Utility again from dosdudes tool on page 1, rebuilt caches and it all seems to be back again.