Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
It may be just me, but the beta seed update for users...bricked my Retina iMac. I was able to restore with a current Time Machine copy. Anybody else the same? I could not restart and had just a black screen with a mouse cursor . Nothing went further after about 20 minutes. Then I restored.
 

JWorld127

macrumors 6502
Jan 12, 2013
414
111
after reading the warning i am not going to download it. glad i read this aswell.

why would apple do that? scares the sht outta me
 

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
after reading the warning i am not going to download it. glad i read this aswell.

why would apple do that? scares the sht outta me

This is the first issue I have ever had with any OS X beta or update!
 

bmac89

macrumors 65816
Aug 3, 2014
1,388
468
It may be just me, but the beta seed update for users...bricked my Retina iMac. I was able to restore with a current Time Machine copy. Anybody else the same? I could not restart and had just a black screen with a mouse cursor . Nothing went further after about 20 minutes. Then I restored.

Same thing happened to me. Stuck on Black screen for me... after 20 minutes I hard shutdown and tried again. Now it seems to be working - or atleast it is in the process of installing the updates.

If it did not install the updates then you did not need to restore with time machine.
 

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
What exactly was the problem?

Sorry, I did not include enough info in my original post....I have a retina iMac and the issue was no final restart...just a final black screen and a mouse cursor.

----------

Same thing happened to me. Stuck on Black screen for me... after 20 minutes I hard shutdown and tried again. Now it seems to be working - or atleast it is in the process of installing the updates.

If it did not install the updates then you did not need to restore with time machine.

So you are okay now? Also are you showing the beta update as 10.10.2...and running okay?
 

bmac89

macrumors 65816
Aug 3, 2014
1,388
468
Sorry, I did not include enough info in my original post....I have a retina iMac and the issue was no final restart...just a final black screen and a mouse cursor.

Sounds like the same issue which I posted "Yosemite update stuck on black screen" 15 minutes prior to your post.

However I don't understand why you needed to do a time machine restore if it didn't even get to the stage of installing the updates?

It has just this second finished installing the update and rebooting...

Update: It finished installing and I am now running 10.0.2 (build 14C81h)
 
Last edited:

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
Sounds like the same issue which I posted "Yosemite update stuck on black screen" 15 minutes prior to your post.

However I don't understand why you needed to do a time machine restore if it didn't even get to the stage of installing the updates?

It has just this second finished installing the update and rebooting - will update...

Did not see your post...it was not up when I posted. One question...how long did you wait out the black screen? Now I installed the update and it went no farther. Then I restored.
 

tywebb13

macrumors 68040
Apr 21, 2012
3,052
1,717
I assume you got the new build 14C81h that came out today, not 14C81f.

Anyway, in both cases, if you get it through the mac app store, it will update the firmware - without warning.

If you would prefer to install it without the firmware update, you can use direct links for the delta or combo. That will not update the firmware.

It could be the firmware update causing your problem, not yosemite itself.
 

bmac89

macrumors 65816
Aug 3, 2014
1,388
468
Did not see your post...it was not up when I posted. One question...how long did you wait out the black screen? Now I installed the update and it went no farther. Then I restored.

I waited approximately 20 minutes then I hard shutdown the computer.
I restarted and went to App Store and clicked update - computer restarted fine and update finished.

I now have 10.0.2 (build: 14C81h)

----------

I assume you got the new build 14C81h that came out today, not 14C81f.

Anyway, in both cases, if you get it through the mac app store, it will update the firmware - without warning.

If you would prefer to install it without the firmware update, you can use direct links for the delta or combo. That will not update the firmware.

It could be the firmware update causing your problem, not yosemite itself.

Hmmm! Too late for me. I just updated through App Store. I am running Yosemite off an external hard drive, however Yosemite is not my main operating system. I am still running Snow Leopard as main OSX.
I'm not sure that I wanted to update firmware!
I understand what firmware is, but are there any potential issues in my circumstance?

Thanks
 

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
I waited approximately 20 minutes then I hard shutdown the computer.
I restarted and went to App Store and clicked update - computer restarted fine and update finished.

I now have 10.0.2 (build: 14C81h)

----------



Hmmm! Too late for me. I just updated through App Store. I am running Yosemite off an external hard drive, however Yosemite is not my main operating system. I'm not sure that I wanted to update firmware!


I guess I will wait this out...thanks for the check back!
 

w0lf

macrumors 65816
Feb 16, 2013
1,268
109
USA
Bricked isn't the right term to use here. Bricked would imply that your computer was rendered permanently unusable. All you had to do was reinstall. That doesn't even seem like that big of an issue...
 

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
Bricked isn't the right term to use here. Bricked would imply that your computer was rendered permanently unusable. All you had to do was reinstall. That doesn't even seem like that big of an issue...

What a minute...my system would not restart past a black screen. It was not a big issue and I did not say it was so. I have indicated that I restored and successfully. it was unusable versus a restore...bricked is a relative term to the moment and nothing more! No intent to offend any users or trash Apple...I know this is a beta and was just looking for common issues.
 

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
why would apple do that? scares the sht outta me

This was a Beta release, they can be expected to have some issues and are only released to those users who subscribe to them. They should not be used by average Joe's just to get a new release early.

Some of the issues will affect installation no doubt but Apple developer's won't intentionally release code that simply won't install, it will have hit some circumstance that prevented installation but isn't handled (yet) by the software.

If it scares you, simply don't subscribe to the Beta programme, and have a good backup strategy, Beta or not, and software update should be treated that it can have/cause issues and need to be reversed.
 

tywebb13

macrumors 68040
Apr 21, 2012
3,052
1,717
when was there last a firmware update that bricked Mac's

A few hours ago when apple released build 14C81h to public beta testers.

Those who used the direct links for delta or combo (which will not update the firmware) are not reporting brickings. But those who just tried to do it through the mac app store (which will update the firmware) are reporting brickings. So what else could it be? I doubt it is yosemite itself causing the brickings.

I'm running builds 14C81f and 14C81h without any problems. I did not allow the firmware updates to occur.
 

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
A few hours ago when apple released build 14C81h to public beta testers.

Those who used the direct links for delta or combo (which will not update the firmware) are not reporting brickings. But those who just tried to do it through the mac app store (which will update the firmware) are reporting brickings. So what else could it be? I doubt it is yosemite itself causing the brickings.

I'm running builds 14C81f and 14C81h without any problems. I did not allow the firmware updates to occur.

Correct...I have now tried twice and the same results...the update will not complete to a desktop screen. I did each update from the App store for an iMac retina. By the way I was informed that "bricked" was an improper term.
 

tywebb13

macrumors 68040
Apr 21, 2012
3,052
1,717
Are you going to try the direct links method, or just wait it out?

No offence, but there is not much point in being part of a beta program if you are going to wait till it is publicly released if you don't mind me saying so.

In any case, the problems in this thread would make for a good bug report. I'm not going to do it though because I'm getting the betas to run pretty well on my computers.
 

GatorGhost

macrumors regular
Original poster
Jun 30, 2014
113
19
Are you going to try the direct links method, or just wait it out?

No offence, but there is not much point in being part of a beta program if you are going to wait till it is publicly released if you don't mind me saying so.

In any case, the problems in this thread would make for a good bug report. I'm not going to do it though because I'm getting the betas to run pretty well on my computers.


Happy to try the beta scenario..no complaints...it is free and fun...but I have questions and my"puter is not adapting and I am wondering why? Is that not what i should be doing?
 

tywebb13

macrumors 68040
Apr 21, 2012
3,052
1,717
Yes we can wonder and theorise as much as we like here on macrumors. But that is not the point of the beta program.

If you are asking me to advise you on what to do, I'd say give the direct links method a go, but also to make a bug report to apple.

Note about bug reports

Bug reports to apple will ultimately be more useful than complaining on macrumors.

Even in cases that say "duplicate of radar number #####". I have even seen apple engineers go onto the developer forums to say that duplicates sometimes get higher priority. If you are new to this, getting a message from apple that you have a duplicate may at first be discouraging, but when you get to know more about how the system works, you begin to appreciate that it's not necessarily a bad thing to have a duplicate.
 

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
A few hours ago when apple released build 14C81h to public beta testers.

Those who used the direct links for delta or combo (which will not update the firmware) are not reporting brickings. But those who just tried to do it through the mac app store (which will update the firmware) are reporting brickings. So what else could it be? I doubt it is yosemite itself causing the brickings.

I'm running builds 14C81f and 14C81h without any problems. I did not allow the firmware updates to occur.

These reports aren't of the machine being bricked to a useless irretreivable state though, people are restarting and trying again and either succeeding or getting back where they started, that isnt being bricked as the industry understands the term.

Firmware update would be an issue if it needed reversing but that doesnt seem the case.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.