Got a tip for us?
Let us know
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
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Mojave Patcher has now been updated to support the DP6 installer app.
Weird, 091-98048.English.dist shows 14.0.15 for me.
Code:
<pkg-ref id="MajorOSInfo" installKBytes="1962" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="InstallAssistantAuto" installKBytes="24094" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="RecoveryHDMetaDmg" installKBytes="0" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="InstallESDDmg" installKBytes="0" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="InstallInfo.plist" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="AppleDiagnostics.dmg" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="OSInstall.mpkg" installKBytes="0" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="BaseSystem.chunklist" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="InstallESDDmg.chunklist" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="AppleDiagnostics.chunklist" version="10.14.0.0.0.1533200099"/>
<pkg-ref id="BaseSystem.dmg" version="10.14.0.0.0.1533200099"/>
This will be extremely off-topic since I just noticed here that Mojave beta 6 is out.
Anyway I want to share this unusual experiment:
I do have a bricked EFI CHIP on MBA 2,1 , then today with the help of a friend, have desoldered the "QFN EFI CHIP".
Now since I don't have yet the USB kit tools to reprogram the EFI EEPROM, I've tried to boot the MBA 2,1 without the EFI CHIP.
So I've discovered that it has the exactly same behavior of booting with a soldered Bricked EFI CHIP, a bricked EFI CHIP is considered by the Mac's logic board as like a totally missing EFI CHIP.
That's all.
Anyway I want to share this unusual experiment:
I do have a bricked EFI CHIP on MBA 2,1 , then today with the help of a friend, have desoldered the "QFN EFI CHIP".
Now since I don't have yet the USB kit tools to reprogram the EFI EEPROM, I've tried to boot the MBA 2,1 without the EFI CHIP.
So I've discovered that it has the exactly same behavior of booting with a soldered Bricked EFI CHIP, a bricked EFI CHIP is considered by the Mac's logic board as like a totally missing EFI CHIP.
That's all.
Attachments
Yeah, that's right. I've had this happen many times during experimentation.
Will I have to make a clean install os DP6? System update still not working?
It should work.
[doublepost=1533582476][/doublepost]
Make sure you have installed the software update patch.
You never need to do a clean install, even if using a new patched USB installer. Just proceed through the install as normal, selecting the volume that has a previous version of macOS without erasing it first.
I do the System Preferences update but make patched usb first just in case.
when my update finished installing I ran the post install updates and the force rebuild like I always do just to be safe I did not see the night shift listed in the post install patches and as you can see its is not listed in the patch updater even reinstalled the backlight patch still no luck 
Attachments
From DP4 to DP5 I have downloaded the system update but when I went to install it, it was like I wanted to make a new installation procedure and not an update per se...
if your download is 5.87 to 6 GB you might be downloading the full install instead of the update
There is extra area in the list not shown... Did you scroll all the way down in the list of installed updates?when my update finished installing I ran the post install updates and the force rebuild like I always do just to be safe I did not see the night shift listed in the post install patches and as you can see its is not listed in the patch updater even reinstalled the backlight patch still no luck
so, grey menu bar again? maybe we should report this bug to apple as it could happen even on 2012 mbp which is supported model? Let's make Apple fix this)
Hey man, I am using dp5 that I have downloaded from macOS patcher tool that you provide. I should receive the update to DP6, right? Why I can't? It never shows up... Can you explain what might be wrong?
this worked for me on my MacBook 5,2 I made a usb patcher version 1.1.1 and downloaded macOS Mojave DP5 after the patcher I booted into the the patcher and installed over DP4 and it works well now issues the version now is 1.1.2 of the patcher on the OP
[doublepost=1533583896][/doublepost]
it might be an issues with the software update and are you in the developers beta program or the public beta program
Could you please report this bug to Apple?
When I download a new patcher version and download MacOS Mojave beta I have it downloaded in my applications folder so my theory is when you run the software update it checks your application folder for the install macOS Mojave beta so if you have for example your about Mac says you have 18A336e 14014 and your install macOS Mojave beta is the previous version 18A326g or if you don't have a install macOS Mojave beta in your applications folder you get the full download installer just my thinking I think your about Mac and install macOS Mojave beta have to match to get the the upgrade
No, I have it on applications folder. I am checking the steps and I think I did something wrong. Installed with Patcher and then enroll my device to developers beta. Then it pulls the update (developer one) and it always download the full version and not the update. I think my device is on public beta, so probably I don't give enough time to receive public beta update... What do you think?
[doublepost=1533586146][/doublepost]I
Nope, unenrolled and then enrolled again and it shows that the macOS version is not available.... What the heck....
[doublepost=1533586238][/doublepost]@dosdude1 hey, which macOs version I have when we download from the patcher tool? Public beta or developer beta?
Downloaded *3* times, two from Developer Beta Profile and one with installinstallmacos.py, still got version 14015. Did you only looked at CFBundleShortVersionString and not on the About Install macOS of the Installer app?
CFBundleShortVersionString is 14.0.16, but on the About Install macOS is 14.0.15. Something is very weird here.
Last edited: