PS3 4.88.2 Evilnat Cobra (8.3) Custom FirmWare (CFW-CEX) Released

solomonbyte · Nov 30, 2021

"""everything is working fine else, except when you leave the console idle for long enough,
the screen turns black and it locks up completely. """

---> exactly the same.

+ this cfw hard crash console randomly when updating games.

this is really not trusty cfw. no offence to the job done, just factual.

i recommand to downgrade to something better.

aldostools · Nov 30, 2021

For the users experiencing random lock ups, I suggest to use the debug cobra (selectable in CFW Tools menu) and run socat on the PC to log the real cause of the error.

Without that log information it is impossible to help or fix any bug for future releases.

solomonbyte · Nov 30, 2021

Errors are not reproducible, all is random.

i launched mlb 16 and idle for 5min time to check something online on computer and the console bipped 3 short times and instant shutdown herself. followed with red blinking after until i press power to totally turn led off. 1st time ever the console it happened. NEVER DID THIS BEFORE.

this firmware is unstable in ways i'm unable to help.

Aldo, thank you, but you already made a list of issues and we still do not have any revision from him for what you underlined. in page 112 of the thread.

really sad because the way the tools were available to fake on xmb any psn account was genius.

Life is give and take :/

solomonbyte · Nov 30, 2021

GRRRRRRRRRRRR

Please, give me the modified command line from this one

Code:

socat udp-recv:18194 stdout

to write a .log file (i am on windows)

and if possible, display in same time than recording to file, so i can check the recording is active

solomonbyte · Nov 30, 2021

ok, update: your socat is pointless with this command

Code:

 socat udp-recv:18194 stdout

console makes reproducible crash on mlb16, ird rebuilt :

MLB The Show 16 - [BCUS 01089]
size: 23 275 503 616 bytes
md5 of iso : 486B1588810A3E28305795026F07B323
game updated from internet at 1st launch, then full 10gb data on HDD installed.

Now i got an entry point of the trigger,
1) simply launch the game and let it run from main menu, no button pressed.
2) console ends couple minutes later instant shut down, red blinking. regular, faster than 1 pulse/Sec..

3) pressing power normally does nothing. have to stay 1 full sec, to ear 1 bip, that terminate the console so red led becomes permanently on.

4) another simple press will turn console on again.

5) on restart console requests HDD scan.
* disk is SSD 120gb 840 samsung - ( console never crashed on overflow 4.85 ) drive is healthy

the log end with this informations:

[...]
open_path /dev_hdd0/tmp/wm_request
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/HeadFaceCacheFile
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/MLBPS3_GD.WAD
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/MLBPS3_GD.WAD
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/MLBPS3_GD.WAD
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/MLBPS3_GD.WAD
open_path /dev_hdd0/tmp/wm_request
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/MLBPS3_GD.WAD
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/MLBPS3_GD.WAD
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/PXP_SAVE.BIN
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/PXP_SAVE.BIN
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/PA_SAVE.BIN
open_path /dev_hdd0/game/BCUS01089_R/USRDIR/PA_SAVE.BIN
open_path /dev_bdvd/PS3_GAME/USRDIR/SNDPS3/SOUND/CROWD_REACTIONS.SKX
open_path /dev_hdd1/replays
open_path /dev_hdd0/game/BCUS01089/USRDIR/PATCH_GD.WAD

which is just a behavior of readen files, nothing about the system by itself?
if you have more tools for me to test...

console is not heating, i completed GT6 last month and past 2 months i did last of us.
i've done the cleaning job when i get it, range 30-40% fan on webman, average 68°.
tested couple minutes ago at constant 50% fan, T° = 55°, and BAAAM instant power off.
so this is not heat related.

from this point i don't see what else it can be. all what remain is downgrade to rebug 86 lite or 84.2 or overflow 85 then check, but i'm pretty sure it will fix the crash.

common point of my earlier GT6 freezes and the mlb 16 instant off is the fact that there is no input from the gamepad at all ( rest on table ) and console is idling.

--- model 2004B; which have not been tested on the list :p hihihi
webman mod version 1.47.36 full

STLcardsWS · Nov 30, 2021

There is always an expectation that something will not work 100% bug free in a hobby community. There is always going to be a bug somewhere or with something. Happens all the time. If you expect something to always run 100% in every scenario and for every setup you are expecting way to much. Billion dollar companies have trouble with this, my educated guess would say a hobby developer would have some difficulty covering every scenario to create a 100% bug free environment

What's great about most of these dev's here is that you can politely report something and when they have time. they are usually more then willing to try and find the issue. Especially if its something that has been reported by many. But they also have lives and are not on stand by to provide a fix. There is 1,000's of variables and without you even knowing i would not throw shade at something, Keep in mind a revision or a fix is not a right its a privilege and that is something the user's must understand in the community more.. Its a community of idea's , not a service or a product..

solomonbyte · Nov 30, 2021

remember me how many people have sent socat report lately ? my memory is failing.

STLcardsWS · Nov 30, 2021

aldostools · Nov 30, 2021

@solomonbyte if the system is crashing without a kernel error or some other error log, it will be hard to identify the cause.

If your system is more stable using Rebug, then use that CFW until a fix is found (which could never happen due the cause of these shutdowns is still unknown).

bguerville · Nov 30, 2021

Like I said before it would be perfectly normal to experience unexpected issues given the number of new features & new code introduced in this CFW, it would have been a miracle otherwise.

Technically speaking, there can be many sources of problems in any CFW, configuration/setup specificities, conflicts between specific apps or custom mods, unofficial game repacks etc...

Now assuming those things are not the problem and that the hardware is not malfunctioning (hdds are known to be a very common source of issues but other hardware parts are also critical) or not officially supported (hdd > 1.5Tb, ssd..), we can basically divide the remaining potential CFW issues in 4 categories according to their origin.

1. Patches in firmware files (self/sprx) if one or more of them is found to be source of problems (quite possible with certain patches, Nat knows what he is doing but in some cases patches can have unforeseen consequences), it should eventually be identified & fixed but in the meantime there is not much a user can do except provide error reports with as much details & socat debug output as possible.

2. Cobra, one of the most probable cause of issue I suppose, not just because by nature, it is a sensitive part of the CFW but also because I think Nat added a fair amount of new code in it.

However it should be easy enough to disable Cobra (using CFW Tools or manually renaming stage2.bin to stage2.bin.bak in /dev_flash/sys & rebooting is enough) & then you could try to use Mamba (current or older version) instead.
Use the Mamba Loader to test Mamba & if everything works well, install the Mamba Autoloader & Mamba will load automatically at boot time.
If Mamba solves your problem, don't forget to report a Cobra related problem with appropriate details in this thread.

3. xai_plugin related problems are not the most likely because xai_plugin should only be running when CFW Tools xmb items are used in theory but anyway, if ever xai_plugin crashes when you use it, you should get a lv2 crash output in the socat log, post it here.

4. Apps (wMM, sMan or other resident plugins), an app could have problems dealing with the new features of this CFW & may need updated. Turn off all resident plugins (rename /dev_hdd0/boot_plugins.txt) & reboot, see if you still get crashes. Like for xai_plugin, a resident plugin crash should be logged to socat, post it here.

All reports are welcome & helpful as long as they include enough details to investigate and even if they don't seem to be addressed right away however Nat has not been around for some time now, we hope he is alright & just busy with life. He may or he may not be back & interested to update his work, but either way, nobody should rely on him alone to sort out all the issues that may be reported about his CFW release.

CFWs have always been experimental, a slow accumulation of patches & custom source code, a kind of long term project with multiple contributors.
This CFW Cobra source & xai_plugin source have both been released on github, and if Nat is unavailable, it is up to others to take up the flag & do their part, improve existing code, fix errors, and if anyone with a hardware flasher wants to build a better custom firmware, everything needed is at their disposal, tools, data, info, source code & extra help can be found among our members, all in all, making a CFW has never been easier than it is today & ironically there are fewer made than ever.

bguerville · Nov 30, 2021

And btw for those users wanting to post their socat output to report an issue, here is a possible socat command to log the broadcasted data to a file (named "cobra_dbg.log" for the purpose of this example) rather than to the terminal display (stdout).

Code:

socat -u UDP-RECV:18194 CREATE:cobra_dbg.log

On Windows, you can just copy this command into a new batch file (.bat) in the socat folder & double click the batch file when you wish to start logging.

solomonbyte · Dec 1, 2021

new informations:

rebug 4.86.1 / webman mod 1.47.36 / SSD/ game updated / game data installed : Crash
evilnat 4.88.2 / webman mod 1.47.36 /SSD / game updated / game data installed : Crash
evilnat 4.88.2 / webman mod 1.47.36 /HDD / game updated / game data installed : Crash
evilnat 4.88.2 / webman mod 1.47.36 /SSD / game v1.0 / game data installed : Crash

if crash not happen from the " press start " to demo loading on v1.0 , and the demo plays along for long time, quitting the demo, reverting to game menu and letting the demo loading again will trigger the crash.

i joined a log of ssd version crash. nothing special except the last call is not data from HDD/SSD but ISO :

open_path /dev_bdvd/PS3_GAME/USRDIR/MLBPS3_ROM.WAD

i just don't know what happen on this particular game but i'm pretty sure there is something wrong. i will start test with no webman, it is last common factor known to me.

it is not overheat, nor drives, not network, not ps3netserver ( i got gui issue on win10 but still hosting files and whole process works fine, so i do not think about this, otherwise i would happen on all games.

i don't know.

but I Apologize to Evilnat suspicion since other firmware gives same result.
beg for your pardon on that point.

i Also Thanks Bguerville for the command line. I could not find exemple on google and the -h is very poorly explained for amateurs.

--------

i am unloading webman from memory and copying iso to internal to use multiman / irisman /managunz and try something else.

will also try to off cobra & try mamba ( i never used, dunno yet how to proceed, learning on the fly )

aldostools · Dec 1, 2021

solomonbyte said:
rebug 4.86.1 / webman mod 1.47.36 / SSD/ game updated / game data installed : Crash
evilnat 4.88.2 / webman mod 1.47.36 /SSD / game updated / game data installed : Crash
evilnat 4.88.2 / webman mod 1.47.36 /HDD / game updated / game data installed : Crash
evilnat 4.88.2 / webman mod 1.47.36 /SSD / game v1.0 / game data installed : Crash

if crash not happen from the " press start " to demo loeading, and the demo play along for any time, quitting the demo with game pad, reverting to game menu and letting the demo loeading again will trigger the crash

It could be a memory conflict (maybe the game demand too much memory or maybe an incorrect setting in webMAN MOD).

I suggest to disable all background VSH plugins and mount the game using IRISMAN, multiMAN or ManaGunZ, to determine if the issue is caused by webMAN MOD or any other plugin.

In addition to the 4 categories mentioned by @bguerville, the customizations can be another source of frequent problems:
- Some themes (p3t) cause random bugs
- Non-official fonts may cause random crash
- Large amount games generate big XMLs that consume more memory than the allowed.
- Big images used for icons cause issues.

I'm not saying that it's your case. I'm only adding other possible causes of freeze/shutdowns/black screens that frequently are overseen.

solomonbyte · Dec 1, 2021

i edited my message, i think i am trying to do what you suggested. i dont have technical lexical

but

- Large amount games generate big XMLs that consume more memory than the allowed.

hmmmmmmmmmmmmmmm

i cannot deny that. i am in a kind of extreme situation on that point. the console keep xml gamelist on ram when playing a game ? i tought it was a file reading on menu only and that was not residual. serious hint here.

bguerville · Dec 1, 2021

If the game files are all legit & the issue persists even without wMM loaded (using whatever other backup manager to mount it), you might want to narrow the range of possibilities, it might be worth trying that game with Managunz or Irisman, after disabling Cobra & rebooting.
To do this test, you should not really need to install Mamba separately, Irisman & Managunz should have some mamba based payloads included for iso mounting afaik.
And unless you are curious to test, I think you should only need to install Mamba system wide if you find that Cobra is the culprit..

solomonbyte · Dec 1, 2021

new tests:

evilnat 4.88.2 / webman mod unloaded / multiman mounted / SSD / game 1.0/ game data installed : Crash

then :

cobra disabled, rebooted, then disabling webman from memory crash console.
trying to uninstall webman mod while cobra disabled also crash console

evilnat 4.88.2 / webman mod uninstalled / cobra OFF / managunz 1.4 / SSD / game 1.0/ game data installed : crash
evilnat 4.88.2 / webman mod uninstalled / cobra OFF / irisman 4.88 / SSD / game 1.0/ game data installed : crash

mounting internal iso with irisman or managunz will display on cobra info in the xmb v8.4. both cobra based ?

GuilloteTesla · Dec 1, 2021

@solomonbyte, can you try running this game on OFW?. Just to discard if your crashes are CFW related or not.

Checkity_CheckYoSelf · Dec 1, 2021

solomonbyte said:
new tests:

evilnat 4.88.2 / webman mod unloaded / multiman mounted / SSD / game 1.0/ game data installed : Crash

then :

cobra disabled, rebooted, then disabling webman from memory crash console.
trying to uninstall webman mod while cobra disabled also crash console

evilnat 4.88.2 / webman mod uninstalled / cobra OFF / managunz 1.4 / SSD / game 1.0/ game data installed : crash
evilnat 4.88.2 / webman mod uninstalled / cobra OFF / irisman 4.88 / SSD / game 1.0/ game data installed : crash

mounting internal iso with irisman or managunz will display on cobra info in the xmb v8.4. both cobra based ?

Couldn't hurt plugging in the HDD into a pc and checking the health with Crystal disk or something just to eliminate that as a potential issue for your crashes.

I can only speak to my experience with this firmware, and for me once the freezes started to occur in the XMB on Evilnat 4.88, it did not matter what firmware I downgraded to, the freezing issues would persist until I re-formatted the HDD at that point.

solomonbyte · Dec 1, 2021

i have filmed with phone the led of the console.

console turn off fan and the led is yellow for 200-300ms then the bip occur while going red.

i checked file written on drive, all md5 are ok. so the hardware general failure must be really hardware and have nothing to do with any cfw related.

the last element is that console is like 10 years old, and just like a computer, some games will keep PSU 12v line in the standard, above 11.4v. but some will draw and the reel power cannot be read with the shitty software sold with mobo, we must use fast numerical multimeter with min-max function to see the dip and in my case my computer psu was going 11.0 and crash occured with 10.9v. with the min value.

i suspect the console to behave the same. it must be electrical.
many post here i discover talk about same phenomen :

https://www.psx-place.com/threads/ps3-shuts-off-and-red-light-starts-blinking.20983/page-2
https://www.psx-place.com/threads/cecha-ps3-ylod-saga.20826/page-2#post-140116
https://www.psx-place.com/threads/p...y-beep-or-light-on-cut-off-electricity.13604/

i will rip the case and start electrical checks to confirm my theory.

solomonbyte · Dec 1, 2021

to be precise on what happen with the console, if i play the game, there is no crash at from MLB 16. the gag is the console will proceed to general hardware failure security with the shutdown blinking but the game itself playing is ok.

the moment is very fast, but i extracted 4 pics, showing the game loading a demo at 11.859v
the console stop emitting display output, meaning the problem already happened somewhere and the voltage is still 11.859. THEN i have a fast step to 11.364, then other measures are lower because of dischargin psu.

measure is taken at output of PSU.

so many people on youtube having this issue. it must be electrical.

the difference with a classic YLOD is that YLOD wont allow power resume. for me, i just have a 1 fast press to terminate powering off process, then another simple power press make console fresh again as if nothing never happened, excepted warning about hdd cause system halt but it never corrupt drive anyway.

i am stopping report here i'll transfer to Ylod forum section.

PS3 4.88.2 Evilnat Cobra (8.3) Custom FirmWare (CFW-CEX) Released

solomonbyte

aldostools

solomonbyte

solomonbyte

solomonbyte

STLcardsWS

solomonbyte

STLcardsWS

aldostools

bguerville

bguerville

solomonbyte

Attachments

aldostools

solomonbyte

bguerville

solomonbyte

GuilloteTesla

Checkity_CheckYoSelf

solomonbyte

solomonbyte

Attachments

Similar threads

Featured content

Trending content

Latest posts