macOS 10.14 Mojave on Unsupported Macs Thread

[MTBnBeer]

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

HMMM.... When I boot from my Mojave Patcher USB drive, launch it's Disk Utility, select my MacBook Pro's internal drive "Mac SSD" then "Edit" the :Convert to APFS" menu item is greyed out...

How do I resolve this so I can convert this SSD from Mac OS Extended (Journaled) to APFS?

Could I just create another partition on this internal SSD in APFS then use SuperDuper! to copy everything from the current Mac OS Extended (Journaled) partition to this new APFS partition?

 

[kinwin]

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?

 

[roronl]

HMMM.... When I boot from my Mojave Patcher USB drive, launch it's Disk Utility, select my MacBook Pro's internal drive "Mac SSD" then "Edit" the :Convert to APFS" menu item is greyed out...

How do I resolve this so I can convert this SSD from Mac OS Extended (Journaled) to APFS?

Could I just create another partition on this internal SSD in APFS then use SuperDuper! to copy everything from the current Mac OS Extended (Journaled) partition to this new APFS partition?

Just unmount it, (or Mount it if it's not, that's all)

 

[segfaultdotorg]

https://www.ifixit.com/Guide/MacBook+Air+13-Inch+Mid+2011+Battery+Replacement/6359

Worth a shot, ...No?

Thanks for the tip! It doesn't look that bad, I had completely forgotten this was before Apple started gluing batteries into place. I will probably wait until it gets worse before attempting it--it's still usable at 60% capacity.

 

[viktorbychkov]

Just boot from your USB stick or ext. drive again (containing the Mojave installer/patcher) and run the post-install patches again. Should get your Mojave running again.

Thank you for your help!
[doublepost=1544946053][/doublepost]

You wanna restore from a time machine backup? Try to boot into internet recovery (cmd + opt + r) you can restore your TM backup from there

does not work properly
cmd + opt + r = start to system
cmd + r = crossed out circle
_____
rescue advice from Larsvonhier
thank

 

[alpez]

I think I will give my macmini5,1 mojave with macOS Mojave Patcher

Or is it not worth the trouble/time ... ?

Anyone done it ?

Regards
Alexis

---
Bokföring och Lön för Mac
http://www.ct.se

 

[roronl]

I think I will give my macmini5,1 mojave with macOS Mojave Patcher

Or is it not worth the trouble/time ... ?

Anyone done it ?

Regards
Alexis

---
Bokföring och Lön för Mac
http://www.ct.se

When you place a SSD it will be worth the trouble/time

 

[alpez]

So true, booting high sierra wo an SSD was a pain

 

[Blackriton]

On my MacPro 3,1 with 10.14.2 patched successfully with Dosdude's patcher, I decided to convert the SSD from HFS+ to APFS.
I used the USB stick and Disk Utility on it to convert. It worked but before the boot on the SSD, I have now some verbose output running before and I just want to know if that is obligatory or there is a way to get rid of it ?????????

Many thanks in advance for help and ideas but its not very important anyway............

 

[IusAP]

Dear all,

i am new to this thread here. I am running an MBP 5,5 (mid 2009) with an internal SSD 850 EVO 250GB.
Formatted Journaled HFS+. I successfully installed Mojave 10.14 on this machine, Now I wants tp upgrade it to 14.10.2. I I therefore generated a new usb-drive with the latest version of the patcher and subsequently the (hopefully) latest version of the MacOS Mojave installer which is named in my app folder 14.0.22. After booting from the usb drive the boot process stops after the grey bar in the booting window is complete.

has anyone an idea?

I appreciate any help!
Thanx
IuSAP

 

[indigotheory]

Dear all,

i am new to this thread here. I am running an MBP 5,5 (mid 2009) with an internal SSD 850 EVO 250GB.
Formatted Journaled HFS+. I successfully installed Mojave 10.14 on this machine, Now I wants tp upgrade it to 14.10.2. I I therefore generated a new usb-drive with the latest version of the patcher and subsequently the (hopefully) latest version of the MacOS Mojave installer which is named in my app folder 14.0.22. After booting from the usb drive the boot process stops after the grey bar in the booting window is complete.

has anyone an idea?

