Jump to content

Badruzeus

Members
  • Content Count

    1,279
  • Joined

  • Last visited

  • Days Won

    21

Badruzeus last won the day on December 22 2018

Badruzeus had the most liked content!

5 Followers

About Badruzeus

  • Rank
    InsanelyMac Legend

Contact Methods

  • Website URL
    http://www.technowtrend.com/

Profile Information

  • Gender
    Male
  • Location
    Indonesia
  • Interests
    Graphics Design.

Recent Profile Visitors

7,361 profile views
  1. Badruzeus

    Clover General discussion

    Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)? Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then? sudo nvram specialbootdevice blah blah blah Thanks. #EDIT: ..and I have this on my preboot logs with r4847: nvram_dmpstore_all_a43sj.txt.zip
  2. Badruzeus

    Lilu — kext and process patcher

    Yeah, weird.. where did you previously get Lilu 1.1 and it was installed using which method?
  3. Badruzeus

    Lilu — kext and process patcher

    At least give us your EFI\CLOVER\misc\preboot.log (Press F2 on Clover GUI) or ..\misc\debug.log: <key>Boot</key> <dict> <key>Debug</key> <true/> ... </dict>
  4. Badruzeus

    Clover Themes

    Thanks, working fine with BootCampStyle=true r4844-Test.zip #EDIT: I did patch ../menu.c before you edited the post with attached "CLOVERX64.efi", if I know this before; I won't patch && compile it my self but using yours LoL...
  5. Badruzeus

    Clover General discussion

    I believe there's better way than this: (Clover build root on my case is ~/udk, not ~/src)
  6. Badruzeus

    Clover General discussion

    Did you mean BootChimeCfg.efi? You could include it into package manually, right? Hah haa But *.wav files? Oh sh*t.. it makes the *.pkg "Not Sexy", can't imagine sound.wav && sound_night.wav from \themes will increase some MegaBytes in size, not a big deal since users are still able to customize by their selves (I think).
  7. Badruzeus

    Clover General discussion

    Use this option on your config.plist: <key>GUI</key> <dict> ... <key>Scan</key> <true/> ... </dict>
  8. Badruzeus

    Clover General discussion

    Weird is, now I'm also having a same issue even running Clover's UEFI Shell through VM (VirtualBox).. with or w/o drivers64UEFI/EnglishDxe-64.efi installed.
  9. Badruzeus

    [pre-release] macOS Mojave 10.14.3

    On going.. 2 updates in no more than a week, even faster than Linux hah haa.. but, w/o any changelog.
  10. Badruzeus

    Clover General discussion

    Yeah, those "Assertion" when I launched your EFI Shell Debug directly from BIOS (not Clover). If versioning is important, these what I got from different Shell's (via Clover Bootloader): Thanks. // EFI Shell from EDK2 r28597 or UDK2018 (Legacy w/o EnglishDxe): UEFI Interactive Shell v2.204 EDK II UEFI v2.70 (CLOVER, 0x000112EC) // EFI Shell from old Clover rev (UEFI + EnglishDxe, https://ptpb.pw/~Shell2.zip) UEFI Interactive Shell v2.0 Copyright 2009-2011 Intel(r) Corporation. UEFI v2.00 (American Megatrends, 0x0004027B) // OpenCore Shell (UEFI + EnglishDxe), https://github.com/acidanthera/OpenCoreShell UEFI Interactive Shell v2.2 EDK II UEFI v2.00 (American Megatrends, 0x0004027B)
  11. Badruzeus

    Clover General discussion

    (Late reply, sorry) With EnglishDxe.efi is installed on ..\drivers64UEFI, using Shell.efi as.. \EFI\CLOVER\tools\Shell64U.efi (via Clover UEFI) = BestLanguage ( ESP Root\SHELLX64.EFI (Launch EFI Shell via AMI Aptio v2.0.1 BIOS) = Screenshot below: Thanks.
  12. Badruzeus

    Clover General discussion

    just manually move it to drivers-off before ./makepkg lol
  13. Badruzeus

    Clover General discussion

    20 pages back on this topic, it's still not solved till now, honestly: On another side, @apianti ever said; it could be issue with specific firmware.. or Shell version matching. Using OpenCore Shell is a solution that I've found (on my case), beside using old version of your Shell.
  14. Badruzeus

    Clover General discussion

    (Sorry, I don't really get what your 1st line means actually) Yes, I'm able to manually replace Clover's EFI Shell with OpenCore's one as \tools\Shell64U.efi (before ./makepkg or after *.pkg installed). Would be better (for some with similar issue) if Installer do the work (user defined).
  15. Badruzeus

    Clover General discussion

    OK, thanks.. not a proposition, just my thought if it' s possible looks like.. 1. There's an Option on Clover package [ ] Tools: Shell (3rd party) 2. If user check it, provided Shell by Clover will be overrided by that one. Nevermind, I'm still able to run ebuild.sh then replace *.efi before ./makepkg (for my personal use).
×