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 used Mojave Patcher 1.3.2 to to apply patches after upgrading my HackBookPro 5,1 from 10.14.4 to 10.14.5. kextcache -i produces the following error/warning messages. Is this a problem with the patched
IOUSBHostFamily.kext / LegacyUSBInjector.kext? Details below.

kextcache -i / output includes the following:

  • /System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBVHCIBCE.kext - dependency 'com.apple.driver.usb.AppleUSBVHCI' not found.
  • /System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBVHCIBCE.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
  • kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostTxRxQueue was not patched because its parent, the vtable for AppleUSBVHCIHostTransferQueue, was not patchable.
  • kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostTransferQueue was not patched because its parent, the vtable for AppleUSBVHCIBCETransferQueue, was not found.
  • Link failed (error code 5).
  • Prelink failed for com.apple.driver.AppleUSBVHCI; omitting from prelinked kernel.
 
Last edited:
I used Mojave Patcher 1.3.2 to to apply patches after upgrading my HackBookPro 5,1 from 10.14.4 to 10.14.5. kextcache -I produces the following error/warning messages. Is this a problem with the patched
IOUSBHostFamily.kext / LegacyUSBInjector.kext? Details below.

kextcache -i / output includes the following:

  • /System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBVHCIBCE.kext - dependency 'com.apple.driver.usb.AppleUSBVHCI' not found.
  • /System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBVHCIBCE.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
  • kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostTxRxQueue was not patched because its parent, the vtable for AppleUSBVHCIHostTransferQueue, was not patchable.
  • kxld[com.apple.driver.AppleUSBVHCI]: The vtable for AppleUSBVHCIHostTransferQueue was not patched because its parent, the vtable for AppleUSBVHCIBCETransferQueue, was not found.
  • Link failed (error code 5).
  • Prelink failed for com.apple.driver.AppleUSBVHCI; omitting from prelinked kernel.
This can be ignored; it's simply failing to link USBVHCI kexts, which aren't necessary on unsupported machines.
 
Hi, I've a early 2009 Macbook (5,2 white).
I'm trying to installa Mojave but I get the "NO" symbol when I plug usb, restart Mac and try to installa Mojave. Same happens when I try to install High Sierra.
It's kinda strange because 1 year ago I installed High Sierra via patcher (then returned to El Capitan).
I downloaded both HS and Mojave but nothing works.
I titled my usb with different names but nothing.
What can I do? I tryied HS with 8gb and 16gb usb but nothing. I tryied Mojave with my only 16gb usb.. it seems all okay with 'complete', I reboot, select my usb, Apple logo with bar and then NO symbol.

Thanks!
 

Attachments

  • Schermata 2019-05-28 alle 6.34.48 PM.png
    Schermata 2019-05-28 alle 6.34.48 PM.png
    120.8 KB · Views: 278
  • 20190528_183906.jpg
    20190528_183906.jpg
    6.4 MB · Views: 265
Last edited:
Hi, I've a early 2009 Macbook (5,2 white).
I'm trying to installa Mojave but I get the "NO" symbol when I plug usb, restart Mac and try to installa Mojave. Same happens when I try to install High Sierra.
It's kinda strange because 1 year ago I installed High Sierra via patcher (then returned to El Capitan).
I downloaded both HS and Mojave but nothing works.
I titled my usb with different names but nothing.
What can I do? I tryied HS with 8gb and 16gb usb but nothing. I tryied Mojave with my only 16gb usb.. it seems all okay with 'complete', I reboot, select my usb, Apple logo with bar and then NO symbol.

Thanks!

Not all USB drive's are bootable on a Mac. You need to try different USB brands.
 
Hi, I've a early 2009 Macbook (5,2 white).
I'm trying to installa Mojave but I get the "NO" symbol when I plug usb, restart Mac and try to installa Mojave. Same happens when I try to install High Sierra.
It's kinda strange because 1 year ago I installed High Sierra via patcher (then returned to El Capitan).
I downloaded both HS and Mojave but nothing works.
I titled my usb with different names but nothing.
What can I do? I tryied HS with 8gb and 16gb usb but nothing. I tryied Mojave with my only 16gb usb.. it seems all okay with 'complete', I reboot, select my usb, Apple logo with bar and then NO symbol.

