Contribute
Register
@pkdesign,

Installing the Boot-loader and /Extra on to the EFI Partition is not recommended if using FileNVRAM because FileNVRAM needs constant access to its plist in /Extra. It is possible to make it work but you have to ensure that the EFI partition is mounted at all times.

See Part-1, Step-5c - Note 2 for more info on this.

Cheers
Jay

Hmm, so a similar problem with having /Extra on a USB thumbdrive will happen if I put the whole shebang on the EFI partition. I guess I am stuck with an additional /Extra folder on the root of the boot drive as well :(
 
Last edited:
Hi.
Thanks Jay for your guide . I called Apple Support then they unblock ID in 3 minutes.. Now iMessage is back on my Hackintosh. But first i was need valid serial number as Kris404 explained. see post http://www.tonymacx86.com/general-help/110471-how-fix-imessage-127.html#post868047

Wouldn't created a "valid" serial number using Chameleon Wizrad based on https://selfsolve.apple.com/ just mean that you are using someones else's serial number? Would that not cause a cloned hardware issue?
 
Okay, after some more testing I realized that I had to create the /Extra folder on the root drive to create the nvram.xx.plist file. But I moved it to the /Extra folder on my USB thumbdrive and deleted the one I created on the root drive and after several reboot the MLB and ROM have remained constant. Yeah! I don't need the additional /Extra folder!

Now I need to pin down whether I need a real Mac Pro serial number or am I fine with the Chameleon created one? I have several real serials from various sites but am afraid to use them.
 
Okay, after some more testing I realized that I had to create the /Extra folder on the root drive to create the nvram.xx.plist file. But I moved it to the /Extra folder on my USB thumbdrive and deleted the one I created on the root drive and after several reboot the MLB and ROM have remained constant. Yeah! I don't need the additional /Extra folder!

Now I need to pin down whether I need a real Mac Pro serial number or am I fine with the Chameleon created one? I have several real serials from various sites but am afraid to use them.

@pkdesign,

Don't use those leached values, there really is no need, only use them if you absolutely have to when talking to Apple but don't use them in your SMBIOS. Use Chameleon Wizard as stated in the guide to set your System Type correctly and click on the random buttons a few times - see part 1, Step 3.

As stated by RehabMan below, if you end up with a S/N that matches someone's else's system it can only lead to security and identity issues, something Apple are quick to stomp on light of the recent iCloud hacks. Better to have an 'un-identified' system than one that belongs to some-one else.....

Cheers
Jay
 
Wouldn't created a "valid" serial number using Chameleon Wizrad based on https://selfsolve.apple.com/ just mean that you are using someones else's serial number? Would that not cause a cloned hardware issue?
No didn't use any of users serial.. Extactly i created a serial with Chameleon Wizard as i explain. Bu i can say ,this is not giving serial with first time.i had to try many time for create a valid serial. But eventually i did.
 
No didn't use any of users serial.. Extactly i created a serial with Chameleon Wizard as i explain. Bu i can say ,this is not giving serial with first time.i had to try many time for create a valid serial. But eventually i did.

If you randomly generate a serial# that eventually is confirmed as being valid by Apple's server, you are by definition, using "someone elses serial#" given the fact that you do not own the actual Mac that has that serial#. Someone else owns (or will own) that machine.

I use purposely invalid serial#s. For example, by using G8 prefix (indicating US manufacture), because there are no Apple MacBookPro/iMac/MacBookAir/MacMini made in the states.
 
If you randomly generate a serial# that eventually is confirmed as being valid by Apple's server, you are by definition, using "someone elses serial#" given the fact that you do not own the actual Mac that has that serial#. Someone else owns (or will own) that machine.

I use purposely invalid serial#s. For example, by using G8 prefix (indicating US manufacture), because there are no Apple MacBookPro/iMac/MacBookAir/MacMini made in the states.

You right. After unblock ID, i deleted this product serial from my account just in case
 
hello to all,

i have not got an ethernet card in my notebook that works, how do i get the device to show up under ethernet.
i only have wifi perfekt working.

and now it is so that every boot i get different iMessage_debug output like this.
2014-09-11 22:19:43.712 imessage_debug[305:507] Gq3489ugfi: <a0afe2f5 c2463593 4480422b fb600e85 36>
2014-09-11 22:19:43.731 imessage_debug[305:507] Fyp98tpgj: <f2df5787 5187f376 3796dd11 6ae2333e cf>
2014-09-11 22:19:43.733 imessage_debug[305:507] kbjfrfpoJU: <1cff9842 ce571323 8b90a87b 79a91502 84>
2014-09-11 22:19:43.734 imessage_debug[305:507] IOPlatformSerialNumber: W80316QCAGU
2014-09-11 22:19:43.735 imessage_debug[305:507] IOPlatformUUID: CD73108A-8410-5CA9-95DD-D206B27E0603
2014-09-11 22:19:43.736 imessage_debug[305:507] board-id: Mac-F22589C8
2014-09-11 22:19:43.737 imessage_debug[305:507] product-name: MacBookPro6,1
2014-09-11 22:19:43.738 imessage_debug[305:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <2989fb39 46fd>
2014-09-11 22:19:43.739 imessage_debug[305:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: W80316QCAGUNI84B
2014-09-11 22:19:43.741 imessage_debug[305:507] oycqAZloTNDm: <450c5168 d60a12cd 8d2ba201 94185c2c 26>
2014-09-11 22:19:43.742 imessage_debug[305:507] abKPld1EcMni: <0178f1e0 892dffe9 95e7eef1 fb0221a1 90>

can somebody please help in getting iCloud,App Store and iMessage to work?

if there is someone that speaks german than that will be very good.
 
Gud Day, Sir jaymonkey

i just wanna ask you if USB Lan card works for iCloud,Appstore,iMessage and Facetime? i have a working Hackintosh Mavericks 10.9.3 when suddenly my Ethernet built-in stop working, what i did is I bought a USB Lan Card came with a driver for mac. i think the brand is ASIX then reformat my drive and did a clean installation, installed the kext for the USB Lan Card and it was detected

USB Ethernet:

Type: Ethernet
Hardware: Ethernet
BSD Device Name: en0
IPv4 Addresses: 192.168.254.2

followed all ur instructions but to no avail... when i log in to iCloud it sez Unable to sign in because of problem communication with iCloud, iMessage error is Could not sign in to iMessage an error occured during activation. Try again....Appstore error is Your device computer could not be verified. contact support for assistance...

here's my iMessage debug :

2014-09-12 08:17:03.776 imessage_debug[930:507] Gq3489ugfi: <ee0e9dfb 0bfbeb33 9f68ee53 4d1c2cc5 95>
2014-09-12 08:17:03.778 imessage_debug[930:507] Fyp98tpgj: <eca9e151 dd066b35 b964b4ad b5b46ad8 72>
2014-09-12 08:17:03.778 imessage_debug[930:507] kbjfrfpoJU: <e9476be2 7d2c2070 decddafd 545f3b15 c1>
2014-09-12 08:17:03.778 imessage_debug[930:507] IOPlatformSerialNumber: C02K6150DTY3
2014-09-12 08:17:03.779 imessage_debug[930:507] IOPlatformUUID: 8497EB1C-608B-5D29-8E33-DA6A533B4589
2014-09-12 08:17:03.779 imessage_debug[930:507] board-id: Mac-6F01561E16C75D06
2014-09-12 08:17:03.779 imessage_debug[930:507] product-name: MacBookPro9,2
2014-09-12 08:17:03.779 imessage_debug[930:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <00000000 09a4>
2014-09-12 08:17:03.780 imessage_debug[930:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02K6150DTY3M1J7
2014-09-12 08:17:03.780 imessage_debug[930:507] oycqAZloTNDm: <43839d61 c07e2467 16ac722f 4eef8e56 58>
2014-09-12 08:17:03.780 imessage_debug[930:507] abKPld1EcMni: <5e9de7f1 7a4e784f c7656619 f708b820 cc>

hope you can help me with my problem sir....

btw my specs are as follow

Mother Board - GA H67M-D2-B3 F7
Processor - i7 2600 (2nd Gen)
memory - 8gig
Graphic Card - GT 610
Hard disk - SSD 128 Kingston and 2TB Sata Drive

Thanks in advance
 
@tadoan,

Glad you up and running, I've added your Motherboard to the list in Part-2 of confirmed boards suffering from the SId Bug.

I'm thinking of writing a new part to the guide for updating to Clover using my hybrid method and getting iMessage up and running, but not sure what the demand would be and where i would find the time ...it seems many users think Clover is complicated which I think is down to overly complex guides - which method did you use ?

Cheers
Jay

I installed UEFI method, although on initial install, the boot loader wasn't initiating correctly so had to USB back in and reinstalled with default options for UEFI. Then used Clover Configurator, Mounted EFI, loaded EFI/EFI/CLOVER/config.plist, disabled graphics injects (GTX 770), injected my MLB/ROM, setup my SMBIOS with identical numbers from Chameleon (system definition, Sn, etc), CMD+S, crossed my fingers and rebooted.
 
Back
Top