Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

SavageAUS
SavageAUS
Posted
Posted

Awesome thanks @Slice.

I like to test out linux distro's on a regular basis so ill let you know if i run into any trouble on the Clover end.

Maybe i still had EFI files left over from Ubuntu on my mint install which could be why Clover showed Mint as Ubuntu.

arsradu
arsradu
Posted
Posted

Guys, I've done something really stupid. 

 

I bought a Retina Macbook Pro 13 late-2013 and installed Sierra 10.12.1 onto it. No problems so far. Then I created a new partition and tried to install the Beta onto it, using a USB drive made with Clover (hackintosh style) and at first I selected OSX Base System on boot up. And it got to the installer and got an error (error 0 or something like that). And now I think I know why that happened.

 

Anyway, then I selected EFI (also from the USB drive) and it loaded up Clover. Then I selected the USB drive from the Clover UI (like I would do if I want a Hackintosh installation) and...it would just stay there with the Apple logo and no loading bar. After a while, I force shut down the computer. And tried to boot up normally. Removed the USB and everything.

 

But since then, it goes into boot loop, with no Apple logo, only the chime. It sounds the chime over and over again.

 

Please, tell me you know how to fix this. It's clearly a software issue. I'm pretty sure something got corrupted. I just don't know what and how to fix it. :(

 

I tried booting in Safe Mode (holding the Shift key while booting), tried booting in Recovery (holding Command + R), tried selecting a different boot drive (Option key). I don't know what else to try....

 

Sorry about the possible off-topic. I just don't know what to do. I even made a new USB installation and tried to boot from it. But..I only got the endless loop and nothing else.

Faradis
Faradis
Posted
Posted
 
 

 

Guys, I've done something really stupid. 

 

I bought a Retina Macbook Pro 13 late-2013 and installed Sierra 10.12.1 onto it. No problems so far. Then I created a new partition and tried to install the Beta onto it, using a USB drive made with Clover (hackintosh style) and at first I selected OSX Base System on boot up. And it got to the installer and got an error (error 0 or something like that). And now I think I know why that happened.

 

Anyway, then I selected EFI (also from the USB drive) and it loaded up Clover. Then I selected the USB drive from the Clover UI (like I would do if I want a Hackintosh installation) and...it would just stay there with the Apple logo and no loading bar. After a while, I force shut down the computer. And tried to boot up normally. Removed the USB and everything.

 

But since then, it goes into boot loop, with no Apple logo, only the chime. It sounds the chime over and over again.

 

Please, tell me you know how to fix this. It's clearly a software issue. I'm pretty sure something got corrupted. I just don't know what and how to fix it. :(

 

I tried booting in Safe Mode (holding the Shift key while booting), tried booting in Recovery (holding Command + R), tried selecting a different boot drive (Option key). I don't know what else to try....

 

Sorry about the possible off-topic. I just don't know what to do. I even made a new USB installation and tried to boot from it. But..I only got the endless loop and nothing else.

trybooting from usb without clover only with apple installer

smolderas
smolderas
Posted
Posted

Can't select the boot drive anymore. :( It just sounds the chime over and over again. With no logo, no graphics on the screen.

Try reseting PRAM and then SMC. After that recovery mode should work.

 

If none of those above works, try with an USB installer (vanilla!). If that won't work either, try the apple support.

arsradu
arsradu
Posted
Posted

Try reseting PRAM and then SMC. After that recovery mode should work.

 

If none of those above works, try with an USB installer (vanilla!). If that won't work either, try the apple support.

Tried PRAM and SMC reset. None of them worked. I mean they did work (at least I think the SMC reset worked), but didn't actually solve the issue.

 

 

I made another USB drive. Without Clover. And it boots fine from it on another Macbook Pro (using the Option key to select the boot drive). So I'm pretty sure the USB is now ok.

 

But on this Mac, it just doesn't show anything on the screen when pressing Option. It just sounds the chime, over and over again, without showing the logo.

 

