4.93 EVILNAT (Cobra 8.5)

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

Go to download
Overview Extra info Updates (8) Reviews (4) History Discussion
It's been tried before without success. What was achieved though is to dump a PS2 disc into an ISO and mount it on ps2_netemu for full software emulation.

But ps2_netemu lacks any kind of hardware I/O code in it in order to comunicate with the PS3 other than basic devices (audio, video, CPU, memory cards and controllers), it's pure software on a sandboxed environment.

Forcing the other emulators on non-BC consoles will just not work because there is no PS2 hardware of any kind to comunicate with.

The only thing I can think of is sort of make an hybrid of both PS2 emus, wrapping the hardware calls to their software counterparts. But without the source code and proper knowledge and documentation I find it rather most difficult and not worthy. Not even Sony bothered doing that with the unfinished, bug ridden ps2_softemu.
 
GuilloteTesla said:
It's been tried before without success. What was achieved though is to dump a PS2 disc into an ISO and mount it on ps2_netemu for full software emulation.

But ps2_netemu lacks any kind of hardware I/O code in it in order to comunicate with the PS3 other than basic devices (audio, video, CPU, memory cards and controllers), it's pure software on a sandboxed environment.

Forcing the other emulators on non-BC consoles will just not work because there is no PS2 hardware of any kind to comunicate with.

The only thing I can think of is sort of make an hybrid of both PS2 emus, wrapping the hardware calls to their software counterparts. But without the source code and proper knowledge and documentation I find it rather most difficult and not worthy. Not even Sony bothered doing that with the unfinished, bug ridden ps2_softemu.
Click to expand...

That is some food for thought, we've already ruled out wrapping PS3 calls to a modern API - too much work due to the spaky programming language Sony invented for the PS3, so whatever we do would have to utilise an existing method the PS3 already has fully established. By chance would you happen to know if anyone has tried combining the emulators and simply just adding a launcher window that pops up when a disc is inserted and the user just selects the appropriate emulator? That would seem viable.
 
Ketxxx said:
That is some food for thought, we've already ruled out wrapping PS3 calls to a modern API - too much work due to the spaky programming language Sony invented for the PS3, so whatever we do would have to utilise an existing method the PS3 already has fully established. By chance would you happen to know if anyone has tried combining the emulators and simply just adding a launcher window that pops up when a disc is inserted and the user just selects the appropriate emulator? That would seem viable.
Click to expand...

GuilloteTesla said:
But ps2_netemu lacks any kind of hardware I/O code in it in order to comunicate with the PS3 other than basic devices (audio, video, CPU, memory cards and controllers), it's pure software on a sandboxed environment.
Click to expand...

I am no expert, but if this is accurate about ps2_netemu, it seems like it wouldn't matter if a launcher opened it up as the emulation system still would not have any knowledge of the I/O.

I could be wrong though as I am not a developer / hardware expert.
 
Chubs said:
I am no expert, but if this is accurate about ps2_netemu, it seems like it wouldn't matter if a launcher opened it up as the emulation system still would not have any knowledge of the I/O.

I could be wrong though as I am not a developer / hardware expert.
Click to expand...

The launcher would be a "manual" one, jumping ahead of any autolaunch (to work around the black screen) detecting when a PS2 disc is inserted and allow the user to select themselves ps2_netemu. It would literally be a quality of life improvement saving people with later model PS3s from having to make ISOs. That's the theory anyway, if that's possible or not would take someone chiming in with experience in this area.
 
GuilloteTesla said:
It's been tried before without success. What was achieved though is to dump a PS2 disc into an ISO and mount it on ps2_netemu for full software emulation.

But ps2_netemu lacks any kind of hardware I/O code in it in order to comunicate with the PS3 other than basic devices (audio, video, CPU, memory cards and controllers), it's pure software on a sandboxed environment.

Forcing the other emulators on non-BC consoles will just not work because there is no PS2 hardware of any kind to comunicate with.

The only thing I can think of is sort of make an hybrid of both PS2 emus, wrapping the hardware calls to their software counterparts. But without the source code and proper knowledge and documentation I find it rather most difficult and not worthy. Not even Sony bothered doing that with the unfinished, bug ridden ps2_softemu.
Click to expand...
It would be really nice though if there were a friendly message that says physical discs are not supported instead of a kernel panic.
 
Chubs said:
@Evilnat , when upgrading, the installation failed halfway through (PS3 had reboot and failed there) and I received the following error message. It reboot and tried again, successfully installing the second automatic attempt.

  • Error: An error occured during the update operation. Restart the system and perform the update again. (8002F155)
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Before Update FW: EvilNat 4.91.2 [BETA 1] [PEX]
  • Before Update CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: DEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
    • QA Flags are enabled
Seems like after it auto attempted to update again, everything is working fine. I confirmed that I am on 4.91, Cobra 8.5 in the Cobra menu. Just wanted to drop a note here in case this was unexpected and you needed anything from my device.
Click to expand...
I just had the same error tried to run the [pex] [cex] on a cecha01 with a working bd drive and it threw the same error at me, it did give me the package manager though.
 
Sorry if this has been asked before but I just want clarification. My current version of Cobra says it's CEX, can I use the [PEX] [CEX] update or do I need to wait for the [CEX] version to update? If I need to wait I have no problem waiting, just want to make sure before I screw something up.
 
hello, i want update my ps3 slim with latest cfw evilnat pex (beta3) where i can find md5sum? my is 4042807942de4e1be5a0fbfb50402747 is right?
 
Naxil said:
hello, i want update my ps3 slim with latest cfw evilnat pex (beta3) where i can find md5sum? my is 4042807942de4e1be5a0fbfb50402747 is right?
Click to expand...

Yes, MD5 for PS3UPDAT.PUP of CFW Evilnat 4.91.2 BETA PEX CEX should be 4042807942DE4E1BE5A0FBFB50402747

OmegaN9ne said:
Sorry if this has been asked before but I just want clarification. My current version of Cobra says it's CEX, can I use the [PEX] [CEX] update or do I need to wait for the [CEX] version to update? If I need to wait I have no problem waiting, just want to make sure before I screw something up.
Click to expand...

Yes. PEX can be installed on CEX consoles. D-PEX are intended for consoles DEX or converted to DEX.

PEX is a 4.91 CEX firmware that includes modules from 4.84 DEX ported to 4.91. It allows conversion to DEX and back to CEX.

PEX is the equivalent to Rebug REX for 4.91 with many new features added.
 
Chubs said:
@Evilnat , when upgrading, the installation failed halfway through (PS3 had reboot and failed there) and I received the following error message. It reboot and tried again, successfully installing the second automatic attempt.

  • Error: An error occured during the update operation. Restart the system and perform the update again. (8002F155)
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Before Update FW: EvilNat 4.91.2 [BETA 1] [PEX]
  • Before Update CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: DEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
    • QA Flags are enabled
Seems like after it auto attempted to update again, everything is working fine. I confirmed that I am on 4.91, Cobra 8.5 in the Cobra menu. Just wanted to drop a note here in case this was unexpected and you needed anything from my device.
Click to expand...

Thanks for pointing that out. First time installing CFW (updated from HEN, on 4.90), so I kinda freaked out. Installed successfully on 2nd attempt. Then after the 2nd boot I got an "appropriate system storage was not found" error. Freaked out again, thought it corrupted my SSD. Shut it down and rebooted it again and finally, the Evilnat logo showed up. Everything seems to be in order.

Tried to boot a PS2 game and I get a black screen/no signal however. Gonna look around for a fix.
 
aldostools said:
Yes, MD5 for PS3UPDAT.PUP of CFW Evilnat 4.91.2 BETA PEX CEX should be 4042807942DE4E1BE5A0FBFB50402747



Yes. PEX can be installed on CEX consoles. D-PEX are intended for consoles DEX or converted to DEX.

PEX is a 4.91 CEX firmware that includes modules from 4.84 DEX ported to 4.91. It allows conversion to DEX and back to CEX.

PEX is the equivalent to Rebug REX for 4.91 with many new features added.
Click to expand...
@aldostools Can you tell me if you have a Cecha01? I have the question if you have ever played a Pal PS2 game on it?
 
aldostools said:
Yes, MD5 for PS3UPDAT.PUP of CFW Evilnat 4.91.2 BETA PEX CEX should be 4042807942DE4E1BE5A0FBFB50402747



Yes. PEX can be installed on CEX consoles. D-PEX are intended for consoles DEX or converted to DEX.

PEX is a 4.91 CEX firmware that includes modules from 4.84 DEX ported to 4.91. It allows conversion to DEX and back to CEX.

PEX is the equivalent to Rebug REX for 4.91 with many new features added.
Click to expand...
why evilnat haven't post the md5?
 
