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
Hi guys!! I hope it's simple to be solved my problem, and someone can help me. Well then. The following happens, I have a ps3 fat console, one of the last models before the slims, regardless of whether I spend 6 hours playing or just 1 hour, when I press the ps button to turn off the console, it turns off everything, including the red light, making it impossible to turn the console on again, both by control and by button on the console itself, in this case, I have to turn off the console using the switch on the back of it and turn it back on, then the front led lights up again, being able to turn on the console, both by control , how much, per console. Everything works, wifi, bluetooth, blu-ray drive, in short, everything, the only problem is when you turn it off, it erases everything, having to turn it off and on again using the little key behind the console. Is it some eviknat bug on fat consoles? Did it happen to someone who has fat? Any tips to help me, without having to take some technical assistance?
Thank you very much in advance.
 
TioJoaoGamer71 said:
Everything works, wifi, bluetooth, blu-ray drive, in short, everything, the only problem is when you turn it off, it erases everything, having to turn it off and on again using the little key behind the console. Is it some eviknat bug on fat consoles?
Thank you very much in advance.
Click to expand...

I suspect something hardware related rather than something in CFW itself. I have Phat CECHG and CECHM units, both working without problems on Evilnat 4.90.
 
hi, i have a ps3 slim cech 2504A with ofw 4.89, my lowest downgradeable to 3.40, i have a E3 flasher can i patch my nand dump with
PS3DumpChecker and then go to cfw 4.90, or do i have to go to ofw 4.90 first and then patch de dump???
thanks
 
You don't need to fiddle with the E3 flasher at all. You can just update to 4.90 ofw and then use the bgtoolset to be able to install a CFW
 
I have three ps3, one superslim on hen , one fat on CFW , the thirld on CFW just died of YLOD
(ps3 is my passion i could buy all consoles today if i want).
I like evilnat 4.90 cfw A LOT but on my console it losing controler conection often mostly after i open the console , and always after i play PS2 games.
Doesnt happen on REBUG so is not the console. It would be great if that would be fixed.
 
cha0shacker said:
Losing it before and after PS2 games is normal.
But what do you mean with "open the console"?
Click to expand...
I am losing it the way that i got to use the cable to relink the controler to the console. Sometimes the PS3 button open the console and the console just break the link with the controler and again i got to use the cable.
 
japonezul said:
I am losing it the way that i got to use the cable to relink the controler to the console. Sometimes the PS3 button open the console and the console just break the link with the controler and again i got to use the cable.
Click to expand...
That's indeed weird and then sadly outside of my expertise.
 
aldostools said:
You first need to disable CFW syscalls to log into PSN. You can purchase or download content on the PSN store. This is generally safe to do, but there is not guarantee of no ban. Only Sony knows who or when to ban.

You can purchase content also using the web version of the PSN store.

Use your main PSN account only to download content and a new account to play online.
That way if your console and account get banned, you don't lose your purchased content.

Other recommendations for CFW users are:
Never use auto login or auto update while using PSN or HEN.
Don't execute homebrews while connected to PSN.
Disconnect from PSN if you are not using playing or using a service that requires it.
Be careful re enabling CFW syscalls. Log off before create the syscalls. Reboot is recommended.
Keep a low profile while playing online.
Don't use cheats or game mods online.
Click to expand...

thank you so much for the information. some people also suggested to delete the history before logging in. good or bad? and how about trophy syncing? is that a good idea also?

and i also have a webman related question for you. is it possible to disable the abort message when playing music at startup? btw thank you 1000 times for working so hard on this thing. the ps3 3 scene wouldn't be what is is without people like you
 
BillyRene said:
thank you so much for the information. some people also suggested to delete the history before logging in. good or bad? and how about trophy syncing? is that a good idea also?

and i also have a webman related question for you. is it possible to disable the abort message when playing music at startup? btw thank you 1000 times for working so hard on this thing. the ps3 3 scene wouldn't be what is is without people like you
Click to expand...

The history is always deleted when a game is mounted through webMAN MOD.
If the game is a PSN game or mounted through another backup manager, the history may haven't be deleted.

The message 'Starting music / Press O to abort' is now not shown if the music is disabled at startup. Optionally you can compile a custom version with that message in www_start.h

About your question about trophies... my personal opinion is that the trophies are useless.
 
Last edited:
aldostools said:
The history is always deleted when a game is mounted through webMAN MOD.
If the game is a PSN game or mounted through another backup manager, the history may haven't be deleted.
Click to expand...
ok thank you good to know

aldostools said:
The message 'Starting music / Press O to abort' is now shown if the music is disabled at startup. Optionally you can compile a custom version with that message in www_start.h
Click to expand...
sorry but i don't undertsand. you said it is now shown if the music is disabled at startup? i have the music enabled at startup and the message is showing. is it it possible to disable the message while still playing the music at startup?

aldostools said:
About your question about trophies... my personal opinion is that the trophies are useless.
Click to expand...
:biggrin2:
 
BillyRene said:
sorry but i don't undertsand. you said it is now shown if the music is disabled at startup? i have the music enabled at startup and the message is showing. is it it possible to disable the message while still playing the music at startup?
Click to expand...
It was a typo. I mean the message it is NOT shown if music is disabled at startup.
 
@Evilnat
just a question, but have you tried PS2 emu on backwards compatible models? I have read by coincidence on psxtools from versed users, that they couldn't run PS2 isos on a CECHC and the PS3 just shuts down when switching lpar
 
haxxxen said:
hm, I see. too bad, when you cannot try for yourself...erm which version of PEX are you running? I think they were using the CEX counterpart
Click to expand...
Hi, I created a custom firmware using MFW Builder, I changed the lv1.self file using lv1 overclocked file. But when I updated my ps3 with this custom update.pup I got an ylod on 90% or after complete update, i dont know what happend because i was in my kitchen. Yes, It isn't very good to see a CECHC04 dying. I have been read the syscon but the errors code are always the same every time that I try to power on the system and read it, what does I mean is that the Syscon isn't able to create new error. Undestend what i say? I check voltage ripple on RSX_VDDC(1.32v here) and BE_VDDC(1.16v here) with oscilloscope and every thing is right. I can't start recovery mode. What happend guys? Maybe I bricked my ps3?
 
DarlanZ said:
Hi, I created a custom firmware using MFW Builder, I changed the lv1.self file using lv1 overclocked file. But when I updated my ps3 with this custom update.pup I got an ylod on 90% or after complete update, i dont know what happend because i was in my kitchen. Yes, It isn't very good to see a CECHC04 dying. I have been read the syscon but the errors code are always the same every time that I try to power on the system and read it, what does I mean is that the Syscon isn't able to create new error. Undestend what i say? I check voltage ripple on RSX_VDDC(1.32v here) and BE_VDDC(1.16v here) with oscilloscope and every thing is right. I can't start recovery mode. What happend guys? Maybe I bricked my ps3?
Click to expand...
oh my, PLEASE DO NO EXPERIMENTS with this tool without any flasher and also without knowing what you are doing. it is bricked it seems and from the sounds of it, you have just replaced the coreos file and not patched it directly. without any flasher, you won't be able to revive

dunno, but does the "firmud" cmd works also on a retail PS3 for mullion syscon @M4j0r ?
 
M4j0r said:
No, it only works on the CXR F models if the chip is in backup mode. Retail CXR chips do have the command, but the flash controller is missing since there's no flash.
Click to expand...
I see, so hardware limitation here. thanks for clarifying. maybe adding note to devwiki?

I am thinking about adding "flasher" nag screens to mfwbuilder now, to be sure no random experiments will happen again
 
You must log in or register to reply here.

Similar threads

Back
Top