The fog is lifting.However it remains still a mistery why after introducing the dark mode as a new Mojave feature this doesn't glitch with OpenGL instead the old consolidated light mode does. I mean they changed the API calls only for the light mode. Anyway continue to break it sooner or later you will.
No. What device do you have?Hybrid mode patch is only for macs with 2 cards?
The fog is lifting.
The patches prove that vibrancy in Light mode is achievable. The only possible explanation is that a special core animation layer combination + blend and filter compositing sauce just doesn't sit well with our old GPUs in Light. Since there are no real tools to peel through these ca layers in an asset bundle (except for a secret internal Apple one called Mica) I am developing one based on Zielinski's ThemeEngine. I've already forked the project on github. This has the most promise for an alternative to patching frameworks.
No. What device do you have?
I have Mojave 10.14.1 on MBA mid 2011 and it runs without a problem. I used an updated USB stick with 1.2.3 Patcher, and installed over the existing 10.14 installation. I will use an updated USB stick for every new version and omit all the betas. I can then use the stick to update 3 more computers (2x iMac 9.1, MBP 4.1).Hello! I use Mojave on my MBA mid 2011 since first betas of dosdudes tool. I have a problem with every update. Description on tools's website states that updates should auto install with "software update" patch installed. Its installed by default to my machine but after every update I reinstall with post installation utility and force rebuild cache. With recent update autoupdate failed and system were unable to boot and doing patch update didn't worked. I had to reinstall 10.14.
Can you clarify if MBA 2011 is compatible with patched 10.14.1 and if so how should I upgrade to avoid bricking my machine? Should I download and make new USB stick every time. Or autoupdates works for you and patches installed automatically.
P.S. I think update process can be described better in manual
We can’t actually install the update packages themselves though. We need all the dependencies. I don’t know what they all are but they get downloaded when you download an OTA update.
Can you show me exactly where to put the return true; in the body of the text. I have tried a couple of times but when running the patched update it responds with an error.
I had to encrypt the ZIP due to Google falsely flagging DirectHW (used in APFS ROM Patcher) as malware. With the ZIP encrypted, Google has no way of scanning the file. To extract, just use the password "apfs".@dosdude1 It appears your APFS Patcher is back online with a password? How does one learn the password?
I tried using an older download (2.0.0) I had on my cMP3,1. I got the error "DirectHW.kext could not be loaded". I verified that SIP was disabled, and had booted into programming mode. I have 2 GPUs and 32GB of RAM.
Happy to take this to the appropriate thread if there is one...
You mean 10.14 ?I found 10.4 awful. Slow transfers to USB HDDs, spinning wheel, two button click intermittent on the touchpad. basically terrible to use.
Here is my experience installing 10.4.1 on a Macbook Pro 5,5 (Mid 2009 model). Hopefully it may help someone.
1. downloaded the latest mojave patcher and downloaded the latest Mojave update via the tool.
2. Installed over my existing install
3. Boot from USB to install patch (failed to boot, or stuck on about 80% loading)
4. After 15 mins turned off and on, tried again. Same
5. Tried booting from my HDD or recovery I got a no entry sign
6. Turn off and on. Same
7. Tried booting USB stick from another USB port - Success!
8. Applied patch for my model (ticked clear caches), rebooted and it's working again!
Touchpad seems ok, transfering files seem ok and no annoying spinning wheel.
Hybrid Mode v1.3 is tested and released. Find it here. We've addressed most of the issues reported in the repo...Thanks to all of you for doing so. As always, read instructions and notes carefully here. This may not be for you.
You must be on 10.14.1 18B75 - backwards compatibility or forward betas are not supported.
File issues and problems in the repo if you can (just the way I prefer to operate - no offense to this site...)
Some highlights of the additional fixes (mostly CoreUI):
1. Search bar pull downs in apps like Safari and iMessage are back to vibrant in Light:
View attachment 802864
2. Brightness, Sound and other HUDs are "vibrant" in Light and Dark
View attachment 802865
3. Sidebar Search element blends correctly with the background
View attachment 802867
4. While "Inactive" Sidebar selections now blend in correctly
View attachment 802869
Guys, It is running: Mojave 10.14.1 on RAID 0 and APFS file system (hybrid), I followed some installation tips in the Brazilian forum (macmagazine) and it worked.
diskutil appleRaid create stripe raid0 JHFS+ disk1 disk2
diskutil unmountDisk disk3
sudo gpt create disk3
gpt add -t hfs disk3
If you convert to APFS, this will affect future updates, getting stuck in the current version
after install Mojave:
diskutil list to Locate the Mojave Installation Partition
diskutil apfs convert disk(x)s(y)
Keep on JHFS + to receive updates normally.
Hello. I'm interested in trying this patch... but i have a question:
- The instructions says that i have to replace three files: HIToolbox, AppKit and CoreUI. OK. I made a backup of this three files. But the original patch only have two files named as CoreUIHybrid-18B75-Fat-v1.3 and HIToolboxMenubar-18B75-Fat-v1.3
- I suposse that i have to rename this two files to "CoreUI" and "HIToolbox" and put it in the folder of the other files. But ¿Where is the AppKit file? I suppose that must be a file like that if it appears in the instructions.
I've tried, but never had any luck with those. I've always had to desolder the EEPROM, and put it in my programmer externally.can somebody confirm that it's possible to exctract/backup eeprom with an eeprom clipper tool. ?
I want to make a back-up first before applying the AFPS patch tool..
It looks like an standard 8-legged eeprom chip to me, and my eeprom clip would fit right on it.. ?
Anybody here can give me an answer on this one.. ?
APFS ROM Patcher adds native APFS booting support to your system firmware, while the APFS Patch adds a custom EFI booting implementation, and doesn't modify your firmware at all.@dosdude1, sorry if this question has been asked and answered before ...
Is there a difference between "APFS ROM Patcher" and the "APFS Patch" on your 1.2.3 MacOS Post Install? I used the latter on my mojave unsupported MBP5,3 which is currently on the latest 10.14.2 beta 2. And it is working well for me (no issues). Is one better than the other?
Thanks for your awesome apps.