Contribute
Register

BrcmPatchRAM - Upload firmware into Broadcom Bluetooth USB devices

Status
Not open for further replies.
macOS Sierra 10.12.6

Hi, I am having problems getting my bluetooth working on my Azurewave AW-NB290 card. Card is BCM943225HMB and WiFI is working well with FakePCIID_Broadcom_WiFi.kext and FakePCIID.kext

My bluetooth appears to be loading but I cannot turn it off. It also has difficulty staying connected. I can see other devices fine and other devices see me fine. The bluetooth is also causing my system to fail to sleep/hibernate.

Because of all of these problems I have simply unplugged the USB connection to my PCIe card and my system works like a dream. Sleep and hibernation problems disappear.

I would like bluetooth to work if possible. If anyone can help.

I searched the Windows drivers package for my vendor (0x0489) and device (0xE030) IDs with no joy. So I presume and have attached the BrcmNonPatchRAM2.kext as noted for other BCM943225 devices. However, when I remove all PatchRAM kexts from clover I noticed no difference at all. The system still loads the bluetooth in the same condition as noted above. I am also not seeing the kexts loaded when I am injecting from clover.

I would also like to note I believe most documentation on the Azurewave BCM943225 is referring to the AW-NB290H

Im not sure where to move from here. Other than detaching the bluetooth/usb. I hope I can use it.

Thanks for your consideration.

[Attached Problem Reporting zip]

If you think your device does not require firmware, add the device-id/vendor-id to BrcmNonPatchRAM2.kext.
Look at the existing Info.plist to see how.
 
If you think your device does not require firmware, add the device-id/vendor-id to BrcmNonPatchRAM2.kext.
Look at the existing Info.plist to see how.
Thanks RehabMan for your reply. I added the vendor and product ID to BrcmNonPatchRAM2.kext. Because the documentation says BrcmNonPatchRAM2.kext relies on BrcmPatchRAM2.kext, does that file need any adjustments? Both are in my Clover kexts folder.

Anyway, I see no difference. Bluetooth still is on but cannot shut it off. Neither do I see BrcmNonPatchRAM2 as a loaded kext.

Added:
Code:
        <key>0489_e030 native</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string>
            <key>IOClass</key>
            <string>BroadcomBluetoothHostControllerUSBTransport</string>
            <key>IOProviderClass</key>
            <string>IOUSBHostDevice</string>
            <key>idProduct</key>
            <integer>57392</integer>
            <key>idVendor</key>
            <integer>1161</integer>
        </dict>
        <key>0489_e030 no firmware</key>
        <dict>
            <key>#FirmwareKey</key>
            <string>only load and unload native bluetooth</string>
            <key>CFBundleIdentifier</key>
            <string>com.no-one.BrcmNonPatchRAM2</string>
            <key>DisplayName</key>
            <string>Foxconn AW-NB290</string>
            <key>IOClass</key>
            <string>BrcmPatchRAM2</string>
            <key>IOMatchCategory</key>
            <string>BrcmPatchRAM2</string>
            <key>IOProviderClass</key>
            <string>IOUSBHostDevice</string>
            <key>idProduct</key>
            <integer>57392</integer>
            <key>idVendor</key>
            <integer>1161</integer>
        </dict>
 

Attachments

  • Screen Shot 2017-07-22 at 2.13.42 PM.png
    Screen Shot 2017-07-22 at 2.13.42 PM.png
    105.1 KB · Views: 136
  • Screen Shot 2017-07-22 at 2.14.28 PM.png
    Screen Shot 2017-07-22 at 2.14.28 PM.png
    123.4 KB · Views: 142
Thanks RehabMan for your reply. I added the vendor and product ID to BrcmNonPatchRAM2.kext. Because the documentation says BrcmNonPatchRAM2.kext relies on BrcmPatchRAM2.kext, does that file need any adjustments? Both are in my Clover kexts folder.

Anyway, I see no difference. Bluetooth still is on but cannot shut it off. Neither do I see BrcmNonPatchRAM2 as a loaded kext.

Added:
Code:
        <key>0489_e030 native</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string>
            <key>IOClass</key>
            <string>BroadcomBluetoothHostControllerUSBTransport</string>
            <key>IOProviderClass</key>
            <string>IOUSBHostDevice</string>
            <key>idProduct</key>
            <integer>57392</integer>
            <key>idVendor</key>
            <integer>1161</integer>
        </dict>
        <key>0489_e030 no firmware</key>
        <dict>
            <key>#FirmwareKey</key>
            <string>only load and unload native bluetooth</string>
            <key>CFBundleIdentifier</key>
            <string>com.no-one.BrcmNonPatchRAM2</string>
            <key>DisplayName</key>
            <string>Foxconn AW-NB290</string>
            <key>IOClass</key>
            <string>BrcmPatchRAM2</string>
            <key>IOMatchCategory</key>
            <string>BrcmPatchRAM2</string>
            <key>IOProviderClass</key>
            <string>IOUSBHostDevice</string>
            <key>idProduct</key>
            <integer>57392</integer>
            <key>idVendor</key>
            <integer>1161</integer>
        </dict>

BrcmNonPatchRAM2.kext has no dependencies.

No ideas on your issue without "Problem Reporting" files.
Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

If you need me to check your work on BrcmNonPatchRAM2.kext, you will need to upload it as well.
 
BrcmNonPatchRAM2.kext has no dependencies.

No ideas on your issue without "Problem Reporting" files.
Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

If you need me to check your work on BrcmNonPatchRAM2.kext, you will need to upload it as well.

Attached above in post #807. Seriously, thanks for taking the time in everything you're doing in this community. Ive read many of your posts/documentation to get my systems working.
 
Attached above in post #807. Seriously, thanks for taking the time in everything you're doing in this community. Ive read many of your posts/documentation to get my systems working.

Those "Problem Reporting" files were before my suggestion to edit BrcmNonPatchRAM2.kext Info.plist.
And no BrcmNonPatchRAM2.kext attached.

Any change requires new "Problem Reporting" files.
 
Those "Problem Reporting" files were before my suggestion to edit BrcmNonPatchRAM2.kext Info.plist.
And no BrcmNonPatchRAM2.kext attached.

Any change requires new "Problem Reporting" files.

You're right, of course. I've attached the full problem report after changes were made.
 

Attachments

  • problem report.zip
    2.1 MB · Views: 84
You're right, of course. I've attached the full problem report after changes were made.

The Info.plist you have in BrcmNonPatchRAM2.kext is corrupt.
Never edit plist files with a text editor. Always use a plist editor such as Xcode or PlistEditPro.
 
Hello. I got myself an IOGear GBU521. Am able to pair my BT earphones and get audio but the audio freezes when the mic needs to be used (Siri, Skype, System Preferences>Audio Input). I installed both BRCMFirmwareRepo.kext and BRCMPatchRAM2.kext with kextbeast but the firmware version is still stuck on 4096. Currently running Sierra 10.12.6.

Attached are the problem reporting files as well as the relevant screenshots! Thanks in advance!
 

Attachments

  • Problem Reporting Files Zhenyu162.zip
    2.3 MB · Views: 79
  • Screen Shot 2017-07-28 at 9.05.12 PM.png
    Screen Shot 2017-07-28 at 9.05.12 PM.png
    207.7 KB · Views: 134
Hello. I got myself an IOGear GBU521. Am able to pair my BT earphones and get audio but the audio freezes when the mic needs to be used (Siri, Skype, System Preferences>Audio Input). I installed both BRCMFirmwareRepo.kext and BRCMPatchRAM2.kext with kextbeast but the firmware version is still stuck on 4096. Currently running Sierra 10.12.6.

Attached are the problem reporting files as well as the relevant screenshots! Thanks in advance!

It is a mistake to allow Google Chrome to hook your USB ports.
See details in the laptop FAQ.
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html
 
Status
Not open for further replies.
Back
Top