Jump to content

Matgen84

Donators
  • Content Count

    1,806
  • Joined

  • Last visited

  • Days Won

    8

Reputation Activity

  1. Like
    Matgen84 reacted to ITzTravelInTime in TINU: The bootable macOS installer creation tool - Mac app   
    I am creating a TINU 2.0.2 version which for you will be just a small bug fix and improvements version, with the addition of macOS mojave dark mode support, but it will have a whole reorganizzation of some of the code, i am working on it as a preparation work for TINU 3 and also for a future app store upload which will require me to work more professionally following the Mdel View Controller method for the code.
     
    But debugging on macOS mojave beta is still very buggy, so i am working on macOS high sierra and then testing the code on macOS mojave.
     
    As always i will keep you updated.
  2. Like
    Matgen84 reacted to Badruzeus in Clover Themes   
    Well, 3 new Clover themes with drive icons are available on the repo. Enjoy! 
     
    1. FlatCamp

     
    2. Classical
     
    3. ClassicalDark
     
     
  3. Like
    Matgen84 reacted to arsradu in [pre-release] macOS Mojave   
    Well, the APPS need to be optimised to run on the new OS, not the other way around.  So...I'm feeling confident that this will be fixed by the app manufacturer sooner or later. I really doubt that this is something that Apple removed or something. I mean, I looked at your hardware config. I'm sure there is nothing there that can't run this "$8000" software.  But again, apps need to be updated sometimes, to run on the new OS. And that's a job for the APP developer, not the OS manufacturer.
    I remember a few years ago when they released Yosemite if I'm not mistaken...almost none of the apps in the Adobe Suite would run on the new OS. They've been updated, obviously, and they run perfectly fine now. But when the OS was first released to the developers (by the way, this is exactly why Apple releases a DEVELOPER Beta in the first place, so that app developers can build and optimise their apps for the new OS before it hits final version), the apps were not optimised and they would often crash. C'est la vie! It will most likely be fixed in the future.
     
    For example, I'm using Adobe products, and, even though they don't crash or something, they are not yet optimised for Mojave. And I'm not gonna blame Apple for this, since it's not their fault. :)) Actually, the OS even mentions that the app is not yet optimised. It's a BETA. And not just A BETA, it's the FIRST BETA. I wouldn't recommend anyone switching to it full time, unless they're ok with the downsides.
  4. Like
    Matgen84 reacted to Download-Fritz in AptioMemoryFix   
    But boot.efi does, which is what I said
  5. Sad
    Matgen84 reacted to SavageAUS in Build_Clover.command, another Script to build standard Clover (or customized)   
    I only get offered xcode 9.4 in mojave.
    EDIT: Downloading Xcode 10 beta now, will test and report.
     
    EDIT: @Matgen84 Does not compile with xcode 10 beta yet, unknown xcode version error.
  6. Sad
    Matgen84 reacted to arsradu in Build_Clover.command, another Script to build standard Clover (or customized)   
    Well, building might not be the problem...when you have the source code. Unfortunately, svn is down...again.
  7. Like
    Matgen84 reacted to Sherlocks in [pre-release] macOS Mojave   
    no need to update bios version everytime in smbios part if you use latest clover. clover compare your config bios version to clover's bios version. then determine lastest bios version.

     
    나의 LG-F800S 의 Tapatalk에서 보냄
     
     
     
  8. Like
    Matgen84 reacted to XLNC in Clover General discussion   
    that file is not there in my EFI/CLOVER/ 
    only config.plist is present there .
  9. Like
    Matgen84 reacted to vector sigma in Clover General discussion   
    What should be AMB.plist?
    EFI\CLOVER\AMB.plist not loaded with name from LoadOptions: Not Found  
  10. Like
    Matgen84 reacted to SavageAUS in Donator status   
    Hi, not sure if i need to post or wait but i made a dontion to insanelymac and was wondering if i needed to let anyone know or if my status will just be updated after x amount of time.
  11. Like
    Matgen84 reacted to Sherlocks in Lilu — kext and process patcher   
    report.
    lvs1974 kexts are working in 10.14.
    i checked all.
    thanks in advance
  12. Like
    Matgen84 reacted to SavageAUS in [pre-release] macOS Mojave   
    Yeah it is only beta, maybe next release they will readd support for it. I do plan on getting one of those osxwifi adapters with wifi + bt.
    Yup the AirPortAtheros40.kext is missing from /System/Library/Extensions/IO80211Family.kext > Contents/Plugins
    So i have copied it form High Sierra and rebuild permissions, will reboot and test.
    Edit: Fixed.

  13. Like
    Matgen84 reacted to ammoune78 in [pre-release] macOS Mojave   
    It just need to put HS network kext for it to work!
  14. Like
    Matgen84 reacted to SavageAUS in Build_Clover.command, another Script to build standard Clover (or customized)   
    I know its beta but just reporting that i cannot add symlink in Mojave
    Extra lines removed.

    Last login: Sat Jun  9 20:11:41 on ttys000 Shanes-MBP:~ shane$ /Users/shane/Documents/Build_Clover.command   ================================================================================ Build_Clover script v4.8.5                                  No update available.                              <-------------------------------------------------- ================================================================================ By Micky1979 based on Slice, apianti, vit9696, Download Fritz, Zenith432, STLVNUB, JrCs,cecekpawon, Needy, cvad, Rehabman, philip_petev, ErmaC   Supported OSes: macOS X, Ubuntu (16.04/16.10), Debian Jessie and Stretch                              <-------------------------------------------------- CLOVER Remote revision: 4523 Local revision: 4521 EDK2 Remote revision: 27308 Local revision: 27233   The current local EDK2 revision is the suggested one (27233).  Used settings: /Users/shane/BuildCloverConfig.txt                               <-------------------------------------------------- Please enter your choice:   1) add "buildclover" symlink to /usr/local/bin  2) update Clover only (no building)  3) update Clover + force edk2 update (no building)  4) run my script on the source  5) build existing revision (no update, for testing only)  6) build existing revision for release (no update, standard build)  7) build existing revision with custom macros enabled  8) enter Developers mode (only for devs)  9) Try Clover Configurator Pro.app  10) edit the configuration file  11) Exit ? 1   /usr/local/bin does not exist, cannot add a symlink..   Press any key to continue...   Please enter your choice:   1) add "buildclover" symlink to /usr/local/bin  2) update Clover only (no building)  3) update Clover + force edk2 update (no building)  4) run my script on the source  5) build existing revision (no update, for testing only)  6) build existing revision for release (no update, standard build)  7) build existing revision with custom macros enabled  8) enter Developers mode (only for devs)  9) Try Clover Configurator Pro.app  10) edit the configuration file  11) Exit ? 
     
    In terminal i did sudo mkdir /usr/local/bin
    Then i was able to add the symlink.
  15. Like
    Matgen84 reacted to arsradu in [pre-release] macOS Mojave   
    OMG...did you actually install ALL drivers suggested by the Clover installer? :))))
    This proves what I was saying the other day with many users not knowing what they need or not need...
     
    Alright, I think I found the culprit.  I'll try to cleanup the drivers folder and upload a more streamlined version so we can try it out.
     
    Update:
     
    @robi39 Ok, please, remove the current drivers64UEFI folder (or make a backup of it on your Desktop if you're planning to compare the two of them) and replace it with the attached one. Try the installer again.
     
    Update2:
    Though not related to the current issue, your kexts/Other folder could use a cleanup, as well. Since, I'm pretty sure at least SOME of those kexts are redundant or not necessary. But we can talk about that after we solve the initial issue with the installation.
    drivers64UEFI.zip
  16. Like
    Matgen84 reacted to crazybirdy in [pre-release] macOS Mojave   
    Find (Post #72)
     
    Waiting for lucky day in an upcoming beta.
    ----
    Mac Pro (Mid 2010) is W3530, E5620, both are SSE4.2 cpu.
    I think it's the end now for SSE4.1 cpu.
     
  17. Like
    Matgen84 reacted to moman2000 in [Guide] [10.14] Installation Guide for macOS 10.14 Mojave Beta   
    Hi,
     
    Here is my guide for making a bootable media for installation of macOS 10.14 Mojave Beta
     
    Pre-Requisites
    A computer running macOS / or at least OS X 10.7.5 A USB Drive of at least 8GB in size. Access to Installation App "Install macOS 10.14 Beta.app" Clover EFI Installer /// Clover r4509 and prior releases are known to not work well with Mojave... Try to avoid it. Thanks @Hervé 
    Download here:https://github.com/Dids/clover-builder/releases Some time to have fun behind your screen  
    Steps:
     
    Step 1:
    WARNING: Erasing your USB drive will remove all contents off it. If you need to backup the data on the USB Drive, DO IT NOW!
     
    a) Plug in a USB of at least 8GB in size. I used a partition of my SSD.
    b) Open Disk Utility and format the aforementioned USB Drive with these options:
    Name: "USB" (without quotation marks) Format: Mac OS Extended Journaled Scheme: GUID Partition Map  
    WARNING: Erasing your USB drive will remove all contents off it. If you need to backup the data on the USB Drive, DO IT NOW!
     
    Press Erase and let the process complete.
     
    Step 2:
    a) Open Terminal and run this command:
    Notice that the "--applicationpath" command is not included as it is now depreciated. In addition to this, "--converttoapfs NO" is also depreciated and therefor macOS Mojave can can initially be installed on HFS+ but, the installer will later convert it to AFPS if you are using a SSD for the installation. Please bear this in mind before continuing.
    sudo /Applications/Install\ macOS\ 10.14\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB WARNING: Erasing your USB drive will remove all contents off it. If you need to backup the data on the USB Drive, DO IT NOW!
     
    Press Enter and then "Y" to confirm the erase and let the process complete.
     
    Upon completion, the USB will be renamed Install macOS 10.14 Beta.
     
    Step 3:
     
     
    a) Download the latest version of Clover from sourceforge
    b) Open Clover package installer
    c) Hit Continue, Continue, Change Install Location...
    d) Choose the USB, now called Install macOS 10.14 Beta
    e) Hit Customise and install Clover to the same USB using one of the following examples:

    f) Copy apfs.efi to /EFI/CLOVER/drivers64UEFI/ See attachments for latest version as of writing this guide
    g) Navigate to /EFI/CLOVER/kexts/Other/ and add FakeSMC.kext Choose the latest version!
    h) (Optional) Navigate to /EFI/CLOVER/kexts/Other/ and add your ethernet kext
     
     
    Finished:
     
    You have now successfully created a bootable USB. You can now boot from this to install macOS Mojave Beta on your system.
     
    Good luck!
     
    Credits:
    Apple for macOS Insanelymac for this amazing forum Clover for Clover @Hervé Info on Clover Compatibility and APFS error  
     
    apfs.efi
  18. Sad
    Matgen84 reacted to crazybirdy in [pre-release] macOS Mojave   
    Same here,
    Core2 Duo E8400 (SSE4.1 only, no SSE4.2) + GT 640 1G, after installation success, boot to system restarting on gray screen and mouse.
    GPT + APFS, Clover 4522.
     
    Works fine with 10.13.6.
     
    I think, it may end of hackintosh(10.14) now.
  19. Like
    Matgen84 reacted to fusion71au in macOS Mojave - Launched   
    @fantomas1, I can confirm you can boot + install Mojave beta in normal mode (without acceleration) with unsupported HD5770 - desktop 2 specs in my signature .
     
    Updated Clover to latest (r4515+) and changed my SMBIOS from iMac11,3 to 14,2.  Boots with VESA safemode drivers.  Post install, I substituted some High Sierra 10.13.5 kexts to restore WIFI, SATA and graphics functionality:
     
    IO80211Family.kext v12.0 for my Atheros Wifi card AppleAHCIPort.kext v328 for 5 series/ICH10 SATA (@Sunki's patch doesn't seem to work in 10.14beta) AMD5000Controller, AMDLegacyFramebuffer, AMDLegacySupport, AMDRadeonX3000, AMDSupport kexts for my Radeon HD5770.  This was enough for CI to work but not QE acceleration (AMDRadeonX3000 from HS refuses to load).
     
     
    HS AMD Kexts.zip
  20. Like
    Matgen84 got a reaction from chris1111 in AppleALC — dynamic AppleHDA patching   
    Hi
     
    I left layout-id=1 (for my system) inject by Clover in High Sierra and Mojave, AppleAlc v1.2.8 works well, on both OS. I also use -lilubeta -alcbeta on 10.14.
  21. Like
    Matgen84 got a reaction from chris1111 in AppleALC — dynamic AppleHDA patching   
    Hi
     
    I left layout-id=1 (for my system) inject by Clover in High Sierra and Mojave, AppleAlc v1.2.8 works well, on both OS. I also use -lilubeta -alcbeta on 10.14.
  22. Like
    Matgen84 reacted to ellaosx in AppleALC — dynamic AppleHDA patching   
    success on Mojave but not on Sierra/High Sierra.
    It seems "auto convertion" of existing "layout-id" to "alc-layout-id" does not work on Sierra/High Sierra... it works n Mojave though.
    Just my observation.
    Thanks
  23. Like
    Matgen84 reacted to SavageAUS in Clover General discussion   
    Yeah it's all good. My uefi firmware has option for other os or Windows, when I switched to Windows option I could disable csm which gave me native resolution. (New monitor today)
  24. Like
    Matgen84 reacted to vit9696 in AppleALC — dynamic AppleHDA patching   
    Please pay an attention to this:
    the latest AppleALC in master addresses all the issues of 10.14. It works just fine by simulating an existing layout id and does not require any manipulations with your previous preferences.
     
    The only issue preventing it from working on your system are obviously your borked hands, and clearly in such a case you should refrain from installing betas. What you do here is only confusing other people, and misguide them by providing some pseudotechnical information.
     
    To summarise I suggest everyone to take a break. Thank you for understanding.
     
    Please note, that HDMI audio may need separate updates, and it will be addressed later in other kexts.
  25. Like
    Matgen84 reacted to arsradu in [pre-release] macOS Mojave   
    If you already have Clover 4515 installed on your HDD/SSD, you can use that to boot the USB drive, as well. Which has the advantage of keeping your USB drive untouched so you can put (ONLY) the installer on it.
     
    So, if you previously had Clover on it I would recommend removing it from EFI and using the one on your HDD to boot. Should also be easier since you won't need to constantly switch to the USB drive in Boot option screen. Not to mention, once the files are copied to the HDD/SSD, the installation actually continues from there, for as far as I know. So...I'm not sure you will need the USB drive anymore at this point. Could be wrong though.
     
    Anyway, what I would suggest:
    1. Format the USB drive (including EFI, or at least mount it and remove Clover from there manually, if you previously had it)
    2. Download the FULL installer. Make sure it's the complete one, and not just some 17MB installer. It needs to have around 5GB.
    3. Wait until it pops up to install it and Quit that.
    4. Open up Terminal and do:
    sudo /Applications/Install\ macOS\ 10.14\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled This assumes that your USB drive is called "Untitled" (default naming scheme). If that's not the case, adjust this part in the command above and try again.
     
    5. Wait for the process to complete.
    6. Boot from your HDD/SSD's Clover installation and select the USB drive (it most likely got renamed to something like "install......10.14 Beta" or something like that).
    7. Decide which partition you want to use and whether or not you want to format it and use that one for future reboots (it should say something like "Boot Install from....[insert partition name here]").
     
    Let's see if this works.
×