PS3 4.88.2 Evilnat Cobra (8.3) Custom FirmWare (CFW-CEX) Released

bguerville · Jan 24, 2022

Gelo De Guzman said:
Although, the first steps in the bgtoolset works, the update doesn't work

Several possible causes.

1. USB device not compatible, device fat32 partitioning not compatible (GPT), USB hub, corrupted pup file etc..
2. You loaded the no-fsm patch into the Flash Memory Manager but you forgot to apply it so the console isn't jailbroken.
3. You applied the patch but didn't reboot before trying to install the CFW PUP file, the jailbreak is fully applied only after reboot.

Coro · Jan 24, 2022

aldostools said:
Very nice guides.

It would be nice if you update your guides adding a link the other guide, since both are related.

thanks, Aldo! i will try to remember to do it a little later tonight.

Gelo De Guzman · Jan 24, 2022

devinfriday said:
Seems an issue with the usb drive. Try another one, preferably a smaller one, around >256mb <4gb.

I bought a 16GB Sandisk Cruzer Blade. I thought its an issue before with my 2TB flash drive which is why I bought a smaller one because I read on some forums that PS3s only support 1TB and below

bguerville · Jan 24, 2022

Gelo De Guzman said:
I bought a 16GB Sandisk Cruzer Blade. I thought its an issue before with my 2TB flash drive which is why I bought a smaller one because I read on some forums that PS3s only support 1TB and below

Generally speaking, when you need technical data & specs, you should refer to the wiki.
Regarding HDDs compatibility (internal or external storage), you can get the specs in the wiki HDD section.
https://www.psdevwiki.com/ps3/Harddrive

Gelo De Guzman · Jan 24, 2022

bguerville said:
Several possible causes.

1. USB device not compatible, device fat32 partitioning not compatible (GPT), USB hub, corrupted pup file etc..
2. You loaded the no-fsm patch into the Flash Memory Manager but you forgot to apply it so the console isn't jailbroken.
3. You applied the patch but didn't reboot before trying to install the CFW PUP file, the jailbreak is fully applied only after reboot.

My answers are:
1. I bought a new flash drive; got it to FAT32 format; got it to MBR partition scheme, if the problem is the USB hub, I wonder why because it shows that it works because when I swipe to Music-Video-Photos tab, I see my flash drive shows up and when I try to update it via XMB, it shows the Evilnat CFW update but while on the process of it being copied, just before it loads up the process, it keeps on showing "An error occurred while copying files (80029C55)" which is why I guess the flash drive works but it kept on getting an error while doing an update; the PUP file is not corrupted because I have it downloaded from this thread and I just followed what you guys said to me in this thread which I am thankful for but unfortunately, I still keep on getting errors despite of the smooth process on the bgtoolset.

2. I loaded the no-fsm patch into the Flash Memory Manager and I did apply it so I thought it was jailbroken because I followed the instructions of the links you guys recommended to.

3. I applied the patch and rebooted afterwards, then I tried to install the CFW PUP file via XMB and Recovery/Safe mode but it still kept on giving me the same error.

Gelo De Guzman · Jan 24, 2022

bguerville said:
Several possible causes.

1. USB device not compatible, device fat32 partitioning not compatible (GPT), USB hub, corrupted pup file etc..
2. You loaded the no-fsm patch into the Flash Memory Manager but you forgot to apply it so the console isn't jailbroken.
3. You applied the patch but didn't reboot before trying to install the CFW PUP file, the jailbreak is fully applied only after reboot.

I used Rufus to format my Flash Drive to FAT32 for referrence.

Gelo De Guzman · Jan 24, 2022

bguerville said:
Generally speaking, when you need technical data & specs, you should refer to the wiki.
Regarding HDDs compatibility (internal or external storage), you can get the specs in the wiki HDD section.
https://www.psdevwiki.com/ps3/Harddrive

I don't use HDDs, but I only use Flash Drives for installing the CFW

bguerville · Jan 24, 2022

According to the wiki, the error 0x80029C55 is

Code:

Error occurred while accessing storage media

If you wish to verify the jailbreak status, you could boot into XMB, load the PS3 Toolset again in the browser & look at the top right of the screen once the Toolset has finished loading.
What does it say about custom syscalls?

If it says OFW, it means the no-fsm patch was not applied properly, the console is not jailbroken.

If it says Cobra or CFW, the patch was applied, the console is jailbroken & custom syscalls are installed.

Keep in mind that jailbreak through replacement of official CoreOS with a CFW CoreOS is all the PS3 Toolset patching feature guarantees, any other problem related to PUP installation or whatever is not something the PS3 Toolset can address.

bguerville · Jan 25, 2022

Gelo De Guzman said:
I don't use HDDs, but I only use Flash Drives for installing the CFW

Whether it is a hdd or a stick makes no difference to supported USB mass storage size specs.

Gelo De Guzman · Jan 25, 2022

bguerville said:
According to the wiki, the error 0x80029C55 is

Code:

Error occurred while accessing storage media

If you wish to verify the jailbreak status, you could boot into XMB, load the PS3 Toolset again in the browser & look at the top right of the screen once the Toolset has finished loading.
What does it say about custom syscalls?

If it says OFW, it means the no-fsm patch was not applied properly, the console is not jailbroken.

If it says Cobra or CFW, the patch was applied, the console is jailbroken & custom syscalls are installed.

Keep in mind that jailbreak through replacement of official CoreOS with a CFW CoreOS is all the PS3 Toolset patching feature guarantees, any other problem related to PUP installation or whatever is not something the PS3 Toolset can address.

Oh, it says on Custom Syscalls that it is CFW

Gelo De Guzman · Jan 25, 2022

Is this the Evilnat CFW patched?

bguerville · Jan 25, 2022

Gelo De Guzman said:
Oh, it says on Custom Syscalls that it is CFW

So the PS3 Toolset did its job as expected and your console is currently running on Evilnat 4.88.2 CoreOS (if you are on 4.88).
Your problems are not jailbreak related & I would assume you will experience the same problem with any PUP file, OFW, HFW (which is basically a repacked OFW) or CFW.

If you dump the Flash memory & validate it with the latest pyps3checker tool, the 2 ROS regions should come up as Evilnat 4.88 patched or something like that.

Gelo De Guzman · Jan 25, 2022

bguerville said:
So the PS3 Toolset did its job as expected and your console is currently running on Evilnat 4.88.2 CoreOS (if you are on 4.88).
Your problems are not jailbreak related & I would assume you will experience the same problem with any PUP file, OFW, HFW (which is basically a repacked OFW) or CFW.

Yes, but how do I install HEN from here? I mean, I want to put some games in my PS3 but how do I do that?

bguerville · Jan 25, 2022

Gelo De Guzman said:
Yes, but how do I install HEN from here?

You don't install HEN.
You have to choose, it is either CFW (full jailbreak) or HEN (partial jailbreak), not both.
If you prefer to use HEN, you have to install a HFW 4.88 pup first.
But on a CFW compatible console, it makes little sense to use HEN.

At this stage, you should first eliminate all common causes for USB based firmware update errors, remove all external devices plugged into the ps3, use only the USB stick in rightmost USB port & no USB hub, no disc in BD drive, no BT devices other than the gamepad.
You should verify the integrity of your pup file, check its md5 checksum or whatever.

In recovery mode, check file system then rebuild db to ensure that all of is good there.
Then still in recovery mode try to install the CFW using the system update feature.
If it doesn't work & gives you the same error code, try another USB device just to be sure.
And if you still cannot install, get a different error code or whatever, report here, we can explore other avenues like reformatting the internal hdd.

Gelo De Guzman said:
I mean, I want to put some games in my PS3 but how do I do that?

What do you mean?
What games?
Ps3? Ps2 for emulation? Others?
Do you have retail discs?
PSN pkg files with licenses?
Game backups?
What format? Iso images? Legacy JB folder?

Gelo De Guzman · Jan 25, 2022

bguerville said:
So the PS3 Toolset did its job as expected and your console is currently running on Evilnat 4.88.2 CoreOS (if you are on 4.88).
Your problems are not jailbreak related & I would assume you will experience the same problem with any PUP file, OFW, HFW (which is basically a repacked OFW) or CFW.

If you dump the Flash memory & validate it with the latest pyps3checker tool, the 2 ROS regions should come up as Evilnat 4.88 patched or something like that.

It just said:
******* Getting SDK versions *******
ROS0 : 488.000
ROS1 : 488.000

and no Evilnat CFW

bguerville · Jan 25, 2022

Gelo De Guzman said:
It just said:
******* Getting SDK versions *******
ROS0 : 488.000
ROS1 : 488.000

and no Evilnat CFW

Post the entire log, this quote is not sufficient to identify the CoreOS.

Gelo De Guzman · Jan 25, 2022

bguerville said:
Post the entire log, this quote is not sufficient to identify the CoreOS.

This is the entire log:

PyPS3checker v0.11.x. Check log.
Checked file : D:\dump.hex
******* Getting flash type *******
Flash type : NOR
Reversed : NO
******* Getting SKU identification datas *******
idps = 0x09
metldr0 = 0xE890
metldr1 = 0x0E85
metldrkey = 0xBC78B8F02879A81184A0DA74
bootldr0 = 0x2F13
bootldr1 = 0x2F13
bootldrsize = 0x2F170
Matching SKU : OK
CECH-20xxx (DYN-001)
Minimum version 2.70
******* Getting SDK versions *******
ROS0 : 488.000
ROS1 : 488.000
******* Checking first_region_header *******
001.01 First Region Header 0x00 Filled Area 0 : OK
001.02 First Region Header Magic : OK
001.03 First Region Header 0x00 Filled Area 1 : OK
******* Checking flash_format *******
002.01 Flash Format String : OK
002.02 Flash Format Version : OK
002.03 Flash Format 0xFF Filled Area : OK
******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg0 Offset - Length : OK
003.11 trvk_prg0 Name : OK
003.12 trvk_prg1 Offset - Length : OK
003.13 trvk_prg1 Name : OK
003.14 trvk_pkg0 Offset - Length : OK
003.15 trvk_pkg0 Name : OK
003.16 trvk_pkg1 Offset - Length : OK
003.17 trvk_pkg1 Name : OK
003.18 ros0 Offset - Length : OK
003.19 ros0 Name : OK
003.20 ros1 Offset - Length : OK
003.21 ros1 Name : OK
003.22 cvtrm Offset - Length : OK
003.23 cvtrm Name : OK
003.24 Flash Region Table 0x00 Filled Area : OK
******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK
******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK
******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK
******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK
******* Checking Revokation_region *******
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.02 trvk_prg0 0xFF filled area : OK
008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2E0
MD5 = E537DE954DCF25D4DE961DF44549BAF7
Version = 3.50 (from PUP)
008.04 trvk_prg1 0xFF filled area : OK
008.05 trvk_pkg0 SCE : OK
008.06 trvk_pkg0 0xFF filled area : OK
008.07 trvk_pkg1 SCE : OK
008.08 trvk_pkg1 0xFF filled area : OK
******* Checking CoreOS_region *******
009.01 ROS0 Header : OK
009.02 ROS0 Hash : OK
Size = 0x6FFFE0
MD5 = EA9F81A031A7B6701560B3501712DF1A
Version = 4.88 CEX Patched (Evilnat based)
009.03 ROS0 unused 0xFF Filled Area : OK
009.04 ROS1 Header : OK
009.05 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = EA9F81A031A7B6701560B3501712DF1A
Version = 4.88 CEX Patched (Evilnat based)
009.06 ROS1 unused 0xFF Filled Area : OK
******* Checking cvtrm_region *******
010.01 Pre cvtrm 0xFF Filled Area : OK
010.02 cvtrm0 Header : OK
010.03 cvtrm0 0xFF Filled Area : OK
010.04 vtrm0 Magic : OK
010.05 vtrm0 Reserved Entries : OK
010.07 cvtrm1 Header : OK
010.08 cvtrm1 0xFF Filled Area : OK
010.09 vtrm1 Magic : OK
010.10 vtrm1 Reserved Entries : OK
******* Checking Second_Region_Header *******
011.01 Second Region Header 0x00 Filled Area 0 : OK
011.02 Second Region Header Magic : OK
011.03 Second Region Header Count : OK
011.04 Second Region Header 0x00 Filled Area 1 : OK
011.05 Second Region Unknown Block 0 : OK
011.06 Second Region Header 0x00 Filled Area 2 : OK
011.07 Second Region Unknown Block 1 : OK
011.08 Second Region Header 0x00 Filled Area 3 : OK
******* Checking Unreferenced_Area *******
012.01 unreferenced area 0xFF Filled : OK
******* Checking CELL_EXTNOR_AREA_Region *******
013.01 CELL_EXTNOR_AREA Header : OK
013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 : OK
013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 : OK
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : OK
013.05 CELL_EXTNOR_AREA 0x00 Filled Area 3 : OK
013.06 CELL_EXTNOR_AREA 0xFF Filled Area 0 : OK
013.07 CELL_EXTNOR_AREA 0x00 Filled Area 5 : OK
013.08 CELL_EXTNOR_AREA 0x00 Filled Area 6 : OK
013.09 CELL_EXTNOR_AREA 0xFF Filled Area 1 : OK
******* Checking bootldr_region *******
014.01 bootldr0 : OK
014.02 bootldr1 : OK
014.03 bootldr Rev key : OK
014.04 bootldr Statistics : OK
014.05 bootldr 0xFF Filled Area : OK
******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
CELL_EXTNOR_AREA Hash1 : OK
CELL_EXTNOR_AREA Hash2 : OK
metldr size : OK
vtrm0 : OK
vtrm1 : OK
******* Checking repetitions *******
Header Magic0 Repetitions : OK
asecure_loader Repetitions : OK
eEID Repetitions : OK
cISD Repetitions : OK
cCSD Repetitions : OK
trvk_prg0 Repetitions : OK
trvk_prg1 Repetitions : OK
trvk_pkg0 Repetitions : OK
trvk_pkg1 Repetitions : OK
ros0 Repetitions : OK
ros1 Repetitions : OK
cvtrm Repetitions : OK
******* Additional information *******
HDD : Hitachi HTS545025B9SA00 090915PB4208QSKA67BH
MAC address : 00:24:8D:C0:20:54
CID : 0x00010077C738
eCID : 01C52002E20A370E1D0D5F4200000000
board_id (part of console S/N) : 27453973
kiban_id (board barcode) : 3HG14647437G
******* Checks completed *******
Total number of checks = 155
Number of dangers = 0
Number of warnings = 0
All checks done in 8.30 seconds.
----------------------------------------------------------------------------
| IMPORTANT NOTICE ! |
| Checks of late CECH-25xxx, CECH-3xxxx and CECH-4xxxx consoles dumps still |
| under development and may return false results. If you feel it's the case, |
| please post your *.checklog.txt in a new issue on my github repository: |
| https://github.com/littlebalup/PyPS3tools/issues |
| Thanks! It will help me a lot to improve that tool

|
----------------------------------------------------------------------------

Gelo De Guzman · Jan 25, 2022

bguerville said:
Post the entire log, this quote is not sufficient to identify the CoreOS.

Oh...I see the Checking CoreOS part and it's Evilnat..sorry my bad

bguerville · Jan 25, 2022

No errors, no warnings & as expected, it clearly says for each ROS region where CoreOS is stored:

Code:

Version = 4.88 CEX Patched (Evilnat based)

Like I said the issue is not with the jailbreak, the PS3 Toolset did its job exactly the way it is supposed to.

Gelo De Guzman · Jan 25, 2022

bguerville said:
You don't install HEN.
You have to choose, it is either CFW (full jailbreak) or HEN (partial jailbreak), not both.
If you prefer to use HEN, you have to install a HFW 4.88 pup first.
But on a CFW compatible console, it makes little sense to use HEN.

At this stage, you should first eliminate all common causes for USB based firmware update errors, remove all external devices plugged into the ps3, use only the USB stick in rightmost USB port & no USB hub, no disc in BD drive, no BT devices other than the gamepad.
You should verify the integrity of your pup file, check its md5 checksum or whatever.

In recovery mode, check file system then rebuild db to ensure that all of is good there.
Then still in recovery mode try to install the CFW using the system update feature.
If it doesn't work & gives you the same error code, try another USB device just to be sure.
And if you still cannot install, get a different error code or whatever, report here, we can explore other avenues like reformatting the internal hdd.

When it comes to removing the external devices plugged into the PS3, does it include my controller? it's a wired controller though

PS3 4.88.2 Evilnat Cobra (8.3) Custom FirmWare (CFW-CEX) Released

bguerville

Coro

Gelo De Guzman

bguerville

Gelo De Guzman

Gelo De Guzman

Gelo De Guzman

bguerville

bguerville

Gelo De Guzman

Gelo De Guzman

bguerville

Gelo De Guzman

bguerville

Gelo De Guzman

bguerville

Gelo De Guzman

Gelo De Guzman

bguerville

Gelo De Guzman

Similar threads

Featured content

Trending content

Latest posts