8002F281 Error

Pitrsak

Member
So I am changing HDD on my PS3 FAT CECHL04 from 80gb to 500gb. On old drive I've had new Evilnat 4.88 firmware so I can everything backup. While I was changing the drive I thought I clean out PS3 from dust etc. After that in Safe mode I used the 5th option for then new drive and then update it to Evilnat 4.88. Apparantly I damaged the 24 pin cable that connects blu ray to motherboard, so the installation was cancelled due to the 8002f14E error, so I bought new cable and now it seems to work. But when I want to install the firmware it always shows after checking 8002F281 error and I tried varius combination of the new HDD (keep it NTSF, change it to FAT32, make 30gb FAT32 partition, of course I tried resettting file system, default settings - after that it says that HDD can't be read, rebuilding database - that was in a loop but I will probably try it again, format flash drive, try ofw...) and none of them worked. And I tried old HDD and it wants an update due to the "corrupted" data and after checking it again shows 8002F281 error.
Now I am trying fully format the new HDD if that helps.
 
Last edited:
Okay it may sound stupid, but apparently I did not have to go to safe mode and just format the HDD from first screen.
 
(keep it NTSF, change it to FAT32, make 30gb FAT32 partition, of course I tried resettting file system, default settings - after that it says that HDD can't be read, rebuilding database - that was in a loop but I will probably try it again, format flash drive, try ofw...)

Waste of time. PS3 will not using it, instead she overwriting by her own partition table and making a lot of her own partitions. Everything is encrypted. So whatever You would do with HDD it doesn't matter.
 
Waste of time. PS3 will not using it, instead she overwriting by her own partition table and making a lot of her own partitions. Everything is encrypted. So whatever You would do with HDD it doesn't matter.
i'm getting the same error at 6%, according to the install breakdown of ofw, this is where it happens. Any ideas? i dont think its the hdd or the bd, or the bt. i have a 3001B, got it with a broken hdmi port, resoldered a new port, got an image, and it was the install screen with the error. i put 4.90 ofw on a usb, reformatted the hdd, and same thing at 6%
Update Package Revoke list
read package revoke list package (576 bytes) elapsed = 6 msec
update package revoke list elapsed = 331 msec
Update Package Revoke list done(0x8002f000)
RL_FOR_PACKAGE.img copied from PUP to trvk_pkg
Update Core OS Package
read core os package (5193774 bytes) elapsed = 324 msec
update core os package elapsed = 1965 msec
Update Core OS Package done(0x8002f000)
Core OS package (CORE_OS_PACKAGE.pkg) is unpkg'ed from PUP and written to ros
 
What You have quoted is old but technically true... However I read many times on internet that FAT32 on MBR on internal drive, *somehow*, fixing detection problems for those people. Personally I don't see any sense in that. But there are still many mysteries with internal HDD. One of it is leaving first sector intact and not encrypted which should never happening in theory. So I've got more distance to such reports.
 

Similar threads

Back
Top