Excellent. No further questions, Your Honour.
I'm now off to think about whether I want to buy an SSD to port my HS installation to, and whether I'm brave enough to patch my ROM or to just live with the verbose booting method. So many questions.
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
I'm now off to think about whether I want to buy an SSD to port my HS installation to, and whether I'm brave enough to patch my ROM or to just live with the verbose booting method. So many questions.
If your machine only has one definition then it should be fine most of the time.
I believe this is a reference whether multiple part numbers of eeproms were used for the same model.
As for the patching, perhaps you should ask dosdude1 about your exact configuration. He might know if the fact that your machine has a firmware update that doesn't match the exact model will present a problem for the ROM patcher. If so, you might look trying to run the firmware restoration CD for that exact model and overwrite the current firmware before trying the ROM patcher.
Light Mode "glitch" update:
Of Interest To :
Good news. Currently I'm able to patch AppKit to intercept the Light-Dark Mode switch and substitute a "hybrid" mode with our beloved translucency/transparency for some key UI elements while keeping content in a Light Mode. I call it Hybrid Mode. Most side bars are "vibrant" like in Dark mode, allowing for background blur. As seen below:
I think this may be an acceptable workaround for the VibrantLight mode which is currently broken on some of our machines (hence the famous "glitches")
I am currently working on getting the top menu bar to "vibe" also. It's not obvious as Apple is using some old (very old!) Carbon HTLB apis (wow - thought it was dead) . There are also some other menu bar solutions, but not as elegant as system wide approaches.
What do you think - just wanted to get your thoughts? Any one?
Of Interest To :
- those who have an unsupported machine running a non-metal card
- those who hate Dark Mode
- those who don't want to patch/tweak app by app (this is a system wide AppKit approach)
- (currently) those who have NVIDIA gpus (this was tested on my mbp 5.3 with stock NVIDIA GeForce 9600M). I'm not sure what happens on AMD gpus.
Good news. Currently I'm able to patch AppKit to intercept the Light-Dark Mode switch and substitute a "hybrid" mode with our beloved translucency/transparency for some key UI elements while keeping content in a Light Mode. I call it Hybrid Mode. Most side bars are "vibrant" like in Dark mode, allowing for background blur. As seen below:
I think this may be an acceptable workaround for the VibrantLight mode which is currently broken on some of our machines (hence the famous "glitches")
I am currently working on getting the top menu bar to "vibe" also. It's not obvious as Apple is using some old (very old!) Carbon HTLB apis (wow - thought it was dead) . There are also some other menu bar solutions, but not as elegant as system wide approaches.
What do you think - just wanted to get your thoughts? Any one?
You are doing a awesome Job can't wait to try it out Thanks
Are there any Carbon HTLB API's in El Captain that might work
Last edited:
A
Awesome. That hybrid mode is beautifull
Thank you ASentientBot
I am going to need your help as so far I have unsuccessfully tried to run two versions of the Quicktec QT1.app in order to load compatible kexts and restore the Bluetooth 4.0 functionality under MacOS Mojave 10.14 Beta (18A353d) My Wi-Fi functionality is working utilizing the same QuickerTec mcard 2
@dosdude1 Can you tell what I'd need to look at to investigate this? AFAIK I have the exact same machine that you show booting (verbosely) with the APFS patch in your YT video i.e. MacBookPro 5,1 (late 2008).
All I can tell you is that my BootROM version is MBP51.007E.B06
Yessss !
No further question, Your Honour !
It work perfectly : "mount the EFI System Partition of your hard disk and delete "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi"
..."La parole est à La Défense"...
All you need to know is the exact model number of your system's EEPROM. You can find this by opening the machine, and looking at your logic board. It will be the largest 8-pin SOIC chip on the board, so it will be easy to spot. Once you read the model number off it, you'll be ready to apply the APFS ROM patch. It will probably take close to 15 minutes to flash on that system, so just be aware and DO NOT quit the program while it is in progress.
OK, cheers. Now all I need to do is answer my other questions and decide whether I'm brave enough.
This looks amazing. I'm sorry that I kind of abandoned the effort to patch this, it was way over my head. This is a fantastic start and I can't wait to hear about any progress you make with the menu bar.
[doublepost=1535744171][/doublepost]
This is super weird, it looks to me like the install app is modifying a system kext: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/ is built into Mojave and it wants to replace its Info.plist file? Presumably this will allow it to recognize the third-party card by adding a vendor id/device id to the file. That seems like an awfully hack-ish way for a legitimate hardware manufacturer to use, but alright...
If the script is failing, you can do it yourself.
In Terminal:
cd /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents
sudo mv Info.plist Info.plist.backup
sudo cp /path/to/QT1.app/Contents/Resources/Info.plist ./
sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo kextcache -i /
You will obviously have to put in the correct path to your app. If any step produces an error, stop. I haven't tried this and we might need to tweak things.
Last edited:
Great job! I believe with your method that also the Safari's Favorites page is rendered in a "DarkAqua" transparency, if you haven't swapped the .CAR files may you try to override some App's top menu bar in light mode for ex. from Terminal:
/Applications/System\ Preferences.app/Contents/MacOS/System\ Preferences -NSRequiresAquaSystemAppearance 1
Some developers are reporting that with this script from Terminal:
defaults write -g NSRequiresAquaSystemAppearance -bool YES
(Just user logout to see the changes)
You'd obtain another kind of hybrid "light mode" windows with "dark mode" transparencies (and the infamous grey Finder menu bar turned into translucent dark). But I haven't tested yet.
edit:
Just tested, it will work partially but of course the grey transparent zones in hybrid "light mode" are still there. Your "hybrid" solution appears much better than this "NSRequiresAquaSystemAppearance".
To return into both normal "dark mode" and "light mode" just type from Terminal:
defaults delete -g NSRequiresAquaSystemAppearance
Last edited:
Thx.You are doing a awesome Job can't wait to try it out Thanks
No I just need time to crack open the Carbon framework. Believe it or not, the menu bar's appearance is the primary way the system determines which mode (darkAqua or Aqua) you are in at any point in time.
[doublepost=1535746018][/doublepost]
Thx!I think that's awesome pkouame !
[doublepost=1535746152][/doublepost]
No problem. I will need some folks to test the patching approach and on multiple platforms. I think a dark vibrant menu bar will look great. I see no reason why it can't happen.
[doublepost=1535746902][/doublepost]
This approach does not swap any .car files. At least yet, I think there will come a point when tuning these for our own special "modes" may be fun.
Yes, I see the switch NSRequiresAquaSystemAppearance in the code. I'm not sure what it does exactly yet.
I'll check it out. But this way, switching modes from preferences runs smoothly.
Last edited:
I have inserted the path in Terminal script below but I am still having problems. Does this look correct?
cd /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents
sudo mv Info.plist Info.plist.backup
sudo cp /Users/trs02/Desktop/QT1 .app/Contents/Resources/Info.plist ./
sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo kextcache -i /mymac1
Here is the Terminal output I am getting:
MacBook-Pro:Contents trs02$ cd /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.k
ext/Contents
MacBook-Pro:Contents trs02$ sudo mv Info.plist Info.plist.backup
mv: Info.plist: No such file or directory
MacBook-Pro:Contents trs02$ sudo cp /Users/trs02/Desktop/QT1 .app/Contents/Resources/Info.plist ./
cp: /Users/trs02/Desktop/QT1: No such file or directory
cp: .app/Contents/Resources/Info.plist: No such file or directory
MacBook-Pro:Contents trs02$ sudo chown -R root:wheel /System/Library/Extensions
MacBook-Pro:Contents trs02$ sudo chmod -R 755 /System/Library/Extensions
MacBook-Pro:Contents trs02$ sudo kextcache -i /mymac1
Out of interest, can you make that but inverted? So apps dark, sidebars and stuff light?
ASentientBot tips are correct, you have simply to replace the Info.plist inside that path but it seems missing or deleted, anyway a simpler way, open Finder and use keyboard shortcut: CMD+SHIFT+G
Then into Go to Folder copy/paste this:
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents
And click GO
Leaving this Finder window opened, type this other shortcut: CMD+N
Now you should navigate where is your QT1.app/Contents/
Once you are inside the QT1.app packages copy the Info.plist and paste into the other previous Finder path
Once you have copied the Info.plist in both place, open Mojave Terminal and copy/paste in one line:
sudo chown -R root:wheel /System/Library/Extensions ; sudo chmod -R 755 /System/Library/Extensions ; sudo kextcache -i / ; sudo reboot
Last edited:
Thank you so much for your help.
Attached is my Terminal Text output...not sure where I am going wrong.
Your Terminal scripts appear ok, your issue is that Info.plist is totally missing in both path, try to download again the full QT1.app and explore inside packages to find the Info.plist, to copy try using Finder windows instead of Terminal
My mistake, last command was:
sudo reboot
Restart your mac it should work now.
Thanks for sticking with me on this, jackluke.
In the QT1.app the package Contents folder it contains an info.plist I attached...but there is also a info.plist in the Resources folder within the Contents folder.
Ok, then repeat all the steps but this time use the Info.plist inside the Resources folder copying it from the QT1.app into the other long Airportbrcm4360.kext/Contents path
Then from Mojave Terminal copy/paste the one line command to rebuild kextcache
Last edited:
[doublepost=1535755760][/doublepost]I must be doing something wrong...computer did reboot but still no bluetooth.
Attached the Terminal output...Thanks again for giving this a try.
The steps appear ok, retry last time re-replacing the QT1.app Info.plist from Contents into the long Airportbrcm4360 Contents
If still doesn't work, not sure but you could try to replace the entire IO80211Family.kext from HS into Mojave S/L/E