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
[doublepost=1551627926][/doublepost]Reboot with your macOS Mojave patcher and reinstall Mojave you won’t lose anything
when i try reinstall and select destination disk, osx say "not enought disk space available"!!!!! and the partitition is disabled
i dont mount macintosh HD. i dont reinstall
Last edited:
when i try reinstall and select destination disk, osx say "not enought disk space available"!!!!! and the partitition is disabled
i dont mount macintosh HD. i dont reinstall
So I assume that you were running your system drive far too close to capacity and ran out of space during the system update. If that is correct, your best approach, assuming that you don't have another bootable external drive, would be to boot from the Mojave patcher USB key, launch the Terminal application and find some large files that you can delete with the 'rm' command. Once you have at least 16 GB free on the system drive, reinstall Mojave and apply the patches again.
diskutil mount disk1s1
cd /Volumes/MacBook\ HD
cd /private/var/vm/
rm sleepimage
You can reinstall only chosing APFS, APFS and Bootcamp are not good friends.
Volume on disk1s1 failed to mount; it appears to be an APFS Volume which might be locked
Try "diskutil apfs unlockVolume"
Right, infact you have around 50 gb free on the APFS, so try this:
diskutil apfs unlockVolume /dev/disk1s1
Unlocking any cryptographic user on APFS Volume disk1s1
Error unlocking APFS Volume: The given APFS Volume is not encrypted (-69593)
[doublepost=1551636405][/doublepost]Container disk1 4581CB29-3CAD-4278-9D70-3C4477F40192
====================================================
APFS Container Reference: disk1
Size (Capacity Ceiling): 159800864768 B (159.8 GB)
Capacity In Use By Volumes: 113065025536 B (113.1 GB) (70.8% used)
Capacity Not Allocated: 46735839232 B (46.7 GB) (29.2% free)
|
+-< Physical Store disk0s2 CC203607-4AA6-4CA1-ACC3-45EE48A0921D
| -----------------------------------------------------------
| APFS Physical Store Disk: disk0s2
| Size: 159800864768 B (159.8 GB)
|
+-> Volume disk1s1 412115E6-0E05-33BE-91CD-12B8C040181B
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s1 (No specific role)
| Name: MacBook HD (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 107032932352 B (107.0 GB)
| FileVault: No
|
+-> Volume disk1s2 213020E5-D1A6-4F70-9704-BBBD251D4756
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s2 (Preboot)
| Name: Preboot (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 23896064 B (23.9 MB)
| FileVault: No
|
+-> Volume disk1s3 2A7623CE-A440-45C3-B266-FF1C3CBCA5F9
| ---------------------------------------------------
| APFS Volume Disk (Role): disk1s3 (Recovery)
| Name: Recovery (Case-insensitive)
| Mount Point: Not Mounted
| Capacity Consumed: 509485056 B (509.5 MB)
| FileVault: No
|
+-> Volume disk1s4 DDFF8EE6-B75F-4C90-833D-986E96E50AB4
---------------------------------------------------
APFS Volume Disk (Role): disk1s4 (VM)
Name: VM (Case-insensitive)
Mount Point: Not Mounted
Capacity Consumed: 5368729600 B (5.4 GB)
FileVault: No
FileVault should be disabled first before attempt a major system ugpgrade especially on unsupported mac.
Anyway you maybe have a corrupted APFS, try a couple of DiskUtility First Aid, then unlock again the volume.
-bash-3.2# fsck_apfs /dev/disk1s1
** Checking the container superblock.
** Checking the EFI jumpstart record.
** Checking the space manager.
** Checking the space manager free queue trees.
** Checking the object map.
** Checking volume.
** Checking the APFS volume superblock.
** The volume MacBook HD was formatted by hfs_convert (748.67.14) and last modified by apfs_kext (945.200.129).
** Checking the object map.
error: btn:3: invalid key order (1) oid 547121 / oxid 0
Object map is invalid.
** The volume /dev/disk1s1 could not be verified completely.
Typical corruption after installing a major unsupported system upgrade over an encrypted supported system.
I dont know much about fixing that, anyway my last advise would be booting from the APFS Volume holding CMD+S and try fsck from there:
/sbin/fsck -fy
/sbin/mount -uw /
New problem...
I uninstalled my previous install, completely erased and reformatted the ssd from the root drive, not the volume. No more grub boot loader, I will have to figure out what happened there, but I digress...
Everything was working fine until recently, as in the last few hours I am getting weird graphical glitches which for some reason the screen capture doesn't capture... I wish I knew how to describe them but I don't quite know the words.
edit: I took a picture with my iPhone.
edit 2: I found the culprit, sort of. It only happens when f.lux is active and my screen starts shifting color to the warmer end of the spectrum. Is this indicative of a failing piece of hardware?
I uninstalled my previous install, completely erased and reformatted the ssd from the root drive, not the volume. No more grub boot loader, I will have to figure out what happened there, but I digress...
Everything was working fine until recently, as in the last few hours I am getting weird graphical glitches which for some reason the screen capture doesn't capture... I wish I knew how to describe them but I don't quite know the words.
edit: I took a picture with my iPhone.
edit 2: I found the culprit, sort of. It only happens when f.lux is active and my screen starts shifting color to the warmer end of the spectrum. Is this indicative of a failing piece of hardware?
Attachments
Last edited:
Just finished implementing a new Patch Updater feature! Now, Patch Updater has the ability to check the integrity of patches installed on your machine, allowing it to detect cases where system patches get overwritten (such as during a software update, etc.) When such a case occurs, it will alert you and prompt you to re-install the affected patches automatically. The new Patch Updater version is, of course, available as an update through previous Patch Updater versions. Also, both this new patch integrity check feature, and automatic update checking, can be disabled via the new System Preferences item.
Last edited:
Thank you works like a charm is there a possibility implementing it in the Mojave patcher. I have a feeling after the post install patches they get overwritten during the reboot process
Mine is find Backlight Control Patch and I re-install it but now I am getting a kernel panic machine never boot. Loading bar coming and it is loading 3/4 and restart again. I tried re-patch with the macOS Post Install rebuild cache but it doesn't help. Always the same thing happening.
I think Re-Install patches break the system and start giving a kernel panic. And never boot.
Please help Is there any way to boot again without re-install the Mac OS?
Last edited:
Now if the issue with software updates that touch the recovery partition and are thus failing on patched Mojave for an unsupported machine could be sorted out.
I am wondering what is the potential issue of the recovery partition can be? At the moment Mojave and High Sierra APFS Recovery partitions are working great.
[doublepost=1551707166][/doublepost]
Have you tried selecting EFI Boot in the boot menu?
Every minor and major system update rebuild a new prelinkedkernel (also for Recovery) and restrict the hardware compatibility check, it's hard to interfere into those processes dynamically with a script I guess, or I don't know how to.
But essentially the APFS Recovery needs first dodging compatibility check (no_compat_check argument in nvram) and then using a patched prelinkedkernel (immutablekernel that is the same thing) with legacy USB kext pre-built inside, otherwise you can enter with CMD+R but without input devices (BT/USB keyboard/mouse) responsively so unusable, same talk applies to CMD+S single user mode. Another fact is that with APFS disks UUID are random generated, so only a manual Recovery patching is possible at the moment.
Yes, but it didn't help. Never boot, always loop. Something wrong on Backlight Control Patch just this patch make a problem on my iMac 9,1. I can reinstall Night Shift Patch and boot without any problem but when I re-install backlight control patch system never boot and start looping.
@jackluke
Is it possible to restore from time machine? I tried but it never worked.
As far I know Mojave's TimeMachine doesn't work with a non-native APFS firmware machine (only mac produced after early 2010 support APFS natively), so another chance would be re-installing the latest 10.14.3 from an USB Installer over your current drive, you'd not lose your personal datas, because it's a re-installing or refresh installation, not a clean install.
iMac 7,1 that also bricked when updating using patcher and showing that 2 plist were not matching. After they were updated and not restarted, logging in as one of my profiles before rebooting would kick you back out to the login. Rebooting and repatching also hangs with a fresh stick, reinstalling osx fails. Disk first aid shows as complete, but the log shows:
error: cib :invalid o_oid (0x0)
error: failed to read spaceman cib 0x6cfd
Tried to wipe the drive and install, "running bless on boot files failed"
error: cib :invalid o_oid (0x0)
error: failed to read spaceman cib 0x6cfd
Tried to wipe the drive and install, "running bless on boot files failed"
Last edited:
Dosdude, I want to express my thankfulness for your work.
The whole mac community is thankful for your work!
As soon as I can, I'll send you some monetary recognition.
Om shanti, shanti, shanti.