Jump to content

jackluke

Members
  • Content count

    25
  • Joined

  • Last visited

About jackluke

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

1,181 profile views
  1. Please don't spam.
  2. I have specified on the Premise that the APFS Recovery is only for use the macOS Utilities in case of emergency, you can't re-install from that of course, because the re-installation from any macOS Recovery needs to download the full Installer through Internet from servers, and on a non-mac hardware is not advisable to re-install from there. When you install Mojave in APFS, you will have almost always these partitions numbers (the diskXsY may change according to your internal disk partitioning): EFI disk0s1APFS Container disk0s2APFS Container Scheme disk1APFS Volume disk1s1 (used for HighSierra or Mojave)APFS Preboot disk1s2 (used for FileVault 2 encryption)APFS Recovery disk1s3 (used for Recovery and CMD+R)APFS VM disk1s4 (used for sleep image)
  3. Premise: the following explanation is only to exploit the little APFS Recovery (less than 600 MB) embedded inside the APFS File System, so avoiding an external USB Installer, you can't reinstall macOS from here but use just the Utilities (Terminal, DiskUtility) in case of emergency, however as known from a Recovery Terminal can do a lot of things, especially troubleshooting an unbootable macOS. To those who have installed Mojave on APFS file system with a GUID/GPT Scheme (I suppose it will work even on MBR scheme), I have managed to "fix" the "APFS Recovery Volume" to make it bootable from any computer (capable of HighSierra and Mojave) with USB input devices (trackpad, keyboard, USB mouse and so on) responsive, working wifi and everything else, just follow next steps, totally safe and harmless for any Mojave installation, after booting normally from your Mojave APFS Volume, launch Terminal and type:diskutil apfs list{locate your "APFS Recovery Volume" on diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]} On APFS scheme the "APFS Recovery Volume" is tipically on the 3rd (hidden) partition.diskutil mount diskXs3 open /Volumes/Recoverylanding on Finder, double click on the "random-numbers-letters" folder (it's the gpt UUID folder where Recovery stores itself), once inside rename these files:prelinkedkernel into prelinkedkernelbackup immutablekernel into immutablekernelbackup PlatformSupport.plist into PlatformSupportbackupDon't close this opened Finder window yet, once you renamed those 3 files, now you have to open a new Finder window, then from this new Finder window go into your Mojave path: /System/Library/PrelinkedKernels/ while inside this path copy the file prelinkedkernel into the previous Finder window exactly where you renamed those 3 files lastly rename this fresh copied file from prelinkedkernel to immutablekernelNow you have a working APFS Recovery Volume. Note for those who use Clover bootloader in the config.plist you have to don't "Hide" the APFS Preboot and Recovery hidden partition, otherwise you can't use the APFS Recovery.
  4. Here is my original method "translated" into an AppleScript so anyone can put it on Automator and it will do the trick switching between a full translucent "dark mode" and a semi-translucent "light mode": tell application "System Events" tell appearance preferences if dark mode is false then set dark mode to true do shell script "defaults write com.apple.universalaccess reduceTransparency -bool false" do shell script "killall Finder" do shell script "killall Dock" do shell script "killall NotificationCenter" do shell script "killall Spotlight" else set dark mode to false do shell script "defaults write com.apple.universalaccess reduceTransparency -bool true" do shell script "killall Finder" do shell script "killall Spotlight" end if end tell end tell Here is the Applescript already-ready to download: hybrid dark light switch.zip
  5. jackluke

    Lenovo ThinkPad T420 with UEFI Only

    Not only, it allows to keep Dock and Notification Center transparencies fixing only the "grey" finder menus in "light mode", while using that from the Accessibility prefpane "Reduce Transparency" everything become without any transparency.
  6. Yes, I have exploited the "reduce transparency" Accessibility feature discovering that doing it from Terminal until you don't relaunch Finder.app or Dock.app (I mean the CoreServices app) the GUI will keep a partial transparency, it's not a long run patch however it works and totally harmless for the system. In your specific case I guess you refer to these dictionary keys: Light mode: defaults delete Apple\ Global\ Domain AppleInterfaceStyle Dark mode: defaults write Apple\ Global\ Domain AppleInterfaceStyle Dark You can follow the method I used for create my script, to see the immediate effect without logout/login just type from Mojave Terminal: defaults write com.apple.universalaccess reduceTransparency -bool false killall Finder killall Dock killall NotificationCenter killall Spotlight While this is used only for the "light mode": defaults write com.apple.universalaccess reduceTransparency -bool true killall Finder killall Spotlight
  7. I did already tried to create an automated process in this way: creating a mojavehld.plist in /Library/LaunchDaemons/ to execute a script before shutdown and startup creating a mojavehld.sh in /Library/LaunchDaemons/ to execute the script to keep the "hybrid transparency" pointing the mojavehld.plist to the mojavehld.sh sudo chown 0:0 /Library/LaunchDaemons/mojavehld.plist sudo chown 0:0 /Library/LaunchDaemons/mojavehld.sh sudo launchctl load -w /Library/LaunchDaemons/mojavehld.plist One little issue I've encountered is that I've to consider to edit this file before the loginwindow: ~/Library/Preferences/com.apple.universalaccess.plist In Mojave this is not in plaintext but binary encoded, so it will result a bit invasive for most users. For now I believe that the script I did on the main post is a good workaround for those who want to use a temporary "light mode" until a reboot of course, and even if a bit uncomfortable, relaunching the script after a restart to me is not a drama.
  8. Ok that's a legacy Nvidia Tesla so it works, but unluckily in your case probably there is conflict with your internal "trackpad", try with an USB mouse to notice that "hybrid transparency" is working. Ok then go through "System Preferences - Accessibility prefpane - Display" de-select the "reduce transparency" checkbox Then relaunch my script and type 1, close Terminal, now it should give Dock and Notification Center transparencies and fix the greyed Finder menu.
  9. Of course HD4000 is Metal supported, you should instead try that on HD3000 that is OpenGL only (non-Metal), or any Legacy Nvidia Tesla or ATI with QE/CI. Please try that on an HD3000 and you'll notice what I meant. Anyway you evidenced the less important thing into your screenshot, my patch is working fine. If you get offended because I called it "patch", call as you want, but I can assure that this little script does its own duty as workaround for Mojave "light mode". You can't find a better solution till now to keep transparent Dock and at the same time a clear white opaque Finder menu bar in "light mode". Which GPU do you have ? Try again these steps, launch the Terminal mojavehld.command then type followed by "enter key": 2, 1, 4 Probably when you lost the trackpad, if in the "meanwhile" you used an USB mouse you could notice that script was perfectly working.
  10. Mine has a totally different purpose, is needed to fix the "grey" Finder menu bar on unsupported Metal GPUs for Mojave "light mode", it enables a "partial transparency reduction" while that link you posted is an applescript for "global transparency reduction". And my "patch" doesn't require any "sudo" or "System Events" permissions. The "new" is that you will have an opaque Finder menu while keeping all other elements like Dock, Notification Center and some other transparencies. This is needed for Mojave "non-Metal" GPUs with only OpenGL rendering, as a workaround for the "light mode".
  11. Those who use Mojave with an OpenGL (non-Metal) Video Card in "dark mode" have noticed that global transparencies are working fine, while in "light mode" encountered the "grey" Finder menu bar and sidebars issues, this patch is intended for those who want to use Mojave mainly in "light mode" saving some transparencies around, so here is my "hybrid reduce transparency" patch. It is totally safe, harmless and reversible, it has been deeply tested and will 100% work until restart or logout, even after sleep lock screen it will still work. To return with normal "transparency" you can also do that from Accessibility prefpane disabling the "reduce transparency" checkbox. To use this patch just double click on this attached shell "mojavehld.command" and it will launch through Terminal. [METHOD 1: Enable hybrid transparency] After launch the mojavehld.command just follow these steps: type 1 type 4 close Terminal (CMD+Q) and any other app previously opened. (The choice number 3 is not mandatory) [METHOD 2: Force hybrid transparency] If for some reason after that you will still get Dock and Notification Center without "transparencies" then relaunch the mojavehld.command: type 2 type 1 type 4 close Terminal (CMD+Q) and any other app previously opened. Download attached here: mojavehld.zip
  12. it seems that starting from lion the kext cache doesn't work anymore, however I had the same issue still waiting for root device changing from VM bios the scsi order didn't do the trick rather bring me back to the EFI console, I discovered that this was due to the fact that after installing I have removed/moved/added the virtual scsi hdd changing its position in vm settings from 2nd to the 1st (as primary) and get an unresponsive system, so I suggest you don't switch the virtual scsi hdd after install just remove the hdd installer.
  13. about the videos same issue after a while, could be the beta bugs or QE/CI missing callings, indeed for me on workstation 8.0.2 no need to fix the vmtools, ESXi is totally another environment, another world I would say
  14. you have not to update from lion, but do you have already installed it or you need to install? Anyway if as I say in first point, you can't neither boot the installer you need to copy in this path Volumes/YourMLHddlabel/System/Library/Extensions of your virtual scsi hdd FakeSMC.kext and maybe AppleLSIFusionMPT.kext taken from your Lion, then to make these patches work you need to repair/fix permissions of those files in that folder path, so at the next reboot you can load up your vmdk installer. On a single file you can do this way: open terminal give sudo su reach that folder path through cd Volumes/YourMLHddLabel/S/L/E chown -R 0:0 FakeSMC.kext chmod -R 755 FakeSMC.kext
  15. here: http://goo.gl/WdeHi
×