4.93 EVILNAT (Cobra 8.5)

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

I believe Luan is referring to reverting debug settings such as toggling "improper shutdown warning" and or any other manual revisions once installed. Basically, revert all changes back to original that you had made, if you didn't change anything, just ensure you have changed back to CEX for debug settings. Not to beat a dead horse here, but I have never had the flash memory error through all 5 Beta iterations and thats been by ensuring all settings are reverted back to CEX beforehand, even XMB mode / VSH , 'CEX' across the board. Downgrading, or upgrading. :sfun deadhorse:

Can someone please help this chap with his question? I don't know the answer either.
LOL! The dump.bin is required for truly bricked situations or when all other methods of recovery have subsequently failed, and to the point of requiring a hardware flasher, usually a last ditch effort, AFAIK. There are some pieces of software for both windows and linux which allow you to rescramble, however, this process can vary dependent upon NOR/Nand and your console model. In most cases with soft bricks you can still access recovery and reinstall CFW or OFW or recover partition that is corrupted by rebuilding the database, and in some cases by removing cmos and a cold restart. Its just good to have a solid dump.bin in the back pocket. As for using the legendary toolset, I would have to defer you to someone with more experience in this area for manually manipulating flash files. Some great info here & here. I hope this helps. If anyone would like to add to my newb summary, please do, and I appreciate all of the support!
 
I believe Luan is referring to reverting debug settings such as toggling "improper shutdown warning" and or any other manual revisions once installed. Basically, revert all changes back to original that you had made, if you didn't change anything, just ensure you have changed back to CEX for debug settings. Not to beat a dead horse here, but I have never had the flash memory error through all 5 Beta iterations and thats been by ensuring all settings are reverted back to CEX beforehand, even XMB mode / VSH , 'CEX' across the board. Downgrading, or upgrading. :sfun deadhorse:


LOL! The dump.bin is required for truly bricked situations or when all other methods of recovery have subsequently failed, and to the point of requiring a hardware flasher, usually a last ditch effort, AFAIK. There are some pieces of software for both windows and linux which allow you to rescramble, however, this process can vary dependent upon NOR/Nand and your console model. In most cases with soft bricks you can still access recovery and reinstall CFW or OFW or recover partition that is corrupted by rebuilding the database, and in some cases by removing cmos and a cold restart. Its just good to have a solid dump.bin in the back pocket. As for using the legendary toolset, I would have to defer you to someone with more experience in this area for manually manipulating flash files. Some great info here & here. I hope this helps. If anyone would like to add to my newb summary, please do, and I appreciate all of the support!

Thank you so much for the reply! I really do appreciate it. I seem to be struggling to get attention from people on my various posts and subjects, and I'm not sure why. I'll check out your links next available chance i get. Thanks again for taking the time to answer me, and appreciate my continued sense of humour (despite my frustrations!) :-)
 
I believe Luan is referring to reverting debug settings such as toggling "improper shutdown warning" and or any other manual revisions once installed. Basically, revert all changes back to original that you had made, if you didn't change anything, just ensure you have changed back to CEX for debug settings. Not to beat a dead horse here, but I have never had the flash memory error through all 5 Beta iterations and thats been by ensuring all settings are reverted back to CEX beforehand, even XMB mode / VSH , 'CEX' across the board. Downgrading, or upgrading. :sfun deadhorse:


LOL! The dump.bin is required for truly bricked situations or when all other methods of recovery have subsequently failed, and to the point of requiring a hardware flasher, usually a last ditch effort, AFAIK. There are some pieces of software for both windows and linux which allow you to rescramble, however, this process can vary dependent upon NOR/Nand and your console model. In most cases with soft bricks you can still access recovery and reinstall CFW or OFW or recover partition that is corrupted by rebuilding the database, and in some cases by removing cmos and a cold restart. Its just good to have a solid dump.bin in the back pocket. As for using the legendary toolset, I would have to defer you to someone with more experience in this area for manually manipulating flash files. Some great info here & here. I hope this helps. If anyone would like to add to my newb summary, please do, and I appreciate all of the support!

Already did and I still have it. Sorry, but what do you mean by "flash memory error" and what does it have to do with my problem?
 
Last edited:
No, but I also have it in [BETA 5].

I thought PS3 games would only work if burned to BD-Rs and that every PS3 model could read burned PS2 games.

Will PS3 games burned to CD/DVD get worse graphics?

Can PS1 games be burned to DVD/BR and PS2 games to BR?

Just to simplify the quotes:

Reported Issues:
  1. "when clicking "Enable FTP" in "Cobra Tools" in "* Custom Firmware Tools" if an external HDD is connected to the console."
  2. "Also, now the "Check File System" setting in "Service Tools" in "* Custom Firmware Tools" isn't working. The PS3 just reboots to XMB when clicking it."
Response:

  1. "I already reported the issue to Evilnat. It seems to be caused by setting 'Improper Shutdown Warning' to Off in Debug Settings."
Did you try this? To expand on the response from @CFW-Us3r, did you try this?

Suggestion w/ Steps:
  1. Settings > * Debug Settings
    • If this option is not there, make sure you have PEX version installed and VSH is set to DEX
      • This can be checked under Network > * Custom Firmware Tools > CEX2DEX Tools > Show Information (PEX specific menu item).
      • To enable VSH DEX (if set to CEX): Network > * Custom Firmware Tools > CEX2DEX Tools > Toggle XMB Mode and restart your PS3.
  2. 45th Option: Improper Shutdown Warning: Set this to off.

I have not verified any of this, just going off what CFW-Us3r suggested earlier. See if adjusting that setting solves your problems with FTP / Check File System Settings options.
 
Just to simplify the quotes:

Reported Issues:
  1. "when clicking "Enable FTP" in "Cobra Tools" in "* Custom Firmware Tools" if an external HDD is connected to the console."
  2. "Also, now the "Check File System" setting in "Service Tools" in "* Custom Firmware Tools" isn't working. The PS3 just reboots to XMB when clicking it."
Response:

  1. "I already reported the issue to Evilnat. It seems to be caused by setting 'Improper Shutdown Warning' to Off in Debug Settings."
Did you try this? To expand on the response from @CFW-Us3r, did you try this?

Suggestion w/ Steps:
  1. Settings > * Debug Settings
    • If this option is not there, make sure you have PEX version installed and VSH is set to DEX
      • This can be checked under Network > * Custom Firmware Tools > CEX2DEX Tools > Show Information (PEX specific menu item).
      • To enable VSH DEX (if set to CEX): Network > * Custom Firmware Tools > CEX2DEX Tools > Toggle XMB Mode and restart your PS3.
  2. 45th Option: Improper Shutdown Warning: Set this to off.

I have not verified any of this, just going off what CFW-Us3r suggested earlier. See if adjusting that setting solves your problems with FTP / Check File System Settings options.

I no longer have 1 and it doesn't have to do with 2.

@CFW-Us3r never talked about clicking "Show Information" and "Toggle XMB Mode" and I don't think that has to do with this (2) problem.

Like I said, I can't find that setting ("Improper Shutdown Warning").

Anyway, I wasn't having these issues some versions ago and with the current settings.
 
Last edited:
How is dynamic fan control in cfw tools different than the dynamic settings in webmanmod setup?

In my case it defaults at 33% fan speed and when target temps are reached my ps3 would turn into a jet engine then goes quite again, i assume the default 33% in cfwtools isn't enough at around this time of they year in my country since it's begin getting hot
 
I have Evilnat 4.91 Cobra 8.4 [PEX], IRISMAN 4.91 and FileZilla Client installed and I'm having these issues:

1 - As soon as I click "Enable FTP" in "Cobra Tools" in "* Custom Firmware Tools" with an USB device connected to the PS3, the latter freezes (I tested this in another PS3 Slim and a friend of mine also did it in his PS3 Slim and we're having this problem in them, too);

2 - The PS3 beeps thrice and restarts when exiting IRISMAN using the PS button after uploading files from the PC to the PS3 with FileZilla Client and with an USB device connected to the PS3;

3 - The PS3 often freezes when returning to XMB from IRISMAN using the Circle button after uploading files from the PC to the PS3 with FileZilla Client and with an USB device connected to the PS3 and when clicking the PS3's power button, the PS3 beeps thrice and turns off;

4 - Sometimes, the PS3 also beeps thrice and restarts after exiting a game or app using the PS button with an USB device connected to the PS3;

5 - There are times when the PS3 beeps thrice and restarts in other occasions as well;

6 - Occasionally, when using FileZilla Client to upload PKG files from the PC to the PS3 while IRISMAN is running, the uploads start very slowly (like under 1 MiB/s instead of 18 something MiB/s) and take some time to reach the right speed (18 something MiB/s);

7 - If I leave FileZilla Client connected to the PS3 for some time, I can't reconnect to it until I close FileZilla Client and run it again. This also happens with the PS2, PSP, PS Vita and PS TV;

8 - My PS3 keeps asking to connect the controller and press the PS button. I also have this issue with the stock HDD (the current HDD was bought in August 2021);

9 - When checking the HDD after clicking "Check File System" in "Service Tools" in "* Custom Firmware Tools", it doesn't even reach 50% and the PS3 turns off.

EDIT: If I close FileZilla Client after uploading files from the PC to the PS3 or if I don't connect an USB device to the PS3 before uploading them (or if I take it after uploading them), I can exit IRISMAN using the PS button without the PS3 beeping thrice and restarting and I can return to XMB from IRISMAN using the Circle button without the PS3 beeping thrice and turning off.

EDIT 2: I've reinstalled Evilnat 4.91 Cobra 8.4 [PEX], IRISMAN 4.91 and FileZilla Client, used the "Restore File System" and "Rebuild Database" settings from the PS3's Safe Mode and swapped the PS3's HDD for the stock one and for a SSD I bought in February 2023 and I still have these issues.

EDIT 3: Thanks to the SSD, I'm now getting 21 something MiB/s instead of 18 something MiB/s when uploading PKG files from the PC to the PS3, at least.

EDIT 4: I have a new PC and when uploading PKG files from the PC to the PS3, I'm now getting 22 MiB/s (and even slightly more).

EDIT 5: Now, the PS3 sometimes says it cannot start and the appropriate system storage was not found. I never had this problem with both HDDs.

EDIT 6: Currently, the PS3 isn't saying it cannot start and the appropriate system storage was not found but the PS3 still asks to connect the controller and press the PS button from time to time. I only had the former problem that day.

EDIT 7: I haven't had the latter issue.

EDIT 8: I had the latter issue again.
I no longer have 1 and it doesn't have to do with 2.

@CFW-Us3r never talked about clicking "Show Information" and "Toggle XMB Mode" and I don't think that has to do with this (2) problem.

Like I said, I can't find that setting ("Improper Shutdown Warning").

Anyway, I wasn't having this issues some versions ago and with the current settings.


Already did and I still have it. Sorry, but what do you mean by "flash memory error" and what does it have to do with my problem?

Apologies, I just saw your other thread, but still feel this is relevant.

1) FTP errors using Cobra: For me, I have only encountered an 'unable to connect' error during Beta 3 utilizing File-zilla via cobra FTP, and by following Evilnats suggestion to 'toggle enable ftp/ disable ftp' to resolve, it fixed the issue. Also, Evilnat noted that there may be a slight delay after enabling, so try enabling and wait 2 min before upload if using Cobra options for FTP. As others have mentioned, I was also able to use WebMAN mods FTP without issue, but either appears to be working in any case at least for me.

2) I have not had any of the shutdown errors while exiting IRISMAN after upload via FTP, even with external storage connected.

3) DEBUG SETTINGS: I noticed on Beta 2 by flashing with VSH still in DEX mode as it is in default, Debug settings disappeared while in CEX mode and VSH in Dex, however, after fulling switching over to DEX across the board via Cobra Custom firmware tools, all settings came back. **When switching EVERYTHING back to CEX before flashing, Debug settings were present in CEX & DEX modes, which helped me draw the conclusion that we need to be CEX across to mitigate errors.

4) The flash memory error I was referring to was the 8002F155, and the initial CFW update failing first time around, and succeeding on 2nd attempt, apologies if this was not what you were referencing.

5) I have not used FTP to access an externally connected storage device to the PS3, and don't fully understand the use case for needing to do this.

6) I have not yet utilized service tools as Evilnat provided that some of the ports were not fully finished, so I cannot report on these just yet as waiting for final before testing.

In summary: Debug settings have been consistent and present when always flashing from CEX, and while different options are available dependent upon whether in CEX or DEX mode, they have all been present and consistent with the methods mentioned, at least for me. FTP via Cobra and also Webman works without issues aside from delay etc, and 'Improper Shutdown method' option is visible only while in DEX Debug mode for me, 5 options from bottom. I have never had the flash error or the need for a second attempt at flashing as others have reported.

Model: CECHK-01
Storage: 1TB Toshiba, old school
 
Last edited:
Back
Top