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

UPDATE 4.88.2: PS3 Developer @Evilnat has updated and released 4.88.2 Evilnat (Cobra 8.3) CFW , there is a number of new options like an added File manager, Option to toggle Cobra version, and various other new options detailed in the changlog provided below. Also the developer has provided a number of fixes and improvements, View all the details of 4.88.2 release of this latest CFW by @Evilnat

.Original release (4.88.1) Developer @Evilnat (creator of releases like SEN Enabler and PAUD Unpacker) has created and released 4.88 EVILNAT's COBRA CFW, following the success of 4.87 Evilnat's CFW, the developer provides another trusted CFW release that provides the Cobra Payload and all the features it brings (note: MAMBA is an alternative to the Cobra Payload, Cobra is included in firmware's where as MAMBA is typically injected in a Standard CEX CFW via a homebrew app. See all the details of this CFW Release below

Also Included are: noBD / noBT / noBD & noBT CFW Builds (for damaged console's to make them usable again)
-STLcardsWS​



CFW Evilnat.png

  • 4.88.2 EVILNAT (COBRA 8.3)

    Changelog
    • Fixed memory leak in LV2 kernel while Cobra is enabled
    • Added option to dump ERK (eid_root_key) through xai_plugin (from flatz's EID root key dumper)
    • Added option to dump LV2 through xai_plugin
    • Added option to dump LV1 through xai_plugin
    • Added File Manager in xai_plugin (by DeViL303)
    • Added option to toggle Cobra version, release (default in CFW) and debug (get debug logs through socat)
    • Manual FAN speed now works with Cobra disabled too
    • Added system to block login in on PSN/SEN while CFW syscalls are enabled (by DeViL303)
    • Added sort games by name and date options (by aldostools)
    • xai_plugin translated to Brazilian (thanks to jcorrea and LuanTeles)
    • xai_plugin translated to Polish (thanks to KcrPLo and Agrippa)
    • xai_plugin translated to Italian (thanks to Sheireen)
    • xai_plugin translated to Chinese Traditional/Simplified (thanks to xiaoyang)
    • xai_plugin translated to Spanish

    Features
    • Made out of 4.88 OFW
    • Made manually without automatic tools
    • SEN/PSN enabled
    • Disabled deletion of unsigned act.dat and .rif files
    • Allowed unsigned act.dat and .rif files
    • Allowed running of unsigned applications
    • Compatibility with FSELF
    • C00 demo unlocker
    • Disabled LIC.EDAT license check
    • Can be installed over 3.55 OFW
    • Can be installed over +3.56 OFW (bguerville Toolset)
    • Can be installed over any CFW CEX
    • COBRA 8.3 added and enabled as default
    • Full PS2 Games Compatibility
    • Possibility of Downgrade from any CFW with active QA Flags
    • QA Flags active if previously enabled
    • Disabled Epilepsy Message on Boot
    • Compatibility with PSX games in ISO
    • Compatibility with PSP games in ISO
    • Compatibility with PS2 games in ISO
    • Compatibility with PS3 games in ISO/JB folder format
    • Compatibility with ReactPSN
    • Display of Temperatures in XMB In-Game on PS2 Games
    • RSOD Screen Bypass
    • BSOD Screen Bypass
    • PS3_GAME/app_home
    • XMB In-Game Screenshot
    • Added Package Manager
    • CoreOS Hash Check patched to prevent Brick on non-dehashed Downgradate consoles
    • Patched to remove LV2 Protection
    • Peek and Poke (LV2)
    • Peek and Poke (LV1)
    • CINAVIA protection disabled
    • Option to sort games by name and date

    Cobra 8.3
    • Failsafe Cobra stage2 (by bguerville/aldo)
    • Restore CFW Syscalls without reboot just entering to 'Settings > System Update' on XMB (by aldo)
    • Integrated Dynamic Control FAN (to control fan when webMAN is unloaded) (by aldo/Evilnat)
    • Support Photo GUI integration with webMAN MOD (mount games from 'Photo' column) (by aldo/DeViL303)
    • Get/Set FAN speed (by aldo)
    • Enable/disable features: Photo GUI, Restore Syscalls (by aldo)
    • Opcode to create CFW Syscalls (6, 7, 8, 9, 10, 11, 15, 35) (by aldo)
    • Opcode to set fake accountID (by Evilnat)
    • Opcode to activate account (act.dat) (by Evilnat)
    • Opcode to create license (RIF) (by Evilnat)
    • Updated ps3mapi_load_process_modules to load custom modules and system modules (by haxxxen)
    • Added ps3mapi_get_process_module_info
    • Increased from 24 to 32 the max number of map paths (by aldo)
    • Added sm_get_temperature patch in kernel (by Evilnat)
    • Added sm_get_fan_policy patch in kernel (by Evilnat)
    • Added sm_set_fan_policy patch in kernel (by Evilnat)
    • Fixed Control FAN payload, avoids loading previous mode (by Evilnat)
    • Disable stage2.bin while Recovery Menu is loaded (by haxxxen)
    • Fixed max FAN speed after shutdown (by Evilnat)
    • Improved Habib's QA flags code imported by aldostools (by Evilnat)
    • Fixed black screen in CFW2OFW converted games (by Evilnat)
    • Added sm_ring_buzzer with single_beep, double_beep and triple_beep (by Evilnat)
    • Skip license creation (rif) if it already exists (by aldo)
    • Added cellFsMkdir symbol (by Evilnat)
    • Added constant FAN Speed while a PS2 ISO is launched (by Evilnat)
    • Check/Disable/Enable QA Flags (by Evilnat)
    • Creation of act.dat while launching a PSN game (by Evilnat)
    • Convert someones's else savedata to your own savedata (by Evilnat)
    • Block Log In on PSN/SEN when CFW syscalls are enabled (by DeViL303)

    Tested in:
    • CECH-2000A
    • CECH-2000B
    • CECH-2001A
    • CECH-2002B
    • CECH-2004A
    • CECH-2012A
    • CECH-2104B
    • CECH-2500A
    • CECH-2501A
    • CECH-2504A
    • CECH-2511A
    • CECH-2511B
    • CECH-L04
    • CECHA01
    • CECHE01
    • CECHB01
    • CECHC04
    • CECHG01
    • CECHP01

    Improvements xai plugin


    These options are in Network tab under [★ Custom Firmware Tools] option:

    Power Options
    • Turn Off: Turns off the PS3
    • Hard Reboot: Reboots the PS3 completely
    • Soft Reboot: Reboots the PS3 softly
    • Reboot LV2: Reboots the LV2

    File Manager
    • Internal Hard Disk Drive 0: Manage PS3 files in /dev_hdd0
    • Internal Hard Disk Drive 1: Manage PS3 cached files in /dev_hdd1
    • USB Mass Storage Devices: Manage files on your USB devices
    • Internal Flash Memory: Manage PS3 internal flash files
    • Optical Disc: Manage optical discs
    • Memory Cards: Manage memory cards

    Basic Tools
    • FAN Speed: Shows current FAN speed
    • PS3 Temperature: Shows current CPU and RSX temperature
    • Show IDPS: Shows current IDPS
    • Show PSID: Shows current PSID
    • Toggle Coldboot: Toggles between custom/original coldboot.raf
    • Toggle System Version: Toggles between custom/original system version in "System Information"

    Basic Tools > xRegistry Tools

    • Backup xRegistry.sys: Creates a backup of xRegistry.sys to /dev_usb or /dev_hdd0
    • Button Assignment: Switches O and X buttons

    Cobra Tools
    • Cobra Information: Shows current Cobra information
    • Check Syscall 8: Checks Cobra's Syscall 8 status
    • Create Syscalls: Create syscalls 6, 7, 8, 9, 10, 11, 15 and 35
    • Allow Restore Syscalls: Allows restoring syscalls through "System Update"
    • Skip license creation: Skips overwriting license file (RIF) if it already exists
    • Toggle Cobra Version: Toggles between release and debug versions (reboot is required)
    • Toggle Cobra: Enables or disables Cobra (reboot is required)

    Cobra Tools > FAN Tools
    • Control FAN Mode: DISABLED: Disables Cobra's Control FAN
    • Control FAN Mode: SYSCON: Allows the PS3's SYSCON to control FAN speed
    • Control FAN Mode: MAX: Set Cobra FAN speed to 0xFF

    Cobra Tools > QA Tools
    • Check QA Flags: Check if QA flags are enabled or disabled
    • Enable QA Flags: Enables QA Flags
    • Disable QA Flags: Disables QA Flags

    Cobra Tools > FAN Tools > Dynamic FAN Control
    • Maximum temperature: 60°C: Sets the fan speed dynamically to keep the system at a maximum temperature of 60°C
    • Maximum Temperature: 65°C: Sets the fan speed dynamically to keep the system at a maximum temperature of 65°C
    • Maximum Temperature: 70°C: Sets the fan speed dynamically to keep the system at a maximum temperature of 70°C
    • Maximum Temperature: 75°C: Sets the fan speed dynamically to keep the system at a maximum temperature of 75°C

    WARNING: Some PS3 cannot reach/stay some option temperatures, use with caution

    Cobra Tools > FAN Tools > Manual Speed
    • Manual Speed: 40%: Sets the fan speed statically at 40% (0x67)
    • Manual Speed: 45%: Sets the fan speed statically at 45% (0x75)
    • Manual Speed: 50%: Sets the fan speed statically at 50% (0x80)
    • Manual Speed: 55%: Sets the fan speed statically at 55% (0x8E)
    • Manual Speed: 60%: Sets the fan speed statically at 60% (0x9B)
    • Manual Speed: 65%: Sets the fan speed statically at 65% (0xA8)
    • Manual Speed: 70%: Sets the fan speed statically at 70% (0xB5)
    • Manual Speed: 75%: Sets the fan speed statically at 75% (0xC0)
    • Manual Speed: 80%: Sets the fan speed statically at 80% (0xCE)
    • Manual Speed: 85%: Sets the fan speed statically at 85% (0xDA)
    • Manual Speed: 90%: Sets the fan speed statically at 90% (0xE7)
    • Manual Speed: 95%: Sets the fan speed statically at 95% (0xF4)

    WARNING: The chosen speed will be static, it will not be changed at any time automatically

    Cobra Tools > FAN Tools > PS2 FAN

    • PS2 Fan Mode: DISABLED: Disables Control FAN on PS2 game
    • PS2 Fan Mode: SYSCON: Allows the PS3's SYSCON to control FAN speed on PS2 game
    • PS2 Fan Mode: 40%: Sets FAN speed to 0x66 on PS2 game
    • PS2 Fan Mode: 50%: Sets FAN speed to 0x80 on PS2 game
    • PS2 Fan Mode: 60%: Sets FAN speed to 0x9A on PS2 game
    • PS2 Fan Mode: 70%: Sets FAN speed to 0xB4 on PS2 game
    • PS2 Fan Mode: 80%: Sets FAN speed to 0xCE on PS2 game
    • PS2 Fan Mode: 90%: Sets FAN speed to 0xE8 on PS2 game

    WARNING: There is no Control FAN in a PS2 game, select with caution

    PSN Tools
    • Disable Syscalls: Disables syscalls and remove history files
    • Show accountID: Shows current user's accountID
    • Create accountID: Creates a fake accountID for current user's in xRegistry
    • Overwrite accountID: Overwrites current user's accountID with a fake one in xRegistry
    • Activate account: Creates act.dat file in the current local account
    • Create license: Creates RIF licenses from RAP files from "x:\exdata"
    • Backup activation file: Creates a backup of act.dat to /dev_usb or /dev_hdd0
    • Disable account: Deletes current user's activation file act.dat permanently
    • Convert savedata: Converts savedata from "/dev_usbXXX/PS3/SAVEDATA" to your own savedata

    Dump Tools
    • View Log: http://localhost/dev_hdd0/tmp/cfw_settings.log (webMAN MOD is required for this function)
    • Clean Log File: Resets /dev_hdd0/tmp/cfw_settings.log file
    • Dump IDPS: Saves IDPS to log file
    • Dump PSID: Saves PSID to log file
    • Dump LV2: Dumps LV2 to /dev_usb or /dev_hdd0/tmp
    • Dump LV1: Dumps LV1 to /dev_usb or /dev_hdd0/tmp
    • Dump ERK: Dumps eid_root_key to /dev_usb or /dev_hdd0/tmp
    • Log KLicense usage: Saves filename and klicensee to log file
    • Log Secure File ID usage: Writes save data name and file ID key to log file
    • Dump Disc Hash Key: Retrieves disc hash key from an ORIGINAL game disc

    Service Tools
    • Display Applicable Version: Displays minimum downgrade version
    • Check File System: Reboots and allows you to check and repair filesystem
    • Rebuild Database: Reboots with Database rebuilding flag set
    • Toggle Recovery Mode: Reboot to Recovery Mode (Not supported on NAND models!)

    Service Tools > Advanced Service Tools
    • RSOD fix: Re-initialize VTRM-Region to attempt to fix RSOD
    • Toggle Factory Service Mode: Enter/Exit Factory Service Mode (DON'T INSTALL CFW ON FSM)
    • Remarry Bluray Drive: Requires: Enter to FSM and copy "eid_root_key" to /dev_usb
    • Load LV2 kernel: Loads lv2_kernel.self file from /dev_usb000 or /dev_flash


    Savegames conversion tutorial

    WARNING: This option will overwrite your current savedata in dev_usbXXX, use it with caution

    • Download someone else's savegame for your game of your choice
    • Put the savedata in your pendrive in "X:\PS3\SAVEDATA" (pendrive must be in FAT32)
    • Put in the pendrive in the PS3
    • Select Network Tab > [★ Custom Firmware Tools] > PSN Tools > Convert Savedata
    • Wait until the conversion finishes
    • Once finished, copy your converted savedata throught XMB "Saved Data Utility (PS3)"
    • Launch your game and load your new savedata


    Creation of act.dat tutorial

    WARNING: The accountID is linked to savedata and trophies, so, if your current user already have a valid accountID and you overwrite it, you will be unable to use your trophies and savedata on that account until you restore the original accountID in xRegistry.sys.


    I recommend to use an empty account without trophies and savedata or an account without accountID.


    To create a fake act.dat, Cobra 8.3 must be enabled, and your PS3 must have at least one account with a valid accountID and launch a game that requires a RIF/RAP license file.

    Cobra will search a valid accountID in all existing accounts and create act.dat while the game is launched through the XMB. If no accountID is found, act.dat will not be created.

    You can create a fake accountID (like reactPSN), to do this go to Network > ★ Custom Firmware Tools > PSN Tools and choose between "Create accountID" or "Overwrite accountID" (Be careful about the last option because if you already have a fake/real accountID it will be overwritten). It is recommended to use these options in an account that does not have an ID. The PS3 will restart if everything went well.

    The tutorial would be the following:
    • Download your purchased PSN game from PS Store
    • Put game RAP file in "X:\exdata" or "/dev_hdd0/exdata"
    • Launch your purchased PSN game
    • Cobra will check if any of your PS3 accounts have accountID
    • Faked act.dat will be created while the game is launching

    If none of your accounts have a valid accountID you will need to create it. To do this log into the local PS3 account where you want to create the accountID. You can see if your current local account has an accountID choosing Network Tab > [★ Custom Firmware Tools] > PSN Tools > Show accountID.

    To create a faked act.dat do the following:
    • Make sure Cobra 8.3 is enabled
    • Select Network Tab > [★ Custom Firmware Tools] > PSN Tools > Create accountID
    • Select Network Tab > [★ Custom Firmware Tools] > PSN Tools > Activate account
    • Launch your purchased PSN game
    • Faked act.dat will be created while the game is launching

    Now you have a faked act.dat and your local account is activated. The act.dat file works for every local account, you only need one file for all accounts.


    Block PSN log in

    This method is developed by @DeViL303, it will only work with Cobra enabled, Cobra will block log in on PSN/SEN while the CFW syscalls are enabled, to enable it again you need to disable CFW syscalls completely (you can do it with webMAN MOD, psnpatch, SEN Enabler, etc…).

    If you want to disable this feature, simply delete /dev_flash/vsh/resource/npsignin_plugin.lck


    Translations


    Final Words

    I hope that the CFW is working fine and without issues for everyone, but if you see any issue, please let me know in my twitter and I will try to fix it as soon as possible: @xXEvilnatXx

    Cobra 8.3 and xai_plugin source code can be found in my Github repository:


    Credits and Acknowledgment

    Credits to Team Rebug, Team Cobra, @mysis, @Joonie, @habib, @aldostools, @haxxxen, @DeViL303, @zecoxao, @3141card, @Berion, @kakaroto, @KW, @naehrwert, @flatz, @Dean, @Rogero, @Estwald and anyone who has contributed to the PS3 scene.

    Thanks to @DeViL303, @Berion, @Brandon Stump, @jcorrea, @nhie07, @NSC-Modz, @LuanTeles, @thejavigames, @raidriar, @xiaoyang, @Zwei, @haxxxen, @RetroFan_90, @SpyroMancer, @patricksouza472, @MrYadro, @CFW-Us3r, @Andrio, @KcrPLo, Nur Rakhmadi Rajab, @Lwiz, @Sheireen, @TheWizWiki and all who helped me testing the CFW 4.88.

    If I forgot someone, I apologize, there are many people in the PS3 scene and you are many people who
    have helped me to test the CFW.



Download: MEGA FOLDER WITH ALL CFW VERSION

Download: CFW EVILNAT 4.88.2 COBRA 8.3 [CEX]
MD5: 3202971E05140F24E52B36D5C443AD35

Download: CFW EVILNAT 4.88.2 COBRA 8.3 [CEX] [noBD]

MD5: 80029DC0FBD238DAF8ED45BCDFD04CD6

Download:CFW EVILNAT 4.88.2 COBRA 8.3 [CEX] [noBT]
MD5: 360569FE808B1815BD05258C8496003F

Download: CFW EVILNAT 4.88.2 COBRA 8.3 [CEX] [noBD] [noBT]
MD5: D8BB1F47B77F1737F974308B935F81B6
 
Last edited by a moderator:
For some reason I don't have the Custom Firmware Tools under Network menu. I first installed the custom firmware on 4.84 with PS3Xploit and did the reinstall. Then installed EvilNat 4.87 over it, twice. Then after EvilNat 4.88 came out, installed that over EvilNat 4.87, twice. Still no Custom Firmware Tools menu.

Rebug Toolbox says Cobra 8.30 is active.
are you installing any mods or toolboxes after you install evilnat?
 
very strange. custom firmware tools has existed for years, so I'm surprised it wasn't even on 4.84 for you. I can't remember if it was on ferrox, but it was on rebug 4.84.
 
@Evilnat Maybe you could implement this code in Cobra 8.3 for lock Sign In to PSN using @DeViL303's npsignin_plugin.rco when CFW syscalls are enabled. It requires a copy of the modded rco saved in dev_flash as /dev_flash/vsh/resource/npsignin_plugin.lck

The lock is removed when the CFW syscalls are disabled and locked again if the CFW syscalls are restored.

main.c
Code:
void create_syscalls(void)
{
    create_syscall2(8, syscall8);
    create_syscall2(6, sys_cfw_peek);
    create_syscall2(7, sys_cfw_poke);
    create_syscall2(9, sys_cfw_lv1_poke);
    create_syscall2(10, sys_cfw_lv1_call);
    create_syscall2(11, sys_cfw_lv1_peek);
    create_syscall2(15, sys_cfw_lv2_func);

    // Lock Sign In to PSN if DeViL303's rco exists
    CellFsStat stat;
    if(cellFsStat("/dev_flash/vsh/resource/npsignin_plugin.lck", &stat) == SUCCEEDED)
        map_path("/dev_flash/vsh/resource/npsignin_plugin.rco", "/dev_flash/vsh/resource/npsignin_plugin.lck", 0);
}

main.c -> syscall8()
Code:
case SYSCALL8_OPCODE_STEALTH_ACTIVATE: //KW PSNPatch stealth extension compatibility
{
    map_path("/dev_flash/vsh/resource/npsignin_plugin.rco", NULL, 0);
    uint64_t syscall_not_impl = *(uint64_t *)MKA(syscall_table_symbol);
    //*(uint64_t *)MKA(syscall_table_symbol+ 8* 8) = syscall_not_impl;
    ps3mapi_partial_disable_syscall8 = 2; //NzV Edit: Keep PS3M_API Features only.
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 9) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 10) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 11) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 15) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 35) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 36) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 38) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 6) = syscall_not_impl;
    *(uint64_t *)MKA(syscall_table_symbol + 8 * 7) = syscall_not_impl;
    return SYSCALL8_STEALTH_OK;
}
break;

EDIT:
I think it would be a good idea to use in create_syscalls() the new map_path feature "/./" to protect the mapping from accidental removal of the mapping by the backup managers.

map_path("/dev_flash/vsh/resource/npsignin_plugin.rco", "/./dev_flash/vsh/resource/npsignin_plugin.lck", 0);
 
Last edited:
I've updated to latest version but if I click on Create license: it says Cobra 8.3 required???

Did you remove the CFW syscalls before click that option? Most of these features require syscall 8 enabled.

Many of the error messages in xai_plugin are misleading. Many of them say "Cobra 8.3 required" instead of "CFW syscalls are disabled'. The user may think that there is a problem with the version of Cobra, when the real cause it the status of the syscalls.
 
@Evilnat

I need to use the DEX explorer_plugin.sprx, but it will break the compatibility with the ps2 games, i never messed with it, but i think i need to calculate your sprx hash, the dex one and replace it yours with mine inside stage2.bin, is it right?

Or can you include it by default?
 
Last edited:
@Evilnat

I need to use the DEX explorer_plugin.sprx, but it will break the compatibility with the ps2 games, i never messed with it, but i think i need to calculate your sprx hash, the dex one and replace it yours with mine inside stage2.bin, is it right?

Or can you include it by default?

You need to replace the hashes in the following module and compile stage2
https://github.com/Evilnat/Cobra-PS3/blob/master/8.3/4.88/NORMAL/CEX/SRC/stage2/modulespatch.h

