Jump to content

ApexDE

Members
  • Content count

    215
  • Joined

  • Last visited

About ApexDE

  • Rank
    InsanelyMac Geek

Recent Profile Visitors

2,763 profile views
  1. ApexDE

    iMessage won‘t activate with Clover >4428

    You're welcome Happy Messaging. Took me some hours too to check this out. Really tricky to discover. See also this post: default „IOBuiltin“ Injection is disabled by default now with recent Clover Versions. So i guess more Users will be affected when their iMessage Security Token expires. Anyone knows how long the Token lasts?
  2. ApexDE

    iMessage won‘t activate with Clover >4428

    You need to insert it under „Devices“ in config.plist. You can also use CloverConfigurator App if you are unsure.
  3. ApexDE

    iMessage won‘t activate with Clover >4428

    The Network Card has been working perfectly fine since at least 10.11 without any issues and is supported out-of-the-box, best method useable. All other network interfaces are disabled in the BIOS. I installed Clover 4558 and found the problem: Injection as "Ethernet built-in" doesn't work with Clover >4428. Screenshot taken with IORegistryExplorer and Clover 4558. With Clover 4428 it said "IOBuiltin: true". It MUST be "true" to activate iMessage. Final EDIT: It turns out that Clover doesn't inject the Network Card automatically as "built-in" since Clover 4428. You need to add two more lines in config.plist in "Devices" for properly injected internal Ethernet, so IORegistryExplorer shows "True" for IOBuiltin: I'll report back when my iMessage Security Token expires and new iMessage Activation is needed, but i guess it will be working again from now on.
  4. ApexDE

    iMessage won‘t activate with Clover >4428

    Yes, i used the same config.plist for 4428 and newer Clover Versions. I don't have any LAN Injection options enabled in the config.plist. I use a extra PCIe Network Card for better compatibility. It's working out of the box since at least macOS 10.11, onboard LAN is disabled in the BIOS. The screenshot is taken with 4428. Heres my complete config.plist. EDIT: removed
  5. ApexDE

    iMessage won‘t activate with Clover >4428

    i don't have LANInjection or InjectLAN in my config.plist. Maybe it is needed with Clover >4428? This is my Profiler-Ethernet-Report with 4428 and without any LAN Injection active in config.plist:
  6. ApexDE

    iMessage won‘t activate with Clover >4428

    at first, i kept MacModel at iMac 10,1 , updated to 10.13.5 and Clover to 4497 which broke iMessage. I then updated Clover upto 4522 to no avail. As last resort, i changed MacModel to iMac 13,1 with Clover 4522 and 4497, iMessage still didn't activate, always Error 13 in System Log. I then rolled back to 4428 and iMessage activated just fine, just as always before. iMessage_debug always showed good valid values, with all MacModel and Clover variations. Very strange. The SMBIOS Settings always stayed the same with all variations tried. <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>04/09/2018</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>IM131.88Z.0115.B00.1804091830</string> <key>Board-ID</key> <string>Mac-00BE6ED71E35EB86</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardSerialNumber</key> <string>STRIPPED</string> <key>BoardType</key> <integer>10</integer> <key>BoardVersion</key> <string>1.0</string> <key>ChassisAssetTag</key> <string>iMac-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>0x0D</string> <key>Family</key> <string>iMac</string> <key>FirmwareFeatures</key> <string>0xE00DE137</string> <key>FirmwareFeaturesMask</key> <string>0xFF1FFF3F</string> <key>LocationInChassis</key> <string>Part Component</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <false/> <key>PlatformFeature</key> <string>0x01</string> <key>ProductName</key> <string>iMac13,1</string> <key>SerialNumber</key> <string>STRIPPED</string> <key>SmUUID</key> <string>STRIPPED</string> <key>Version</key> <string>1.0</string> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x3</string> <key>MLB</key> <string>STRIPPED</string> <key>ROM</key> <data> STRIPPED </data> </dict> What do you mean with profiler? I read about changes in LAN Injection post-4428. Could this be a source of the issue?
  7. ApexDE

    Clover General discussion

    So, let‘s work this out. I made a own thread for this issue:
  8. I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame. Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428). Any CLOVER Version i tried prevented activating iMessage (iMessage Error in systemlog: 13) I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428 brought back the capability to activate iMessage. iMessage is set up correctly regarding ROM and MLB and never was a issue before. /EFI/CLOVER/DRIVERS64UEFI has: AppleImageCodec-64.efi DataHubDxe-64.efi FirmwareVolume-64.efi PartitionDxe-64.efi AppleKeyAggregator-64.efi EmuVariableUefi-64.efi HFSPlus-64.efi SMCHelper-64.efi AppleUITheme-64.efi FSInject-64.efi OsxAptioFix2Drv-64.efi apfs.efi Any ideas why it fails with CLOVER Versions greater 4428?
  9. Thanks, you made my day. I had the same issue and tried nearly anything and was about to give up. Rolling back to clover 4428 made iMessage work again here too.
  10. ApexDE

    Clover General discussion

    I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame. Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428). Any CLOVER Version i tried prevented activating iMessage (iMessage Error in systemlog: 13) I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428 brought back the capability to activate iMessage. iMessage is set up correctly regarding ROM and MLB and never was a issue before. Any ideas?
  11. Even with "-DisableSleepProxyClient" in the mDNSResponder plist?
  12. Nice to see mDNSResponder coming back Anyone knows if we still need the -DisableSleepProxyClient option to prevent the wake every two hours?
  13. Fine Thanks for testing. So i can update to Yosemite now
  14. So, the 2-hourly wake seems to be fixed since 10.10.2 Can anyone test if Wake-on-Lan is still possible? I need Wake-On-Lan but don't want that 2 hourly wake. If it doesn't work i need to stay at Mavericks. How is the behaviour when "wake for administrative Network access" is activated? We have the 2 hourly wake back again?
×