CFW Mamba idea...

aldostools

developer MOD
Moderator
Developer
This is an idea that have been circulating in my mind...

Every time that a new OFW is released, we usually get first a Standard CEX edition & OFW Dual Boot edition, then Cobra is ported and we get Cobra Edition and finally REX when OFW Debug is leaked. Also NoBD variations are released in-between.

The question is: why CFW devs don't simply skip the Standard CEX edition (or even Cobra edition), and instead release a "CFW Mamba edition" with NzV mamba/prx auto-loader pre-installed?

The gap between Mamba 3.x & Cobra now is practically null... so a "Mamba edition" would have the benefits of being very easy to port (at least 2.x); prx loader, netiso, ps3mapi, PS3ISO, BDISO and PSXISO would be out-of-the-box features without extra software, webMAN could be pre-installed like in Rebug and the users wouldn't depend of having to install Mamba/PRX Loader (which rarely happens) or using IRISMAN to have ISO support.

Eventually Mamba payload could be updated with PS2ISO & PSPISO support without having to install a new "CFW Cobra edition"... The best of all, your CFW would be unique until others follow :)

What are your thoughts about this idea?
 
I don't know the details as they are beyond my knowledge but *if* difference between Cobra and Mamba are null and Mamba it's easier (why it is?) to maintain/implement, I have no objections as end user. :)
 
I don't know the details as they are beyond my knowledge but *if* difference between Cobra and Mamba are null and Mamba it's easier (why it is?) to maintain/implement, I have no objections as end user. :)

Indeed there are still differences, but internal (IIRC some non-critical patches are not implemented in Mamba)...

From the user's point of view, there are not big differences. e.g. The plugins are loaded from different files, but that can be changed easily; if Mamba 2.x is installed PSPISO and PS2ISO will not supported (but PS2 Classics & PSP Minis/Remaster are); if Mamba 3.x is installed, you won't notice the differences.

From the developer's point of view, Mamba 2.x (BDISO, DVDISO, PS3ISO, PSXISO, netiso & prx loader) is easier to port than Cobra because the number of offsets that are needed to find are less (~100 vs ~200). So the chances of errors are less. My tool GetSymbols can find 80-90% of the symbols accurately, so the port can be done in few minutes (maybe hours if things get hard).

Mamba 3.x (same as 2.x but with PSPISO + PS2ISO added) use almost the same number of offsets needed by Cobra. Also requires to calculate the hashes of various files: VSH, explore_plugin, hashes of emus (PS1, PS2, PSP), psp drm patches, etc. The chances of errors are higher and may need some hours to complete just to get a payload that only add PSP & PS2 emulation with ISO..

Mamba also is safer for developers, because the risk of bricks are reduced because it can be installed after the system boots. At most you get a black screen or have to hold down power off for 15 secs.


I like the idea, but I also like the idea of releasing a standard CFW and release everything else as standalone add-on :)

I think that was the idea that @Rancid-o came up with his last PS3iTA release.

Of course, if Rancid-o did all that work with Mamba 3.x, he should have thought of this idea first :)
 
I have a question regarding Mamba since I never used it. Lately I've been tinkering with building my own stealth version of Movian and was able to mask an older version (4.99) into Crackle that exits back to stealthMAN, and as deank stated stealthMAN isn't compatible with cobra enabled fw. So my question is, could it work with a Standard CEX+Mamba 2/3.x or would it fail loading ISOs as well?
 
Last edited:
I have a question regarding Mamba since I never used it. Lately I've been tinkering with building my own stealth version of Movian and was able to mask an older version (4.99) into Crackle that exists back to stealthMAN, and as deank stated stealthMAN isn't compatible with cobra enabled fw. So my question is, could it work with a Standard CEX+Mamba 2/3.x or would it fail loading ISOs as well?

