macOS 10.14 Mojave on Unsupported Macs Thread

[avz]

For people with a iMac 2011 with an AMD 6750M 512Mb GPU. I got it working with normal colors!
For now it is working in a test setup with an external HDD.

What works:
- video showing no strange colors
- audio is working
- external screen via DisplayPort/ thunderbolt
- wifi

Strange behavior:
- for as far as I can see no transparenacy
- the search bar shows a horizontal line
- maps not working

What I tested:
- Youtube 1080P works very well
- Quicktime 1080P works also very good (sometimes some lines... but overall no problems)
- Photoshop - works great, only some hiccups when moving large area's
- Zoom works
- Affinity Design does work but suffers from strange lines etc...

I am not a gamer, but I had a Sims 2 installation on the HDD and that worked
However Unreal Tournament 2004 was not able to run. So I guess this is no setup for gaming.

===========

What did I do to install this?

1. Install via normal means with DosDude patcher
2. Go to his fix with the Kext files
3. Patch the system again
4. Downloaded this and install the kext files from a YouTube video (Link is =

)

If this is not allowed please remove! I do not want to do stuff against the rules...

Judging by the picture there is still no graphic acceleration. Not sure what was the point of this exercise. My Late 2008 unibody MacBook can handle heavier activity without any issues.

 

[techinfant]

So I went through with my repeat of the clean install on my MBP 5,5 as described above, and had some interesting things happen:

• The TM restore during the post-install setup went through, albeit with some errors. It wasn't able to transfer a few /Library files over.
• After I logged in, I got a blank startup screen.
• I restarted the Mac, and it restarted itself thrice before it finally went through and took me to the login screen.
• Once I logged in, the CPU was calm for a change. I suspect skipping iCloud during setup helped.
• Oddly enough, I was unable to open any downloaded files (I tried apps, and image files); I suspect this has to do with some of the Library files not transferring over.
• My System Report shows that macOS 10.14.6 (18G103) is installed. (I expected that with having installed Mojave on APFS, I would be offered the latest Mojave Security Update 2020-002, either via the App Store or Patch Updater. I plan to manually run that update - hoping it'll fix the issue with downloaded files - and will update this post with the results.
• Scratch the above; I was able to find the Security Update under System > Software Update, and install it successfully. However, it wouldn't start back up after going through numerous restart cycles. Ultimately, I applied the patch, and it went through and started up. However, once I logged in, Mojave notified me that due a Panic Medic Boot, it had decided to disable all third party kernel extensions. So I went through a few iterations of applying patches through the Patcher Tool ("force rebuild") and Patch Updater, and finally seem to have things up and running. One good side-effect of this ordeal is that downloaded files are opening now

I hope some of this will be helpful to others, and I'm open to any pointers to doing anything differently. Thank you!

A quick follow-up question after my clean install. Now that I'm able to open downloaded files, I decided to move my ~/Downloads folder from the SSD to the HDD, and create a symlink on the SSD to keep things seamless. However, when I tried the run the commands, which involved sudo, it turned out that my account was not in the /etc/sudoers file despite being designated as an administrator. I was able to work around it, but am wondering if this is normal for a clean install of Mojave, or a symptom of something problematic with the clean install. Thank you for weighing in.

 

[jasoncarle]

I strongly suggest going here and getting an SSD if you're going to run APFS and Mojave. They have them available for most Macs, yes even old ones.

OWC SSDs for Apple Desktops, Laptops, and PCs

Experience the maximum speed of your Mac or PC by upgrading to an OWC SSD. Find the prefect SSD for almost any Mac Pro, iMac, MacBook Pro, and more.

eshop.macsales.com

[automerge]1588386790[/automerge]

A quick follow-up question after my clean install. Now that I'm able to open downloaded files, I decided to move my ~/Downloads folder from the SSD to the HDD, and create a symlink on the SSD to keep things seamless. However, when I tried the run the commands, which involved sudo, it turned out that my account was not in the /etc/sudoers file despite being designated as an administrator. I was able to work around it, but am wondering if this is normal for a clean install of Mojave, or a symptom of something problematic with the clean install. Thank you for weighing in.

not normal... You seem to be having a lot of problems.

 

[techinfant]

I strongly suggest going here and getting an SSD if you're going to run APFS and Mojave. They have them available for most Macs, yes even old ones.

OWC SSDs for Apple Desktops, Laptops, and PCs

Experience the maximum speed of your Mac or PC by upgrading to an OWC SSD. Find the prefect SSD for almost any Mac Pro, iMac, MacBook Pro, and more.

eshop.macsales.com

[automerge]1588386790[/automerge]


not normal... You seem to be having a lot of problems.

Thank you for weighing in and confirming my suspicions. My hunch is that restoring from the TM backup was introducing some system-level errors. So I did another clean install on the SSD and decide not to restore (for now), and things seem to be running smoothly. I found that relocating the Downloads folder and the iTunes Media folder to the HDD work nicely, but moving the Photos Library to the HDD causes artifacts when zooming in/out in the Photos app, so the Photos Library better kept on the home drive (SSD). One other thing - I've never run this cool in a while! I suspect that is from holding off an iCloud for now, so no syncing in the background to constantly tax the CPU. I'll see how it goes for some time and then look into replacing the HDD with an SSD; thanks for the pointer!

 

[quaccOS]

So I went through with my repeat of the clean install on my MBP 5,5 as described above, and had some interesting things happen:

• The TM restore during the post-install setup went through, albeit with some errors. It wasn't able to transfer a few /Library files over.
• After I logged in, I got a blank startup screen.
• I restarted the Mac, and it restarted itself thrice before it finally went through and took me to the login screen.
• Once I logged in, the CPU was calm for a change. I suspect skipping iCloud during setup helped.
• Oddly enough, I was unable to open any downloaded files (I tried apps, and image files); I suspect this has to do with some of the Library files not transferring over.
• My System Report shows that macOS 10.14.6 (18G103) is installed. (I expected that with having installed Mojave on APFS, I would be offered the latest Mojave Security Update 2020-002, either via the App Store or Patch Updater. I plan to manually run that update - hoping it'll fix the issue with downloaded files - and will update this post with the results.
• Scratch the above; I was able to find the Security Update under System > Software Update, and install it successfully. However, it wouldn't start back up after going through numerous restart cycles. Ultimately, I applied the patch, and it went through and started up. However, once I logged in, Mojave notified me that due a Panic Medic Boot, it had decided to disable all third party kernel extensions. So I went through a few iterations of applying patches through the Patcher Tool ("force rebuild") and Patch Updater, and finally seem to have things up and running. One good side-effect of this ordeal is that downloaded files are opening now

I hope some of this will be helpful to others, and I'm open to any pointers to doing anything differently. Thank you!

I installed Security Update 2020-002 and it bricked my MacBook Pro 8,3. However my MacBook Pro 7,1 updated to it without problems – I just re-ran Post Install. 2011 17" MBP did not like the new Security Update…

 

[techinfant]

I installed Security Update 2020-002 and it bricked my MacBook Pro 8,3. However my MacBook Pro 7,1 updated to it without problems – I just re-ran Post Install. 2011 17" MBP did not like the new Security Update…

Sorry to hear about the bricking. I hope you had backups and can reuse the machine ?

 

[jowaju]

I installed Security Update 2020-002 and it bricked my MacBook Pro 8,3. However my MacBook Pro 7,1 updated to it without problems – I just re-ran Post Install. 2011 17" MBP did not like the new Security Update…

The update did not “brick” your machine. That means it is dead, completely and forever. What happened was it undid the GPU fixes you had in place to disable your AMD video card so it could run Mojave in the first place. Specifically it put the AMDRadeonx3000.kext back in the system/library/extensions folder. Just go move it/rename it/delete it from that folder and you should be fine again.

PS - Once you get a 2011 15/17” MacBook Pro working with Mojave, it’s best to leave it alone unless you really really know what you are doing. They are absolutely fast and stable once you tweak them just right, but they are very picky about changes. Best to leave them alone.

 

[techinfant]

Thank you for weighing in and confirming my suspicions. My hunch is that restoring from the TM backup was introducing some system-level errors. So I did another clean install on the SSD and decide not to restore (for now), and things seem to be running smoothly. I found that relocating the Downloads folder and the iTunes Media folder to the HDD work nicely, but moving the Photos Library to the HDD causes artifacts when zooming in/out in the Photos app, so the Photos Library better kept on the home drive (SSD). One other thing - I've never run this cool in a while! I suspect that is from holding off an iCloud for now, so no syncing in the background to constantly tax the CPU. I'll see how it goes for some time and then look into replacing the HDD with an SSD; thanks for the pointer!

Follow-up: I experimented some more with Photos for Mac (4.0), and turns out the artifacting persists even with the library on the home drive (SSD), so it seems like an underlying issue with the OS or the patch. Essentially, any time I try to edit an image and click on crop, Photos starts to beachball, and once it stabilizes, the cropped image appears corrupted. Internet research suggests this is a previously observed quirk on Photos (and iPhoto) across generations, and even this thread has instances of instability in Photos, but I didn't find a fix. This is a bit of a setback, as one of my primary reasons to upgrade to Mojave was to use the new editing features in Photos. I'd greatly appreciate if anyone can share a fix or pointers to underlying issues to remedy. Thank you!

 

[avz]

Follow-up: I experimented some more with Photos for Mac (4.0), and turns out the artifacting persists even with the library on the home drive (SSD), so it seems like an underlying issue with the OS or the patch. Essentially, any time I try to edit an image and click on crop, Photos starts to beachball, and once it stabilizes, the cropped image appears corrupted. Internet research suggests this is a previously observed quirk on Photos (and iPhoto) across generations, and even this thread has instances of instability in Photos, but I didn't find a fix. This is a bit of a setback, as one of my primary reasons to upgrade to Mojave was to use the new editing features in Photos. I'd greatly appreciate if anyone can share a fix or pointers to underlying issues to remedy. Thank you!

Erase and rewind?
Keep in mind that not all SSD's are "good" for Macs. The only time I remember seeing a beachball is when I was trying to save photos to the Samsung USB flash drive. I am surprised how quickly they go bad and slow down(~2 years).

 

[techinfant]

Erase and rewind?
Keep in mind that not all SSD's are "good" for Macs. The only time I remember seeing a beachball is when I was trying to save photos to the Samsung USB flash drive. I am surprised how quickly they go bad and slow down(~2 years).

Thank you for the pointer. Will keep an eye on the SSD health. I get the sense that the problem here is an issue with the Photos app on Mojave, either natively, or due to my machine configuration after the patch. I am thinking of reverting to High Sierra to see if the problem persists. That would help narrow down the issue.

 

[techinfant]

Thank you for weighing in and confirming my suspicions. My hunch is that restoring from the TM backup was introducing some system-level errors. So I did another clean install on the SSD and decide not to restore (for now), and things seem to be running smoothly. I found that relocating the Downloads folder and the iTunes Media folder to the HDD work nicely, but moving the Photos Library to the HDD causes artifacts when zooming in/out in the Photos app, so the Photos Library better kept on the home drive (SSD). One other thing - I've never run this cool in a while! I suspect that is from holding off an iCloud for now, so no syncing in the background to constantly tax the CPU. I'll see how it goes for some time and then look into replacing the HDD with an SSD; thanks for the pointer!

Observing the following quirky behavior on my MBP 5,5 after a clean install with the patcher tool:

• Following clean install, Patch Updater alerts me of a few updates: Software Update Patch, Night Shift Patch, News OpenCL Patch. I apply these updates.
• Security Update 2020-002 is not flagged by the Patch Updater (likely by design), so I installed this update via System Prefs > Software Update > More items. On restart, I need to run the patcher tool to apply patches so I can restart the Mac.
• On login, Patch Updater notifies me that there is a newer Software Update Patch. So I run the update and restart the Mac.
• After the patch, Patch Updater notifies me that the Night Shift patch was overwritten, and asks me to reapply it. I do it and restart again.

I suspect there is a better way to sequence these updates so I do not have to restart as many times. Anybody else notice this behavior on their systems and / or know if I'm doing something wrong? Any pointers will be appreciated.

 

[jconly01]

So here goes a blow by blow account of how this worked (for me)
View attachment 776077
READ THIS PANEL! After doing so I heard a long Beep! Then your machine will boot up normally...
View attachment 776078
View attachment 776079 View attachment 776080
Success!
View attachment 776082 View attachment 776083
Your backed up roms are here...
View attachment 776084
Profit!

I haven't installed APFS yet. Will do so tonight...

Hey all ( and @dosdude1 ) ... I did this APFS ROM update a while ago, and things were a success.
After a bit of usage though, my MacPro 3.1 started to randomly power off.
Regardless of whether booted into OSX or otherwise.
I swapped the PSU thinking that could be an issue, but problem returned.
All other hardware checks out fine.

Hoping to revive the machine. Is it possible to restore to my original ROM?
Any tips on how to achieve this would be appreciated. Still have the backup.
Thanks.

 

[techinfant]

Thank you for the pointer. Will keep an eye on the SSD health. I get the sense that the problem here is an issue with the Photos app on Mojave, either natively, or due to my machine configuration after the patch. I am thinking of reverting to High Sierra to see if the problem persists. That would help narrow down the issue.

Reverted back to High Sierra by way of a similar clean install (on the APFS-formatted SSD), and found that the artifacts during cropping in Photos are not quite as bad as in Mojave, but the app crashes frequently during editing. I'm starting to think that age has caught up with my Mac and it is no longer able to keep up with the processing requirements of the newer apps and OSes. Even so, it's surreal to be able to run the newer OSes on these older Macs, and I'm learning a ton. Much thanks to @dosdude1 and the other ninjas here that make this happen! ?

 

[TimothyR734]

unzip this script and run it in the terminal to get Zoom 5.0 working from dosdude

 

[Eithanius]

Is Zoom even safe to use nowadays...?

 

[TimothyR734]

The new version is supposed to fix the flaws by the end of the month the older versions will not work
[automerge]1588737308[/automerge]

Video Conferencing, Web Conferencing, Webinars, Screen Sharing

Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webinars across mobile, desktop, and room systems. Zoom Rooms is the original software-based conference room solution used around the world in board...

zoom.us

 

[trifero]

Is Zoom even safe to use nowadays...?

?

 

[BvanBart]

Is Zoom even safe to use nowadays...?

Yes... they really made effort in security. Using it each day as a teacher for college.

 

[BvanBart]

Woaw... Just tried the most fun thing:
Installed Parallels 14 on High Sierra... installed Mojave from Dosdude without the patching... and it works xD!
I can even run games all without graphical issues?! Performance is ofcourse 90% from what it would otherwise be... But still... I am surprised that this works?!

@dosdude1 is it possible to use this somehow in a patch to run newer versions on the not supported GPU's?

 

[pqueirosf]

Hello, i'm a new fan this, and ia have some problems with my Grafic card and my creative x-fi fatality on Mojave 10.14.6 (18G103) can anyone help me?
Tank's

 

[havannaffair]

Hey there! First things first: thanks to everyone involved in this! My MacbookPro 7,1 is working flawlessly with the last Mojave update. And know I can even run the latest Zoom update which is great for the lessons I must give. I do have a small problem:

• Everything works great but i noticed this odd behaviour: when I open a Pages file, it crashes whenever a "smart annotations" that i did on my iPad appears on screen. It justs freezes Pages. It's the only thing that bothers me since I do quite a lot of this manual writing. This happens on Catalina (same 7,1 Mac, with the Patcher) too. If I hide the smart annotations i can see all the pages on the document normally. Naturally, this is not the best since I cannot edit them. Also, if even one small annotations is on the first page, the file does not even open.

Also I have just 1.40GB free of a total 8GB RAM. While on High Sierra I would normally have between 2 and 4 GB. Is Mojave more intense on memory or is there something I can do to balance this? Otherwise everything is normal, the system is working great and snappy.

If anyone can give me a hand, I'll be thankful!

 

[TBrownJr]

Hello!

I've got a MacBook Pro 8,1 early 2011. I installed Mojave 10.14.6 and everything has been working perfectly except for the built-in iSight camera. Whenever I open FaceTime it says: "no video, FaceTime has not received any video from the connected camera. Restarting your computer may fix this issue." Even after couples of restart, it didn't work. And it wasn't really bothering because I didn't need the camera by then. But now that I'm working a lot more from home, I get to do conference calls.

Has any fix been release yet for the built-in iSight camera on MacBookPro 8,1?
Specs if needed:
- Processor: 2.3 GHz Intel Core i5
- Memory: 8GB 1333MHz
- Graphics: Intel HD Graphics 3000 512MB

Thanks

 

[jowaju]

Hello!

I've got a MacBook Pro 8,1 early 2011. I installed Mojave 10.14.6 and everything has been working perfectly except for the built-in iSight camera. Whenever I open FaceTime it says: "no video, FaceTime has not received any video from the connected camera. Restarting your computer may fix this issue." Even after couples of restart, it didn't work. And it wasn't really bothering because I didn't need the camera by then. But now that I'm working a lot more from home, I get to do conference calls.

Has any fix been release yet for the built-in iSight camera on MacBookPro 8,1?
Specs if needed:
- Processor: 2.3 GHz Intel Core i5
- Memory: 8GB 1333MHz
- Graphics: Intel HD Graphics 3000 512MB

Thanks

Boot to the patcher, choose post install patcher, choose your model from the drop down menu, make sure the Legacy iSight patch is checked, then apply. Make SURE you choose the Force Cache Rebuild option BEFORE clicking reboot. Now try your Camera again with Facetime. If it still doesn't work, repeat this procedure until it does. Unless your camera is actually bad, this will fix it 100% of the time, in my experience.

 

[TBrownJr]

Boot to the patcher, choose post install patcher, choose your model from the drop down menu, make sure the Legacy iSight patch is checked, then apply. Make SURE you choose the Force Cache Rebuild option BEFORE clicking reboot. Now try your Camera again with Facetime. If it still doesn't work, repeat this procedure until it does. Unless your camera is actually bad, this will fix it 100% of the time, in my experience.

Thanks a lot, it helped.

 

[jowaju]

Thanks a lot, it helped.

It helped as in your iSight camera is now working?