4.93 EVILNAT (Cobra 8.5)

PS3 4.93 Evilnat w/ Cobra v8.5 - (CEX/PEX/D-PEX) 4.93

Finally, after several days of reverse engineering, the online CFW update also works on CEX. This will allow you to select the CFW, download it, and install it

DEX
HegGqjZ.jpeg

CEX
vP6EzsP.jpeg

I will post the results after testing it with all versions
 
Finally, after several days of reverse engineering, the online CFW update also works on CEX. This will allow you to select the CFW, download it, and install it

DEX
HegGqjZ.jpeg

CEX
vP6EzsP.jpeg

I will post the results after testing it with all versions

Amazing!, well done Nat, good job!.

One question: where are stored the different PUP files?, are they on a public GitHub repo, for example?. And if so, can we edit the URL to point somewhere else? (I'm thinking like a local web server or NAS).
 
Amazing!, well done Nat, good job!.

One question: where are stored the different PUP files?, are they on a public GitHub repo, for example?. And if so, can we edit the URL to point somewhere else? (I'm thinking like a local web server or NAS).

The update server can be set via vsh.self or through debug settings (xregistry) on DEX. I'm not sure if NAT patched it on CEX to also read from the registry instead of vsh.

Additionally, you can use webMAN's ps3update-list.txt to provide the PUPs
 
hi

we need to wait an new firmware verson after ul post the results ? thank you for your work :) a 4.92.1 ?
 
Last edited:
Do you want the color of the wave image when updating the CFW to be different colors to distinguish which variant is being installed (CEX/PEX/D-PEX)?

Blue (Default) = CEX
Purple = PEX
Green = D-PEX
Red = Overclock

bJadKlK.jpeg

geEcODr.jpeg

2NfQxxx.jpg
Anyone can create any image they want, not only the wave. I only changed the color of the wave because I don't want to waste time creating one when I can use it to research other things
 
Last edited:
Anyone can create any image they want, not only the wave. I only changed the color of the wave because I don't want to waste time creating one when I can use it to research other things

Amazing feature Nathan! These images look good.
I think it would be helpful if you add a small text in a corner that says CEX, PEX, DEX or D-PEX.

I find it is not very intuitive to identify the FW type just by the colors.
 
Amazing feature Nathan! These images look good.
I think it would be helpful if you add a small text in a corner that says CEX, PEX, DEX or D-PEX.

I find it is not very intuitive to identify the FW type just by the colors.
I did it, but I can only put the text in the bottom corners. The PS3 uses the image from the middle down, but I think each TV loads the image differently, making the text partially or completely invisible. I can research how to reverse-engineer it with ASM if possible

nQQJhm4.jpeg

The text is in the most upper right, but the PS3 loads it at the middle. I don't think the text will fit exactly in the corner, it depends on the resolution and how much image the PS3 loads
 
I did it, but I can only put the text in the bottom corners. The PS3 uses the image from the middle down, but I think each TV loads the image differently, making the text partially or completely invisible. I can research how to reverse-engineer it with ASM if possible

nQQJhm4.jpeg

The text is in the most upper right, but the PS3 loads it at the middle. I don't think the text will fit exactly in the corner, it depends on the resolution and how much image the PS3 loads

How did you do that? changed the image inside emer_init.self ?
 
I did it, but I can only put the text in the bottom corners. The PS3 uses the image from the middle down, but I think each TV loads the image differently, making the text partially or completely invisible. I can research how to reverse-engineer it with ASM if possible

nQQJhm4.jpeg

The text is in the most upper right, but the PS3 loads it at the middle. I don't think the text will fit exactly in the corner, it depends on the resolution and how much image the PS3 loads

Maybe it could be possible to replace the internal PNG resource in the ELF with one different but smaller.

For instance the PNG in the attachment is the extracted image edited with the text hard coded and saved as 8-bit PNG, so the new image is 75KB instead of 170KB.

IMG2.PNG


EDIT:
This is one has the text moved below the wave. Maybe it looks better since the image is aligned to the bottom of the screen.
IMG.PNG
 
Last edited:
Maybe it could be possible to replace the internal PNG resource in the ELF with one different but smaller.

For instance the PNG in the attachment is the extracted image edited with the text hard coded and saved as 8-bit PNG, so the new image is 75KB instead of 170KB.

View attachment 45864

EDIT:
This is one has the text moved below the wave. Maybe it looks better since the image is aligned to the bottom of the screen.
View attachment 45865
Exactly, that's how I did it. You can modify or create a new image and save it as a PNG, but the size can't exceed the original image size (170KB and 26,9KB)

My modified images was exported as an 8-bit PNG with 99.7KB and 18,8KB

Also remember to replace the current PNG data and size with the current one:

ps3swu.self/ps3swu2.self 4.92
  • OFFSET: 0xAA74B4
  • ORIGINAL: 0x0002AB84
  • REPLACE: Current PNG size
  • OFFSET: 0xAA74EC
  • ORIGINAL: 0x00006BBC
  • REPLACE: Current PNG size
PNG data location
  • 1920x540: 0xADD874
  • 640x180: 0xB083F8
ps3swu2.self has the same data as ps3swu.self but it uses a different key revision (0x01 and 0x0D)
 
Last edited:
Exactly, that's how I did it. You can modify or create a new image and save it as a PNG, but the size can't exceed the original image size (170KB and 26,9KB)

My modified images was exported as an 8-bit PNG with 99.7KB and 18,8KB

Also remember to replace the current PNG data and size with the current one:

ps3swu.self/ps3swu2.self 4.92
  • OFFSET: 0xAA74B4
  • ORIGINAL: 0x0002AB84
  • REPLACE: Current PNG size
  • OFFSET: 0xAA74EC
  • ORIGINAL: 0x00006BBC
  • REPLACE: Current PNG size
PNG data location
  • 1920x540: 0xADD874
  • 640x180: 0xB083F8
ps3swu2.self has the same data as ps3swu.self but it uses a different key revision (0x01 and 0x0D)

Thanks for sharing it ;)

I already made some tests and it looks cool

Btw what is ps3swu2.self for? Different model Super slims (emmc) ?
 
Hi can i ask how do install .rap and .edat. The problem is that PSNpatch 2017 is that it does notstall anything and gets stuck does not work with the latest
evilnat but when downgrade the lower version it works. I want ask the creator of evilnat to add built in application to allow use to install these files. Can this be done or should i stick to old version but i cant seem to find old verion?
 
Last edited:
Hi can i ask how do install .rap and .edat. The problem is that PSNpatch 2017 is that it does notstall anything and gets stuck does not work with the latest
evilnat but when downgrade the lower version it works. I want ask the creator of evilnat to add built in application to allow use to install these files. Can this be done or should i stick to old version but i cant seem to find old verion?
In xai_plugin there is an option to install rap files in [Custom Firmware Tools > Cobra Tools > Create license]. It will create RIF licenses from rap files from an USB device in "x:\exdata" to your current exdata user folder

I don't know about edat files, can you tell more about them please?
 
will the update give the option to cross-flash between CEX and PEX ?
i'm not sure if thats a good thing or not - maybe set it with a flag or something?
 
Back
Top