macOS 10.14 Mojave on Unsupported Macs Thread

[gotcoding24]

Would someone be able to help me with this? I noticed that it said apfs and unsported cpu somewhere in the verbose mode for some reason, which can’t run on here, not sure what happened there.
iMac 24” 2007, Intel T9300 CPU. Thanks!


This is the link to the video, since file was too large to upload here:
https://drive.google.com/file/d/1yyflKj437hy6ROHIDIFEyMqyOam6hF9e/view?usp=drivesdk

 

[roronl]

Sorry if this has been asked, this thread is long. I have 14.1 installed through patcher process. Can I install 14.2 through the system update? Last time it hung because I think it tried to to a firmware update.

Yes, you can update, 10.14.2 has no firmware update included. Just reaply the Night shift patch perhaps.

 

[Project Alice]

10.14.2 kernel panics my MacBook 5,2. Reinstalling as I type this. I will probably go back to HS on my MacBook if this doesn't work. I haven't had this many problems with an operating system since the last time I tried to use Windows ME lol.

 

[dosdude1]

10.14.2 kernel panics my MacBook 5,2. Reinstalling as I type this. I will probably go back to HS on my MacBook if this doesn't work. I haven't had this many problems with an operating system since the last time I tried to use Windows ME lol.

Did you re-apply post-install patches after installing the update? If not, a kernel panic is normal until you do so.
[doublepost=1545007127][/doublepost]

Thanks for the explanation. It looks the APFS ROM Patcher didn't worked (but I don't know how to verify this anyway.....) and I can live with the verbose pre-boot. Only 10 seconds more for booting, not a big deal......!!!!!!!!!

If your system BootROM supports APFS, then just set your startup disk using System Preferences to your macOS volume. Then, it'll boot without the EFI script.

 

[Project Alice]

Did you re-apply post-install patches after installing the update? If not, a kernel panic is normal until you do so.

Yes, of course. I did that twice. Then I reinstalled, and ran the patcher again and it still panic'd.
Under a verbose boot I can't tell why because it reboots too fast for me to see the panic.

I'm currently making a HS patcher USB. It isn't just this, on 10.14 GM and 10.14.1, I had constant WindowServer crashes that forced me back to the login screen. And now I can't even boot into to 10.14.2. Idk if that has anything to do with the Mac, or just a buggy OS. I don't use this laptop everyday, which is why I even opted to test mojave out on it at all. But, I would like it to be somewhat useable lol. I'll probably try mojave on my 3,1 MacPro later when/if we get nvidia web drivers.

 

[OGNerd]

10.14.2 kernel panics my MacBook 5,2. Reinstalling as I type this. I will probably go back to HS on my MacBook if this doesn't work. I haven't had this many problems with an operating system since the last time I tried to use Windows ME lol.

Fresh install to external APFS formatted SSD using @dosdude1's v.1.2.3 Mojave Patcher to download the Mojave Installation app, create a USB boot stick, install the OS, and apply the post-install patches (including software APFS patch). I then re-installed the Nightshift patch via the Patch Updater.

 

[jbarley]

Fresh install to external APFS formatted SSD using @dosdude1's v.1.2.3 Mojave Patcher to download the Mojave Installation app, create a USB boot stick, install the OS, and apply the post-install patches (including software APFS patch). I then re-installed the Nightshift patch via the Patch Updater.


View attachment 811245

Nice to hear a success story for a change...

 

[Blackriton]

Did you re-apply post-install patches after installing the update? If not, a kernel panic is normal until you do so.
[doublepost=1545007127][/doublepost]
If your system BootROM supports APFS, then just set your startup disk using System Preferences to your macOS volume. Then, it'll boot without the EFI script.

Thanks Dosdude, I have done that but EFI Script still preceding normal boot. No way to get rid of the EFI script I suppose ?????????

 

[bmue5]

Just want to tell you that I updated a Mac Pro 3.1 from 10.14.0 to 10.14.2 without any hassles. The old Pro was pimped with a Geoforce GTX 680 and a Broadcom BCM94360 card as well as a Rocketek Bluetooth 4.0 stick

 

[Project Alice]

Just want to tell you that I updated a Mac Pro 3.1 from 10.14.0 to 10.14.2 without any hassles. The old Pro was pimped with a Geoforce GTX 680 and a Broadcom BCM43xx card.

My 3,1 Mac Pro has a GTX 1060, so I need the web drivers.
[doublepost=1545038029][/doublepost]

Fresh install to external APFS formatted SSD using @dosdude1's v.1.2.3 Mojave Patcher to download the Mojave Installation app, create a USB boot stick, install the OS, and apply the post-install patches (including software APFS patch). I then re-installed the Nightshift patch via the Patch Updater.


View attachment 811245

Are you thinking it will work better if I format with APFS? I am not using an SSD so I stayed HFS+.

 

[LarryJoe33]

I installed the update through system update. It booted fine but I had no sound. I applied the patches through the updated which I think is outdated. Reboot and hang at full bar of boot screen.

Any ideas? Going to restore to 14.1 and start over.

 

[skiabox]

Hello guys!
I did a 10.14.1 clean installation (macbook pro 2010 17 inch) some time ago using dosdude1.com site and it worked flawlessly!
How can I update to 10.14.2?
Is it safe to do it since it is not a clean install any more and I have some programs already installed?
Thank you very much!!!

 

[jhowarth]

I agree, my Mac Pro 3.1 was quite happy with the apfs patch and the verbose startup did not bother me either. However, I thought I would risk the apfs ROM patch and it was fine. You can check the ROM version you have: Open System Information (click on apple top left and select "About this Mac"). Then overview>System report. In the hardware section it will show you the ROM details. My 3.1 gives:

Boot ROM Version: MP31.006C.B05

SMC Version (system): 1.25f4

However, I suspect these may not have changed after using the APFS ROM tool but I did not record the before and after. Dosdude1 or someone may be able to help here. If you have a successful ROM update then to remove the verbose output you will need to mount the efi drive. To find which one it is use:

sudo diskutil list

This will display your drives and you can identify the efi partition. In my case it is disk0s1. Then mount this partition:

sudo diskutil mount disk0s1

After a moment the efi drive should appear on your desktop. You can then use finder to delete the following: apfs.efi, /BOOT/BOOTX64.EFI and startup.nsh. Restart and the verbose startup should have gone. Only do this if you have a apfs ROM. If you like to experiment then doing this without a suitable ROM will result in the Mac not starting up. You should be able to reboot using the installer USB and reapply the apfs patch. However, this is at your own risk but would show you if you have an apfs ROM or not. I suspect you do not.

Did you throw away the backup and APFS bin files that the APFS ROM Patcher saves? On my MacPro 3,1, both files are of identical size but have differing check sums. You should be able to tell if the APFS ROM patch took by using the option key boot selector which will now show the APFS volume as well as Boot EFI copy (a minor glitch in the current implementation of the ROM patching).

-rw-rw-r-- 1 howarthjw howarthjw 2097152 Aug 30 17:02 MacPro3,1_APFS.bin
-rw-rw-r-- 1 howarthjw howarthjw 2097152 Aug 30 17:02 MacPro3,1_backup.bin

$ md5sum MacPro3,1_backup.bin
5c4db63cd46e4bad8c7aedeff74ded84 MacPro3,1_backup.bin
$ md5sum MacPro3,1_APFS.bin
e27e37ab39f8e31323b397ebc73c422f MacPro3,1_APFS.bin

Note that the APFS ROM patching doesn't change the reported boot ROM version string.

 

[Frodotg]

It's keeping all you're data intact. Converting will take just a minute and is save.

But, it's necessary to reinstall the os??? Or you can only convert the drive??

Thanks!!!

 

[roronl]

But, it's necessary to reinstall the os??? Or you can only convert the drive??

Thanks!!!

No and yes

 

[macinfo]

For all with MacBookPro4,1 (Early 2008) and maybe others…

After a restart with Mojave or High Sierra, the keyboard backlight is always turned on, System Prefs will always be reset, as to having no effect at all. After searching around a bit, I now have found a workaround fix with the tool 'Lab Tick', which puts an Item in the Menu Bar, with it’s Slider or Prefs Menu the keyboard backlight can be set to one’s liking.

The option "Prevent Mac OS X from autom…" can be turned off, as it takes some CPU cycles.

Now I have my keyboard backlight turned on as always after a reboot, but after the login screen vanishes, the backlight is softly turned back to zero – for a somehow nice feeling. ;-)

 

[Frodotg]

No and yes

I converted the drive but it wasn't possible to boot the os and it was necessary to reinstall the whole os.

It's normal to see "conteiner disk2" inside the ssd drive and inside the os dive???

Thank you for your help!!!

 

[K two]

Just wanted to say THANK YOU to all the responsible developers.
I just upgrade my 27" 2009 iMac to Mojave and it's running great. Everything is working as far as I can tell. With a new SSD drive and now Mojave, this old computer feels just as fast and capable as the new ones I see at the Apple store. Thank you, thank you, thank you!!!

Now, I have another newer iMac from 2010, can somebody explain to a newbie like me why the older and slower GPU in the 2009 iMac works with Mojave, but the newer and faster GPUs in 2010/2011 iMacs don't work?

Depends on which 2010 iMac.

 

[skiabox]

I am downloading macosmojave using macOS Mojave Patcher.
Then I plan to follow steps 1-4 from dosdude1.com/mojave
Am I doing the right thing?
Is it too risky?
I have Mac OS Mojave 10.14.1 installed with a clean install method following dosdude1.com/mojave complete list of steps!
Thank you!

 

[indigotheory]

Hi all

Does the early 2011 17" Macbook Pro have a Broadcom BCM4321 WiFi module? Just checking I can definitely put Mojave on it before I go for one

Thanks

 

[Flacko]

Did you throw away the backup and APFS bin files that the APFS ROM Patcher saves? On my MacPro 3,1, both files are of identical size but have differing check sums. You should be able to tell if the APFS ROM patch took by using the option key boot selector which will now show the APFS volume as well as Boot EFI copy (a minor glitch in the current implementation of the ROM patching).

-rw-rw-r-- 1 howarthjw howarthjw 2097152 Aug 30 17:02 MacPro3,1_APFS.bin
-rw-rw-r-- 1 howarthjw howarthjw 2097152 Aug 30 17:02 MacPro3,1_backup.bin

$ md5sum MacPro3,1_backup.bin
5c4db63cd46e4bad8c7aedeff74ded84 MacPro3,1_backup.bin
$ md5sum MacPro3,1_APFS.bin
e27e37ab39f8e31323b397ebc73c422f MacPro3,1_APFS.bin

Note that the APFS ROM patching doesn't change the reported boot ROM version string.

Many thanks, I forgot I had the backup and APFS bin files. As you say, the file size is identical but the checksums are different. Mine are different to yours though. As I thought, the ROM patching does not change the reported ROM version. I am quite happy the APFS ROM patch worked for me and my MP3.1 is working very well with Mojave. It is Blackriton who is asking to how to remove the verbose APFS during start-up. However, I suspect he does not have the APFS ROM and is therefore stuck with the APFS patcher method and will have to put up with the verbose output during startup. Maybe you can suggest a method he can use to confirm whether or not he has the appropriate APFS ROM.

 

[Blackriton]

Many thanks, I forgot I had the backup and APFS bin files. As you say, the file size is identical but the checksums are different. Mine are different to yours though. As I thought, the ROM patching does not change the reported ROM version. I am quite happy the APFS ROM patch worked for me and my MP3.1 is working very well with Mojave. It is Blackriton who is asking to how to remove the verbose APFS during start-up. However, I suspect he does not have the APFS ROM and is therefore stuck with the APFS patcher method and will have to put up with the verbose output during startup. Maybe you can suggest a method he can use to confirm whether or not he has the appropriate APFS ROM.

I'm quite sure I don't have the APFS ROM as I don't got your two APFS.bin and backup files. When I tried to run Dosdude's ROM patcher, it failed with an error and Dosdude's recommendations were to don't run it a second time
to be safe of bricking the MacPro 3,1 !!! I can live with the verbose boot, its only a 10 second waste of time !!!!!!

 

[skiabox]

I completed the creation of the usb drive using MacOS Mojave Patcher Tool and the latest 10.14.2 mojave version downloaded using this tool.
Is it safe now to proceed with the final step 4 of dosdude1.com/mojave/ guide?
I am currently running mac os mojave 10.14.1 (clean install method).

 

[webg3]

I completed the creation of the usb drive using MacOS Mojave Patcher Tool and the latest 10.14.2 mojave version downloaded using this tool.
Is it safe now to proceed with the final step 4 of dosdude1.com/mojave/ guide?
I am currently running mac os mojave 10.14.1 (clean install method).

Yes, it is safe, since there were no errors in creating the USB stick.

 

[jhowarth]

Many thanks, I forgot I had the backup and APFS bin files. As you say, the file size is identical but the checksums are different. Mine are different to yours though. As I thought, the ROM patching does not change the reported ROM version. I am quite happy the APFS ROM patch worked for me and my MP3.1 is working very well with Mojave. It is Blackriton who is asking to how to remove the verbose APFS during start-up. However, I suspect he does not have the APFS ROM and is therefore stuck with the APFS patcher method and will have to put up with the verbose output during startup. Maybe you can suggest a method he can use to confirm whether or not he has the appropriate APFS ROM.

In my experience the APFS patches can be a bit sticky to totally purge out. In my case, after I had flashed the boot ROM, I had to resort to 'sudo gpt destroy' to start over with a clean partition map in order to remove all of the APFS patch changes.