Hacker Newsnew | past | comments | ask | show | jobs | submit | whaevr's commentslogin

Thats what I was thinking, Im going to go ahead and guess that not too many fb users go through their entire timeline and delete Every.Single.Post. Flagging something like that as hostile and then "restoring" your timeline makes sense. However, I feel like there should be some kind of communication going on in email before something is actually done (for the mass deletes and auto restoring) and a simple "click here if this is what you really wanted to do" would suffice..


Ooh gestapit..


Wait for the company to realize what's going on. Wait for said company to release a patch to fix a problem that was obviously their fault to begin with. You face can return to it's normal color now. Jumping to conclusions like "SOL" is a bit ridiculous

edit: I'll gladly take a downvote for this, you're talking about screaming at customer support and IM getting downvoted. Constructive group we have here.


This happened during another wave of bricked PS3's about a year ago. One year later - same shit is happening to PS3 owners, no real addressing of the problem happened.

My device has been stuck in a perpetual (failing) update loop like many others. No patch was ever released. There's no known way without specialized hardware (PS3Key) or out-of-warranty RMA. I don't want to invest in either solution.


My device does something similar. When a new update comes out, 95% of the time the update will fail. When that happens, it continues to fail no matter how often I retry.

Through much trial and error, I found a way to make the update work every time. This may look stupid, but I swear it works:

  1. Try the update. It fails.
  2. Turn off the console.
  3. Take the hard drive out.
  4. Turn on the console. It will fail to boot and shutdown.
  5. Put the hard drive back in.
  6. Turn on the console. The update will start again and succeed.
I have no idea why this works, it makes no sense to me. But it's been working this way without fail for a few years.


Thanks man. I tried this out to no avail. When I realized that I was faced with a hefty RMA bill, I tried both removing the battery and letting its settings RAM clear overnight as well as booting without a hard drive. Both had no effect unfortunately.

In my opinion, it's a poorly designed update mechanism that makes it prone to failure. There should be some redundancy built into the process so that the machine can always force itself back to a "known-good" state and at least access the recovery menu.


Officially out of luck? I've read in multiple places they are looking into it and will release a patch


The question was what happens if your device is bricked. Bricked means you are unable to even apply a patch and need to take the device in for servicing or replacement.

If you are able to apply an update yourself, your device is not bricked.


This bug hasn't caused any devices to get bricked either. The title is wrong. The recovery menu is accessible, so is definitely patchable.


Correct with respect to the issue discussed in the article.

Though I was answering the related hypothetical question "What happens if an official update bricks your device and the warranty expired?".


>It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.

I feel your paIEnumerable


http://goo.gl/b1dXA Seems to suggest slightly otherwise, I remember seeing it on a commercial and just going slack jawed...WHAT?


Well, if they want to stay with the ! theme how about something along the lines of !AnotherStagnantProductFailure


I'll take my "more clever", and head back to the 1800s I suppose.


Interesting, one question though. Who thought orange text on white background was a good idea? Ow


Discuss the topic please.


? It is related to the topic. Maybe not specifically the article but the website in question that was linked. I thought it was a pretty odd choice, and website design is definitely relevant to HN


Boom. That right there pretty much ended any defense the CEO had. HN has countless submissions focusing on site layout/design/user interaction/click rate/etc

If you wanted the user to be able to see the message or cared that they did, you would have made it more obvious what was going on here.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: