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 tried to do the opposite on an MBP 15", I mean I needed a lower resolution in the EFI login screen or Refind bootloader icons / Terminal shell in order to have them bigger, and once I succeeded but after latest Mojave update at EFI bootloader I only can get the default LCD resolution with very small icons and Terminal shell, of course in booted macOS I can switch among all the available resolutions.

Editing the com.apple.boot.plist adding "Graphics Mode" key setting a custom resolution seems to not work more.

Anyway I noticed that if you set a wrong resolution in Refind config file, Refind bootloader will tell you all the available custom resolutions for your Display, I simply added a line following these steps:

sudo mkdir /Volumes/efi
sudo mount -t msdos /dev/disk0s1 /Volumes/efi


open /Volumes/efi/EFI/refind/

then from Finder take a backup of your current refind.conf

and edit it with TextEdit or any other plain-text editor, and search inside for these lines:

# Default is "0 0" (use the system default resolution, usually 800x600).
#
#resolution 1024 768
#resolution 3


then under these lines add without # :

resolution 1440 900

Save and reboot

Now Refind bootloader should tell that resolution is not supported and suggest which are the native supported EFI resolutions for your Display.


And about using a third party external LCD Display with a Mac mini, I noticed that if you use an HDMI cable it auto fits to the correct EFI bootloader resolution.

Thank you for an idea, tried and got instant blank screen without boot. The EFI can't work higher resolution with this setup ATM. I need more skill in this question :)
 
Last edited:
Thank you for idea, tried and got instant blank screen without boot. The EFI can't work higher resolution with this setup ATM. I need more skill in this question :)

If you got a blank screen then most probably your GPU hasn't an official Mac EFI ROM, but a PC one I guess, when you set a custom resolution from Refind, you should get only a warning on-screen, this doesn't affect the apple bootloader, I mean after power-on holding alt-option key (with an apple genuine keyboard) will override Refind bootloader showing the normal apple startup manager.
 
I believe you may have trouble with your GTX950 as it is a Maxwell card and there are no Mojave drivers for it. Mojave works well for nVidia Kepler cards as it has built in drivers for the GTX680. At present it seems unlikely that Apple and Nvidia are going to resolve this.
If you have a Kepler card then the mp3.1 runs Mojave well and can be kept updated vis system preferences if you have a APFS drive or by the dosdude1 installer. In both instances you have to patch afterwards so always have the latest usb handy. the APFS ROM update also works well for the mp3.1 - see page 1.

Appreciate this. Thanks very much! I'll do some more research and have a think about it. Thanks again! :)
 
If you got a blank screen then most probably your GPU hasn't an official Mac EFI ROM, but a PC one I guess, when you set a custom resolution from Refind, you should get only a warning on-screen, this doesn't affect the apple bootloader, I mean after power-on holding alt-option key (with an apple genuine keyboard) will override Refind bootloader showing the normal apple startup manager.

No, i flashed the card with Evga mac rom. Cmd+alt+p+r helped me, it booted with original bootloader and i deleted that line.

Do you know, how can i use refind-mkdefault script? Always i got this message in terminal:

Mac-Pro:~ mac-pro$ /Volumes/efi/EFI/refind/refind-mkdefault ; exit;

env: python3: No such file or directory
---
I always reinstall with refind-install and of course it doesn't appear between start up disks too...
 
No, i flashed the card with Evga mac rom. Cmd+alt+p+r helped me, it booted with original bootloader and i deleted that line.

Do you know, how can i use refind-mkdefault script? Always i got this message in terminal:

Mac-Pro:~ mac-pro$ /Volumes/efi/EFI/refind/refind-mkdefault ; exit;

env: python3: No such file or directory
---
I always reinstall with refind-install and of course it doesn't appear between start up disks too...

Refind to be installed requires SIP disabled, so you should boot first to a Recovery or USB Installer and from there open Terminal and type: csrutil disable

Then re-booting again from macOS you should type from a macOS Terminal: sudo /path/refind-install

re-installing Refind will make it defaults again too.
 
Last edited:
Refind to be installed requires SIP disabled, so you should boot first to a Recovery or USB Installer and from there open Terminal and type: csrutil disable

Then re-booting again from macOS you should type from a macOS Terminal: sudo /path/refind-install
Yes i know, i did that way. There isn't refind, is it natural? I've seen choosable refind partition in start up disk. I attached pictures, the black is mine.
Képernyőfotó 2019-05-29 - 21.50.29.png startup-disk.png
 
Yes i know, i did that way. There isn't refind, is it natural? I've seen choosable refind partition in start up disk. I attached pictures, the black is mine.
View attachment 839540 View attachment 839541

Yes it's normal, I also use refind on some machines and I don't have any Refind either on apple startup manager and Startup Disk. It's just hidden let's say.

Probably you saved the refind.conf in non-plain-text (probably rich-text), it happens sometimes so you should copy a new refind.conf to make Refind correctly detected after the power-on.

Because when you re-install it keeps the old refind.conf .
 
Yes it's normal, I also use refind on some machines and I don't have any Refind either on apple startup manager and Startup Disk. It's just hidden let's say.

Probably you saved the refind.conf in non-plain-text (probably rich-text), it happens sometimes so you should copy a new refind.conf to make Refind correctly detected after the power-on.

Because when you re-install it keeps the old refind.conf .

Ah, thank you. No, i didn't save to rich text, there isn't any problem with config file.Képernyőfotó 2019-05-29 - 22.57.54.png
 
For the MB4,1 lovers:

I've updated my kext-package to v1.4 with the Broadcom Wifi kexts needed to run the original BRCM4321 card that the MB4,1 was equipped with. Runs fine and has been tested on 10.14.4 and 10.14.5. Thanks to @dosdude1 for the test machine! (In the MB4,1 that I previously used I swapped the card to get around this but after folks started using @0403979 alternative patcher it became clear that the old card was really not supported any more - just like in other machines). There will most certainly be better/cleaner/more straightforward solutions for the WiFi issue than this initial kext combo. Julian has some ideas, too, that can be tried out. More to come, it'd seem ;-)
What did not work was the Broadcom plus corecatcher replacement and corecatcherresponder solution that did the trick on other systems with similar cards...

Here's the download link for the package. Install with kext utility or copy to /S/L/E and correct permissions. Then rebuild prelinked kernel and reboot.

See screenshot for current kext contents in v1.4 compared to older versions.

View attachment 838078

Hi, thanks for making 10.14 available on MB4,1, I used 0403979's patch to create an installer and installed 10.14.5 successfully on my MB4,1 everything goes fine except no WIFI. I found the wifi kexts you mentioned here are missing from 0403979's patch file. So I used Kext Utility to install these Broadcom Wifi kexts and repatched the system, but no use, no wifi function loaded. Could you explain in detail how to do if I copy these two Broadcom wifi kexts to /S/L/E to make them work? Many thanks!
 
I've just released a cloud update to macOS Downloader to add the 10.14.5 installer download and an update to macOS Patcher to add 10.14.5 installer support and fix graphics patch issues in 10.14.4 and 10.14.5. macOS Patcher 2.2.1 should fully support 10.14.5 betas and the final version.

Release notes for macOS Patcher 2.2.1:

- Add 10.14.5 installer support
- Fix 10.14.4 and 10.14.5 graphics patch issues

Download macOS Patcher 2.2.1 here and macOS Downloader 2.0.1 (latest version) here.

cc: @Larsvonhier

Hi, thanks for making 10.14 available on MB4,1, I used your latest patch to create an installer and installed 10.14.5 successfully on my MB4,1 everything goes fine except no WIFI. I found the Broadcom wifi kexts are missing from your patch file. Could you include these wifi kexts files provided by Larsvonhier to rewrite the script and update the patch file?Many thanks!
 
I'm trying to install with the latest 1.3.2 version on an iMac10,1. I am able to install MacOS on the HDD and it reboots back to the USB so I can do the macOS Post Install. After the Post Install it reboots and comes right back to the USB. I can't get it to boot to the macOS on the HDD. I tried do a force cache rebuild but it just reboots right back to the USB. Any ideas on what I should try?
I'm running this as a clean install after wiping the HDD. Thank you.

EDIT:
So I was originally trying with APFS format. I just tried MAC OS Journaled and it booted up. But the warning on the site says to use APFS to get system updates. Is there a way to convert to APFS now? Or any ideas on how to get it to install and boot correctly from APFS to begin with?
 
Last edited:
  • Like
Reactions: K two
I'm trying to install with the latest 1.3.2 version on an iMac10,1. I am able to install MacOS on the HDD and it reboots back to the USB so I can do the macOS Post Install. After the Post Install it reboots and comes right back to the USB. I can't get it to boot to the macOS on the HDD. I tried do a force cache rebuild but it just reboots right back to the USB. Any ideas on what I should try?
I'm running this as a clean install after wiping the HDD. Thank you.

EDIT:
So I was originally trying with APFS format. I just tried MAC OS Journaled and it booted up. But the warning on the site says to use APFS to get system updates. Is there a way to convert to APFS now? Or any ideas on how to get it to install and boot correctly from APFS to begin with?

What was the previous OS you had installed on your machine?
 
  • Like
Reactions: K two
I'm trying to install with the latest 1.3.2 version on an iMac10,1. I am able to install MacOS on the HDD and it reboots back to the USB so I can do the macOS Post Install. After the Post Install it reboots and comes right back to the USB. I can't get it to boot to the macOS on the HDD. I tried do a force cache rebuild but it just reboots right back to the USB. Any ideas on what I should try?
I'm running this as a clean install after wiping the HDD. Thank you.

EDIT:
So I was originally trying with APFS format. I just tried MAC OS Journaled and it booted up. But the warning on the site says to use APFS to get system updates. Is there a way to convert to APFS now? Or any ideas on how to get it to install and boot correctly from APFS to begin with?
Your machine does not natively support APFS so you have 2 methods that can be used. 1. Use the APFS option in the patcher. Make sure this is ticked if you are using an APFS drive. 2. More risky but many have done it successfully. Use the APFS ROM upgrade - see page 1. See if any iMac 10.1 users get back to you. I would use APFS if you have an SSD otherwise stay with HFS+. Updating vis preferences is one thing APFS gives you but you will still more than likely have to patch using the latest usb drive as there is a good chance that the patcher files will be overridden. So using the usb patcher to install over your present system is not too much of an inconvenience.
[doublepost=1559214454][/doublepost]
What was the previous OS you had installed on your machine?
To correct my last post, your iMac is one of the earliest that supports High Sierra and therefore should support APFS. What system are you presently running and do you have an SSD? If you have an SSD and installed HS then it should have been converted to APFS then and you should therefore not need any patches or ROM update. I believe a firmware update would have been carried out during the HS installation.
 
  • Like
Reactions: K two and roronl
Hi, thanks for making 10.14 available on MB4,1, I used your latest patch to create an installer and installed 10.14.5 successfully on my MB4,1 everything goes fine except no WIFI. I found the Broadcom wifi kexts are missing from your patch file. Could you include these wifi kexts files provided by Larsvonhier to rewrite the script and update the patch file?Many thanks!
Sorry about the WiFi issue. I don't have a 4,1 right now so I've just been relying on information from @Larsvonhier for now. I will be getting a 4,1 of my own in a few days (just in time for wwdc), so I'll be able to test on my own. It's good that everything works at the moment.
 
  • Like
Reactions: Larsvonhier
I'm trying to install with the latest 1.3.2 version on an iMac10,1. I am able to install MacOS on the HDD and it reboots back to the USB so I can do the macOS Post Install. After the Post Install it reboots and comes right back to the USB. I can't get it to boot to the macOS on the HDD. I tried do a force cache rebuild but it just reboots right back to the USB. Any ideas on what I should try?
I'm running this as a clean install after wiping the HDD. Thank you.

EDIT:
So I was originally trying with APFS format. I just tried MAC OS Journaled and it booted up. But the warning on the site says to use APFS to get system updates. Is there a way to convert to APFS now? Or any ideas on how to get it to install and boot correctly from APFS to begin with?

