Contribute
Register
At this point you've been successful enough to logon to both iMsg and F-Time, then you're just one step away to getting things right. Your problem is synchronising those services between all your Apple devices. The easy way forward is to log both your Hack and your iPhone out from iCloud and then back in again. Remember they can be a slight delay for the Apple Servers to register all the devices using your ID account. Good luck.

Hi, thanks. iMessage does sort of work as I now can send messages. The problem is my old messages are not showing up like it does on my real mac's. only 1 or 2 conversations and not complete.
Also FaceTime (and therefore using my iPhone to make real calls) doesn't work. Sign-in works, but not calling a number.

-edit
now iMessage is also broken again :(
 
Last edited:
I have followed the idiot guide to the letter, my values are persistent, series is good and everything but i am getting the 'call apple' thingie.
My AppleID works on my macbook and my iPad, just not on my hackintosh.
Am i screwed?

Newly created Apple ID's on new builds tends to invoke the call 'Apple with a Code' popup message, this is a security measure to White List your rig on the Servers so I am afraid once you get that message, there is nothing you can do apart from putting in that call.
 
Hi, thanks. iMessage does sort of work as I now can send messages. The problem is my old messages are not showing up like it does on my real mac's. only 1 or 2 conversations and not complete.
Also FaceTime (and therefore using my iPhone to make real calls) doesn't work. Sign-in works, but not calling a number.

-edit
now iMessage is also broken again :(

Seems like your injected values are not consistent hence the sporadic behaviour with iMsg and the non working F-Time. You need to at least insure your injected values are correct and constant between every reboots.
 
Newly created Apple ID's on new builds tends to invoke the call 'Apple with a Code' popup message, this is a security measure to White List your rig on the Servers so I am afraid once you get that message, there is nothing you can do apart from putting in that call.

Yeah it is a new AppleID. Does the calling usually work?
 
Yeah it is a new AppleID. Does the calling usually work?

I suppose these days its up to the Apple person you speak with, judging by some of the reported calls they can be quite dismissive at times if you let them take over the dialogue, don't be intimidated. Have a read of the 'How to Fix iMessage Guide' on the section how to conduct the call.
 
I suppose these days its up to the Apple person you speak with, judging by some of the reported calls they can be quite dismissive at times if you let them take over the dialogue, don't be intimidated. Have a read of the 'How to Fix iMessage Guide' on the section how to conduct the call.

Will do, thank you.
 
As advocated over and over, once your rig throws up the message to call Apple Customer Care with a given code there is absolutely nothing you can do to change the situation, going to the length of changing Mac model with new injected values is fruitless. The call is to get your rig 'White Listed' on the servers, Apple's security measures are more stringent here on late and were put into place since the bad days of foolhardy cloning and is not really directly anything to do with Sierra.

Are we so self indulged to think that they cannot distinguish the difference between a genuine Mac and a hack logged onto their servers???!!! - I would like to think otherwise, I personally think it's one of the main reasons you can logon with a genuine Mac without any bother but lately can't with a hack even if all injected values are static and correct. All Macs/PC's has to pass a security check before they are issued with a security 'Token' or 'Certificate' every time they log into Apple Servers, have a look in 'Console' to get an idea whats going on under the hood so to speak. Note 'Server watchdog' and 'Security Checking'.
 
On my build iMessage only works with Systemdefinitions iMac14,1. When i generate an iMac 14,2 iMessage won´t work.
 
After a few hours of testing yesterday imessage is now working on my build.

I used the clover configurator for all settings.

  1. First i checked the network interface name of my Ethernet card and the wirless card. One of booth should be en0 and buildin
  2. Create a new mac with Clover Configurator (shake week and unit number several times)
  3. Create a SmUUID with the command "uuidgen" in terminal
  4. Copy the created UUID from terminal in the SmUUID textfield in clover configurator
  5. On RT Variables i copied the mac adress from my wlan card directly in the ROM textfield (you can find the macadress in systemprofile under Ethernet connections or WLAN)
  6. Create a MLB number with SimpleMLB (https://www.tonymacx86.com/threads/...3-4330-geforce-gt640-10-11-4.189452/#imessage) and copied it to MLB
  7. BooterConfig is 0x28 and CsrActiveConfig is 0x67
  8. Restart your pc and disconnect your account from imessage and connect it again.
 
Last edited:
Hi,
I was trying to fix iMessage and just crashed all system, won't boot up from clover, I'm not even able to boot in safe mode or recovery, any time I want to boot from clover, computer restart and stop in clover menu, over and over again. I have OS Sierra. Is it possible to boot somehow this system or have to reinstall it ?
 
Back
Top