Jump to content
97 posts in this topic

Recommended Posts

@arsradu

I have a message issue for 1 monts, trying all the trick without success, calling Apple even Apple can not fix the problem, only my iphonne can be use.

then it fix by imself magically when I receive a pop up on my Iphone this mac can use message.

  • Like 1
On 3/21/2026 at 4:54 PM, chris1111 said:

@arsradu

I have a message issue for 1 monts, trying all the trick without success, calling Apple even Apple can not fix the problem, only my iphonne can be use.

then it fix by imself magically when I receive a pop up on my Iphone this mac can use message.

 

This is so weird... :))

Were you logged into iCloud already when that happened? Were you on Tahoe or something older?

 

If I'm trying to sign into Facetime and make a call (before exiting, which forces me to sign in again) it says this:
image.png.f9b9895c12b03626f79cb53f77f4d424.png

 

Obviously BOTH the iPhone and the Mac are in fact already using the same account. So this is another error that makes no sense to me.

 

 

Update: I went back to Ventura, tried to log in, same exact issue. At this point it doesn't look like a problem with the OS, but something on the account or something...

Update 2: changing the password didn't make a difference to me. Neither for FaceTime, nor iMessage.

Edited by arsradu
  • Sad 1

Looks like there are quite a lot more people with the same issue. And it’s not OS related. It’s device related. 
I found this thread on reddit: 

so…yeah, I think in preparation for intel removal, only legit Macs are allowed to log into imessage and Facetime. I even tried on another hack which was working fine a while ago, and got the exact same behaviour. Automatically closing, and asking to login again. Facetime actually stays on. But if you close it and open it again, it asks to login again. So clearly it’s not actually working. 
Well, if someone can find a fix so I can retire my hack fully working, that would be really nice. If not, well it’s been super cool and super fun and I’ve learned a lot of new and interesting things..while it lasted. I’m still grateful for everything. :)

Edited by arsradu

Hey guys,

 

Just wondering, is the order of the network interfaces here important? Looks like it's sometimes en0 on top, en1 on the bottom, but mine seems to be en1 on top, en0 on the bottom. 

 

If that makes a difference, how do I set them to be the other way around?

image.thumb.png.610506e5225591b5fde7f3cb3f41bb8f.pngimage.thumb.png.ccc8c542980a659ccc9ba6195ccbb677.png

Edited by arsradu

If I recall well, the Dortania OpenCore specifically addresses this question clarifying that en0 should be the network present to have iMessage up and running. I read somewhere else that sometimes the en0 versus en1 assignment to each network can create issues too, and I recall fixing some of that in the past when I had issues with iMessage many years ago. en0 has to be also marked at built-in.

Edited by jlrycm
  • Like 1
9 hours ago, jlrycm said:

Hello! Thank you very much for this! :)

I went though it, and… while the guide provides useful information, it does not say anything about the order of those interfaces in Hackintool. Moreover, as far as I can see, the guide itself lists en1 as first option. So…I’m guessing the order is probably not that important. But we need to have en0 and set as built-in. Which mine is anyway. 
Ok.. then it might be something else. 

  • Like 1

Apple contact help primarly if iPhone had this problem and solve very fast. When problem is with Macs or Hackintoshes with  Facetime and iMesaga open and forwarding, rarely are able to solve. I try many times.

 

Deleting account and forming new one is most effective and fastest for this symptom.....if you have not paid apps on iOs.  This is account problem, not problem with Tahoe or any other OSX...maybe on their server side. One cynic said, Apple can be so proud how many MacPro7,1  are logged 😂

Edited by notobo
  • Haha 2

Yeah, well, looks like this new support link is precisely for Mac. It is definitely server-side. And....I'm not sure how much it's account related. I tried it with an old account, worked only once, after which it got to the exact same symptoms as the current one. Interesting fact is that even real Macs are encountering the same issue. And what Apple reps seem to see on their side is some sort of "spam report" caused by the phone number. Basically the phone number being reported as spam. I've seen this way too many times online trying to figure out what's going on to be just a coincidence. Also, pretty sure nobody's phone was actually reported by anyone as spam.

I'm not sure if changing the phone number also fixes this issue... It would be interesting to try, if someone has the opportunity and the means to do so. But weird issue nonetheless. At this point, I don't even think this is a serials issue. I think it's just a bug on Apple's side, and the only way to solve it is (probably) either changing the phone number, or...trying the link above.