Thanks!
and make sure your SIP is disabled and you have apple the post install patches after you install macOS High Sirra or Mojave
 
  • Like
Reactions: K two
Mine is working fine natively, (after post install of course) (10.14.1) without any kext replacing until i restart in ElCap.

I did kext business from final release of HS. Are u sure is it solve this? I got reboot loop, tried to reset pram, repatch, same: apple appears about few seconds, boom restart.
What you think?

Thank you :)
Sorry to hear that replacing the BT kexts did not help. This has worked for many (but not all) on this forum. Mojave and BT has been a problem for quite a few of us. Can you confirm that you fixed the preferences and rebuilt the kext cache after you replaced the kexts.
It does seem strange that your problem occurs once you have booted to El Cap. This may indicate that something is going on with your SMC/PRAM. Can you give some more details on your setup. Graphics card, APFS or HFS+, APFS ROM update etc.
To get Mojave back you can reboot to the install USB and reinstall over the top of your Mojave drive. This will overwrite any changes that you may have made. Remember to repatch afterwards.
 
QUOTE="avz, post: 27398062, member: 1148741"]Not all USB drive's are bootable on a Mac. You need to try different USB brands.[/QUOTE]

So unlucky, 3 different brand and 3 times No Symbol! Thanks..

and make sure your SIP is disabled and you have apple the post install patches after you install macOS High Sirra or Mojave

Sure, thank you!
 
QUOTE="avz, post: 27398062, member: 1148741"]Not all USB drive's are bootable on a Mac. You need to try different USB brands.

So unlucky, 3 different brand and 3 times No Symbol! Thanks..



Sure, thank you!

Unplug the USB Mojave patcher, and from any internal (or USB external) OSX bootable partition, or Recovery CMD+R, or Snow Leopard DVD or anything else, boot holding CMD+S , then when you land in any Shell type:

nvram boot-args="-no_compat_check"

reboot



and then retry to boot the USB Installer.
[doublepost=1559066492][/doublepost]
Mine is working fine natively, (after post install of course) (10.14.1) without any kext replacing until i restart in ElCap.

I did kext business from final release of HS. Are u sure is it solve this? I got reboot loop, tried to reset pram, repatch, same: apple appears about few seconds, boom restart.
What you think?

Thank you :)

But do you have chown/chmod the replaced kexts ?

During Post-Install Patches are you targeting the right Partition ?

Even if sometimes also a meaningless kext replace can cause this bootloop, the "IOACPIFamily.kext" is a very tricky kext that involves others, I'd haven't replaced it, so I guess you cannot neither enter in single user mode CMD+S since the bootloop occurs earlier than preliminary kexts loaded, I guess only fix to this is to re-install Mojave over your current Volume, you won't lose your datas.
 
Last edited:
  • Like
Reactions: avz
Sorry to hear that replacing the BT kexts did not help. This has worked for many (but not all) on this forum. Mojave and BT has been a problem for quite a few of us. Can you confirm that you fixed the preferences and rebuilt the kext cache after you replaced the kexts.
It does seem strange that your problem occurs once you have booted to El Cap. This may indicate that something is going on with your SMC/PRAM. Can you give some more details on your setup. Graphics card, APFS or HFS+, APFS ROM update etc.
To get Mojave back you can reboot to the install USB and reinstall over the top of your Mojave drive. This will overwrite any changes that you may have made. Remember to repatch afterwards.

Thank you.

My file system is HFS+, now reinstalled Mojave without reformat, bt working again. I patched recovery partition and tried to enabling system integrity protection and viola it's solved finally. :)

Another thing:

I've GTX680 Gigabyte Windforce 2gb with Evga mac rom, just replaced last week my older 27" FHD display to 32" 16:9 Sam UHD, it can work via HDMI in native resolution with 30hz, but the GUI little slow, so i using 2560 x 1440 60hz: it is more acceptable.
The bigger problem is: The efi / boot selector LOW resolution (800 x 600 and half time of boot switched to 1024 x 768)
» Installed Refind (now usable, i see all of my bootable partitions and installers) and tried to edit higher resolutions in config file without luck.
Do you or Anybody have any idea how to increase that resolution? Is it possible somehow?
My old monitor appeared Efi too in FHD with nice, sharp Apple logo.
 
A follow-up to this post. The problem turned out to be the 120Gb SSD (Kingston) that I used. Once I changed it, the machine was fine - except for AirDrop. It would not work. The laptop had the original BCM94321 WiFi card which I patched using the post-install patch tool of @dosdude1 Mojave patcher. Finally, I put in the BCM94322 card from the old 17", and AirDrop started working. I am not sure if it's just a one-off. Perhaps others would report on their experience with patched BCM94321 WiFi cards.

Also had problems with Kingston SSDs as boot drives on both supported and unsupported Macs. Crucial, SanDisk Plus and Samsung EVO 800 series all down-shift to SATA2, readily. Never a problem in service for years.
 
  • Like
Reactions: olad
Also had problems with Kingston SSDs as boot drives on both supported and unsupported Macs. Crucial, SanDisk Plus and Samsung EVO 800 series all down-shift to SATA2, readily. Never a problem in service for years.

Thanks for confirming the flakiness of (some) Kingston SSDs. I substituted a Crucial. No problems so far. The other question - didn't anyone have problems with patched BCM94321 WiFi cards?
 
  • Like
Reactions: K two
Hey folks,

Have a MacPro 3.1 here with a GTX 950 that I'm considering upgrading to Mojave. I'm sure this question has been answered a thousand times so sorry in advance, but is it relatively easy to keep Mojave updated on these unsupported Macs?

I'm assuming that the adjusted bootable USB will be needed to patch the OS, but is it generally the case that updates will just install through the Software Update section of System Preferences? Or is there another method that people generally use here?

Thanks in advance for any insights!
 
Hey folks,

Have a MacPro 3.1 here with a GTX 950 that I'm considering upgrading to Mojave. I'm sure this question has been answered a thousand times so sorry in advance, but is it relatively easy to keep Mojave updated on these unsupported Macs?

I'm assuming that the adjusted bootable USB will be needed to patch the OS, but is it generally the case that updates will just install through the Software Update section of System Preferences? Or is there another method that people generally use here?

Thanks in advance for any insights!
Yes if your hdd/ssd is formatted on APFS your updates will install throughout software updates and yes you will need to reapply the post install patches after a macOS update. If you choose to stay with HFS then you will have to wait in the final comes like 10.14.6 and you will be able to download macOS Mojave and create the mouse patcher with it :)
 
  • Like
Reactions: Argyboy and roronl
Hi,
Its been some time and I have missed a lot. Last I tried I got stuck with installing 10.14.4 on my Late MBP 13" . I reverted back to .3 and since then have been afraid of doing anything to my laptop.

Is it safe to update from .3 to .4 or .5 ?
If yes can someone outline the detailed process again? I believe I still have 1.2.3 version of the dosdude's patcher and don't know how to update it.

Any help or detailed instructions would be very much appreciated! =)
 
You will need to download the newest patcher on pg 1 of this thread which is 1.3.2 follow the instructions there on creating one and will also tell you how to download the latest macOS Mojave the newest patcher has the most recent fixes
 
  • Like
Reactions: K two
You will need to download the newest patcher on pg 1 of this thread which is 1.3.2 follow the instructions there on creating one and will also tell you how to download the latest macOS Mojave the newest patcher has the most recent fixes
I understand.
The thing that confuses me is when you say, "update the patcher" how am i supposed to do that or just making a usb with the latest patcher trying an inplace upgrade to 10.14.5 work?
 
I understand.
The thing that confuses me is when you say, "update the patcher" how am i supposed to do that or just making a usb with the latest patcher trying an inplace upgrade to 10.14.5 work?
I hope this helps its on the very first page
 

Attachments

  • Screen Shot 2019-05-28 at 10.02.23 PM.png
    Screen Shot 2019-05-28 at 10.02.23 PM.png
    1.2 MB · Views: 252
  • Screen Shot 2019-05-28 at 10.02.41 PM.png
    Screen Shot 2019-05-28 at 10.02.41 PM.png
    1.1 MB · Views: 231
  • Screen Shot 2019-05-28 at 10.02.41 PM.png
    Screen Shot 2019-05-28 at 10.02.41 PM.png
    1.1 MB · Views: 245
  • Like
Reactions: K two
Hi,
Its been some time and I have missed a lot. Last I tried I got stuck with installing 10.14.4 on my Late MBP 13" . I reverted back to .3 and since then have been afraid of doing anything to my laptop.

Is it safe to update from .3 to .4 or .5 ?
If yes can someone outline the detailed process again? I believe I still have 1.2.3 version of the dosdude's patcher and don't know how to update it.

Any help or detailed instructions would be very much appreciated! =)

The process(song) remains the same since the Sierra patcher. You need to do exactly the same thing you did when you installed 10.14.3. You start by creating the Mojave patcher from the scratch. This is the beauty of the patcher, you don't have to follow every page of this thread(just pay attention to the updated instructions on the dosdude1.com website).

I made an effort of following this thread closely and it allowed me to learn how to do most of the patching manually. This is the only difference. I still use 1.2.3 version of the patcher as I am able to do the rest manually. That is all there is to it.
 
Hey folks,

Have a MacPro 3.1 here with a GTX 950 that I'm considering upgrading to Mojave. I'm sure this question has been answered a thousand times so sorry in advance, but is it relatively easy to keep Mojave updated on these unsupported Macs?

I'm assuming that the adjusted bootable USB will be needed to patch the OS, but is it generally the case that updates will just install through the Software Update section of System Preferences? Or is there another method that people generally use here?

Thanks in advance for any insights!
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.
 
  • Like
Reactions: Argyboy
Mine is working fine natively, (after post install of course) (10.14.1) without any kext replacing until i restart in ElCap.

I did kext business from final release of HS. Are u sure is it solve this? I got reboot loop, tried to reset pram, repatch, same: apple appears about few seconds, boom restart.
What you think?

Thank you :)

If you have a spare drive, you might try a clean install of 10.14.5 from the patched full installer without migrating user accounts. When I was initially testing the use of a BCM94360CS2 in a MacPro 3,1, the BT refused to be recognized until I purged out all of the settings with a clean install.
 
Thank you.

My file system is HFS+, now reinstalled Mojave without reformat, bt working again. I patched recovery partition and tried to enabling system integrity protection and viola it's solved finally. :)

Another thing:

I've GTX680 Gigabyte Windforce 2gb with Evga mac rom, just replaced last week my older 27" FHD display to 32" 16:9 Sam UHD, it can work via HDMI in native resolution with 30hz, but the GUI little slow, so i using 2560 x 1440 60hz: it is more acceptable.
The bigger problem is: The efi / boot selector LOW resolution (800 x 600 and half time of boot switched to 1024 x 768)
» Installed Refind (now usable, i see all of my bootable partitions and installers) and tried to edit higher resolutions in config file without luck.
Do you or Anybody have any idea how to increase that resolution? Is it possible somehow?
My old monitor appeared Efi too in FHD with nice, sharp Apple logo.
Good that you have got Mojave back. Does El Cap affect the BT now? I still think it was issue with the NVRAM. These are 2 of the variables in the NVRAM - bluetoothActiveControllerInfo – Bluetooth active controller information and bluetoothInternalControllerInfo – Bluetooth internal controller information.