Chubs said:
@Evilnat , when upgrading, the installation failed halfway through (PS3 had reboot and failed there) and I received the following error message. It reboot and tried again, successfully installing the second automatic attempt.

  • Error: An error occured during the update operation. Restart the system and perform the update again. (8002F155)
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Before Update FW: EvilNat 4.91.2 [BETA 1] [PEX]
  • Before Update CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: DEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
    • QA Flags are enabled
Seems like after it auto attempted to update again, everything is working fine. I confirmed that I am on 4.91, Cobra 8.5 in the Cobra menu. Just wanted to drop a note here in case this was unexpected and you needed anything from my device.
Click to expand...

@Evilnat , I saw this error again when installing EvilNat 4.91.2 Cobra 8.5 [BETA 3] [PEX]. Same thing happened where halfway through it failed with the below error, it reboot and finished the install after auto attempting it a second time:

  • Error: An error occurred during the update operation. Restart the system and perform the update again. (8002F155)
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Before Update FW: EvilNat 4.91.2 [BETA 2] [PEX] Cobra 8.5
  • Before Update CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: CEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
  • QA Flags are enabled

I am not sure how to validate that it is actually running BETA 3, last time I could tell because Cobra had updated to 8.5 on the system.
 
Chubs said:
@Evilnat , I saw this error again when installing EvilNat 4.91.2 Cobra 8.5 [BETA 3] [PEX]. Same thing happened where halfway through it failed with the below error, it reboot and finished the install after auto attempting it a second time:

  • Error: An error occurred during the update operation. Restart the system and perform the update again. (8002F155)
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Before Update FW: EvilNat 4.91.2 [BETA 2] [PEX] Cobra 8.5
  • Before Update CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: CEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
  • QA Flags are enabled
I am not sure how to validate that it is actually running BETA 3, last time I could tell because Cobra had updated to 8.5 on the system.
Click to expand...
  • Allowed installing of retail PKG on DEX

That's super weird, I was able to successfully flash BETA 3 no problem, however, as mentioned, this was with a full changeover of all options from DEX to CEX beforehand. I have done this consistently since BETA 1, again without issue. I see that in Evilnat's BETA 3 release, it appears as though support was added to flash either way or 'from DEX', however, with these practices in action each time for me on strictly CEX, no issues or errors were encountered at any point throught all BETAs, so has become common practice for me.
Maybe worth a shot... VSH does start out default as DEX, but an easy toggle with XMB option from CEX2DEX options. Give it a try next go and report back, would be curious to know if you still run into issues.

As for confirming BETA 3, you should see your games list sortable in Alphabetical order now,
Or with XML Host enabled, I have noticed that it displays a bit lower in right hand corner this time around.

Recommended settings before flashing PEX:
  • Firmware: 4.91 CEX
  • IDPS: Original
  • TargetID: CEX
  • VSH: CEX
  • XMB Host: CEX
  • Debug Settings: CEX
 
Sighfur said:
  • Allowed installing of retail PKG on DEX
That's super weird, I was able to successfully flash BETA 3 no problem, however, as mentioned, this was with a full changeover of all options from DEX to CEX beforehand. I have done this consistently since BETA 1, again without issue. I see that in Evilnat's BETA 3 release, it appears as though support was added to flash either way or 'from DEX', however, with these practices in action each time for me on strictly CEX, no issues or errors were encountered at any point throught all BETAs, so has become common practice for me.
Maybe worth a shot... VSH does start out default as DEX, but an easy toggle with XMB option from CEX2DEX options. Give it a try next go and report back, would be curious to know if you still run into issues.

As for confirming BETA 3, you should see your games list sortable in Alphabetical order now,
Or with XML Host enabled, I have noticed that it displays a bit lower in right hand corner this time around.

Recommended settings before flashing PEX:
  • Firmware: 4.91 CEX
  • IDPS: Original
  • TargetID: CEX
  • VSH: CEX
  • XMB Host: CEX
  • Debug Settings: CEX
Click to expand...
Honestly I don't even change the xmb mode. It runs on all cex but xmb dex and I don't encounter issues even installing the new firmwares.
Chubs said:
@Evilnat , I saw this error again when installing EvilNat 4.91.2 Cobra 8.5 [BETA 3] [PEX]. Same thing happened where halfway through it failed with the below error, it reboot and finished the install after auto attempting it a second time:

  • Error: An error occurred during the update operation. Restart the system and perform the update again. (8002F155)
  • Model: CHECHA01
  • HDD: Upgraded to 1TB HDD
  • Before Update FW: EvilNat 4.91.2 [BETA 2] [PEX] Cobra 8.5
  • Before Update CEX/DEX: Network > * Custom Firmware Tools > CEX2DEX > Show Information:
    • Firmware: 4.91 CEX
    • IDPS: Original
    • TargetID: CEX
    • VSH: DEX
    • XMB Host: CEX
    • Debug Settings: CEX
  • QA: Network > * Custom Firmware Tools > QA Tools > Check QA Flags
  • QA Flags are enabled
I am not sure how to validate that it is actually running BETA 3, last time I could tell because Cobra had updated to 8.5 on the system.
Click to expand...
As far as this goes, if you get this error which I have once before it reloads and will try installation of the pup that was selected. If it's successful the second time around no need to worry. It won't switch the pup you previously loaded with a different one. Your more than likely on beta 3 if that is indeed the pup you tried to install.id be more worried if it constantly fails and no success
 
bguerville said:
Probably because he released the pup files compressed as rar archives, if the pup is successfully extracted, it cannot be corrupted.
Click to expand...
Ok but when you copy it from pc to usbstick can be.. and i can check md5 on ps3 via file manager. So i do my personal check. If u say that... iam safe
 
bguerville said:
Probably because he released the pup files compressed as rar archives, if the pup is successfully extracted, it cannot be corrupted.
Click to expand...

That's true. However I think the MD5 was not included because at this point it could cause confusion on some users due the large number of releases.
These MD5 are only used as example. They are not the official ones.

307202949BC82F6C3C64417F14384379 4.91 Evilnat PEX 03-09-2024
F57EDE08F6479EE876E9E0405746529C 4.91 Evilnat CEX 03-09-2024
325BDD44F07A813FBBC62062B14D254D 4.91 Evilnat PEX 03-10-2024*
3D9606827C4D92DE38B76E0D82BDE3DB 4.91 Evilnat CEX 03-10-2024*
DDE1994A9340BB10ABC38C687B67F522 4.91 Evilnat PEX 03-10-2024
3D9606827C4D92DE38B76E0D82BDE3DB 4.91 Evilnat CEX 03-10-2024
7C137244CA055D100E161F17C2A85603 4.91 Evilnat CEX[OC] 03-10-2024
40DB7FBD12DF84048DEF9B446CA265B2 4.91 Evilnat CEX[noBD] 03-10-2024
3A5EE7F5BA03904963C84D1628B500E4 4.91 Evilnat CEX[noBD+noBT] 03-10-2024
DDED7920A9E2757C65BCCA0601A8647C 4.91 Evilnat CEX[noBT] 03-10-2024
EBA775CD6802FF9462BACC56FDE4BF42 4.91 Evilnat DEX 03-10-2024
98177D2DEEDF4A71287E611C6722CC48 4.91 Evilnat D-PEX 03-10-2024
31043D25D771D13B5EFDC0C6E2654072 4.91 Evilnat PEX 03-12-2024
A7C82D108BEB5F3C94B3C5BEA6B6AD08 4.91 Evilnat CEX 03-12-2024
41E2FEA77E3678758CA22333C90010F6 4.91 Evilnat DEX 03-12-2024
71E738EFB02C8FB784EE17CEDE68E215 4.91 Evilnat DPEX 03-12-2024
E972E698E1FB2907F0A5DF78FE87BBFC 4.91.2 Evilnat PEX BETA1 03-24-2024
E7E38CCAE1789F9FF7E1424D7956C559 4.91.2 Evilnat D-PEX BETA1 03-24-2024
A3988E6D3C0A7344A5B0E8D430038E04 4.91.2 Evilnat PEX BETA2 03-29-2024
6D2B9EB073776EF73F1F979B749C21A4 4.91.2 Evilnat PEX[noBD] BETA2 03-29-2024
60AC998DA9E7B0C29B783AFBDC783969 4.91.2 Evilnat D-PEX BETA2 03-29-2024
DD1CBF134785ADB33005392AE9D24972 4.91.2 Evilnat D-PEX[noBD] BETA2 03-29-2024
4042807942DE4E1BE5A0FBFB50402747 4.91.2 Evilnat PEX BETA3 04-02-2024
323C2B72585B758183DCF75E560445D3 4.91.2 Evilnat D-PEX BETA3 04-02-2024
 
You must log in or register to reply here.

Similar threads

Back
Top