PS3 OFW 4.86 to CFW 4.86.1 gives 8002F957 error at 70%

A

Axxx

Forum Noob
Hi all,

I am new to this, so forgive me for all the newbie mistakes. Other post do not apply to my situation as far as I can tell.
I have a FAT PS3 CECHG04, which has been 'altered' in the past.
Installed is the OFW 4.86 which installed fine some time ago.
When installing CFW (Rebug lite 4.86.1) i get the famous 8002F957 error.
Tried it several times (reboot, clean stick, new download) but the same result.

I don't know how to move on.

To verify my PS3 I used PyPs3Checker to analyse my dump, and there is a: Danger at vtrm

vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEB94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEBE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)

Could this be related?

Any help is appreciated, before I completely brick the device :)
 
Axxx said:
Hi all,

I am new to this, so forgive me for all the newbie mistakes. Other post do not apply to my situation as far as I can tell.
I have a FAT PS3 CECHG04, which has been 'altered' in the past.
Installed is the OFW 4.86 which installed fine some time ago.
When installing CFW (Rebug lite 4.86.1) i get the famous 8002F957 error.
Tried it several times (reboot, clean stick, new download) but the same result.

I don't know how to move on.

To verify my PS3 I used PyPs3Checker to analyse my dump, and there is a: Danger at vtrm

vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEB94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEBE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)

Could this be related?

Any help is appreciated, before I completely brick the device :)
Click to expand...


OFW without modification does NOT allow installation of CFW.... 99% of the time you get that error when trying to install CFW... it's because you didn't patch to allow custom firmware. That being said, be happy you didnt, because flashing a dump with errors WILL give you a brick.

That was one of many steps you've missed.
Here's a good toolset to work with: https://www.psx-place.com/threads/u...ion-of-tools-fueled-by-new-ps3-exploit.28658/
 
psykosis said:
OFW without modification does NOT allow installation of CFW.... 99% of the time you get that error when trying to install CFW... it's because you didn't patch to allow custom firmware. That being said, be happy you didnt, because flashing a dump with errors WILL give you a brick.

That was one of many steps you've missed.
Here's a good toolset to work with: https://www.psx-place.com/threads/u...ion-of-tools-fueled-by-new-ps3-exploit.28658/
Click to expand...

Thank you for your very swift reply!! Much appreciated.
After the first failure I started with the above mentioned toolset based upon this how-to video.
Which then led to the vtrm-error in the Dump. But I can't find the next step for this error...
What's the next step to take on this one, before continuing with who-to/toolkit?
 
Axxx said:
Thank you for your very swift reply!! Much appreciated.
After the first failure I started with the above mentioned toolset based upon this how-to video.
Which then led to the vtrm-error in the Dump. But I can't find the next step for this error...
What's the next step to take on this one, before continuing with who-to/toolkit?
Click to expand...

I don't use random videos. A known valid working toolset for what you are trying to accomplish is here: https://www.psx-place.com/threads/u...ion-of-tools-fueled-by-new-ps3-exploit.28658/

A video for 4.85 was done by mrmario that may be more helpful.
 
psykosis said:
I don't use random videos. A known valid working toolset for what you are trying to accomplish is here: https://www.psx-place.com/threads/u...ion-of-tools-fueled-by-new-ps3-exploit.28658/

A video for 4.85 was done by mrmario that may be more helpful.
Click to expand...

Thanks again for the help. I used your proposed video and did all the steps, including updating 2 x in recoverymode.
At 26 minutes into the video it's time to check the dump.hex. and that gives the same Danger again.

******* Checking datamatches *******
per console nonce : OK
metldr size : OK
vtrm header datas : OK
vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEB94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEBE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)

The instructions specifically say it should be without. What can and should I do?
 
Axxx said:
Thanks again for the help. I used your proposed video and did all the steps, including updating 2 x in recoverymode.
At 26 minutes into the video it's time to check the dump.hex. and that gives the same Danger again.

******* Checking datamatches *******
per console nonce : OK
metldr size : OK
vtrm header datas : OK
vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEB94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEBE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)

The instructions specifically say it should be without. What can and should I do?
Click to expand...

From searching around it looks like RSOD issue, but i could be wrong. There are fixRSOD things that can be done, but I don't want to recommend it until it's verified that's the case.

Hey @esc0rtd3w might have a suggestion, or know someone that could chime in perhaps? :)
 
Axxx said:
Hi all,

I am new to this, so forgive me for all the newbie mistakes. Other post do not apply to my situation as far as I can tell.
I have a FAT PS3 CECHG04, which has been 'altered' in the past.
Installed is the OFW 4.86 which installed fine some time ago.
When installing CFW (Rebug lite 4.86.1) i get the famous 8002F957 error.
Tried it several times (reboot, clean stick, new download) but the same result.

I don't know how to move on.

To verify my PS3 I used PyPs3Checker to analyse my dump, and there is a: Danger at vtrm

vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEB94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEBE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)

Could this be related?

Any help is appreciated, before I completely brick the device :)
Click to expand...
did you use the BG Toolset to patch it yet?

cause if not, then yeah as @psykosis said, you cant just install CFW over OFW and will receive some error trying to install it on PS3, without being patched

that vtrm issue i am not sure of how it got corrupted or exactly how it affects firmware installs? old linux leftovers or RSOD (as stated by @psykosis)?

idk @Joonie @bguerville @habib @littlebalup may know the implications
 
esc0rtd3w said:
did you use the BG Toolset to patch it yet?

cause if not, then yeah as @psykosis said, you cant just install CFW over OFW and will receive some error trying to install it on PS3, without being patched

that vtrm issue i am not sure of how it got corrupted or exactly how it affects firmware installs? old linux leftovers or RSOD (as stated by @psykosis)?

idk @Joonie @bguerville @habib @littlebalup may know the implications
Click to expand...

Hi esc0rtd3w and psykosis,

Thanks both for the help! Much appreciated.
As mentioned, the patch has not yet been applied. In the suggested video, I came to the part where you flash the PS3 twice from the recovery mode with the HFW, which works, then got to the toolset, created the dump, and as suggested tested that with PyPS3Checker.
At this part the hashes data does not match and the Checker reports a error.

I have had my consule HW jailbroken in the past (years ago!) but since then update with several new OFW's without issues.
On RSOD, I have never had one... The only 'issue' lately is the PS3 reporting: "playing BD's on this device is not allowed" but games and all the other stuff work like a charm.

If someone could comment on the VTRM issue, that would be great. I could then continue with the toolset :)
 
Axxx said:
Hi esc0rtd3w and psykosis,

Thanks both for the help! Much appreciated.
As mentioned, the patch has not yet been applied. In the suggested video, I came to the part where you flash the PS3 twice from the recovery mode with the HFW, which works, then got to the toolset, created the dump, and as suggested tested that with PyPS3Checker.
At this part the hashes data does not match and the Checker reports a error.

I have had my consule HW jailbroken in the past (years ago!) but since then update with several new OFW's without issues.
On RSOD, I have never had one... The only 'issue' lately is the PS3 reporting: "playing BD's on this device is not allowed" but games and all the other stuff work like a charm.

If someone could comment on the VTRM issue, that would be great. I could then continue with the toolset :)
Click to expand...
You should try installing the nobd Rebug pup Joonie posted on the forum https://www.psx-place.com/threads/modified-rebug-4-86-1-lite-for-broken-ps3-nobt-nobd-rsod.28922/

Once cfw installed you can try the rsod fix in cfw tools to fix vtrm

EDIT #1:
If you already have Rebug installed you can just try the rsod fix directly

EDIT #2:
If you are still on OFW, then you can use the toolset to patch and then install Rebug from there
 
Last edited:
esc0rtd3w said:
You should try installing the nobd Rebug pup Joonie posted on the forum https://www.psx-place.com/threads/modified-rebug-4-86-1-lite-for-broken-ps3-nobt-nobd-rsod.28922/

Once cfw installed you can try the rsod fix in cfw tools to fix vtrm

EDIT #1:
If you already have Rebug installed you can just try the rsod fix directly

EDIT #2:
If you are still on OFW, then you can use the toolset to patch and then install Rebug from there
Click to expand...

Hi Guys!
I really, really appreciate the time you take to help me! But I am stuck on a few things.

I followed the linkt to the nobd pup, but there is no instruction how to. So I used the approach via the recovery menu.
This results in a Error 8002F2C5

Edit#1: Nope, I am trying to install (and may have installed) the HFW installed during the above mentioned video.

Edit#2: If I am going to use the bgtoolset to install Rebug, what's the difference from above.
I would still have the vtrm Danger to deal with right? Or am i missing something.
 
Axxx said:
Hi Guys!
I really, really appreciate the time you take to help me! But I am stuck on a few things.

I followed the linkt to the nobd pup, but there is no instruction how to. So I used the approach via the recovery menu.
This results in a Error 8002F2C5

Edit#1: Nope, I am trying to install (and may have installed) the HFW installed during the above mentioned video.

Edit#2: If I am going to use the bgtoolset to install Rebug, what's the difference from above.
I would still have the vtrm Danger to deal with right? Or am i missing something.
Click to expand...
use the toolset.
make a backup of flash
patch your flash
reboot
install Rebug CFW
then fix your vtrm with CFW Tools under network
 
You must log in or register to reply here.

Similar threads

Back
Top