Hervé

There's really nothing to it; it's as described in previous pages, i.e. Rehabman's latest build with uncompressed firmware v5803 posted on p5. Make sure to adjust PCI ids if required of course... Bluetooth_kexts.zip I've remembered I had my 12yr old Vostro200 Bluetooth mouse & keyboard lying around so I connected the mouse via Bluetooth and been using it without issue whatsoever for the last hour or so. SysInfo reports BT firmware v7 c5799, so not sure the targeted firmware actually loads but everything works fine for sure... Edit: no BT mouse disconnection or other issue after over 3hrs. All Ok as far as I'm concerned.

I'm not using any Bluetooth injector kext at all and have no issue whatsoever. TBH, I don't even know where the idea of this injector came from.

A real Mac card may not fit in your E7470; you'd need to check the physical space available. If it does, you'd need an M.2 adapter and, possibly, an antenna kit. You'd have to check the latest wireless cards used on Apple most recent Mac models of course but I understand that Apple used soldered components in some of their latest models. I use the BCM94360CD + mini-PCIe adapter in my older Hacks (Latitude E6220/E6230) and an M.2 DW1820A in my most recent Latitude 7490. In those recent Dell laptops, a compatible M.2 card is, by far, the best solution. Go for the DW1560 if you hesitate in a DW1820A.

Ok, got it. I've reverted to uncompressed firmware file; it's not as if it made a big difference in terms of size...

@wl_michael, quite possible I did something wrong; wouldn't be the 1st time... I simply Gzip'ed the extracted .hex firmware file but, yes, Rehabman's instructions clearly stipulate that the uncompressed firmware can load too. I looked at your files and I see the same 6KB .zhx compressed file I posted. I don't see any uncompressed file in there... Anyway, I've reverted to uncompressed firmware files and the version I seek to load now shows Ok in SysInfo: With regards, to the 2nd firmware file I had found and uploaded, it may not actually be a more recent firmware: even though the extracted file bears a name ending with "xxxx.0221.4688" when the previous one bears a name ending with "xxxx.0095.1707", once I load it, SysInfo displays version v7 c4688. So, who knows?

Where did you find this other version c5083? Or is it just a typo and you meant version c5803 which I posted a few days ago?

Obviously, the E5550 supports the latest and current macOS version, i.e. Mojave 10.14. Please refer to existing guides for this model in our Guides section and to existing topics/discussions in this current Support section. I also recommend you consult our FAQ section.

Please note that the Qualcomm wireless card fitted to your laptop is not supported. You may refer to our R&D-> Wireless section for inventories of alternatives.

Moved from "Installation Guides" to proper support section. Please make the effort to post in the appropriate and relevant forum sections in the future. There are existing guides for this model in our Guides section. Eg: Did you follow them?

What partition scheme did you use on your target SSD when you reformatted it? MBR or GUID? Should be latter, nor former.

You may lookup Muttonhead411's thread re: Bluetooth. Work was done on that yesterday.

The only thing I've now used intensively is my JBL speaker and I've had no issues whatsoever.

I don't believe there is an equivalent to HWMonitor for VirtualSMC. You may look at alternative apps such as iStat Menus but this may rely on data provided by the traditional sensor PlugIns of FakeSMC.

I know that screenshot! It's good old HWMonitor app that comes with FakeSMC package... You can Google for it.

Guys, 1st of all, check that the reported MAC address in the OS matches that of the label on the card. If it does not, well, I'm beggining to suspect that there are false or dodgy DW1820A cards being offered on the market (like there used to be for Apple's own BCM94360CD)... If all looks Ok, then please try the pin masking. That's it. Nothing further to offer.

I found version 4688, dated July 2018 which seems to work Ok too. BCM4350C5_003.006.007.0221.4688.hex.zip In BrcmPatchRAM2 kext, the FirmwareKey for device 0a5c_6412 in Info.plist file must be updated to "BCM4350C5_003.006.007.0221.4688" Edit: reverted to uncompressed .hex firmware file.