It could work hex editing the hashes in stage2.bin, but it is safer to compile the project. It is open source code, use it!

#define EXPLORE_PLUGIN_HASH 0xc50d0000000e0000
upload_2021-7-9_18-53-0.png
 
Last edited:
Did you remove the CFW syscalls before click that option? Most of these features require syscall 8 enabled.

Many of the error messages in xai_plugin are misleading. Many of them say "Cobra 8.3 required" instead of "CFW syscalls are disabled'. The user may think that there is a problem with the version of Cobra, when the real cause it the status of the syscalls.
Good point.
I think that's something Nat might want to look into.
 
@bgurville

I have some questions I was wondering if you or other forum members could assist me with...

1. My current CFW modded PS3 is a 60GB model (CECHC03); its one of those PS2 Bw/C models that gets very hot. My original unit became faulty with YLOD many years ago; it lasted about 3-4 years of light usage, unknowingly slowly cooking itself due to $0nY's inadequate OFW stock fan control. The unit I have now only has about 12 days of continuous power-on usage according to the WebManMOD browser screen. One of the reasons I wanted to install Evilnat's CFW was to have better fan control and hopefully reduce the risk of this console reaching the same YLOD fate that my old one did. The debate on what most commonly causes YLOD on Bw/C PS3s and the supposed 'long term fixes' are widely contested on the internet - what is your opinion on the subject?
____

2. With an ambient room temperature of approximately 24*C / 75.2*F this system is idling at the XMB menu at around 41%~ fan speed; a 'dynamic control' target max temperature of 60*C / 140*F is set in WebManMOD; playing a game like Uncharted 3 brings it up to 56%~ fan speed. When balancing fan noise and overheating damage, is a target temperarue of 60*C good-enough to keep this system safe from future YLOD in the long-term? Should I set a lower more aggressive (louder), a or more relaxed higher target (quieter), or keep as it is?
____

3. What fan % speed do you recommend to be set in WebManMOD for PS2 emulation mode where dynamic control is not available?
____

4. When playing a PS2 ISO emulated game, the console does not detect the presence of my DualShock 4 or DualSense controllers and I am only able to play PS2 games with the original DualShock 3; is this a known limitation and is there a workaround?
____

5. After closing a PS2 game, the PS3 seems to turn itself off then back on before returning to the XMB menu; is this a normal hardware behaviour?
____

6. Using Evilnat's CFW, is it possible to restore the 'OtherOS' feaure that was hidden in earlier OFW to allow installing of linux on a different partition?
____

7. After using the Triangle+R2 button combination to 'unlock' PSN access (I think this is a WebManMOD feature?), is it possible to re-lock afterwards and re-enable syscalls/homebrew access after signing-out of PSN negating the need to restart the system?
____

