Clover General discussion

[SavageAUS]

Hmm... Did it work before? What changed in the meantime?

 

Also, are you using automatic time zone set to ON? If not, maybe you can switch it on... Some people say it could be a server issue here, caused by the wrong date and time. I could be very wrong though. I'm still trying to find a probable cause here. But...you can try. Maybe it helps.

No I've never ever had working iMessage.

I'll check time zone settings.

 

Sent from my SM-G930F using Tapatalk

[camillionario]

No I've never ever had working iMessage.

I'll check time zone settings.

 

 

share your config plist to take a look. I have several config.plist with iMessage and Facetime ok.

[chris1111]

No I've never ever had working iMessage.

I'll check time zone settings.

 

Sent from my SM-G930F using Tapatalk

Try this

Edit

enable message FaceTime in my new Mavercicks now with that way 

 

 

 

 

 

Message FaceTime.pdf.zip

[Cyberdevs]

No I've never ever had working iMessage.

I'll check time zone settings.

 

Sent from my SM-G930F using Tapatalk

I suggest you remove your device from iCloud, create a new config.plist and then reconfigure your new config as same as the old one, after choosing the SMBIOS generate several serial numbers then in system parameters create a new custom UUID and then go to Rt Variables and generate a new ROM then save the config and reboot.

 

Just copy the existing EFI folder on a USB disk just in case if anything goes wrong then try with the new settings and sign in iCloud and iMessage.

[Funky frank]

What happened?

[SavageAUS]

I suggest you remove your device from iCloud, create a new config.plist and then reconfigure your new config as same as the old one, after choosing the SMBIOS generate several serial numbers then in system parameters create a new custom UUID and then go to Rt Variables and generate a new ROM then save the config and reboot.

 

Just copy the existing EFI folder on a USB disk just in case if anything goes wrong then try with the new settings and sign in iCloud and iMessage.

Yeah I've tried that and didn't work unfortunately. Could it be because I don't have an iPhone? And have never setup iMessage on a real mac?

 

Sent from my SM-G930F using Tapatalk

[Pavo]

Yeah I've tried that and didn't work unfortunately. Could it be because I don't have an iPhone? And have never setup iMessage on a real mac?

 

Sent from my SM-G930F using Tapatalk

That would be interesting, I would imagine you could still use Messages without ever owning a phone but would only be able to send messages to Apple ID members only. Not sure if it would even be possible to activate Messages without activating the service on a iPhone first. 

[SavageAUS]

That would be interesting, I would imagine you could still use Messages without ever owning a phone but would only be able to send messages to Apple ID members only. Not sure if it would even be possible to activate Messages without activating the service on a iPhone first.

I don't suppose anyone has a spare iMessage account that works that I could test? You can change the password before allowing me to use it and change it again after.

 

Sent from my SM-G930F using Tapatalk

[Cyberdevs]

Yeah I've tried that and didn't work unfortunately. Could it be because I don't have an iPhone? And have never setup iMessage on a real mac?

 

Sent from my SM-G930F using Tapatalk

Yeah that will explain it

[MICKHAEL]

It works without activating on iPhone, or maybe I am just lucky) use MBL and ROM from real Mac!

 

Sent from my Nexus 4 using Tapatalk

[Slice]

You need to dump some real MBL and MAC

 

Sent from my Nexus 4 using Tapatalk

I have own MLB and MAC, non-Apple. And I registered AppleID before I bought iPhone. All works!

I have to remind that you should have a payable account (VISA or something else).

[SavageAUS]

I have own MLB and MAC, non-Apple. And I registered AppleID before I bought iPhone. All works!

I have to remind that you should have a payable account (VISA or something else).

I do have my visa card attached to my apple id.

 

Unless a sure fire way is described I'll wait a few months when I switch from android to apple.

 

Sent from my SM-G930F using Tapatalk

[MICKHAEL]

I have own MLB and MAC, non-Apple. And I registered AppleID before I bought iPhone. All works!

I have to remind that you should have a payable account (VISA or something else).

No Visa non payable account.

 

Sent from my Nexus 4 using Tapatalk

[ccphuc2016]

Why my PC install Clover 4380 - 4387 - 4391 to HDD  bios UEFI - GPT boot into macOS 10.13.2 & 10.13.3 verry slow 15 minute ?

 

 

Install for UEFI booting only

Install Clover in the ESP

 

