Supplemental Update: I can confirm successful installation even ontop of 10.14.3 beta 3, just had to re-apply audio patch on my MBAir 11,6”
Which model do you have? Have you had any glitch or bug?
Or it might be the other way round: Apple might have taken care of the final release 10.14.3 with the suppl. update, but will roll out another coming beta containing it with 10.14.4 beta 3 (i.e.) - no rush here due to test usage anyway here.Checked to see if my unsupported MBA4,2 on 10.14.4 beta 2 has an update (i.e. Supplemental Fix - Group Facetime Fix), but it didn't show. Only Safari Technology Preview 75 was listed. So I guess the fix that was available for 10.14.3 Final was already fixed on the beta 2 update.
Just an FYI.
I think so as well, I think 10.14.4 beta 2 is not fixed yet, though there is no rush since the bug is fixed or blocked for not fixed client versions on the server sideOr it might be the other way round: Apple might have taken care of the final release 10.14.3 with the suppl. update, but will roll out another coming beta containing it with 10.14.4 beta 3 (i.e.) - no rush here due to test usage anyway here.
That has been their procedure in previous cases.
macOSUpd10.14.3Supplemental:
"This software is not supported by your system."
10.14.3, iMac 27" late 2009.
Any ideas?
Thanks for your reply!
I have HFS+.
The modified PlatformSupport.plist on S*/L*/ CS, how to check it?
Starting the patcher, I'll try it.
What do I've to change on the patchers GUI?
$ cd ~/Downloads
$ pkgutil --expand [PackageName].pkg NewFolder
$ cd NewFolder && ls
$ nano edit Distribution
// or using your fav. xml editor, Find for:
function FileSystem1(prefix) {
if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
return false;
}
return true;
}
// change to:
function FileSystem1(prefix) {
if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
return true;
}
return false;
}
// Save.
$ cd ~/Downloads
$ pkgutil --flatten NewFolder [PackageNameHFS].pkg
I have the 2.0 GHz model, I also noticed that my logic board already has a backlit keyboard connector. I might add it at some stage.
It just worked in my experience. No glitches or bugs.
Just use Offline methods:
1. Download macOS Mojave 10.14.3 Supplemental Update.
// change to:
function FileSystem1(prefix) {
if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
return true;
}
return false;
}
Thanks, I'll give it a try.
Btw, was it a clean install or upgrade?
My script can do this automatically. https://github.com/Julian-Marius-Fairfax/macOS-Patcher Just run chmod +x on the script file and then run the script file with sudo and go through the steps to patch the update package.Just use Offline methods:
1. Download macOS Mojave 10.14.3 Supplemental Update.
2. Extract *.pkg (from *.dmg), assumed it' s located on ~/Downloads
3. Edit "Distribution" file for forcing installation on HFS+, Terminal:
4. Try updating with your new modified [PackageNameHFS].pkgCode:$ cd ~/Downloads $ pkgutil --expand [PackageName].pkg NewFolder $ cd NewFolder && ls $ nano edit Distribution // or using your fav. xml editor, Find for: function FileSystem1(prefix) { if (my.target.filesystem && my.target.filesystem.type == 'hfs') { return false; } return true; } // change to: function FileSystem1(prefix) { if (my.target.filesystem && my.target.filesystem.type == 'hfs') { return true; } return false; } // Save. $ cd ~/Downloads $ pkgutil --flatten NewFolder [PackageNameHFS].pkg
Or it might be the other way round: Apple might have taken care of the final release 10.14.3 with the suppl. update, but will roll out another coming beta containing it with 10.14.4 beta 3 (i.e.) - no rush here due to test usage anyway here.
That has been their procedure in previous cases.
Hello everyone,
my MacBook 5,2 and I, we celebrated our 10 years companionship this month.
Today I opened the MacBook to identify the type of EEPROM in order to choose the right type for flashing APFS Rom-Patcher.
Unfortunatly, I couldn't find the EEPROM.
Please, can someone tell on which side of the printed circuit board the EEPROM is soldered?
Relax. The bug is very likely still present in 10.14.4 betas (up to now) - but as all comm is routed through Apple´s servers, you're fine. Apple disabled group FaceTime on the server-side for all non-patched systems trying to engage FaceTime calls with more than two participants and even on newer systems you cannot add new members ad-hoc any more (which was part of the bug or 0day).If that is the case, am I to assume then that my 10.14.4 beta 2 MBAir4,2 still have the "Group FaceTime bug" ? Thanks.
Relax. The bug is very likely still present in 10.14.4 betas (up to now) - but as all comm is routed through Apple´s servers, you're fine. Apple disabled group FaceTime on the server-side for all non-patched systems trying to engage FaceTime calls with more than two participants and even on newer systems you cannot add new members ad-hoc any more (which was part of the bug or 0day).