macOS 10.14 Mojave on Unsupported Macs Thread

[Olivia88]

It's a known issue, @ASentientBot found a workaround in dropping the OpenGL feature, if you can isolate your Mojave booting only to IntelHD3000 then boot holding CMD+S single user mode and rename the /S*/L*/E*/AppleIntelHD3000GraphicsGLDriver.bundle

into AppleIntelHD3000GraphicsGLDriver.bundle2

In this way at next reboot the OpenGL kext of your GPU won't be loaded in the prelinkedkernel and you can reach the desktop.
[doublepost=1549393692][/doublepost]

There is, post here the result from your Terminal:

diskutil apfs list

Ok, so it wasn't even finished updating. But it did finish now and went straight to the login screen. No gpu acceleration ofc.

Renaming AppleIntelHD3000GraphicsGLDriver.bundle back, and its doing the same thing again unfortunately, both with the Amd and Intel gpu.

Thanks Jackluke.
[doublepost=1549395997][/doublepost]

I don't understand much about the OpenGL issue but I am wondering if GeForce 9400M is going to have the same issues as IntelHD3000?

Yes, it seems so.

 

[jackluke]

APFS Recovery is working great! I used DU and did Time Machine system restore to my MacBook5,1's original 160GB HDD connected externally via SATA to USB adapter. The original 160GB HDD is still going strong after 10 years of use.

I don't understand much about the OpenGL issue but I am wondering if GeForce 9400M is going to have the same issues as IntelHD3000?

Yes, I'd say OpenGL acceleration looks like a common issue since 10.14.4 beta testing, and Geforce 9400M belonging to the "Nvidia Tesla Family" is affected too.

Spoiler: Nvidia Tesla list

GPU Tesla GeForce:



NVIDIA GeForce 205

NVIDIA GeForce 210

NVIDIA GeForce 305M

NVIDIA GeForce 310

NVIDIA GeForce 310M

NVIDIA GeForce 315

NVIDIA GeForce 315M

NVIDIA GeForce 320M

NVIDIA GeForce 405

NVIDIA GeForce 505

NVIDIA GeForce 8100 / nForce 720a

NVIDIA GeForce 8200

NVIDIA GeForce 8200M

NVIDIA GeForce 8200M G

NVIDIA GeForce 8200M G

NVIDIA GeForce 8300

NVIDIA GeForce 8300 GS

NVIDIA GeForce 8300 GS

NVIDIA GeForce 8400

NVIDIA GeForce 8400 GS

NVIDIA GeForce 8400 SE

NVIDIA GeForce 8400GS

NVIDIA GeForce 8400M G

NVIDIA GeForce 8400M GS

NVIDIA GeForce 8400M GT

NVIDIA GeForce 8500 GT

NVIDIA GeForce 8600 GS

NVIDIA GeForce 8600 GT

NVIDIA GeForce 8600 GTS

NVIDIA GeForce 8600M GS

NVIDIA GeForce 8600M GT

NVIDIA GeForce 8700M GT

NVIDIA GeForce 8800 GS

NVIDIA GeForce 8800 GT

NVIDIA GeForce 8800 GTS

NVIDIA GeForce 8800 GTS 512

NVIDIA GeForce 8800 GTX

NVIDIA GeForce 8800 Ultra

NVIDIA GeForce 8800M GTS

NVIDIA GeForce 8800M GTX

NVIDIA GeForce 9100

NVIDIA GeForce 9100M G

NVIDIA GeForce 9200

NVIDIA GeForce 9200M GS

NVIDIA GeForce 9300

NVIDIA GeForce 9300 / nForce 730i

NVIDIA GeForce 9300 GE

NVIDIA GeForce 9300 GS

NVIDIA GeForce 9300 GS

NVIDIA GeForce 9300 SE

NVIDIA GeForce 9300M G

NVIDIA GeForce 9300M GS

NVIDIA GeForce 9300M GS

NVIDIA GeForce 9400

NVIDIA GeForce 9400 GT

NVIDIA GeForce 9400M

NVIDIA GeForce 9400M G

NVIDIA GeForce 9500 GS

NVIDIA GeForce 9500 GT

NVIDIA GeForce 9500M G

NVIDIA GeForce 9500M GS

NVIDIA GeForce 9600 GS

NVIDIA GeForce 9600 GSO

NVIDIA GeForce 9600 GSO 512

NVIDIA GeForce 9600 GT

NVIDIA GeForce 9600 S

NVIDIA GeForce 9600M GS

NVIDIA GeForce 9600M GT

NVIDIA GeForce 9650 S

NVIDIA GeForce 9650M GS

NVIDIA GeForce 9650M GT

NVIDIA GeForce 9700 S

NVIDIA GeForce 9700M GT

NVIDIA GeForce 9700M GTS

NVIDIA GeForce 9800 GT

NVIDIA GeForce 9800 GTX/9800 GTX+

NVIDIA GeForce 9800 GTX+

NVIDIA GeForce 9800 GX2

NVIDIA GeForce 9800M GS

NVIDIA GeForce 9800M GT

NVIDIA GeForce 9800M GTS

NVIDIA GeForce 9800M GTX

NVIDIA GeForce G 103M

NVIDIA GeForce G 105M

NVIDIA GeForce G 110M

NVIDIA GeForce G100

NVIDIA GeForce G102M

NVIDIA GeForce G105M

NVIDIA GeForce G210

NVIDIA GeForce G210M

NVIDIA GeForce GT 120

NVIDIA GeForce GT 120M

NVIDIA GeForce GT 130

NVIDIA GeForce GT 130M

NVIDIA GeForce GT 140

NVIDIA GeForce GT 220

NVIDIA GeForce GT 220M

NVIDIA GeForce GT 230

NVIDIA GeForce GT 230M

NVIDIA GeForce GT 240

NVIDIA GeForce GT 240M

NVIDIA GeForce GT 320

NVIDIA GeForce GT 320M

NVIDIA GeForce GT 325M

NVIDIA GeForce GT 330

NVIDIA GeForce GT 330M

NVIDIA GeForce GT 335M

NVIDIA GeForce GT 340

NVIDIA GeForce GT 415

NVIDIA GeForce GTS 160M

NVIDIA GeForce GTS 240

NVIDIA GeForce GTS 250

NVIDIA GeForce GTS 250M

NVIDIA GeForce GTS 350M

NVIDIA GeForce GTS 360M

NVIDIA GeForce GTX 260

NVIDIA GeForce GTX 260M

NVIDIA GeForce GTX 275

NVIDIA GeForce GTX 280

NVIDIA GeForce GTX 280M

NVIDIA GeForce GTX 285

NVIDIA GeForce GTX 285M

NVIDIA GeForce GTX 295

NVIDIA ION

NVIDIA ION LE

NVIDIA nForce 730a

NVIDIA nForce 750a SLI

NVIDIA nForce 760i SLI

NVIDIA nForce 980a/780a SLI

 

[jbarley]

It's ok but I guess I made many other (annoying) posts about that, there is another important step to override the platform support hardware check (typically prohibitory symbol guilty) and needs to edit inside the APFS Recovery the com.apple.Boot.plist
adding next to the "BaseSystem.dmg" string this: "BaseSystem.dmg -no_compat_check -v"

In this way at 99% of the times you can pass the prohibitory CMD+R symbol.

Just to be clear, this is my com.apple.Boot.plist.
Where exactly do I need to add this "BaseSystem.dmg -no_compat_check -v" ?

 

[timthomason]

hello folks.. great project.. I just installed the 10.4.4 beta using the script from pages before..I started the computer, and first message was something wrong send to apple. umm no. it is a EFIcheck.dump file.
can anyone tell me what it means?

 

[jbarley]

It's a known issue, @ASentientBot found a workaround in dropping the OpenGL feature, if you can isolate your Mojave booting only to IntelHD3000 then boot holding CMD+S single user mode and rename the /S*/L*/E*/AppleIntelHD3000GraphicsGLDriver.bundle

into AppleIntelHD3000GraphicsGLDriver.bundle2

In this way at next reboot the OpenGL kext of your GPU won't be loaded in the prelinkedkernel and you can reach the desktop.
[doublepost=1549393692][/doublepost]

There is, post here the result from your Terminal:

diskutil apfs list

Last login: Tue Feb 5 11:52:44 on ttys000
MacPro-mojave:~ jbarley$ diskutil apfs list
APFS Container (1 found)
|
+-- Container disk4 B8078899-61BB-4AF2-9A36-0EE24D03A803
====================================================
APFS Container Reference: disk4
Size (Capacity Ceiling): 229847650304 B (229.8 GB)
Capacity In Use By Volumes: 23588827136 B (23.6 GB) (10.3% used)
Capacity Not Allocated: 206258823168 B (206.3 GB) (89.7% free)
|
+-< Physical Store disk1s2 B464B8A1-609B-4B27-AEAE-6FCA51019A12
| -----------------------------------------------------------
| APFS Physical Store Disk: disk1s2
| Size: 229847650304 B (229.8 GB)
|
+-> Volume disk4s1 2D8D5DE7-8850-4967-81FA-44DD77324875
| ---------------------------------------------------
| APFS Volume Disk (Role): disk4s1 (No specific role)
| Name: Mojave (Case-insensitive)
| Mount Point: /
| Capacity Consumed: 22875131904 B (22.9 GB)
| FileVault: No
|
+-> Volume disk4s2 73C39A23-64ED-4B50-A5E4-9D817FF86793
| ---------------------------------------------------
| APFS Volume Disk (Role): disk4s2 (Preboot)
| Name: Preboot (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 45121536 B (45.1 MB)
| FileVault: No
|
+-> Volume disk4s3 6BF12FB1-A129-4EB1-B397-8633C6FE19C8
| ---------------------------------------------------
| APFS Volume Disk (Role): disk4s3 (Recovery)
| Name: Recovery (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 532062208 B (532.1 MB)
| FileVault: No
|
+-> Volume disk4s4 308BE4D2-343C-4253-9267-9CEFAB2DB9BB
---------------------------------------------------
APFS Volume Disk (Role): disk4s4 (VM)
Name: VM (Case-insensitive)
Mount Point: /private/var/vm
Capacity Consumed: 20480 B (20.5 KB)
FileVault: No
MacPro-mojave:~ jbarley$

 

[jackluke]

Just to be clear, this is my com.apple.Boot.plist.
Where exactly do I need to add this "BaseSystem.dmg -no_compat_check -v" ?

View attachment 820138

Exactly in this way:
<string>root-dmg=file:///2D8D5DE7-8850-4967-81FA-44DD77324875/BaseSystem.dmg -no_compat_check -v </string>

insert without quotes of course and save the com.apple.Boot.plist

At next reboot you should boot with CMD+R, if it works then you can drop the "-v" re-editing the com.apple.Boot.plist, showing the Apple Logo with progress bar instead of verbose code lines, they're needed only for diagnostics.

 

[Olivia88]

I tried updating my 2010 15 mbp too, just to see if it would behave even slightly different, but its not.
Its doing exactly the same as my mbp 15 2011.

 

[jbarley]

Exactly in this way:
<string>root-dmg=file:///2D8D5DE7-8850-4967-81FA-44DD77324875/BaseSystem.dmg -no_compat_check -v </string>

insert without quotes of course and save the com.apple.Boot.plist

At next reboot you should boot with CMD+R, if it works then you can drop the "-v" re-editing the com.apple.Boot.plist, showing the Apple Logo with progress bar instead of verbose code lines, they're needed only for diagnostics.

Got it. Everything is as it should be now with full access to Recovery if or when needed.
Thanks to jackluke for making this happen and flygbuss for pointing me in the right direction.

 

[jackluke]

I tried updating my 2010 15 mbp too, just to see if it would behave even slightly different, but its not.
Its doing exactly the same as my mbp 15 2011.

Predictable, not 100% sure if your MBP 2010 has dual graphics or not, but booting as you already know from single user mode, rename both AppleIntelHDGraphicsGLDriver.bundle and GeForceTeslaGLDriver.bundle in *.bundle2 as ASentientBot pointed some pages ago you can use 10.14.4 w/o acceleration but at least it's the best workaround by now, or as you pointed before, better to stay with 10.14.3 .

 

[DuncanGarp]

Yes, I'd say OpenGL acceleration looks like a common issue since 10.14.4 beta testing, and Geforce 9400M belonging to the "Nvidia Tesla Family" is affected too.

Spoiler: Nvidia Tesla list

GPU Tesla GeForce:



NVIDIA GeForce 205

NVIDIA GeForce 210

NVIDIA GeForce 305M

NVIDIA GeForce 310

NVIDIA GeForce 310M

NVIDIA GeForce 315

NVIDIA GeForce 315M

NVIDIA GeForce 320M

NVIDIA GeForce 405

NVIDIA GeForce 505

NVIDIA GeForce 8100 / nForce 720a

NVIDIA GeForce 8200

NVIDIA GeForce 8200M

NVIDIA GeForce 8200M G

NVIDIA GeForce 8200M G

NVIDIA GeForce 8300

NVIDIA GeForce 8300 GS

NVIDIA GeForce 8300 GS

NVIDIA GeForce 8400

NVIDIA GeForce 8400 GS

NVIDIA GeForce 8400 SE

NVIDIA GeForce 8400GS

NVIDIA GeForce 8400M G

NVIDIA GeForce 8400M GS

NVIDIA GeForce 8400M GT

NVIDIA GeForce 8500 GT

NVIDIA GeForce 8600 GS

NVIDIA GeForce 8600 GT

NVIDIA GeForce 8600 GTS

NVIDIA GeForce 8600M GS

NVIDIA GeForce 8600M GT

NVIDIA GeForce 8700M GT

NVIDIA GeForce 8800 GS

NVIDIA GeForce 8800 GT

NVIDIA GeForce 8800 GTS

NVIDIA GeForce 8800 GTS 512

NVIDIA GeForce 8800 GTX

NVIDIA GeForce 8800 Ultra

NVIDIA GeForce 8800M GTS

NVIDIA GeForce 8800M GTX

NVIDIA GeForce 9100

NVIDIA GeForce 9100M G

NVIDIA GeForce 9200

NVIDIA GeForce 9200M GS

NVIDIA GeForce 9300

NVIDIA GeForce 9300 / nForce 730i

NVIDIA GeForce 9300 GE

NVIDIA GeForce 9300 GS

NVIDIA GeForce 9300 GS

NVIDIA GeForce 9300 SE

NVIDIA GeForce 9300M G

NVIDIA GeForce 9300M GS

NVIDIA GeForce 9300M GS

NVIDIA GeForce 9400

NVIDIA GeForce 9400 GT

NVIDIA GeForce 9400M

NVIDIA GeForce 9400M G

NVIDIA GeForce 9500 GS

NVIDIA GeForce 9500 GT

NVIDIA GeForce 9500M G

NVIDIA GeForce 9500M GS

NVIDIA GeForce 9600 GS

NVIDIA GeForce 9600 GSO

NVIDIA GeForce 9600 GSO 512

NVIDIA GeForce 9600 GT

NVIDIA GeForce 9600 S

NVIDIA GeForce 9600M GS

NVIDIA GeForce 9600M GT

NVIDIA GeForce 9650 S

NVIDIA GeForce 9650M GS

NVIDIA GeForce 9650M GT

NVIDIA GeForce 9700 S

NVIDIA GeForce 9700M GT

NVIDIA GeForce 9700M GTS

NVIDIA GeForce 9800 GT

NVIDIA GeForce 9800 GTX/9800 GTX+

NVIDIA GeForce 9800 GTX+

NVIDIA GeForce 9800 GX2

NVIDIA GeForce 9800M GS

NVIDIA GeForce 9800M GT

NVIDIA GeForce 9800M GTS

NVIDIA GeForce 9800M GTX

NVIDIA GeForce G 103M

NVIDIA GeForce G 105M

NVIDIA GeForce G 110M

NVIDIA GeForce G100

NVIDIA GeForce G102M

NVIDIA GeForce G105M

NVIDIA GeForce G210

NVIDIA GeForce G210M

NVIDIA GeForce GT 120

NVIDIA GeForce GT 120M

NVIDIA GeForce GT 130

NVIDIA GeForce GT 130M

NVIDIA GeForce GT 140

NVIDIA GeForce GT 220

NVIDIA GeForce GT 220M

NVIDIA GeForce GT 230

NVIDIA GeForce GT 230M

NVIDIA GeForce GT 240

NVIDIA GeForce GT 240M

NVIDIA GeForce GT 320

NVIDIA GeForce GT 320M

NVIDIA GeForce GT 325M

NVIDIA GeForce GT 330

NVIDIA GeForce GT 330M

NVIDIA GeForce GT 335M

NVIDIA GeForce GT 340

NVIDIA GeForce GT 415

NVIDIA GeForce GTS 160M

NVIDIA GeForce GTS 240

NVIDIA GeForce GTS 250

NVIDIA GeForce GTS 250M

NVIDIA GeForce GTS 350M

NVIDIA GeForce GTS 360M

NVIDIA GeForce GTX 260

NVIDIA GeForce GTX 260M

NVIDIA GeForce GTX 275

NVIDIA GeForce GTX 280

NVIDIA GeForce GTX 280M

NVIDIA GeForce GTX 285

NVIDIA GeForce GTX 285M

NVIDIA GeForce GTX 295

NVIDIA ION

NVIDIA ION LE

NVIDIA nForce 730a

NVIDIA nForce 750a SLI

NVIDIA nForce 760i SLI

NVIDIA nForce 980a/780a SLI

My MBP5,3 has NVIDIA GeForce 9600GM GT 512 MB.

Which one of these GLDriver.bundle should I rename?
GeForceGLDriver.bundle
or
GeForceTeslaGLDriver.bundle

Thanks.

 

[flygbuss]

This might not be relevant but my supported MBP 2012 seemed to upgrade it's firmware (apple logo with the thicker status bar) while updating to the second beta today.

 

[jackluke]

My MBP5,3 has NVIDIA GeForce 9600GM GT 512 MB.

Which one of these GLDriver.bundle should I rename?
GeForceGLDriver.bundle
or
GeForceTeslaGLDriver.bundle

Thanks.

Not sure I guess the Tesla one but if you rename both it doesn't break nothing and you can still boot.

 

[Olivia88]

Predictable, not 100% sure if your MBP 2010 has dual graphics or not, but booting as you already know from single user mode, rename both AppleIntelHDGraphicsGLDriver.bundle and GeForceTeslaGLDriver.bundle in *.bundle2 as ASentientBot pointed some pages ago you can use 10.14.4 w/o acceleration but at least it's the best workaround by now, or as you pointed before, better to stay with 10.14.3 .

It has both Nvidia and intel hd first gen. I thought I'd try because I had some time on my hands, and more documented cases doesn't hurt.

I don't think I'll mess with it any further now until or if someone has any idea how to rectify the issue.

If anyone wants me to try anything just say so, I left both my machines as they were after the failed update.

 

[ragingfighter1]

View attachment 797301 View attachment 797302 View attachment 797303 View attachment 797304
View attachment 797317 View attachment 797306 View attachment 797308View attachment 797311

​

​

Current Hardware Support Status:

• Machine Support
  • Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
    • MacPro3,1
    • MacPro4,1
    • iMac8,1
    • iMac9,1
    • iMac10,x
    • iMac11,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
    • iMac12,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
    • MacBookPro4,1
    • MacBookPro5,x
    • MacBookPro6,x
    • MacBookPro7,1
    • MacBookPro8,x
  • Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
    • MacBookAir2,1
    • MacBookAir3,x
    • MacBookAir4,x
    • MacBook5,1
  • Early-2009 or newer Mac Mini or white MacBook:
    • Macmini3,1
    • Macmini4,1
    • Macmini5,x
    • MacBook5,2
    • MacBook6,1
    • MacBook7,1
  • Early-2008 or newer Xserve:
    • Xserve2,1
    • Xserve3,1

• Video Card Support
  • Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)
  • Pre-Metal Nvidia video cards (GeForce 5xx series and older, i.e. 8600M(GT), 8800M(GT), 9400M, 9600M(GT), 320M)
  • Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)

Current Issues

• Minor Issues
  • Graphics anomalies: Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transparency as some systems with pre-metal AMD graphics render the dock in dark gray).
  • Built-in iSight cameras: Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.
  • Trackpad (MacBook5,2 affected only). Trackpad multi-finger gestures on the MacBook5,2 not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
• Major Issues
  • AMD Radeon HD 5xxx/6xxx series GPU acceleration: Currently, it is not possible to get full graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series GPU. Mojave will be almost UNUSABLE without graphics acceleration. This includes the 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these machines, you'll need to disable the AMD GPU (This will work on MacBook Pro 8,2 and 8,3 systems ONLY. You CANNOT disable the AMD GPU in an iMac.) Weird colors will also be produced when running Mojave with one of these video cards installed/enabled. To disable the AMD GPU on a 2011 MacBook Pro 8,2 or 8,3, follow the guide found here.
  • App Store Crashing: Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround. Safari may also experience crashes with certain kinds of embedded videos.
  • Early-2008 Mac Pro (MacPro3,1) GPU support: When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-compatible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are Nvidia cards, which work perfectly fine.
  • Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running Mojave. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.

Current Issues by Hardware

• Minor Issues
  • Graphics anomalies:
    • All machines
  • Built-in iSight camera:
    • All machines, hit or miss
  • Trackpad:
    • MacBook5,2
• Major Issues
  • AMD GPU acceleration:
    • All machines with a Radeon HD 5xxx or 6xxx series GPUs (these systems will be almost unusable when running Mojave. More details are located in the Current Issues section above.)
  • App Store Crashing:
    • All machines with Radeon HD 4xxx series GPUs
  • AMD GPU support:
    • MacPro3,1
  • Unsupported WiFi modules:
    • All machines with Broadcom BCM4321 WiFi modules

Installation:
To install on your machine, you can download and run the macOS Mojave Patcher application, which will let you download a copy of the latest installer app from Apple and create a bootable installer drive for use on unsupported Macs. It contains all the patches necessary to achieve the hardware support listed above. The installation guide can be found here and an installation guide video here.

APFS ROM Patcher:
Warning: This tool could irreversibly brick your EFI chip. Please exercise caution with machines that have multiple EEPROM definitions. Relevant information can be found here and here. The APFS ROM patcher can be found here. Use the password apfs to decrypt the ZIP.

Mojave Builds and Installer Versions (Developer Preview, Public Beta):

2018/06/04 - 2018/09/12 10.14.0 DP1 - DP11, PB1 - PB10

2018/06/04 DP1, build 18A293u, installer 14.0.08
2018/06/19 DP2, build 18A314h, installer 14.0.11
2018/06/26 PB1, build 18A314k, installer 14.0.11
2018/07/03 DP3, build 18A326g, installer 14.0.12
2018/07/06 PB2, build 18A326h, installer 14.0.12
2018/07/16 DP4, 2018/07/17 PB3, build 18A336e, installer 14.0.14
2018/07/30 DP5, 2018/07/31 PB4, build 18A347e, installer 14.0.15
2018/08/06 DP6, 2018/08/06 PB5, build 18A353d, installer 14.0.16
2018/08/13 DP7, 2018/08/13 PB6, build 18A365a, installer 14.0.17
2018/08/20 DP8, 2018/08/20 PB7, build 18A371a, installer 14.0.18
2018/08/27 DP9, 2018/08/27 PB8, build 18A377a, installer 14.0.20
2018/09/04 DP10, 2018/09/04 PB9, build 18A384a, installer 14.0.21
2018/09/12 DP11, 2018/09/12 PB10, build 18A389, installer 14.0.21​

2018/09/24 10.14.0 Final, build 18A391, installer 14.0.22
2018/09/25 - 2018/10/23 10.14.1 DP1 - DP5, PB1 - PB5 - do not install

2018/09/25 10.14.1 DP1, 2018/09/27 PB1, build 18B45d - do not install
2018/10/02 10.14.1 DP2, 2018/10/02 PB2, build 18B50c - do not install
2018/10/08 10.14.1 DP3, 2018/10/08 PB3, build 18B57c - do not install
2018/10/17 10.14.1 DP4, 2018/10/17 PB4, build 18B67a - do not install
2018/10/23 10.14.1 DP5, 2018/10/23 PB5, build 18B73a - do not install​

2018/10/30 10.14.1 Final, build 18B75, installer 14.1.0 - install from drive
2018/10/31 - 2018/11/28 10.14.2 DP1 - DP4, PB1 - PB4

2018/10/31 10.14.2 DP1, 2018/11/02 PB1, build 18C31g
2018/11/07 10.14.2 DP2, 2018/11/07 PB2, build 18C38b
2018/11/16 10.14.2 DP3, 2018/11/16 PB3, build 18C48a
2018/11/28 10.14.2 DP4, 2018/11/28 PB4, build 18C52a​

2018/12/05 10.14.2 Final, build 18C54, installer 14.2.2
2018/12/10 - 2019/01/11 10.14.3 DP1 - DP4, PB1 - PB4

2018/12/10 10.14.3 DP1, 2018/12/11 PB1, build 18D21c
2018/12/19 10.14.3 DP2, 2018/12/19 PB2, build 18D32a
2019/01/07 10.14.3 DP3, 2019/01/07 PB3, build 18D38a
2019/01/11 10.14.3 DP4, 2019/01/11 PB4, build 18D39a​

2019/01/21 10.14.3 Final, build 18D42, installer 14.3.2
2019/01/24 - 2019/02/04 10.14.4 DP1 - DP2, PB1

