Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.14 Mojave on Unsupported Macs Thread

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.
nmincone said:
Use with care, I bricked an install trying this.

But in the process after having to reinstall Mojave, I then ran the post installation again, checked all the boxes and clicked force cache rebuild, when I restarted my iSight camera was working!
Click to expand...

I recall after first running the Mojave installer & patch upon first boot my camera was working but audio was not.

So I ran the OSX Patcher app to reinstall the KEXT patches again and rebooted. Days later I went to use the camera and it was not working anymore.

I spent last night replacing KEXTs from a command line following instructions I found all over the internet and ended up blowing up my OS (no boot, no mouse support, etc)

So, at 1 am, I begin reinstalling Dosdude's Mojave and run the post install patches and after I reboot the camera is now working.

So here's the take away that worked for me. I just duplicated it on a second MBP Early 2011 that also had no camera support after the initial install.

Install Mojave and run the post install patch from the installer screen on your second boot
If there is another dosdude patch update and you run it from the bootable OS install and you loose any functions then reboot back into the original installer.
Run the Post Install again
Choose your computer model (mine was 2,1)
Check each box of all the patches
Check Force Cache rebuild
Click reboot

Your mileage may vary... I'm off to the donate page. Thanks DosDude!
 
  • Like
Reactions: FarmerBob, TimothyR734, olad and 1 other person
0403979 said:
How can I run the actual install in virtualbox? The installer made from my patcher or dosdude1's patcher.
Click to expand...

Virtualbox is mostly a BIOS-oriented emulation, so in order to run any HFS partition you'd need to create an empty virtual machine using a virtual disk for the bootloader like Clover (but don't use on real mac never), I guess Refind won't work in that scope (you can try however), then to run a macOS Installer from there best practice is to convert the Installer into an .iso file (not dmg compressed iso) and create another virtual disk with it inside the same virtual machine, then your bootloader will recognize your Installer and you can record videos/pictures at the highest quality you need. Recent Virtualbox versions should support EFI emulation and APFS.

edit:
I meant recording videos while using in background the "Mojave host machine" screenshot default app, virtual machines snapshots are another thing.
 
Last edited:
  • Like
Reactions: TimothyR734 and ASentientBot
Sorry if wrong place to ask, i am looking for a link to the program that is used to change you setting for which Beta Dev channel your system is set to so you can get beta or Dev releases. I know i have seen it in here, just cant look thru 473 pages....
 
  • Like
Reactions: TimothyR734
jackluke said:
Try replacing /S/L/PrivateFramework/IOAccelerator.framework and or its plugin inside /S/L/E/ with previous Mojave 10.14.3 , it's involved too in graphics acceleration at loginUI and WindowServer.
[doublepost=1548836603][/doublepost]

I know well these kext family when I played with their VRAM, for IntelHD3000 the OpenGL driver is simply this: /System/Library/Extensions/AppleIntelHD3000GraphicsGLDriver.kext

So just rename it to something else (ex. A*.kext2) or move out from its folder or delete directly and an automatic kextcache schedule will occur at your next reboot and as @ASentientBot stated without OpenGL you should be able to pass the LoginWindow with the current 10.14.4 beta.

If for some reason you still can't reach the LoginUI then repeat the same steps even for its Framebuffer: /System/Library/Extensions/AppleIntelSNBGraphicsFB.kext
Removing this last one is equivalent to a holding-SHIFT-safe mode.
[doublepost=1548838477][/doublepost]
Click to expand...

@jackluke,

There is no AppleIntelHD3000GraphicsGLDriver.kext on the /S/L/E folder. However, it does have a AppleIntelHD3000GraphicsGLDriver.bundle

Are those the same? Thank you.

EDIT: I did find these entries on Info.plist under /Contents of the bundle.

<string>AppleIntelHD3000GraphicsGLDriver</string>
<key>CFBundleGetInfoString</key>
<string>AppleIntelHD3000GraphicsGLDriver 10.4.14</string>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleIntelHD3000GraphicsGLDriver</string>

So my follow-up question --- is the bundle file the one I need to rename? Thanks.
 
Last edited:
  • Like
Reactions: TimothyR734 and jackluke
ASentientBot said:
I'm not sure if anybody wants this information, but I might as well share it. I never use the automated macOS downloaders. Since day one I just downloaded the files from the software catalog by hand. (I just got beta 4 this way.) If anybody else wants to know how to do that...


1. Download the software catalog. This year's is https://swscan.apple.com/content/ca...n-lion-snowleopard-leopard.merged-1.sucatalog but they always follow the same pattern. Next year's will just be ...index-10.15seed-10.15-10.14... so you can do what I do and grab a copy the moment it's released to developers without waiting for somebody to upload the beta access utility.

2. Open it in a text editor.

3. Search for InstallAssistantAuto.smd and go to the last instance of that.

4. From the point you're at, find the next instance of RecoveryHDMetaDmg.pkg and download that link.

5. Do the same for InstallESDDmg.pkg and InstallAssistantAuto.pkg. They should all be close together inside a "Packages" dict.

