donhass.com

Well, I think I have realized COD:MW2 is pluggin up the inter-tubes folks!  Just got Error Code 80022A07 when trying to sync my PS3 trophies tonight.  From what it sounds it has to do with the PS3 failing to talk to the PSN servers to sync.  I tried like 5 times over 5 – 10 minutes and then it finally went through.  Otherwise it would get to the same % and die.

I saw some other forums start complaining about it yesterday (what 24 hours into COD:MW2) and back in April 09.  I can only imagine servers everywhere on all consoles are just toasty from COD release this week.  I bet if you did a little research around some of the major releases you will find that some of the network based solutions (especially on PSN) get a little fussy as well.

If you get this, best solution, be patient and try to sync during another time of the day (most likely early morning when all your COD players are beginning to pass out).

Don’t delete your saved games, game data, etc.  It will come back, it is a network issue most likely at Sony and nothing to do with your PS3.

Patience is the key here.  Thank goodness.  Now if we could only have Sony put a “text” message on the screen instead of error codes.  The Sony Firmware guys must of worked at Oracle or something!

Thank you Sony for the elegant error codes!

So when is 120G not enough?  When it can be 500G.

Since Sony is nice enough to allow PS3 owners upgrade their systems with newer and more importantly, larger drives we ventured down the path.  A Western Digital WD500BEVT showed up at our door step.  From all the Sony docs and blog entries, the process should be a piece of cake.

Well….

All we had to do was (oh ya, this is going to be a wild ride Mr Toad!):

1. Got a external USB drive that could hold our 40G+ of current data.  No problem had a 320G laying around.
2. Clean off external 320G since it was formatted NTFS and PS3 not playing that game.  No problem dropped stuff on one of our 1T drives.
3. Wait, no NTFS, need FAT32.  Wait, Windows 7, Vista and XP don’t format FAT32 above 32G.  Never would of thought I would run into that issue.
4. In comes FAT32 Formatter (http://www.ridgecrop.demon.co.uk/index.htm) command-line if you like that or Windows GUI version (http://www.ridgecrop.demon.co.uk/guiformat.htm).
5. Formatted 320G to FAT32.  All good to go.
6. In PS3 XMB, went to Settings -> System Settings -> Backup Utility -> Back Up.
7. Selected our external drive, away it started chugging.  An hour an half later it was done.  Everything looked fine.
8. Drive Swap!  Sony describes this along with about a million other sites.  Slim is VERY easy to do and no problem with a torqued to heck screw for us.  This definitely sounded like more of an issue on the PHAT model.
9. Slid in new WD500G.  Closed up the drive cover.  Ready to restore.
10. Forgot to put firmware update on external drive in a PS3/UPDATE folder like it said to… fail.
11. Get firmware file, put in proper directory, do over.
12. PS3 found firmware on external drive this time.
13. Installed new firmware with the brand new bare drive.
14. Formatted new drive, all is good.  Can taste 500G just over the hill now.
15. Got blank slate and now back to Settings -> System Settings -> Backup Utility -> Back Up, select Restore.
16. Select external drive, yep!
17. Select only backup we had on drive, yes sir!
18. Restore, restoring, restoring, sleep, restoring.  1 hour 40 minutes later, 98%, 99%, FAIL!!!!!!!!
19. What, how, where, why oh why? Truly epic fail.
20. Go back to 6 and start over thinking something was bad with original backup.  Has to be right!? right?  What else could it be.  Following Sony’s rules.  It’s not like this is that other company that make RedRing machines?
21. FAIL! Again. Oh woe is me.
22. Maybe something to do with files its backing up… maybe a little house cleaning of original drive will make it all right Will Robinson.  Dump vids, photos, demos, that should be better, heck that is less to backup.
23. Go back to 6 and do this AGAIN. Another hour and 20 minutes or so fly by, not really.  But hey that is 15 less than last time.
24. FAIL! AGAIN.   NO NO NO NOOOOOOOoooooo ooooooooooooohhhhhhhhhhhhhh
25. So we finally realize a good old error code right in front of our face 80010029.  Corrupt data file basically.  Come to find out this has been around for years, thank you very much Sony!
26. Finally figured it out after reading way too many sob stories about people losing saved game data and starting their games over, yada yada yada.  Living with bare really big drives, it wasn’t going to happen to me!
27. One thing to know about FAT32 is that it has a max file size limit of 4G – 1 byte.  It led me to wondering in the now slimmed down 32G worth of data I am backing up if there was a file size limit of some of the files still left.
28. So slap back in the original Toshiba 120 in our Slim.
29. Here goes the last area to clean on the original drive before doing my final backup AGAIN (and final time).  It was the Game Data section, you know all the Installed Games (Devil May Cry 4, MGS4 as a couple examples) and patches.  Well there was some in there passing 4G in size.  Hmmmm wonder if that just happens to be by chance or we are something.  Who cares at this point.
30. Well we PURGE every Game Data (FIOS will get them for me again <G>), backup last time around.
31. One positive note, it only took 10 minutes to backup this time around since we purged 31G+ worth of Game data and patches.  Scary!
32. Swap in the new drive (last time please), button the slim back up and hook it all back and lets do some restoring!
33. Start restore, 12 minutes later….. Success
34. Yep it was either size of those Game Data files (one or more) or a corrupt one (which I doubt otherwise the game would not of worked).  Needless to say, Slim is sportin a new 500G!  Actually 416G clean.

Never think something that is suppose to be easy, is going to be easy.  However, working through the problem all things are possible, even with bad software!   I should know, I have written some and definitely seen plenty from the other side.

Thanks Sony, love you too.

So if my 360 killing itself over MS update back in August, now it seems Sony’s PS3 is having similar issues (knock on plastic mine isn’t yet since it survived the 3.0 update).

Ars has a good write up on it and I was wondering how long it was going to take for someone to pursue the matter.

Not to mention the actual class action lawsuit (PDF) now.

This really does seem like a trend and both companies (Sony and MS) both are touting the same fix.  Send in your console + XXX money and we will “fix” it for you.  Fix what your software broke it, so why am I giving you a dime?!  Sadly enough, MS is charging less right now ($100 dead 360) vs Sony PS3 ($150 bricked PS3).

My post back in August (XBOX 360 Aug 11 System Update Update) ran through what worked for many a solution to MS killer system update.  That was the breaking point for me on giving MS any more pennies period.  Their customer support was horrible and not to mention wanting $ for something they broke.

I can see where the PS3 owners are completely coming from.  I reported MS to BBB about their service breaking my hardware, what did I get?!  Nothing!  Zip, zilch, squat.

Exact quote from final status from BBB:

Complaint status: Inform Business Of Information Only Complaint

Nice huh.  This will be one to watch going forward for sure.  Since if anything comes from the Sony, I could see MS in for the exact same thing if Sony ends up paying anything to PS3 owners.

These are when you love having FIOS!

Speedtest.net FIOS Results

So since I have posted the following over on the xbox forums and seem to get back quite a bit of feedback that it has solved several others RROD August 11 System Update deaths, I figured I would post it here as well before MS decides to pull the whole thread to make sure they don’t admit that they had anything to do with everyone’s consoles dying!

So my console was completely dead after working with MS support related to the Aug 11 update failure on my 3 year old Pro console. They basically wanted me to send it in saying I had a hardware failure (even though initially didn’t have RROD) and wanted the 100 bucks to repair since it was long past its warranty.

Since I wasn’t going to pay for any old hardware to be fixed that was broken by their software, I figured I would find a solution on my own since their support was pretty useless on the phone.

Since the console was working fine before the update I started to see what options to clear the system of the update. Since mine was not even getting past the 360 startup logo before it completely froze and then showed RROD recently, I had nothing to lose. It was going to meet the dumpster at this point!

First thing I did was use the sync clear method stated early on in the post and several others places in the forums and web:

1. Held the sync button (on the console to the right of the 2nd memory module port).
2. Pressed the power button (still holding down sync button the whole time) until it was at the dashboard.

Mine didn’t say anything, but oddly enough it got me past the logo and I actually could see the NXE dash now. I have not seen this for days (say the last 8 tries of starting the console). That was positive.

---

Next I used the 360 Clear Cache method (the new method, since the August 11 update was still in place at this point apparently). Not the long (X,X,LB,RB,X,X) combo.

I quickly navigated to the system blade (thinking I had less than 30 seconds before it RROD on me):

1. Selected Memory.
2. Selected Hard Drive.
3. Selected Y for device options.
4. Selected Clear Cache (3rd Choice).

In my case it freed up about 5 gigs worth of disk space by clearing out the “cache”. Dang all those software updates for games!

Restarted the console to be safe and see if everything still worked. Sure enough it started up, the lag I noticed after the August 11 update was not there and I actually was able to play two XBL games and even some Fable II. All of which was impossible the previous days.

Does this solve all my problems, probably not, but things are working again until the next failure or RROD. I find it interesting that MS doesn’t force these kinds of clearing of the cache if they can be problems with system updates.

Since both of these steps together has currently (and maybe only temporarily) fixed my RROD. This leads me to believe it is really not hardware failure! Does anyone else see something wrong with this if my console lives on and MS was going to take my 100 bucks to just clear the cache on my box and send it back to me!!! Or is there really changes to the latest system code that is taking a border line stable console and sending it over the edge?

This was the first time I ever had any failures on my 360, which would lead one to believe something not right with this system update. I wonder if these steps works for anyone else out there with the Aug 11 failures!?”

I have verified that this has worked on my console (still working many gaming sessions later) and at least 8 reported instances of others consoles (ranging from 3+ years old to not even a month old elite) being fixed by these steps above. Even with complete RROD’s. Of course I can’t guarantee this will work for anyone else’s 360 or that it will last, but it has worked on ours at this point.
Thanks for nothing Microsoft, maybe you would like to test your stuff before releasing. All for new avatar and netflix junk!? Dang, what happens come fall with the Twitter and Fackebook stuff piled on top of this… I smell smoke in them there hills?

They just released their next music video.  Felicia sounds great, not to mention that this is what all The Guild fans have been waiting for!

Season 3 starts August 25 on XBOX Live (right now the only reason I can see I want an 360 right now!).  How is this for a early gift to get you ready for the new fall season!

Got to love geeks!