Clover Package doesn't work on Catalina #6

bpresles · 2019-10-14T22:15:56Z

On Catalina (OS X 10.15), Clover installer can't get read/write access

Of course I've SIP completely enabled (0x0) ;). I didn't try without SIP, but I don't want to have to disable it each time I need to update Clover

esetnik · 2019-10-15T15:24:24Z

I have the same issue

G3NSVRV · 2019-10-16T00:34:42Z

Same here.

g3nsvrv@G3NSVRVs-Mac ~ % sudo mount -u -o rw /Volumes/Install\ macOS\ Catalina 
g3nsvrv@G3NSVRVs-Mac ~ % sudo installer -pkg ./Downloads/Clover_v2.5k_r5096.pkg -target /Volumes/Install\ macOS\ Catalina
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted
installer: Error - Cannot install without ensuring the file system is read-write

oantajames · 2019-10-17T14:51:44Z

Same here.

icastillejogomez · 2019-10-17T17:58:37Z

Same here!!

EricTheRed1 · 2019-10-18T00:47:20Z

Same here

riverLethe9 · 2019-10-18T01:31:57Z

I have the same issue. It does not seem to be version specific.

cnsilvan · 2019-10-18T03:33:07Z

Same here

simmy1232 · 2019-10-18T12:37:33Z

Can install but the system crashes. It's also made my system very slow

vectorsigma72 · 2019-10-19T09:12:39Z

On Catalina (OS X 10.15), Clover installer can't get read/write access

Of course I've SIP completely enabled (0x0) ;). I didn't try without SIP, but I don't want to have to disable it each time I need to update Clover

Hi, what happens if you write your administrative account name and your administrative account password?

vectorsigma72 · 2019-10-19T09:17:29Z

Same here.

g3nsvrv@G3NSVRVs-Mac ~ % sudo mount -u -o rw /Volumes/Install\ macOS\ Catalina 
g3nsvrv@G3NSVRVs-Mac ~ % sudo installer -pkg ./Downloads/Clover_v2.5k_r5096.pkg -target /Volumes/Install\ macOS\ Catalina
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted
installer: Error - Cannot install without ensuring the file system is read-write

Sir you are the cause of the error. "Cannot install without ensuring the file system is read-write" means you did not accepted a pre install action that require you to interact into the GUI directly.

bpresles · 2019-10-19T09:18:17Z

On Catalina (OS X 10.15), Clover installer can't get read/write access

Of course I've SIP completely enabled (0x0) ;). I didn't try without SIP, but I don't want to have to disable it each time I need to update Clover

Hi, what happens if you write your administrative account name and your administrative account password?

It shows the error shown in the screenshot:

https://user-images.githubusercontent.com/220623/66786465-b0ee4100-eee0-11e9-96c2-312c2831f27d.png

Same here.
g3nsvrv@G3NSVRVs-Mac ~ % sudo mount -u -o rw /Volumes/Install\ macOS\ Catalina 
g3nsvrv@G3NSVRVs-Mac ~ % sudo installer -pkg ./Downloads/Clover_v2.5k_r5096.pkg -target /Volumes/Install\ macOS\ Catalina
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted
installer: Error - Cannot install without ensuring the file system is read-write
Sir you are the cause of the error. "Cannot install without ensuring the file system is read-write" means you did not accepted a pre install action that require you to interact into the GUI directly.

No, it's the error that is reported AFTER having entered Administrator credentials.

In a nutshell, the installer is unable to get read/write access even if you enter the appropriate credentials of an Administrator account in the dialog shown in the first screenshot: https://user-images.githubusercontent.com/220623/66786460-adf35080-eee0-11e9-9de0-f2352b0d3dc0.png

vectorsigma72 · 2019-10-19T09:20:21Z

It shows the error shown in the screenshot:

https://user-images.githubusercontent.com/220623/66786465-b0ee4100-eee0-11e9-96c2-312c2831f27d.png

Can you post the install log? Just after the error go to menu->Window->Install log

vectorsigma72 · 2019-10-19T09:21:41Z

On Catalina (OS X 10.15), Clover installer can't get read/write access