I haven't used stealthMAN to confirm if it's compatible with Cobra or not, but if it is not compatible with Cobra as you state, then it shouldn't be compatible with Mamba either, since "Mamba" is just another name used by Estwald to refer to his fork of Cobra that initially only had partial ISO support.
 
I always liked of Mamba.
At season that I used it,did not have PSP or PS2 support.
I think that Mamba should be more disclosed.
Your idea,if it's done,will definitely take the name of the Mamba for front .
It's an excellent program,but many people still do not know it,how the user ordinary.
This is my vision as a spectator.
 
Some PSP Games for me (i know other say opposite, really depends on game) but Cobra PSP has played better for example Ghost & Goblins i can actually play it on Cobra, where as Remaster's or Mini's there is speed issues. (too fast). This various from game to game though. Where as some games play the same on all methods.
 
I have a question regarding Mamba since I never used it. Lately I've been tinkering with building my own stealth version of Movian and was able to mask an older version (4.99) into Crackle that exists back to stealthMAN, and as deank stated stealthMAN isn't compatible with cobra enabled fw. So my question is, could it work with a Standard CEX+Mamba 2/3.x or would it fail loading ISOs as well?
mmCM detects Mamba as Cobra, so everything works fully :)
 
mmCM detects Mamba as Cobra, so everything works fully :)
I appreciate your input Joonie, and I'm sure multiMAN detects Mamba in mmCM mode but deank designed stealthMAN a little bit differently. It not only installs in game_repo dir inside dev_hdd0/tmp as it's unable to load mmCM on Cobra enabled firmwares, and if Mamba only replaces the payload in Standard-CEX it probably won't load mmCM either like aldo said.
 
I appreciate your input Joonie, and I'm sure multiMAN detects Mamba in mmCM mode but deank designed stealthMAN a little bit differently. It not only installs in game_repo dir inside dev_hdd0/tmp as it's unable to load mmCM on Cobra enabled firmwares, and if Mamba only replaces the payload in Standard-CEX it probably won't load mmCM either like aldo said.

Ah I totally forgot about that, multiMAN release comes with two executable elf, one for multiMAN and another for mmCM, so if stealthMAN is missing mmCM, then probably won't work. but I haven't used stealthMAN ever since I got my very first ban while on Rogero 4.30 / stealthMAN, So I don't really know how that would work with Cobra/Mamba
 
Ah I totally forgot about that, multiMAN release comes with two executable elf, one for multiMAN and another for mmCM, so if stealthMAN is missing mmCM, then probably won't work. but I haven't used stealthMAN ever since I got my very first ban while on Rogero 4.30 / stealthMAN, So I don't really know how that would work with Cobra/Mamba
Yeah, I shouldn't change my MO for going online since I've been playing a few games and using PSN without a hitch since 2013 but with Phony loosening their grip (given the recent bizarre IDPS byte swap bug) I decided to stick my neck out a lil bit lol.
 
I like the idea, but I also like the idea of releasing a standard CFW and release everything else as standalone add-on :)

I think that was the idea that @Rancid-o came up with his last PS3iTA release.

Yes that was the idea..

Regarding "mamba 3.xx required the same amount of offset of cobra" well is not completely right:
- you don't need find the vsh offsets (aside vmode_patch_offset) you can simply set them to 0x0 if you want
- the lv2 symbols are less (if i remember right)
- you can use a single hash for all cfw (aside rebug), just take it from ofw

Ok no that big different but helps..
 
Yes that was the idea..

Regarding "mamba 3.xx required the same amount of offset of cobra" well is not completely right:
- you don't need find the vsh offsets (aside vmode_patch_offset) you can simply set them to 0x0 if you want
- the lv2 symbols are less (if i remember right)
- you can use a single hash for all cfw (aside rebug), just take it from ofw

Ok no that big different but helps..

I'll take a look at your changes on mamba see if I can adopt this to COBRA, @habib and I have never been a fan of Estwald's core, which was the reason why we kept messing with COBRA instead, but I think it's worth a shot to move along since MAMBA 3.XX now has more pros than cons :)
 
