I did that, but instead FAT32 I did a Exfat partition and other (11gb) with MacOS Extended Journaled (GUID) for Mojave but when I'm go to do the USB Mojave always says: partition format isn't ok, but if only have one partition all is ok.
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
Thanks
I finish my clone and will for sure try and let you know
For infos about this weird APFS Schemes/Containers
I discovered it recently. At Start I had to install Mojave (with the patcher) on Samsung SSD, my boot disk, but I was wrong I installed it on the data disk! (Macintosh SSD) I erased and recloned the data disc at all, but the created partition recovery was kept I do not know why.
Last edited:
It's weird because this method worked with any OSX USB Installers , maybe is the Exfat even if similar to the FAT32 could be a bit incompatible with that ? Could you try using FAT32 ? Or better try instead to create a GUID USB Drive with two "MacOS Extended Journaled" partitions, one label USBMojave, the other USBOther, then on USBMojave apply the Mojave Patcher procedure, when you completed, erase only the USBOther into FAT.
Possibly use the first USB Partition of your drive for the Mojave Installer.
[doublepost=1541173592][/doublepost]
Yes, it's not simple to get rid of those APFS hidden partitions, you can mount them through diskutil and empty their content, but their ghosts are still there.
Going bonkers in the nut..
Mac Pro 3.1 new SSD, trying to install Mojave, using Disk Utility on the patcher USB formatting disk as APFS.
Then install Mojave, boot to USB, apply patches including APFS patch, reboot.
Get the APFS verbose start up screen, goes to Apple screen and hey presto opens up on my Sierra drive every time.
So remove all other disks in the 3.1 and it will boot to the Mojave disk, put the other disks back in and same thing happens, looks like it is booting to Mojave but then boots to Sierra disk.
Any ideas otherwise going back to rubbing sticks together and eating things raw.
Mac Pro 3.1 new SSD, trying to install Mojave, using Disk Utility on the patcher USB formatting disk as APFS.
Then install Mojave, boot to USB, apply patches including APFS patch, reboot.
Get the APFS verbose start up screen, goes to Apple screen and hey presto opens up on my Sierra drive every time.
So remove all other disks in the 3.1 and it will boot to the Mojave disk, put the other disks back in and same thing happens, looks like it is booting to Mojave but then boots to Sierra disk.
Any ideas otherwise going back to rubbing sticks together and eating things raw.
Have you tried to select from "Startup Disk" prefpane your Mojave "EFI Boot" Volume ?
Otherwise, unplug again all the other disks physically (just for safety), leaving only the Mojave one, power-on then landing on Mojave open Terminal and type:
diskutil list
(locate your Mojave Volume diskXs1)
diskutil apfs updatePreboot diskXs1
Hey Jackluke
I can reach the APFS Recovery now after a lot off lines off "texte" on the blackscreen.
No Bluetooth, no wifi on this Recovery, i had to plug 1 USB mouse and keyboard.
I think this is good enough ?
Thanx you Jackluke, I learned something today
Do i have to do that after each update ?
Hey Jackluke
I can reach the APFS Recovery now after a lot off lines off "texte" on the blackscreen.
No Bluetooth, no wifi on this Recovery, i had to plug 1 USB mouse and keyboard.
I think this is good enough ?
Thanx you Jackluke, I learned something today
I'm glad, anyway if you want to see the apple logo just return editing the com.apple.boot.plist inside your Recovery as you already know and drop the "-v" leaving just this:
<string>root-dmg=file:///0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/BaseSystem.dmg -no_compat_check</string>
From what I read you are on 10.14.2 , while instead to make BT/Wifi working you should enter again inside your APFS Recovery through Finder, then delete the current immutablekernel and use instead the latest dosdude1's /USBMojaveInstaller/System/Library/Prelinkedkernels/prelinkedkernel copying it into your APFS Recovery and from your Recovery folder renaming it into immutablekernel.
I was forgetting, the prelinkedkernel file inside the dosdude1's Installer is locked (I don't know why), but to unlock simply highlight the file and on it press CMD+i (Get Info) and de-select the "locked" checkbox.
Maybe not on any upgrade you have to repeat those steps, I'd do an automatic procedure, but others on this thread putting me off.
Last edited:
Wooo, that's the service !!
Yes i am on 10.14.2 after a great relentlessness and all the help given here
I can't edit (with BBEDIT) the com.apple.boot.plist
i have this :
The document “com.apple.Boot.plist” couldn’t be unlocked because it resides on the locked disk “Recovery”.
Last edited:
Wooo, that's the service !!
Yes i am on 10.14.2 after a great relentlessness and all the help given here
I can't edit (with BBEDIT) the com.apple.boot.plist
i have this :
The document “com.apple.Boot.plist” couldn’t be unlocked because it resides on the locked disk “Recovery”.
copy only the Recovery com.apple.boot.plist file on your desktop, then modify it editing from Desktop, then copy back and replace the one inside your APFS Recovery.
Thanks, sorry for the next question, but my system is toast at the moment so I can't check - can the Patcher program update itself to 1.2.3 that I need for 10.14.1 or do I need to download 1.2.3 directly and install?
I can't do that , when I drag the modified com.apple.boot.plist back into the recovery I have a forbidden icon
[doublepost=1541180523][/doublepost]
You need to download it again from the Dosdude1 Page
Refresh the page if you have some cache in your browser
It seems only a permission issue (on the agenda when using APFS), most probably you have to use DiskUtility's First Aid over your APFS Volume.
Meanwhile try this open Terminal and type then edit and save from there:
sudo open -a TextEdit /Volumes/Recovery/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist
Hi Jackluke. Many thanks for your quick reply. I see you have been helping quite few of us with this problem, much appreciated. As dosdude said, this problem seems to be quite random and it would be great to find the problem with BT and Mojave. My main ssd is working well with 14.0 so I will not update this until I find a solution. I have another ssd that I use for "experimentation" which is presently on 14.1 but with no BT. I have tried your suggestion (IOBluetooth kexts version 6.08) but again without success. My 14.0 is successfully using version 6.07 from HS. I have not used the wifi patch at all. Strangely the Apple Magic Mouse works partly. Left and right buttons ok but no scrolling so even though it says bluetooth unavailable something is happening. I notice this mouse behaviour is also replicated using the usb installer which has the smaller IOBluetooth kexts version 6.09. What I might try is to reinstall Mojave and apply the wifi patch to see what happens. I know this is different to your final advice but I have not used this patch before on my combo card.
sudo open -a TextEdit /Volumes/Recovery/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist
Password:
The file /Volumes/Recovery/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist does not exist.
Weiiiird !
Because when i mount the recovery partition with Mojave cache cleaner for ex i can see it
Maybe there is an issue because i have 2 recovery partitions ?
sudo open -a TextEdit /Volumes/Recovery/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist
Password:
The file /Volumes/Recovery/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist does not exist.
Weiiiird !
Because when i mount the recovery partition with Mojave cache cleaner for ex i can see it
Maybe there is an issue because i have 2 recovery partitions ?
You're right here is adjusted script just copy/paste in your Terminal:
sudo open -a TextEdit /Volumes/"Recovery 1"/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist
I haven't figured out how to do it yet. You have to somehow install using the .dist file that comes with the update package (it's the equivalent to a Distribution in an mpkg, and references the rest of the packages). I'll mess with it this weekend if I have time.
Yes, also dosdude1 explained that, the Bluetooth kext have a strange behavior on different machines, anyway before re-installing try first to use the IOBluetooth*.kext inside the /USBMojaveInstaller/S/L/E/ replacing yours in your /S/L/E/ and see what happens.
wooo ...
sudo open -a TextEdit /Volumes/"Recovery 1"/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist
The file /Volumes/Recovery 1/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/com.apple.Boot.plist does not exist.
That's really strange because i have mount this recovery 1
Do this, launch DiskUtility First Aid a couple of time on your APFS Volume, then reboot, and retry normally.
Same issue.
so that's really weird
NO ! DONE
!No i 'm going for the flag, heuuuuuu no, lol i'm going to get wifi and bluetooth on the recovery
Thx jackluke
Last edited:
Then try this open Mojave Terminal and type:
sudo -s
diskutil mount disk2s3
open /Volumes/Recovery/
then open your "number-letters" (post a picture here of its content here) folder from Finder and replace the com.apple.Boot.plist with the one you edited on your desktop.
YES ! see my message above please
[doublepost=1541184395][/doublepost]Everything is working now (Until the next update ?)
Mojave and the Recovery. (iMac 10,1)
iI just fails to harmonize the interface clear, (because of metal) but hey, it's not really useful and the dark is very good.
What a job,(But I learned a lot)
it really piss off Apple, they do not have enough money? it gets them through all the holes!
Luckily you are here in this forum.
Thank you for your help and a great hat trick for his precious help, his patience and his time, to jackluke and of course to Dosdude1
Last edited: