4.93 EVILNAT (Cobra 8.5)

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

Anyone experiencing video settings return to 576p when powering on console, then getting the HDMI cable was found, do you want to change the settings?

I get that a lot, last times. I switched to 4.86 rebug lite for a few days and I don't have this issue anymore
not so far i do use a hdmi 2.1 cable and it goes really good at 1080p and 720p on gaming on latest 4.92.2 CFW from evilnat
 
Hi, i updated my ps3 from 4.91 to 4.92, and now driver san Fransisco doesn't work. It just gets stuck at a black screen. It's the same copy i played on 4.91 firmware. I deleted cache and all game files, rebuilt data base and fixed system files, and i installed the game again. It just stuck on black screen with this new update.

Update: it seems using webman mod, the game only works if it's in folder format. Converting to iso will give you black screen.
 
Last edited:
its weird so far im actually playing it on 4.92.2 and goes really good, i do use multiman mod though due to that on webman mod it takes 9mb of my available 64mb of ram when im using it

hi @Evilnat i was wondering maybe on a future xai plugin release, its possible that you can add an auto#2 profile from fan speed, maybe the same one or similar as webman mod? this one it goes really good to control temps without leaving fan speeds too high to cooldown the ps3, or maybe do you know if there is a similar profile that i can choose that does the same without using webman mod? i do ussually use the one from max temps at 65C on my ps3 slim 2101B, thanks a lot, i will look foward on your response
 
Last edited by a moderator:
I'm in huge trouble and need some help:

In the past, I successfully jailbroke my PS3 slim with Evilnat 4.91 CFW and the console worked perfectly.

Today, I wanted to update to version 4.92 and assumed that this could be done easily via System Settings -> Software Update.

The update was successfully downloaded and the installation process started normally.

However, when the update reaches about 69-70%, an error message appears stating that the update could not be installed and the process was canceled (error code 8002F334).

When I turn the console off and on again by holding down the power button, the update starts from the beginning but stops again at the same point.

I also tried to boot into the recovery menu (hold down the power button until you hear two short beeps) to install the previous Evilnat 4.91 CFW via USB stick. But that doesn't help; the console automatically restarts with the update instead of displaying the recovery menu.

What can I do?


Edit:
Never mind, i was able to save myself by taking out the harddisk and repormat it via PC. After that i was able to install the official PS3 4.92 firmware, apply the the exploit, and install Evilnat 4.92.2. So everything is working again, alltought i have to install all my apps and games again. But that's the smaller issue than a bricked PS3 console :P
 
Last edited:
Hi
I was wondering if anyone else has experienced lag or issues loading certain PS3 games, or if the system has ever frozen to the point where you had to unplug the power cord. I feel like this version might have some issues that cause the console to struggle at times.
 
Hi
I was wondering if anyone else has experienced lag or issues loading certain PS3 games, or if the system has ever frozen to the point where you had to unplug the power cord. I feel like this version might have some issues that cause the console to struggle at times.
yeah, sometimes i do have some lag issues, so far for the moment my ps3 is under a delid process, lets hpe that everything goes fine, but yep, i remember that sometimes my ps3 freezes on 4.92, i would like to leave it on 4.86.1 rebug lite as far as i do play offline games only
 
I don't know if this is a known feature, but it was new to me, so I thought I'd share.

The software update utility can load multiple firmware files from a USB drive. This is originally a DEX feature, but in the latest Evilnat version, it has been enabled to work in both CEX and DEX modes. Just place the files in the following directory:

PS3/SEARCH/

The files can have any name, and the .PUP extension is not required.

Additionally, you can log errors that occur during the update process. To do this, simply create a directory at /PS3/UPDATE/LOG/. A file named NET_ERR_LOG.txt will be created there if any errors are found.

Xwlz9o7.png
 
Last edited:
The overclock with txt didn't work for me idk why I did everything and put it in dev_hdd0 root but still get the same freq

Something i found really interesting. The OC margin seems to be reduced considerably on the new firmware for me.
I could do 800/975 before the update fine. Now i get crashes if i go over 750/900
I got the same problem I was using 700/900 on the last update now it causes artifacts on the xmp and froze my system right after the startup once
 
Last edited by a moderator:
The overclock with txt didn't work for me idk why I did everything and put it in dev_hdd0 root but still get the same freq


I got the same problem I was using 700/900 on the last update now it causes artifacts on the xmp and froze my system right after the startup once

Maybe webMAN MOD is replacing the clock speeds, try to set it to default in setup.ps3
 
Maybe webMAN MOD is replacing the clock speeds, try to set it to default in setup.ps3
Nah I managed to get it working U just have to but another line under the clocks (press enter) anyways the problem with the clocks speeds still persist my console can't handle the same clocks I had to revert back to the old version and now everything is fine
 
For more information and make things clear it's a 25xx slim tsmc rsx I am running at 700/900 on evilnat 4.92.1 when I use the new verison with either changing clocks from xmb or the new txt cobra feature I get artifacts on the xmb and even sometimes freeze straight after boot @cha0shacker is having a similar problem I guess

Mine can go up to 1000 on Core just fine, either via LV1patch , cobra LV1 poke, or webMAN, more than that the icons start to "melt" (really funny) when the rsx reaches 71C
 
Some discs can be dumped perfectly but only in encrypted form, as the console is unable to read their decryption keys for some reason - and they spit out 80010514. I figure hijacking the console's decryption process for real discs with xai's in case there's a valid key file could make them work.

Hello, I came to ask about this.
I'm running the latest 4.92.2 - I still have original copies of my games, but went cfw route (mainly) to have them always handy on my hdd.
I'm experiencing an issue with [BLES-00779] - (Battlefield Bad Company 2 LE). This game refuses to start with 80010514 error - directly starting from optical media.

When I dump the game using MultiMan (Create ISO), and try to start it, it complains about 8001001.

This is the only game I'm experiencing issues with.

Could you have a look into this / what would be the proper place to report such bug.

I've double checked, and verified my pristine disc by running it on stock (ofw) console of my friend.

Edit: running ManaGunZ - Extract DECrypted ISO...
"RESULT: Something went wrong: 'Error: failed to get_keys'"
 
Last edited:
Back
Top