Jump to content
Welcome to InsanelyMac.com - No more ads! And some exciting news... Read more... ×

Leaderboard


Popular Content

Showing content with the highest reputation since 11/24/2020 in all areas

  1. 12 points
    Dear forum dwellers and visitors, the team from CleverFiles is pleased to welcome you here. We've taken over this cozy Mac-devoted community space a couple weeks ago, and we are learning our ways around with the help of the friendly team of long-time admins and community supporters. First and foremost, we'll do our best to help the forums evolve and prosper. With some optimizations already under way, most of the sections you are all used to will live on. Expect a ton of new materials, FAQs and articles, product comparison and expert advice. You may have noticed the vastly improved speed, and tiny refinements here and there. The most important of those - we turned off all ads! We are committed to removing all distractions and boosting our communication on the way to the world's #1 fan-supported forums about Macs. We are open to your comments and suggestions. Have you found a bug or a forum issue, please report to our team asap. BTW, we are always looking for talented writers to help us with the new content (top-level English only, for now). Get in touch for our pricing offer. Seeking high quality, self-verified and self-uploaded content. Wordpress knowledge required. Contact us: send a direct message via these forums, email [email protected] or just post below... PS: Please excuse some technical turbulence the upcoming weeks while we are fine-tuning the new server. PSS: We are software developers, just like many of you. Our brainchild product is Disk Drill, the top data recovery app on the net. We'd appreciate a shout-out at www.cleverfiles.com - thx!
  2. 9 points
    chris1111

    Clover General discussion

    What do you think of a nice Folder Icon when the Backup Clover is done? some one propose a different style of folder? Or folder blue like Origin Big Sur ? Its look like this
  3. 8 points
    Jief_Machak

    Clover General discussion

    @PG7 @MICKHAEL and other who did the same : fixing kext loading problem by putting some kext in plugins directory of other kext must be a temporary solution. We can fix that in Clover, I'm sure, even if we hard code for the time being. Please, do not share over the internet your modified kext, because if you do, we'll start to have problem with people getting kexts without knowing there is unrelated plugins. So again do not share zip of these kext. Instead, let's fix that. The problem is that I asked more than one time to send us the needed order and I got response like "I put them in plugins so that's fine". Sorry to be ranting here, but NO, that's not fine as a solution. It's fine as a workaround. Please, people who got this problem : open an issue on github, let's fix this and go back to original version of your kexts. Why am I saying this : Do you realize how much time is taken by trying to help people ? All this time is less development time. And if we start having kext with random plugins inside, I'll have a lot of people sending me their debug.log... So please...
  4. 6 points
    Allan

    Site Issues

    And now with ads-free!
  5. 6 points
    iCanaro

    Clover General discussion

    Clover 5127 available https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5127
  6. 6 points
    Jief_Machak

    Clover General discussion

    @everyone : debug.log name has changed. It's now a timestamp followed by the name of the efi file.
  7. 5 points
    mifjpn

    Clover General discussion

    Thank you for always working for us, Slice, Jief, Chris. I have confirmed that Clover r 5127 works on Big Sur 11.1 beta1, Catalina (10.15.7). I also found that the 11.1 version number was not yet assigned to the icon. I would appreciate it if you could fix it. Thank you.
  8. 5 points
    Folks, the new M1 Macs are the real deal. I bought the cheapest M1 Mac Mini to test, and it plays back 4K timelines in FCP like butter and better than my i9 Hackintosh with Radeon VII that I built with this guide. I'm awestruck, it's a little beast and an engineering masterpiece. I'm going to dismantle my Hackintosh and sell it for parts. I want to thank everyone here that helped me along the Hackintosh journey, but it's time to go back to real Macs. Apple did it.
  9. 4 points
    Background: Since the Pre-Release of Clover v5123, OpenCore Momory Fixes have been integrated into Clover in the form of OpenRuntime.efi. It replaces previous AptioMemory Fixes. Since v5126 AptioMemoryFixes are obsolete and no longer supported, so an upgrade to v5126 is mandatory in order to be able to install and boot macOS BigSur with Clover. This guide is for everyone trying to update to the latest Clover version or having issues while updating from previous versions, so they can install and run BigSur on their Machines. While updating to the latest iteration of Clover, there are several obstacles one can come across along the way. This guide is here to assist users trying to make the switch from the "old" Clover version with AptioMemory Fixes to the new one with OpenRuntime and Quirks Settings in CloverConfigurator. Problem: If you update your existing Clover installation by either installing the clover.pkg file or manually updating it the way you used to this will most likely result in an inoperable bootlader due to missing boot parameters. Approach: In order to avoid the dilemma of your system not wanting to boot, you have to know that the following files are obsolete and are no longer necessary, so they should eiither be disbabled/deleted when updating Clover from a built prior to v 5123 or omitted altogether when setting up a new EFI Folder: AptioMemoryFixes: AptioMemoryFix.efi, OsxAptioFix3Drv.efi, OsxAptioFixDrv.efi and everyhing else containing "memoryfix". Unnecessary Drivers (for UEFI-based Systems): DataHubDxe.efi – enables DataHub Protocol Support if it is missing from the BIOS. Modern UEFI BIOSes support this. So it's probably only necessary for Legacy Systems. FSInject.efi – For Kext-Injecttion. But pretty much obsolete since it's fully integrated in Clover nowadays. Might be necessary for Legacy Systems, though. SMCHelper.efi – Necessary when using FakeSMC.kext and ONLY FakeSMC. If you use it in combination with VirtualSMC.efi, it leads to an instant Kernel Panics. So, in other words: when using VirtualSMC – which is higly recommended over FakeSMC – DON'T use SMCHelper, use it in conjunction with VirtulSMC.efi (although unnecessary in most cases). EmuVariableUefi.efi – necessary for emulating NVRAM, if NVRAM is either not available (legacy systems) or working incorrectly. OcQuirks.efi and OcQuirks.plist – delete if present. OcQuirks is a relict from earlier attempts to include OpenCore Booter Quirks into Clover up until version 5122. Incompatible Kexts – wherever possible, you should use the latest available kexts provided by acidanthera (one of the devs behind OpenCore). Because incompatible Kexts are a source for Kernel Panics. I had an issue with my Laptop where VoodooPS2Controller.kext would cause a kernel Panic when used alongside VoodooPS2Mouse.kext, VoodooPS2Trackpad.kext and VoodooPS2Controller.kext. At the time I updated clover from 5122 to 5123, I didn't know that these 3 kexts are now includes as plugins inside of VoodooPS2Controller, so having them twice would cause a panic. In general, having Kexts wich have depedencies to oher kexts can cause a KernelPanic if not loaded in the correct order. In OpenCore, you can and have to set up the correct loading order of kexts manually by yourself, but in Clover only a few essential kexts like Lilu and Fake/VirtualSMC are hard-coded in, so they are always loaded first. It took me a while to figure this out. So when you update Clover and you are using lot of Kexts (usually on Laptops), try to update all Kexts first using Kext-Updater which is incredibly useful tool to download all sorts of bootloader-related files, have a look inside of them so see if they include more kexts as plugins and make sure nothing is present twice – HID, Wifi and Bluetooth kexts come to mind here. If you get panics you can not isolate, just move all unnecessary kexts to the "off" folder to temporarily to work around the issue by starting with a minimal set up to get the system running. Then put the disabled kexts back one by one to find the culprit for the panic. Updating your EFI Prepare an USB Stick. Format it to FAT32 (MBR). We'll use it for testing our updated EFI Folder first, before copying it to the ESP on the HDD. Download the latest Clover Release as a .zip archive for a manual update (currently "CloverV2-5126.zip"): https://github.com/CloverHackyColor/CloverBootloader/releases Extract the .zip. We'll create our EFI based on the one insides of it. Have a look at the "EFI > Clover > drivers > off > UEFI" Folder – you find the following Files: Copy the following files over to EFI > Clover > drivers > UEFI: ApfsDriverLoader.efi, VBoxHfs.efi and OpenRuntime.efi Now we have a minimal set of Drivers which looks like shown below. The files tagged in gray are in the drivers Folder by defautl and are most likely unnecessary on UEFI-based systems. As mentioned earlier, SMCHelper MUST be deleted when using VirualSMC.kext! I would turn of each of the gray drivers one by one and chick if the system still boots without them. Next, copy over your kexts (updated to the latest available version, of course), your ACPI > patched folder and your config.plist form your existing EFI Folder Open CloverConfigurator and update it to the latest Version. It should now include a new section at the bottom called Quirks, as mentioned earlier Now open your config.plist you copied over from your working EFI and click on "Quirks". It should look like this (without the descriptions of course): Head over to the OpenCore Install Guide and pick the guide for your CPU Family and Platform. Jump to the "Booter" Section. It contains all required Booter Quirks tinted green in the screenshot. Make sure to unfold the "more in-depth info" box to see what they do. Find the options for your system and tick them away in Clover Configurator. Next, jump to the "Kernel" section of Dortania's guide and copy over the settings from "Quirks" and "Scheme". Again, make sure to unfold the "more in-depth" section to find all necessary settings. NOTE: some of the settings Located in "Kernel > Quirks" have different names and are located in the "Kernel and Kext Patches" section of Clover Configurator. These include: In most cases you have these set up correctly already, otherwise your system wouldn't have started before. But it's good to double check if you have settings enabled which may be unnecessary. Once you've ticked all the necessary quirks, save your configuration, copy the new EFI Folder to the root of your USB Flash Drive and try booting from it. If everything was set up correctly, the system should boot as expected. If it does boot, you can mount the ESP partition of your hard drive, backup your EFI Folder, delete it and put in the one from your USB Flash drive to make the changes permanent. TROUBLESHOOTING: If you get Kernel Panics take a note of them and head over to the OpenCore Troubleshooting Guide and have a look at the "OpenCore Boot issues" and "Kernelspace Issues" sections to find your error message and possible fixes to resolve it. Another great resource to check if your Clover config is set-up correctly in general (excluding Quirks) is the Hackintosh Vanilla Desktop Guide For more info about how OpenCore differs from clover and see which settings, drivers and features are compatible, check out the Clover Conversion Guide. Good luck! PS: If you run into trouble after following this guide you can upload your config.plist and I can have a look at the quirks. PSS: When running BigSur, you need to remove the PreBoot Volume from the "Hide" Section of the GUI because if I understand correctly, BigSur requires booting from it. PSSS: if your system boots correctly you can upload a screenshot with your quirks with additional Info like your Board and CPU which might be helpful for other users.
  10. 4 points
    chris1111

    Clover General discussion

    Yea me to I prefer the blue because its look like Apple folder
  11. 4 points
    Hervé

    The path is open : Hackintosh ARM

    I've got an old Acorn Archimedes A310 if anyone wants to have fun... Failing that, if anyone wants to look at Huawei's promising ARM-based desktop: https://www.slashgear.com/huaweis-arm-based-desktop-pc-could-leave-you-scratching-your-head-06627865/
  12. 4 points
    eSaF

    Site Issues

    Congrats on the improvements to the site, I thought I was imagining things when everything started being snappy again, no more waiting two minutes for uploads to appear etc, etc. Now we have a site that is very enjoyable again.
  13. 4 points
    Slice

    Clover General discussion

    Some kernel patches is not verified for 10.6 - 10.7 so we can account these systems are no more supported. But Clover versions before 5000 probably still support old systems.
  14. 3 points
    I've written some detailed guide in my time but I'm going to keep this one shorter. I want to accomplish 2 things with this write up.1. Address the native nvram problem, this is huge for people with similar hardware moving forward with Big Sur.2. Help others get installed and booted with a very clean setup. Hardware and OverviewASUS Maximus VII Hero Z97, 4790K, Sapphire Nitro+ RX 580 8GB, HDMI to 43" 4K screen. Modifying the BIOS to get native nvram fix for Big Sur is also confirmed working for these boards ASUS Z97 ROG Maximus VII Hero ASUS Z97-A, requires manual modifying of BIOS file ASUS Z97-P ASUS Z97 ROG Maximus VII Gene ASUS Z97 ROG Maximus VII Ranger ASUS Z97 ROG Maximus VII Impact ASUS Z97 ROG Maximus VII Formula ASUS H97M-E ASUS Z97-PRO(Wi-Fi ac) This included setup was used to upgrade directly to from Catalina to Big Sur but installation should be fine as well.Using OpenCore 0.6.3 and latest kexts. Using SMBIOS iMacPro1,1 even tho it may be frowned upon but it worked for DRM at least in Catalina, not willing to change it now. You can however do as you please.Everything pretty much works. FaceTime, Messages, AppStore etc. Waking the computer from sleep though requires pressing the PWR button.There is no options in OpenCore or Clover, drivers or magic to get native nvram working. You have to modify the BIOS or flash an old one that doesn't have the white list as discussed below. So if you can't go through with fixing the NVRAM, you will have to use the transplant method.NVRAM Problem Big Sur installer fails after about 20% progress in the Apple logo, fails shortly after disk#: device is write locked ending with apfs_vfsop_unmount. Verbose output below just before restart. I imagine a new install the same problem occurs because after the first state information on the drive and whatever is stored in the native nvram and the installer can't access something that is not there because it wasn't saved in the first place. BackgroundReddit post here starts to question it as Haswell in general but seemed more an issue with ASUS Z97 boards. A comment in that thread led me to Vit9696 saying fix your NVRAM. All other paths led to devs are aware and it's an macOS bug or giving up and transplanting the installation by using another machine. Well I ain't having none of that, Vit9696 said fix nvram, so I fixed it.WhyVit9696 actually solved this for us years ago here. The key take away is the whitelist part and replacing NvramSmi driver. FixAs stated above we can extract the NvramSmi driver from an older BIOS and the replace it in the latest one. I believe most our boards from this era are no longer being supported but the latest firmwares do have microcode to patch vulnerabilities like Spectre, meltdown, etc. It would be ideal to go this route and it's not that hard and working nvram is great!I'm guessing another way would be to flash back to old BIOS where native nvram is working and upgrade/install Big Sur and then flash the latest after. You could save your BIOS profile if available that way you won't have to set everything back up. If this is also the case for incremental updates, sounds like a nightmare.How (I chose to fix)Replacing the NvramSmi driver made the most sense and it was relatively easy. I am no expert and you know the responsibility I take in anyone trying this **** and failing, ZERO.To find a BIOS version before the whitelist was added to the NvramSmi driver I used the dates from the link in Vit9696's quotes. User 314TeR said his ASUS Maximus VII Impact nvram broke after 0412 which was released 2014/10/17 and worked with 0217 released 2017/07/28. To me anything after 2014/10/17 will have added the whitelist.So with my board I downloaded version 1104. THE BELOW METHOD HAS AN ISSUE WITH XMP and RAM SPEED. No matter what you set in BIOS, ram speed will remain default, likely 1333Mhz. I updated the steps and linked below to fix that but it does require Windows. No other issues have been found other than that so if you don't mind or were already using default ram speeds then you don't have to redo anything. Download UEFITool 0.26.0 as the latest versions won't let you rebuild/replace.Download latest BIOS and one without whitelist.Load older BIOS in UEFI tool, my case 1104. Search with text nvramsmi and extract as is, the file section. Like below. Save the ffs, name it whatever and close out we are done here.Load the latest BIOS now, 3503 in my case and search nvramsmi again. This time replace as is and select the ffs you just named and saved. You can't flash the modified BIOS as usual, they are contained in a way with write security. I just used my board's USB Flashback Utility. Named the modified BIOS to M7H.CAP, each board will have it's own naming method. Copied to a fat32 usb, stuck it in the correct USB port in the back and pressed the button for 3 seconds. 2 minutes later and I was booting my modified BIOS and restarted the upgrade process again from within macOS. That last bit is IMPORTANT, if you were trying to upgrade from Catalina and have the bootable option to install MacOS it still won't work after you fixed your nvram. You MUST restart the process again from within Catalina. If you don't have USB Flashback Utility, take a look here for alternative ways.After BIOS modified flash test your nvram, mine worked right away. Then I tried the upgrade and that worked fine. I believe it was 4 phases total and 3 reboots. Took about 25 minutes on SSD.My modified BIOS 3503 is attached, don't be stupid with it and try to install on a different board. Rename it accordingly if you want to use it.Some BIOS SettingsAHCI - EnabledVTD - DisabledPrimary Display - AutoCPU Graphics Multi Monitor - DisabledLegacy USB - EnabledxHCI - EnabledEHCI handoff - EnabledFast Boot - DisabledSecure Boot - Other OSCSM - DisabledOpenCore Configuration Basic Understanding ACPI SSDT-EC.aml - fix for EC on Catalina and above SSDT-GPRW.aml - fixes immediate wake from sleep, paired with rename patch in plist SSDT-LPCB.aml - allows AppleLPC to be loaded, helps with power management SSDT-PLUG.aml - necessary for CPU identification and power management SSDT-SBUS-MCHC.aml - allows AppleSMBusPCI/Family/Controller SSDT-USBX.aml - USB power config Drivers AudioDxe.efi - boot chime HfsPlus.efi - reading Hfs partitions OpenCanopy.efi - GUI boot picker OpenRuntime.efi - NVRAM, memory management, etc Kexts AppleALC.kext - audio IntelMausiEthernet.kext - nic Lilu - various fixes and system enhancements USBPorts.kext - USB Mapping (you can edit this details in USB section) VirtuaSMC.kext - Apple SMC emulator WhateverGreen.kext - various fixes for graphics and system devices Resources download from binary resources, removed all audio except boot chime Tools OpenShell.efi - shell cli config.plist Highly suggest looking at the Dortania Guide Haswell section if you are want to know why x is set the way it is, I don't have time for that and that information is readily available USB PortsIf all accessible ports are enabled in our system it is going to break the 15 port limit so a single sacrifice needs to be made. Instead of wiping out a whole port, I personally removed USB 2.0 ability on one of the USB 3 ports.The included USBPorts.kext includes all 16 ports, so the last USB 3.0 port SSP6 port(furthest from ethernet) will not function at 3.0 speeds if you use this kext as is. Customizing is simple with the kext. Open the plist inside the kext and you can remove the one port/functionality you don't need. Included are pictures labeling what is what HSXX and SSPX. There's also a SSDT included to help identify.Shout out to @YoshiMac for posting images of the USB ports mapped out. I included some of his work so you have quick access when deciding but his post is great as well. Hopefully I can return the favor a bit with this guide.OpenCore Config Customize While I added a SMBIOS just to get you going, you need to get your own SMBIOS - > https://dortania.github.io/OpenCore-Install-Guide/config.plist/haswell.html#platforminfo I'm using UIScale 2 for HiDPI, where as you may need to change to 1 Boot args currently uses verbose, you can remove that if all is well after I'm sure I'm forgetting to mention stuff, just let me know if I should warn about some other stuff here. Files AttachedThe included EFI is OpenCore 0.6.3 with updated kexts as of 11/18/2020USB Folder includes pics of the mapping and original USBPorts.kext with 16 ports for back up. There is also .dsl file which maps the ports if you need some clarification textually, do not use it.Modified 3503 bios for Maximus VII Hero with replaced NvramSmi from 1104.Well that wraps it up I think. If you need any extra advice or questions shoot away. Asus Maximus VII Hero OC 0.6.3 Share.zip BIOS in next post due to size limit Modified 3503 bios for Maximus VII Hero with replaced NvramSmi from 1104. 3503modifiedM7H.CAP
  15. 3 points
    jlrycm

    Clover General discussion

    @naiclub, @iCanaro. Someone shared with me the attached kext that if loaded solves the Big Sur issue with the ASMedia 2142 based USB 3.1 controller. It was tested in a X299 build and in mine and it worked in the sense that the USB 3.1 drive I connect is recognized. Thanks a lot to all for the efforts and time spent trying to help me with this. Credit to @apfelnico ASMedia.kext.zip
  16. 3 points
    Slice

    Clover General discussion

    Clover take icon based on version number. If it is wrong then it is a bug. DataHubDxe is used for HWSensors project and some other applications and methods. But yes, you can live without this.
  17. 3 points
    Matgen84

    Clover General discussion

    Hi @Slice @Jief_Machak Thanks for Clover r5127 Release, and all the work you do for users Please, when do you plan to solve the problem of icons and detection of BS Recovery ! Since BS 11.0.1 Release and BS Beta 11.1, the Clover GUI don't show correct icons: os_mac instead of os_bigsur
  18. 3 points
    Cyberdevs

    Site Issues

    The search function is also fixed and the whole site seems to be more responsive Thanks for fixing it.
  19. 3 points
    Jief_Machak

    Clover General discussion

    That's why I've made it !
  20. 3 points
    kushwavez

    Clover General discussion

    So after some more testing I figured out my PS2 built-in kb doesn't work with AppleUiSupport.efi (because of the built-in AppleKeyAggregator?), so I can't input my password. If I add the separate AppleKeyAggregator.efi the error msg appears as mentioned above, no PS2 kb. I've had to add your "AppleKeyFeeder.efi" to get it working, now with that it's finally okay.
  21. 3 points
    Jief_Machak

    Clover General discussion

    The less you have the better. "AppleImageCodec.efi" seems not needed. "Not needed" is enough to say that there is a need for deleting it.
  22. 3 points
    iCanaro

    Clover General discussion

    I confirm; I don't use DataHubDxe.efi in any hacks
  23. 3 points
    Jief_Machak

    Clover General discussion

    yes
  24. 3 points
    mifjpn

    Clover General discussion

    Slice, Jeif, Chris Thank you for always doing the hard development work. I apologize to had be using my exaggerating "ethics". I don't want to lost your morale. Therefore, my tiny ethics can be disregarded. You have the skills and morale, you can beat me easiry. And I'm really sick. It's depression. I actually take dozens of anxiolytics. I say the truth. I'm afraid that someone is scared here,and can not talk here. I can understand PG7 said, thus,it's not a good idea for anyone to eliminate developers time. Therefore if someone can not codeing source,they must be not talk. So I apologize that I had demoralize you. I want to eliminate all that can interfere with your time. I would especially like to thank Chris and Jief and Slice for their moderation. Thank you. And I'm sorry. I hope that many voices will come together and that Clover will be great. I just love Clover's beautiful boot selection screen and the freedom to use Windows normally without disguising the BIOS. That's why I thought you wouldn't ignore those who demand aesthetics. As a result, it is wrong to allow the criticisms of those who are not worth your great efforts to be adopted. I am disappointed with myself. Please forgive me. I am especially grateful to Jief's message for giving me this opportunity.
  25. 3 points
    PG7

    OpenCore Discussion

    tesa with a FakeID of this "0x73001002 0x730F1002" in BigSur Beta 11.1 these IDs are already in the AMD9000Controlleur.kext of Beta 11.1 also has id 0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73401002 0x73411002 0x73471002 0x73471002 0x734711002 0x73601002 in AMDRadeonX6000Framebuffer.kext which means that working FakeID should normally take
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×