The laptop is not under warranty. So..not sure what good the Apple Support would do in this case. :(

smolderas
smolderas
Posted
Posted

Tried PRAM and SMC reset. None of them worked. I mean they did work (at least I think the SMC reset worked), but didn't actually solve the issue.

 

 

I made another USB drive. Without Clover. And it boots fine from it on another Macbook Pro (using the Option key to select the boot drive). So I'm pretty sure the USB is now ok.

 

But on this Mac, it just doesn't show anything on the screen when pressing Option. It just sounds the chime, over and over again, without showing the logo.

 

The laptop is not under warranty. So..not sure what good the Apple Support would do in this case. :(

Well, then begin using clover on it then ;)

You said that it works.

bronxteck
bronxteck
Posted
Posted

did your clover boot stick have a apple folder? if it did it might have tried installing an smc update and if it was from another model then you might have to load the correct one into it.

 also if you can pull the drive and see if the bootloop stops then you know its just a corrupted drive.

arsradu
arsradu
Posted
Posted

Well, then begin using clover on it then ;)

You said that it works.

 

I can't select any boot drive anymore. It doesn't respond to Option + Power. It just keeps rebooting.

did your clover boot stick have a apple folder? if it did it might have tried installing an smc update and if it was from another model then you might have to load the correct one into it.

 also if you can pull the drive and see if the bootloop stops then you know its just a corrupted drive.

 

I don't know.... If it ads one when installing it, then it might have had one indeed. And yeah, it was surely from another model.... Stupid me. I just realized it. Of course it couldn't have worked.

 

I'm pretty sure it will stop. Just as I'm pretty sure it's just a corrupted EFI.

 

But I've got two problems here:

1. no pentalobe screwdriver.

2. even if it stops, how do I correct the mistake from outside? How can I put back the correct whatever it is, without being able to boot up the computer? It's not like I can connect it to my hackintosh and access it from outside. The connector on those SSDs is proprietary.

Use createinstallmedia and reinstall. Be sure to wipe the ESP.

 

How? I already got a USB drive and it boots fine on another MacBook Pro. So let's say the USB drive is ok now. With no Clover. But how do I wipe the ESP without being able to load the USB drive and without being able to boot into the OS?

joevt
joevt
Posted
Posted

2. even if it stops, how do I correct the mistake from outside? How can I put back the correct whatever it is, without being able to boot up the computer? It's not like I can connect it to my hackintosh and access it from outside. The connector on those SSDs is proprietary.

Target disk mode?

https://support.apple.com/en-ca/HT201462

 

Or maybe your EFI boot fails before it checks for that "T" keypress, like it fails for every other keypress you've tried?

arsradu
arsradu
Posted
Posted

Target disk mode?

https://support.apple.com/en-ca/HT201462

 

Or maybe your EFI boot fails before it checks for that "T" keypress, like it fails for every other keypress you've tried?

 

Indeed it does. None of the key combinations (aside from Reset SMC, which didn't actually do anything to fix the issue) seemed to worked. Maybe PRAM reset too. i don't know, cause it didn't make a difference.

Anyway, I bought an adapter to connect the SSD directly to my hackintosh and see what's wrong with it. I suppose the EFI partition got corrupted or something. Or it just wrote some wrong values onto it. I think it's the most logical explanation. Anyway, I still need the screwdrivers (Torx T5 and Pentalobe P5) to remove the SSD from the MacBook before attempting anything with it. So maybe tomorrow I'll try to fix this.

 

If anyone got any idea how to do it without taking out the SSD, I would gladly try it. But so far this looks like the only possible solution to this issue.

bronxteck
bronxteck
Posted
Posted

maybe you can uncompress the smc from apples download page and add it to the apple folder on the efi of the thumb drive using the file paths and structures. you would have to look at an existing APPLE folder of course. or setup a hack with your machines smbios and see if osx creates it for you on the efi partition then transfer it.

arsradu
arsradu
Posted
Posted

maybe you can uncompress the smc from apples download page and add it to the apple folder on the efi of the thumb drive using the file paths and structures. you would have to look at an existing APPLE folder of course. or setup a hack with your machines smbios and see if osx creates it for you on the efi partition then transfer it.

 

So..I got the SSD out... Connected it to my hackintosh. And the only thing I noticed different from my other macbook's EFI, is the presence of an UPDATERS folder, containing what I can only assume is what Clover tried to flash onto it.

 

post-1303722-0-62218600-1481134591_thumb.png post-1303722-0-76575900-1481134612_thumb.png post-1303722-0-10709400-1481134625_thumb.png

 

Problem is that, even with no SSD installed, it still goes into the endless chime... So..I guess it's either cached somewhere. Or I don't know... But it doesn't seem to be the SSD anymore. Any ideas what else could it be?

bronxteck
bronxteck
Posted
Posted

mac-189a3d4f975d5ffc seems to be MacBook Pro 11,1 but i do not see an SMC update for it at https://support.apple.com/en-us/HT201518only an EFI Boot Rom.

maybe a methode like this one might help https://pubmem.wordpress.com/2011/04/09/flash-efi-firmware-update-manually-on-a-macbook-51/

even if you can create it on a hack and compare/ transfer it. or boot the hack with the MAC HDD using the correct smbios and trying.

FredWst
FredWst
Posted
Posted

So..I got the SSD out... Connected it to my hackintosh. And the only thing I noticed different from my other macbook's EFI, is the presence of an UPDATERS folder, containing what I can only assume is what Clover tried to flash onto it.

 

attachicon.gifScreen Shot 2016-12-07 at 8.08.00 PM.png attachicon.gifScreen Shot 2016-12-07 at 8.08.08 PM.png attachicon.gifScreen Shot 2016-12-07 at 8.08.16 PM.png

 

Problem is that, even with no SSD installed, it still goes into the endless chime... So..I guess it's either cached somewhere. Or I don't know... But it doesn't seem to be the SSD anymore. Any ideas what else could it be?

 

So..I got the SSD out... Connected it to my hackintosh. And the only thing I noticed different from my other macbook's EFI, is the presence of an UPDATERS folder, containing what I can only assume is what Clover tried to flash onto it.

 

attachicon.gifScreen Shot 2016-12-07 at 8.08.00 PM.png attachicon.gifScreen Shot 2016-12-07 at 8.08.08 PM.png attachicon.gifScreen Shot 2016-12-07 at 8.08.16 PM.png

 

Problem is that, even with no SSD installed, it still goes into the endless chime... So..I guess it's either cached somewhere. Or I don't know... But it doesn't seem to be the SSD anymore. Any ideas what else could it be?

 

hi,

 

if you got this, it means that your smbios data are not up to date.

Try to use Clover last revision. and delete these files.

 

Fred

arsradu
arsradu
Posted
Posted

 

 

hi,

 

if you got this, it means that your smbios data are not up to date.

Try to use Clover last revision. and delete these files.

 

Fred

 

I did, but not using Clover. As I said above, I bought a PCI adapter for Mac SSDs to have direct access to it. But it's not the SSD since it does this even without the SSD plugged in. It doesn't even show the boot drive picker (Option key + Power)

 

Update: fixed by replacing the EFI chipset on the motherboard. Apparently, the firmware on that chipset got corrupted due to an incomplete update (I suppose when I force shut it down, that happened). It was like a $60 repair. Could have been a lot worse. Just for everyone wondering if it can be fixed without replacing the entire board. Yeah, it can.

 

Thanks for everyone's feedback on this.

smolderas
smolderas
Posted
Posted

Hello Slice,

 

here is updated shutdown script. There were some issues in previous script, that it saved to root of boot Volume and exited. But it can't be read on file vault 2. With this version it only saves the content of NVRAM to the EFI partition of the boot volume.

 

Second thing is: I'm not sure, that those rc.shutdown scripts get called. I had to set a LogoutHook for it to get it run:

sudo defaults write com.apple.loginwindow LogoutHook /etc/rc.shutdown.d/80.save_nvram_plist.local

Cheers

Slice
Slice
Posted
Posted

Hello Slice,

 

here is updated shutdown script. There were some issues in previous script, that it saved to root of boot Volume and exited. But it can't be read on file vault 2. With this version it only saves the content of NVRAM to the EFI partition of the boot volume.

 

Second thing is: I'm not sure, that those rc.shutdown scripts get called. I had to set a LogoutHook for it to get it run:

sudo defaults write com.apple.loginwindow LogoutHook /etc/rc.shutdown.d/80.save_nvram_plist.local

Cheers

Thanks,

committed to 3961.

  • Like 1
PMheart
PMheart
Posted
Posted

Hi.

In kext_inject.c we may try removing some byte values between KBEYosSearchEXT & KBESieSearchEXT?

And this makes KBEYosSearchEXT & KBESieSearchEXT the same and thus we just keep one of them?

 

// Yosemite

UINT8   KBEYosSearchEXT[]        = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0xEB, 0x05, 0xE8, 0xCE, 0x02, 0x00, 0x00 };  // Remove ', 0xE8, 0xCE, 0x02, 0x00, 0x00'

 

