Recent content by Hasslethehoff

That is amazing that you posted this today and I'm googling for info about the Highpoint vs. Areca for a hackintosh install and here it is. I was planning on an Areca 1224-8i but I will check eBay for the newer model as you found. Thank you!

Right, I know that works as well, but doesn't it often result in the "call Apple" as the system doesn't exist in their DB? Which is fine, I can do that again, but I have extra old Macs here that won't ever be used for messaging so I'm glad to have it working this way first.

^^ Agreed. And as someone who works with databases and writes reports to detect fraud, mismatching things like MLB and S/N is very easy to detect if they want to start doing it.

Your guide was so in-depth I bet the Apple devs link each other to this thread when they work on ways to stop iMessage frauds as an example of how they are being beat.

I'll confirm ^^^ I took just the ROM and MLB from an old system I'll never use any more and injected them with RTVariables. Everything else was made up by Clover Config and it worked.

OK As I'm sure Jaymonkey suspected, you have to be very careful about completely duping all of the IDs of another Apple device you own and use. Since duping my Air's ID on to my Hack, I've started experiencing messaging weirdness. My iPhone is now stuck at waiting for activation, the Text...

You can get most of this info from the giant iMessage sticky but some of of the details like putting ROM in RTVariables is buried or not obvious. Good post, I used the same technique. edit: one point that wasn't clear from the giant thread is that to put your real mac's ROM into RTVariables...

SmUUID (IOPlatformUUID): 5002e503-4904-ed05-e306-560700080009 ^^ That is the real Mac's hardware UUID. Verify this yourself in System Report.

This sounds simpler but also more risky. If you don't use the spoofed mac's systemID and descriptor, the logs will have two different machines using the same serial number to login. At least if you leave it as the original mac's system type, the log would look more similar on Apple's end. IMO...

Same here except I used my Air. I was going to spoof a mini but using the definition MacMini only brought up one GPU and one screen. Everything is just as smooth with it thinking it is an Air as it was when it thought it was a MacPro3,1 under Chameleon.

First, thanks for all the work; the guide has been invaluable. I wish I had read the post#1762 before and kept my old Mavericks values. I may try and go back to those IDs. However to get the ROM/MLB to exactly match the debug output of my Air, I had to set both the smUUID to the hardware UUID...

I believe that is correct. I had to use RTVariables since I was using a "stolen" ROM from my own machine and without RTVariables the ROM wouldn't be right. Keep using imessage_debug until you get it all set and good luck!

Put one in the smUUID and a different one in the <key>SystemParameters</key>...<key>CustomUUID</key> If smUUID and CustomUUID are different THEN smUUID becomes your HardwareUUID and will not change.

I just got mine working as well. I switched from Chimera 4 to Clover. I didn't want to call Apple again with another fake ID so I spoofed my info from my Air into the .plist. This was invaluable to get the spoofing right: I also had to use the RtVariables to inject the ROM and not let it...

NVIDIA Releases Alternate Graphics Drivers for 10.10.0 (343.01.01f01) with 'Maxwell' GeForce GTX 970 and 980 Support I'm no expert but I do have three 780s going under Clover/Yosemite and had them going under Chimera/Yos and Chameleon/Mavericks. Are you on Clover? For me, only one card would...