8. Is it possible to convert PS3 ISOs I created from my BD game discs to PSN-style format so they can be launced directly from the XMB without the need to emulate a physical disc?
____

9. For existing account safety I have created a new PSN ID for use with my CFW PS3. Some games I have installed .PKG PSN versions of instead of creating ISOs of my own BD discs as it seems to save space on internal storage. When copying game saves from my OFW 4.86 PS3 Slim to this CFW console, many titles don't seem to acknowledge the existance of my current save files, instead insisting I create new and start from the beginning.

This doesn't affect all titles - for example Ridge Racer 7 and Mirror's Edge seem to load previous save data, Split/Second loads the data but at launch always prompts me that my "save file and trophy data do not match, would you like to delete the save file?", whilst other games like InFamous and Tomb Raider: Underworld don't recongise my previous save data at all.

I have tried resigning the save data using the apollo save tool app for the new PSN account, changing the title ID where I am using a PSN version of a game instead of a BD/ISO, but so far I cannot get many games to play-nice with my previous saves. Can you advise how I could try resolve this?
 
1. I am not the expert on YLOD, I have never had a YLOD issue myself either, I think I would ask @RIP-Felix or the other guys currently contributing to various hardware related threads including the one on Frankenstein 40nm RSX setup on backward compatible PHAT models.
They should be able to tell you what you need to know about YLOD & how to help prevent problems.
From what I understand, causes for YLOD are varied, sometimes a reballing will solve it, other times the tantalum fix will do the trick, etc.. The BGA setup is crap to begin with anyway..
You can use the logged errors from the syscon in order to diagnose the YLOD issue, there is a dedicated thread on this topic in which contributors did a wonderful job.
There is also a fairly recent thread in this forum talking specifically about YLOD & its causes, trying to debunk a number of myths, I would refer to that if I were you.
I won't comment on whether or not other sources of ylod information are confusing & contradictory, I can only say that to my knowledge the info posted on this topic in various threads in this forum can be taken seriously, research is still on going, new data comes out regularly, as we learn new things, drawn conclusions may evolve with time.