Yes that was the idea..

Regarding "mamba 3.xx required the same amount of offset of cobra" well is not completely right:
- you don't need find the vsh offsets (aside vmode_patch_offset) you can simply set them to 0x0 if you want
- the lv2 symbols are less (if i remember right)
- you can use a single hash for all cfw (aside rebug), just take it from ofw

Ok no that big different but helps..

Yes, you're right... the lv2 offsets are 45% less (108 in Mamba vs 194 in Cobra).

These definitively are a great advantage compared with Cobra :)

My point is that Mamba 3.x requires a little more time than 2.x, which can be done in few minutes with minimal effort ;)

And I should add that you did an awesome job in Mamba 3.x!
 
Indeed there are still differences, but internal (IIRC some non-critical patches are not implemented in Mamba)...

From the user's point of view, there are not big differences. e.g. The plugins are loaded from different files, but that can be changed easily; if Mamba 2.x is installed PSPISO and PS2ISO will not supported (but PS2 Classics & PSP Minis/Remaster are); if Mamba 3.x is installed, you won't notice the differences.

From the developer's point of view, Mamba 2.x (BDISO, DVDISO, PS3ISO, PSXISO, netiso & prx loader) is easier to port than Cobra because the number of offsets that are needed to find are less (~100 vs ~200). So the chances of errors are less. My tool GetSymbols can find 80-90% of the symbols accurately, so the port can be done in few minutes (maybe hours if things get hard).

Mamba 3.x (same as 2.x but with PSPISO + PS2ISO added) use almost the same number of offsets needed by Cobra. Also requires to calculate the hashes of various files: VSH, explore_plugin, hashes of emus (PS1, PS2, PSP), psp drm patches, etc. The chances of errors are higher and may need some hours to complete just to get a payload that only add PSP & PS2 emulation with ISO..

Mamba also is safer for developers, because the risk of bricks are reduced because it can be installed after the system boots. At most you get a black screen or have to hold down power off for 15 secs.




Of course, if Rancid-o did all that work with Mamba 3.x, he should have thought of this idea first :)

the idea is not bad but you have to implement and PS2ISO PSPISO to make it similar to the cobra.
Perhaps the experiences of @ Rancid-or can be useful, but if I remember correctly PS3ITA worked on DEX.
The best thing would be to merge the best features of Cobra and Mamba and realize "ANACONDA" This is a more futuristic idea.
A Union Project of all the experiences of the various developer.
 
Last edited:
the idea is not bad but you have to implement and PS2ISO PSPISO to make it similar to the cobra.
Perhaps the experiences of @ Rancid-or can be useful, but if I remember correctly PS3ITA worked on DEX.
The best thing would be to merge the best features of Cobra and Mamba and realize "ANACONDA" This is a more futuristic idea.
A Union Project of all the experiences of the various developer.

I don't understand what you mean... Rancid-O ad PS3ITA Team already added PSPISO and PS2ISO support to Mamba 3.x months ago. BTW it's still called Mamba, not "anaconda" or any other snake. IMO it could be called "Cobra" since there are no major differences anymore.

The latest IRISMAN 4.81 includes the Mamba payload from Rancid-O for *all* the CFW up to version 4.81.

It doesn't include the patched PS2EMUs, but you can install them separately using Mamba/PRX Loader 3.1.3, which also supports up to CFW 4.81. Using the auto-loader option, any CFW standard is transformed in a "CFW Cobra".

The point of this thread is that these patches could come already included in CFW Standard, eliminating the need of having 2 editions: one CFW standard and one CFW Cobra.

The second point suggested here is that the initial release of any new CFW could include Mamba 2.x, and later it could be updated to 3.x (when all the payload offsets are found and tested) without forcing the users to install a new CFW.


anaconda dont want none unless you got buns hun
Jump to 2:16 ;) Oh my gosh, look at her butt
 

Similar threads

Back
Top