jaymonkey do you think it will stay like this generating normal MLB and ROM and Serial numbers or will apple change it again?
@jbamford,
I'd like to think that Apple learnt a valuable lessen last year .... when they locked iMessage down to point where people turned to using cloned values, it caused massive problems for Apple from both from a security and support desk point of view, it must have played havoc with their systems ....
I'm sure that Apple gains a lot from the debugging and innovation that the Hackingtosh Community has, even if they wont admit it. It makes more sense for Apple to work alongside the Hackingtosh community rather than work against it ...
The Hackingtosh community helps a lot with Mac 3rd Party software and hardware, Nvidia is a good example...
I wonder how many new customers Apple got because someone turned their PC into hackingtosh ? ... for most a hackingtosh allows a frustrated or curious PC user to sample OS X without expense .... if they like it they'll buy into it with the on-line services and mobile devices such as iPad & iPhone ....
Hopefully someone true to the Apple ethos told the suits to back-off ..... at least thats what i'd like to think.
Cheers
Jay
@RandomNumber,
Should not be necessary to wipe your drive since all ID's are injected at boot time via Clover, you just need to make sure that everything is correct and it should work. I don't understand how you can be getting the same (16 digit) MLB value if you changed all your ID's .... somethings not quite right ?
Make sure your boot Clover correctly and editing the correct config.plist..
Cheers
Jay
Once rebooted I checked iMessageDebug2 and the exact same 16 character Board Serial Number appears. Also, and I think this is a critical clue, the old ROM value also appears in iMessageDebug, not the new one. So, how do I proceed? Is this a cache file causing this? Could it be related to the "other system MacPro 3,1" with Mavericks that exists on another drive altogether that might be causing some glitch? I have seen no one with this exact issue. Frankly, I'm stumped!
@jaymonkey@RandomNumber,
Make sure your system is booting via UEFI and using /EFI/EFI/Clover .... if not and you still have an old legacy boot-loader in the root of your os x then it could be that your inadvertently booting from that and not the clover config .... just a thought, i've seen this many times .... I've even read about systems booting from forgotten usb drives plugged in the back....something to check.
Enable show all files and look for a file called 'boot' in the root of your OS X Start-up Partition (not the EFI Partition), if its there then delete it and fix your BIOS/UEFI config to boot from the EFI Partition with Clover on it.
I've also seen where people install Clover in legacy and UEFI mode, they think the system is booting via the EFI partition so edit the config.plist in /EFI/EFI/Clover, but the system is in reality booting from the OS X startup partition and the /EFI/Clover folder ....it's an easy mistake to make when starting out with Clover and unfamiliar with PC UEFI/EFI booting.
Cheers
Jay
@jaymonkey
Just to be clear if I was not before. This is NOT a UEFI Board. I have installed Clover using Legacy method. Does that change things?