macOS 10.14 Mojave on Unsupported Macs Thread

Larsvonhier · Jan 5, 2019

Yojx21 said:
Thanks for that test ! I was looking to buy a 2008 MB just to see where i can get with
So that mean that there is maybe a thing to do on that machine !

All hints duly noted about how slow this machine is without (or even with) accelerated graphics output. Still an interesting experiment - and still way better than some virtualisation attempts that some folks run.

I have now repaired the flex keyboard cable, so up to El Cap everything runs fine on the Macbook 4,1. ("Fine" meaning frame buffers for video memory and basic acceleration work, but of course not OpenGL. Makes it still a machine you could work on: I have prepared such a setup a while ago for a friend who works with M$ Office 2016 on it and wants to use modern browsers. No complaints from that side! Also: Nice to be able to sync the latest iOS gadgets vie iTunes on it. So I´d be glad to be spared about further warnings about how unfeasible Mojave would be on it. I want to experience it myself - is that not the spirit in especially this thread? ;-) )

As (High) Sierra USB does not work either, am I right that it would take the El Cap or Yosemite kexts to get it running under Mojave? Any chance that such old kexts would be usable? Any info on the dependencies of IOUSBFamily / IOPCIFamily / IONDRVSupport - or perhaps some more of the AppleUSB_ sorts?

mikethebook · Jan 5, 2019

Thanks for your replies but I'm technically challenged and a lot of long words throw me

Am I right in thinking then that, having installed Mojave with dosdude1's Patcher Tool including the Post Install installation of patches, the APFS ROM Patcher would allow future Mojave updates to be installed without need for manually updating the patches? Is this correct?
I also don't understand what it means to brick the machine. Presumably it is some sort of freezing. If that were to happen when attempting to install the APFS ROM Patcher, does that preclude erasing the disk and using Carbon Copy Cloner to reinstall the clone made before a Mojave install was attempted? That would be my way back if I didn't like the install of Mojave but would it still work if the machine was bricked?

Larsvonhier · Jan 5, 2019

jackluke said:
I had a similar issue and fixed through another mac laptop using the T key target disk mode through Firewire cable, you have to inject inside your installing path /System/Library/Prelinkedkernel/ a "patched prelinkedkernel" with embedded in the IOUSB legacy kexts, then you will able to use any BT input devices, except keyboard/mouse with broken flex cable, of course.

Good hint, thank you! At which point of the process is this done? Right now, I´ve done a fresh install and end up at the configuration screen of Mojave, unable to move mouse or input anything - which was predictable.
[doublepost=1546680788][/doublepost]

mikethebook said:
Thanks for your replies but I'm technically challenged and a lot of long words throw me Am I right in thinking then that, having installed Mojave with dosdude1's Patcher Tool including the Post Install installation of patches, the APFS ROM Patcher would allow future Mojave updates to be installed without need for manually updating the patches? Is this correct?
I also don't understand what it means to brick the machine. Presumably it is some sort of freezing. If that were to happen when attempting to install the APFS ROM Patcher, does that preclude erasing the disk and using Carbon Copy Cloner to reinstall the clone made before a Mojave install was attempted? That would be my way back if I didn't like the install of Mojave but would it still work if the machine was bricked?

You can decide any time to either install Mojave on a APFS partitioned drive or convert your HFS+ volume to APFS later on. On older machines, you will not be able to boot APFS volumes "out of the box". Here the software/hardware patches come into play. The riskless way is to apply the post-install software patch for APFS. This means you´ll see some text output in the pre-phase of the boot process. Just a bit weird but ok to live with.
The other way would be to run the APFS ROM patcher and if done right, this spares you the cosmetically ugly text output and makes your machine fit for booting APFS out of the box. Note: The ROM patch cannot be undone by re-formatting your drive or anything - its a mod of your mainboard. Done wrong it means you have to actually repair your machine by soldering/desoldering the chip.
Downside of just staying with HFS+ is that you´ll never get updates (of the OS, not the Apps!) automatically.

mikethebook · Jan 5, 2019

Thanks, Larsvonhier. That kicks the APFS ROM patcher into touch for me!! I'm currently running Sierra on a late 2009 Mac Mini but with an SSD drive. I presume I don't get a choice as regards APFS or HFS+. I presume that installing Mojave over Sierra using dosdude1's Patcher Tool will involve converting the drive to APFS automatically. Am I correct?

Larsvonhier · Jan 5, 2019

mikethebook said:
Thanks, Larsvonhier. That kicks the APFS ROM patcher into touch for me!! I'm currently running Sierra on a late 2009 Mac Mini but with an SSD drive. I presume I don't get a choice as regards APFS or HFS+. I presume that installing Mojave over Sierra using dosdude1's Patcher Tool will involve converting the drive to APFS automatically. Am I correct?

On the contrary: You always have the choice on HFS+ vs APFS, that did not change since (High)Sierra.
The patcher tool(s) do not convert HFS+ to APFS, you´ll either have to install a fresh copy of Mojave on your APFS-initialized volume or use the conversion feature in the Apple installer (or recovery volume, if booted later into it) to do that separately...

mikethebook · Jan 5, 2019

Thanks very much.

qura12 · Jan 5, 2019

I solved problem by converting to APFS. I booted from pendrive with 10.14.1 made by dosdue1's tool and I converted partition in Disk Utility. After restart macOS didn't boot even after I applied post patch. I needed to reinstall system from pendrive and apply post patch again. After that system booted and downloaded 10.14.2 update. The only problem is that I don't have Apple logo while booting. It looks like on the picture. Before that there is some fast scrolling text I couldn't take on a photo.

jackluke · Jan 5, 2019

Larsvonhier said:
Good hint, thank you! At which point of the process is this done? Right now, I´ve done a fresh install and end up at the configuration screen of Mojave, unable to move mouse or input anything - which was predictable.
[doublepost=1546680788][/doublepost]

Well, I used the T key at power-on (only works for macs with at least a Firewire port inside or a Thunderbolt adapter to Firewire) cause I was on an iMac and was unable to boot with option-alt key so unable to load startup manager and since it was an iMac to me is very boring and a bit difficult to disassembly the internal hdd, so holding T key I was able to boot the iMac internal hdd from another macbook and from there I replaced the prelinkedkernel file fixing the usb input devices.

Since you're on a laptop it's simpler cause you can easily unplug it an mount externally through usb adapter into another mac, so you don't need the T key, you should try to find your right prelinkedkernel file, for example the dosdude1's one on its Mojave Patcher I would say is almost universal for all the machines, otherwise you should try to use your latest working IOUSB***.kext (they are five) on your current El Capitan and rebuild a kernelcache with those on your MB4,1 hdd, in few words you have to:

- Replace all the 5 IOUSB***.kext from your "El Capitan" to your Mojave /S/L/E/
- chmod/chown your Mojave /S/L/E/
- and rebuild kextcache aka the prelinkedkernel tipically done through sudo commandline: kextcache -i /

Austinxs12 · Jan 5, 2019

Hi dosdude1,
I did upgrade to Mojave every thing seams to be working fine except for vlc,
I can’t play any video, the screen gets glitching black and the canvas resizes in a frenetic manner, however, I can hear audio.
Quicktime plays mp4 videos normally.
What can I do to fix this issue?

Mac Pro (Mid 2010)
graphics:ATI Radeon HD 5770 1024 MB

Regards,

dosdude1 said:
View attachment 797301 View attachment 797302 View attachment 797303 View attachment 797304
View attachment 797317 View attachment 797306 View attachment 797308 View attachment 797311

Current Hardware Support Status:

Machine Support

Early-2008 or newer Mac Pro, iMac, or MacBook Pro:

MacPro3,1

MacPro4,1

iMac8,1

iMac9,1

iMac10,x

iMac11,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)

iMac12,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)

MacBookPro4,1

MacBookPro5,x

MacBookPro6,x

MacBookPro7,1

MacBookPro8,x

Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:

MacBookAir2,1

MacBookAir3,x

MacBookAir4,x

MacBook5,1

Early-2009 or newer Mac Mini or white MacBook:

Macmini3,1

Macmini4,1

Macmini5,x

MacBook5,2

MacBook6,1

MacBook7,1

Early-2008 or newer Xserve:

Xserve2,1

Xserve3,1

Video Card Support

Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)

Pre-Metal Nvidia video cards (GeForce 5xx series and older, i.e. 8600M(GT), 8800M(GT), 9400M, 9600M(GT), 320M)

Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)

Current Issues

Minor Issues

Graphics anomalies: Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transparency as some systems with pre-metal AMD graphics render the dock in dark gray).

Built-in iSight cameras: Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.

Trackpad (MacBook5,2 affected only). Trackpad multi-finger gestures on the MacBook5,2 not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.

Major Issues

AMD Radeon HD 5xxx/6xxx series GPU acceleration: Currently, it is not possible to get full graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series GPU. Mojave will be almost UNUSABLE without graphics acceleration. This includes the 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these machines, you'll need to disable the AMD GPU (This will work on MacBook Pro 8,2 and 8,3 systems ONLY. You CANNOT disable the AMD GPU in an iMac.) Weird colors will also be produced when running Mojave with one of these video cards installed/enabled. To disable the AMD GPU on a 2011 MacBook Pro 8,2 or 8,3, follow the guide found here.

App Store Crashing: Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround. Safari may also experience crashes with certain kinds of embedded videos.

Early-2008 Mac Pro (MacPro3,1) GPU support: When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-compatible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are Nvidia cards, which work perfectly fine.

Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running Mojave. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.

Current Issues by Hardware

Minor Issues

Graphics anomalies:

All machines

Built-in iSight camera:

All machines, hit or miss

Trackpad:

MacBook5,2

Major Issues

AMD GPU acceleration:

All machines with a Radeon HD 5xxx or 6xxx series GPUs (these systems will be almost unusable when running Mojave. More details are located in the Current Issues section above.)

App Store Crashing:

All machines with Radeon HD 4xxx series GPUs

AMD GPU support:

MacPro3,1

Unsupported WiFi modules:

All machines with Broadcom BCM4321 WiFi modules

Installation:
To install on your machine, you can download and run the macOS Mojave Patcher application, which will let you download a copy of the latest installer app from Apple and create a bootable installer drive for use on unsupported Macs. It contains all the patches necessary to achieve the hardware support listed above. The installation guide can be found here and an installation guide video here.

APFS ROM Patcher:
Warning: This tool could irreversibly brick your EFI chip. Please exercise caution with machines that have multiple EEPROM definitions. Relevant information can be found here and here. The APFS ROM patcher can be found here. Use the password apfs to decrypt the ZIP.

Mojave Builds and Installer Versions (Developer Preview, Public Beta):

2018/06/04 - 2018/09/12 10.14.0 DP1 - DP11, PB1 - PB10

2018/06/04 DP1, build 18A293u, installer 14.0.08
2018/06/19 DP2, build 18A314h, installer 14.0.11
2018/06/26 PB1, build 18A314k, installer 14.0.11
2018/07/03 DP3, build 18A326g, installer 14.0.12
2018/07/06 PB2, build 18A326h, installer 14.0.12
2018/07/16 DP4, 2018/07/17 PB3, build 18A336e, installer 14.0.14
2018/07/30 DP5, 2018/07/31 PB4, build 18A347e, installer 14.0.15
2018/08/06 DP6, 2018/08/06 PB5, build 18A353d, installer 14.0.16
2018/08/13 DP7, 2018/08/13 PB6, build 18A365a, installer 14.0.17
2018/08/20 DP8, 2018/08/20 PB7, build 18A371a, installer 14.0.18
2018/08/27 DP9, 2018/08/27 PB8, build 18A377a, installer 14.0.20
2018/09/04 DP10, 2018/09/04 PB9, build 18A384a, installer 14.0.21
2018/09/12 DP11, 2018/09/12 PB10, build 18A389, installer 14.0.21
2018/09/24 10.14.0 Final, build 18A391, installer 14.0.22
2018/09/25 - 2018/10/23 10.14.1 DP1 - DP5, PB1 - PB5

2018/09/25 10.14.1 DP1, 2018/09/27 PB1, build 18B45d
2018/10/02 10.14.1 DP2, 2018/10/02 PB2, build 18B50c
2018/10/08 10.14.1 DP3, 2018/10/08 PB3, build 18B57c
2018/10/17 10.14.1 DP4, 2018/10/17 PB4, build 18B67a
2018/10/23 10.14.1 DP5, 2018/10/23 PB5, build 18B73a
2018/09/25 - 2018/10/23 10.14.1 Beta Installation Issues
2018/10/30 10.14.1 Final, build 18B75, installer 14.1.0
2018/10/31 - 2018/11/28 10.14.2 DP1 - DP4, PB1 - PB4

2018/10/31 10.14.2 DP1, 2018/11/02 PB1, build 18C31g
2018/11/07 10.14.2 DP2, 2018/11/07 PB2, build 18C38b
2018/11/16 10.14.2 DP3, 2018/11/16 PB3, build 18C48a
2018/11/28 10.14.2 DP4, 2018/11/28 PB4, build 18C52a
2018/12/05 10.14.2 Final, build 18C54, installer 14.2.2
2018/12/10 - 2018/12/19 10.14.3 DP1 - DP2, PB1

2018/12/10 10.14.3 DP1, 2018/12/11 PB1 build 18D21c
2018/12/19 10.14.3 DP2, build 18D32a

Credits:
@dosdude1 - Developed macOS Mojave Patcher.
@parrotgeek1 - Developed LegacyUSBInjector, SIPManager, and NDRVShim. (Source Code)
@Czo - Developed SUVMMFaker. (Source Code)
@Badruzeus - Discovered that Sierra OpenGL drivers work in Mojave.
@ASentientBot - Fixed Nvidia kernel panic, Core 2 Duo kernel panic, and iSight.
@jackluke - Narrowed down cause of Core 2 Duo kernel panic.

Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.

jhowarth · Jan 5, 2019

qura12 said:
I solved problem by converting to APFS. I booted from pendrive with 10.14.1 made by dosdue1's tool and I converted partition in Disk Utility. After restart macOS didn't boot even after I applied post patch. I needed to reinstall system from pendrive and apply post patch again. After that system booted and downloaded 10.14.2 update. The only problem is that I don't have Apple logo while booting. It looks like on the picture. Before that there is some fast scrolling text I couldn't take on a photo.

That is because, without modifying your boot rom code with the APFS ROM Patcher application, an efi booter kludge, the post install APFS Patch, has to be used in order for the system to recognize and use the APFS boot volume.

Flacko · Jan 5, 2019

Austinxs12 said:
Hi dosdude1,
I did upgrade to Mojave every thing seams to be working fine except for vlc,
I can’t play any video, the screen gets glitching black and the canvas resizes in a frenetic manner, however, I can hear audio.
Quicktime plays mp4 videos normally.
What can I do to fix this issue?

Mac Pro (Mid 2010)
graphics:ATI Radeon HD 5770 1024 MB

Regards,

Your Mac Pro should be able to support Mojave’s natively. Have a look at the link to apple support:

https://support.apple.com/en-gb/HT208898#cards

Your problem is with the graphics card. The HD 5770 is not listed by apple as a supported card for the Mac Pro 2010 and Mojave.

Tanith · Jan 5, 2019

Tanith said:
Hello,

I tried to upgrade my Macmini3,1 from High Sierra and HFS+ file system to

Mojave and APFS file system with dosdude1's macOS Mojave Patcher and now I cannot boot Mojave.

Before I started the upgrade-process from High Sierra to Mojave I converted the HFS+ file system to APFS file system with the Installers Disk Utility. The upgrade to Mojave seemed to be successful and also the macOS Post Install seemed to be successful. But now the APFS volume is not recognized during the boot up. It looks like the APFS-Patch from the macOS Post Install was not installed. I already checked the EFI-partition and no files where touched there.
I already did rebuilt the cache with macOS Post Install.

Are there any ways to install the APFS Patch after the upgrade to Mojave? I can access the internal APFS-volume and EFI-volume via a clean Mojave-installation from an external drive.
I already try to erase the EFI-volume and moved all the (visible and invisible) files from the Mojave-Update-installation to a backup-folder on the same partition so that I can try a clean Mojave-installation on that partion. But even with a new clean Mojave-installation no APFS-Patch seemed to be installed.
Unfortunately I cannot format this internal APFS-volume and create a new APFS-volume with the Installers Disk Utility because I cannot backup my files from that volume.

Hope you can help me.

I solved the problem by myself: I copied the files from the EFI volume of the external clean Mojave installation to the empty EFI volume of the internal clean Mojave installtion. System is now booting correcty and the APFS-Patch worked. Great job, dosdude1!

avz · Jan 5, 2019

I am not sure if it is Mojave on unsupported Macs related but when I am using my MacBook5,1 with an external monitor in a clam shell mode, the internal monitor seems to stay on(Apple Logo stays lit unless I turn the brightness all the way down). In About this Mac under Displays it shows both Internal and External Displays, I was under the impression that it only suppose to show the external display in a clam shell mode. It would be great to dedicate all of the GPU to the external monitor only. Any ideas?

P.S. Today I finally replaced the thermal compound after going strong for 10 years with and original compound out of the box.

schwab · Jan 5, 2019

Thank you again, DosDude.

I just installed Mojave on yet another unsupported Mac in our household.

iMac 12,1 21.5" mid2011

Because it has an OEM AMD RadeonHD 6750M 512MB Graphics Card post-install there was a strange blue hue/color even to the sand dunes(ie absence of red) to the LCD screen that I could not work-a-round UNTIL.....

I used ResXtreme to decrease from a 10 to an 8 bit profile and all colors are now restored to normal/standard.

The Geekbench results = single core score of 3224 and multicore score is 8123 with 20GB of RAM

Thanks DosDude and all forum members for keeping this thread active & vital!

MTBnBeer · Jan 5, 2019

Flacko said:
Your Mac Pro should be able to support Mojave’s natively. Have a look at the link to apple support:

https://support.apple.com/en-gb/HT208898#cards

Your problem is with the graphics card. The HD 5770 is not listed by apple as a supported card for the Mac Pro 2010 and Mojave.

We installed Mojave on an older 2009 MacPro4,1 (flashed to 5,1) with 32gb RAM and 1TB Samsung 860 Pro SSD on Apricon Duo PCIe card by replacing our original non-Metal video card with the exact MSI Gaming Radeon RX 560 128-bit 4GB GDRR5 video card on Apple's list above. Works perfectly running dual 24" Samsung Syncmaster displays at 1920 x 1200 (WUXGA - Widescreen Ultra eXtended Graphics Array) in Extended Desktop mode. RX560 doesn't need additional power cable(s) to the video card and runs cooler than the RX580 and other high performance dual fan cards which we don't need.

No DosDude1 Mojave Patcher required on our Mac Pro... unlike the 17" Early 2008 MacBook Pro 5,1 which DID need Mojave Patcher to upgrade to Mojave.
[doublepost=1546731034][/doublepost]Mojave running beautifully on our 17" Early 2008 MacBook Pro A1261 (MacBookPro4,1)... but wondering if my "vintage" Meritline Merax Dual Port eSATA ExpressCard/34 Cardbus Adapter (Silicon Express SI3132 Express Card) will run in Mojave? It was running in Sierra by installing the Silicon Express SI3132 Express Card drivers into Sierra and rebooting... but not sure if it will work in Mojave.

Any ideas?

I use the eSATA ExpressCard/34 card for Time Machine and SuperDuper! backups since I believe it ran significantly faster than the MacBook Pro's USB 2.0 ports... and FireWire hard drive enclosures were so expensive.

dosdude1 · Jan 5, 2019

avz said:
I am not sure if it is Mojave on unsupported Macs related but when I am using my MacBook5,1 with an external monitor in a clam shell mode, the internal monitor seems to stay on(Apple Logo stays lit unless I turn the brightness all the way down). In About this Mac under Displays it shows both Internal and External Displays, I was under the impression that it only suppose to show the external display in a clam shell mode. It would be great to dedicate all of the GPU to the external monitor only. Any ideas?

P.S. Today I finally replaced the thermal compound after going strong for 10 years with and original compound out of the box.

Yeah, it seems the legacy graphics hardware has weird issues with external displays/clamshell mode under Mojave... Unfortunately there's really nothing that can be done about that.

On a different note, as a MacBook5,1 owner, I think you'll find my latest endeavor quite interesting... I upgraded the CPU on a MacBook5,1 to a 3.06 GHz Core 2 Duo T9900, the absolute fastest CPU that board can support! You can see the process in my video here:

avz · Jan 6, 2019

dosdude1 said:
Yeah, it seems the legacy graphics hardware has weird issues with external displays/clamshell mode under Mojave... Unfortunately there's really nothing that can be done about that.

On a different note, as a MacBook5,1 owner, I think you'll find my latest endeavor quite interesting... I upgraded the CPU on a MacBook5,1 to a 3.06 GHz Core 2 Duo T9900, the absolute fastest CPU that board can support! You can see the process in my video here:

This is great news! Can't wait for the Hrutkay Mods review video. Interesting to see how well the original cooling system keeps up.

Kent W · Jan 6, 2019

schwab said:
Thank you again, DosDude.

I just installed Mojave on yet another unsupported Mac in our household.

iMac 12,1 21.5" mid2011

Because it has an OEM AMD RadeonHD 6750M 512MB Graphics Card post-install there was a strange blue hue/color even to the sand dunes(ie absence of red) to the LCD screen that I could not work-a-round UNTIL.....

I used ResXtreme to decrease from a 10 to an 8 bit profile and all colors are now restored to normal/standard.

The Geekbench results = single core score of 3224 and multicore score is 8123 with 20GB of RAM

Thanks DosDude and all forum members for keeping this thread active & vital!

How about the missing graphics acceleration?

I have avoided to upgrade my mid 2011 iMac 27 due to that.

Cheers

mikethebook · Jan 6, 2019

Larsvonhier said:
On the contrary: You always have the choice on HFS+ vs APFS, that did not change since (High)Sierra.
The patcher tool(s) do not convert HFS+ to APFS, you´ll either have to install a fresh copy of Mojave on your APFS-initialized volume or use the conversion feature in the Apple installer (or recovery volume, if booted later into it) to do that separately...

Still confused over the choice I have. even after watching a video by Dosdude1. I'm running Sierra on an SSD drive with HFS+. To upgrade to Mojave without a clean install, do I still have a choice of format? You mention a conversion feature in the Apple installer. Can you explain that please? And am I right in thinking that sticking with HFS+ I would have the funny boot and Mojave updates would require additional patches. But if I moved to APFS (if that's possible), booting would be normal and so would updates. I'm sure I have this wrong. Dosdude didn't cover the use of an SSD drive nor of converting to APFS. Thanks.

qura12 · Jan 6, 2019

@mikethebook, You're right there is still choice and the better way is to convert to APFS because of updates. I converted to APFS when I was on Mojave already but I think there is no difference. Just use Dosdude1's tool to make pendrive with 10.14.1, before starting installation use Disk Utility to convert partition and then install Mojave according to Dosdude1's tutorial.

jhowarth · Jan 6, 2019

mikethebook said:
Still confused over the choice I have. even after watching a video by Dosdude1. I'm running Sierra on an SSD drive with HFS+. To upgrade to Mojave without a clean install, do I still have a choice of format? You mention a conversion feature in the Apple installer. Can you explain that please? And am I right in thinking that sticking with HFS+ I would have the funny boot and Mojave updates would require additional patches. But if I moved to APFS (if that's possible), booting would be normal and so would updates. I'm sure I have this wrong. Dosdude didn't cover the use of an SSD drive nor of converting to APFS. Thanks.

The patched installer doesn't automatically convert the target volume to APFS unlike the stock installer on a supported machine. You can do this prior to or after the installation by booting from the patched installer USB stick and selecting the Convert to APFS... menu option in the Disk Utility application. However, if you want the same disk layout that the installer produces on a supported machine, you need to clone your volume to an external, repartition the disk as APFS and do a install with migration from the cloned volume. That is the only approach that produces the single container with all partitions within it...

/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +249.8 GB disk4
Physical Store disk0s2
1: APFS Volume Macintosh SSD 128.0 GB disk4s1
2: APFS Volume Preboot 43.1 MB disk4s2
3: APFS Volume Recovery 514.0 MB disk4s3
4: APFS Volume VM 20.5 KB disk4s4

Apple's installer on supported machines does some additional tricks beyond simple conversion that probably involves deletion of partitions and their recreation within the container.

antony34 · Jan 6, 2019

jhowarth said:
The patched installer doesn't automatically convert the target volume to APFS unlike the stock installer on a supported machine. You can do this prior to or after the installation by booting from the patched installer USB stick and selecting the Convert to APFS... menu option in the Disk Utility application. However, if you want the same disk layout that the installer produces on a supported machine, you need to clone your volume to an external, repartition the disk as APFS and do a install with migration from the cloned volume. That is the only approach that produces the single container with all partitions within it...

/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +249.8 GB disk4
Physical Store disk0s2
1: APFS Volume Macintosh SSD 128.0 GB disk4s1
2: APFS Volume Preboot 43.1 MB disk4s2
3: APFS Volume Recovery 514.0 MB disk4s3
4: APFS Volume VM 20.5 KB disk4s4

Apple's installer on supported machines does some additional tricks beyond simple conversion that probably involves deletion of partitions and their recreation within the container.

is it iMac 2009 also need to do this process? or just non supported machine need to do?

mikethebook · Jan 6, 2019

Thanks, guys! I think I may stick with HFS+ as dosdude1 did on his video. It's obviously simpler, opens up with a normal boot and there shouldn't be any issues with Time Machine. Installation of updates is the only downside but additional patches should sort any problems out. jhowarth, what you're talking about is just too complex for me. What would the disk layout look like without the adjustments you suggest? I confess I'm not particularly bothered what the layout looks like . . . I don't think.

Converting to APFS doesn't necessarily require use of the APFS ROM patch does it? That seems to cause so many issues and be risky. I'm presuming that's a separate patch.

jhowarth · Jan 6, 2019

mikethebook said:
Thanks, guys! I think I may stick with HFS+ as dosdude1 did on his video. It's obviously simpler, opens up with a normal boot and there shouldn't be any issues with Time Machine. Installation of updates is the only downside but additional patches should sort any problems out. jhowarth, what you're talking about is just too complex for me. What would the disk layout look like without the adjustments you suggest? I confess I'm not particularly bothered what the layout looks like . . . I don't think.

Converting to APFS doesn't necessarily require use of the APFS ROM patch does it? That seems to cause so many issues and be risky. I'm presuming that's a separate patch.

No, you don't need to use the APFS ROM Patcher to change your boot rom in order to use APFS for your boot volume. However, you will be stuck with the verbose text boot on APFS volumes if you go the route of using the post install APFS Patch instead from within Mojave Patcher.
[doublepost=1546787602][/doublepost]

antony34 said:
is it iMac 2009 also need to do this process? or just non supported machine need to do?

If you have a late 2009 iMac, you should be able to install High Sierra as a supported machine and let the stock Apple installer do the APFS conversion which will produce the fully populated container.

bplein · Jan 6, 2019

When attempting to create a USB thumb drive based on http://dosdude1.com/mojave/ , I get the following error:

-----
Edited later: This was running on a Mojave based system (not the target that I want to use the installer on).

I'm retrying with an old MBA running High Sierra and it's getting further along.

macOS 10.14 Mojave on Unsupported Macs Thread

macrumors 68000

macrumors regular

macrumors 68000

macrumors regular

macrumors 68000

macrumors regular

macrumors newbie

Attachments

macrumors 68040

macrumors newbie

macrumors 65816

macrumors 6502

macrumors newbie

macrumors 68000

macrumors member

macrumors regular

macrumors 68030

macrumors 68000

macrumors member

macrumors regular

macrumors newbie

macrumors 65816

macrumors regular

macrumors regular

macrumors 65816

macrumors 6502a

Attachments

Our Staff