You could have followed this guide too, it may be more appropriate than the 7480.

Yes, it's been known for years and quite frequently/widely mentioned here and at other forums too. https://osxlatitude.com/forums/topic/3181-carbon-copy-cloner-and-chameleon-boot-loader/?tab=comments#comment-24428 https://osxlatitude.com/forums/topic/907-usb-configuration-seagate-hybrid-install/?do=findComment&comment=6248 https://osxlatitude.com/forums/topic/2836-how-to-dell-inspiron17-3721-fully-working/?do=findComment&comment=30498

Simple obvious logic... create 2 x config files, each with a different name and select/call on one or the other from Clover's main menu as required. Eg: Config_Moj.plist and Config_Cat.plist if you want or need to inject different kexts for the different macOS versions, place those kexts in the relevant 10.xx folders. As simple as that...

In case the above Google link becomes unavailable... Dell_Precision-M6800_Jul2019.zip

Ok, I downloaded the latest driver for DW1820A I could find on Dell's web site here (Win7 64bit for XPS 9350, dated May 2019). I extracted the firmware 1707 for our 0A5C:6412 DW1820A device: BCM4350C5_003.006.007.0095.1707_v5803.hex.zip All you need to do then is: copy the uncompressed .hex firmware file to the Resources folder of BrcmFirmwareRepo kext to supersede current version 1703 (=v7 c5799) update the key for device 0a5c_6412 in Info.plist file of BrcmPatchRAM2 kext After repairing permissions and rebuilding the cache, I can now connect to my JBL USB speaker without issues: This firmware version 1707 (which equates to v7 c5803) seems to be quite old (dated December 2015) but works Ok nevertheless. I'll try and lookup for a more recent firmware than that one. Edit: reverted to uncompressed .hex firmware file.

Funny that you copied all your add-on kexts to /L/E, except FakeSMC. Depending on your Clover settings, you could be trying to inject kexts that are already cached. So, copy FakeSMC to /L/E, repair permissions, rebuild your cache and set Clover kext injection to "Detect". Reboot and check Bluetooth again. This being said, your setup is probably Ok: your Bluetooth SysInfo, things look identical to the info for my own card. On my side AirDrop works perfectly with my other Hacks and so does HandOff with my iPhone. I had not even attempted to pair with any other Bluetooth device but on trying to connect to my JBL speaker, I too cannot establish a connection. I guess more work is required on that front. In all likelihood, Rehabman's kext need an update of firmware in which case you could try to extract the latest one as explained here. Device 0a5c:6412 is not mentioned in the list of tested devices but, nevertheless, it appears to be covered by a 4yr+ old firmware (BCM4350C5_003.006.007.0095.1703_v5799)... Looking at the contents of BrcmFirmwareRepo, you'll see a list of firmware and that's where the latest version for the DW1820A should go. I'll try to update asap.

Looking at Dell's documentation, the Latitude 5580 shows fitted with an Alps TouchPad. The driver page says it's compatible with other model such as the Latitude E6x30 or E6x40 so give Dr Hurt's kexts a try. Initially, I would have been tempted to say this laptop was likely fitted with an I2C TouchPad in which case I would have suggested you try the latest I2C PS2 kexts. The mouse pointer is unlikely to be supported by the I2C kexts. https://github.com/alexandred/VoodooI2C https://github.com/alexandred/VoodooI2C/releases Intel wireless cards are not supported (you appear to know that already), so you have to replace it by a supported model or, as you currently do, use a USB dongle. We have inventories of supported/unsupported cards available in our R&D section.

You could look at the info posted in the other topics in our Keyboard section that relate to the same issue.

Bluetooth has nothing to do with wireless. You've got to make sure you've got all your USB ports working through an injector or otherwise and then use Rehabman's firmware patching kexts as detailed in my 7490 guide.