Of course I've SIP completely enabled (0x0) ;). I didn't try without SIP, but I don't want to have to disable it each time I need to update Clover

Hi, what happens if you write your administrative account name and your administrative account password?

It shows the error shown in the screenshot:

https://user-images.githubusercontent.com/220623/66786465-b0ee4100-eee0-11e9-96c2-312c2831f27d.png
Same here.
g3nsvrv@G3NSVRVs-Mac ~ % sudo mount -u -o rw /Volumes/Install\ macOS\ Catalina 
g3nsvrv@G3NSVRVs-Mac ~ % sudo installer -pkg ./Downloads/Clover_v2.5k_r5096.pkg -target /Volumes/Install\ macOS\ Catalina
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted
installer: Error - Cannot install without ensuring the file system is read-write
Sir you are the cause of the error. "Cannot install without ensuring the file system is read-write" means you did not accepted a pre install action that require you to interact into the GUI directly.
No, it's the error that is reported AFTER having entered Administrator credentials.

In a nutshell, the installer is unable to get read/write access even if you enter the appropriate credentials of an Administrator account in the dialog shown in the first screenshot: https://user-images.githubusercontent.com/220623/66786460-adf35080-eee0-11e9-9de0-f2352b0d3dc0.png

Sure the install will fail if you run the package from the command line. no way

bpresles · 2019-10-19T09:23:09Z

It shows the error shown in the screenshot:
https://user-images.githubusercontent.com/220623/66786465-b0ee4100-eee0-11e9-96c2-312c2831f27d.png

Can you post the install log? Just after the error go to menu->Window->Install log

So here the log after I entered my administrator account credentials successfully:

Oct 19 11:21:37 iMac Installer[58510]: Package Authoring Error: has an unsupported MIME type: image/data
Oct 19 11:21:37 iMac Installer[58510]: Package Authoring Error: has an unsupported MIME type: image/data
Oct 19 11:21:37 iMac Installer[58510]: Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber
Oct 19 11:21:37 iMac Installer[58510]: Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber
Oct 19 11:21:37 iMac Installer[58510]: Package Authoring Error: has an unsupported MIME type: X-NSObject/NSNumber
Oct 19 11:21:38 iMac Installer[58510]: Could not load resource license: (null)
Oct 19 11:21:58 iMac Installer[58510]: Installation checks failed.
Oct 19 11:21:58 iMac Installer[58510]: Installation check failure. . Installation impossible sans passer le système de fichier en lecture/écriture.
Oct 19 11:22:01 iMac Installer[58510]: Package Authoring Error: Infinite loop between attributes and mixed state aborted.

Translation in english would be:

Oct 19 11:21:58 iMac Installer[58510]: Installation checks failed.
Oct 19 11:21:58 iMac Installer[58510]: Installation check failure. Cannot install without ensuring the file system is read-write

Oh oh, same error than the one provided by the user who tried with command line (with sudo and ensuring the FS was mounted read/write before starting the "sudo installer" command) ! Surprising, isn't it ? ;)

G3NSVRV · 2019-10-19T09:46:53Z

Same here.
g3nsvrv@G3NSVRVs-Mac ~ % sudo mount -u -o rw /Volumes/Install\ macOS\ Catalina 
g3nsvrv@G3NSVRVs-Mac ~ % sudo installer -pkg ./Downloads/Clover_v2.5k_r5096.pkg -target /Volumes/Install\ macOS\ Catalina
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted
installer: Error - Cannot install without ensuring the file system is read-write
Sir you are the cause of the error. "Cannot install without ensuring the file system is read-write" means you did not accepted a pre install action that require you to interact into the GUI directly.

Bruh, Do you think that I didn’t try it through the UI? Right click open, put admin credentials, get same error on EULA screen?

vectorsigma72 · 2019-10-19T09:58:07Z

no surprise if it fails from the command line because there is a check that abort the installation if you did not accept it:

`function checkFileSystemIsWritable()
{
var writable = true;
var cmd = '[[ yes == $(diskutil info / | grep -i 'read-only volume:' | awk '{print $NF}' | tr '[:upper:]' '[:lower:]') ]]'
r = system.run('/bin/bash', '-c', cmd);
system.log('checkFileSystemIsWritable diskutil result = ' + r);

writable = (r != 0);

if (writable) {
  system.log('checkFileSystemIsWritable: file system is writable: Passed');
} else {
  system.log('checkFileSystemIsWritable: root file system is read only, try to make it RW...');
  var cmd2 = '/usr/bin/osascript -e\''
  cmd2 += 'do shell script "mount -uw /'
  cmd2 += '" with prompt '
  cmd2 += '"' + system.localizedString('MakingRootRW') + '"'
  cmd2 += ' with administrator privileges\''
  
  try
  {
    r2 = system.run('/bin/bash', '-c', cmd2);
    writable = (r2 == 0);
    if (writable) {
      system.log('mount -uw / succeded.');
    }
  } catch (e) {
    system.log('mount -uw / returned with error: ' + e);
    writable = false;
  }

  if (writable == false) {
    my.result.message = system.localizedString('GoToFailRootRW');
    my.result.type = 'Fatal';
  }
}

	return writable;
}`

so there is no way you can skip it (i.e. even if the file system was already writable). A failure after giving a correct administrative account name/password can be a bug instead. But the try-catch block should print 'mount -uw / succeded.' when succeded or

'mount -uw / returned with error: ' + e
when it fails...
but there is no trace of them just as you refuse to go ahead or anyway some how the installation-check is refused, if not by you, is refused by the system. So the question is: are you running from an Administrative account? Why the user name did not appear in your screen shot? Did you remove it for your privacy?

vectorsigma72 · 2019-10-19T10:15:08Z

Same here.
g3nsvrv@G3NSVRVs-Mac ~ % sudo mount -u -o rw /Volumes/Install\ macOS\ Catalina 
g3nsvrv@G3NSVRVs-Mac ~ % sudo installer -pkg ./Downloads/Clover_v2.5k_r5096.pkg -target /Volumes/Install\ macOS\ Catalina
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted
installer: Error - Cannot install without ensuring the file system is read-write
Sir you are the cause of the error. "Cannot install without ensuring the file system is read-write" means you did not accepted a pre install action that require you to interact into the GUI directly.
Bruh, Do you think that I didn’t try it through the UI? Right click open, put admin credentials, get same error on EULA screen?

This bothered you? Simply is not possible from the command line, ad it was the only things visible from your message. Any way from your log, this time I can see an comprehensive and illuminating
mount: / failed with 77 (77)t_apfs: volume could not be mounted: Operation not permitted

bpresles · 2019-10-19T11:23:02Z

Why the user name did not appear in your screen shot? Did you remove it for your privacy?

Yes

bpresles · 2019-10-19T11:23:36Z

So the question is: are you running from an Administrative account ?

Yes

vectorsigma72 · 2019-10-19T11:41:26Z

Yes

Ok thanks, that is clear. Usually administrative account show the name while guests or non administrative accounts require to fill both user name and password, why I asked.
Have you notice a line in your log that starts with:
mount: / failed with
as for @G3NSVRV ?

some other questions:
Is that happening on the root file system or on another disk only, like an external one? Happens on both cases or one of the two works?
Is that happening because you are targeting a volume containing a Catalina installer or another Catalina partition running from a Catalina installation?

bpresles · 2019-10-21T19:19:19Z

Yes

Ok thanks, that is clear. Usually administrative account show the name while guests or non administrative accounts require to fill both user name and password, why I asked.
Have you notice a line in your log that starts with:
mount: / failed with
as for @G3NSVRV ?

I gave you the whole log from the Installer, so I guess no ;)

some other questions:
Is that happening on the root file system or on another disk only, like an external one? Happens on both cases or one of the two works?

I'm running the installer from the root filesystem.

Is that happening because you are targeting a volume containing a Catalina installer or another Catalina partition running from a Catalina installation?

I'm trying to install Clover while booted in Catalina from my main SSD (with previous clover). There is no Catalina installation partition or app (nothing in /Applications).

riverLethe9 · 2019-10-22T19:16:54Z

I found this article on Apple's website that may be useful.
About the read-only system volume in macOS Catalina

gavineadie · 2019-11-01T18:42:43Z

Returning to this issue .. the bottom line is that the Clover installer seems dysfunctional when used from a Mac running Catalina in that you cannot reach the "click 'Continue' twice" step of the Clover instructions because the installer aborts before offering that option. I presume, since I don't know the intervals of the process, that the Clover installer always checks if it can write to the root volume, even if the user has no intention of doing that (the more common target of the install being a USB stick), when it finds it can't do that it aborts.

Apple's article, referenced above, points to the reason for the failure, which is nice to know but doesn't lead to any resolution. So, my questions are:

.. is this impacting all Catalina users or only some ?

.. can this 'writable root volume' check be avoided ?
.. if not, is Clover useless in macOS 10.15+ ?
.. if so, is a Clover issue to be addressed ?

My personal solution is to use a pre-Catalina Mac when needing to use the Clover installer to set up USB sticks, hardly an optimal solution.

gavineadie · 2019-11-01T20:06:01Z

I just pulled the Clover repo and as @vectorsigma72 notes, the key to this lies in the Installer "Distribution" script in the function checkFileSystemIsWritable() where a mount -uw / conditions the success of the installation.

Seems like the failure side of that test, instead of making efforts to make root writeable (which can't be successful in Catalina), should work a little harder and look for other writable (bootable?) volumes. Sadly, the last time I messed with Installer scripts was in the Mac System 7 days, so maybe someone with modern Installer skills could do that (or something better).

Papavero3535 · 2019-11-01T22:18:05Z

Same issue here. Any fix in sight??

gavineadie · 2019-11-01T22:26:00Z

A fast, but unsatisfactory, fix would be to set my.result.type to Warning instead of Fatal when the root is not writable .. a one word fix in the Installer script! And, yes, I've tested it!!

Papavero3535 · 2019-11-01T22:32:05Z

A fast, but unsatisfactory, fix would be to set my.result.type to Warning instead of Fatal when the root is not writable .. a one word fix in the Installer script! And, yes, I've tested it!!

Thanks gavineadie - Unfortunately I am not very familiar with how to edit the script. Im a film editor just trying to build a hackintosh haha. Any chance you could either share your new package or share some knowledge? thanks!

gavineadie · 2019-11-01T22:56:29Z

As a stranger to this product, I feel reluctant to step in. I don't recommend patching the file in the installer, if it's even possible, because it'll get changed back on the next upgrade. I built the entire installer from scratch but I'm a programmer and familiar with the tools and processes required. I expect this will be fixed soon in a better way than my patch.

Papavero3535 · 2019-11-01T22:57:59Z

As a stranger to this product, I feel reluctant to step in. I don't recommend patching the file in the installer, if it's even possible, because it'll get changed back on the next upgrade. I built the entire installer from scratch but I'm a programmer and familiar with the tools and processes required. I expect this will be fixed soon in a better way than my patch.

Definitely understand. Appreciate the extra info though! 18 days an no fix though... not exactly holding my breath haha

Erictoby · 2019-11-05T20:01:50Z

Maybe, it's time to move /EFI-Backup folder to somewhere, such as /usr/local/EFI-Backup or ~/EFI-Backup...

juliendonck · 2019-11-05T20:56:26Z

Have the same issue. Any chance for an update?

gavineadie · 2019-11-05T20:57:58Z

This is not an issue of where things are put, it is merely checking that "/" can be mounted writable. If it's not (and it is not in Catalina), the Installer immediately aborts, making the issue of where anything gets put beside the point.

Erictoby · 2019-11-05T21:06:28Z

@gavineadie The purpose of checking "/" is writable is to create /EFI-Backup.

gavineadie · 2019-11-05T21:58:02Z

.. but, if your intention is to create "/Volumes/USB/EFI_Backup", and not touch "/" at all (a not-uncommon usage), the Installer script always aborts before you get to chose the install volume because it prematurely checks the success of mount -uw /.

vectorsigma72 · 2019-11-06T23:16:47Z

@gavineadie The purpose of checking "/" is writable is to create /EFI-Backup.

No. RC Scripts needs that, the Clover preference file needs that as well, and so on. The system knows this and wont start the package because potentially can install in /.
Since the work around was to make / writable before any check on any volume (you cannot do that after having selecting one because is too late) ... the package fails.
The fix is just not using the package: Clover.app is the way to go. Under testing.

mnsrit · 2019-11-26T16:18:30Z

Hmm that's odd. It seems only confined to the latest version of Clover 5099. I was able to install Clover version 5089 on USB stick with Catalina installer in it. I was able to install it but got a black screen through.

douira · 2019-12-12T20:08:37Z

A similar thing happens when I use Clover.app to install to a removable USB device. It says this:

Installation begin..
0:142: 
execution error: My Path = /Applications/Hackintosh/Clover.app/Contents/MacOS/Cloverhelper
Target volume: /Volumes/EFI 1
Error: target volume "/Volumes/EFI 1" is not writable. (1)

Installation failed.

bchernicoff · 2019-12-15T22:58:37Z

I cloned the repo, did a checkout on the 5100 tag, and hard coded checkFileSystemIsWritable to return true. Built the package and ran it from Catalina and was able to install Clover on a USB drive without issue. They need to update the installer to check the permissions on the selected install volume not the root volume of the system running the installer.

bharat-mukheja · 2020-01-04T02:21:31Z

What steps did you follow to built the package? @bchernicoff

bchernicoff · 2020-01-04T20:16:05Z

@bmukheja With the latest xcode and command line tools installed, I just ran the buildme script which will present a menu asking what to build. I believe I chose Build Package but maybe I chose Build All. Sorry, I don't remember exactly.

fallenprogrammr · 2020-01-15T05:49:51Z

Circumvented it by -
Modifying CloverPackage/package/Distribution file
Change functioncheckFileSystemIsWritable in the file to:

function checkFileSystemIsWritable() { var writable = true; return writable; }
Run buildme from command line
Select option 3 (make pkg)
Run newly created package from CloverPackage/sym/

norda72 · 2020-01-26T16:42:01Z

Can Apple have blocked Clover in Catalina? To protect their system?

gavineadie · 2020-01-26T16:59:42Z

No .. this is a feature of Catalina. It's not only Clover that's impacted .. Finder has the same restriction.

gomsoup · 2020-02-10T16:40:04Z

I fixed this problem with this manual

restart your mac
press command + r until appear Apple's logo
go to menubar-utility-terminal
type this command

csrutil disable

profit

rafaelmx · 2020-02-11T19:12:27Z

Gomsoup's solution worked for me! Thanks!

bchernicoff · 2020-02-11T19:38:41Z

Gomsoup's solution worked for me! Thanks!

Yeah but now you've disabled an important security feature of your Mac. I would re-enable now that you've made the USB drive.

roddy20 · 2020-02-11T19:56:49Z

"Of course I've SIP completely enabled (0x0) ;)."

SIP is disabled by Clover as default
CsrActiveConfig
0x3E7

if you enabled SIP you cannot install some packages

bchernicoff · 2020-02-12T21:10:25Z

"Of course I've SIP completely enabled (0x0) ;)."

SIP is disabled by Clover as default
CsrActiveConfig
0x3E7

if you enabled SIP you cannot install some packages

Sure. What's that got to do with the Apple Mac he was disabling SIP on to run the Clover installer?

roddy20 · 2020-02-12T21:17:45Z

Sure. What's that got to do with the Apple Mac he was disabling SIP on to run the Clover installer?

It is not related with Clover and it's development
Mac doesnt require Clover to boot
If you want use your Mac in any unusual and unsupported way you may need to disable SIP
Do you want to change the system and protect it from changes, simultaneously?

roddy20 · 2020-02-12T21:20:09Z

and the second thing, no need to use installer to update Clover
Just copy BOOTx64.efi and/or CLOVERx64.efi

RedxTar · 2020-05-28T12:29:21Z

Im having the same issue on Catalina. Is there a workaround that doesn't involve disabling the SIP just to install it on the USB?

douira · 2020-05-28T13:01:36Z

Not a proper solution, but you can partially disable parts of SIP in the Options in the boot screen without disabling SIP altogether. You only need to enable "Allow Unrestricted FS"

ZinkDifferent · 2020-06-01T07:46:08Z

This still doesn't work. So basically Clover simply can't be installed on Catalina?

guizy67 · 2020-09-09T12:01:21Z

Clover does work with Catalina, just make sure your config.plist is correct.

I was having the same issue until I corrected these values (they were initially blanc)

SergeySlice closed this as completed Nov 21, 2019

jonasrk mentioned this issue May 5, 2020

"Cannot install without ensuring the file system is read-write" when trying to install on a USB drive #158

Closed

pawanzZ referenced this issue in cjtim/SF314-55G-hackintosh Jul 19, 2020

README.md format fixing, sorry for little late.

2d33756

arrmo mentioned this issue Oct 2, 2020

Upgrade, Installation Fails #243

Closed

Clover Package doesn't work on Catalina #6

Clover Package doesn't work on Catalina #6

Comments

bpresles commented Oct 14, 2019

esetnik commented Oct 15, 2019

G3NSVRV commented Oct 16, 2019 • edited

oantajames commented Oct 17, 2019

icastillejogomez commented Oct 17, 2019

EricTheRed1 commented Oct 18, 2019

riverLethe9 commented Oct 18, 2019

cnsilvan commented Oct 18, 2019

simmy1232 commented Oct 18, 2019

vectorsigma72 commented Oct 19, 2019

vectorsigma72 commented Oct 19, 2019

bpresles commented Oct 19, 2019 • edited

vectorsigma72 commented Oct 19, 2019

vectorsigma72 commented Oct 19, 2019

bpresles commented Oct 19, 2019 • edited

G3NSVRV commented Oct 19, 2019

vectorsigma72 commented Oct 19, 2019 • edited

vectorsigma72 commented Oct 19, 2019 • edited

bpresles commented Oct 19, 2019

bpresles commented Oct 19, 2019 • edited

vectorsigma72 commented Oct 19, 2019 • edited

bpresles commented Oct 21, 2019

riverLethe9 commented Oct 22, 2019

gavineadie commented Nov 1, 2019

gavineadie commented Nov 1, 2019

Papavero3535 commented Nov 1, 2019

gavineadie commented Nov 1, 2019

Papavero3535 commented Nov 1, 2019 • edited

gavineadie commented Nov 1, 2019

Papavero3535 commented Nov 1, 2019 • edited

Erictoby commented Nov 5, 2019

juliendonck commented Nov 5, 2019

gavineadie commented Nov 5, 2019

Erictoby commented Nov 5, 2019

gavineadie commented Nov 5, 2019

vectorsigma72 commented Nov 6, 2019 • edited

mnsrit commented Nov 26, 2019

douira commented Dec 12, 2019

bchernicoff commented Dec 15, 2019

bharat-mukheja commented Jan 4, 2020

bchernicoff commented Jan 4, 2020

fallenprogrammr commented Jan 15, 2020

norda72 commented Jan 26, 2020

gavineadie commented Jan 26, 2020

gomsoup commented Feb 10, 2020 • edited

rafaelmx commented Feb 11, 2020

bchernicoff commented Feb 11, 2020

roddy20 commented Feb 11, 2020 • edited

bchernicoff commented Feb 12, 2020

roddy20 commented Feb 12, 2020

roddy20 commented Feb 12, 2020 • edited

RedxTar commented May 28, 2020

douira commented May 28, 2020

ZinkDifferent commented Jun 1, 2020

guizy67 commented Sep 9, 2020

G3NSVRV commented Oct 16, 2019 •

edited

bpresles commented Oct 19, 2019 •

edited

bpresles commented Oct 19, 2019 •

edited

vectorsigma72 commented Oct 19, 2019 •

edited

vectorsigma72 commented Oct 19, 2019 •

edited

bpresles commented Oct 19, 2019 •

edited

vectorsigma72 commented Oct 19, 2019 •

edited

Papavero3535 commented Nov 1, 2019 •

edited

Papavero3535 commented Nov 1, 2019 •

edited

vectorsigma72 commented Nov 6, 2019 •

edited

gomsoup commented Feb 10, 2020 •

edited

roddy20 commented Feb 11, 2020 •

edited

roddy20 commented Feb 12, 2020 •

edited