Edited by arsradu
  • Like 2

Yes...that was my thought at first. But when you delete actual phone No. from account and put other and close account and after that open new acc. with same No. like in first and everything works...that apple story drink no more water. 

 

Maybe is with some phone providers and Apple together, who knows. I analyzed what I have done with testing and changing SMBIOS-es when I was logged (very clever of me 😀) that was probably thing which put question mark at my account on Apple servers. 

Edited by notobo
  • Like 1
  • 2 weeks later...

After testing and testing and testing, I think the conclusion is pretty straightforward: Apple has increased their checks to only allow real/valid devices. Whether that's because they're gonna drop suport for Intel or something else, I don't know. I'm still not sure what changed. But...looks like something did. Cause older configs which used to work, don't work anymore, new configs don't work anymore. Sadly I don't have another Intel Mac to test on.

But the results to my tests are pointing in that direction.

  • New serials don't make a difference.
  • New/old (never used for iMessage) Apple IDs don't make a difference (at least they didn't in my case).
  • New/old OSes didn't make a difference.
  • Fresh installs vs current/older installation didn't make a difference.
  • Logging into iCloud vs not being logged in also didn't make a difference.

Everything works perfectly fine on real Apple hardware, and this only affects Facetime and iMessage. iCloud works perfectly fine.

So...if you can still use iMessage/Facetime, you're probably one of the few lucky ones. :))

 

So.... yeah. :) That's about it. It was super cool while it lasted. And again, I'm super grateful to everyone who contributed to this community and to where we are now.

  • Like 1

@arsradu

 

Strange. I have iMessage and Facetime working in Sonoma and Tahoe. Serials are here since long time ago. Serial number outputs not valid in the check coverage Apple site. Maybe Apple has changed something but, for now, I haven't seen any difference.

6 minutes ago, miliuco said:

@arsradu

 

Strange. I have iMessage and Facetime working in Sonoma and Tahoe. Serials are here since long time ago. Serial number outputs not valid in the check coverage Apple site. Maybe Apple has changed something but, for now, I haven't seen any difference.

Lucky you! :) I couldn't get it to work, regardless of serials, OS, Apple ID... Nothing worked. Pretty sure, even with all valid serials, it would still not work. :)) But again, since I don't have another Intel Mac...I can't confirm that. And on the M1 MacBook Pro that I own, there are no issues. 

So, I'm still confused how is it that some of you guys have no issues whatsoever. And what exactly caused this whole issue. Could be just random, could be something else. But at this point, I think I've tried pretty much everything I could think of. :))) 

  • Confused 1

Hi, I had the same problems not being able to use the services. All the tests done with serials, new Apple IDs, restoration of old firmware that previously worked with iMessage and FaceTime, tutorials etc. etc. They didn't work. I thought Apple ID with original Mac works, in the previous hack configurations worked (high sierra, Monterrey, Ventura, Sonoma and also Sequoia...) with Tahoe never succeeded until I realised that in the EFI folder the Apple subfolder was missing and Nvram you could only see OC and Boot. I tried to put these folders from old EFIs where the services worked in the EFIs of Tahoe and ...... Magic .... iMessage and FaceTime work, I had already reported it in the forum at the top part. you just have to try

Sorry but the translation doesn't work for me, you do it

Edited by vrondena
non è stato tradotto ha tenuto il testo con lingua originale
  • Like 3
3 hours ago, vrondena said:

Hi, I had the same problems not being able to use the services. All the tests done with serials, new Apple IDs, restoration of old firmware that previously worked with iMessage and FaceTime, tutorials etc. etc. They didn't work. I thought Apple ID with original Mac works, in the previous hack configurations worked (high sierra, Monterrey, Ventura, Sonoma and also Sequoia...) with Tahoe never succeeded until I realised that in the EFI folder the Apple subfolder was missing and Nvram you could only see OC and Boot. I tried to put these folders from old EFIs where the services worked in the EFIs of Tahoe and ...... Magic .... iMessage and FaceTime work, I had already reported it in the forum at the top part. you just have to try

Sorry but the translation doesn't work for me, you do it

I have such folder. It contains 2 subfolders. A FIRMWARE one and an UPDATERS one.

 

Something like this. Is it the same for you? I thought that folder is meaningless for hacks and only useful for real Macs. Now I'm confused...

 

Also, I'm wondering if your ROM is comprised of your actual MAC address (Ethernet maybe?) or something else?

 

And if it gets malformed when it gets to nvram. For example, if you check it with"nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM" do you get back something that looks like what you entered as your ROM? Cause it looks weird in my case. Aside from the % separator I get something like this: %8c-%aaA%e9%b5. Which doesn't look right to me... So if all of my ROM attempts are getting malformed like this, no wonder it doesn't work. I don't even know where would this come from. It slightly resembles what I added but I don't think it is supposed to be like this.

 

Is there another way to check that what I entered is actually interpreted ok in NVRAM?

 

Also, I'm using SSDT-PMC.aml for my Z390 Aorus Pro motherboard. Is it still needed....? Can it affect this functionality in some way?

 

image.png.42ae3bef21f6ff8adb810e1d86edf8d0.png

Edited by arsradu

@arsradu

 

I always supposed that the APPLE folder in EFI does nothing in a Hackintosh. This APPLE folder is created every time you install or update macOS. It does nothing if the hardware is not a real Mac. In fact, I delete them from time to time (when I look at the EFI). 

  • Like 1
8 minutes ago, miliuco said:

@arsradu

 

I always supposed that the APPLE folder in EFI does nothing in a Hackintosh. This APPLE folder is created every time you install or update macOS. It does nothing if the hardware is not a real Mac. In fact, I delete them from time to time (when I look at the EFI). 

Me too. Now I’m confused… :))

What about rom? What do you use? And does it look ok in nvram?

6 hours ago, miliuco said:

@arsradu

 

Strange. I have iMessage and Facetime working in Sonoma and Tahoe. Serials are here since long time ago. Serial number outputs not valid in the check coverage Apple site. Maybe Apple has changed something but, for now, I haven't seen any difference.

We all forget that Mykola now works for Apple. Maybe he knows 😅

7 hours ago, arsradu said:

After testing and testing and testing, I think the conclusion is pretty straightforward: Apple has increased their checks to only allow real/valid devices. Whether that's because they're gonna drop suport for Intel or something else, I don't know. I'm still not sure what changed. But...looks like something did. Cause older configs which used to work, don't work anymore, new configs don't work anymore. Sadly I don't have another Intel Mac to test on.

But the results to my tests are pointing in that direction.

  • New serials don't make a difference.
  • New/old (never used for iMessage) Apple IDs don't make a difference (at least they didn't in my case).
  • New/old OSes didn't make a difference.
  • Fresh installs vs current/older installation didn't make a difference.
  • Logging into iCloud vs not being logged in also didn't make a difference.

Everything works perfectly fine on real Apple hardware, and this only affects Facetime and iMessage. iCloud works perfectly fine.

So...if you can still use iMessage/Facetime, you're probably one of the few lucky ones. :))

 

So.... yeah. :) That's about it. It was super cool while it lasted. And again, I'm super grateful to everyone who contributed to this community and to where we are now.

Change the phone No. just to be sure.  

 

After experience which I explained ih posts before, i am not changing anything anymore regarding SMBIOS. Couple a week ago I installed Sequoia in new APFS Container, have regularly Ventura. It was ok, I don't log  in anyway on my Apple ID, check system just to be sure is it ok and go back to Ventura. Ventura inform me that I must logged again in Apple ID where I was logged anyway because I don't logout. You know, confirm with passw etc. Check on iPhone, everything was ok and on iMessage fwd menu I saw another iMac 😅... Apple knows either you login in or not,  that you have another OS. Never experience that before. Too make long story short, I logged out from Ventura, go to Sequoia and login with the same ID. Everything was/is working. 

Edited by notobo
  • Like 2
8 hours ago, notobo said:

Change the phone No. just to be sure.  

Did that too. :)) Also, one of the apple ids i tried had another phone nr asociated with it. No difference whatsoever. :)) i don’t know what it is. Maybe nvram. Maybe keychain. I don’t know. But it doesn’t seem to work anymore. 

  • Confused 1
  • Sad 1
8 minutes ago, miliuco said:

What do you mean by rom? I’m on MacPro7,1. 
What is your wifi?

ROM...as in you MAC address or whatever you're using as the "ROM" value in your config. :) 

 

For WiFi question, you mean what do I use for WiFi? I have an adapter and using an Apple WiFi card (BCM943602CDP). 

  • Like 1
×
×
  • Create New...