6. Extract the contents of the packages and the payload of InstallAssistantAuto.pkg (use a pbzx parser). You should end up with the install app, InstallESD.dmg, and RecoveryHDMeta.dmg.

7. Show package contents on the app and go to Contents/SharedSupport. Copy InstallESD.dmg into here.

8. Mount RecoveryHDMeta.dmg and copy the contents of the virtual disk into SharedSupport too.


These steps, without fail since at least macOS Sierra, will produce a functioning copy of the install app without needing an Apple ID, developer ID, or supported Mac.

Since there are now automatic download scripts, there's no real reason to follow these steps. I figured I'd share them for academic purposes only, if anyone wants to make their own automated downloader or whatever.

Edit: I've never actually looked at the code for the automated downloaders. I assume that they use this same process, though.
Click to expand...
Can I download the Sierra or El Capitan installer somehow? I can't find either them in the software catalog.
 
  • Like
Reactions: TimothyR734
Thanks @jackluke! I am now able to boot into Recovery by pressing CMD+R at the startup.

Unfortunately I was unable to get rid of the "ghost" EFI Boot in the boot menu by running commands:
gpt remove -i 1 /dev/disk0
gpt add -b 40 -i 1 -s 409600 -t efi /dev/disk0

I successfully used these commands to get rid of the "ghost" EFI Boot in the past before I patched the ROM.
I guess patching the ROM did came at a price, unless there is another safe way to get rid of the EFI Boot in the boot menu. It would be nice to completely tidy up my APFS boot. Any ideas welcome!
 
  • Like
Reactions: TimothyR734 and jackluke
DaniloGeekDude said:
@jackluke,

There is no AppleIntelHD3000GraphicsGLDriver.kext on the /S/L/E folder. However, it does have a AppleIntelHD3000GraphicsGLDriver.bundle

Are those the same? Thank you.

EDIT: I did find these entries on Info.plist under /Contents of the bundle.

<string>AppleIntelHD3000GraphicsGLDriver</string>
<key>CFBundleGetInfoString</key>
<string>AppleIntelHD3000GraphicsGLDriver 10.4.14</string>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AppleIntelHD3000GraphicsGLDriver</string>

So my follow-up question --- is the bundle file the one I need to rename? Thanks.
Click to expand...

Yes, essentially .bundle and .kext mean the same thing, a kext after-all is bundle package of plist, binaries and resources, so just rename .bundle to .bundle2 and upon @ASentientBot's suggestion you should be able to boot w/o acceleration anyway.
[doublepost=1549102333][/doublepost]
avz said:
Thanks @jackluke! I am now able to boot into Recovery by pressing CMD+R at the startup.

Unfortunately I was unable to get rid of the "ghost" EFI Boot in the boot menu by running commands:
gpt remove -i 1 /dev/disk0
gpt add -b 40 -i 1 -s 409600 -t efi /dev/disk0

I successfully used these commands to get rid of the "ghost" EFI Boot in the past before I patched the ROM.
I guess patching the ROM did came at a price, unless there is another safe way to get rid of the EFI Boot in the boot menu. It would be nice to completely tidy up my APFS boot. Any ideas welcome!
Click to expand...

I guess you're completely right with those "gpt commands", the APFS ROM patch I believe creates a semi-permanent EFI ghost residual (at EFI ROM level?), at the moment I don't know another safe way to remove, and consider that even those your correct commands, if done improperly could break the whole gpt disk structure.
 
  • Like
Reactions: TimothyR734, DaniloGeekDude and avz
10.14.4 Beta 1 is funny #LoL
(Sorry, on a hack mach --the only one in my hand #atm that having IntelHD 1st Gen / Arrandale gfx).

My PC BIOS has "Display Setting: Auto & LCD Only"). Using exactly same config, AppleIntelHDGraphics* etc as 10.14.3, with LCD Only = Stuck on "IOLock blah blah (not remember exactly)", it never reach LoginUI. With "Display: Auto" it reaches LoginUI - Desktop, but having WhiteScreen (I'm pretty sure gfx / igpu is working, system is up & running, Brightness Fn+Keys, Volume keys are also working with notif sound heard).

Prematurely assummed but it seems, the issue is related to Display (or screen, LinkWidth, or Framebuffer) and not OpenGL related to gfx accel as my prev. report, it's still working on NVDA Fermi. I've tried various AppleIntelHDGraphics* from 10.12 upto 10.13 with similar results.

Using SkyLight, CoreDisplay, CoreGraphics, DisplayServices, IOAccel, OpenCL/GL frameworks from 10.14.3.. dependencies are satisfied on my case, but still.. it's still unable to reach LoginUI #LoL.. will try again with diff. methods. Oh ya, my mach (though it' s h*tosh) is using vanilla system files on LE/SLE except AppleIntelHDGraphics since they're missing from 10.14).
 
  • Like
Reactions: TimothyR734, jackluke and ASentientBot
Hi,
Great ... my old iMac 24" early 2009 is running very well under Mojave 10.14.3
No problem.
Thanks a lot

captur10.jpg
 
  • Like
Reactions: TimothyR734, olad and Badruzeus
0403979 said:
@jackluke I saw a tutorial by you to make the apfs recovery partition show in the disk selection menu at boot. I can’t find it, could you link me to it please?
Click to expand...

I did only for HFS installation, APFS scheme is ultra hidden, I have attempted but didn't succeed, only way to show the hidden APFS partitions is through Refind, the default apple startup manager won't show the APFS Recovery but only with CMD+R.
 
  • Like
Reactions: FarmerBob, TimothyR734 and ASentientBot
jackluke said:
I did only for HFS installation, APFS scheme is ultra hidden, I have attempted but didn't succeed, only way to show the hidden APFS partitions is through Refind, the default apple startup manager won't show the APFS Recovery but only with CMD+R.
Click to expand...
Ah alright. Could you link me to the HFS one?
 
  • Like
Reactions: TimothyR734
I’ve been running Mojave Patcher for several months on my Early 2011 13 inch MacBook Pro. It’s was running Ok for a while but I’ve been having some graphic anomalies and after the last Mojave update it won’t boot so I’ve decided to revert back to High Sierra. I backed up High Sierra with Time Machine to an external Hard Drive but when I hold down Command + R to boot to the external drive I get the the Circle with the line through it.

Can someone please let me know how I can boot to the external drive? Thanks.
 
  • Like
Reactions: TimothyR734
cosrocket said:
I’ve been running Mojave Patcher for several months on my Early 2011 13 inch MacBook Pro. It’s was running Ok for a while but I’ve been having some graphic anomalies and after the last Mojave update it won’t boot so I’ve decided to revert back to High Sierra. I backed up High Sierra with Time Machine to an external Hard Drive but when I hold down Command + R to boot to the external drive I get the the Circle with the line through it.

Can someone please let me know how I can boot to the external drive? Thanks.
Click to expand...

Many reported incompatibility with the latest Mojave update, from your point it's not simple to fix the Recovery unless you can boot with CMD+S, otherwise use the dosdude1's Mojave Installer as your Time-machine Recovery holding alt-option after the power-on and booting from the USB thumb drive.
[doublepost=1549130458][/doublepost]
0403979 said:
Ah alright. Could you link me to the HFS one?
Click to expand...

Making HFS Recovery HD available at startup manager
 
  • Like
Reactions: TimothyR734
ASentientBot said:
The UI animations are fine on my GeForce 320M (mid-2010 MacBook here), no worse than on High Sierra. The only graphical issues I've noticed are the ones fixed by @pkouame's patch.

@lorehaze, are you sure you have full acceleration? Do you have transparency of the Dock and menubar? If not, try reinstalling the legacy graphics patch and rebuilding the prelinkedkernel. You might be running in software rendering mode which'd explain the slowness.
Click to expand...
well thoose animations are working flawlessly, but I really feel sluggish the whole system under Mojave, high Sierra seems so snappy
 
  • Like
Reactions: TimothyR734
Has anyone else experienced problems waking from sleep? On my 2008 MacPro 3,1 - If the computer goes to sleep, and I wake it up later the screen just stays black and I have to hard restart it. If I put it to sleep, and wake it up a few seconds later SOMETIMES it wakes up, but usually it is the same affect.
Its running a macvidcards GTX 780 Ti, so that should rule out any graphic driver issues. The event log shows a million crashes at the same time as I wake it up. I don't have it in front of me so I don't know what exactly is crashing. I think login UI. This has happened ever since I put mojave on it, but has gotten way worse after 10.14.3.
 
  • Like
Reactions: TimothyR734
jackluke said:
Yes, essentially .bundle and .kext mean the same thing, a kext after-all is bundle package of plist, binaries and resources, so just rename .bundle to .bundle2 and upon @ASentientBot's suggestion you should be able to boot w/o acceleration anyway.
[doublepost=1549102333][/doublepost]

I guess you're completely right with those "gpt commands", the APFS ROM patch I believe creates a semi-permanent EFI ghost residual (at EFI ROM level?), at the moment I don't know another safe way to remove, and consider that even those your correct commands, if done improperly could break the whole gpt disk structure.
Click to expand...

Thanks @jackluke

Now I am able to login to my beta 10.14.4 MBAir, 2011 by renaming the bundle file.

Screen Shot 2019-02-02 at 12.26.03 PM.png

You also mentioned "without acceleration". How can I verify or test the effects of "no acceleration"?
 
Last edited:
  • Like
Reactions: TimothyR734, jackluke and ASentientBot
avz said:
If I were you I would do a fresh start. I would clean install the 10.14.3 on APFS formated drive, making sure it is the only partition on the drive. And then go from here. After you run the tool you might get a drop down menu with multiple definitions for your EEPROM. And here can get very tricky as you must select the correct one(which can involve looking up the chip on your logic board). If you are not presented with a choice of multiple definitions, the procedure should be straightforward.
Click to expand...

That worked. Thanks for the direction
 
  • Like
Reactions: TimothyR734 and avz
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back