Contribute
Register
Joined
Apr 22, 2011
Messages
369
Motherboard
GA-Z68MX-UD2H-B3 (U1E)
CPU
i5-2500 3.3GHz
Graphics
XFX Radeon HD 6870
Mac
Classic Mac
Mobile Phone
  1. iOS
Little status update- don't give up on Legacy bootloaders yet- they do have their advantages. ;)

I know a few people currently looking at Meklort's FileNVRAM code to see if a fix can be compiled for Yosemite. It's only a few days since the OS was launched- I'm sure that can be done- just will take a bit of time and research. Watch this space.

Source of FileNVRAM
https://public.xzenue.com/websvn/listing.php?repname=FileNVRAM

I don't know enough about this stuff to be able to do anything, but thanks @tonymacx86 for the persistence. I am eagerly waiting for a Chameleon/Chimera fix for iMessage!
 
Joined
Mar 17, 2010
Messages
119
Motherboard
ASUS sabertooth z97 mark 2
CPU
i7 4790k
Graphics
HD 4600
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Thanks for this guide and introduction to Clover. I updated to Yosemite, my MB GA-p55m-ud2., with patches DSDT. On Mavericks I was using chimera, had valid ROM and MLB values, iMessage working fine. After update I injected the same values with clover but can not log in. I noticed that the hardware UUID, has changed. Is there any way to inject this value with clover, or is there a better work around? Thanks.
 
Joined
May 6, 2010
Messages
194
Motherboard
Z68-XP-UD3
CPU
i7-2600K
Graphics
GTX 660 Ti
Mac
  1. MacBook Air
  2. Mac Pro
Thanks for this guide and introduction to Clover. I updated to Yosemite, my MB GA-p55m-ud2., with patches DSDT. On Mavericks I was using chimera, had valid ROM and MLB values, iMessage working fine. After update I injected the same values with clover but can not log in. I noticed that the hardware UUID, has changed. Is there any way to inject this value with clover, or is there a better work around? Thanks.



Yup, same reoccurring issue for people. I could 't use the compiled SmUUID that Clover gave me. Every reboot was a different number. So what I did is left SmUUID blank on my config.plist/configurator. This consistently gave me the same UUID every time however unknown if this would be flagged.

If you are trying to patch in your previous UUID then I don't know if it can be done (seeing as it keeps changing it).
 
Joined
Mar 17, 2010
Messages
119
Motherboard
ASUS sabertooth z97 mark 2
CPU
i7 4790k
Graphics
HD 4600
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hopefully someone can help me out....

I have everything up and running and followed this guide and Tony macs to get my ga-77n-wifi onto Yosemite using Clover. I followed all the directions but my UUID and the Rom are changing after every boot. Every other # is staying the same. Usually it's Rom/MLB that change but UUID & Rom are changing after every reboot and MLB stays.


UPDATE: I used my MAC address and that fixed the ROM. I was still getting a changing / non matching UUID. I removed the SmUUID from configurator that clover generated and rebooted. the System now has matching ROM / MLB / UUID every time I turn on or reboot. The only issue is that SmUUID in configurator (aka config.plist) I left blank. The system still pulls the same UUID everytime and verified it with Imessage-Debug. Will this get flagged? And if so, is there a way to fix this. :)

Has anyone come across this? Any help is greatly appreciated :)
Seems ok. When I had the same hardware UUID , ROM and MLB, gave it a tried and worked perfectly. I'm having some trouble in another system with changing hardware UUID. Please let me know how it went with yours.
 

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,984
Motherboard
GB Z490 Vision G
CPU
i9 10850K OC @ 5.2 GHz
Graphics
Vega 64 LC + HD 630
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Mobile Phone
  1. iOS
To all having issues with iMessage after Migrating to Clover ...

As stated multiple times in the guide, you should use all your existing ID's from your Mavericks (assuming iMessage was working OK)

This includes all of the following :-

SMUUID (SystemId)
OSX S/N
MLB
ROM

You can get these from your old build using iMessage Debug and IOJones

Failure to do this will result in a new device being logged with Apple and you will not be able to access iMessage, please make sure that you put the SystemID UUID in the SMUUID field on the SMBIOS page, do not put it in the Custom UUID filed on the System Parameters field but do ensue that 'Inject System ID' is checked.

Before trying iMessage run iMessage Debug and ensure that all your ID's match your previous Mavericks build including the Hardware (platform) UUID, if all ok try iMessage and it should work. If ANY ID's are not the same or are changing on each boot then resolve the issues before trying iMessage or Contact Apple to Unlock AppleID/Device.

I've been using Clover Version r2953 and have had no issues updating to Yosemite on five machines so far and iMessage is working on them all using each machines existing ID's.

As previously suggested if your new to Clover I recommend that you install Clover first on your existing Mavericks build and ensure that iMessage is working before installing OSX 10.10.

Cheers
Jay
 
Joined
Mar 19, 2014
Messages
32
Motherboard
ASRock b75 pro3
CPU
intel e1230v2
Graphics
gtx 670
Mac
  1. Mac mini
i follow this thread to set the SMBios.
first time.
my iMessage was locked by Apple, i have to call apple support to unlock it. the serial number actually was generated by clover, however, the apple unlocked my iMessage :) i can login my account, BUT i Can Not Send / Receive iMessage. i checked the system.log, there is some error returned like " this application is not permitted to access iCloud".

second time.
i have a real macbook air (2011 model), i cloned its SMid, serial number everything i can to my hackintosh. unfortunately, my iMessage was locked again.... BUT the iMessage on my MBA (real mac) still works fine... i log in / out , send / receive , no any problem at all...it's weird and interesting.

anyway, i have to call apple support in tomorrow to unlock iMessage account, but honestly, i do not know what should i say....
 
Joined
Feb 10, 2011
Messages
36
Motherboard
Hackintosh
CPU
(Lynnfield) Intel Core i7
Graphics
EVGA GTX 660Ti
Mac
  1. Mac Pro
Classic Mac
Mobile Phone
  1. iOS
I agree too much work
 
Joined
Sep 23, 2011
Messages
79
Motherboard
I didn't read
CPU
the RULES
Graphics
so ignore me
Mac
  1. MacBook Pro
  2. Mac Pro
Mobile Phone
  1. iOS
To all having issues with iMessage after Migrating to Clover ...

As stated multiple times in the guide, you should use all your existing ID's from your Mavericks (assuming iMessage was working OK)

This includes all of the following :-

SMUUID (SystemId)
OSX S/N
MLB
ROM

You can get these from your old build using iMessage Debug and IOJones

Failure to do this will result in a new device being logged with Apple and you will not be able to access iMessage, please make sure that you put the SystemID UUID in the SMUUID field on the SMBIOS page, do not put it in the Custom UUID filed on the System Parameters field but do ensue that 'Inject System ID' is checked.

Before trying iMessage run iMessage Debug and ensure that all your ID's match your previous Mavericks build including the Hardware (platform) UUID, if all ok try iMessage and it should work. If ANY ID's are not the same or are changing on each boot then resolve the issues before trying iMessage or Contact Apple to Unlock AppleID/Device.

I've been using Clover Version r2953 and have had no issues updating to Yosemite on five machines so far and iMessage is working on them all using each machines existing ID's.

As previously suggested if your new to Clover I recommend that you install Clover first on your existing Mavericks build and ensure that iMessage is working before installing OSX 10.10.

Cheers
Jay


Could you make a youtube guide on how to fix it?:)
 
Joined
Jul 16, 2014
Messages
18
Motherboard
GIGABYTE GA-Z87X-UD4H LGA 1150 Intel Z87
CPU
Intel Core i7-4790 Haswell 3.6GHz
Graphics
ASUS GTX760-DC2OC-2GD5 G-SYNC Support GeForce GTX 760 2GB
Mac
Classic Mac
Mobile Phone
To all having issues with iMessage after Migrating to Clover ...

As stated multiple times in the guide, you should use all your existing ID's from your Mavericks (assuming iMessage was working OK)

This includes all of the following :-

SMUUID (SystemId)
OSX S/N
MLB
ROM

You can get these from your old build using iMessage Debug and IOJones

Failure to do this will result in a new device being logged with Apple and you will not be able to access iMessage, please make sure that you put the SystemID UUID in the SMUUID field on the SMBIOS page, do not put it in the Custom UUID filed on the System Parameters field but do ensue that 'Inject System ID' is checked.

Before trying iMessage run iMessage Debug and ensure that all your ID's match your previous Mavericks build including the Hardware (platform) UUID, if all ok try iMessage and it should work. If ANY ID's are not the same or are changing on each boot then resolve the issues before trying iMessage or Contact Apple to Unlock AppleID/Device.

I've been using Clover Version r2953 and have had no issues updating to Yosemite on five machines so far and iMessage is working on them all using each machines existing ID's.

As previously suggested if your new to Clover I recommend that you install Clover first on your existing Mavericks build and ensure that iMessage is working before installing OSX 10.10.

Cheers
Jay

Jay,

Any suggestions for people who didn't have iMessages working in Mavericks either (after the august issues)? I am able to log in and send and receive SMS but not iMessages. Before reinstalling Yosemite, I as well was getting the ******** is not registered with iMessages error.

Thanks,

CJ.
 
Joined
Jun 5, 2012
Messages
5
Jay,

Any suggestions for people who didn't have iMessages working in Mavericks either (after the august issues)? I am able to log in and send and receive SMS but not iMessages. Before reinstalling Yosemite, I as well was getting the ******** is not registered with iMessages error.

Thanks,

CJ.

I'm getting this problem too. I had Apple unlock my account so I could register with iMessage which I can but now can only send SMS messages through SMS relay and couldn't send iMessages (before I set up SMS relay and after). I've tried a restart but to no avail.
 
Top