Apple created the update and they wouldn't have done that if they didn't think it was necessary. I never misled anyone about the fact that it was a beta. It even said so in the screenshot itself. You know it and anybody reading this thread knows it.
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.
How to update the recovery partition
- Thread starter tywebb13
- Start date
- Sort by reaction score
Apple created the update and they wouldn't have done that if they didn't think it was necessary. I never misled anyone about the fact that it was a beta. It even said so in the screenshot itself. You know it and anybody reading this thread knows it.
I completely agree if you are on the beta, but that is not what this thread is about and that is not what you said.
Okay, whatever you say.
There is something about this stuff which I haven't said yet. But I'm going to say it now.
I said before that the 10.12.1 delta system update won't update the recovery partition. But what should also be said is that it CAN'T update the recovery partition.
That is why other methods are needed in the first place. And there are 4:
1. My preferred method as per the first post: run dmtest from lion recovery hd update via recovery.sh as applied to the 10.12.1. (This is perfectly legal in contrast to method 4)
2. Or run the full installer for 10.12.1 - despite the fact you may end up with downgraded apps and have to then update them again.
3. Or if you are a developer, get the Sierra Recovery HD Update via the mac app store. This however is not available to the public.
4. Or use an illegal app which stole dmtest from apple and used it in their app.
And it works for 10.12.2 now too.
Here is an updated 10.12.2 recovery partition:
![recovery 10.12.2.png]( "recovery 10.12.2.png")
I used the lion method for this one.
Here is an updated 10.12.2 recovery partition:
I used the lion method for this one.
If you want a clean install it's probably quicker to do it via a bootable usb instead of the recovery partition since the whole installer is already on the bootable usb, whereas if you want to install via the recovery partition, it will have to redownload the installer - taking more time. I made a thread for making a bootable usb here if you need it: https://forums.macrumors.com/thread...ler-for-sierra-gm-and-public-release.1992501/
Here are apple's instructions on how to use macos recovery: https://support.apple.com/en-au/HT201314
Last edited:
Thanks. updated the recovery and then did a clean install on macbook 12. No issues or glitches and it flies!
In the end I get this error:
<--[Local dmAsyncFinishedForDisk:mainError:detailError:dictionary:]
Creating recovery partition: finished
Cleaning up
"disk3" unmounted.
"disk3" ejected.
"disk4" unmounted.
"disk4" ejected.
touch: /Library/Preferences/SystemConfiguration/com.apple.Boot.plist: Operation not permitted
Should we continue here? 2 copying //System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey to /Volumes/Recovery HD/com.apple.boot.S/System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey: No such file or directory
Should we continue here? 2 copying //System/Library/Caches/com.apple.corestorage/EFILoginLocalizations to /Volumes/Recovery HD/com.apple.boot.S/System/Library/Caches/com.apple.corestorage/EFILoginLocalizations: No such file or directory
[doublepost=1486026388][/doublepost]
How can you see that drive who is in the picture? When I'm holding down the option key at boot up I only see my hard drive MacHD
Last edited:
Don't worry about most of the stuff that gets displayed in terminal during the process.
The only important bit is "Creating recovery partition: finished" anyway.
If you see that somewhere it definitely worked.
If you can't see the recovery partition in the startup manager it is because you have a core storage volume which prevents the recovery partition from showing up there.
For many people that won't matter. The recovery partition is still there and can be accessed by holding down cmd r whilst booting up.
On the other hand if you need the recovery partition to show up in the startup manager you can revert the core storage as follows:
Run these 2 commands in terminal.
diskutil cs list
and then
diskutil coreStorage revert lvUUID
where lvUUID is the last lvUUID reported by the previous Terminal command.
Then restart for everything to get back to normal after you have run these commands in Terminal.
Booting to the Startup Manager with option key will then show the recovery partition.
The only important bit is "Creating recovery partition: finished" anyway.
If you see that somewhere it definitely worked.
If you can't see the recovery partition in the startup manager it is because you have a core storage volume which prevents the recovery partition from showing up there.
For many people that won't matter. The recovery partition is still there and can be accessed by holding down cmd r whilst booting up.
On the other hand if you need the recovery partition to show up in the startup manager you can revert the core storage as follows:
Run these 2 commands in terminal.
diskutil cs list
and then
diskutil coreStorage revert lvUUID
where lvUUID is the last lvUUID reported by the previous Terminal command.
Then restart for everything to get back to normal after you have run these commands in Terminal.
Booting to the Startup Manager with option key will then show the recovery partition.
Sorry if this re-kindles the earlier argument but it seemed to me the discussion missed the point that sometimes Apple has released a Recovery Update to all users (not just beta). They do not routinely do it for every dot release. My interpretation is that if, and only if there are changes in the dot release affecting the the Recovery HD which Apple believes are important they will release a general Recovery HD update on MAS. This doesn't happen very often so I assume most dot releases contain no or unimportant changes to the Recovery HD. Apologies if this point was made and missed it.
That said I always download the full installer for every dot release and run it over my install to get the latest Recovery HD as well as updating the OS. Running the full installer is very easy to do and is a useful problem solver sometimes, and running it has never caused me any problems.....and I am a self confessed update junkie.
That said I always download the full installer for every dot release and run it over my install to get the latest Recovery HD as well as updating the OS. Running the full installer is very easy to do and is a useful problem solver sometimes, and running it has never caused me any problems.....and I am a self confessed update junkie.
Yeah. As I said before, that is one of the 4 available methods.
It's usually OK to do it that way too if you want to .... but the point of the Lion method is that it is much quicker and only extracts the Recovery Partition update from the installer and ignores the rest. So this is much more efficient if the rest of the system has already been updated.
Yes I realise that is one of your four methods. Didn't mean to imply I was suggesting another.
Yes, sometimes there are one or two updates to after running the full installer. The other methods may well be quicker in clock time but I just do something else so doesn't use less of my time.
Yes, sometimes there are one or two updates to after running the full installer. The other methods may well be quicker in clock time but I just do something else so doesn't use less of my time.
Sorry to resurrect a zombie thread, but there is a good reason to update the recovery partition for some users. DeployStudio. If you’re managing a significant number of Macs, and using DeployStudio for your imaging, when you create the NetBoot set it can cause issues if the OS version of the machine doesn’t match the recovery partition’s version. Again, not your average users issue I’ll grant you, but it is a specific reason why you’d want to do this.
An extreme niche issue.
The OP posted this thread as some sort of PSA clearly insinuating that Apple was at fault for not updating the recovery partition and that it was a recommended process for general users to use his hack, neither of which is accurate.
An extreme niche issue.
The OP posted this thread as some sort of PSA clearly insinuating that Apple was at fault for not updating the recovery partition and that it was a recommended process for general users to use his hack, neither of which is accurate.
It’s not a niche issue for sysadmins trying to do their job. I suppose developers and admins that are concerned about the lack of imaging support with APFS deserve an eye roll as well.
And no, he did not. The initial post describes how to do it in very neutral terms, a reply asks if there’s a technical reason for this “screw up” and the OP directly says it’s not a screw up, it’s just the way it’s been done since Lion. He makes no recommendation about general users doing it or not. He presents a method to do so if one is so inclined or needs to do so.
My point was that sysadmins doing their job that need to do this hack are a niche in comparison to the general Mac-using populace at large. I meant you no insult with the eyeroll.
Thank you for the correction. It wasn't the initial post but rather in post #12 where the OP claimed Apple was at fault and that his was a recommended workaround.
Can I use this method to create a recovery partition from scratch? Or will it only update an existing partition? After a Time Machine restore mine is completely missing.
Yes. It can be used to create one from scratch. Usually people ask me about this if they restored from a carbon copy cloner clone which sometimes doesn't copy back the recovery partition.
It is unusual for time machine to behave this way however.
Are you sure it is completely missing? If there is core storage it may appear to be missing from the startup manager. But that doesn't mean it isn't there.
What happens if you try booting up with Cmd R? Even if the recovery partition doesn't show up in the startup manager this will still boot up the hidden recovery partition.
Alternatively you can check if you have a recovery partition in terminal with the following command:
diskutil list
That should list all partitions including the hidden recovery partition.
Pretty sure it's missing. CMD-R boots Internet Recovery.
Code:
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 1.0 TB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_HFS Macintosh HD 999.6 GB disk0s2
3: Apple_Boot 650.0 MB disk0s3https://forums.macrumors.com/thread...disk-utility-from-recovery-partition.2064025/
It's probably related.
That Apple_Boot one looks very much like a recovery partition.
But it should look like this:
3: Apple_Boot Recovery HD 650.0 MB disk0s3
It seems that the name Recovery HD is missing.
So I actually think you do have a recovery partition, but it seems to be corrupted.
So maybe you could try the method I posted in the first post in this thread to make a proper recovery partition.
But before you do that you could try mounting it with
diskutil mount /dev/disk0s3
If mounting it works maybe you could then simply give it its proper name Recovery HD without doing anything else.
Mounting didn't work.
Code:
Volume on disk0s3 failed to mount
If the volume is damaged, try the "readOnly" option
If the volume is an APFS Volume, try the "diskutil apfs unlockVolume" verbI'm going to try the instructions you have posted and will get back to you.
EDIT: Well that didn't work. Im getting:-
Code:
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy pluginEDIT 2:
I fixed the sudo permission problem by following the instructions in this thread:- https://forums.macrumors.com/threads/sudo-permission-denied.447812/
But your instructions throw up an error:-
Code:
Expanding RecoveryHDUpdate.pkg
Checksumming Driver Descriptor Map (DDM : 0)…
Driver Descriptor Map (DDM : 0): verified CRC32 $E43B1327
Checksumming (Apple_Free : 1)…
(Apple_Free : 1): verified CRC32 $00000000
Checksumming Apple (Apple_partition_map : 2)…
Apple (Apple_partition_map : 2): verified CRC32 $4B6015F5
Checksumming Macintosh (Apple_Driver_ATAPI : 3)…
Macintosh (Apple_Driver_ATAPI : 3): verified CRC32 $F1E8BA9E
Checksumming (Apple_Free : 4)…
(Apple_Free : 4): verified CRC32 $00000000
Checksumming disk image (Apple_HFS : 5)…
..............................................................................
disk image (Apple_HFS : 5): verified CRC32 $5C5AFC1B
Checksumming (Apple_Free : 6)…
(Apple_Free : 6): verified CRC32 $00000000
verified CRC32 $3436F997
/dev/disk1 Apple_partition_scheme
/dev/disk1s1 Apple_partition_map
/dev/disk1s2 Apple_Driver_ATAPI
/dev/disk1s3 Apple_HFS /Volumes/Mac OS X Lion Recovery HD Update
Expanding InstallESD.dmg
Checksumming Protective Master Boot Record (MBR : 0)…
Protective Master Boot Record (MBR :: verified CRC32 $A9C57BFE
Checksumming GPT Header (Primary GPT Header : 1)…
GPT Header (Primary GPT Header : 1): verified CRC32 $D77F2898
Checksumming GPT Partition Data (Primary GPT Table : 2)…
GPT Partition Data (Primary GPT Tabl: verified CRC32 $6D9EBA8C
Checksumming (Apple_Free : 3)…
(Apple_Free : 3): verified CRC32 $00000000
Checksumming EFI System Partition (C12A7328-F81F-11D2-BA4B-00A0C93EC93B : 4)…
..
EFI System Partition (C12A7328-F81F-: verified CRC32 $B54B659C
Checksumming disk image (Apple_HFS : 5)…
.............................................................................
disk image (Apple_HFS : 5): verified CRC32 $C16DFE8C
Checksumming (Apple_Free : 6)…
..............................................................................
(Apple_Free : 6): verified CRC32 $00000000
Checksumming GPT Partition Data (Backup GPT Table : 7)…
GPT Partition Data (Backup GPT Table: verified CRC32 $6D9EBA8C
Checksumming GPT Header (Backup GPT Header : 8)…
GPT Header (Backup GPT Header : 8): verified CRC32 $38EE2A7A
verified CRC32 $3B94F102
/dev/disk2 GUID_partition_scheme
/dev/disk2s1 EFI
/dev/disk2s2 Apple_HFS /Volumes/OS X Install ESD
Building Recovery Partition. Please Wait
Donor=disk0s2 Image=/Volumes/OS X Install ESD/BaseSystem.dmg DoVerifyImage=0 DoRepairDonor=0
ChunkList=/Volumes/OS X Install ESD/BaseSystem.chunklist
Creating recovery partition: async call initiate
Creating recovery partition: async call exit success; operation now in progress
->-[Local dmAsyncStartedForDisk:]: del callback: DADR=0x7ff681f097b0
<--[Local dmAsyncStartedForDisk:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff681f07260=disk0s2 str=Attaching disk image /Volumes/OS X Install ESD/BaseSystem.dmg dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x0=(null) pole/pct=0/7.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x0=(null) pole/pct=0/10.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x7ff681c12490=disk0s2 pole/pct=0/16.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff681d07e80=disk0s2 str=Reusing recovery partition; no growth needed; host is a simple storage partition dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff681d07e80=disk0s2 str=Checking and re-using booter dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff681e17fa0=disk0s3 str=Updating boot support partitions for the volume as required. dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x7ff681e17fa0=disk0s3 pole/pct=1/26.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x7ff681d07e80=disk0s3 pole/pct=0/26.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff681c12490=disk0s2 str=Formatting booter dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff681e18500=disk0s3 str=newfs_hfs: cannot create filesystem on /dev/rdisk0s3: Operation not permitted
dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x7ff681d07e80=disk0s2 pole/pct=0/95.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncMessageForDisk:string:dictionary:]: del callback: DADR=0x7ff684200070=disk0s2 str=Detaching Base System disk image dict=(null)
<--[Local dmAsyncMessageForDisk:string:dictionary:]
->-[Local dmAsyncProgressForDisk:barberPole:percent:]: del callback: DADR=0x7ff681d07e80=disk0s2 pole/pct=0/100.000000
<--[Local dmAsyncProgressForDisk:barberPole:percent:]
->-[Local dmAsyncFinishedForDisk:mainError:detailError:dictionary:]: del callback: DADR=0x7ff681e18b40=disk0s2 errMain=-69832 errAux=0 infoDict=(null)
<--[Local dmAsyncFinishedForDisk:mainError:detailError:dictionary:]
Creating recovery partition: finished
Error (async): File system formatter failed (-69832)
Cleaning up
"disk1" unmounted.
"disk1" ejected.
"disk2" unmounted.
"disk2" ejected.
touch: /Library/Preferences/SystemConfiguration/com.apple.Boot.plist: Operation not permitted
Last edited:
Error messages are normal for this process. As I said before the most important part is
"Creating recovery partition: finished"
That's a good sign that something worked at least.
So see if it has created a proper recovery partition.
Maybe run
diskutil list
to see it has a proper name now
and boot up with Cmd R to see if it works.
"Creating recovery partition: finished"
That's a good sign that something worked at least.
So see if it has created a proper recovery partition.
Maybe run
diskutil list
to see it has a proper name now
and boot up with Cmd R to see if it works.