8001050F Error Fixed


****ACHTUNG****

THIS WILL VOID YOUR WARRANTY

****ACHTUNG****

Attention to those of you too impatient to wait until tomorrow (or whenever Sony actually solves this problem) to fix their Playstation 3′s by-now-notorious 8001050F error: our very own Joe the Tech has come up with a solution. Those techno-savvy enough to void their warranty can reset the PS3′s CMOS by unplugging the CMOS battery for 5-10 minutes.  We’ve confirmed that this works at least on our PS3 down here at The Big’s corporate offices, and it really is that simple.

Now to the not-so-simple part.  This fix involves dismantling your PS3 so that you can get to the underside of your motherboard.  However, Sony (in their infinite wisdom) has actually made the PS3 relatively easy to dismantle (relative to the PS2, if you’re wondering). Remember to unplug your PS3 from the power source before continuing. Dismantling instructions can be found here.

You only need to go as far as being able to remove the motherboard assembly to get to the battery (on our model, anyways).  Again, fair warning, THIS WILL VOID YOUR WARRANTY (if you still have one on your old PS3).  This problem does not effect the newer PS3 Slim models.

Now, after you’ve removed the motherboard assemble and see the CMOS battery (it’s a standard 3.3v CR2032 battery inside of a green rubber casing with a red and a black wire coming out of it and leading to a plug), just go ahead and unplug the battery from the motherboard.  You’ll need to wait a good 5-10 minutes (an hour if you want to be REALLY sure) for the capacitors to drain and for the CMOS to reset.  After that, just plug the battery back in and reassemble the PS3.

After it’s reassembled, you can go ahead and hook it back up to your TV/Monitor.  When you first start it up, you’ll be greeted with a Date/Time Set menu.  Set it to the current date/time (or any time after 11:59pm 2/28/10), hit X, and you’re back up and running as though nothing happened.

DISCLAIMER:

The Big Critique and/or its parent company/shareholders can not be held responsible for any damage that may come to you or your PS3 as a result of following the instructions here.  You perform this fix at your own risk.

PICTURES




19 thoughts on “8001050F Error Fixed”

  1. Just hope they dont pull a “Microsoft” on ps3 owners and ban every system thats been opened for any reason from their online services..

    had they pulled this shit on the FFXIII release date, then i might have a problem, as it stands right now. i’m gonna just wait it out…

  2. I’d be REAL impressed if they were actually able to determine that the PS3 had been dismantled from a software perspective. I suppose they could look to see if there were any logs that the CMOS had been reset, but that could just as easily be caused by a bad CMOS battery. There’s no modding or altering of the machine’s original configuration here. It’s simply an issue of the motherboard being reset back to factory specifications. This is something that should be available from within the system software itself.

  3. I agree, and i dont think sony would take it as far as microsoft.

    i’m not sure exactly how the “tamper” detection for the 360′s worked, but alot of people got banned for even minuscule things like modifying the cooling system so their damn machine worked! some people also opened them to fix the RROD issues themselves, result? banned. Ha, some reported being banned after receiving their machines back from a WARRANTY repair. gg Microsoft..

  4. I’m glad they just replaced mine instead of actually repairing it, then. It was just a bitch getting all my DLCs transferred over to the new console (something Microsoft claims they do on replaced consoles).

  5. Nope, it was Sony’s own personal Y2K. Once the date flipped over to Feb. 29th on the actual console, it looked like PSN freaked out and wouldn’t let any console connect with a non-existent date. Or something like that.

  6. Your solution looks eerily simular to Jared0327 on the following
    site:
    http://community.eu.playstation.com/t5/Technical-Help/Stuck-in-system-update-loop-error-8002F1F0/td-p/9465304/page/2

    I guess the tech saavvy research involved scouring the web. Short of one or 2 steps that may still be needed or may not, they are the same.
    Posted on the above site: 12/30/09 at 6:28PM. This fix resolves many of the 800XXXX Errors, not just one.

    And SONY refuses to admit that the update caused the issue and they will continue to deny such.

  7. Mike,
    That’s crazy! I honestly didn’t realize something like this had happened before. We were perhaps a little impatient with this latest issue, but hey, God of War III had just came out, and it seemed worth a try since our PS3 had been giving us so much grief in general, we were thinking of replacing it. My question is, if it’s not Sony’s fault, who’s could it possibly be?? Ridiculous.

  8. Actually, our “tech savvy research” involved the knowledge that the 8001050F error was a simple system clock error, and the PS3 (like any computer system) used a CMOS battery to keep its BIOS settings during times when the system isn’t supplied an outside power source. Also, like any computer, when there is no external power source and the CMOS battery isn’t present (provided the capacitors have had ample time to drain), the BIOS will reset itself to factory settings, taking the system clock with it. It’s a common practice in other computer systems when a BIOS has been set improperly so as to make the system non-bootable. Consumer electronics lesson aside, I really don’t see many similarities to the forum post linked by Mike other than the concept of removing the battery itself which, like I said, is a common practice for BIOS based issues.

  9. Holy crap mike! You’re so right! Them disassembling a ps3 looks just like YOU disassembling a ps3. That shit be craaazy. It’s almost like the same problem with identical equipment has an identical solution. Mind. Blown.

  10. It would be, but I don’t think so. This Mike and the other Mike have different email and IP addresses (yes, we can see those). Also, notice the curious lack of extraneous and superfluous punctuation.

Speak up!