Search results

Loading Google Results...
  1. lulezi

    BrcmPatchRAM - Upload firmware into Broadcom Bluetooth USB devices

    Solved it! What did the trick was disabling the internal bluetooth module of the GA-Z170N-WIFI by setting the bootflag uia_exclude=HS08 so the ASUS BT-400 would be used.
  2. lulezi

    BrcmPatchRAM - Upload firmware into Broadcom Bluetooth USB devices

    I have an ASUS BT-400 which is showing up correctly in System Profiler - USB (see screenshot). However, in Blutooth, the MAC address is still 00:00:00:00:00:00 and while the Bluetooth icon is showing up in System Preferences and appears to be working, no devices will get listed. What did I do wrong?
  3. lulezi

    Clover won't boot USB Sierra

    I just found another way, although this does not make the change persistent and you have to do it again after every reboot. Boot up to the Clover screen. Then go to `Options` > `PCI devices` and set the checkbox at `USB Ownership`. Then go back to Clover start screen and start the installation.
  4. lulezi

    Clover won't boot USB Sierra

    check this out on how to mount the EFI partition: http://themacadmin.com/mounting-the-efi-boot-partition-on-mac-os-x/ when you've done this, you can run the command `open /Volumes/EFI/EFI/CLOVER/config.plist` in Terminal. this opens the `config.plist` file, which you'll have to modify according...
  5. lulezi

    Clover won't boot USB Sierra

    No, in the EFI partition of your USB drive, you have to modify the `/EFI/CLOVER/config.plist` (see this explanation on what to modify exactly).
  6. lulezi

    Clover won't boot USB Sierra

    Setting `USB FixOwnership` to `true` fixed it for me: https://clover-wiki.zetam.org/Configuration/Devices#devices_usb_usb-fixownership.
  7. lulezi

    Clover won't boot USB Sierra

    sorry, `ig-platform-id 0x19120000` should be `ig-platform-id=0x19120000`.
  8. lulezi

    Clover won't boot USB Sierra

    I just set up my first CustoMac too and ran into the same exact issue. I come to think of the possibility that the IGPU is not supported. adding `ig-platform-id 0x19120000` to the boot flags improves the situation a little, but doesn't really fix it.
Back
Top