Whoops! Thank you for the reminder.You have to boot the installer.
Whoops! Thank you for the reminder.You have to boot the installer.
I've never seen that error anywhere. Interesting. Good luck for the update and good luck for school.@0403979
Installing 10.14.4 via Software Updates. Showed THIS UPDATE CANNOT BE VERIFIED. YOU NEED TO REBOOT AND TRY TO REINSTALL...
I have to download the update again(Worried if I will late for school)
Could be system time is wrong. Boot USB installer, start terminal, type “date” and hit enter. If date is wrong, can cause weird errors.@0403979
Installing 10.14.4 via Software Updates. Showed THIS UPDATE CANNOT BE VERIFIED. YOU NEED TO REBOOT AND TRY TO REINSTALL...
I have to download the update again(Worried if I will late for school)
I've never seen that error anywhere. Interesting. Good luck for the update and good luck for school.
After getting it together (Thanks to Julian) the Installer process and Post-install process went perfectly and 14.4.08 in-place installed on a 14.3 HFS+ SSD in this early Mini3,1. The Screenshot app and System Preferences crashed the Mini, immediately. Ran the Maintenance app from Titanium, rebooted and the Mini now runs flawlessly.Whoops! Thank you for the reminder.
cp /Volumes/OSX/GPU/HIToolbox /Volumes/OSX/S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current/
cp /Volumes/OSX/GPU/CoreUI /Volumes/OSX/S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current/
chmod 755 /Volumes/OSX/S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current/HIToolbox
chown 0:0 /Volumes/OSX/S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current/HIToolbox
chmod 755 /Volumes/OSX/S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current/CoreUI
chown 0:0 /Volumes/OSX/S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current/CoreUI
Re-apply Legacy Audio Patch, and you should be good. Also, force cache rebuild.
Last week @dosdude1 shared full acceleration patch for non-metal graphics. is this patch will fix grey top bar transparency issue?
So did you updated OTA and also download and create the bootable installer using Dosdude1's patcher tool, and ran the patches?Successfully updated to 10.14.4 GM on my unsupported MacBookAir4,2
View attachment 828478
- OTA
- Post Install Patch using @dosdude1's 1.3.0 Mojave Patcher app
- Rebuilt Caches
- Reboot
As always, thanks to the excellent/awesome patcher app by @dosdude1.
By your example, I made myself such an improvised partition Rescue. Thank you for the idea. Now I don’t need to insert a flash drive, and all dosedude patches can be run from HDD.I had tried to create "custom Recovery" here are my observations:
- Any Recovery is a hidden bootable partition with CMD+R, contains the BaseSystem.dmg (about 500-700 MB) that is completely expanded in RAM so it's real size is around 1,3 GB (but is allocated in 2,01 GB in DiskUtility) and in-fact Recovery requires at least 2 GB RAM to be used;
- APFS Recovery is very particular, requires an Unique ID and can't be customized since its BaseSystem.dmg has a unique DMG signature that when changed it won't boot more;
- HFS Recovery almost the same, when you "edit" the BaseSystem.dmg it won't boot more with CMD+R because has a DMG signature checking too;
The only way, valid both for APFS scheme or HFS+, is to create a separate HFS partition (outside the APFS container) at least 2-3 GB free space, and restore on that partition an untouched BaseSystem.dmg , you can customize that partition content as you want, in this way "custom Recovery" will work holding alt-option key as a bootable emergency Volume.
Otherwise clone the dosdude1's USB Installer to a spare 9 GB HFS partition, if you want that smaller (before resizing) just delete from there the content (the pkgs especially the Core.pkg) in this folder /System/Installation/
I’m the dev of transutil (part of macOS Patcher) but not the actual fixes. I will test it on 10.14.4 and report back when I’ve come up with a fix.I updated macbook 6.1 using the old dosedude patcher for 10.14.3 and my script. I wrote it earlier when updated on 10.14.4 beta 6. In the script there is also a fix for Siri, AppleGVA from 10.13.6 to fix hardware acceleration freezes, and most importantly, fix issues with the weired side bar, which was fixed earlier by the transutil script, but after the update becomes gray again and the rerun of the transutil script has not been fixed it again.
Now a dosedude patcher has been released, I don’t urge to use my own script, I just want to show if someone after the upgrade cannot fix these issues on the weired gui transutil script on video cards without metal support, as I fixed them.
View attachment 828466 View attachment 828464
I downloaded the latest release from this project, renamed CoreUIHybrid-18C54-v1.4.1 and HIToolboxHybrid-18C54 to CoreUI and HIToolbox, and in my script these commands put these files in places.
As you can see on the screenshots above - it worked.Code:cp /Volumes/OSX/GPU/HIToolbox /Volumes/OSX/S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current/ cp /Volumes/OSX/GPU/CoreUI /Volumes/OSX/S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current/ chmod 755 /Volumes/OSX/S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current/HIToolbox chown 0:0 /Volumes/OSX/S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current/HIToolbox chmod 755 /Volumes/OSX/S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current/CoreUI chown 0:0 /Volumes/OSX/S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current/CoreUI
do not use these commands as is - this is just for example
I don’t know. You could try using OnyX and running the maintenance. I don’t have 10.14.4 yet so I’m not aware of any bugs.Got updated really fast though (not worried about late for school anymore haha) But had anyone saw the 3 ios apps crash on 10.14.4 especially News app. May be it's a IOS framework-related problems or something else??![]()
It’s lovely to see a case of it working correctly on real hardware. I can only test that the files were copied on my MacBook7,1. I can’t test the actual functionality since it’s a MacBook7,1. I don’t have any other models either.After getting it together (Thanks to Julian) the Installer process and Post-install process went perfectly and 14.4.08 in-place installed on a 14.3 HFS+ SSD in this early Mini3,1. The Screenshot app and System Preferences crashed the Mini, immediately. Ran the Maintenance app from Titanium, rebooted and the Mini now runs flawlessly. View attachment 828460 View attachment 828463
I'm seeing odd version/timestamp differences between the version of the Mojave 10.14.4 installer I downloaded tonight using @dosdude1 's MacOS Mojave Patcher v1.3.0, versus the version of the 10.14.4 installer I downloaded tonight through the App Store/Software Update:
MacOS Mojave Patcher 1.3.0 version:
Get Info says:
Version: 14.4.08
Size: 6,041,505,576 bytes
Created: March 25, 2019 at 5:16 pm [Pacific Daylight Time; this is when I downloaded it]
Modified: March 25, 2019 at 5:16 pm
Copyright: 2007–2019
App Store/Software Update version:
Get Info says:
Version: 14.4.10
Size: 6,048,742,022 bytes
Created: March 14, 2019 at 10:19 pm
Modified: March 25, 2019 at 5:57 PM [Pacific Daylight Time; this is when I downloaded it]
Copyright: 2007–2018
I know that the Created and Modified dates for some downloaded items will be whatever day/time you download the item, instead of their original Created and Modified dates, so that's fine, but why are there these differences between the Version strings, the size, and the copyright year? Obviously the URL that Mojave Patcher is using is different from the one the App Store/Software Update is using, but why? I guess I could assume the version I downloaded from the App Store/Software Update is the more recent version since its version string is actually more recent, but is the mismatch in the Copyright year just someone's oversight at Apple?
I looked at some of the files a few levels deep inside each installer application, opening some of the plist files, but I found nothing that confirmed which installer is the more recent. I also found that many of the files inside the version downloaded by Mojave Patcher were modified on March 20 2019, but the corresponding items in the installer downloaded through the App Store/Software Update were modified on March 14 2019. But in a few cases, some items in the installer downloaded by the App Store/Software Update were modified two or three days later than the version downloaded by Mojave Patcher. This is another confirmation that the URLs for these two downloads are different, but it still doesn't tell me for sure which version is the most recent.
I found that isight, built-in camera, doesn't work.
Is there any way of solving this issue?
I am using mid-2009 MacBook Pro 13 inch(5,5) now.
That wasn’t my intention, I just wanted to make sure that your system boots at least with a supported os. I asked about time machine because that way you could go back to your last known system configuration before it stopped working.I use timemachine but i’m not going back to high sierra.