Standard cfw vs cobra vs rebug

I don't know what cex vs Dex even is

CEX is Retail for CECH PS3's, what most people use. DEX is DEBUG FW used on DECH Debugging units that games dev's use. Only REBUG REX/D-REX CFWs allow your CECH to be convert DEX to be able to use these features, Other wise you need a DECH model PS3 to use DEX.

REBUG REX- used on CFW compatible CECHs to be used a CEX or converted to DEX.

REBUG D-REX - used on CFW compatible DECH PS3's or can be installed on converted CECH units.

NOTE: You cannot install DEX OFW on a converted CECH unit as it can brick the PS3 and it can also trigger a panic in lv1ldr as there is an EID check here.
 
Last edited:
Also, since running a Cobra CFW and have the ability to run background plugins on boot. Using a plugin like PSNpatch disables a PSN connection until you disable CFW syscalls (i.e. temporary disable CFW until next boot cycle)
really.. i can still sign in just using psn patch..

thx for the tip. keep up the good work:angel:
 
Wow a lot of info here. Thanks everyone! So cex is the way to go unless I want to do advanced stuff that's way over my head...

And to summarize, if I want to play PS3 isos, I should either do cobra cfw or REBUG lite? These 2 are my easiest options? Does REBUG lite play isos by default or do I have to do anything before trying to boot isos?
 
Wow a lot of info here. Thanks everyone! So cex is the way to go unless I want to do advanced stuff that's way over my head...

And to summarize, if I want to play PS3 isos, I should either do cobra cfw or REBUG lite? These 2 are my easiest options? Does REBUG lite play isos by default or do I have to do anything before trying to boot isos?
i dont really covert my games to iso.. i drag em to Games folder in HDD0. But best choice is rebug..once u know how to use everything.. it becomes very easy:tickled pink:
 
And to summarize, if I want to play PS3 isos, I should either do cobra cfw or REBUG lite? These 2 are my easiest options? Does REBUG lite play isos by default or do I have to do anything before trying to boot isos?

REBUG LITE has the Cobra payload included in the CFW so you will be able to play your PS3 game in ISO format using a backup manager.
 
Hopefully last question: it's probably okay to connect to internet when I want to ftp something and then disconnect after?
It is perfectly safe to be connected to the internet on CFW, just not PSN. You can FTP, use modified NoPSN packages such as YouTube (which normally requires PSN sign in) and update games via the XMB. All of these things are safe to do without posing any ban risk whatsoever. It's only when you connect to PSN while on CFW that you expose yourself to the possibility of an account and/or console ban.
 
I have ferrox standard 4.83 and it is not updated because my games run well without errors ps1 ps3 folder, ps2 does not work the classic ps2 when I try to put the rap my ps3 is blocked therefore it does not activate the ps2 applications, psp games pkg format, everything retro works ...... ps1 at a click the game enters either iso or bin cue format, some time ago I put the ferrox charges 4.83 and it gave me only errors it did not load anything from ps1 it does not recognize the saved data etc ... .. ..of rebug I don't know bn and the han or hen I don't like it, so I continued with ferroz standard 4.83 ..... I don't know if it's good to stay as I am or paste a cfw update to my console .. ... I have my multiman at 4.82 and I know what I can update but I think it can give me an error because it is a different version than the cfw ...
 
I have ferrox standard 4.83 and it is not updated because my games run well without errors ps1 ps3 folder, ps2 does not work the classic ps2 when I try to put the rap my ps3 is blocked therefore it does not activate the ps2 applications, psp games pkg format, everything retro works ...... ps1 at a click the game enters either iso or bin cue format, some time ago I put the ferrox charges 4.83 and it gave me only errors it did not load anything from ps1 it does not recognize the saved data etc ... .. ..of rebug I don't know bn and the han or hen I don't like it, so I continued with ferroz standard 4.83 ..... I don't know if it's good to stay as I am or paste a cfw update to my console .. ... I have my multiman at 4.82 and I know what I can update but I think it can give me an error because it is a different version than the cfw ...
Bienvenido al foro (welcome to the forum) :)
If you dont play online is ok to stay in a old firmware, as far that firmware version is equal or bigger than the firmware version required by the newest game of your collection, lets say... if the newest game you have requires 4.70 then you are good to stay in a 4.70 CFW
But there is no need for it, if at some point you are going to do some repair or manteinance tasks in the PS3 (like replacing hdd, or formattings it, or a cleanup to reinstall all software etc...), most probably the best thing you can do is to install the newest CFW first

About the backup managers, you can update them without problems because they keeps "backward compatibility" with previous CFW... so a backup manager released for 4.86 is going to work fine in 4.83 CFW
The latest multiman udpates are minor (doesnt adds new features as far i remember) so you are not going to find any improvement by updating it, but the code is very stable so nothing to worry, if a some point you have doubts about updating it... just update it

For the PS2 backups is a lot easyer to load them as a plain ISO (not encrypted, and not related with the "PS2 classics" format that requires a license and some trickery)
The point is... in CFW you should get used first to load the PS2 backups as a plain ISO (i suggest you to try managunz for this)... and later if you are curious take a look at how to create the "PS2 classics" format
 
friend good answer three questions 1) what difference is there between ferrox standard 4.83 and ferrox cobraa 4.83?
2) each folder of ps1 has my saved reads the game with a click reads the save without creating memory card ...... in cobraa ps1 games do not have options to emulate something that was in standard ferrox as netemu, at Clicking sends me to the xmb the game enters but the save can't I do to find the options that were in standard ferrox? .....
3) I suppose that in standard ferrox if I copy an iso ps3 it would not read it as it happens to me with ps2
Thank you for answering, I plan to switch to Ferrox Cobraa 4.86 because there is no standard Ferrox 4.86, but it is a thought ... but I must know the Cobraa to know how it works and if it works or if I stay or continue in Ferrox Standard 4.83.
 
friend good answer three questions 1) what difference is there between ferrox standard 4.83 and ferrox cobraa 4.83?
2) each folder of ps1 has my saved reads the game with a click reads the save without creating memory card ...... in cobraa ps1 games do not have options to emulate something that was in standard ferrox as netemu, at Clicking sends me to the xmb the game enters but the save can't I do to find the options that were in standard ferrox? .....
3) I suppose that in standard ferrox if I copy an iso ps3 it would not read it as it happens to me with ps2
Thank you for answering, I plan to switch to Ferrox Cobraa 4.86 because there is no standard Ferrox 4.86, but it is a thought ... but I must know the Cobraa to know how it works and if it works or if I stay or continue in Ferrox Standard 4.83.
1) Well, the biggest difference is the cobra :D
Is hard to write a short description of how cobra works and how many things it does, but lets say... cobra is a process that is hooked to a low level of the PS3 boot chain, is triggered automatically when the PS3 boots, and it runs in paralell to the firmware
The main goal of cobra is to allow to run plugins (custom programs that are going to run in paralell to the firmware too, in the background, active at all times) and to apply patches and deal with the emulators
Additionally, cobra have 8 "slots" to run plugins, and some of them are reserved to run internal plugins named rawseciso (this gives ISO support) and/or netiso (this gives ISO support by network)
Cobra have lot more features, im just mentioning the ones related with game backups

2) I dont understand well, you mean PS2 game format/s ?... well this could be a bit confusing because cobra have a lot of features related with the PS2 emulator/s. In old firmwares (before sony invented the "PS2 classics" and netemu) the saves was stored in "PS2 virtual memory cards" (is just a file, his internal structure is exactly like a real PS2 memory card) and this files are located under your "home" path in dev_hdd0
And with the "PS2 classics" format you are installing 2 memory cards located inside the installation directory of your "PS2 classics" game (so they belongs to the game, not to the system)

The format and locations of that PS2 virtual memory cards are different but are not an special problem
Cobra patches the emulator to use the old format... so you only need to "mount" a plain ISO and the saves are going to use the old format

3) This depends of the backup manager you use. When the source code of cobra was released there was a guy named estwald that was the mantainer of iris backup manager, and he made a derivate of cobra named "mamba", and he integrated mamba inside iris with the goal of having all/most of cobra features running inside a backup manager
The biggest difference is mamba starts when you enter in the backlup manager (not when the PS3 boots, like cobra)

Irisman and managunz (both are derivates of iris) have mamba integrated, they supports PS3 ISO since the first day (with 100% compatibility with the PS3 game library). The PS2 support was added later at some point, but im not so sure how good it works because nowadays most people uses a CFW with cobra (when irisman and managunz boots they autodetects that there is a "cobra running" and disables the internal mamba)
As far i remember... some months ago there was something broken in the mamba inside irisman (and probably managunz too) related with the PS2 support... but not sure about it
Anyway... you can try it right now, there is no need to update your firmware to check this

You can install irisman or managunz (latest version available), copy a non-encrypted (standard) ISO inside dev_hdd0/PS2ISO and try to mount it... and they should take you back to XMB with the "virtual" disc icon visible in [XMB]>[Game] column

*do the test with one of the PS2 games reported as "playable" in this list (this is important, by now you should ignore the other games with problems, or that requires a config file)
https://www.psdevwiki.com/ps3/PS2_Classics_Emulator_Compatibility_List
 

Similar threads

Back
Top