OsxAptioFix2Drv + EmuVariableUefi-64.efi

 

HELP ME ? THANK

 

 

 

[artur_pt]

hello

 

maybe u don't need

 

EmuVariableUefi-64.efi

 

try without it and use 

 

OsxAptioFix3Drv.efi

 

good hack

[ccphuc2016]

hello

 

maybe u don't need

 

EmuVariableUefi-64.efi

 

try without it and use 

 

OsxAptioFix3Drv.efi

 

good hackI install Cliver 4391 on HDD

 

 

I insstall Clover 4391 on HDD bios UEFI- GPT

 

- Install for UEFI booting - only

- Install Clover in the ESP

- OsxAptioFix2Drv + EmuVariableUefi-64.efi

 

 

 

 

I download FakeSMC unzip & copy 6 file to my Clover 4391 on HDD path EFI\Clover\Kexts\other

 

https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/

 

 

 

 

 

Boot to login green verry fast 1minute

 

Thank

[el_charlie]

I insstall Clover 4391 on HDD bios UEFI- GPT

 

- Install for UEFI booting - only

- Install Clover in the ESP

- OsxAptioFix2Drv + EmuVariableUefi-64.efi

 

 

 

 

 

 

I download FakeSMC unzip & copy 6 file to my Clover 4391 on HDD path EFI\Clover\Kexts\other

 

https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/

 

 

 

 

 

 

 

Boot to login green verry fast 1minute

 

Thank

HWMonitor is an app, there's no need to have it on CLOVER/Kexts/Other, Lol. Put that in /Applications.

 

Like people said, use OsxAptioFix3 without Emuvariable. Make a backup USB first in case it doesn't boot.

 

You can also try with AptioMemoryFix instead of OsxAptio.

[arsradu]

Also, @el_charllie, if I may, I think you don't need RC scripts anymore...if you're using OsxAptioFix3Drv. Someone, please, correct me if I'm wrong, but I didn't have any issues so far without that.

 

Now, I know Clover is meant to be as customisable as possible, so people can use whatever they need, if they need it, and it's been an amazing tool for me for YEARS, but for the sake of usability, do you guys think it would be maybe better to allow users to select only drivers which are not mutually exclusive?

 

For example, if you select OsxAptioFix3Drv, automatically deselect EmuVariableUefi since you don't need it anymore? This way, it's clear for everyone that they are doing the same thing, and they're not needed (or not supposed to work) together. In this particular case, having them both won't create any issues (at least as far as I'm concerned), but there could be cases where you're not supposed to mix two drivers, because that WILL create issues. And, especially for those cases, such a feature would be nice to have.

 

I know this is like a minor "issue" (if you can call it an issue in the first place). I don't know... It's just an idea.

 

Also, I know that someone will probably come back and say something like "Clover is not meant for stupid people" ). Still, I think it would be a good idea for newcomers. Clover has a pretty steep learning curve, in my opinion. And I personally found a lot of things to be confusing at the beginning (especially coming from Chameleon).

 

Point I'm trying to make is this: I know it's not for "stupid people". Still, I don't think that's a reason not to make it a bit more user friendly, if that helps to avoid confusion (and possible issues) for newcomers.

[el_charlie]

Also, @el_charllie, if I may, I think you don't need RC scripts anymore...if you're using OsxAptioFix3Drv. Someone, please, correct me if I'm wrong, but I didn't have any issues so far without that.

 

Now, I know Clover is meant to be as customisable as possible, so people can use whatever they need, if they need it, and it's been an amazing tool for me for YEARS, but for the sake of usability, do you guys think it would be maybe better to allow users to select only drivers which are not mutually exclusive?

 

For example, if you select OsxAptioFix3Drv, automatically deselect EmuVariableUefi since you don't need it anymore? This way, it's clear for everyone that they are doing the same thing, and they're not needed together. I know this is like a minor "issue" (if you can call it an issue in the first place). I don't know... It's just an idea.

 

I know that someone will probably come back and say something like "Clover is not meant for stupid people" ). Still, I think it would be a good idea for newcomers. Clover has a pretty steep learning curve, in my opinion. And I personally found a lot of things to be confusing at the beginning (especially coming from Chameleon).

 

Point I'm trying to make is this: I know it's not for "stupid people". Still, I don't think that's a reason not to make it a bit more user friendly, if that helps to avoid confusion for newcomers.

 