2. I always use target temperatures between 68C & 70C, depending on the console's tendency to heat up, in order to keep the fan speed under 50% at all times. Any more than that is way too noisy.
If you already changed the thermal paste & pads and did a good job, there is nothing more you can do without either delidding to change the internal paste that is probably dry (very risky especially if you don't have any experience) or attempting some customisations to improve the cooling (possible but not very easy either).

3. That largely depends on the console's propension to heat up I suppose. You need to establish the minimum fan percentage in order to keep the temps overall under 70C through series of trials.
At my end, I found in tests that my slims handle the emulator pretty well & their fans can generally be kept a bit lower than with PS3 games but I don't play PS2 games on them.
Additionally the ps2 emulator may naturally run at very different temps on your backward compatible PHAT, I cannot provide you with any proper references for comparison purposes.

4. I dunno, I have never tried BUT it's quite likely. The ps2 emulator takes the place of the GameOS kernel therefore it uses its own gamepad support implementation.
It makes sense to find differences in pad handling & I would not be surprised if that meant DS3 support only.

5. Yes it's normal behaviour. At the ps3 software lower level, you have what we call an hypervisor, it's like a virtual machine manager, it can run different OSes. The ps2 emulator is not an app running in GameOS, it is an OS just like GameOS or OtherOS(Linux), so when you start a ps2 game, the hypervisor puts GameOS in some kind of hibernation & launches the ps2 emulator OS. When you exit the ps2 game, the hypervisor closes the ps2 emulator OS & restores GameOS, hence the black screen delay when switching OS.

6. No, you would have to apply some patches either with Mfwbuilder or manually so that the PUP handling system would know to create the necessary partitions during the installation phase. What you might be able to do however is launch OtherOS from an external USB drive. In any case that is what I would suggest you do first before deciding to mess with the internal hdd structure, there is no updated Linux distros to install, Red Ribbon is old & unless you are a dev wanting to research the system or a skilled Linuxer willing to work on an updated distro, it will probably not satisfy your needs. But if you are 100% sure you want to use OtherOS on internal hdd, there is always the solution to downgrade using an available CFW prepatched for OtherOS installation (iirc there are some Rebug & some MLT CFWs with different OtherOS partition sizes), the downgrade CFW installation would take care of the hdd prepping then you could update to a 4.8x CFW, alternatively you could even go back to an older 3.xx OFW & install OtherOS in the official way. It would be quite straightforward if you really wanted to do it. Keep in mind that in order to downgrade you must first enable QA with CFW Settings, it's recommended to keep QA enabled all the time as it unlocks abilities that could potentially save your bacon the day you encounter system software complications, if that ever happens, but it's like keeping a backup of eid_root_key & of the Flash memory, neglecting to do it could mean the loss of your data or the death of the console one day because of a user error & just a bad luck power outage at the wrong time. A console on CFW gives root permissions to the apps you run therefore the user becomes able to damage his own software system.

7. You will need to ask @aldostools about this as personally I use the PSNPatch plugin to deal with that. Generally speaking, the reboot has been necessary for a simple reason, once syscalls are disabled & in some setups, plugins like wMM or PSNPatch have been unloaded, you can no longer reload the custom plugins or re-enable the syscalls.
Having said that, at some point, code was added to perform some semi disabling of syscalls ie all syscalls disabled except one to give you opportunity to re-enable all syscalls. I don't really know how Aldo may have made use of that possibility in the wMM features you are asking about.

8. The only tools that can do something like that are CFW2OFW tools that will transform a disc game into a NP game as long as at least one pkg update exists for that game, games without updates cannot be converted.
That is what the old HAN exploit was relying on to bring game backups to OFW users, you can still use HAN signed CFW2OFW converted games on CFW if you really wish but it's an obsolete exploit & it does not make much sense tbph.
I would never use this on CFW myself though, for a number of reasons I much prefer ISO & keeping all original files but you are free to bother converting all your games.
Imho the best setup is iso games located on a ntfs external USB disk, I happened to have a spare SSD so that's what I use for this, it's flexible, files can be managed just as easily & quickly on PC or on PS3, no need for ftp transfers & the likes, it doesn't clog up your internal hdd & the game perfs are as good as you can get on a PS3, I find games running better than with the BD but also better than iso or JB folder games stored on internal hdd.

9. You need to ask @bucanero (Apollo Save Tool dev) or @aldostools (Bruteforce Save Data dev) about this, you can reuse your previous saves in most cases as long as they are properly resigned with the correct ids, there might still be a few problematic games, the devs should be able to tell you which ones & propose workarounds if any exist.

Generally speaking, you may also find some answers to your questions in the wiki, it's a mine of information & more is added all the time.
https://www.psdevwiki.com/ps3
 
Last edited:
@bgurville

I have some questions I was wondering if you or other forum members could assist me with...

1. My current CFW modded PS3 is a 60GB model (CECHC03); its one of those PS2 Bw/C models that gets very hot. My original unit became faulty with YLOD many years ago; it lasted about 3-4 years of light usage, unknowingly slowly cooking itself due to $0nY's inadequate OFW stock fan control. The unit I have now only has about 12 days of continuous power-on usage according to the WebManMOD browser screen. One of the reasons I wanted to install Evilnat's CFW was to have better fan control and hopefully reduce the risk of this console reaching the same YLOD fate that my old one did. The debate on what most commonly causes YLOD on Bw/C PS3s and the supposed 'long term fixes' are widely contested on the internet - what is your opinion on the subject?
____

2. With an ambient room temperature of approximately 24*C / 75.2*F this system is idling at the XMB menu at around 41%~ fan speed; a 'dynamic control' target max temperature of 60*C / 140*F is set in WebManMOD; playing a game like Uncharted 3 brings it up to 56%~ fan speed. When balancing fan noise and overheating damage, is a target temperarue of 60*C good-enough to keep this system safe from future YLOD in the long-term? Should I set a lower more aggressive (louder), a or more relaxed higher target (quieter), or keep as it is?
____

3. What fan % speed do you recommend to be set in WebManMOD for PS2 emulation mode where dynamic control is not available?
____

4. When playing a PS2 ISO emulated game, the console does not detect the presence of my DualShock 4 or DualSense controllers and I am only able to play PS2 games with the original DualShock 3; is this a known limitation and is there a workaround?
____

5. After closing a PS2 game, the PS3 seems to turn itself off then back on before returning to the XMB menu; is this a normal hardware behaviour?
____

6. Using Evilnat's CFW, is it possible to restore the 'OtherOS' feaure that was hidden in earlier OFW to allow installing of linux on a different partition?
____

7. After using the Triangle+R2 button combination to 'unlock' PSN access (I think this is a WebManMOD feature?), is it possible to re-lock afterwards and re-enable syscalls/homebrew access after signing-out of PSN negating the need to restart the system?
____

8. Is it possible to convert PS3 ISOs I created from my BD game discs to PSN-style format so they can be launced directly from the XMB without the need to emulate a physical disc?
____

9. For existing account safety I have created a new PSN ID for use with my CFW PS3. Some games I have installed .PKG PSN versions of instead of creating ISOs of my own BD discs as it seems to save space on internal storage. When copying game saves from my OFW 4.86 PS3 Slim to this CFW console, many titles don't seem to acknowledge the existance of my current save files, instead insisting I create new and start from the beginning.

This doesn't affect all titles - for example Ridge Racer 7 and Mirror's Edge seem to load previous save data, Split/Second loads the data but at launch always prompts me that my "save file and trophy data do not match, would you like to delete the save file?", whilst other games like InFamous and Tomb Raider: Underworld don't recongise my previous save data at all.

I have tried resigning the save data using the apollo save tool app for the new PSN account, changing the title ID where I am using a PSN version of a game instead of a BD/ISO, but so far I cannot get many games to play-nice with my previous saves. Can you advise how I could try resolve this?
6. Using Evilnat's CFW, is it possible to restore the 'OtherOS' feaure that was hidden in earlier OFW to allow installing of linux on a different partition?

Interesting this question
I remember that this function was present in OFW 3.15
 
9. For existing account safety I have created a new PSN ID for use with my CFW PS3. Some games I have installed .PKG PSN versions of instead of creating ISOs of my own BD discs as it seems to save space on internal storage. When copying game saves from my OFW 4.86 PS3 Slim to this CFW console, many titles don't seem to acknowledge the existance of my current save files, instead insisting I create new and start from the beginning.

This doesn't affect all titles - for example Ridge Racer 7 and Mirror's Edge seem to load previous save data, Split/Second loads the data but at launch always prompts me that my "save file and trophy data do not match, would you like to delete the save file?", whilst other games like InFamous and Tomb Raider: Underworld don't recongise my previous save data at all.

I have tried resigning the save data using the apollo save tool app for the new PSN account, changing the title ID where I am using a PSN version of a game instead of a BD/ISO, but so far I cannot get many games to play-nice with my previous saves. Can you advise how I could try resolve this?

Saves are tied to several ids (Game ID, PSN Account ID, console id, user account id, etc.). If you changed one or more of them, the save will not work.

If you changed from ISO to PKG the game ID could have changed from retail (BL*S/BC*S) to (NP*A/NP*B). Or you could have changed the region of the game. The EBOOT supports specific game ids and not always support all the regions.

If you transferred the data using the data transfer tool found in Settings column, the system will make the conversion automatically. If you copied the saves manually, you will need to resign all your saves using Apollo Save Tool (on the PS3) or Bruteforce Save Data (on the PC).

If you are using a different PSN account, the saves must be resigned with your new account id. If you use Bruteforce Save Data you must provide the PARAM.SFO of one of your saves as template for your new account id. Also you need to configure the Global Settings with the user id in /dev_hdd0/home assigned to that account. Apollo Save Tool normally is easier to use because the tool gets all the required ids directly from the PS3.
 
Hello I recently acquired a BC Ps3 Cecha00 and installed CFW 4.88 and wanted to ask if running PS2 ISO's with Webman will run them with hardware mode or software emulation.
 
Dumb question by what is BD and BT? Which one is blue Ray drive? I'm
Missing one.
BD is Bluray Drive & BT is Bluetooth.
Both the BD drive + BD controller & the BT/WIFI subsystem must be functional for the system software to work properly and for PUP installations to succeed.
NoBD & NoBT patches will get a PUP installation to succeed even if the BD or BT are not functional on the console however the parts of the system software that specifically rely on BD or BT will still malfunction until the hardware is fixed.
 

Featured content

Trending content

Latest posts

Back
Top