UINT8   KBEYosReplaceEXT[]       = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0x90, 0x90, 0xE8, 0xCE, 0x02, 0x00, 0x00 };

 

// Sierra

// Sherlocks: Sierra SIP, cecekpawon: Sierra DP2+

// need to use KBEYos*EXT patch for Sierra DP1

// need to use KBESie*EXT patch for Sierra DP2+

UINT8   KBESieSearchEXT[]        = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0xEB, 0x05, 0xE8, 0x7E, 0x05, 0x00, 0x00 }; // Remove ', 0xE8, 0x7E, 0x05, 0x00, 0x00'

UINT8   KBESieReplaceEXT[]       = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0x90, 0x90, 0xE8, 0x7E, 0x05, 0x00, 0x00 };

 

 

Confirmed. Just patch them 1 time after deleting the redundant byte values. Not caused confusions. So I think we can just keep one of them for convenience?

But... Not tested for Yos and EC. Just tested on 10.12.1 (16B2657) and 10.12.2 (16C63a)...

 

 

Sherlocks
Sherlocks
Posted
Posted

Hi.

In kext_inject.c we may try removing some byte values between KBEYosSearchEXT & KBESieSearchEXT?

And this makes KBEYosSearchEXT & KBESieSearchEXT the same and thus we just keep one of them?

 

// Yosemite

UINT8 KBEYosSearchEXT[] = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0xEB, 0x05, 0xE8, 0xCE, 0x02, 0x00, 0x00 }; // Remove ', 0xE8, 0xCE, 0x02, 0x00, 0x00'

 

UINT8 KBEYosReplaceEXT[] = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0x90, 0x90, 0xE8, 0xCE, 0x02, 0x00, 0x00 };

 

// Sierra

// Sherlocks: Sierra SIP, cecekpawon: Sierra DP2+

// need to use KBEYos*EXT patch for Sierra DP1

// need to use KBESie*EXT patch for Sierra DP2+

UINT8 KBESieSearchEXT[] = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0xEB, 0x05, 0xE8, 0x7E, 0x05, 0x00, 0x00 }; // Remove ', 0xE8, 0x7E, 0x05, 0x00, 0x00'

UINT8 KBESieReplaceEXT[] = { 0xE8, 0x25, 0x00, 0x00, 0x00, 0x90, 0x90, 0xE8, 0x7E, 0x05, 0x00, 0x00 };

 

 

Confirmed. Just patch them 1 time after deleting the redundant byte values. Not caused confusions. So I think we can just keep one of them for convenience?

But... Not tested for Yos and EC. Just tested on 10.12.1 (16B2657) and 10.12.2 (16C63a)...

 

attachicon.gifnew_kext_inject.c.zip

Did you check all kernel binary value?

 

I checked all. If reduce binary value, Mavericks kernel patched two times. Its not correct. I think we remain enough binary value.

 

reduce binary value cause to patch other parts.

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

 Share
Go to topic listing
×
×
  • Create New...