Contribute
Register

[Guide] Airport - PCIe Half Mini v2

Status
Not open for further replies.
Hi all,

I have a problem of my own to contribute to this thread. (Please point me in the right direction if a working solution's been posted before)

I've followed this guide and a couple other guides to get my AzureWave AW-CE123H working perfectly. Bluetooth works amazingly, I get 2.4GHz and 5GHz bands, it's recognized as Airport Extreme, FCC Locale, US Country code (see my last post about that), Handoff.
The only thing that's not working for me is Instant Hotspot. I've applied the-darkvoid's (He gave credit to Doktordok) Handoff / Instant Hotspot patch that's located here at post #6:

http://www.tonymacx86.com/network/1...apple-mini-cards-pcie-mini-pcie-adapters.html

I've tested Handoff a multitude of times, and it works pretty well (props Apple), but Instant Hotspot hasn't worked once. It appears in my wireless devices as:

Personal Hotspot:
Duncan's iPhone 6: (Cellular and battery information displayed here)

I click to connect with it, and it does something, and then it give me an error message (not word for word):

"Unable to connect to Personal Hotspot. Make sure your tethering device is on and in range." It's sitting 3 feet away from my computer most tests, and it hasn't worked once. Anyone else have / had the same problem with a possible solution?

Cheers!
 
Hi all,

I have a problem of my own to contribute to this thread. (Please point me in the right direction if a working solution's been posted before)

I've followed this guide and a couple other guides to get my AzureWave AW-CE123H working perfectly. Bluetooth works amazingly, I get 2.4GHz and 5GHz bands, it's recognized as Airport Extreme, FCC Locale, US Country code (see my last post about that), Handoff.
The only thing that's not working for me is Instant Hotspot.

Unfortunately I can't even get Handoff to work.. but can you explain your procedure on how you get "Bluetooth work amazingly"? That would be nice.

Thank you!
 
Folks, I need help in figuring out what is wrong with my configplist after I pasted patches to the kext patch section. After pasting these patches I am no longer to import and then export this file using Clover Configurator. The CC does not even recognize this as a ConfigPlist file. Can someone please review its contents and offer any advice.

By copy paste method the system was unable to boot.

Thanks and looking forward to hearing your responses.

issue resolved by using Plist Editor Pro.

 
Unfortunately I can't even get Handoff to work.. but can you explain your procedure on how you get "Bluetooth work amazingly"? That would be nice.

Thank you!

If you have the AzureWave AW-CE123H card what I'm about to tell you should work (since I'm using the same card), but theoretically this can also work with any wireless card w/ the BCM4352 wireless chipset. Make sure you have a vanilla IOBluetoothFamily.kext and IO80211Family.kext, and Clover, since all of my patches are done through Clover's Kext Patching. You'll want to download and install these 3 kexts :

https://www.dropbox.com/s/hhhihay3ry67wfc/bcm4352.kext.zip?dl=0
https://www.dropbox.com/s/5ewt3z6ly3voxpv/BTFirmwareUploader.kext.zip?dl=0
https://www.dropbox.com/s/nccu7r5xvxhv630/toledaARPT.kext.zip?dl=0

Install them w/ something like Kext Wizard, and make sure you rebuild the kernel cache. Also make sure that you have the boot arg "kext-dev-mode=1" on or else your system won't boot up and will give you the gray stop sign of death (the kernel detects unsigned kexts and doesn't let the OS boot)

Now that'll enable wireless and BT functionality (does on mine). To get it FULLY working though, you're going to need 3 patches: the 5GHz patch, the Full Continuity Patch (Handoff / Instant Hotspot), and the Airport Extreme patch. I'll put them below here (add these to Clover's config.plist KextsToPatch section):

5GHz Patch (Credit Skvo):

Kext to patch: AirPortBrcm4360

Find: 58 54 00 2B 18 2C 21 00 20
Replace: 55 53 08 0A 36 1C 47 00 0A

This patch will give you 5GHz bands on your wireless card and it'll have the OS detect the Locale as "FCC" and country as "US". Check my last post on here about that.

Full Continuity Patch (credit the-darkvoid / Doktordok):

Kext to patch: IOBluetoothFamily

Find: 8B 87 8C 01 00 00
Replace: B8 0F 00 00 00 90

This patch will change the IOBluetoothFamily code so that when the OS calls the method getCompatibilityFlags(), it will return 0xF (or 0x0F, can't remember), which means all features (aka Handoff / Instant Hotspot). I haven't gotten Instant Hotspot to work, though, let me know if somebody has :)
Now an important thing after applying this patch and restarting your computer is to LOG OUT OF ICLOUD ON ALL OF YOUR IDEVICES! The handoff option on your Hackintosh won't appear until you log out and back into iCloud on your iDevices (it's in system preferences on Hackintosh). Make sure you don't skip this. Once you have you should have an option to enable Handoff in the "General" system preference pane.

Airport Extreme Patch (credit Skvo):

Kext to Patch: AirPortBrcm4360

Find: 6B 10 00 00 75 0D
Replace: 6B 10 00 00 90 90

This basically will change it so that instead of being as recognized as a "Third-Party Wireless Card" as it does OOB (after installing kexts), it'll be recognized as Airport Extreme.

Hope this helped you!

EDIT: I almost forgot! Make sure that you have an SMBIOS that will be able to be compatible w/ Handoff / Instant Hotspot. On my laptop I'm using a MacbookAir5,2 SMBIOS, and it works fine. I think you could use this as well, as you have an Ivy Bridge processor (MacbookAir5,2 is i5 & i7 IvyBridge)

Cheers!
 
Just a quick note or two on country codes and the 5GHz patch for the BCM4532 cards.

XT gives the following 'supported channels' for the card:

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 144, 149, 153, 157, 161, 165

While US reduces the number of supported channels to:

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 144, 149, 153, 157, 161, 165.

For a desktop unit, based in the US of course this makes no difference really (as actual channel is determined by the router locale) but for a laptop, where you may be travelling around the world with it, there might be some logic in keeping the country code for the card as XT.

Also I assume this patch comes from having made the following observations (please click the images to enlarge and then looked for the "grey" highlighted section):

HexFiend shot 1, showing the 4360 binary before 5GHz patch:

4360beforepatch.png


Hex fiend shot 2, showing original patch for 5GHz:

4360Skvopatch.png

Hex fiend shot 3, where the text on the right hand side is changed from "XT" to read "US":

4360US.png

This "US" patch therefore makes the assumption that the XT in the text (which has hex code 5854) corresponds to the country code for the card and that by changing XT to a desired letter combination (e.g. US which gives a hex value of 5553) will change the country code of the card.

If that were true then surely editing the text on the right and observing/implementing the hex code change in the left panel would lead to being able to set the country code for any given wifi area? However, I am not convinced that this is actually the case as any other change I attempt here (such as trying GB etc- hex 4742) still returns the locale within system profiler as being US....as do all the other letter combinations I have so far tried apart from XT....so maybe others can look at this and determine if these numbers/letters at this code section really are a valid way to change country code. Or maybe this card is only ever supposed to return US or XT as country?
 
Status
Not open for further replies.
Back
Top