I appreciate any help!
Thanx
IuSAP

No need to keep making usb installers. Install from system preferences - software update and reboot into the usb installer and apply the default patches for your machine and check force cache rebuild

 

[IusAP]

Thanks for your reply. the software preferences -software update pathway does not show the existance of a new macOS version. it says 10.14 is the latest.


Update: Solved. I generated an usb installer on a mojave native machine with latest patch version and latest masOS Mojave version and now it has worked.

 

[roronl]

On my MacPro 3,1 with 10.14.2 patched successfully with Dosdude's patcher, I decided to convert the SSD from HFS+ to APFS.
I used the USB stick and Disk Utility on it to convert. It worked but before the boot on the SSD, I have now some verbose output running before and I just want to know if that is obligatory or there is a way to get rid of it ?????????

Many thanks in advance for help and ideas but its not very important anyway............

After the conversion, you do not need the patch regarding the APFS. So uncheck this via the tool and reboot without verbose.

 

[Blackriton]

After the conversion, you do not need the patch regarding the APFS. So uncheck this via the tool and reboot without verbose.

If the APFS was wrongly checked is there a way to get rid of the verbose start effect ???????????? If I reapply the post-install patches without checking the APFS option; will it be enough to eliminate the verbose ?????? Thanks for the ideas and help.

 

[roronl]

If the APFS was wrongly checked is there a way to get rid of the verbose start effect ???????????? If I reapply the post-install patches without checking the APFS option; will it be enough to eliminate the verbose ?????? Thanks for the ideas and help.

Yes, reapply the post-install patches without checking the APFS option. (rebuild caches) and reboot.

 

[flygbuss]

Thank you for your help!
[doublepost=1544946053][/doublepost]

does not work properly
cmd + opt + r = start to system
cmd + r = crossed out circle
_____
rescue advice from Larsvonhier
thank

Oh I forgot to mention that you might need an internet connection. But I’m glad it worked with the usb Flash Drive

 

[Blackriton]

Yes, reapply the post-install patches without checking the APFS option. (rebuild caches) and reboot.

I reapply the post-install patches without checking APFS but the verbose is still before the boot.

Maybe its related to a fact : I tried several months before to apply Dosdude's APFS ROM Patcher. It fails to succeed with an error message but I still have in the User/Library/App Support this file here included. Does that mean the APFS ROM Patcher is active ??????? And when I boot to the USB Sticker, the MacOS installer lies with an EFIBoot option as alternative boot........... Is this a proof of the ROM Patcher effect ?????????

 

[MTBnBeer]

Just unmount it, (or Mount it if it's not, that's all)

Thanks !!! Unmounting my MBP's internal SSD was the trick to convert my MBP's internal SSD to APFS.

HOWEVER when I rebooted my MBP it wouldn't boot to the internal SSD (only the appears. 8-(

So I rebooted off the Mojave Patcher USB drive and re-ran the Mojave Patcher "Post Install" patches. Same bad result.

Booted off Mojave Patcher USB drive again and reinstalled Mojave again "over" the existing Mojave 10.14.1 system still on my SSD, reinstalled, re-ran the Mojave Patcher "Post Install" patches, and BINGO back in business.

Ran About This Mac: Software Update, got the 10.14.2 software update available, ran it, and not my 17" Early 2008 MacBook Pro is running the latest macOS...and software updates are just a click away! Only remaining issue is WiFi doesn't work which hopefully the newer Airport card off eBay arriving this week should fix.

THANKS EVERYONE FOR ALL YOUR HELP !!!

 

[jhowarth]

Thanks !!! Unmounting my MBP's internal SSD was the trick to convert my MBP's internal SSD to APFS.

HOWEVER when I rebooted my MBP it wouldn't boot to the internal SSD (only the appears. 8-(

So I rebooted off the Mojave Patcher USB drive and re-ran the Mojave Patcher "Post Install" patches. Same bad result.

Booted off Mojave Patcher USB drive again and reinstalled Mojave again "over" the existing Mojave 10.14.1 system still on my SSD, reinstalled, re-ran the Mojave Patcher "Post Install" patches, and BINGO back in business.

