Bascially I’m trying to find out how I can access recovery mode as it dosent work anymore due to me using the patcher to upgrade on an unsupported mac.
the usb flash drive had the installer on it and macOS was installed on the Mac hard drive.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
the usb flash drive had the installer on it and macOS was installed on the Mac hard drive.
... and basically, my question to you was: why do you need recovery mode? Not trying to be awkward here - if you boot from the patched installer, it has Disk Utility and Terminal. You're not going to use recovery mode to re-install your system. If you could explain what you think you may need to do from recovery mode, then maybe all will become clear.
I need to do this which can only been done within recovery mode
[automerge]1582298839[/automerge]
It‘a bascially to help improve CPU usage but requires a custom SPI that can not be done from terminal when logged on.
and I obviously can’t access recovery mode to do it
Can't you execute that command from Terminal when booted from your patched installer? I'm no expert here, so others might chime in, but I thought SIP wasn't related to your drive but to the hardware. It may be stored in NVRAM - not sure.
My other question would be, is it OK to enable SIP on an unsupported machine?
No because the actions taken in terminal on the usb recovery mode wouldn’t effect the Mac itself that runs on the Hard drive.
also thier is very little risk in doing it on an unsupported machine
If you still haven't catch on to what the mrploppy is saying:
SIP MUST REMAIN DISABLED AT ALL TIMES WHILE RUNNING THE UNSUPPORTED SYSTEM.
P.S. You can disable SIP from the Recovery mode of Mojave patcher, the functionality of the recovery mode is identical to the native recovery(or even better).
I'm not convinced you're correct. That would suggest the SIP setting is stored on the drive - your USB drive in this case. I don't think that's true. If I'm wrong, someone will be along in a bit to correct me.
Anyway, why don't you try it by booting from your USB drive and running the csrutil commands. Like I said earlier though, not sure you should be enabling SIP on an unsupported machine. @dosdude1's very own words (albeit for Catalina) say this:
Because system files are patched, and extra, unsigned kexts are being installed, SIP must remain disabled at all times when running a patched copy of macOS. Having SIP enabled will cause the system to simply stop booting, or have functionality issues. Catalina Patcher includes an implementation that ensures SIP is always disabled, regardless of what the user sets in NVRAM.
If you forget about the SIP, for future purposes how would I be able to access the Mac if I lost all my files or had to do something crucial in recovery mode which meant whether I could use the Mac or not without erasing the hardrive?
Well, first of all, I would create a bootable backup of your installation. You do have a backup somewhere, yes? I do this with Carbon Copy Cloner to an external drive. I tend to do this after every system update, and periodically after security updates. And I did it before installing a new SSD as my internal drive. I'm not anal about backups i.e. I don't do daily backups and don't use Time Machine, but I at least have a system that I could go back to that was only a few months old. In reality, most of my stuff is either gmail'd, stored on iCloud, or periodically cloned as a backup. Not sure if that answers your question. If my internal drive died, I'd just install a new one and clone from my external drive onto the empty new drive.
That last sentence made me think about the SIP question. If you had a brand new empty internal hard drive on which you wanted to install Mojave using the patched installer on a USB drive, how do you think you'd disable SIP, or set any SIP status, before installation? There'd be no recovery partition on the empty drive to boot from. That kinda defeats the argument that the SIP status is stored on the drive (I think).
But does the backup contain programs as well as the files. I’m a music creator so if I loose a file I’m in a trouble and without recovery mode it opens a big risk to me not being able to recover my Mac if anything should happen to it.
is thier any solution to this issue they dosent invole An external drive and can be done straight on the Mac?
If your Mojave installation is in APFS , then this early script that I wrote should still work, allowing CMD+R , a standard recovery environment and maybe also the Wifi function into Recovery to open for example "Get Help Online" aka Safari browser from osx recovery mode.
Try this: Mojave APFS Recovery fix script
There is an old saying that there are two types of hard drives, those that have failed and those that are about to fail. What happens when the drive that is about to fail, that you have all your files on, does fail?
The Mac Recovery Mode is just one piece in a backup strategy and will not be of any use in such a situation.
I don't have such criticality but I run the following:
- Time Machine Backups: To recover individual files whenever needed going back several months. Also a potential system recovery point if needed
- A bootable clone on a drive called "Daily" using Carbon Copy Cloner that runs twice a day
- Another bootable clone that runs once a week on a drive called "Weekly"
Sorry, I was a little late answering, so others have already given you some input. The bottom line is: you need to back up.
To answer your specific question, I use Carbon Copy Cloner (others are available) to clone the whole of my internal drive to an external USB drive (actually, to a part of an external drive - it's bigger than my internal). It makes a bootable copy - everything - system, applications, user directories - everything. I could boot from the clone if I wanted. I could copy the clone back to the internal drive (using CCC) if I wanted. It's a sledgehammer approach to backups though. If your files are really critical to you, then you really should address the backup issue: how often you want to back up, how would you feel if you lost a day/week/month of work, etc. And if they are seriously critical to you, then as someone else said, you should keep a backup offsite as well - in case your house/office burns down. The only issue I've had with cloning a drive is sometimes an application will need "re-activating" - this happened to me with Office because I guess it realised that it was now on a different drive to when it was initially installed.
The SIP configuration is stored in NVRAM and what csrutil does is the same from all installer environments: it just changes that NVRAM variable. And it affects the whole machine.
Thanks. I thought so but wasn't entirely sure. One thing that had passed me by was the introduction of the SIP Disabler patch (and the fact that disabling SIP is not mentioned in the installation instructions anymore). So, assuming @MacMusic01, has the patch installed, his attempt to "csrutil enable" isn't going to achieve anything anyway. Is that correct?
It’s works now! Thanks so much
Attachments
I could be agree with others on many points about that APFS Recovery is almost unuseful but consider these cases when a macbook has only two available usb ports:
1) Trackpad broken or someone might prefer to use an external usb mouse (ok probably you have a bluetooth one then maybe you want to plug an additional external usb devices for files recoveries or an usb time machine backup)
2) For sure the other spare usb port is almost always needed for an external usb backup drive.
From unsupported Recovery you can't re-install an unsupported macOS, of course.
I understand sometimes if an internal drive fails, probably also internal recovery results damaged, but in other situation maybe since on different partition the recovery might work also over a failed drive.
If you want to attempt an effective "csrutil enable --without kext" you should first remove this kext and rebuild a kextcache without it:
/Library/Extensions/SIPDisabler.kext
Anyway on unsupported machine enabling SIP, even if only "--without kext" after a post-frameworks patching might work, is not advisable.
Last edited:
With that kext, SIP is turned off only on the volume with it installed. Running csrutil enable/disable will only affect volumes without that kext.
After a PRAM reset and maybe also after a major system upgrade (example from HighSierra to Mojave), SIP turns enabled again, but keeping @parrotgeek1 SIPManager.kext is equivalent to "csrutil disable", allowing any patches on a target macos volume to work properly.
Another example with SIP enabled you couldn't apply my Mojave apfs recovery script.
Last edited:
So I disable it, how do I do it?
Is thier a script I can use for it?
If on your Mojave Volume /Library/Extensions/ is present this SIPManager.kext , then it's already disabled.
Last edited:
The kext name is SIPManager.kext I made a typo writing SIPDisabler.kext.
Anyway boot from CMD+R or usb installer, open a recovery terminal and type:
csrutil disableOk worked thanks
[automerge]1582461166[/automerge]
Would it be ok to do —without kext
[automerge]1582461263[/automerge]
Whenever I try to enter recovery mode now, it turns off and reboots to normal log in
[automerge]1582461950[/automerge]
So after a few reboot it works fine.
but when trying to disable the SIP this comes up in terminal, please can someone help me with this
Attachments
Last edited: