macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

I tried writing that command in the terminal but it still doesn't work. Nothing has changed replacing files or with that command

These are the steps I knew, cannot go further.
[doublepost=1538479417][/doublepost]

Delete all data from Recovery and try to recreate it on MacBook Pro 7.1 but it did not work, it continues with a forbidden symbol when pressing CMD + R

I created a new container named Recovery by Disk Utility and I cloned the patched pendrive, it occupied 8GB, I would like to delete the Recovery container (default) that has been empty, already tried anyway and does not leave, it is only as an unwanted entry, without any serventia.

Agree, APFS scheme is very particular especially in Recovery part, however you can clone the USB Mojave Installer as you done and you'll have a custom recovery lets say, even the HighSierra Recovery is good in this scope I used that BaseSystem.dmg infact.

To avoid "prohibitory symbol" you should impart the "-no_compat_check" inside the BaseSystem.dmg but I can't mess with com.apple.boot plist

 

[yeiyei0891]

CCC (Carbon Copy Cloner) 5.1.5

you created a new partition o volume?
[doublepost=1538480658][/doublepost]

These are the steps I knew, cannot go further.
[doublepost=1538479417][/doublepost]

Agree, APFS scheme is very particular especially in Recovery part, however you can clone the USB Mojave Installer as you done and you'll have a custom recovery lets say, even the HighSierra Recovery is good in this scope I used that BaseSystem.dmg infact.

To avoid "prohibitory symbol" you should impart the "-no_compat_check" inside the BaseSystem.dmg but I can't mess with com.apple.boot plist

and it's not possible clone the USB Mojave Installer inside the Recovery Partition instead of creating a new container????

 

[jackluke]

you created a new partition o volume?
[doublepost=1538480658][/doublepost]

and it's not possible clone the USB Mojave Installer inside the Recovery Partition instead of creating a new container????

Creating a Volume inside APFS scheme is less invasive, so I suggest a Volume, and yes it could be possible to enlarge the Recovery container, however is a bit tricky, so use a new container of 8-9 GB, leave the APFS Recovery there, it's small less than 600 MB, not a big loss of space.

 

[webg3]

You can recover all the space used by the default recovery partition, but you can not delete it, it's part of the system.

 

[whazzup]

Did you follow step 8, 9, 10, 11? -> (http://dosdude1.com/mojave/)

Yes I did every time I try to re-install.

From your previous post, you have a Macbook Pro 17 Early-2011 dual GPUs (AMD 6xxx and IntelHD3000), i5/i7 cpu Intel Chipset you don't need the C2D fix and probably neither the USB fix, I guess you should try to re-install Mojave and boot without the "Legacy Video Card Patch" applied.

Or without reinstalling try this, single user mode, after power-on hold CMD+S until you reach a Mojave Terminal and type:

fsck -fy
mount -uw /
cd /System/Library/Extensions/
mv AMDRadeonX3000.kext AMDRadeonX3000.kext2
reboot

Thanks for your advice, I've done re-install Mojave, reboot back to installer drive, and @dosdude1 's Post Install for Macbook 8,3 (with unchecked "Legacy Video Card Patch").

The result is unable boot to OS, halfway loading bar and then it directly shut down.

Any other suggestion?

 

[tiddlywinks]

iMac Late 2009 27" Core i5 2.66GHz:
I used an internal partition (14GB) to install the patcher. On inspection it had a couple of .dmg files. (?)
Took a long time to install on a FW drive but when rebooted it always booted from the patcher drive?
Made a USB patcher but got the grey no-entry sign on USB boot . The USB had no .dmg files?
So I went back to remake the patcher on the internal drive and no .dmg files??
It installed ok, took a long time but running well as can be expected on FW.
Don’t like the “bin” or the challenging similar to Vista when doing ‘naughty’ stuff.
Just waiting for 10.14.1 to see what happens then CCC to my internal SSD.
Thanks dosbloke.

 

[yeiyei0891]

You can recover all the space used by the default recovery partition, but you can not delete it, it's part of the system.

I created other volume and cloned USB there. Works. I will not touch the recovery partition for now.

And other question:
I'm using your Light mode scripts and now dock, side bar is ok, but the background with a lot apps isn't ok, background of volumen or brightness, controls in VLC have a gray color instead of their original color. Does this happen to you too?

 

[jackluke]

Yes I did every time I try to re-install.


Thanks for your advice, I've done re-install Mojave, reboot back to installer drive, and @dosdude1 's Post Install for Macbook 8,3 (with unchecked "Legacy Video Card Patch").

The result is unable boot to OS, halfway loading bar and then it directly shut down.

Any other suggestion?

Ok had similar issue with an Intel Chipset "Sandy Bridge" mac, I guess you have to replace all the 5 IOUSB*** kext, this fixed to me, I mean you need 5 IOUSB*** untouched kext from HighSierra copying into your Mojave/S/L/E/ and fix permissions, rebuild kextcache.

 

[webg3]

If something strange (gray) appears, it is the fault of the Finder that sometimes does not comply with the configuration. need to reapply so I created the light mode and dark mode scripts in addition to LightScript and now DarkScript in order to make things easier. yeiyei0891

 

[yeiyei0891]

This patch in light mode is the same as reducing transparency in System Preferences, but keeping some elements with vibration and some transparency.

Dock
Notification Center

The rest is all opaque, because transparency reduction is applied

I made it to be nice and the guilt of these applications to be without transparency is because they are connected to the Finder, it is responsible for a lot of things, including the menus, so in order not to look greedy, I had to choose to lose the transparency of the others.

If something strange (gray) appears, it is the fault of the Finder that sometimes does not comply with the configuration. need to reapply so I created the light mode and dark mode scripts in addition to LightScript and now DarkScript in order to make things easier.

Is there no way to fix the sidebar and the status bar in Finder and leave the rest as it is by default?

 

[webg3]

Is there no way to fix the sidebar and the status bar in Finder and leave the rest as it is by default?

Wait for the final solution (@pkouame is working on it.)

LightScript and DarkScript are temporary while there is nothing better.

 

[whazzup]

Ok had similar issue with an Intel Chipset "Sandy Bridge" mac, I guess you have to replace all the 5 IOUSB*** kext, this fixed to me, I mean you need 5 IOUSB*** untouched kext from HighSierra copying into your Mojave/S/L/E/ and fix permissions, rebuild kextcache.

If you don't mind, can you give detailed steps about this? Because I'm newbie about kext / driver.

But as far as I could get from your reply, I have to re-install High Sierra, copy untouched kext, then re-install Mojave and paste the kext ?

 

[ASentientBot]

Trying to get up and running on a Mac Pro 2008, but I'm having all kinds of grief with the video card. I have a Mac-flashed 7950 on board (which would show the boot screen), and the whole system worked fine with High Sierra and dosdude1's patch. So I figured I'd upgrade.

The initial upgrade appeared to go well. No errors during the initial install, got all the way through to the reboot. Then no boot screen. No display at all. Holding option on boot doesn't seem to let me choose to boot from the install USB, though I tried bless'ing it from SSH with no success either.

From SSH, I can watch /var/log/system.log which shows that WindowServer is repeatedly crashing. I had a look at the crash file for this, and it shows the following (abridged):

Process:               WindowServer [2338]
Path:                  /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier:            WindowServer
Version:               600.00 (336.80.6)
System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [2338]

Application Specific Information:
StartTime:2018-10-02 20:14:22
GPU:AMD
MetalDevice for accelerator(0x0): 0x7fbb7f409ec8 (MTLDevice: 0x7fbb8305be00)
MetalDevice for accelerator(0x343b): 0x7fbb7f719808 (MTLDevice: 0x7fbb8305be00)
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/NRP5@5/IOPP/PXS1@0/ATY,Hamachi@0/AMDFramebufferSI

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.AMDRadeonX4000GLDriver    0x000000014dac0089 glrATI_SI_InitMiscTextureInfo + 177
1   com.apple.AMDRadeonX4000GLDriver    0x000000014daf9d46 glrATI_SI_InitHardwareContext + 270
2   com.apple.AMDRadeonX4000GLDriver    0x000000014daab365 glrInitializeContext + 26
3   libGPUSupportMercury.dylib        0x00007fff497524a5 gldCreateContext + 1221
4   GLEngine                          0x00007fff37e06959 gliCreateContextWithShared + 691
5   com.apple.SkyLight                0x00007fff53cfb5ac slglsCreateContext + 247
6   com.apple.SkyLight                0x00007fff53dfeed9 initialize_display_context + 1794
7   com.apple.SkyLight                0x00007fff53dfe674 CGXInitializeGL + 18
8   com.apple.SkyLight                0x00007fff53e01613 WSInitialize + 3359
9   com.apple.SkyLight                0x00007fff53e960ae SLXServer + 1138
10  WindowServer                      0x000000010b15e4cc 0x10b15d000 + 5324
11  libdyld.dylib                     0x00007fff5adee085 start + 1

So it's crashing deep inside the driver for the display. But I don't think that explains why I've lost my boot screen. Did the installer try to update my display's BIOS? I've tried flicking the alternate bios switch on the card with no success.

Anybody else had any experience with this combination? Is there any way to get back to a working mac? Still have my 2016 MBP daily driver, but it'd be nice to get a desktop back too (or at least to a working state so I could sell it...)

I believe that AMDRadeonX4000GLDriver uses SSE4.2 instructions that your CPU does not have, but I'm not an expert on this topic and I don't want to scroll through a couple hundred pages looking for where it was mentioned. @dosdude1 is this correct?

 

[jackluke]

If you don't mind, can you give detailed steps about this? Because I'm newbie about kext / driver.

But as far as I could get from your reply, I have to re-install High Sierra, copy untouched kext, then re-install Mojave and paste the kext ?

Yes but not exactly, however before any other attempt, you should boot in verbose mode your current Mojave, after power-on hold CMD+V, keep holding until you see a verbose boot, then you should take a picture a couple of seconds before shutdown and post here so others can diagnosticate what's your issue, in rare cases the HardDisk is becoming faulty.

 

[whazzup]

Yes but not exactly, however before any other attempt, you should boot in verbose mode your current Mojave, after power-on hold CMD+V, keep holding until you see a verbose boot, then you should take a picture a couple of seconds before shutdown and post here so others can diagnosticate what's your issue, in rare cases the HardDisk is becoming faulty.

This I captured from the last second before shutdown.

 

[Starplayr]

I believe that AMDRadeonX4000GLDriver uses SSE4.2 instructions that your CPU does not have, but I'm not an expert on this topic and I don't want to scroll through a couple hundred pages looking for where it was mentioned. @dosdude1 is this correct?

Sort answer, AMD 7xxx series cards to not work in Mojave because your CPU does not have the right instruction set to use Apple’s AMD drivers.

Sell your 7950 or keep it as a backup for older OS’ like ELcapitan or Windows 10.

Get a Kepler based Mac video card.

If you need one that is flashable get. EVGA GTX 680 2G. I actually have some on hand that are flashed and work fine on the 3,1 and also have 5GT/s and bootscreen.

 

[jackluke]

This I captured from the last second before shutdown.

Yes, I confirm the issue could be still addressed replacing with 5 IOUSB***.kext from HighSierra, however, it seems your file-system is corrupted, try to boot now from single user mode, hold as you did before this time CMD+S then type:

fsck -fy
mount -uw /
reboot

if single user mode will shutdown your mac without giving chance to type, then you have to do this, boot from USB Mojave Installer, open DiskUtility, from the finder top bar View > Show All Devices, you have to use "First Aid" first on your main Disk (vendor name), then inside the Mojave Volume partition, do a twice "First Aid", then reboot again holding CMD+V and see if you pass some lines on verbose.

 

[whazzup]

Yes, I confirm the issue could be still addressed replacing with 5 IOUSB***.kext from HighSierra, however, it seems your file-system is corrupted, try to boot now from single user mode, hold as you did before this time CMD+S then type:

fsck -fy
mount -uw /
reboot

if single user mode will shutdown your mac without giving chance to type, then you have to do this, boot from USB Mojave Installer, open DiskUtility, from the finder top bar View > Show All Devices, you have to use "First Aid" first on your main Disk (vendor name), then inside the Mojave Volume partition, do a twice "First Aid", then reboot again holding CMD+V and see if you pass some lines on verbose.

I tried to CMD+S then I got a chance to type. "fsck -fy" gave feedback "Filesystem cannot be checked".
So, I move to boot USB Mojave Installer, do what you said, and here's the result :

 

[jackluke]

Here's the result :

I guess your SSD is faulty that string "filesystem cannot be checked" isn't a good sign, anyway have you tried to boot from USB Mojave Installer and open DiskUtility doing First Aid on your SSD ? Try it then reboot with CMD+S and see if it doesn't shutdown.

Another attempt I'd suggest is to re-install Mojave (if possible erase/format the current one) then without applying any Post-Install patch leave it booting with CMD+V after power-on.

 

[ASentientBot]

Sort answer, AMD 7xxx series cards to not work in Mojave because your CPU does not have the right instruction set to use Apple’s AMD drivers.

Sell your 7950 or keep it as a backup for older OS’ like ELcapitan or Windows 10.

Get a Kepler based Mac video card.

If you need one that is flashable get. EVGA GTX 680 2G. I actually have some on hand that are flashed and work fine on the 3,1 and also have 5GT/s and bootscreen.

I don't have the hardware to mess with, but why couldn't one just use the Sierra/High Sierra/El Capitan drivers on Mojave, as we do with nVidia Tesla and older AMD?

 

[whazzup]

I guess your SSD is faulty that string "filesystem cannot be checked" isn't a good sign, anyway have you tried to boot from USB Mojave Installer and open DiskUtility doing First Aid on your SSD ? Try it then reboot with CMD+S and see if it doesn't shutdown.

Another attempt I'd suggest is to re-install Mojave (if possible erase/format the current one) then without applying any Post-Install patch leave it booting with CMD+V after power-on.

Yes I tried to open DiskUtility then doing First Aid as you said. After that, reboot and CMD+S then I got a chance to type. "fsck -fy" gave feedback "Filesystem cannot be checked". Is it possible the SSD fault because I re-install Mojave several times and try to change format from APFS (which cannot boot to OS, as I described here #8723) to JHFS+ ?

Wait, I'm re-installing Mojave now.

 

[webg3]

Guys, this is my final version of Dark Mode in Mojave with a keyboard shortcut

Fixed problem change on Dark Mode to back to Light Mode (this would lose transparency in the Notification Center

I will modify post # 8354 on page 335 with the update.

 

[jackluke]

Yes I tried to open DiskUtility then doing First Aid as you said. After that, reboot and CMD+S then I got a chance to type. "fsck -fy" gave feedback "Filesystem cannot be checked". Is it possible the SSD fault because I re-install Mojave several times and try to change format from APFS (which cannot boot to OS, as I described here #8723) to JHFS+ ?

Wait, I'm re-installing Mojave now.

No, because your MBP early 2011 supports natively APFS file system, so it's the SSD faulty, you haven't done nothing wrong in re-installing and patching.

A last attempt, erase/format your SSD but not only the Mojave partition but the whole disk, then re-install Mojave without any patches and boot with CMD+V and see if you reach the Welcome Screen.

 

[whazzup]

No, because your MBP early 2011 supports natively APFS file system, so it's the SSD faulty, you haven't done nothing wrong in re-installing and patching.

A last attempt, erase/format your SSD but not only the Mojave partition but the whole disk, then re-install Mojave without any patches and boot with CMD+V and see if you reach the Welcome Screen.

Done re-install, without any patches. Here's the result :

 

[jackluke]

Done re-install, without any patches. Here's the result :

Yes expected, lets try one patch at once, boot from USB Mojave Installer, launch Terminal and type:
csrutil disable
nvram boot-args="-no_compat_check"
reboot

if you reach welcome screen but have no working trackpad and keyboard, then re-boot from the USB Mojave Installer, Post-Install and select only "USBOHCI support Patch" install and "Force cache rebuild".