Contribute
Register

Clover Stuck at Root Device uuid is ....

Status
Not open for further replies.
saadzer

saadzer

Joined
Aug 26, 2014
Messages
18
Motherboard
Samsung NP300v5a chipset : intel 6-series
CPU
Intel Core i5 Processor 2410M, 2.30 GHz, 3 MB L3
Graphics
intel graphics HD 3000 / Nvidia GT520MX, 1366x768
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hi I've seen some similar posts on this issue but with no solution, i've installed mavericks successfully with unibeast usb installer on my laptop and it's working fine (i have mac os only on GPT, no dual boot). but the issue is when the installation ends the computer doesn't have any bootloader and i need to use the usb to boot into the mac hardrive.
when i tried installing clover i get the clover bootloader screen but after choosing to boot the mac, it just get stuck on :
root device uuid is "xxx-xxxx-....." and some dots after that .

i've tried removing some Kexts of ATI and AMDRadeon and intelHD4000/5000 which push it a bit further with a lot of dots but still get stuck.

how to get clover boot the mac in the same way the unibeast usb does ?
 
saadzer said:
Hi I've seen some similar posts on this issue but with no solution, i've installed mavericks successfully with unibeast usb installer on my laptop and it's working fine (i have mac os only on GPT, no dual boot). but the issue is when the installation ends the computer doesn't have any bootloader and i need to use the usb to boot into the mac hardrive.
when i tried installing clover i get the clover bootloader screen but after choosing to boot the mac, it just get stuck on :
root device uuid is "xxx-xxxx-....." and some dots after that .

i've tried removing some Kexts of ATI and AMDRadeon and intelHD4000/5000 which push it a bit further with a lot of dots but still get stuck.

how to get clover boot the mac in the same way the unibeast usb does ?
Click to expand...

Make sure you use a valid config.plist.

See here: http://www.tonymacx86.com/hp-probook-mavericks/112383-guide-install-mavericks-clover-bootloader.html

Also, you'll need kernel flags: dart=0 nv_disable=1

No sense in removing Intel HD graphics kexts when that is the only graphics capability you can use.
 
RehabMan said:
No sense in removing Intel HD graphics kexts when that is the only graphics capability you can use.
Click to expand...
yes ! my display was damaged after doing this, i was trying some solutions that i've found and it didn't work , i've done a fresh install now to start all over and i'll try your solution , thank you
 
i've added the boot flags and tried playing around with the config.plist but i'm not sure what to look for ?
i'm still stuck on the same line
 
saadzer said:
i've added the boot flags and tried playing around with the config.plist but i'm not sure what to look for ?
i'm still stuck on the same line
Click to expand...

Post your config.plist
 
RehabMan said:
It is not surprising that config.plist does not work.

For better config.plist files, read carefully at the link provided in post #2.
Click to expand...

So i've been trying some stuff and found out that the Clover drivers 64 were missing from my installation after adding them it passed the part where it says root uuid and everything goes fine until i get the error :
[IOBluetoothHostControllerUSBTransport][configurePM] -- ERROR -- waited 30 seconds and still did not get the commandWakeup() and it get stuck again i'm using the flags "-v dart=0 nv_disable=1" and the same error with "-x" , any help on this ?
 
saadzer said:
So i've been trying some stuff and found out that the Clover drivers 64 were missing from my installation after adding them it passed the part where it says root uuid and everything goes fine until i get the error :
[IOBluetoothHostControllerUSBTransport][configurePM] -- ERROR -- waited 30 seconds and still did not get the commandWakeup() and it get stuck again i'm using the flags "-v dart=0 nv_disable=1" and the same error with "-x" , any help on this ?
Click to expand...

Likely a graphics problem. Make sure you used a config.plist that sets ig-platform-id and injects for Intel appropriate for your hardware.

Also could be lacking FakeSMC.kext. Or other problems.

Point is, the BT error is not the most important. The important messages are those that happen (or don't happen) prior to that.

Read carefully at the link in post #2.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top