Search results

Loading Google Results...
  1. telepati

    Disable system file protection in Big Sur!

    I am still skeptical about this. Because I don't have any problems with FF0F000 as shown in the picture. I think the biggest reason OTA is not working is to play with Snapshots.
  2. telepati

    New DRM enabling method for systems with AMD GPU

    Netflix and other streaming platforms are already running on all other browsers without SMBIOS connected. The goal is whether or not to work in Safari.
  3. telepati

    Disable system file protection in Big Sur!

    This is wrong which I am using this value since Public Beta 1 and I am always getting updates without any problem.
  4. telepati

    Disable system file protection in Big Sur!

    For my experience SIP never been the problem. My SIP and Authenticated-Root always disabled since Public Beta 1 but I never got a problem with the update. But deleting the snapshot completely messed up my update system and caused me to re-install the system each time.
  5. telepati

    TimeMachine Doesn't Backup in Big Sur Public Beta

    I don't know but I am using Time Machine with Public Beta 2. But Time Machine now using APFS even you format HFS+. When you try to select Time Machine Disk it formats auto to APFS.
  6. telepati

    macOS 10.15.5 Update

    Combo Update OC v0.5.9 with the latest commit everything smooth.
  7. telepati

    ASUS TUF Z390 - i7-9700k -iGPU: speed step does not work

    Follow this guide; https://www.tonymacx86.com/threads/macmans-build-asus-tuf-z390-pro-gaming-i9-9900k-vega-64-updated-for-10-14-6-and-nvram-support.275272/
  8. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    I guessed. Meanwhile, I was reading the guide. I saw it there too.:thumbup:
  9. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Are you using vault? If not you dont need AppleSmcIo. I dont know why you are need others?
  10. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    I am glad you figured it out. :clap: But don't use Clover .efi drivers with OpenCore. Also, why are you using Protocols?
  11. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Ok. Use your own config.plist. Just add these strings which are some of them empty in your NVRAM.
  12. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Cause EFI is not your boot drive. Choose number 4
  13. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Sorry my bad; Try this one I removed 0.5.7 entries; These two not recommended. NTFS Fat
  14. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef sometimes leaving empty field cause this type of error under the NVRAM. I forgot to remove Booter/Quirks ProtectUefiServices you can remove this you probably not use v5.0.7.
  15. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Actually none. I add a couple of deleting entries under the NVRAM and remove not recommended drivers. All others from your config but I used clean config.
  16. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef try this config with your Platform Info; dont forget to clean NVRAM.
  17. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    I will send you a new config.plist in a couple of minutes if you don't mind try with that.
  18. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Did you try with just two bootargs debug=0x100 keepsyms=1? Why are you using all beta args for debug or something else?
  19. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    But he can't boot, you can!
  20. telepati

    Gigabyte Z390 M Gaming build with working NVRAM

    Something wrong in your NVRAM section. Share your config.plist
Top