Well, I have the RC scripts on my laptop hack because I was booting on legacy before. Should I delete them??

 

I think they deal with EmuVariable to write on the nvram.plist when there's no native NVRAM but IDK if it's safe to delete them.

 

I have rc.boot.d , rc.shutdown.d, rc.clover.lib and other RC but IDK if they're from Clover: rc.common, rc.common˜previous and rc.netboot.

[arsradu]

Well, I have the RC scripts on my laptop hack because I was booting on legacy before. Should I delete them??

 

I think they deal with EmuVariable to write on the nvram.plist when there's no native NVRAM but IDK if it's safe to delete them.

 

I have rc.boot.d , rc.shutdown.d, rc.clover.lib and other RC but IDK if they're from Clover: rc.common, rc.common˜previous and rc.netboot.

 

 

Hmm, I'm not sure about legacy boot... I haven't used that in years (didn't need to). But if you're on UEFI boot now, I don't think you need them anymore. It won't harm you to keep them. And in my personal experience, I haven't gotten any issues without them. But...you can wait for someone else's opinion, if you're not sure. As I said, it won't harm you to keep them both. It's just a matter of "should you remove them, if they're not needed anymore?"

[el_charlie]

Hmm, I'm not sure about legacy boot... I haven't used that in years (didn't need to). But if you're on UEFI boot now, I don't think you need them anymore. It won't harm you to keep them. And in my personal experience, I haven't gotten any issues without them. But...you can wait for someone else's opinion, if you're not sure. As I said, it won't harm you to keep them both. It's just a matter of "should you remove them, if they're not needed anymore?"

 

Yeah, I had them because I didn't know I could boot in UEFI and had native NVRAM (I have hardware nvram without OsxAptio3), so I think I can delete them safely but I'll wait for some confirmation.

[arsradu]

Yeah, I had them because I didn't know I could boot in UEFI and had native NVRAM (I have hardware nvram without OsxAptio3), so I think I can delete them safely but I'll wait for some confirmation.

 

See, this was exactly my case. At the begging, I was using Clover in Legacy mode, although I had an UEFI enabled motherboard. Simply because Chameleon was a legacy bootloader (I think it still is, if anyone is still using it) and I didn't know that I don't actually need to use Legacy mode if I have an UEFI motherboard.

 

Also, if you have hardware NVRAM (meaning a motherboard under series 100, like my Z97S from MSI, for example), you don't need the scripts, EmuVariable or OsxAptioFix3Drv (basically you can use any OsxAptioFix, not necessarily "v3"), for sure. It's already tested. 

 

You can still use OsxAptioFix3Drv, no problem. It's just that, in your particular case, the NVRAM fix won't make any difference, since you already have hardware NVRAM.

[ccphuc2016]

HWMonitor is an app, there's no need to have it on CLOVER/Kexts/Other, Lol. Put that in /Applications.

 

Like people said, use OsxAptioFix3 without Emuvariable. Make a backup USB first in case it doesn't boot.

 

You can also try with AptioMemoryFix instead of OsxAptio.

You are installing this way Clover 4391 ?

 

[el_charlie]

You are installing this way Clover 4391 ?

 

 

No, don't use AptioMemoryFix and OsxAptio3, use one or another. Try with AptioMemory first as recommended by Slice, then give OsxAptio3.

 

Make sure you have a CLover USB backup to boot in case it desn't work.

 

IDK if you need Partition-Dxe, I can boot fine without it. It's best to use the less drivers. But as I said, make a Clover USB backup with the current configuration you have and test you can boot from it in case something goes wrong.

[arsradu]

No, don't use AptioMemoryFix and OsxAptio3, use one or another. Try with AptioMemory first as recommended by Slice, then give OsxAptio3.

 

Make sure you have a CLover USB backup to boot in case it desn't work.

 

IDK if you need Partition-Dxe, I can boot fine without it. It's best to use the less drivers. But as I said, make a Clover USB backup with the current configuration you have and test you can boot from it in case something goes wrong.

 

PartitionDxe is not necessary if you're not doing anything crazy with your partition maps.

 

Quoting from the driver's description: [PartitionDxe-64] is a "64bit driver to support non-usual partition maps such as: hybrid GPT/MBR or Apple Partition Map."

 

So, if you're not using any of that, you shouldn't be needing this driver either.