Contribute
Register
I'm going to try again but for some reason, using rom from macaddress0 results in rom as "FFFFFFFFFFFF".


Not sure what happened.



When people say authorize itunes, what does this mean?
imessage has worked great on this Hack since the start. On every iteration of every osx except this one. I'm on the latest Mojave devoloper beta. iphone to iphone works fine.. mac to sms does not work. Just red numbers. no clue as to why. Sucks
 
imessage has worked great on this Hack since the start. On every iteration of every osx except this one. I'm on the latest Mojave devoloper beta. iphone to iphone works fine.. mac to sms does not work. Just red numbers. no clue as to why. Sucks
Yeah, I am not digging mojave in this regards. I get it. Its a major change compared to sierra but still. Sucks.
 
[SUCCESS]
I just upgraded my system (see signature), updated MacOS from 10.12.5 to 10.12.6 and after some dark days of despair everything finally works.
Just wanted to share the few steps I took that are not mentioned in the thorough guide.
1. I added AptioInputFix-64.efi from Clover/Drivers (in the moment nothing changed so I can't tell whether it helped or not)
2. I created the folder Users/Shared (that wasn't there) and in the terminal I ran the command 'chmod 1777 /Users/Shared' (thanks to YoshiMac!).
At that point it could finally log into iCloud and iMessage works as well!

Some notes:
- The system profile I was trying when it started working was 18,3 (even though 18,2 mounts exactly my CPU)
- To have the ethernet card recognized and set as "built in" I had to use the Intel IE1000e 3.3.6 drivers in MultiBeast instead of the IntelMausl that had been working smoothly in my previous configuration. I was connected to the internet through a silly TP Link external wifi USB stick, not through the ethernet I could finally get to work.
- After several attempts cleaning cache and preferences I just made myself a note to do the operation quickly from the terminal first running 'sudo rm' and putting the password in and then pasting this:
sudo rm -rf ~/Library/Caches/com.apple.iCloudHelper* \
~/Library/Caches/com.apple.Messages* \
~/Library/Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent* \
~/Library/Preferences/com.apple.iChat* \
~/Library/Preferences/com.apple.icloud* \
~/Library/Preferences/com.apple.imagent* \
~/Library/Preferences/com.apple.imessage* \
~/Library/Preferences/com.apple.imservice* \
~/Library/Preferences/com.apple.ids.service* \
~/Library/Preferences/com.apple.madrid.plist* \
~/Library/Preferences/com.apple.imessage.bag.plist* \
~/Library/Preferences/com.apple.identityserviced* \
~/Library/Preferences/com.apple.ids.service* \
~/Library/Preferences/com.apple.security* \
~/Library/Messages

No rocket science but it did save me plenty of time!
Hope it helps and maybe one day I'll dare to update to High Sierra or Mojave or whatever will be there. But it is not this day.
Good luck!
 
Hey guys,

I'm at my wits end with iMessage. I've tried everything from every guide on here, and I still get the contact Apple code when I try to get things going again. I even tried a fresh install. I found a helpful guy at Apple who got me unlocked, but it keeps on locking back up.

I've read through a *lot* of the posts and have tried a LOT of different things.

- Checked my SN on EveryMac & Apple's site (all is well)
- Ethernet is en0
- Deleted everything from the above post & rebooted
- Essentially followed the "Idiots' guide to the letter

Still no joy.

What kind of info can I provide to get a little help?

Thx


Wiley
 
Hey guys,

I'm at my wits end with iMessage. I've tried everything from every guide on here, and I still get the contact Apple code when I try to get things going again. I even tried a fresh install. I found a helpful guy at Apple who got me unlocked, but it keeps on locking back up.

I've read through a *lot* of the posts and have tried a LOT of different things.

- Checked my SN on EveryMac & Apple's site (all is well)
- Ethernet is en0
- Deleted everything from the above post & rebooted
- Essentially followed the "Idiots' guide to the letter

Still no joy.

What kind of info can I provide to get a little help?

Thx


Wiley

I've found iMessages and its activation is very hardware-dependant, that's why more often than not activation is not carried out. I have an old mobo + chipset, I've tried every guide, every smbios with those guides and now I'm probably flagged after dozens of attempts. No joy for me either. I've ordered a fenvi t919 wifi card and I'll try one more time with a fresh high sierra or mojave. If I don't achieve it I'll give up, I cannot buy all the required hardware from buyer's guide for iMessages/FT to work at this moment. If I were to do that I would rather buy a real mac, which I'm considering since iServices are essential to me.
 
Hi guys. For a very long time I tried to get imessages on the new system. And finally, after a clean install, everything worked the first time (ROM and MLB from real mac). Created a new account Apple ID. Immediately after logging, I sent a test message with a new account to the old account. Everything went perfectly. But a minute later I was thrown out and iMessage not working! What do you think happened?
Called apple support service . My account was blocked. The call solved my problem and it all worked!
 
Last edited:
Yes I have tried all of that. I've tried clearing caches and gone into Apple website to unlink the devices and relink. Still the same issue. My MacBook is working great with the service. Just appears that the Customac is having issues. To further update the problem, it does not appear to stay in sync. After several days of not logging into the Customac, messages do not sync.


I am having exactly this issue. iMessages was working fine in a new build of 10.14.0 for several weeks. Then I upgraded to 10.14.2 (the only prep I did was to upgrade to the newest stable build of Clover), and after the 10.14.2 install, I can send iMessages to a few people some of the time, but most of the time I can only send SMS to people who I know are on iMessage. And no ones iMessages get sent to my Hackintosh, ever. If I click on a contact's name (which is red) in Messages, their phone numbers are listed twice--once as iMessage, once as not registered with iMessage--but both are grayed out.

I've tried everything in this guide, including confirming built-in status of en0, logging out of everything and back in, deleting devices from iCloud.com, deleting caches and preferences--nothing works. I am having no error messages when logging in to iMessage, iCloud, or App Store.

I believe something fundamentally changed in the way iMessage syncing works in 10.14.2.
 
the only prep I did was to upgrade to the newest stable build of Clover
Probably the source of your problem.
iMessage depends on native NVRAM or an emulation of it.
If you need to emulate it use EmuVariableUEFI-64.efi and RC scripts,
or AptioMemoryFix-64.efi without EmuVariableUEFI-64.efi.

I believe something fundamentally changed in the way iMessage syncing works in 10.14.2.
Unlikely.
 
Probably the source of your problem.
iMessage depends on native NVRAM or an emulation of it.
If you need to emulate it use EmuVariableUEFI-64.efi and RC scripts,
or AptioMemoryFix-64.efi without EmuVariableUEFI-64.efi.


Unlikely.

Thanks for the quick reply, P1LGRIM. I read your guide in its entirety and this section in Chapter 6 made me think I didn't have to worry about this issue if I'd always been using Clover, which I was when I had stable iMessage function in 10.14.0:

"Clover Users:

If your booting OS X via Clover then you don't have to do anything, Clover includes a comprehensive emulation of OS X's NVRAM features and generates a NVRAM cache file at boot time, since OS X reads NVRAM values from the cache rather than the slow Non-Volatile RAM hardware it negates most of the problems associated NVRAM on non-Apple hardware."

Has the way Clover treats NVRAM changed recently? I don't have either of those other efi approaches in place.

Thanks!
 
Thanks for the quick reply, P1LGRIM. I read your guide in its entirety and this section in Chapter 6 made me think I didn't have to worry about this issue if I'd always been using Clover, which I was when I had stable iMessage function in 10.14.0:
My guide has no Chapter 6, in fact it has no chapters at all.
 
Back
Top