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.
I created a new usb Mojave patcher with the added APFS patch and just like you it was gray out, so formatted my internal hdd to APFS then rebooted into the patcher and the APFS patch was not greyed out installed the latest beta applied the post install patches hit option on reboot and was presented with a EFI and recovery option the only HDD that appeared normal was my external hdd macOSUSB,EFI,recovery. Then name of my formatted internal hdd MacintoshHD is not appearing

Thanks for the reply.

I know I asked this question before (but never got a response back).
Is there an advantage of APFS ROM boot? My MBP5,3 currently has 3 partitions and it's working well.
  1. Internal SSD partition - High Sierra (patched using @dosdude1's HS Patch app.
  2. Internal SSD partition - Sierra - installed regularly as it is supported.
  3. External HDD partition - Mojave Beta (patched using @dosdude1's Mojave Patch app.
All 3 partitions are working well for me. Thus my question above - what the advantage is for having the APFS ROM capability?

Thank You.
 
Thanks for the reply.

I know I asked this question before (but never got a response back).
Is there an advantage of APFS ROM boot? My MBP5,3 currently has 3 partitions and it's working well.
  1. Internal SSD partition - High Sierra (patched using @dosdude1's HS Patch app.
  2. Internal SSD partition - Sierra - installed regularly as it is supported.
  3. External HDD partition - Mojave Beta (patched using @dosdude1's Mojave Patch app.
All 3 partitions are working well for me. Thus my question above - what the advantage is for having the APFS ROM capability?

Thank You.
APFS is designed to work best for ssd's but mostly it is going to be the requirement for Mojave if you want any updates otherwise you will have to create a new mohave patcher for any Mojave OS updates for example 14.0.1 to 14.0.2 with APFS you will be able to update normally
 
Yes, you will get full accelerated video on any Radeon HD 2xxx, 3xxx, or 4xxx series card with my patcher under Mojave.

For the Radeon HD 2600 XT, I should install the legacy video patch, correct? Initially, I didn't and noticed some minor tearing when I moved windows around (however it was much smoother than I would have expected from a really generic video driver). After installing the legacy video patch, the tearing disappeared but I got the dreaded grey menu bars in the bright mode.

Does the MacPro 3,1 require the legacy audio patch? I assumed that if it did that would be preselected.
 
  • Like
Reactions: TimothyR734
For the Radeon HD 2600 XT, I should install the legacy video patch, correct? Initially, I didn't and noticed some minor tearing when I moved windows around (however it was much smoother than I would have expected from a really generic video driver). After installing the legacy video patch, the tearing disappeared but I got the dreaded grey menu bars in the bright mode.

Does the MacPro 3,1 require the legacy audio patch? I assumed that if it did that would be preselected.
Grey menu bar in light mode happens on all legacy video cards with full acceleration. Yes, you do need the Legacy Video Card patch for the 2600XT, of course. The Mac Pro 3,1 does need the Legacy Audio Patch.
 
Grey menu bar in light mode happens on all legacy video cards with full acceleration. Yes, you do need the Legacy Video Card patch for the 2600XT, of course. The Mac Pro 3,1 does need the Legacy Audio Patch.

Thanks. Shouldn't the legacy audio patch be enabled on MacPro 3,1 by default then as the audio hardware is uniform?
 
  • Like
Reactions: TimothyR734
As the earliest adopter of APFS ROM PATCHER v2 on macpro 3.1, I can address some of your questions:

0) Have the same Boot ROM version - the patcher did not change that
1) In my experience, all ROM flashing was completed in one cycle. I then rebooted into HFS+ with no issues. Then rebooted using the patcher to reformat my boot disk as APFS before installing the new patched OS.
2) Haven't checked. Good question.
3) Didn't benchmark, but it seems a little zipper. Can't tell for sure if it's just new car smell...;)

Of course, @dosdude1 is the ultimate authority on all things APFS boot rom related. So make sure and double check with him. This is just my real-world experience. YMMV.

Good luck.
[doublepost=1535317625][/doublepost]
I know...just being a little lazy on a Sunday afternoon...Trying to avoid any unnecessary lifting ;).
Patching CoreDisplay and/or OpenGL so we can avoid application specific workarounds is tricky enough...

And of course, tomorrow is patch Monday! Some new surprises for sure...

One last APFS ROM Patcher v2 question... how long did the patching process take on your MacPro 3,1 from a SSD? Some folks are claiming it can be quite slow.
[doublepost=1535590810][/doublepost]Patched Mojave can be installed on a HFS volume instead of APFS, right? If so, is it correct to say that an HFS installation is limited in being unable to install future Software Updates but that application updates will still work?
 
  • Like
Reactions: TimothyR734
Up to 5 minutes to read and 10 minutes to write.

Once started DO NOT force quit. Wait until the finished message.

One last APFS ROM Patcher v2 question... how long did the patching process take on your MacPro 3,1 from a SSD? Some folks are claiming it can be quite slow.
[doublepost=1535590810][/doublepost]Patched Mojave can be installed on a HFS volume instead of APFS, right? If so, is it correct to say that an HFS installation is limited in being unable to install future Software Updates but that application updates will still work?
 
Up to 5 minutes to read and 10 minutes to write.

Once started DO NOT force quit. Wait until the finished message.

One other question... If I have a pre-existing APFS Mojave volume with the APFS patch installed, would I have to reformat and reinstall afresh or would a simple full reinstall of Mojave followed by patching without the APFS boot patch be sufficient to clear that out?
 
  • Like
Reactions: TimothyR734
One other question... If I have a pre-existing APFS Mojave volume with the APFS patch installed, would I have to reformat and reinstall afresh or would a simple full reinstall of Mojave followed by patching without the APFS boot patch be sufficient to clear that out?
All you'd need to do is set your Startup Disk to the APFS volume using System Preferences (after patching your BootROM of course). Optionally, you can mount the EFI System Partition of your hard disk and delete "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi.
 
Patched Mojave can be installed on a HFS volume instead of APFS, right? If so, is it correct to say that an HFS installation is limited in being unable to install future Software Updates but that application updates will still work?

Correct on both counts.
 
  • Like
Reactions: TimothyR734
I just got a Samsung 840 PRO SSD and will be updating to Mojave soon, an SSD is so fast, even on my mid 2010 MacBook Pro. So should APFS be GUID Partition Map?
 

Attachments

  • Screen Shot 2018-08-30 at 3.42.22 PM.png
    Screen Shot 2018-08-30 at 3.42.22 PM.png
    90.5 KB · Views: 254
I just got a Samsung 840 PRO SSD and will be updating to Mojave soon, an SSD is so fast, even on my mid 2010 MacBook Pro. So should APFS be GUID Partition Map?

GUID Partition Map is standard for any HDD/SSD. The one you would change is "Format". HFS+ file system is "Mac OS Extended (Journaled) and APFS is "APFS". Do not change the GUID Partition Map setting. To format your drive to APFS from an existing drive, boot into Recovery/Installer USB, open Disk Utility, and then unmount it. After unmounting, go to the top bar and select Edit>Convert to APFS. If you are doing a clean install and plan to convert it to APFS right away, then once erasing change the "Format" to APFS from Mac OS Extended (Journaled). Once converting to APFS, the only way to revert back to HFS+ is to erase the container (not the volume) and format it back to Mac OS Extended (Journaled).
[doublepost=1535601503][/doublepost]
Cool. There is no way to update an unsupported Mac to macOS Mojave in-line the operating system without booting off external media, is there? Like opening a macOS Mojave Installer in the /Applications folder.

You can create a small 10GB partition of your internal drive and use the patcher to turn the partition into the bootable installer if you don't have/want a flash drive to install it. Running the application from the unsupported machine will give you an error saying this macOS is not compatible with this Mac or something along those lines.
 
One last APFS ROM Patcher v2 question... how long did the patching process take on your MacPro 3,1 from a SSD? Some folks are claiming it can be quite slow.
[doublepost=1535590810][/doublepost]Patched Mojave can be installed on a HFS volume instead of APFS, right? If so, is it correct to say that an HFS installation is limited in being unable to install future Software Updates but that application updates will still work?
Caught this late but you were very well served.

Some brave soul should gather these into an APFS ROM PATCHER FAQ for the OP. I'm sure many are in the same quandary and newbies are overwhelmed by the amount of background reading necessary to grasp all of the complexities.
As GM, approaches system update questions will multiply and since we discovered that it is closely linked to APFS...Just sayin...
I would attempt it myself but am not the ultimate authority on the tool in question. Plus quite busy trying to figure out why Light mode doesn't work as well as Dark mode does on my laptop...(Arghh)

@dosdude1 and @parrotgeek1 - I just experimented with the Mojave proper IOAccelerator kexts versus the HS ones the patcher installs for my mbp 5.3. They seem to work just fine. Why is it necessary to swap the HS accelerator kexts back in? I'm trying to get to a bear minimum set of post-install kexts and these two seem unnecessary for my configuration (2 NVIDIA gpus) Am I missing something? Thanks.
 
Cool. There is no way to update an unsupported Mac to macOS Mojave in-line the operating system without booting off external media, is there? Like opening a macOS Mojave Installer in the /Applications folder.
You could use CCC & clone a drive that's already running Mojave, that IMHO would be the best way to go if you're looking to incorporate your files. Clone current system to your SSD I'm assuming that's what you're trying to do??
 
  • Like
Reactions: TimothyR734
I used the Mojave 1.2.0 patcher and reformatted my external usb hdd to APFS and install HS with HFS and see if I can boot into APFS that way

I used the 1.2.0 installer on my MBP 8,2 to format an external SSD to APFS, installed Mojave DP9 on the drive, and then applied the the appropriate post-install patches for my MB 5,2. Worked like a charm!
 
  • Like
Reactions: TimothyR734
I used the 1.2.0 installer on my MBP 8,2 to format an external SSD to APFS, installed Mojave DP9 on the drive, and then applied the the appropriate post-install patches for my MB 5,2. Worked like a charm!
I think you have to use the APFS Rom Patcher before you can apply the APFS patch in the post install as I tried High Sierra with just the post install patch internal hdd and Mojave with the APFS post install patch MacintoshHD and macOSUSB the names of my internal and external usb hdd does not appear in boot options just EFI and recovery for both hdd's and APFS doesn't appear in system preferences to elect a startup drive only start up drive
 
I think you have to use the APFS Rom Patcher before you can apply the APFS patch in the post install as I tried High Sierra with just the post install patch internal hdd and Mojave with the APFS post install patch MacintoshHD and macOSUSB the names of my internal and external usb hdd does not appear in boot options just EFI and recovery for both hdd's and APFS doesn't appear in system preferences to elect a startup drive only start up drive

I didn't want to risk bricking my trusty 5,2 with the boot ROM patcher, so I used the "APFS booting patch for machines with non-APFS compatible BootROMs" post-install patch that is now available in the v1.2.0 Patcher. I used the 8,2 to create the APFS volume because it has native support.
 
Hello everyone! eBay took long enough to send my motherboard out. But I’m back and fixed. I am not trying the Boot ROM patcher just yet. School just started and I really do need this laptop

I will give the APFS solution that was ported from the 10.13 patcher a try though. I couldn’t help notice I was made an example of twice in the original post though :^)

Is it me or is build 18A365a a bit laggy in the animations compared to previous builds?
 
  • Like
Reactions: TimothyR734
Since the Mojave installer had an installation problem with my Mac Pro 5,1 (2012) with the proper Metal GPU, with the initial beta, I had to use the famous dosdude1's great installer. The hard drive I'm using is a standard 7200 rpm hard drive. It's been formatted as HFS+ (Journaled). Dosdude1's installer worked great. The updates in System Preferences comes in well and the updates themselves are installed without problems.

Dosdude1, you're great.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.