Jump to content

8 posts in this topic

Recommended Posts

First post, thank you all for any help offered. I am coming from a certain commercialized hackintosh community - after seeing such amazing vanilla installs and reading of the talent here, I decided to have a go at not using such software methods. And I immediately got myself into a predicament 

 

BACKSTORY

I successfully upgraded from Mavericks to Mojave 10.14.2 but decided to start over and do a clean install because my Vega Frontier was not playing OOB even with Lilu & whatevergreen - and there was a lot of 'code junk' Clover barfed at boot from this 'commercialized software'.

 

SUCCESS

I created Mojave USB installer from scratch using the latest Clover, it worked fine, got me to the Mojave install screen.

 

PROBLEM

For reasons unknown to me, I decided for one last ditch effort to see if I could get my already installed Mojave playing nicer - instead of starting over clean. So I installed the latest Clover on my Mojave SSD, (it had a Clover version YEARS ago when I last installed Mavericks) and I replaced the EFI file with the kexts and config of my USB EFI file because I figured, since the USB installer launched, it was all good to go.

 

Now nothing boots after BIOS. Not my Mavericks drive, Mojave SSD, nor my USB Mojave Installer. They all hang right where Clover usually launches. I look at my USB lights and nothing flashes...

 

The only drive I can use is Windows 8.1 (my testing environment) and not from Clover. That's just booting windows up without any HD's plugged in.

 

Is there a way to rescue my predicament? I don't have another Mac computer and CloverConfig only runs on Mac. Is there a way to fix the USB from Windows? Thanks!

 

Specs: Gigabyte GA-X58A-UD5 rev. 2.0, FC BIOS, i7-980x, Vega64 Frontier Edition, Nvidia GTX480, 24 GB 1333 RAM, SSD + various hardrives

Share this post


Link to post
Share on other sites
Advertisement

1. yup. tonymac {censored} install {censored}e in places it shouldnt, it's kinda pathetic really

2. carbon copy a working hack saves a lot of time - including EFI backups, if done the Insanely Mac way you can carbon copy a hack to real mac without any issues btw.

3. copying confing from installer prolly a bad idea

4. mojave needs latest kexts

 

i'd work towards booting installer, you can then work in terminal; diskutil list, diskutil mount /dev/disk3s1 or whatever your EFI is and edit/copy files but without backups makes it a little harder.

 

when it hangs, need more info as to whats on screen

Edited by millusions

Share this post


Link to post
Share on other sites

Hi millusions,

Yes I used CarbonCopy on Mavericks before doing any upgrade. It was bootable.

 

The USB installer was bootable. Mojave was working but then I jacked that.

 

Somehow installing the latest Clover on my working Mojave caused everything to break (I had my Mavericks boot disk mounted when I ran Clover installer. Maybe that messed it up as well).

 

Basically I have the BIOS screen, Clover boot loader starts and there is a _ at the top left of the screen which usually blinks a few times and then the screen changes to grey and the Clover version comes up.

 

Well now it is just _ at the top left of the screen.

 

No blinking on USB or hardrives.

 

BIOS wasn't changed since everything was working...

Share this post


Link to post
Share on other sites

After BIOS says "Verifying DMI Pool Data" Clover gives a .6 /boot command, screen changes and now all I see is the underscore character _ at the top left of the screen.

Share this post


Link to post
Share on other sites

After a full day, here's where I am:

 

1. Created a Clover USB boot loader in windows, still nothing loading.

 

I ask myself, "what has changed since when it was working?" Oh yes, I was running older versions of Clover from 2014 & 2015.

 

So in Windows I created another bootloaded with Clover from 2017, boots perfect.

 

2. Now I created another Mojave installer loading various versions of Clover settling with 4522 to where the USB installer launches and works.

 

Perfect.

 

3. Once in Mojave installer, I now select my SSD which has my broken Mojave loaded and run disk utilities to format it GUID.

 

4. Big trouble in little hackintosh world!

Disk Utilities takes a good 15 min, I know something is wrong. At the end it fails and said something like "could not format, met end of block".

 

