Jump to content

813 posts in this topic

Recommended Posts

2 minutes ago, valeryimm said:

 

I don’t get the idea how it works. I got clover r.4972 and Make my disk readwriting. I first try to run your program and after that clover,  but didn’t see the option “Install anyway”.

Does this program should modify Clover bootloader? How it knows which disk to make readwritable?

And how to make Gatekeeper disabled?

 

Strange its work here without issue

Share this post


Link to post
Share on other sites
Advertisement
4 minutes ago, valeryimm said:

And how to make Gatekeeper disabled?

sudo spctl --master-disable
// also try with `sudo mount -uw /` before running Clover package

 

Share this post


Link to post
Share on other sites
6 minutes ago, chris1111 said:

Strange its work here without issue

Does this program makes all hard disks readable, or it modifies Clover bootloader and then Clover makes disk readable during the boot?

 

My Clover boots from USB and I was able to do full installaton of Catalina.

But during the first boot of Catalina it stuck.

Share this post


Link to post
Share on other sites

I don’t understand if the disk is not readable, how clover managed to install Catalina on it with several reboots?

And finally, after installation was finished, and it start booting the new installation, it stuck, because the disk not readable anymore.

I have 1Gb hard disk divided in two halves. Mojave installed on 1 half and Catalina is on the other.

From Mojave I can read Catalina disk.

Any suggestions?

Edited by valeryimm

Share this post


Link to post
Share on other sites
11 hours ago, nytr0 said:

Thegn, 

Run this command before using Clover package

double click on command and now you will have an option "Install anyway"

 

Gatekeeper-RW-SSD.zip

 

Thank you for your help, nytr0! I will test this! :)

 

Cheers,

Edited by Thegn

Share this post


Link to post
Share on other sites

Is there any solutuion to booting?

I have 1Gb HDD, 2 partitions. One partition with Mojave installed, the other with Catalina b2.

The problem is that I cannot boot into Catalina.

 I reinstalled Catalina twice. Installation went smoothly with couple of reboots.

As soon as installation is finished and first boot started it always stucks.

I removed all kexts from Clover r.4972, except of FakeSMC kext.

When I boot into Mojave I can access Catalina drive.

I am on skylake I7-6520U, Intel HD540, HP Envy.

Can anyone check screen photo?

7FF9822A-AA63-4770-B135-7A3F28AC44E7.jpeg

Edited by valeryimm

Share this post


Link to post
Share on other sites

I used KernelToPatch thing to prevent them showing on screen, to get clear picture of KP.

I will delete it, to get full info.

Share this post


Link to post
Share on other sites
1 hour ago, valeryimm said:

I used KernelToPatch thing to prevent them showing on screen, to get clear picture of KP.

I will delete it, to get full info.

There is no KP on screenshot. All is good.

Share this post


Link to post
Share on other sites
2 hours ago, Slice said:

There is no KP on screenshot. All is good.

That's what I also suspect there's no KP.

It is something else. I also wonder, why it shows "Got boot device... Device is not readable". Because I can read it from Mojave. Maybe FakeSMC kext not loading? I come home soon and I will check kext loading.

 

 

Share this post


Link to post
Share on other sites
1 hour ago, valeryimm said:

That's what I also suspect there's no KP.

It is something else. I also wonder, why it shows "Got boot device... Device is not readable". Because I can read it from Mojave. Maybe FakeSMC kext not loading? I come home soon and I will check kext loading.

 

 

 

I think your problem is your Clover installation.  You must be missing drivers, most likely apfs, like @bronxteck said.  The OS can detect the HDD but can't read it.  If you are booting via UEFI, make sure your drivers are in drivers64UEFI.  If you are not booting via UEFI, start doing so - you have no reason to boot via BIOS.

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

  • Similar Content

    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.15 installation on MBR HFS+ partition.
       
      Please read Readme-10.15.pdf first.
       
      How to finish the Catalina installation.
      1. Use EasyMBR-Installer1015 to make USB Catalina Installer.
      2. Boot to USB Catalina Installer, open Utilities -> Disk Utility, format as MBR HFS+. 
          Install Catalina to blank MBR HFS+ "Target" partition.
      3. Boot to USB Catalina Installer, open Utilities -> Terminal, run the script command:
          copytempdata
      4. Boot to "Target" MBR HFS+ partition on single user mode (-s), run the script command:
          hfsupdatecache
      5. Reboot to "Target" MBR HFS+ partition, setup user name and login, finish the installation.
       
      Also, you need to setup Clover as BooterConfig=0x28, CsrActiveConfig=0x67
       
      ----------------------------------------------------------------------------------------------
      List of known issues:
      1. iCloud Drive need APFS to work.
      2. Some app-pkg-installers can't install to HFS+, but install to APFS fine.
      ----------------------------------------------------------------------------------------------
       
      What is this patched OSInstaller doing?
      1. Pass the MBR check, allow macOS 10.15 installation on MBR partition.
      2. Pass the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Pass auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.15.
      4. This MBR-Manual-Method will never convert to APFS, and will always install as HFS+ partition.
      5. This MBR-Manual-Method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR HFS+ and GUID HFS+, will never convert the partition format.
          We can manually format as MBR HFS+ or GPT HFS+ on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13, 10.14, 10.15 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, 10.14, 10.15 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          End of MBR and HFS+, there is no more MBR HFS+ patch available for 10.15 native OSInstaller.

      How to make 10.15 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-Installer1015 to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q4. How to patch to work with CPU SSE4.1 only for Mojave, Catalina?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       

       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_fullapp to download the full installer app via swscan.apple.com.
       

       
    • By PippoX0
      Working in Progress
       
      I want  that my Catalina  runs smooth
       
      I run Catalina beta on MBr HFS+ (only one partition)
       
      So what we can do ?
       
      0. I have gained my Intel HD3000 QE/CI working
         - i have used Intel HD3000 High Sierra Kexts
          Done
       
      1. Reduce size
        -  I have used monolingual and I have deleted all unwanted languages
        - i have deleted unwanted Speech voices
        - i have delete unwanted Fonts ( Japanese , Chinese, Emoji ...) 
        - i have delete unwanted Templates ( again speech voices)
        My Cat OS have been shrinked  from 16 Gb to 9,96 Gb
        Done
       
      2. Disable all unwanted Deamons and Agents
        -  I'm looking for disable all Debug deamons or Agents running which are slowing my Os
         Still seeking ....
       
      What's else ?
       
       
       
       
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
×