406 replies to this topic

[p.H]

By chance do you have a real mac to try logging in with your apple id to see if you still get the error. That would help narrow down to whether this is a problem with the hack or a problem with your apple id.

I do not. Maybe I can try borrow my classmates idevice to test.

[ncmontas]

Do you have the ending </dict> for the RtVariables section. You can also try setting ROM variable but that shouldn't matter.

yup i have
<key>RtVariables</key>
<dict>
<key>MLB</key>
<string>

xxxxxxxxxxx234567

</string>
</dict>

[dtcalvin]

I do not. Maybe I can try borrow my classmates idevice to test.

same to U！i have tried to login from my mba,and it worked,but not on my hack,i all try ios device tonight....

[eep357]

For MLB I have been adding the extra 6 digits to serial before the last 3 like this: XXXXXXXX234567XXX where the X is all orig serial number. Don't know that it really matters, but have not seen errors when doing it this way.

[p.H]

For MLB I have been adding the extra 6 digits to serial before the last 3 like this: XXXXXXXX234567XXX where the X is all orig serial number. Don't know that it really matters, but have not seen errors when doing it this way.

My hack use MBP6,1 smbios whose fake serial is 12 digits. Dunno if this is the reason why call Apple issue raises.

[fau7i]

I also added 5 more characters at the end of an orig serial number (MBP8,1) to make it 17 char long, and have no problem to sign in and out.

[Pene]

Does anyone have access to a real MacPro5,1 or MacPro4,1?
In case you do, could you please post or send me the output of the following command via terminal:

echo `nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB`[end] `nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM`[end]

(I added the [end] as I suspect the MLB may have some spaces at the end)

[iFIRE]

My hack use MBP6,1 smbios whose fake serial is 12 digits. Dunno if this is the reason why call Apple issue raises.

+ 1

 Captura de pantalla 2013-01-11 a la(s) 11.01.43.png   128.84KB   112 downloads

[p.H]

I also added 5 more characters at the end of an orig serial number (MBP8,1) to make it 17 char long, and have no problem to sign in and out.

Your hack use desktop's smbios ? How about the serial ? Is the serial your real MBP's or the fake one for desktop ?

[fau7i]

My config.plist is like this;

<key>SMBIOS</key>
<dict>
<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>ProductName</key>
<string>MacBookPro8,1</string>
<key>Family</key>
<string>MacBook Pro</string>
<key>SerialNumber</key>
<string>C02XXXXXXXXX</string>
</dict>
<key>RtVariables</key>
<dict>
<key>MLB</key>
<string>C02XXXXXXXXXFAU7I</string>
</dict>

BTW, the serial number comes from real MBP.

[Carstiman]

hello, got it working again with Chameleon 2157, Mac mini 5,1
and ABCDE at the end of the generated serial from Chameleon Wizzard.

tried it with Mac Pro 3.1 too but no luck.

i hope it could help

[STLVNUB]

It's Alive, Messages that is
Silly me had the key as RTVariables, NOT RtVariables

Now to find all the hair I'd pulled out and glue it back on

edit:
actually there is more to the story than that.

[rcork]

hello, got it working again with Chameleon 2157, Mac mini 5,1
and ABCDE at the end of the generated serial from Chameleon Wizzard.

tried it with Mac Pro 3.1 too but no luck.

i hope it could help

Are you saying Chameleon has been updated to populate the MLB and ROM variables?

[ZackehSoul]

Are you saying Chameleon has been updated to populate the MLB and ROM variables?

Here's hoping!

[Carstiman]

Are you saying Chameleon has been updated to populate the MLB and ROM variables?

i don´t know. i just tried it and i could log in again.

could log in as MacPro3,1 again too.
i boot with Clover980 from USB and behind i could log in i boot from HD with Cham. 2157

just want to share it. but can´t tell you why it works

[p.H]

Are you saying Chameleon has been updated to populate the MLB and ROM variables?

Following the change log of chameleon, it seems chameleon is not capable of at the moment.

i don´t know. i just tried it and i could log in again.

could log in as MacPro3,1 again too.
i boot with Clover980 from USB and behind i could log in i boot from HD with Cham. 2157

just want to share it. but can´t tell you why it works

Once you succeeded with clover, unless you log off your message again, it should work fine regardless of your bootloader.

[JUN Ho]

I want to share my experience about iMessage login problem. I hope you Dev team find more hint from my experience.
I was using iMessage after I switch from Chameleon to Clover, and fix login error.
Everything was good.
Today I try to change my config.plst of Clover for experiment.
I was using customUUID in config.plist. and InjectSystemID option was 'No".
I just change from "No" to "Yes", and the other options are all same.
After I reboot I cannot login iMessage, and I met popup to call Apple Care whenever I try to login.
I revoke my config.plist right away (From"Yes" to "No"), and reboot.
Try login, but still I cannot login to iMessage. "call Apple Care" popup again.
I can resolve login error following next process.

1.First, I click to "Forgot Password?"
2.I make new Password following the process.
3.First login iCloud on computer,and second iPhone using new Password.
4.Finally I try to login iMessage, then I got a mail from Apple on my iPhone.
"Dear {censored},
Your Apple ID (xxxxxxx@xxxx.xx) was used to sign in to iMessage on a Mac Pro named “{censored}'s MacPro”.
If you have not recently set up a Mac Pro with your Apple ID, then you should change your Apple ID password…."
5.Finally I can login iMessage again. Voila !!

[p.H]

I want to share my experience about iMessage login problem. I hope you Dev team find more hint from my experience.
I was using iMessage after I switch from Chameleon to Clover, and fix login error.
Everything was good.
Today I try to change my config.plst of Clover for experiment.
I was using customUUID in config.plist. and InjectSystemID option was 'No".
I just change from "No" to "Yes", and the other options are all same.
After I reboot I cannot login iMessage, and I met popup to call Apple Care whenever I try to login.
I revoke my config.plist right away (From"Yes" to "No"), and reboot.
Try login, but still I cannot login to iMessage. "call Apple Care" popup again.
I can resolve login error following next process.

1.First, I click to "Forgot Password?"
2.I make new Password following the process.
3.First login iCloud on computer,and second iPhone using new Password.
4.Finally I try to login iMessage, then I got a mail from Apple on my iPhone.
"Dear {censored},
Your Apple ID (xxxxxxx@xxxx.xx) was used to sign in to iMessage on a Mac Pro named “{censored}'s MacPro”.
If you have not recently set up a Mac Pro with your Apple ID, then you should change your Apple ID password…."
5.Finally I can login iMessage again. Voila !!

The reason why you're able to sign in is perhaps that you'v used your id in idevice!
Meaning you're telling Apple that this id can be used for message because it has been confirmed by your iphone.
Though it's been widely suggested using the idevice to activate your id if you come across problems, you just confirmed it again

[ncmontas]

What did you get about the error?

same as before The server encountered an error processing registration, the odd thing is when i try to logout to my idevice, and login using my account it is saying wrong password, even though i entered the correct one.

[p.H]

same as before The server encountered an error processing registration, the odd thing is when i try to logout to my idevice, and login using my account it is saying wrong password, even though i entered the correct one.

If you're using clover and making the right edits, there should not be this error.