I reboot into Mojave installer and there is a 2.1 GB partition (my SSD is 120 GB).

 

I run Terminal diskutil eraseDisk "Sucks" disk1

 

It can't unmount.

 

I see there are now 25 new disks all unnamed.

 

I run diskutil force unmount for each disk successfully but it still won't unmount the main disk. Says PID 0 prohibited (that's the kernal).

 

I take SSD out, try putting it in a USB hardrive tray reader, nothing.

 

Now when I boot, that SSD freezes up my BIOS. I can't even get past the BIOS logo.

 

So when I boot, I unplug it, then boot, start Clover, then plug it in, Clover freezes.

 

Help?

Share this post


Link to post
Share on other sites
On 11/24/2018 at 3:27 AM, millusions said:

1. yup. tonymac {censored} install {censored}e in places it shouldnt, it's kinda pathetic really

2. carbon copy a working hack saves a lot of time - including EFI backups, if done the Insanely Mac way you can carbon copy a hack to real mac without any issues btw.

3. copying confing from installer prolly a bad idea

4. mojave needs latest kexts

 

i'd work towards booting installer, you can then work in terminal; diskutil list, diskutil mount /dev/disk3s1 or whatever your EFI is and edit/copy files but without backups makes it a little harder.

 

when it hangs, need more info as to whats on screen

Really wish I knew about the carbon copy option the first time I migrated from tmac,nitrash.. That basically what I was asking or trying to do the first time I came to this site a few years ago. even though with no apple OS in sight they were my only option to get to the Appstore to get my copy of OS X, and some other files from clover that could help my vanilla install. Then create a new vanilla usb install. I did notice on ***ZONE they consider Mojave they call it a "special" install now, lol, and at the bottom it says ni**** Mojave, like wow.  

 

Well once I get my vanilla install working I know to make a carbon copy incase something happens in the future I can use that to restore!!

 

I do have one question about perhaps migrating the EFI folder and files from Tmacs software. I want to make sure I'm taking the correct cautions, and, I am going to redownload the kexts and stuff from insanely Mac/links that way I don't have any traces of his hardware on my vanilla install. could I reuse his kexts? are redownload fresh ones from here that way incase some kexts might have backdoors coded into the kexts? call me paranoid, but I feel safer getting files from insanely Mac for my vanilla install. Only used his software to get into the App Store and download my OS and make a vanilla install, and it would be easy to copy the working EFI from his software but I'm scared his kexts are modified and again I trust kexts from here more.

 

I know this is a sorta old post, maybe I should repost this as a separate question, let me know, thanks for any help.

57121456333__7FDAD613-8224-4A5D-A4A4-6DA8FD133760.jpeg

Edited by DiddyKong

Share this post


Link to post
Share on other sites
On 11/25/2018 at 8:08 AM, Mattbatt said:

After a full day, here's where I am:

 

1. Created a Clover USB boot loader in windows, still nothing loading.

 

I ask myself, "what has changed since when it was working?" Oh yes, I was running older versions of Clover from 2014 & 2015.

 

So in Windows I created another bootloaded with Clover from 2017, boots perfect.

 

2. Now I created another Mojave installer loading various versions of Clover settling with 4522 to where the USB installer launches and works.

 

Perfect.

 

3. Once in Mojave installer, I now select my SSD which has my broken Mojave loaded and run disk utilities to format it GUID.

 

4. Big trouble in little hackintosh world!

Disk Utilities takes a good 15 min, I know something is wrong. At the end it fails and said something like "could not format, met end of block".

 

I reboot into Mojave installer and there is a 2.1 GB partition (my SSD is 120 GB).

 

I run Terminal diskutil eraseDisk "Sucks" disk1

 

It can't unmount.

 

I see there are now 25 new disks all unnamed.

 

I run diskutil force unmount for each disk successfully but it still won't unmount the main disk. Says PID 0 prohibited (that's the kernal).

 

I take SSD out, try putting it in a USB hardrive tray reader, nothing.

 

Now when I boot, that SSD freezes up my BIOS. I can't even get past the BIOS logo.

 

So when I boot, I unplug it, then boot, start Clover, then plug it in, Clover freezes.

 

Help?

Thank you, your post helped me so much !

Edited by Boreithen

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MaLd0n
      ---INSTALLATION TUTORIAL---
       
      ---Original Post---
      https://olarila.com/forum/viewtopic.php?f=45&t=9172
       
      ---USB---
      https://pikeralpha.wordpress.com/2016/07/13/simple-skylake-usb-fix-no-kexts-required/
       
      ---CLOVER FOLDER---
       
      CLOVER.zip
       
       
      --MOBO
      GigaByte Z390 M Gaming



      --PROCESSOR
      Intel Core i9-9900K


      --COOLER
      CoolerMaster MasterLiquid ML120R RGB


      --MEMORY
      Corsair Dominator Platinum 16GB (2 x 8GB)


      --GPU
      Sapphiretech Radeon RX 590 8 GB GDDR5


       
      --SSD
      Samsung 970 EVO NVMe M2 Flash Drive


      --POWER SUPPLY
      EVGA 750 N1, 750W


      --WIRELESS
      TP-Link Archer T9E


      --BLUETOOTH
      Orico BTA-403


      --CASE
      Thermaltake View 21 Tempered Glass Edition


      --DSDT Patches--
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM / REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES  
      --SCREENSHOTS--





























      --BruceX--
       
      --USB-C-- test with SanDisk Ultra USB-STICK 128gb


       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By Pericles
      I've been trying to boot MacOS Mojave (10.14.4) after installation on a system I've built.
       
      I was able to successfully install Mojave through my USB, it seemed like the installer recognised my gpu and was working with it in the installation screen as it looked like it was outputting video at 4k resolution. When the computer restarted I then booted into the "Preboot" option on clover twice (the first time I tried the progress bar got to a certain point and then the system restarted) and on the second attempt the progress bar filled up completelly and the mac installer counted down to a restart (which I took as meaning that it had successfully finished the installer). After restarting however I tried to boot into MacOS from the SSD I installed it on, the apple logo showed up with a progress bar that filled up completelly before the screen turned black, then grey with a cursor over the grey screen. Also, it's probably worth noting that the GPU's fans continue to spin from turning the system on, up to the point where the screen turns grey after which they stop spinning.
       
      My system specs are as follows:
      CPU: i5 3470
      GPU: RX 570
      RAM: 16GB DDR3 1600MHz 
      MB: Asrock B75m r2
      SSD: Samsung 850 Evo 250gb
      WiFi/BT: Fenvi FV-T919 PCIE Card
       
      I am thinking that it's probably a gpu related issue as everything about the installation process has gone pretty smoothly up to the point where it's displaying a grey screen at bootup (and not going further). I have attached a photo of the output from rebooting with the verbose bootflag (it's missing one line at the bottom "busy timeout[1], (240s): 'AppleACPICPU'"), after the verbose output stays on the screen for a few minutes the screen then turns grey with the cursor and hangs there.

    • By thiagomenini
      Hello everybody,
      I'm from Brazil, if someone wants to write in portuguese, i will understand too. But english is fine.
       
      Days ago I installed the High Sierra, using the image (HighSierraAMD V2 UEFI.dmg). I have an FX8320e, the Asus M5A78L-M / USB3 mobo, GTX 750 and 12GB of RAM.
       
      Well, I build Hackintosh to run audio programs. Everything is working except the USB audio card on the card. But I read that some gyus updates to 10.13.4 or higher and it work.
      But I have some problem with startup and shutdown. I had installed the Clover in different ways, but it did not appear at startup. If I do not use the pen drive to boot, I do not have access to the system.
       
      I've tried different solutions. I formatted the EFI partition using the Terminal and reinstalled the Clover, but it also did not work.
       
      The other problem is the shutdown. The system goes off, but the fans and the mobo remains on. I need to manually press the on/off button to turn off the computer. I had used the Clover Configurations App to set the flag (shutdonw fix) but it not work too. I think this might be related to the boot problem.
       
      Thanks for any help!
×