iMac 11,2 500GB HDD which runs High Sierra native. Partitioned HDD into two 250GB HFS+ partitions leaving 10.13.6 intact. Running Disk Utility from HS partition, un-mount the blank partition to format into APFS. Currently up to 10.14.6b1 on the APFS HDD using Patcher v.1.3.2 and OTA Beta install. Now can dual boot HFS+/APFS. Runs like a champ on .6b1. Must install 10.14.4 or .5, prior to .6b1.
Word to the wise - reset NVRAM to get back to Option/restart boot drive selection.

iMac11,2 on .6b1.png
 
Last edited:
  • Like
Reactions: roronl
I bought a used iMac with 10.9.5 (Mavericks) and bootcamp Windows 7. I combined the partitions into one and reformatted first as APFS and then MAC OS Journaled.
I can confirm what avz said. If you want to go APFS then you must install HS first. Do this via the Apple store so you get the full installer with the firmware update. You can then move on to Mojave using the patcher.
 
Hi, thanks for making 10.14 available on MB4,1, I used 0403979's patch to create an installer and installed 10.14.5 successfully on my MB4,1 everything goes fine except no WIFI. I found the wifi kexts you mentioned here are missing from 0403979's patch file. So I used Kext Utility to install these Broadcom Wifi kexts and repatched the system, but no use, no wifi function loaded. Could you explain in detail how to do if I copy these two Broadcom wifi kexts to /S/L/E to make them work? Many thanks!
Not sure if you settled the problem in the meantime, but here´s what you essentially need for getting Wifi up and running on your MB4,1 (hopefully you have the same card or at least one of the same sub-group).
Make sure you use the latest Kext Utility (2.6.6?) and most importantly, wait until the pre-linked kernel is re-generated (see folder of the same name, wait for the 0 byte file being replaced). This takes some time more than the kext util suggests...
Also make sure that all three files are included in our post-patch:
IO80211Family.kext v7.0.4
Broadcom43XXFamily.kext and ...Familyrev2.kext (both v3.1.4)

You can also see if kexts are loaded correctly if you do a verbose boot or with "kext wizard", another fine tool.
IO802 reports as version 704.52 then and one of the Broadcom kexts as com.apple.driver.AirPortBrcm43224 v700.36.24

In case you still have no wifi, does it report as missing hardware or just a greyed-out indicator?
 
  • Like
Reactions: pkouame
Not sure if you settled the problem in the meantime, but here´s what you essentially need for getting Wifi up and running on your MB4,1 (hopefully you have the same card or at least one of the same sub-group).
Make sure you use the latest Kext Utility (2.6.6?) and most importantly, wait until the pre-linked kernel is re-generated (see folder of the same name, wait for the 0 byte file being replaced). This takes some time more than the kext util suggests...
Also make sure that all three files are included in our post-patch:
IO80211Family.kext v7.0.4
Broadcom43XXFamily.kext and ...Familyrev2.kext (both v3.1.4)

You can also see if kexts are loaded correctly if you do a verbose boot or with "kext wizard", another fine tool.
IO802 reports as version 704.52 then and one of the Broadcom kexts as com.apple.driver.AirPortBrcm43224 v700.36.24

In case you still have no wifi, does it report as missing hardware or just a greyed-out indicator?
Thanks for your kind help. I will try your suggestions and report to you next week. I am out of town right now. One more thing, could you explain in detail how to correct permissions and rebuild prelinked kernel? I don't know these commands.
 
No, i flashed the card with Evga mac rom. Cmd+alt+p+r helped me, it booted with original bootloader and i deleted that line.

Do you know, how can i use refind-mkdefault script? Always i got this message in terminal:

Mac-Pro:~ mac-pro$ /Volumes/efi/EFI/refind/refind-mkdefault ; exit;

env: python3: No such file or directory
---
I always reinstall with refind-install and of course it doesn't appear between start up disks too...

Are you using refind so that you can boot linux as well? On my MacPro 3,1, I have found that recent Ubuntu and Fedora do a decent job of installing a bootable linux on its own drive such that the boot selector method can be used to select between macOS, linux and windows 10.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.