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.
OMG : I thought that this was only a clean install tutorial!
Can you explain to me what is happening after step 4 when I want to upgrade from one version of mojave to the next?
It's a Standard normal upgrade, 100% the same compared to an Apple upgrade. All you're files stay how the are. Lots of people use this route to upgrade without dataloss. It's the most easy way to upgrade an Patched MacOS-install.
-Correct my if I'm wrong-

-My iMac9.1 MacOS inplace upgrade to 10.14.1 proceded fine; let it Install, give it time, do not interrupt the MacOS Install. After ~45m it was done. And I applied the Patches after the Install after.
 
Last edited:
I swapped out my 2 GeForce 880GT cards for 1 NVIDIA GeForce GT 120 (to see the boot screen) and 1 GeForce GTX 770. With the 2 GeForce 880GT installed and the legacy video patch, I was able to use 4 monitors (but not accelerated). With the GT 120 and GTX 770 installed without the legacy video patch, it hangs on boot. With the legacy video patch, it only can drive 3 monitors. Is this because I mixed a non-metal card with a metal card?

Note: When using the new cards with El Capitan, I can see all 4 monitors (and actually a 5th @ 4k! with the display port on the GTX 770).

To answer my own question... it appears they can't be mixed. On my Mac Pro 2008, I removed the GT 120 card and it booted into Mojave fine (without the gray boot screen as expected). I was able to connect my (1) 27" 4k 3860x2160 and (3) 27" 2560x1440 with full accelerated video.

I didn't choose to use APFS... is this really worth enabling?

Thanks @dosdude1 for the 10.14.1 patch update! I just installed it and it's working fine!

Screen Shot 2018-11-01 at 12.39.06 PM.png
 
  • Like
Reactions: TimothyR734
I was suggesting you to replace from your HighSierra /S/L/E/ into your Mojave /S/L/E/ these kext:

AirPortBrcmNIC-MFG.kext
IOBluetoothFamily.kext
IOBluetoothHIDDriver.kext
IO80211Family.kext
IO80211FamilyV2.kext

but before attempt this last chance to fix your Bluetooth 4.0, I guess @thicla01 is right, most probably only replacing IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from your HighSierra should work into your Mojave 10.14.1 , after replaced just install them from the Mojave Terminal procedure as you already know.

Ok. I did this conservatively and just installed the IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from HighSierra and did Terminal. BOOM, Bluetooth is up and running with connections from my mouse and keyboard! Thank you Jackluke and Tthickla01 !
 
@dosdude1

Do you have any ideas with CAT issue and BT 4 ?

Continuity Activation Tool worked with 10.14 with my Macmini late 2009 (with a swap module from an A1342 MacBook) and BT4 dongle but with 10.14.1 Continuity don't work.

Impossible to uninstall CAT due to APFS/no recovery partition... so impossible to re-install because it report that Continuity is already active (the same in System Prefs).

Thank for your really crazy great job !
 

Attachments

  • Capture d’écran 2018-11-01 à 21.12.41.png
    Capture d’écran 2018-11-01 à 21.12.41.png
    101.1 KB · Views: 135
  • Capture d’écran 2018-11-01 à 21.10.21.png
    Capture d’écran 2018-11-01 à 21.10.21.png
    98.4 KB · Views: 122
  • Capture d’écran 2018-11-01 à 21.05.37.png
    Capture d’écran 2018-11-01 à 21.05.37.png
    72.8 KB · Views: 130
  • Capture d’écran 2018-11-01 à 21.04.29.png
    Capture d’écran 2018-11-01 à 21.04.29.png
    84.6 KB · Views: 145
Last edited:
You need to refresh the webpage first, then download.

Something else (sorry to interrupt this way). Just did my fifth patch, but first mojave patch (on an iMac 8.1). Sound doesn't work. It remains on max, while the slider in the menu bar 'works'. The volume slider in Youtube works correctly (is controlling the sound volume), suggesting that it has something to do with the Mojave patcher. Re-patched etc. Also did a PRAM-reset. Sound is still not controllable. Any ideas?

PS Hello everyone!
 
Something else (sorry to interrupt this way). Just did my fifth patch, but first mojave patch (on an iMac 8.1). Sound doesn't work. It remains on max, while the slider in the menu bar 'works'. The volume slider in Youtube works correctly (is controlling the sound volume), suggesting that it has something to do with the Mojave patcher. Re-patched etc. Also did a PRAM-reset. Sound is still not controllable. Any ideas?

PS Hello everyone!
Did you install the Volume Control Patch using Patch Updater?
 
Information: "
Update to macOS High Sierra 10.13.6
First, use the Mac App Store to update your operating system to macOS High Sierra 10.13.6. Don't upgrade your Mac Pro (Mid 2010) or Mac Pro (Mid 2012) to macOS Mojave directly from macOS versions prior to 10.13.6.

https://support.apple.com/en-us/HT208898

If Apple even asks to upgrade to High Sierra instead of doing a clean install on these older devices, I think that's the way some of us should do, if you're having trouble installing Mojave, try this, install the High Sierra 10.13.6 first and from it upgrade, I did it both times (GM 10.14 and now in 10.14.1) and it worked very well...
Actually I upgraded from El Capitan straight to Mojave 14.1 on a MacMini3.1 with zero problems. Mail and everything was successfully upgraded extremely fast. The only thing I did before the update was to flash the EEROM update from @dosdude1for the native support of APFS. But even after I kept +HFS. Since the conversion can be performed at any given moment I prefer to wait a while. So in a complicated setup (+HFS & El Capitan) I upgraded straight to Mojave without a single problem. The only drawback is no WiFi, but for a mini wireless is usually not so important. Besides I still have a USB WiFi dongle for 15$ which gives wireless whenever I would need one.
 
  • Like
Reactions: TimothyR734
But "proving a point" of what? My procedure if followed carefully works at 99%, anyone has its own priorities to me is more important to have another emergency bootable partition with CMD+R available than upgrade immediately to 10.14.1 that essentially it's an minor update that to me doesn't add nothing new.

Using an internal Recovery apart many troubleshooting you can do to the disks, I have a macbook laptop, for example without booting from an USB Installer, I can save battery power; then another example if I have only 2 USB ports on the logicboard, booting from my internal Recovery I can plug two external USB independent unlocked drives, because as you know when you boot from an USB Installer the USB port used input/output is busy and the device is locked.

That said, in few points I could be agree with your argument.
Your situation is quite complicated my friend. 99% of people here lack knowledge and have a vanilla unsupported mac! They want to go to Mojave and are struggling with all the mumbo jumbo surrounding terminal commands, verbs mode and the rest. They are desperate and are scared to brick their machines. How do you think they feel going through posts, which do not concern them and only contribute to their confusion. My suggestion was to help that majority first. Once all has settled, turn to the exceptions. If you look at the posts in recent weeks, the majority are about beta updates. A point update between 14 and 14.1 is a lot bigger, than any of the betas. So most people would see as a priority going from 14 to 14.1, than to struggle, by your own words, with an obscure creation of a questionable benefit to unsupported macs, like the Apple default Recovery.
 
Has anyone had issues with their external webcams? iSight has known issues, but I'm running into issues with my external logitech webcam. It appears to fire up whenever I launch a camera based application, asks for permission, but shows nothing but a black screen. Puzzled by this. Anyone figure it out?

Yes, I have the same issue with a Logitech cam that was working under High Sierra. I'm running on a Mac Pro 3,1. Everything else seems fine (aside from the well documented graphics niggles). I don't use the webcam much, but it'd be nice if it worked.
 
  • Like
Reactions: TimothyR734
Yes, that is the standard Terminal procedure to install any kext: manual copy replacement into /S/L/E/ , chown/chmod its content, rebuild kextcache.
I would suggest people scared of terminal to use "Kext Drop.app", which will simplify the procedure and will prevent mistakes.
[doublepost=1541104515][/doublepost]
Wait a moment.
Is it possible to upgrade from 10.14.0 to 10.14.1 without using the official system update?
Am I missing something here?
Yes, just follow the steps I wrote above and stay away from Apple's updates in "Software Update" control panel. This way of updating is risky. The described steps are from @dosdude1 and are the only proven, walked-through way. On occasion they also might give problems, but at least there is plenty of people to help. Beta testing with "Software Update" control panel can cause unnecessary aggravation. And be patient, we are in an unchartered territory - the unsupported mac software updating. Your mac will function equally well with 14, 14b1, 14b2, 14b3, 14b4, 14b5 and 14.1. Just enjoy the OS!
 
Has anyone had issues with their external webcams? iSight has known issues, but I'm running into issues with my external logitech webcam. It appears to fire up whenever I launch a camera based application, asks for permission, but shows nothing but a black screen. Puzzled by this. Anyone figure it out?

Having just replied saying I had this issue, I have found a fix in one of the posts: macOS 10.14 Mojave on Unsupported Macs Thread

It worked for me and my Logitech C615!
 
  • Like
Reactions: TimothyR734
Then in case, to troubleshooting your main system, instead of re-installing or doing a full (all day long) TimeMachine, you can boot from CMD+R Recovery (using my hated APFS Recovery fix) or from any USB Installer (higher than Sierra to support APFS), simply launching the GUI TimeMachine Utility your snapshots restore points will be there ready-to-use.

You can add one extra unhater :p

First I checked that the recovery is indeed on disk1s3. Then

Code:
sudo diskutil mount disk1s3
cd /Volumes/Recovery
cd alphabet-soup-folder
sudo mv prelinkedkernel prelinkedkernelbackup
sudo mv immutablekernel immutablekernelbackup
sudo mv PlatformSupport.plist PlatformSupportBackup.plist
sudo cp -a /System/Library/PrelinkedKernels/prelinkedkernel immutablekernel

Then holding Command-R at boot is lauching the recovery tools. Thanks.
 
I wonder how @pkouame is advancing now on 14.1 with his great contribution to Light/Dark modes?

On my account patching Light/Dark modes is at the same level or even less priority than having the ability to use Command-R to enter in recovery mode. I live easily with the workaround of reduced transparency. The less files I have to modify from the original distribution the better for me.
 
Lucky you are :)
Not here iMac 10,1 samsung SSD
I had to do a clean installation (erase SSD) and then transfer from a clone the user with the migration assistant

But even with that i get stuck on a blank screen with a loop restart/blank screen/restart/blank screen ...:mad:

any idea ?

Well, I completely avoided the APFS experiment as there is no big win for me on this machine and it will only slow down the computer, what about you there? SanDisk 240 GB SSD and other 500 GB hybrid drive to to the mix, everything works 100%, only the track pad gets stuck after every odd week but a PRAM reset fixes it.
I wouldn't recommend going the APFS way with older machines, there is nothing to gain really.
 
Last edited:
You can add one extra unhater :p

First I checked that the recovery is indeed on disk1s3. Then

Code:
sudo diskutil mount disk1s3
cd /Volumes/Recovery
cd alphabet-soup-folder
sudo mv prelinkedkernel prelinkedkernelbackup
sudo mv immutablekernel immutablekernelbackup
sudo mv PlatformSupport.plist PlatformSupportBackup.plist
sudo cp -a /System/Library/PrelinkedKernels/prelinkedkernel immutablekernel

Then holding Command-R at boot is lauching the recovery tools. Thanks.

Exactly, well done, and since you like the Terminal way, to detect the APFS Recovery "random-numbers-letters" folder from Terminal just type:

diskutil info disk1s1 | grep "Volume UUID"

I wrote also another post where adjusting the preboot the APFS Recovery should work even if located elsewhere on diskXsY.
 
Last edited:
BTW, 10.14.2 DP1 has been restored, for those who care.

99% of people here lack knowledge and have a vanilla unsupported mac! They want to go to Mojave and are struggling with all the mumbo jumbo surrounding terminal commands, verbs mode and the rest. They are desperate and are scared to brick their machines.
Totally agree. And many avoid the use of Recovery by using CCC or similar software to back up their systems.
 
  • Like
Reactions: TimothyR734
BTW, 10.14.2 DP1 has been restored, for those who care.


Totally agree. And many avoid the use of Recovery by using CCC or similar software to back up their systems.

As a CCC 3.5, 4 and 5 license owner, I can also say that the free SuperDuper app does the job also perfectly, if there are no bucks to spend on software.

I would say no to the APFS issues (and to the OTA updates) for HFS+ with CCC or SuperDuper. :)
 
@dosdude1

Do you have any ideas with CAT issue and BT 4 ?

Continuity Activation Tool worked with 10.14 with my Macmini late 2009 (with a swap module from an A1342 MacBook) and BT4 dongle but with 10.14.1 Continuity don't work.

Impossible to uninstall CAT due to APFS/no recovery partition... so impossible to re-install because it report that Continuity is already active (the same in System Prefs).

Thank for your really crazy great job !

The dosdude1's USB Mojave Installer can act as a Recovery, try uninstalling from there.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.