You will have to keep SIP disabled if you are using dosdude1's patcher otherwise you can have issues with patched system files. The patcher will disable SIP even if you set it enable in the NVRAM preference. To quote dosdude1 "You should not attempt to enable SIP when running Mojave Patcher."

My GTX680 is an EVGA one that has been patched (not the Mac edition one). It does the same as yours in that the initial boot screen resolution is low. I believe this is something that commonly happens with flashed graphic cards. It does not really bother me but if you want to there are some NVRAM commands that could be explored. Again, it is the NVRAM that effects this. See this link for further info:https://forums.macrumors.com/threads/boot-screen-resolution-with-flashed-graphics-card.2052918/
Maybe someone with more knowledge will be able to help you with the NVRAM if you are feeling brave.
 
Another thing:

I've GTX680 Gigabyte Windforce 2gb with Evga mac rom, just replaced last week my older 27" FHD display to 32" 16:9 Sam UHD, it can work via HDMI in native resolution with 30hz, but the GUI little slow, so i using 2560 x 1440 60hz: it is more acceptable.
The bigger problem is: The efi / boot selector LOW resolution (800 x 600 and half time of boot switched to 1024 x 768)
» Installed Refind (now usable, i see all of my bootable partitions and installers) and tried to edit higher resolutions in config file without luck.
Do you or Anybody have any idea how to increase that resolution? Is it possible somehow?
My old monitor appeared Efi too in FHD with nice, sharp Apple logo.

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.
 
Last edited:
  • Like
Reactions: ASentientBot
Good that you have got Mojave back. Does El Cap affect the BT now? I still think it was issue with the NVRAM. These are 2 of the variables in the NVRAM - bluetoothActiveControllerInfo – Bluetooth active controller information and bluetoothInternalControllerInfo – Bluetooth internal controller information.

You will have to keep SIP disabled if you are using dosdude1's patcher otherwise you can have issues with patched system files. The patcher will disable SIP even if you set it enable in the NVRAM preference. To quote dosdude1 "You should not attempt to enable SIP when running Mojave Patcher."

My GTX680 is an EVGA one that has been patched (not the Mac edition one). It does the same as yours in that the initial boot screen resolution is low. I believe this is something that commonly happens with flashed graphic cards. It does not really bother me but if you want to there are some NVRAM commands that could be explored. Again, it is the NVRAM that effects this. See this link for further info:https://forums.macrumors.com/threads/boot-screen-resolution-with-flashed-graphics-card.2052918/
Maybe someone with more knowledge will be able to help you with the NVRAM if you are feeling brave.

Since re-enabled SIP, the bt problem is gone fortunately. Just i've the old issue, when i booting El Cap, absolutely don't have mouse and keyboard » force power off, after that the second boot to El Cap working perfectly. I think another NVRAM issue. I can live together with it, just sometimes need 10.11.


Thank you very much for help and that topic, i will collect more information and ask some help there. :)
 
Thank you.

My file system is HFS+, now reinstalled Mojave without reformat, bt working again. I patched recovery partition and tried to enabling system integrity protection and viola it's solved finally. :)

Another thing:

I've GTX680 Gigabyte Windforce 2gb with Evga mac rom, just replaced last week my older 27" FHD display to 32" 16:9 Sam UHD, it can work via HDMI in native resolution with 30hz, but the GUI little slow, so i using 2560 x 1440 60hz: it is more acceptable.
The bigger problem is: The efi / boot selector LOW resolution (800 x 600 and half time of boot switched to 1024 x 768)
» Installed Refind (now usable, i see all of my bootable partitions and installers) and tried to edit higher resolutions in config file without luck.
Do you or Anybody have any idea how to increase that resolution? Is it possible somehow?
My old monitor appeared Efi too in FHD with nice, sharp Apple logo.

The GTX 680 with 2GB should be capable of delivering 2560x1440 in HiRes mode and native 4K resolution.

See my screenshot below.

Screenshot 2019-03-30 at 10.03.21.png
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.