Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yes that can be a problem sometimes. I am aware of that. It's much easier if you have the debug menu item. However there is another way to do it.

Just type this in terminal

diskutil list

and find the identifier for your recovery partition. So for example if it looks like this:

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 946.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

then the identifier you want is disk0s3

Then mount it with

diskutil mount /dev/disk0s3

and proceed as per my previous post.
 
  • Like
Reactions: Ready-for-Apple
Ok that works:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ProductBuildVersion</key>
<string>15C50</string>
<key>ProductCopyright</key>
<string>1983-2015 Apple Inc.</string>
<key>ProductName</key>
<string>Mac OS X</string>
<key>ProductUserVisibleVersion</key>
<string>10.11.2</string>
<key>ProductVersion</key>
<string>10.11.2</string>
</dict>
</plist>


Could I use your update method now directly or do I to do something (terminal etc.) before?
 
So you have a 10.11.2 recovery partition.

Yeah you can proceed to install the new 10.11.5 recovery partition via instructions I posted before.
 
Thanks a lot! tup

Last line of Terminal says:
touch: /Library/Preferences/SystemConfiguration/com.apple.Boot.plist: Operation not permitted

Is this critical or what does it mean?
 
Don't worry about it. It shouldn't be a problem. It's just a new error because of SIP. If you don't know what that is then I needn't bother explaining any further. But it won't affect the recovery partition and so any such further explanations are of a purely academic nature and would be of no use whatsoever.
[doublepost=1463745918][/doublepost]Also I think it would be a good idea to unmount your recovery partition now.

So run this:

diskutil unmount /dev/disk0s3

or whatever is your recovery partition identifier (in place of disk0s3 if necessary).
 
Last edited:
Could I use instead of diskutil unmount /dev/disk0s3
also the unmount in Finder or is the terminal better?
 

Attachments

  • Bildschirmfoto 2016-05-20 um 14.17.26.jpg
    Bildschirmfoto 2016-05-20 um 14.17.26.jpg
    104.1 KB · Views: 160
Thanks for the tutorial. It's a great summary of what has been said so far on this issue.

But there is just one weakness in it.

I said in my instructions "reboot with holding down the option key to test your recovery partition"

This of course assumes that the recovery partition is visible in the startup manager - which assumes you don't have core storage - and don't object to reverting it if you do.

But what has transpired in discussions here is that if you do have core storage - and do have objections to reverting it then you will need another way to test the recovery partition.

And that other way is to boot up with holding cmd + R.
[doublepost=1463751258][/doublepost]And rather than wait for someone to get into trouble with mods for posting a link to a certain illegal app which does the same thing, I'll nip that one in the bud right now and explain the difference between my method posted earlier and the app.

As far as the end result is concerned there is no difference whatsoever.

The difference is legal.

My instructions before are perfectly legal. I have provided the link apple has published to obtain dmtest as part of RecoveryHDUpdate.dmg legally and proceed from there to update the recovery partition. That is in fact the ONLY legal way to obtain dmtest. It is why we still have to use the Lion version of Recovery HD Update to do this.

dmtest is proprietary software owned by apple.

Theoretically one may extract dmtest from RecoveryHDUpdate.dmg and insert it into an app which would greatly simplify the process. BUT IT ILLEGAL TO DO SO.

Such an app exists but if you want to keep things legal here then don't post it here.
 
Last edited:
  • Like
Reactions: dk001
But then I saw in the iMessage settings of my phone that I was logged out with my Apple ID. It was only activated with my phone number.
I had filed a bug with Apple that sounds somewhat involved with what you were seeing. Basically, I'm still on iOS 8.3 on my iPhone and Mac OS X 10.9.5 on my "daily driver" MacBook Pro, but many clients are on 10.10 and upgrading to 10.11. What I'd find is that when I'd log on to their machines--to an admin account I had previously created and had configured my AppleID--and perform the update, invariably I'd get my AppleID booted out on all the rest of my devices. Apple closed the bug once saying they couldn't repro, but i re-opened it and it stayed open and they have suggested several times (over several updates) the problem is fixed. They still have not reported on the bug more recently. But it would seem that the activation of the newer AppleID security features is playing havoc on previously created login tokens. So I don't find that 10.11.5 causing you these issues surprising, clearly they're doing some voodoo on the backend to try to chase down/fix what is likely now at least a "known" issue.

Unhelpful in the inconvenience, but perhaps comforting in that it means progress.
 
I just wanted to install the combo update of beta 4 over it again. I thought I will find it in that list where all beta updates normally are with direct Apple links but there was only a OSXUpdCombo10.11.5Auto.pkg under the date 2016-05-12 22:59:55 and the Delta update OSXUpd10.11.5.pkg on 2016-05-16 16:57:46.

I installed the combo and the graphics problem seems to be gone now. I am still on build 15F34, what's the final version.

