CANNOT upgrade to REBUG 4.86.1 Lite continuously recieve ERROR -data is corrupted (8002F957)

P

ps2mobbins

Member
I keep encountering ERROR -data is corrupted (8002F957) when trying to update my ps3 to rebug 4.86.1 lite.

I Jailbroke my PS3 months ago and haven't played it in a while so i decided bring it out to play again seeing that a new update for rebug was available i downlaoded the pup to update however when i do i keep getting a corrupted error FYI I AM NOT trying to install cfw for the first time i already have done so i am trying to update. Ive downloaded the version of rebug from the site mirror on waybackmachine
CECH-2101A is my model.
Info On Rebug Toolbox: PS3 SYSTEM:Firmware 4.85 LV2 Kernel:CEX Target Type:CEX Cobra 8.2
Info on mmCM PS3 System: Firmware 4.85 [SC-35 | PL3) Firmware Mode: COBRA 8.20 compatible
YES! i have formated the usb stick to FAT32
YES! i have checked the MD5 Checksum on the update file its correct
YES! I have used the right sided usb port and also tried to install on recovery
please help ive been trying to solve this for about an hour with no solution
 
Install last rebug toolbox and check last column toggle QA enable. Then you can try installing fw from safe mode.
 
Last edited by a moderator:
I'm not sure what "QA Enable" will give?
He is trying to update firmware not to downgrade...

In theory:
0x8002F957Error with installing Firmware update. The data is corrupted (firmware in flash does not allow the MFW installation as it does not contain the needed patches)
https://www.psdevwiki.com/ps3/Error_Codes.

This error mostly occurs when a console is on OFW...
But you have and can launch Rebug toolbox and multiMAN ...
 
Last edited:
correct. qa flagging is only for downgrading. I might say something might be wrong with the bt or bd, but I'm not sure what the error alphanumeric is for that. I'm thinking it either errors around 15% or 75% if that's the problem. if there's a ferrox firmware for 4.86, try installing that. if you've never tried ferrox, don't worry. it's very stable. when I first got my new ps3, the rebug it was on was very buggy. I didn't have those bugs when I upgraded to ferrox, but I did downgrade back and the bugs were gone.
 
Last edited:
I think @Joonie used mfw for the nobt, nobd, rsod versions of the latest firmware. if one of those was being installed, that might explain the error. afaik, even if you try to install nobd, nobt at least, it will still work even if the system is functional in that capacity. I remember bits was making those, since he learned how to do it manually. he'd test them afterwards to make sure they worked. he did tell me that they worked even if you had nobd, nobt (dunno about rsod). rsod is usually an issue with the vtrm iirc. though, I'm really just guessing based on what devwiki says about the error. I do agree, he should try another firmware just in case. when I got my ps3, it was even using the wrong network to connect to psn.
 
ps2mobbins said:
I keep encountering ERROR -data is corrupted (8002F957) when trying to update my ps3 to rebug 4.86.1 lite.

I Jailbroke my PS3 months ago and haven't played it in a while so i decided bring it out to play again seeing that a new update for rebug was available i downlaoded the pup to update however when i do i keep getting a corrupted error FYI I AM NOT trying to install cfw for the first time i already have done so i am trying to update. Ive downloaded the version of rebug from the site mirror on waybackmachine
CECH-2101A is my model.
Info On Rebug Toolbox: PS3 SYSTEM:Firmware 4.85 LV2 Kernel:CEX Target Type:CEX Cobra 8.2
Info on mmCM PS3 System: Firmware 4.85 [SC-35 | PL3) Firmware Mode: COBRA 8.20 compatible
YES! i have formated the usb stick to FAT32
YES! i have checked the MD5 Checksum on the update file its correct
YES! I have used the right sided usb port and also tried to install on recovery
please help ive been trying to solve this for about an hour with no solution
Click to expand...
You might want to find out whether it is a widespread PUP update problem or not.
You could try just reinstalling your current firmware.
Or you could test any other 4.85 or 4.86 CFW or try downgrading to a lower CFW if QA is enabled.
See if you get the same error or not...

If you manage to install another CFW, try again Rebug 4.86.1.
If you don't because of a constant error (0x8002F957), the problem would be elsewhere, it could be caused by a USB hub, the USB device (try another mbr/fat32 USB stick), a corrupted internal hdd, some console internal hardware problem etc..
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top