Jump to content

[GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation


Krim404
1,809 posts in this topic

Recommended Posts

you have to enable it manually by adding something in some config file if the system you specify in the SMBIOS configs doesnt have a native HDMI port. bad thing is: i forgot how to do it and the tutorial has been deleted by tonys guys...

 

EDIT:

try http://www.insanelymac.com/forum/topic/319766-dell-xps-9550-detailled-1011-guide/- STEP 3.5.4

also for audio: http://www.insanelymac.com/forum/topic/319211-guide-fix-skylake-hdmidp-output/

Thanks for your reply wmchris!

 

So, I applied the HDMI output fix to config.plist>KernelAndKextPatches>KextsToPatch

 

I uncompressed layout-13.xml.zlib into layout-13.xml, and added the PublishHDMI_DP boolean as YES  to aDummyHDA.ext (attached with modification) yet no difference... :(

 

EDIT:

Actually - there is something different! My Sound broke  :w00t: And it's confirmed to be because of the PublishHDMI_DP...

aDummyHDA.kext.zip

Link to comment
Share on other sites

Thanks for your reply wmchris!

 

So, I applied the HDMI output fix to config.plist>KernelAndKextPatches>KextsToPatch

 

I uncompressed layout-13.xml.zlib into layout-13.xml, and added the PublishHDMI_DP boolean as YES  to aDummyHDA.ext (attached with modification) yet no difference... :(

 

EDIT:

Actually - there is something different! My Sound broke  :w00t: And it's confirmed to be because of the PublishHDMI_DP...

I'm still working on it. Currently I'm using macbook 9,1 SMBIOS which allows me to use both HDMI ports, d-sub, Ethernet & all of USBs (only external HDD/SSD is detected and mounted, attached mouse or keyboard wont work as well unfortunately, I hope to fix it as soon as I will finish uni work), All hotplugable. DisplayPort is not recognised and attaching any monitor to it result in having a black screen. 13,3 SMBIOS broke HDMI ports and audio, which I mentioned before and none of known fixes and patches works so far. Also if you plug in both monitor into HDMI and d-sub at the hub you will end up with two cloned desktops on each monitor instead of two extended desktops (this issues has been reported several times by Macbook Pro Late 2016 users so I hope so that Apple is working on it).

 

So far only macbook 9,1 SMBIOS allows me to use all of the features of macOS without breaking anything.

I have attached my EFI folder so you can compare what possibly you my missing in yours.

CLOVER.zip

Link to comment
Share on other sites

This all worked on iMac 17 skylake SMBIOS but I have now just like you changed to MacBookPro13,3 and my built in HDMI does not work anymore.

The guide says to go through the AppleGraphicsPolicies kext looking for the board-id and changing "config2" -> "none", but our board-id does not exist for the MBP13,3 SMBIOS.

 

So, I had 15 minutes over and had another look.

 

The KextPatch:

 

<dict>

<key>Comment</key>
<string>Fix HDMI output</string>
<key>Find</key>
<string>3e4d61632d423830394333373537444139424238443c2f6b65793e0a090909093c737472696e673e436f6e666967323c2f737472696e673e0a09</string>
<key>InfoPlistPatch</key>
<true/>
<key>Name</key>
<string>AppleGraphicsDevicePolicy</string>
<key>Replace</key>
<string>3e4d61632d423830394333373537444139424238443c2f6b65793e0a090909093c737472696e673e6e6f6e653c2f737472696e673e0a09090909</string>
</dict>

 

Is not useful at all and I can't believe I didn't cach that before.

 

What it does is the same as going manually into the kext and changing Config2 to none.

 

Search:

>Mac-B809C3757DA9BB8D</key>

<string>Config2</string>
 

Replace:

>Mac-B809C3757DA9BB8D</key>

<string>none</string>
 
As the board-ID with SMBIOS MacBookPro13,3 is: Mac-A5C67F76ED83108C it has no effect. Also as I stated initially there is no setup for Mac-A5C67F76ED83108C in the AppleGraphicsPolicies kext.
 
What I haven't tested yet is to actually add:
 
                                <key>Mac-A5C67F76ED83108C</key>
                                <string>none</string>
 
Since MBP13,3 does not have HDMI output, that just might be the right fix!
I'll check that out later.
  • Like 2
Link to comment
Share on other sites

Macbook 9,1 doesn't have HDMI output either (It have only single USB-C port) yet its working fine, at least display outputs and storage devices. Your patch doesn't work for me, just tried it. I might try it again to make sure that I didn't missed anything.

Link to comment
Share on other sites

Macbook 9,1 doesn't have HDMI output either (It have only single USB-C port) yet its working fine, at least display outputs and storage devices. Your patch doesn't work for me, just tried it. I might try it again to make sure that I didn't missed anything.

Oh no, the patch I copied in is the same patch as wmchris linked to.

 

As I wrote, there is no entry/configuration for our MacBookPro13,3 board-id.

 

I have however changed the patch to add our board-ID with the configuration none (Destroys iMac13,2 configuration)

 

Find: 

>Mac-B809C3757DA9BB8D</key>

<string>none</string>
 
Replace:
>Mac-A5C67F76ED83108C</key>
<string>none</string>
 

 

<dict>

<key>Comment</key>

<string>Fix HDMI output MBP133 Lockzi</string>

<key>Disabled</key>

<false/>

<key>Find</key>

<string>3e4d61632d423830394333373537444139424238443c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string>

<key>InfoPlistPatch</key>

<true/>

<key>Name</key>

<string>AppleGraphicsDevicePolicy</string>

<key>Replace</key>

<string>3e4d61632d413543363746373645443833313038433c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string>

</dict>

 

 

Unfortunately this does not work for me anyhow. I have also tried with adding the "PublishHDMI_DP" to aDummyHDA (http://www.insanelymac.com/forum/topic/319211-guide-fix-skylake-hdmidp-output/?p=2333909) yet it doesn't work and breaks audio.

 

I am on BIOS v 1.2.19 which has the change log: "1.Fixed Pre-OS has no display on external monitor with Lid Close issue" Maybe it also broke something?

 

 

 

UPDATE:

 

--Read from here --

Allright got it working!

 

 

The fix is to simply use the patch I provided.

 

<dict>

<key>Comment</key>

<string>Fix HDMI output MBP133 Lockzi</string>

<key>Disabled</key>

<false/>

<key>Find</key>

<string>3e4d61632d423830394333373537444139424238443c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string>

<key>InfoPlistPatch</key>

<true/>

<key>Name</key>

<string>AppleGraphicsDevicePolicy</string>

<key>Replace</key>

<string>3e4d61632d413543363746373645443833313038433c2f6b65793e0d0a090909093c737472696e673e6e6f6e653c2f737472696e673e0d0a09090909</string>

</dict>

 

Do NOT add the PublishHDMI_DP to aDummyHDA.kext.

 

I now have MBP13,3 SMBIOS with HDMI out working. 

 

post-1873639-0-72496600-1487604487_thumb.png

  • Like 2
Link to comment
Share on other sites

I am pretty sure USB C 3 does not work. Well I have a pixel XL phone that uses type USB C and I can charge a phone connected to the laptop. But I cannot transfer files. I know that it works on Windows 10. Anybody has any suggestions?

 

Sent from my Pixel XL using Tapatalk

  • Like 1
Link to comment
Share on other sites

@Lockzi

I tried your patch and it still doesn't work for me :(  I'm glad that it's working for you :) I guess I'll have to stick to Macbook 9,1 SMBIOS until I find my own workaround for problems with the display outputs. First of all uni work which seems to be never ending.

post-1631985-0-71236700-1487649171_thumb.png

I don't know what exactly make such a difference that both of my displays work under this certain smbios... 9,1 has USB 3-c port & newest Pro too, this doesn't not make sense at all. I'll have to check my config.plist and explore few others possibilities during next break. 

 

@hackedWiFi

Devices such as smartphone are not recognised properly by this port (Tested on iPhone7 & Galaxy S7 with USB-to-USB-c cable). Only what is working so far it's all sorts of Ethernet adapters, external HDD/SSD and I've check HooToo SD Card reader which was working just fine. Mouse & keyboard even don't show up at system information.

Link to comment
Share on other sites

@Lockzi

I tried your patch and it still doesn't work for me :(  I'm glad that it's working for you :) I guess I'll have to stick to Macbook 9,1 SMBIOS until I find my own workaround for problems with the display outputs. First of all uni work which seems to be never ending.

attachicon.gifUntitled.png

I don't know what exactly make such a difference that both of my displays work under this certain smbios... 9,1 has USB 3-c port & newest Pro too, this doesn't not make sense at all. I'll have to check my config.plist and explore few others possibilities during next break. 

 

You could try to add:

 

<key>ForceKextsToLoad</key>

<array>

<string>/System/Library/Extensions/AppleGraphicsControl.kext</string>

<string>/System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext</string>

<string>\System\Library\Extensions\IONetworkingFamily.kext</string>

</array>

 

 

I never have understood what this actually does, yet basically every config.plist has the IONetworkingFamily.kext loaded, and it is not necissary for the kext to be loaded to do the KextsToPatch patches.

 

However I have broken my audio completely now. I've tried both wmchris (which I had working before I went on to this whole HDMI output venture) and the syscl AppleHDA, neither work...

 

I've also noticed that my USB Video Card (DisplayLink) is not recognized anymore... I feel like weird stuff are happening since I changed SMBIOS to MBP13,3

 

Even though I got HDMI out to work on MBP13,3 I am considering as well to switch back to iMac17

 

 

Update:

 

So I spent some time in order to fix my audio trying to revert to where I was before. Guess what Deniryer, now my HDMI patch doesn't work anymore! :(

Clearly, they are related.

Further more, when I restored my audio - suddenly my USB Video card was recognized again!

 

 

My best guess is that you're set up like wmchris guide:

 

L/E>

aDummyHDA.kext

CodecCommander.kext

 

S/L/E>

AppleHDA.kext (vanilla)

 

ACPI/patched/ssdt-ALC298

 

 

 

 

Correct? Then let's try to find a fix together as we're at the same startingpoint! :)

  • Like 1
Link to comment
Share on other sites

I have said USB-C hot plug have fallen in 10.12.3

 

It only can be recognized when i plug it first,when i unplug it and replug it again and the system have no response.

 

I have tested this many times and i am sure it was fine in 10.12.2

 

 

从我的 iPhone 发送,使用 Tapatalk

Link to comment
Share on other sites

Hotplug works partly since I remember. I can unplug & plug in my external HDD drive or both monitors and they are recognised just fine as long as I use Macbook 9,1 SMBIOS (Tested under 10.12.2 & 3 & 4 beta 2). However peripherals & smartphones attached to this port are not detected, recognised nor displayed in the system information fro the very beginning of this patch. At least that never worked for me no matter which version of MacOS Sierra I have been using.

Link to comment
Share on other sites

I'm wanting to update to 10.12.3 but have never done an update to a hackintosh using clover. Just to be sure I don't screw it up, I wanted to see how to go about it. I know I have to run the combo update and then potentially boot from my original install usb to get back in. Will copying my current clover folder suffice to get everything working again after the update completes? Sorry if this is a dumb question but I know updates are often system specific when problems can arise.

 

Also as I've never changed board IDs after getting a machine running, will I need to clear my iCloud cache after changing to the 13,3 system definition and changing serial numbers for those services to work again? Thanks

Link to comment
Share on other sites

Hotplug works partly since I remember. I can unplug & plug in my external HDD drive or both monitors and they are recognised just fine as long as I use Macbook 9,1 SMBIOS (Tested under 10.12.2 & 3 & 4 beta 2). However peripherals & smartphones attached to this port are not detected, recognised nor displayed in the system information fro the very beginning of this patch. At least that never worked for me no matter which version of MacOS Sierra I have been using.

I use MacBookPro 13,3

 

 

从我的 iPhone 发送,使用 Tapatalk

Link to comment
Share on other sites

L/E>

aDummyHDA.kext

CodecCommander.kext

 

S/L/E>

AppleHDA.kext (vanilla)

 

ACPI/patched/ssdt-ALC298

 

 

 

 

Correct? Then let's try to find a fix together as we're at the same startingpoint! :)

 

can you guys check if your issues are fixed with syscls prepatched AppleHDA.kext (it's in my repo, too). Then you dont need the ACPI file anymore and aDummy can be deleted, too.

  • Like 1
Link to comment
Share on other sites

can you guys check if your issues are fixed with syscls prepatched AppleHDA.kext (it's in my repo, too). Then you dont need the ACPI file anymore and aDummy can be deleted, too.

Success!!!

 

 

So here are my steps.

 

run the install.sh from the AppleHDA syscls directory.

 

sudo sed -i.vanilla 's/Mac-FC02E91DDD3FA6A4/Mac-A5C67F76ED83108C/g' /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/Info.plist

 

What it does is stealing Board-ID Mac-FC02E91DDD3FA6A4 and replacing it with the MBP13,3 Mac-A5C67F76ED83108C.

                                <key>Mac-A5C67F76ED83108C</key>

                                <string>none</string>
 
Reload caches.
 
Reboot 
 
I have changed the install.sh script and created a pull request.
 
 
 
 
I do have a KextToPatch fix as well (NOT WORKING!)
<dict><key>Comment</key>
<string>Fix HDMI output MBP133 Lockzi</string>
<key>Disabled</key>
<true/>
<key>Find</key>
<string>3e4d61632d464330324539314444443346413641343c2f6b65793e</string>
<key>InfoPlistPatch</key>
<true/>
<key>Name</key>
<string>AppleGraphicsDevicePolicy</string>
<key>Replace</key>
<string>3e4d61632d413543363746373645443833313038433c2f6b65793e</string>
</dict>
0:228  0:000   - [13]: AppleGraphicsDevicePolicy (Fix HDMI output MBP133 Lockzi) :: PlistPatch :: data len: 27
 

It is being applied according to boot log but it does not seem to have the same effect as manually editing the Info.plist

Maybe someone could see what's wrong and help out? :)

  • Like 1
Link to comment
Share on other sites

Does any one with XPS 15 9550 UHD and using OSXAptioFixDrv2.efi to boot successfully?

 

Because v2 have a lot of improvement with v1 so i want to look some way to use v2 instead of v1.

 

As now i know the XPS 13 9350 can use v2 with no "slide=x" and with no error but XPS 15 9550 can't.

 

Now i get the memmap form uefishell command "memmap > mem.txt" and get all the "slide=x" avaliable but a tried this all data but still can't boot into the osx.

Type       Start            End              # Pages          Attributes
RT_Data    0000000000000000-0000000000000FFF 0000000000000001 800000000000000F
Available  0000000000001000-0000000000057FFF 0000000000000057 000000000000000F
Reserved   0000000000058000-0000000000058FFF 0000000000000001 000000000000000F 
Available  0000000000059000-000000000009CFFF 0000000000000044 000000000000000F
Reserved   000000000009D000-000000000009EFFF 0000000000000002 000000000000000F
RT_Data    000000000009F000-000000000009FFFF 0000000000000001 800000000000000F
Available  0000000000100000-000000000421BFFF 000000000000411C 000000000000000F 
BS_Data    000000000421C000-000000000425BFFF 0000000000000040 000000000000000F
Available  000000000425C000-0000000021D53FFF 000000000001DAF8 000000000000000F 32 270
LoaderCode 0000000021D54000-0000000021EEAFFF 0000000000000197 000000000000000F
ACPI_Recl  0000000021EEB000-0000000021F1CFFF 0000000000000032 000000000000000F
BS_Data    0000000021F1D000-0000000023970FFF 0000000000001A54 000000000000000F
ACPI_NVS   0000000023971000-0000000023971FFF 0000000000000001 000000000000000F
RT_Data    0000000023972000-00000000239BBFFF 000000000000004A 800000000000000F
BS_Data    00000000239BC000-0000000023A12FFF 0000000000000057 000000000000000F
RT_Data    0000000023A13000-0000000024203FFF 00000000000007F1 800000000000000F
BS_Data    0000000024204000-000000002420BFFF 0000000000000008 000000000000000F
Available  000000002420C000-000000003128AFFF 000000000000D07F 000000000000000F 288 392
BS_Data    000000003128B000-0000000036A89FFF 00000000000057FF 000000000000000F
Available  0000000036A8A000-0000000036C2FFFF 00000000000001A6 000000000000000F 436 437
BS_Code    0000000036C30000-0000000037298FFF 0000000000000669 000000000000000F
Reserved   0000000037299000-0000000037645FFF 00000000000003AD 000000000000000F
ACPI_Recl  0000000037646000-0000000037667FFF 0000000000000022 000000000000000F
Available  0000000037668000-0000000037CB9FFF 0000000000000652 000000000000000F 442 445
ACPI_NVS   0000000037CBA000-000000003800EFFF 0000000000000355 000000000000000F
RT_Data    000000003800F000-000000003A48BFFF 000000000000247D 800000000000000F
RT_Code    000000003A48C000-000000003A4FEFFF 0000000000000073 800000000000000F
BS_Data    000000003A4FF000-000000003A4FFFFF 0000000000000001 000000000000000F
Available  0000000100000000-00000004BDFFFFFF 00000000003BE000 000000000000000F 2047 9711
Reserved   000000003A500000-000000003A5FFFFF 0000000000000100 0000000000000000
MMIO       00000000E0000000-00000000EFFFFFFF 0000000000010000 8000000000000001
MMIO       00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001
MMIO       00000000FEC00000-00000000FEC00FFF 0000000000000001 8000000000000001
MMIO       00000000FEE00000-00000000FEE00FFF 0000000000000001 8000000000000001
MMIO       00000000FF000000-00000000FFFFFFFF 0000000000001000 8000000000000001
 
  Reserved  :          1,200 Pages (4,915,200 Bytes)
  LoaderCode:            407 Pages (1,667,072 Bytes)
  LoaderData:              0 Pages (0 Bytes)
  BS_Code   :          1,641 Pages (6,721,536 Bytes)
  BS_Data   :         29,427 Pages (120,532,992 Bytes)
  RT_Code   :            115 Pages (471,040 Bytes)
  RT_Data   :         11,450 Pages (46,899,200 Bytes)
  ACPI_Recl :             84 Pages (344,064 Bytes)
  ACPI_NVS  :            854 Pages (3,497,984 Bytes)
  MMIO      :         69,651 Pages (285,290,496 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      4,117,798 Pages (16,866,500,608 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         16,256 MB (17,046,634,496 Bytes)

So i tried 32 270 288 392 436 437 442 445 2047 9711 but still can't boot.

 

@goodwin_c I saw you have said you can boot into the osx with "slide=32" with v2 drive but i can't with many tried and don't now how...

 

Does this memmap error or other problems?

Link to comment
Share on other sites

Does any one with XPS 15 9550 UHD and using OSXAptioFixDrv2.efi to boot successfully?

 

Because v2 have a lot of improvement with v1 so i want to look some way to use v2 instead of v1.

 

As now i know the XPS 13 9350 can use v2 with no "slide=x" and with no error but XPS 15 9550 can't.

 

Now i get the memmap form uefishell command "memmap > mem.txt" and get all the "slide=x" avaliable but a tried this all data but still can't boot into the osx.

Type       Start            End              # Pages          Attributes
RT_Data    0000000000000000-0000000000000FFF 0000000000000001 800000000000000F
Available  0000000000001000-0000000000057FFF 0000000000000057 000000000000000F
Reserved   0000000000058000-0000000000058FFF 0000000000000001 000000000000000F 
Available  0000000000059000-000000000009CFFF 0000000000000044 000000000000000F
Reserved   000000000009D000-000000000009EFFF 0000000000000002 000000000000000F
RT_Data    000000000009F000-000000000009FFFF 0000000000000001 800000000000000F
Available  0000000000100000-000000000421BFFF 000000000000411C 000000000000000F 
BS_Data    000000000421C000-000000000425BFFF 0000000000000040 000000000000000F
Available  000000000425C000-0000000021D53FFF 000000000001DAF8 000000000000000F 32 270
LoaderCode 0000000021D54000-0000000021EEAFFF 0000000000000197 000000000000000F
ACPI_Recl  0000000021EEB000-0000000021F1CFFF 0000000000000032 000000000000000F
BS_Data    0000000021F1D000-0000000023970FFF 0000000000001A54 000000000000000F
ACPI_NVS   0000000023971000-0000000023971FFF 0000000000000001 000000000000000F
RT_Data    0000000023972000-00000000239BBFFF 000000000000004A 800000000000000F
BS_Data    00000000239BC000-0000000023A12FFF 0000000000000057 000000000000000F
RT_Data    0000000023A13000-0000000024203FFF 00000000000007F1 800000000000000F
BS_Data    0000000024204000-000000002420BFFF 0000000000000008 000000000000000F
Available  000000002420C000-000000003128AFFF 000000000000D07F 000000000000000F 288 392
BS_Data    000000003128B000-0000000036A89FFF 00000000000057FF 000000000000000F
Available  0000000036A8A000-0000000036C2FFFF 00000000000001A6 000000000000000F 436 437
BS_Code    0000000036C30000-0000000037298FFF 0000000000000669 000000000000000F
Reserved   0000000037299000-0000000037645FFF 00000000000003AD 000000000000000F
ACPI_Recl  0000000037646000-0000000037667FFF 0000000000000022 000000000000000F
Available  0000000037668000-0000000037CB9FFF 0000000000000652 000000000000000F 442 445
ACPI_NVS   0000000037CBA000-000000003800EFFF 0000000000000355 000000000000000F
RT_Data    000000003800F000-000000003A48BFFF 000000000000247D 800000000000000F
RT_Code    000000003A48C000-000000003A4FEFFF 0000000000000073 800000000000000F
BS_Data    000000003A4FF000-000000003A4FFFFF 0000000000000001 000000000000000F
Available  0000000100000000-00000004BDFFFFFF 00000000003BE000 000000000000000F 2047 9711
Reserved   000000003A500000-000000003A5FFFFF 0000000000000100 0000000000000000
MMIO       00000000E0000000-00000000EFFFFFFF 0000000000010000 8000000000000001
MMIO       00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001
MMIO       00000000FEC00000-00000000FEC00FFF 0000000000000001 8000000000000001
MMIO       00000000FEE00000-00000000FEE00FFF 0000000000000001 8000000000000001
MMIO       00000000FF000000-00000000FFFFFFFF 0000000000001000 8000000000000001
 
  Reserved  :          1,200 Pages (4,915,200 Bytes)
  LoaderCode:            407 Pages (1,667,072 Bytes)
  LoaderData:              0 Pages (0 Bytes)
  BS_Code   :          1,641 Pages (6,721,536 Bytes)
  BS_Data   :         29,427 Pages (120,532,992 Bytes)
  RT_Code   :            115 Pages (471,040 Bytes)
  RT_Data   :         11,450 Pages (46,899,200 Bytes)
  ACPI_Recl :             84 Pages (344,064 Bytes)
  ACPI_NVS  :            854 Pages (3,497,984 Bytes)
  MMIO      :         69,651 Pages (285,290,496 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      4,117,798 Pages (16,866,500,608 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         16,256 MB (17,046,634,496 Bytes)

So i tried 32 270 288 392 436 437 442 445 2047 9711 but still can't boot.

 

@goodwin_c I saw you have said you can boot into the osx with "slide=32" with v2 drive but i can't with many tried and don't now how...

 

Does this memmap error or other problems?

I can boot with OSXAptioFixDrv2.efi without problem with boot args -v -dart=0, 10.12.04 Beta 3 & Macbook 9,1 SMBIOS, Can't change to 13,3 I can't risk my uni work right now and my xps doesn't cooperate with this smbios correctly. Really weird stuff happens when I use 13,3. 

Clover folder attached to the post.

CLOVER.zip

  • Like 1
Link to comment
Share on other sites

I can boot with OSXAptioFixDrv2.efi without problem with boot args -v -dart=0, 10.12.04 Beta 3 & Macbook 9,1 SMBIOS, Can't change to 13,3 I can't risk my uni work right now and my xps doesn't cooperate with this smbios correctly. Really weird stuff happens when I use 13,3. 

Clover folder attached to the post.

 

I compared your driver with mine and i found the osxaptiofixdrv2 not the latest?

 

You can try this latest.

 

OsxAptioFix2Drv-64.efi.zip

Link to comment
Share on other sites

Hi wmchris. 

 

Followed you for a while and decided to install OS X on 9550. Guide was exemplary and its running smoothly. I have only one issue: iMessage. - call apple with the following code. (iTunes and App Store work fine).

 

 

Networks: ethernet en0, wifi en1, can't get rid of ethernet. everytime it comes back as en0, although I've connected via wifi.

Apple Id: 2 different ids, both connect to Mac App Store and iTunes Store fine, iMessage works on iPhone.

Smbios: set up as 13,3, iMessage debug confirms all remains static when rebooting, id is not valid with apple (As per all the guides). smuid and motherboard serial all look fine, although can post them if needed.

 

I am wondering if this current device (serial, smuid, huuid and mlb) are all blacklisted at this stage? I can connect fine with iPhone. 

 

not sure how to get iMessage working, and was really looking forward to this then handoff as my next step (dw1830).

 

thanks for anyone's help. I followed tonymacosx jaymonkey's guide as much as I could and short of calling apple I'm not sure what else to do. I have not used my most used Apple ID, but ones I've had before, and I am nervous to try that one until I'm sure the device might need new credentials etc.

 

Thanks for the replies

Link to comment
Share on other sites

your serial must be whitelisted by apple. you didnt use a real one? Call the number and talk to them and tell them a good story (obviously only works if you own a real mac with applecare)

 

Hi wmchris. 

 

Followed you for a while and decided to install OS X on 9550. Guide was exemplary and its running smoothly. I have only one issue: iMessage. - call apple with the following code. (iTunes and App Store work fine).

 

 

Networks: ethernet en0, wifi en1, can't get rid of ethernet. everytime it comes back as en0, although I've connected via wifi.

Apple Id: 2 different ids, both connect to Mac App Store and iTunes Store fine, iMessage works on iPhone.

Smbios: set up as 13,3, iMessage debug confirms all remains static when rebooting, id is not valid with apple (As per all the guides). smuid and motherboard serial all look fine, although can post them if needed.

 

I am wondering if this current device (serial, smuid, huuid and mlb) are all blacklisted at this stage? I can connect fine with iPhone. 

 

not sure how to get iMessage working, and was really looking forward to this then handoff as my next step (dw1830).

 

thanks for anyone's help. I followed tonymacosx jaymonkey's guide as much as I could and short of calling apple I'm not sure what else to do. I have not used my most used Apple ID, but ones I've had before, and I am nervous to try that one until I'm sure the device might need new credentials etc.

 

Thanks for the replies

Link to comment
Share on other sites

your serial must be whitelisted by apple. you didnt use a real one? Call the number and talk to them and tell them a good story (obviously only works if you own a real mac with applecare)

I have an air i can rely on but its 2013. If i reset all and ceate a new serial, because my id had a hackintosh before wouls that make a difference?

Link to comment
Share on other sites

I have an air i can rely on but its 2013. If i reset all and ceate a new serial, because my id had a hackintosh before wouls that make a difference?

the thing is: either you have a serial for yourself, or you have a serial, which is used before. The last can even happen if you create one with a generator (thats why you should always check if the generated serial is already in use).

 

If you have a brand new serial it's obviously unknown to apple. Sometimes it still works, most of the time it doesnt.

If you have a real serial and you dont own the original apple device this could result in VERY bad outcomes - mostly of data security.

 

I salvage my serial numbers personally. I dont mind using an old SMBIOS, but it reduces compatibility a lil bit.

Link to comment
Share on other sites

×
×
  • Create New...