4.93 EVILNAT (Cobra 8.5)

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

After successfully updating to BETA 6 4.91.2 I was reading the release notes, and noticed it says you can downgrade straight to 3.55 CFW. Would this be the REBUG 3.55 downgrader release, which then allows you to drop further back again? I'm interested in going back to the earliest my console allows, which is lower than 3.55.


Sent from my iPhone using Tapatalk
Sorry if i ask but, why u want downgrade? I think with qa flag you can it... but why?
 
Sorry if i ask but, why u want downgrade? I think with qa flag you can it... but why?

Because I'm running an experiment, and I've got some interesting results from 4.55 up to 4.66. So now I want to see what the case is earlier than this.

My results and findings with be put up here once I'm finished, but I need time and support to do what I'm doing.

I just need advice to my questions to allow me to do what I want to achieve.


Sent from my iPhone using Tapatalk
 
After successfully updating to BETA 6 4.91.2 I was reading the release notes, and noticed it says you can downgrade straight to 3.55 CFW. Would this be the REBUG 3.55 downgrader release, which then allows you to drop further back again? I'm interested in going back to the earliest my console allows, which is lower than 3.55.


Sent from my iPhone using Tapatalk

On CFW with QA flags enabled you can downgrade to 3.55 directly, if your console has factory FW 3.55 or below (PS3 FAT, Slim 2000, Slim 2100 and some early Slim 2500 can have FW 3.55).
 
On CFW with QA flags enabled you can downgrade to 3.55 directly, if your console has factory FW 3.55 or below (PS3 FAT, Slim 2000, Slim 2100 and some early Slim 2500 can have FW 3.55).

My console is earliest 3.40. So do I downgrade to 3.55 REBUG, then down to 3.40 OFW after that?


Sent from my iPhone using Tapatalk
 
Thanks. I'll try that then. Just like last time, this is just temporary, and I'll be coming back up to the last again (which is where I am now). Are there any tricks I need to know using REBUG? Never used it before. Is the mechanism to go lower with REBUG 3.55 straight forward enough?


Sent from my iPhone using Tapatalk
 
On CFW with QA flags enabled you can downgrade to 3.55 directly, if your console has factory FW 3.55 or below (PS3 FAT, Slim 2000, Slim 2100 and some early Slim 2500 can have FW 3.55).
My slim is 2.40. Minvercheck tell me that. But why we cant go below? Is useless for normal user ok, i want know for curiosity
 
My slim is 2.40. Minvercheck tell me that. But why we cant go below? Is useless for normal user ok, i want know for curiosity

Downgrade security checks. With the PS3, newer models were not manufactured to support previous FW version features. For example, the Slim models do not support OtherOS from factory, and that is reflected on the FW version 3.20 that removes that feature completely.

Bear in mind that it's not expected for common users to downgrade. Just another tool for aiding Sony's technicians in repairing consoles.
 
My slim is 2.40. Minvercheck tell me that. But why we cant go below? Is useless for normal user ok, i want know for curiosity

What is this "Minvercheck", is that another tool, the same as using PS3Toolset? I'm going off the sysinfo.log from PS3Toolset. It has the line "Minimum Applicable Firmware Version: 3.40" on my console. I take it that this is the same applicable number and that I don't need to use this other "Minvercheck" tool? (Wherever one gets that from?)
 
What is this "Minvercheck", is that another tool, the same as using PS3Toolset? I'm going off the sysinfo.log from PS3Toolset. It has the line "Minimum Applicable Firmware Version: 3.40" on my console. I take it that this is the same applicable number and that I don't need to use this other "Minvercheck" tool? (Wherever one gets that from?)
MinVerChk is an offline tool that poses as a system update. It can be "installed" on any PS3. The installation will always fail, but the error message will display the minimum firmware version your PS3 supports. Yes, it would be the same as what ps3toolset reports. The only advantage that MinVerChk has over ps3toolset in that regard is that it's an offline tool, so it might be useful if you plan on buying a 2nd hand PS3 and want to verify whether it's CFW compatible before purchase.

You cannot downgrade below the factory firmware version (i.e. the version reported by ps3toolset / MinVerChk) because the bootloader an/or SYSCON verify the minimum version requirement on each boot, and attempting to force downgrade to an old version would result in a brick. Even if a method were found to bypass this check, newer models have newer hardware, which may not be supported in older firmware, so even on a technical level it won't work.
 
Afaik, the minverchk pup uses your idps to determine base firmware, because I seem to remember a couple of devs mention the base firmware changed after changing their idps. It will still brick I think, but minverchk relays the wrong info. Isn't the idps in eid0 and eid5, and changing it only changes it in one of them? Bgtoolset I think reads both to prevent that problem. Is that right???
 
Hi! I'm a bit of a newbie with this type of CFWs. I followed a tutorial to install 4.91.2 DEX on my PS3 and everything went fine. Now I have updated it to 4.91.2 BETA 6 D-PEX (latest release) and the CEX2DEX tools menu has dissapeared. Could anyone help me?

Some information that may help:
- When I turn on my PS3, it says I'm on 4.91 PEX Cobra 8.5
- When checking Cobra, it says I have DEX Cobra 8.5 installed

Thanks!
 
not sure if this is from Beta 6 (CEX) or its cause i replaced the internal Drive w/ an SSD, but i JUST had a complete lockup (had to hard power cycle by power switch) upon inital restart, it took forever to load to only give me internal storage not found, power cycled again and waited 30 seconds to get back in w/ the "there were issues the last time this device was used." error.

checked logs/syscon logs only errors i see were 2022 errors and thats cause of the Capture card i have connected. (( the System froze-mid stream on twitch.))

It's a common issue on SSD drives.

beta 6: DVD & Blu-ray movies do not auto play. Games do auto play. Turning the auto play setting on and off did not work. not much else I can think to add.
Thanks.

Switch you vsh to CEX.

I have to ask stupidly, does anyone happen to have the 4.84 DEX firmware?

Real 4.84 one? is not available for the public, but, you can grab the HFW 4.84 DEX + HEN 4.84 Modules and build a 4.84 DEX from it.

Hi! I'm a bit of a newbie with this type of CFWs. I followed a tutorial to install 4.91.2 DEX on my PS3 and everything went fine. Now I have updated it to 4.91.2 BETA 6 D-PEX (latest release) and the CEX2DEX tools menu has dissapeared. Could anyone help me?

Some information that may help:
- When I turn on my PS3, it says I'm on 4.91 PEX Cobra 8.5
- When checking Cobra, it says I have DEX Cobra 8.5 installed

Thanks!

@Evilnat
 
Last edited by a moderator:
Hi! I'm a bit of a newbie with this type of CFWs. I followed a tutorial to install 4.91.2 DEX on my PS3 and everything went fine. Now I have updated it to 4.91.2 BETA 6 D-PEX (latest release) and the CEX2DEX tools menu has dissapeared. Could anyone help me?

Some information that may help:
- When I turn on my PS3, it says I'm on 4.91 PEX Cobra 8.5
- When checking Cobra, it says I have DEX Cobra 8.5 installed

Thanks!
CEX2DEX Tools are available only on PEX and D-PEX, try to test BETA 7 (posted below)

CFW Evilnat 4.91.2 [BETA 7] released

ONLY FOR PS3s COMPATIBLE WITH CFW

Changelog
  • Re-compiled LV2 Kernel
  • Re-compiled Cobra stage2
  • Added support for third party BT headset

Uploaded PEX/D-PEX/CEX and DEX, if everything is fine and working I will upload noBD and Overclock variants

Please reply with your feedbacks, Thanks!

Download: https://mega.nz/folder/8Y9SBKKY#cJCrpOL-FAEuPkAxrVeiAA
 
This is awesome - coming from Hen on a 2501a Slim and it works great! However I have probably some stupid questions:
1. Currently I'm forgoing the BD drive entirely but not using the noBD firmware (using OC). It still works but I'm curious the difference - do some models NEED the noBD but mine doesn't?
2. What advantages does non-cex have over cex if any besides debugging etc?
 
Back
Top