The above video goes away if you are a member and logged in, so log in now!
Download an md5 checker and check if your 3.55 update has this md5: ca595ad9f3af8f1491d9c9b6921a8c61
Well, if his CFW is the cause, its a partial brick and affecting 2 users among thousands. If your luck is that bad thank god you didn't try Waninkoko's CFW, lol.
Well, you've got the file in the right place, but you still haven't verified that the file did not get corrupted either downloading it or copying it to the USB stick. After its on the stick, run an MD5 hash check on it, it will take you a few seconds and let us that are trying to help you know that the file is not the issue. I linked 2 MD5 check programs below.
The MD5 of the OFW 3.55 on your USB drive should be ca595ad9f3af8f1491d9c9b6921a8c61.
If the MD5's match, and it still won't install, try another USB flash drive, maybe the one your using is somehow faulty.
Reply back in the next 5 hrs with wether this worked, I have 1 more idea, but I want to make sure you covered these bases first. With my last idea, if the MD5's don't match or the USB drive is bad, it can potential brick your console.
Yes I tried recovery, same result. I'm not sure it will let me downgrade as it will not read any FW, I keep getting corrupt data messages.
Originally Posted by clmepe
Hey thanks for the intelligent response. I ran the MD5 checker first on the OFW file from my computer and it checks out, but when running it from my USB stick it shows b813ff51300c42d7c3b96992edfd6746. I'm not sure what this means other than the file is getting corrupted on the way to my USB drive and I can't go back to OFW with this going on. What could be causing the hash to change?
Originally Posted by blazie151
Its best to assume that your USB thumb drive is failing or slowly dieing. I would try using another USB dongle or device.
Originally Posted by belikeike
Twitter - Linuzo
Makes sense. I'm trying downloading the OFW from Sony directly to the USB drive to see if the hash matches up. If it doesn't then I suppose I'll run and grab another drive sometime soon.
Originally Posted by linuzo
Could being on Vista 64-bit have anything to do with this? Should I ever have to "Run as Administrator" or any of that overthought crap?
Ok, super. The OFW i downloaded straight to the USB drive comes up with matching hashes to the one you guys have posted, but when I try the update via recovery mode it still throws an error code (8002F2B5 corrupt data). Guess I will just have to get another stick tomorrow unless someone has any other ideas. I'll share what happens when it does. Thanks for all the help guys.
Hmmm. Tried again from recovery, this time it started "preparing for update", got to about 30% done, then gave a corrupt data error (8002F285). Now that I'm at my wit's end I think it's time to crack the night's first beer
i have the same problem (data corrupt ) only i have OFW 3.55 and i am tring to install the geohot file through recovery mode, , i checked the MD5 with the app provided (THANK YOU) and i have the blah..blah...DFD6746 on my pc so i am sure i got screwed on the way here, how does these things happen? oh well ..... i was going to try and install the geohot fw although i would really like to know why you are wanting to go back to the OFW what is wrong with goehots CFW???
are we all going to be forced to update as soon as a new forced update is out from $ony, anyways???
The Geohot FW won't let you run backups, as it doesn't allow LV2 patching or something like that. It only lets you run homebrew. And if you want to play online then yes you will be forced to update. I wanted to use my old Fat 40GB as a backup single player machine and my new Slim 250GB as my everyday driver.
Originally Posted by SoCoM_4