2019/01/24 10.14.4 DP1, 2019/01/28 PB1, build 18E174f - do not install
2019/02/04 10.14.4 DP2, build 18E184e - do not install​

Credits:
@dosdude1 - Developed macOS Mojave Patcher.
@parrotgeek1 - Developed LegacyUSBInjector, SIPManager, and NDRVShim. (Source Code)
@Czo - Developed SUVMMFaker. (Source Code)
@Badruzeus - Discovered that Sierra OpenGL drivers work in Mojave.
@ASentientBot - Fixed Nvidia kernel panic, Core 2 Duo kernel panic, and iSight.
@jackluke - Narrowed down cause of Core 2 Duo kernel panic.

Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.

[doublepost=1549411452][/doublepost]Not worth it to me System runs great without the newest OS not necessary

 

[jackluke]

hello folks.. great project.. I just installed the 10.4.4 beta using the script from pages before..I started the computer, and first message was something wrong send to apple. umm no. it is a EFIcheck.dump file.
can anyone tell me what it means?

Here explained:
https://www.macrumors.com/2017/09/25/macos-high-sierra-weekly-efi-security-check/

if you using a real mac hardware don't worry, if using a non-mac hardware just a bit of worry.
But if you can next time, try don't send nothing to them.

edit:
My wrong, you chose "No", right answer.

 

[timthomason]

Here explained:
https://www.macrumors.com/2017/09/25/macos-high-sierra-weekly-efi-security-check/

if you using a real mac hardware don't worry, if using a non-mac hardware just a bit of worry.
But if you can next time, try don't send nothing to them.

edit:
My wrong, you chose "No", right answer.

thank you. i read some other post sites that told me .

 

[magero]

For those of you with systems that are stuck at around 75% or so:

Same issue happened to my Mac mini 5,1.... I was able to resolve this by

logging in remotely
invalidating the kernel cache: sudo kextcache -i /
rebooting: sudo reboot

Installation completed as expected and everything is working correctly.

Hi i have the same issue, after install patched Mojave on MacPro 3.1, boot stuck on approx. 75%, please how can i logging remotely? I have a Macbook pro also.
Thanks for answer.

 

[Badruzeus]

@ASentientBot and @Badruzeus do you have tried to compare the 10.14.4 OpenGL, OpenCL, QuartzCore and Accelerate frameworks with previous 10.14.3 versions, I mean if they differ in byte size (maybe smaller) why don't try to replace with previous ones then checking the WindowServer behavior. I believe in replacing and supporting them even SkyLight is required.

More likely is IOFramebuffer, or IOAccelerator when they trying to load.. found no Display connected (CoreDisplay). Or could be rasterized gfx drawing (GL) fault when sending into framebuffer. If OpenGL is deprecated; my Fermi gfx should be die since 10.14.4 Beta 1 (but it' s still running upto Beta 2), no issue with 24-bit color depth either. Normally, "gIOScreenLockState..." console log appears on LoginScreen or when External Display connected, or Clamshell mode; system should be running on this stage.. but strange is having no display or black / white screen. Aw, guessing I assumed a lot for non-sense #LOL

My last test was using many diff. IOAccelerator* IOGraphics* kexts from prev. macOS versions; replacing OpenCL/GL frameworks as well; still get no screen on 10.14.4. Honestly, this is not a new topic on h*tosh community with IntelHD 1st Gen graphics, yeah.. we need Framebuffer patching, LinkWidth, DisplayConnector to get it running on some cases. I'm bit surprised that now real mac is having similar issue. I can do nothing then, hopefully.. Beta bugs? Or have you tried connecting to External display when 10.14.4 boot (if you have such device)..?

Spoiler

Anyway.. if you're interesting with my patched AppleIntelHDGraphicsFB.kext, files attached below. Though, I'm sure it won't give any difference on real mac with IntelHD Arrrandale. Framebuffer issue is just assumption too.

 

[jackluke]

More likely is IOFramebuffer, or IOAccelerator when they trying to load.. found no Display connected (CoreDisplay). Or could be rasterized gfx drawing (GL) fault when sending into framebuffer. If OpenGL is deprecated; my Fermi gfx should be die since 10.14.4 Beta 1 (but it' s still running upto Beta 2), no issue with 24-bit color depth either. Normally, "gIOScreenLockState..." console log appears on LoginScreen or when External Display connected, or Clamshell mode; system should be running on this stage.. but strange is having no display or black / white screen. Aw, guessing I assumed a lot for non-sense #LOL

My last test was using many diff. IOAccelerator* IOGraphics* kexts from prev. macOS versions; replacing OpenCL/GL frameworks as well; still get no screen on 10.14.4. Honestly, this is not a new topic on h*tosh community with IntelHD 1st Gen graphics, yeah.. we need Framebuffer patching, LinkWidth, DisplayConnector to get it running on some cases. I'm bit surprised that now real mac is having similar issue. I can do nothing then, hopefully.. Beta bugs? Or have you tried connecting to External display when 10.14.4 boot (if you have such device)..?

Spoiler

Anyway.. if you're interesting with my patched AppleIntelHDGraphicsFB.kext, files attached below. Though, I'm sure it won't give any difference on real mac with IntelHD Arrrandale. Framebuffer issue is just assumption too.

I believe at least on real macs it's not a FrameBuffer issue, but OpenGL API rendering. Probably Metal API will use the same FrameBuffer/OpenCL too. We still have a hope that those issues gone away with 10.14.4 full installer final package, maybe next month.

 

[ASentientBot]

I believe at least on real macs it's not a FrameBuffer issue, but OpenGL API rendering. Probably Metal API will use the same FrameBuffer/OpenCL too. We still have a hope that those issues gone away with 10.14.4 full installer final package, maybe next month.

I agree, it's not framebuffer related -- if so, it would still crash with just the OpenGL kexts removed. The framebuffer is working fine on my 10.14.4 system. This is specifically an OpenGL problem.

I wonder if it could be related to my previous patch to GeForceTesla.kext that fixed a similar issue where the system crashed when OpenGL was enabled. However, that happened in a close function, and this happens in an initialization function.

I'll keep trying to figure it out...

 

[Larsvonhier]

My last test was using many diff. IOAccelerator* IOGraphics* kexts from prev. macOS versions; replacing OpenCL/GL frameworks as well; still get no screen on 10.14.4. Honestly, this is not a new topic on h*tosh community with IntelHD 1st Gen graphics, yeah.. we need Framebuffer patching, LinkWidth, DisplayConnector to get it running on some cases. I'm bit surprised that now real mac is having similar issue. I can do nothing then, hopefully.. Beta bugs? Or have you tried connecting to External display when 10.14.4 boot (if you have such device)..?

Done that on my MBP 4,1 after the first round of disappointing findings after 10.14.4 b1.
The external screen (on DVI conn.) comes up in bright white at some stage of boot progress, stays white but error msg on internal screen nonetheless.

 

[Olivia88]

I agree, it's not framebuffer related -- if so, it would still crash with just the OpenGL kexts removed. The framebuffer is working fine on my 10.14.4 system. This is specifically an OpenGL problem.

I wonder if it could be related to my previous patch to GeForceTesla.kext that fixed a similar issue where the system crashed when OpenGL was enabled. However, that happened in a close function, and this happens in an initialization function.

I'll keep trying to figure it out...

If I remember correctly the intelhd3000 didn't need any modifications to run Mojave, and its hanging at the exact same place as the Nvidia 330m, so maybe the issue would be something they both do the same

 

[16v]

an OT question:

Tried the APFS Patcher today.
There was no option to select the Chip Type, it starts flashing, System was not usable...

AND my Batterie run out of energy... i left home when this happens.

When i came back, i chaged my MBP and switched it on. It worked like before.

So, SSD, Mojave and APFS Patch is used (dosdude1 patcher - Software APFS)
Can i check if APFS is in ROM?
AND: Does system boot with both APFS Patches?

THX

 

[0403979]

an OT question:

Tried the APFS Patcher today.
There was no option to select the Chip Type, it starts flashing, System was not usable...

AND my Batterie run out of energy... i left home when this happens.

When i came back, i chaged my MBP and switched it on. It worked like before.

So, SSD, Mojave and APFS Patch is used (dosdude1 patcher - Software APFS)
Can i check if APFS is in ROM?
AND: Does system boot with both APFS Patches?

THX

If your system shows a verbose log at boot then you are using the partition patch. If your system shows nothing at boot then you are using the chip patch. And if your system doesn’t boot APFS drives then you are using neither patch.

 

[16v]

???
When booting there are white and yellow letters on black background.

Try it again right now.
It says writing patched rom since almost 10 minutes...