Now I wait if it appears again. I just turned on my iMac before (the second time today) and immediately saw them both times. At the moment everything is fine again like on beta 4, but I also did not see them on the first day of the update to the finale version.

I will compare the file dates and versions in System/Library/Extensions, if something changed. I made screenshots before.
 
I feel the same way. Unless these few actually did get a lemon of a Mac.
I feel really blessed as I've never had a problem with any of my Mac's. However, I started buying Mac's 3 years ago, and I see people posting problems with computers as old as 2009. 1st, I cannot believe these computers are still running. That is a testament to Apple hardware quality.

Second, I have some theories as to why they are having problems.

The obvious one, that they have old hardware and it's showing it's age.

The less obvious one , that fewer beta testers have the same model of computer , so that it's more likely that bug unique to their hardware will not be caught.

Finally, they have a unique mix of hardware and software that is just the right combination for the bug to appear.

We should clone my Macs that have not had any problem and distribute them amongs the Apple user community. That would solve everyone's problems.
 
I feel really blessed as I've never had a problem with any of my Mac's. However, I started buying Mac's 3 years ago, and I see people posting problems with computers as old as 2009. 1st, I cannot believe these computers are still running. That is a testament to Apple hardware quality.

Second, I have some theories as to why they are having problems.

The obvious one, that they have old hardware and it's showing it's age.

The less obvious one , that fewer beta testers have the same model of computer , so that it's more likely that bug unique to their hardware will not be caught.

Finally, they have a unique mix of hardware and software that is just the right combination for the bug to appear.

We should clone my Macs that have not had any problem and distribute them amongs the Apple user community. That would solve everyone's problems.

The third option is perhaps third party software / kernel extensions, especially old versions.
 
It seems there won't be another beta like 10.11.6 again. They now even removed the link to the 10.11.5 delta update from their "secret" websites what always had the links to every developer beta update and the other one to all public betas back to the first one of 10.11.0 in them. Now there is only the combo update for the final 10.11.5 in both + a separate link to the firmware update as always and most of the usual other stuff.
 
It seems there won't be another beta like 10.11.6 again. They now even removed the link to the 10.11.5 delta update from their "secret" websites what always had the links to every developer beta update and the other one to all public betas back to the first one of 10.11.0 in them. Now there is only the combo update for the final 10.11.5 in both + a separate link to the firmware update as always and most of the usual other stuff.
Makes sense, as all the versions after Snow Leopard have stopped at the .5 release and only get minor security and bug fix updates after that. Timing is just a bit different this year with 10.11.5 releasing prior to WWDC.

The delta update is still publicly accessible though.
 
Maybe it's still there, but all swcdn-links despite the last combo update were removed from those https://swscan.apple.com/.............. websites.

Edit: I mean only the updates from the first beta to the latest version. The Safari betas for older OS X versions are still in there.
 
The Safari betas for older OS X versions are still in there.

Safari betas are not there. They are never there.

If you have a developer account the safari betas, if current, will be at at https://developer.apple.com/downloads

There are no safari betas there anymore because the new version of safari has been released to the public now. But that is where developers go for safari betas, not swscan.apple.com. There probably will be new safari betas there soon.
 
Last edited:
iPhone should be discoverable, for example, to mirror the screen, to use iPhone as controller, and in numerous other apps, such as Infuse https://itunes.apple.com/app/id577130046, which has Bluetooth sharing to iOS devices. The problem is, iPhone isn’t discoverable:


iPhone is on, Bluetooth enabled, with Mac on table

View attachment 631885
I hear you & had been trying to pair them myself ages ago & saw what you see. Initially it seems like they will pair but then don't. I still think its due to protocol support and you won't be able to make it work unless Apple changes the behaviour.
As for mirroring, its a paid app but these guys have a solution : http://www.airsquirrels.com/reflector/
 
  • Like
Reactions: Jess13
[doublepost=1463903748][/doublepost]
After a day....
  • WiFi bug hasn't resurfaced ... yet ... hopefully never ... It's Back :(
  • Battery life is less ... monitor says it is Safari
  • Safari beach ball has taken a vacation ... so far
  • It now gets much warmer when watching streaming video

Will post more as I find it...

Update: Added video item
Update 2: Wifi bug is back. Have to turn off / turn on Wifi this morning to get it to recognize from sleep.

I had that WIFI issue a lot on Yosemite, then El Cap was much better but it still occurred once in a while.
Bought a Ubiquiti Unifi AC Pro, never had that issue again.
 
Last edited:
Is this thing safe to install on a 27" iMac late 2014?
I feel bad having to ask but given the iPad Pro install fiasco, I feel I must.
 
Are there noticeable changes in CPU temperature when using an eGPU on a MacBook Pro running OS X 10.11.5?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.