Ran About This Mac: Software Update, got the 10.14.2 software update available, ran it, and not my 17" Early 2008 MacBook Pro is running the latest macOS...and software updates are just a click away! Only remaining issue is WiFi doesn't work which hopefully the newer Airport card off eBay arriving this week should fix.

THANKS EVERYONE FOR ALL YOUR HELP !!!

Keep in mind that the conversion process doesn't produce the same partitioning scheme as the automatic conversion of HFS on a supported machine. That is, you will never end up with the boot volume, preboot volume, recovery volume and VM volume in a single container. The only way to get that configuration is to clone your drive to an external and then repartition the internal to a single APFS volume followed by installation with migration from the external.

/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +249.8 GB disk4
Physical Store disk1s2
1: APFS Volume Macintosh SSD 118.2 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

Note that the diskutil conversion only converts a single HFS volume to a single APFS volume and there are no options in diskutil for moving volumes between containers.

 

[Flacko]

I reapply the post-install patches without checking APFS but the verbose is still before the boot.

Maybe its related to a fact : I tried several months before to apply Dosdude's APFS ROM Patcher. It fails to succeed with an error message but I still have in the User/Library/App Support this file here included. Does that mean the APFS ROM Patcher is active ??????? And when I boot to the USB Sticker, the MacOS installer lies with an EFIBoot option as alternative boot........... Is this a proof of the ROM Patcher effect ?????????

If you do not have the boot rom for apfs you will have to use the post install patch for apfs. This will give you the verbose text you are seeing during startup. If your rom is updated for apfs then make sure the apfs patch is not ticked during patching. Selecting an apfs drive will automatically tick the box so untick it before you apply the patches. I suspect from what you have said that you do not have the rom updated for apfs so you will have to use the patch and get the verbose startup. Running the patcher again with the apfs unticked will not remove the apfs patch. The efi drives shown during the boot screen is normal for our patched machines and can be ignored. It does not mean you have a successful rom patch. If you have an apfs rom and have applied the apfs patch then the verbose startup can be removed (involves mounting a drive and deleting certain files) but I suspect that you need the apfs patch so do not need to do this unless you successfully update the rom.

 

[MTBnBeer]

Keep in mind that the conversion process doesn't produce the same partitioning scheme as the automatic conversion of HFS on a supported machine. That is, you will never end up with the boot volume, preboot volume, recovery volume and VM volume in a single container. The only way to get that configuration is to clone your drive to an external and then repartition the internal to a single APFS volume followed by installation with migration from the external.

/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +249.8 GB disk4
Physical Store disk1s2
1: APFS Volume Macintosh SSD 118.2 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

Note that the diskutil conversion only converts a single HFS volume to a single APFS volume and there are no options in diskutil for moving volumes between containers.

Great advice. I'll do that another day... Probably after installing the new $10 Apple Airport Express WiFi card hopefully arriving from China later this week (stuck in U.S. Customs for 8 days now).

Wish I had known that when I originally installed Mojave. Coulda Woulda Shoulda

 

[Blackriton]

If you do not have the boot rom for apfs you will have to use the post install patch for apfs. This will give you the verbose text you are seeing during startup. If your rom is updated for apfs then make sure the apfs patch is not ticked during patching. Selecting an apfs drive will automatically tick the box so untick it before you apply the patches. I suspect from what you have said that you do not have the rom updated for apfs so you will have to use the patch and get the verbose startup. Running the patcher again with the apfs unticked will not remove the apfs patch. The efi drives shown during the boot screen is normal for our patched machines and can be ignored. It does not mean you have a successful rom patch. If you have an apfs rom and have applied the apfs patch then the verbose startup can be removed (involves mounting a drive and deleting certain files) but I suspect that you need the apfs patch so do not need to do this unless you successfully update the rom.

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......!!!!!!!!!

 

[Flacko]

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......!!!!!!!!!

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.

 

[Blackriton]

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.

I checked the Boot ROM Version and its exactly the same than yours. I don't want to take a risky step deleting the EFI boot folder as my desktop computer is o-also my work one....... I will wait for Dosdude clues as he may know how to delete the verbose boot with no risks involved !!!!!!!!

Anyway thanks for your ideas and help.

 

[LarryJoe33]

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.