PS3 Errors 8002F2C5 , 8002F957 , 8002F225

D

DragooNC

Forum Noob
Hi there!
So, last week when the new HFW 4.86.1 came out and the ps3Exploit page tools got updated, I did a few Ps3 models with the exploit and installed on all of them Rebug 4.86.1 Lite flawlessly.

Now today, i wanted to cfw a CECHL04 and a CECH2004A, but ran into problems.
First of all, I used the same usb stick with the exact same files on all of these consoles, never had any problems.
Second, I always format all hard drives on a pc first, then use them in the Ps3.
I install OFW 4.86 first, install HFW 4.86.1 twice like recommended, then use the ps3exploit sites new tool to patch the flash and then dump the flash, beforehand i delete all cache/ cookies.
I check the dump in the newest version of Ps3 dump checker and it says OK, but asks me if I want to patch it?
Then I restart the console and try to install Rebug 4.86.1 Lite and it always fails at like 70-72% with error code 8002F2C5 or 8002F957 or 8002F225. I tried it via XMB and recovery mode installation, both with the same outcome. I tried it on both consoles. I tried it with several freshly formatted hard drives, all with the same outcome.

To me it looks like, that the exploits page patch doesn't get applied correctly even though it says SUCCESS, hence the Ps3 dump checker asks me if I want to apply a patch.

Yes, I know that google says these errors have something to do either with the hard drive or usb stick not formatted correctly, but I can assure tha tis not the case since I tested it with several hard drives and formatted the usb stick. I didn't have these issues last week with several Ps3s i did the same way.

So my question, did something change in the new tool set on the page since then and how can i resolve this, because atm I only can run the HEN and am unable to install CFW ?

regards
DragooNC
 
DragooNC said:
Hi there!
So, last week when the new HFW 4.86.1 came out and the ps3Exploit page tools got updated, I did a few Ps3 models with the exploit and installed on all of them Rebug 4.86.1 Lite flawlessly.

Now today, i wanted to cfw a CECHL04 and a CECH2004A, but ran into problems.
First of all, I used the same usb stick with the exact same files on all of these consoles, never had any problems.
Second, I always format all hard drives on a pc first, then use them in the Ps3.
I install OFW 4.86 first, install HFW 4.86.1 twice like recommended, then use the ps3exploit sites new tool to patch the flash and then dump the flash, beforehand i delete all cache/ cookies.
I check the dump in the newest version of Ps3 dump checker and it says OK, but asks me if I want to patch it?
Then I restart the console and try to install Rebug 4.86.1 Lite and it always fails at like 70-72% with error code 8002F2C5 or 8002F957 or 8002F225. I tried it via XMB and recovery mode installation, both with the same outcome. I tried it on both consoles. I tried it with several freshly formatted hard drives, all with the same outcome.

To me it looks like, that the exploits page patch doesn't get applied correctly even though it says SUCCESS, hence the Ps3 dump checker asks me if I want to apply a patch.

Yes, I know that google says these errors have something to do either with the hard drive or usb stick not formatted correctly, but I can assure tha tis not the case since I tested it with several hard drives and formatted the usb stick. I didn't have these issues last week with several Ps3s i did the same way.

So my question, did something change in the new tool set on the page since then and how can i resolve this, because atm I only can run the HEN and am unable to install CFW ?

regards
DragooNC
Click to expand...

A lot of ppl overlook the fact that it's a 2 step process to flash your NOR/NAND flash, it SUCCESSFULLY LOADS the patch then you will have yet again APPLY the LOADED patch to actually flash your NOR/NAND, and then reboot which will grant you the access to CFW.

This process also got me a few times.
 
Last edited:
Maybe it would be better to change that texts to make it more explicit @bguerville
1) Load Patch into PS3 RAM
2) Write Patch to PS3 FLASH chip

What i wrote in bold is like the "target device". Also i added the word "chip" just incase someone have doubts about the meaning of a flash... the word "chip" is a clear indication that you are writing to a hardware component that is soldered in the motherboard
 
Sry folks, but you're not helping in any way.
Like I wrote, I did a lot Ps3 the week before without problems.
I'm now sitting with another CECHG04 here, tried the same way, ended the same way with 8002F2C5 error.
So this is definitely not an error on my end, @bguerville has changed something with the latest build in the toolset.
It doesn't apply the patch even though it says it has !
 
These error codes means (as you already notice):
  • 8002F2C5:
    Error with installing Firmware update. The PUP is not recognised as valid update. (Can be generated by pulling the storage device with the PUP when it is still in checking stage. DANGEROUS!). Or when trying to install MinVerCheck.PUP inmediatly after an hdd replacement in PS3 models with a NOR flash
    Click to expand...

  • 8002F957:
    Error 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)
    Click to expand...

  • 8002F225:
    Error with installing Firmware update. The PUP is not recognised as valid update.
    Click to expand...

Source:

Did you tried to check md5sum of firmware that you want to install?
E.g. for Rebug 4.86.1 LITE: a2c79919cafdbb50ccb5ee9589245380.

EDIT: Mostly when flash memory was not patched you should get only 8002F957...
 
Last edited:
@jolek With any it gives me that error, including ofw hfw cfw.
I'm using toolset
84010a199e2dc518cc464b4a645b9058o.jpg
 
Last edited:
The better proof you can get is by doing a flash dump inmediatly after the patch is written, then scan the dump with an "up-to-date" version of the dump checkers
I mean... a version of the dump checkers able to identify the patch applyed by bguerville toolset

If the patch is identifyed and everything in the dump is correct... then the problems you are reporting doesnt seems to be related with bguerville toolset
 
No idea how many times the patch was applied & if it was applied before getting all those different errors.
But you can tell from the screenshot at least that the 4.86 patch was applied at that particular point, if it hadn't been, the Toolset would not have been able to detect any custom syscalls.
The Toolset called a custom syscall which didn't error out as it does on OFW, which de facto implies that a patched CoreOS, with custom syscalls, in the active ROS was loaded successfully by the system after reboot. With the possible exception of course that HEN was loaded prior to using the Toolset, which would not be a crucial problem but totally pointless.

Verifying a newly made dump with the latest pyps3checker was the best recommendation you could make to dispel any doubts however because the toolset does not modify a single byte outside the ROS regions & we already know that the active ROS was well patched given both the successful system reboot & the detected custom syscalls in the screenshot, I bet you that the inactive ROS region will also validate just fine & have the exact same ROS hash as the active ROS.
The Toolset 1.0.20 release had one single issue with patching (fixed in 1.0.22) but it affected only NAND consoles & could not be confused with another issue given the minimum ffff.ffff fw version in recovery which would not let you install any PUP.

We will see but I think the Toolset patching operation was fine & the problem comes from something else.


##EDIT##
I keep seeing wrong steps taken by users.

1. Deleting browser cache, authentication information or cookies is ALWAYS pointless & potentially problematic in rare cases.
Cache & authentication data should be left alone, they make no difference at all. If anything, deleting cache will slow down the Toolset loading on next run, not exactly a benefit.
Cookies can be deleted safely HOWEVER ONLY under certain conditions, the console must be FRESHLY rebooted & the deletion of cookies must take place BEFORE loading the Toolset for the first time.

2. Never apply a patch twice. You can do it, there is no risk, you could apply it hundred times in a row even BUT there is no point whatsoever. IF the Apply Patch feature ran successfully, validated ok & gave the green light to reboot console, the patch is GUARANTEED to have been applied.
After the patch is applied, FMM extracts the 2 ROS regions again, calculates their respective hashes & compare to the reference hash for the patch file. If all 3 hashes match, it means that the 3 sets of data are identical ie ROS0 = ROS1 = No-fsm Patch. The Toolset will only deem patching a success IF those 3 hashes match otherwise it will indicate a failure. So it is basically impossible to get a false positive or false negative on patching validation. Additionally, FMM GUI is updated after patching so you can see the new hashes of the Flash memory ROS regions & you can verify that they are both equal & match the hash of the patch file too.
3. The Toolset supports CFW, HFW, OFW from 4.82 to 4.86 & there is no need to double install before patching.
4. Whenever there is still a doubt caused by pup installation failing after patching, you should immediately submit a masked idps dump after patching for @esc0rtd3w to check, no point posting text without the data needed for us to help you. A dump is the only way to confirm the patching process validity.
 
Last edited:
DragooNC said:
Hi there!
So, last week when the new HFW 4.86.1 came out and the ps3Exploit page tools got updated, I did a few Ps3 models with the exploit and installed on all of them Rebug 4.86.1 Lite flawlessly.

Now today, i wanted to cfw a CECHL04 and a CECH2004A, but ran into problems.
First of all, I used the same usb stick with the exact same files on all of these consoles, never had any problems.
Second, I always format all hard drives on a pc first, then use them in the Ps3.
I install OFW 4.86 first, install HFW 4.86.1 twice like recommended, then use the ps3exploit sites new tool to patch the flash and then dump the flash, beforehand i delete all cache/ cookies.
I check the dump in the newest version of Ps3 dump checker and it says OK, but asks me if I want to patch it?
Then I restart the console and try to install Rebug 4.86.1 Lite and it always fails at like 70-72% with error code 8002F2C5 or 8002F957 or 8002F225. I tried it via XMB and recovery mode installation, both with the same outcome. I tried it on both consoles. I tried it with several freshly formatted hard drives, all with the same outcome.

To me it looks like, that the exploits page patch doesn't get applied correctly even though it says SUCCESS, hence the Ps3 dump checker asks me if I want to apply a patch.

Yes, I know that google says these errors have something to do either with the hard drive or usb stick not formatted correctly, but I can assure tha tis not the case since I tested it with several hard drives and formatted the usb stick. I didn't have these issues last week with several Ps3s i did the same way.

So my question, did something change in the new tool set on the page since then and how can i resolve this, because atm I only can run the HEN and am unable to install CFW ?

regards
DragooNC
Click to expand...

  1. Nothing was changed on the toolset end
  2. You should not need a USB stick, use HTTPS option to load the patch directly to RAM then apply it to Flash Memory in a second step using the context menu entry.
  3. Formatting HDD is NOT needed. Actually when you suspect a hdd drive, the best is to test another hdd altogether rather than just reformatting.
  4. Installing OFW 4.86 is the only step you need. We DO NOT recommend to install firmware twice anymore, and you only need HFW for PS3HEN use, never for PS3 Toolset use which works on OFW.
  5. You are using the latest PyPS3checker version? This does not offer to patch if using standalone batch file called "drag&drop_your_dump_here.bat".
  6. Post your dumps here (https://www.psx-place.com/threads/bg-toolset-user-issues-and-dump-submissions.28868/) and we can verify your issue!
  7. When the Toolset gives you the green light after loading then applying patch & displays a toast telling you you can reboot the console & install a CFW, it means it has already fully validated the patching, compared all hashes & found all checks successful. There is no point reapplying the patch just in case!
  8. Are you confused as to why NAND patch is much faster than NOR?
NAND Patch Should Take 6 - 8 seconds to apply

NOR Patch Should Take Roughly 1:30 - 1:40 to apply
 
Last edited by a moderator:
esc0rtd3w said:
Formatting HDD is NOT needed. Actually when you suspect a hdd drive, the best is to test another hdd altogether rather than just reformatting.
Click to expand...
Let me add a suggestion that is less radical than formating or replacing the hdd, is something i been doing since lot of time ago, even in OFW
What i use to do inmediatlly before installing a firmware is to enter recovery menu and use the options "restore filesystem" and "rebuild datbase" (in that order, with a reboot in between to enter recovery menu 2 times)

The reason why i do this is because it works as a hdd manteinance task, and also as a hdd safety check
Incase the hdd had some problem the "restore filesystem" is going to fix it (theoretically)
Incase the problem is so huge that cant be fixed, the "restore filesystem" is going to show me a warning... that warning would make me enter in "panic mode" and from that point i know i should not install a firmware with that hdd

In plain words, if the hdd is not able to pass that "restore filesystem" successfully you should not install any firmware with it, because most probably this is going to push you into weird problems
Incase the "restore filesystem" shows a warning, just forget about installing the firmware yet, the priority is to fix the problem in the hdd
 
You must log in or register to reply here.

Similar threads

Back
Top