PS3 CFW RELEASED - 4.89.3 Evilnat (Cobra v8.4) Official debut of PEX (New PS3 CFW type) + Other flavor's

UPDATE (Re-Download PUP) - via @Evilnat "CFW 4.89.3 updated with Cobra 8.4 by default and xai_updater updated to v1.2 for all versions! It fixes updater package for CEX and DEX."

---

.Developer @Evilnat has released the much anticipated update to his PS3 CFW with the release of 4.89.3 Evilnat CFW. This update comes with a variety of PUP to choose from and as we been detailing over the past several months there are alot of new features in this custom firmware release from developer @Evilnat ,

This firmware brings back a lost relic of the scene that was stopped at firmware 4.84 and I am speaking of Rebug REX (the original hybrid of CEX(retail) / DEX (debug) firmware), With no DEX firmware available to the public past 4.84 there was a problem, developer's knew how to create a REX style firmware,they have just been missing the DEX portion since 4.84. Well developer @Evilnat decided he would try and bring 4.84 DEX to 4.89 by porting the firmware and after some trials and error's the developer was able to achieve that goal and now we have Evilnat PEX (& D-PEX) CFW which is a hybrid like Rebug REX..



The dev has also added many new functions and menu listing to the XMB making it a very powerful XMB on CFW and maybe even more functional then ever before with new improvements to the xai_plugin in this update.,The developer was taking many request from user's and developer's here in the psx-place forums and aswell on twitter. The result became alot of new options and functionality for a user-friendly experience and also contains some advanced feature's that should appeal to many CFW user's. There is alot to dive into with this epic PlayStation 3 (PS3) Custom Firmware release. Below is just a small overview of the release, navigate the the link below for the official release notes, setup ect & download from the thread maintained by developer @Evilnat.

Update: The firmware is actually running Cobra v8.4 payload, only listed as 8.3. ​

​

About (via Evilnat) Warning's + Models Tested Available Flavor's / Screenshots FAQ

• 
  After lot of months of work, research and effort (and nights sleeping little), finally I can release it, here it is! Make sure you read all tabs to learn everything about my CFW, there is a lot of information that you should know
  
  A quick overview in case someone does not know what to install,
  
  PEX and CEX is for CFW compatible CEX PS3
  D-PEX and DEX is for CFW compatible DEX PS3​
  
  
  
  CEX and DEX are standard CFWs, like my 4.89.2, Rebug LITE, etc...
  PEX and D-PEX are like REX and D-REX​
  
  Thank so much to everyone who have helped me!

  ---

  .
  
  4.89.3 EVILNAT (COBRA 8.3 8.4)​
  
  Features
  
  • Made out of 4.89 OFW (CEX)
  • Ported Kernel and some modules from OFW 4.84 DEX
  • Made manually without automatic tools
  • PSN/SEN enabled
  • Fixed layouts 272/480 from OFW 4.89
  • 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/PSP/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
  • Allow to use 3rd party controller in Recovery Menu
  • Compatibility with OtherOS
  • Disabled update from OFW PUP in Recovery Mode
  • Dualboot compatible
  • Allowed installing of retail PKG on DEX
  • Allowed installing pseudo-retail PKG
  • Enabled [★Unlock], [★Lock], and [★Delete] options in Trophies
  • Compatibility with Remote Play
  ​
  
  Cobra v8.4 Changes
  Updated Note: (Cobra v8.4 is running, it's just listed as v8.3 by mistake)
  

  It looks like @Evilnat forgot to change the version number in Cobra. It's actually is "8.4" but labeled 8.3

  (link)
  
  • - Blacklist access to homebrews NP0APOLLO / NP00PKGI3 when CFW syscalls are disabled
    
  • - PS3MAPI changes by @OsirizX used for Dynarec
    
  • - Libcrypt Support for PS1 games (LSF/SBI files).
    
  • - PSX Bios patched with product code 0x85 for PAL games
    
  • - Force video mode in PS1 games adding "NTSC" or "PAL" in the file name of the BIN/CUE
    
  • - PS2 FAN Speed now works with PS2 Classic games
    
  • - Updated PS3MAPI_CORE_VERSION to 0x0124 (OsirizX additions for Dynarec)
    
  • - Disabling boot_plugins.txt by Evilnat
    
  • - Check for NULL memory allocation in make_rif.c
    
  • - Map path like Mamba 8.4
    
  • - Fixed issue in PhotoGUI. It was truncating the path by 16 bytes
  Cobra 8.3
  
  Spoiler: Previous Cobra Change's

  • 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 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)
  • 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)
  • Creation of fake act.dat while launching a PSN game (by Evilnat)
  • Block Log In on PSN/SEN when CFW syscalls are enabled (by DeViL303)
  ​
  
  
• 
  PlayStation 3 Model's Tested:
  
  Spoiler: See All Models Tested

  • CECH-2000A
  • CECH-2000B
  • CECH-2001A
  • CECH-2002B
  • CECH-2003A
  • CECH-2004A
  • CECH-2012A
  • CECH-2104B
  • CECH-2500A
  • CECH-2501A
  • CECH-2504A
  • CECH-2511A
  • CECH-2511B
  • CECH-L04
  • CECHA01
  • CECHE01
  • CECHB01
  • CECHC04
  • CECHG01
  • CECHP01
  There is some information that need to be aware, are the following:

  ---

  .
  • The accountID is directly linked to savedatas and trophies data. If you have trophies or savedatas in
    your current local account, THEY WILL BE CORRUPTED after setting FAKE accountID. To fix this, copy the
    savedata to the root of a USB, convert it and then copy it back through XMB in 'Game' tab. To fix
    corruption in trophies you need to delete it/them. Is highly recommended to do this on a local account
    without trophies/savedatas
    
    
  • The FAN speed is constant when in a PS2 game, BE CAREFUL while selecting modes because it will not
    change after the PS2 game is loaded. It is also static when choosing a mode in the "Manual Speed"
    option. All current speeds in xai_plugin must keeping a correct temperature in CPU and RSX
    
    
  • Do not rename vsh.self manually and ALWAYS use the option for it in xai_plugin, it can cause that the
    PS3 can't load the XMB when you have full version of webMAN MOD, DEX Kernel and CEX vsh.self. The
    CFW has a protection to avoid this
    
    
  • Target Manager will show SDK 4.8.4 while the PS3 is DEX, this is normal and it is because I ported
    modules from OFW 4.84 DEX to 4.89, I patched them to work on 4.89 but not to show version 4.8.9
    
    
  • If you want to install OtherOS on PS3's internal HDD you first need to go to Recovery Menu and select
    [Restore PS3 System], this will format the HDD and create a partition for OtherOS. Remember to make
    a backup of all your data before
    
    
  • DON'T TRY TO SWAP KERNEL WHEN YOU HAVE LOADED AN EXTERNAL KERNEL FROM USB/FLASH!!
    This can cause brick and you may need a hardware flasher to repair the PS3
    
    
  • You can unload Cobra/plugins if you have any problem with them, for this you need to go to Recovery
    Menu and then reboot the PS3, this will disable both
    
    
  • It is recommended to ALWAYS activate the QA Flags, it is very important, it allows you to install CFW
    from versions prior to the one installed and also avoids issues
    
    
  • If you can't dump or make an ISO of your game disc in multiMAN, go to mmCM tab and select [Switch
    to multiMAN mode], this will reboot multiMAN and now you will be able to dump/make an ISO of your
    disc
    
    
  • OtherOS on PS3 with NAND is very dangerous if you don't know what you are doing (for example using
    the wrong image to install petitboot), it can cause brick and the only way to repair it is with a hardware
    flasher. PLEASE USE IT WITH CAUTION!
    
    
  • Make sure you are installing the correct image for OtherOS. xai_plugin tells you what image need to be
    installed too. For NAND you need dtbImage.ps3.bin.minimal and for NOR dtbImage.ps3.bin. If the
    wrong image is installed, it can brick on NAND, needing a HW flasher to repair it, in NOR you can fix it
    formatting the HDD
    
    
  • If your PS3 has a CFW noBD (in any of its variants) and latest versión of webMAN MOD (1.47.42 at the
    time of writing this guide), there are chances that the PS3 can't read an external devices (/dev_usb000,
    /dev_usb001, …) in the next two minutes. To fix this, go to webMAN Setup page, click on webMAN
    MOD Setup and check noBD patch and reboot the PS3, now it may read external devices
    
    
  • Enable FTP and Disable FTP can fail randomly, if you want to use any of them wait a few seconds before using any again. It also happens with the option Check GPU/VRAM clock speed, those values are stored in LV1 and sometimes the PS3 doesn't stores it and can fail. If this happen, reboot the PS3 until those values are present in LV1
    
    
  • In PEX and D-PEX versión some of the debug options pressing triangle are missing because a/some
    file/s hasn't been ported yet (needs a lot of research with XMB layouts, I have patched some of them
    but others not, for example, trophies entries are messed up), those options are (maybe more):
    • ★ Check
    • ★ Owner Information
    • ★ Cancel Purchase
    • ★ Performance Bar
    • ★ No Memory Limit
  
  
  • The CFW is meticulously tested and no bugs have been found, but that does not mean that there are
    any or that it fails at any specific time. If that happens, contact me as soon as possible so that I can
    solve it.
• 
  See Official Thread for downloads (below are the various PUP released)
  
  • PEX= A Hybrid of debug (DEX) & retail (CEX) firmware's to create one
    
  • D-PEX = Is the same as PEX (just installs on PS3 debug console or converted dex console's)
  • CEX = Full Retail (CEX) firmware for retail console's
  • DEX = Full Debug (DEX) Firmware for debug console's (or converted)
    
  • noBD = BluRay Drive software patched (removed), allows for console's with damaged daughter boards to launch stored content from XMB (otherwise can't)
  • noBT = Same as noBD but with damaged Bluetooth board
  • OC= Overclocked (LV1 patched for 600 Mhz GPU / 750 Mhz GDDR3 RAM Clock speeds) - if console has heating issue's not advised,

    ---

    ..
  PEX Releases (Installing on a Retail (CEX) PS3 Console)

  ---

  .
  • CFW Evilnat 4.89.3 COBRA 8.3 [PEX] [CEX]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [PEX] [CEX] [noBD]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [PEX] [CEX] [noBD+noBT]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [PEX] [CEX] [noBT]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [PEX] [CEX] [OC]
  
  
  D-PEX Releases (Installing on a DEBUG (DEX) PS3 Console or Converted DEX Console)

  ---

  .
  • CFW Evilnat 4.89.3 COBRA 8.3 [D-PEX] [DEX]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [D-PEX] [DEX] [noBD]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [D-PEX] [DEX] [noBD+noBT]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [D-PEX] [DEX] [noBT]
    
  • CFW Evilnat 4.89.3 COBRA 8.3 [D-PEX] [DEX] [OC]
  
  
  CEX (Retail Console) Releases (Installing on a Retail CEX Console)

  ---

  .
  • CFW Evilnat 4.89.3 COBRA 8.3 [CEX]
  • CFW Evilnat 4.89.3 COBRA 8.3 [CEX] [noBD]
  • CFW Evilnat 4.89.3 COBRA 8.3 [CEX] [noBD+noBT]
  • CFW Evilnat 4.89.3 COBRA 8.3 [CEX] [noBT]
  • CFW Evilnat 4.89.3 COBRA 8.3 [CEX] [OC]
  DEX(Debug Console) Releases (Installing on a DEBUG (DEX) PS3 Console or Converted DEX Console)

  ---

  .
  • CFW Evilnat 4.89.3 COBRA 8.3 [DEX]
  • CFW Evilnat 4.89.3 COBRA 8.3 [DEX] [noBD]
  • CFW Evilnat 4.89.3 COBRA 8.3 [DEX] [noBD+noBT]
  • CFW Evilnat 4.89.3 COBRA 8.3 [DEX] [noBT]
  • CFW Evilnat 4.89.3 COBRA 8.3 [DEX] [OC]
  Random Screen (xai_plugin feature)
  
  Spoiler

  
• 
  (link) With official bguerville PS3 Toolset down, How do i install CFW from OFW?
  
  • via aldostools: "At this moment bgtoolset is unavailable. The service is supposed to come back soon.
    However, bguerville is facing personal issues that have attend first. So there is not a concrete ETA.
    
    If you need to use CFW for specific reasons (like development or specific features), you should get a PS3 with CFW already installed, get a hardware flasher or a CFW compatible model with 4.85 or lower.
    
    There are other options is development like HEN Flasher or lmn7's updated ps3xploit flash writer for 4.89, but they haven't been released yet. There are also fake copies of bgtoolset that you should avoid due they cause random bricks. You may see reports from users saying that it's safe because it worked for them. The problem is that the fake copy fails randomly under different conditions.
    
    If you use PS3 only to play games, you can install 4.89 HFW + HEN. It's proven to be safe and you will enjoy 95% of the CFW features without having to wait. "
  
  (link) How do I know which CFW version to install on my PS3 ?
  
  via @Adlostools Typical users only need Evilnat 4.89.3 [CEX].
  
  If you want the advanced features like DEX support or OtherOS, then install Evilnat 4.89.3 [CEX] [PEX].
  
  The PUP labeled [OC] are overclocked. They are recommended if your console doesn't have overheating issues.
  
  If your console is broken (doesn't have Bluray Drive or BlueTooth module or both) then use the PUP label [noBD], [noBT] or [noBD+noBT].
  
  If your console is in DEX mode (typically if you converted it to DEX using Rebug 4.84.2), then you should install Evilnat 4.89.3 DEX or D-PEX.
  
  In summary, Evilnat 4.89.3 [CEX] [PEX] [OC] is the best option for most of the users.​
  
  
  
  What does all these mean OC / DEX / PEX/ D-PEX?
  
  • PEX= A Hybrid of debug (DEX) & retail (CEX) (like Rebug REX from the past)
    
  • D-PEX = Is the same as PEX (just installs on PS3 debug units)
  • CEX = Full Retail (CEX) firmware for retail console's
  • DEX = Full Debug (DEX) Firmware for debug console's (or converted)
    
  • noBD = BluRay Drive software patched (removed), allows for console's with damaged daugther boards to launch stored apps/content (on HDD/storage media) from XMB (otherwise can't)
  • noBT = Same as noBD but with damaged Bluetooth board.
  • OC= Overclocked (CPU/GDDR3 RAM) - if console has heating issue's not advised.
  
  (link) What is the difference between CEX and PEX? And DEX and D-PEX? DEX is only the DEX fw? D-PEX can switch between DEX and CEX?
  
  • via Evilnat: CEX and PEX have options to swap kernel and convert to CEX/DEX. CEX and DEX versions are like any other standard CFW, like my 4.89.2, but without those options because it only have one kernel
  ​
  (link) What's different between DEX and D-PEX?
  
  • via Evilnat: CEX and DEX are standard CFWs (with default kernel for CEX/DEX) and PEX and D-PEX are like REX and D-REX (with both Kernel CEX and DEX in CoreOS)
  
  (link) What should i do if i already have Evilnat 4.89 on my PS3?
  
  • via Evilnat: You can install PEX or CEX with the new PS3UPDAT.PUP. If you want to install D-PEX or DEX you need to convert it to DEX first (available on PEX and D-PEX)
  
  (link) Does this iteration of otheros only resize of format the drive when allocatting?
  
  • via Evilnat: You mean [Resize VFLASH/NAND Regions] option? This will not format the HDD, to do that and allocate 22gb for OtherOS on internal HDD, you need to use [Restore PS3 System] from Recovery Menu formatting the HDD
  
  (link) I installed the CEX OC version and I wanted to switch to the DEX version, but it says Data is corrupted 80029CCA
  
  • via Evilnat: If you want to install DEX, you need to install PEX first (because your TargetID is CEX), convert to DEX, reboot the PS3 and now you can install DEX
  
  (link) Do we have any tutorial on how to install this CFW? I'm currently on 4.87 OFW and I'm finding a bunch of youtube tutorials that require to open some ps3xploit page through the PS3 browser and install the CFW. Last time I installed CFW, I copied the file on the USB stick and installed it on the PS3 so I'm not sure what to do now.
  
  • via Aldostools: No. Currently the new CFW Evilnat 4.89.3 is available only for users already on CFW, with OFW 4.85 and below (they need to use first the ps3xploit flash writer), or with a hardware flasher.
    
    Users already on CFW CEX or OFW 3.55 and lower, can install CFW Evilnat 4.89.3 PEX or CEX directly from XMB or recovery menu. Just rename the PUP to PS3UPDAT.PUP and copy it the path /dev_usb000/PS3/UPDATE
    
    Users with Rebug on DEX mode can install CFW Evilnat 4.89.3 D-PEX.
    
    Users with OFW 3.56 to 4.85 can use ps3xploit flash writer to patch the PS3 to allow CFW installation.
    
    Users with OFW 4.86 to 4.89 should wait and avoid any dangerous clone of bgtoolset. Meanwhile they can install HFW+HEN until a safe flash tool is available (bgtoolset, lmn7's ps3xploit flash writer for 4.89 or HEN Flasher).
    
    noBD/noBT/noBD+noBT editions are for PS3s with bluray drive and/or bluetooth module damaged.
    
    The OC editions are custom versions with GPU / GDDR3 RAM Clock speeds overclocked to 650 Mhz & 750 Mhz respectively.
  
  
  Additional FAQ on the PS3 (wip thread)
  
  • https://www.psx-place.com/threads/playstation-3-faq-2023-wip.39181/

Final Words (via @Evilnat)​

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:

• Cobra 8.3: https://github.com/Evilnat/Cobra-PS3/tree/master/8.3
• xai_plugin: https://github.com/Evilnat/xai_plugin

Warning:
BEWARE OF IMPOSTER version's OF Bguerville's PS3 Toolset, they carry a brick risk. See more info.
https://www.psx-place.com/threads/b...-for-4-82-4-89-by-p-px-team-is-a-fraud.39266/​

Downloads & Complete Information (Read All) in the Official Release Thread @:
https://www.psx-place.com/threads/cfw-4-89-3-evilnat-cobra-8-3-cex-dex.37294/​

 

Did you have the SSD before updating to 4.89.3 CEX?

EDIT: What CFW did you have before?
EDIT2: Is your PS3 BC?

I came from 4.88 rebug updated to the new 4.89.3 with the 60gb inside then I put a 1tb ssd and it formatted fine. started putting games and it was fine but when I try the ps1 or ps2 backups it shows as a data disc instead of a game. my PS3 is CECHA01 and it is most definitely backwards compatible.

 

Really not needed.
No need to port that stuff to 4.84, when all has been ported to 4.89

Would be really nice though.

Hopefully someone can port Evilnats plug-in and updated Cobra to 4.84 in future.

Huge Respect to Evilnat and the other PS3 devs though, following the news and it's so nice to see this kind of thing in 2023.

 

I came from 4.88 rebug updated to the new 4.89.3 with the 60gb inside then I put a 1tb ssd and it formatted fine. started putting games and it was fine but when I try the ps1 or ps2 backups it shows as a data disc instead of a game. my PS3 is CECHA01 and it is most definitely backwards compatible.

As far as I know there is no official Rebug 4.88, it must be 4.86 LITE spoofed to 4.88.

Were you using the SSD in said CFW Rebug? If you have started using it on my CFW it is possible that it may be the SSD, some give problems on the PS3. Could you confirm it for me?

EDIT: Someone confirmed on twitter that burned PS2 games works in a BC PS3 in my CFW with HDD
EDIT2: Someone with SSD can't play burned PS2 games but if he switches to HDD it can load them

 

As far as I know there is no official Rebug 4.88, it must be 4.86 LITE spoofed to 4.88.

Were you using the SSD in said CFW Rebug? If you have started using it on my CFW it is possible that it may be the SSD, some give problems on the PS3. Could you confirm it for me?

EDIT: Someone confirmed on twitter that burned PS2 games works in a BC PS3 in my CFW with HDD
EDIT2: Someone with SSD can't play burned PS2 games but if he switches to HDD it can load them

I can't run ps2 via DVD but I can via .iso. My ps3 is ceche/partial emulation.
- edit: it is recognized as video dvd.

 

As far as I know there is no official Rebug 4.88, it must be 4.86 LITE spoofed to 4.88.

Were you using the SSD in said CFW Rebug? If you have started using it on my CFW it is possible that it may be the SSD, some give problems on the PS3. Could you confirm it for me?

EDIT: Someone confirmed on twitter that burned PS2 games works in a BC PS3 in my CFW with HDD
EDIT2: Someone with SSD can't play burned PS2 games but if he switches to HDD it can load them

I was still using the original 60GB HDD on the rebug I was on before updating. I added the SSD when I got on Evilnat. is there a solution to this or is there an SSD that will work correctly ?

 

@Evilnat , still same issue

Model: CECHG01
Cfw: 4.89.3 cex

Issue: xia updater 1.2 downloads & installs, run the pkg from game column but console just black screen then beep and reboot. No change. Cobra 8.3 shows in the display.

Note: updater shows 1.2 pex/dpex

I am installing the pex cfw oc now. We will see what happens.

Update: confirmed, the plain cex cfw xia updater doesn't update properly. After pex cfw oc install xia 1.2 updated as expected.

So far pex oc is running nicely.

There should be info display for current xia version installed. Maybe a display showing all plugins installed with current versions and date info etc would be nice as well.

Feature request:
- a cfw tools updater might be useful for future proofing 4.89.3 and forward tool upgrades.
- a plugin/vsh type repository in cfw tools for easy install/uninstall etc..

 

I can't run ps2 via DVD but I can via .iso. My ps3 is ceche/partial emulation.
- edit: it is recognized as video dvd.

Does this happen to you with all the PS2 discs or with some in particular? Do you have webMAN MOD and Cobra enabled?

I was still using the original 60GB HDD on the rebug I was on before updating. I added the SSD when I got on Evilnat. is there a solution to this or is there an SSD that will work correctly ?

Some SSDs give problems on PS3 but I don't think the cause is known, I don't know if will be a fix to this, but at this moment you can try to put back the HDD and try if the game loads, if it does I think the problem is caused by the SSD

@Evilnat , still same issue

Model: CECHG01
Cfw: 4.89.3 cex

Issue: xia updater 1.2 downloads & installs, run the pkg from game column but console just black screen then beep and reboot. No change. Cobra 8.3 shows in the display.

Note: updater shows 1.2 pex/dpex

I am installing the pex cfw oc now. We will see what happens.

Update: confirmed, the plain cex cfw xia updater doesn't update properly. After pex cfw oc install xia 1.2 updated as expected.

So far pex oc is running nicely.

There should be info display for current xia version installed. Maybe a display showing all plugins installed with current versions and date info etc would be nice as well.

Feature request:
- a cfw tools updater might be useful for future proofing 4.89.3 and forward tool upgrades.
- a plugin/vsh type repository in cfw tools for easy install/uninstall etc..

Did you try to re-download 4.89.3 CEX? I updated all CFW to fix the updater on CEX and DEX a few days ago

4.89.3 CEX: https://mega.nz/file/YV9hVIIb#uafNaEhgosViQGOeJCMjsXMYE4aHyqeN6uIy3cyBG_A

Also xai_updater is downloading a PKG from my xai_plugin repository: https://github.com/Evilnat/xai_plugin/tree/latest_release

 

I came from 4.88 rebug updated to the new 4.89.3 with the 60gb inside then I put a 1tb ssd and it formatted fine. started putting games and it was fine but when I try the ps1 or ps2 backups it shows as a data disc instead of a game. my PS3 is CECHA01 and it is most definitely backwards compatible.

This is due to a ssd or sshd being installed in the ps3, for whatever reason a normal hdd makes this problem go away. Just use a normal 1tb hdd and the backup psx/ps2 discs will be detected properly, I have this exact same issue and I unfortunately can't use a ssd in my ps3 because of this, it's also a CECHA01 model.

I know this isn't an Evilnat issue but a general cobra issue as it happens on any cobra cfw.

 

Does this happen to you with all the PS2 discs or with some in particular? Do you have webMAN MOD and Cobra enabled?


Some SSDs give problems on PS3 but I don't think the cause is known, I don't know if will be a fix to this, but at this moment you can try to put back the HDD and try if the game loads, if it does I think the problem is caused by the SSD


Did you try to re-download 4.89.3 CEX? I updated all CFW to fix the updater on CEX and DEX a few days ago

4.89.3 CEX: mega.nz/file/YV9hVIIb#uafNaEhgosViQGOeJCMjsXMYE4aHyqeN6uIy3cyBG_A

Also xai_updater is downloading a PKG from my xai_plugin repository: github.com/Evilnat/xai_plugin/tree/latest_release

As soon as I click on Enable FTP on Evilnat 4.89.3 with an external HDD attached, the PS3 freezes. I tried other external HDDs and USB Flash Drives and it also freezes. I don't have this problem with no USB devices connected to the PS3.

IRISMAN also freezes after transferring a large file from the PC to the PS3 and exiting the app with an external HDD connected to the PS3. I tried other external HDDs and USB Flash Drives and it also freezes and it even froze once with the DualShock 3 connected to the PS3 via USB cable.

Also, I found out the PS3 freezes after enabling FTP and disabling it with no USB devices attached.

 

Added a few more things to the FAQ tab, mostly gathering questions that Evilnat and Aldostools have been answering.. Will add some more

 

I wonder what makes SSD and SSHD break PS2 "DVD" but ISO. Good news is that it only affects BC and Semi BC at least.

 

I wonder what makes SSD and SSHD break PS2 "DVD" but ISO. Good news is that it only affects BC and Semi BC at least.

In Open PS2 Loader, SATA-III disks on some Network Adapters must be slowing down to SATA-I by jumper, or speed set from default UDMA to MDMA or else it will break game booting. Maybe it is somehow related to sector access time?

 

I wonder what makes SSD and SSHD break PS2 "DVD" but ISO. Good news is that it only affects BC and Semi BC at least.

I guess it could be some memory issue in the function is_psx() that prevents the proper detection of the disc type.

I suspect that page_allocate_auto() is failing to allocate the 2KB needed to read the sector 16 used to detect PSX/PS2 discs.
https://github.com/Evilnat/Cobra-PS3/blob/master/8.4/4.89/NORMAL/CEX/SRC/stage2/storage_ext.c#L1154

It would be interesting to know what real disc type & effective disc type the users are getting with stage2 debug version.

@Evilnat may need to make a custom stage2 debug with additional debug messages in is_psx() to know what is happening inside that function.

 

I guess it could be some memory issue in the function is_psx() that prevents the proper detection of the disc type.

I suspect that page_allocate_auto() is failing to allocate the 2KB needed to read the sector 16 used to detect PSX/PS2 discs.
github.com/Evilnat/Cobra-PS3/blob/master/8.4/4.89/NORMAL/CEX/SRC/stage2/storage_ext.c#L1154

It would be interesting to know what real disc type & effective disc type the users are getting with stage2 debug version.

@Evilnat may need to make a custom stage2 debug with additional debug messages in is_psx() to know what is happening inside that function.

Could you help me with my problem?

 

Could you help me with my problem?

"Enable FTP" is a new feature in Evilnat 4.89.3 that I haven't used.

If it is causing issues in your system, I recommend you that keep that option disabled and rely on traditional FTP servers like webMAN MOD, multiMAN, IRISMAN, Rebug Toolbox or OpenPS3FTP plugin.

Running multiple FTP servers on the same TCP port cause conflicts and may result in memory issues.

 

"Enable FTP" is a new feature in Evilnat 4.89.3 that I haven't used.

If it is causing issues in your system, I recommend you that keep that option disabled and rely on traditional FTP servers like webMAN MOD, multiMAN, IRISMAN, Rebug Toolbox or OpenPS3FTP plugin.

Running multiple FTP servers on the same TCP port cause conflicts and may result in memory issues.

But I have that issue by clicking the "Enable FTP" setting and by just exiting IRISMAN after transferring a file to the PS3 via FTP.

 

So does this mean that 4.84.2 D-REX can finally be scrapped for good?

Is there anything that was unable to be ported into this D-PEX build to look out for?

What about mod loaders that boot like game and are able to detect your firmware build? Will these still work and be able to detect latest FWs? Asking because I've always used them on either 4.82.2 or 4.84.2?

(Loader like for changing EBOOTs or SPRX from loader's USRDIR\apps directory?)

I'm definitely ready for 4.89 with DEX capabilities, just wondering if there are any risks or if this should be considered to finally surpass everything that REBUG team did in past?

This seems like amazing news... I just tend to be a bit of a worry-wart about my PS3 lol

 

Is it really compatible with all PS2 games like it's stated? In that case, are PS2 CONFIG Database and the PS2 Classics Emulator Compatibiloty List redudant?

 

Is it really compatible with all PS2 games like it's stated? In that case, are PS2 CONFIG Database and the PS2 Classics Emulator Compatibiloty List redudant?

"Full PS2 Games Compatibility" is a bit overhyped.

PS2 compatibility is not "full". It is "good" if the PS2 CONFIG database is used. Without the configs, it would be "fair".

There are games with issues even on consoles with full backward compatibility.

 

If we could change this damn Bilinear filtering to use Nearest Neighbour, it would be a game changer for PS2 soft emulation. But until then, no matter how greatly patches can fix the emulation, it always be blurry unreadable mass displayed on TV.