@heryts,
Sorry to read that, but i cant say i'm surprised, using someone else's MLB,ROM & UUID values will always carry this danger, however I still think your method has merit, certainly for those users who have a real MAC and a Hack which is having iMessage problems this could be a great solution, but keep the values to yourself.
Have you tired using your method to inject Unique values rather than cloned ones ?
The iMessage debug tool you posted is extremely useful and i would like to include it in the guide as a method of checking that the injected values have 'taken', did you write the tool ?, and if so will it be ok to include in the guide ?
Cheers
Jay
don't worry, i did contact apple support to activate it and my system is working again, it just with different value, i can share if anyone needed, iMessage_debug is not mine, i just found on google, but sorry i can't remember it where it come from and who create it
in my opinion there are only 3 ways we can get iMessage working
1. We need apple id with valid payment information such as credit card then we spend some money on it to buy some application, music or movie via apple store or iTunes store
2. We can contact apple care to activate it.
3. We can take MLB, ROM and if any SMUUID value from real mac or working system (from iMessage_debug of course)
so my conclusion is how many times we generate new smuuid, mlb and maybe rom, i guess it will always end up with contact apple care, unless
1. we have such apple id as above or
2. accidentally we get new random value that match with real mac
and the real problem is when we can't get MLB and ROM at all or any value which is failed on iMessage_debug, it will give activation error on iMessage