PS3 Mamba PRX Loader (+AutoLoader) v2.0 by _NzV_

Another new update has arose for the recently released MAMBA PRX Loader (+AutoLoader) homebrew application for PS3 CFW user's by developer _NzV_.. This useful utility now reaches verson 2.0 and with this update some new changes has been implemented; such as new payload to load MAMBA instead of using "sky" from Estwald's IRIS Manager [break]ss[/break](the original creator of MAMBA). The new payload will offer some new benifits while loading MAMBA the "same way as stage2.bin on COBRA CFW". Then also the utility is no longer tied down to any speific firmware, below you can see how this was achieved and also more on what v2.0 has to offer. View additional usuage and information in the links also provided below:


MAMBA PRX Loader (+AutoLoad).png


What is MAMBA ?
MAMBA is a lite version of COBRA (No NetIso, PSP and PS2 support) for non cobra cfw (or cobra cfw with cobra toggle off), it add features like NFTS support, ISO support, VSH plugins, PS3M_API, ... to your firmware.
What Is MAMBA/PRX LOADER (+AUTOLOAD) ?
MAMBA/PRX Loader is an homebrew who allow you to load MAMBA and/or VSH plugins (with MAMBA or PRX Loader) by two different way : at system boot or after.

_NzV_ said:
v2.0.0 is ready main topic updated and source on github updated too.

What have been changed since v1.5.0:

  • MAMBA/PRX Loader has now is own payload to load MAMBA instead of using Iris (sky) payload. The new payload will load MAMBA as the same way was stage2.bin on COBRA CFW.
  • sys_init_osd.self (Autoloader) is no more firmware specific (payloads are no more embedded in it)
  • sys_init_osd.self (Autoloader) will now clear memory used by COBRA stage1 (if a COBRA CFW is detected and only when cobra was toggled off)

Update Note: If you have already any version previous installed on your PS3 uninstall it first to free some space.

How MAMBA/PRX Loader v2.0.0 do his job:

  • Step 1: Install the new payload who add the ability to load MAMBA and VSH plugins (less than 4Ko, use syscall 1022).
  • Step 2 (if user don't have disable MAMBA loading): Load MAMBA using the new payload (if user don't have disable this loading).
  • Step 3 (if user don't have disable VSH plugins loading): Load VSH plugins (MAMBA will be used to load them, but if it was disabled by user the new payload will be used to load them like PRX Loader did).
  • Setp 4: Uninstall the new payload (clear syscall 1022 and memory used by the payload).

MAMBA/PRX Autoloader work as the same way.

Download: MAMBA_PRX_Loader
Source Code: https://github.com/NzV/MAMBA_PRX_Loader

Source of information:
psx-place.com/forum

 
Another report regarding mamba loader, tested on 4.30 dex, it caused 3 beeps and shutdown I think it needs correction on symbols, I have corrected version in my house, I will test this when I get back home or maybe it is just missing memory protection patch.. Haven't checked source yet

EDIT,

After applying lv2mem protection patch, it worked, prx loader worked fine as well as mamba, I have a feeling mamba itself was working fine on IRIS but its payload was somehow improper, ported by MLT by the way. So now it solves my mystery with mamba payload of 4.30 dex :)


Sent from my iPhone using Tapatalk
 
Last edited:
Another report regarding mamba loader, tested on 4.30 dex, it caused 3 beeps and shutdown I think it needs correction on symbols, I have corrected version in my house, I will test this when I get back home or maybe it is just missing memory protection patch.. Haven't checked source yet


Sent from my iPhone using Tapatalk

LV2 memory protection patch is only enabled for 446, i need to enable it for other fw ?

By way i have tried to load stage2.bin from cobra instead of mamba.bin with my payload... it works too^^ (but it cant do all necessary patch to vsh.self since the process was started before we cant write from the offset 0x10000 to 0x10000+vsh_size)
 
LV2 memory protection patch is only enabled for 446, i need to enable it for other fw ?

By way i have tried to load stage2.bin from cobra instead of mamba.bin with my payload... it works too^^ (but it cant do all necessary patch to vsh.self since the process was started before we cant write from the offset 0x10000 to 0x10000+vsh_size)

I edited my post, it works after applying lv2mem patch, you should apply that for all rebug cfw below 4.46


Sent from my iPhone using Tapatalk
 
I edited my post, it works after applying lv2mem patch, you should apply that for all rebug cfw below 4.46


Sent from my iPhone using Tapatalk

Great news :)

All rebuf cfw have this folder ""/dev_flash/rebug/" if iam right ?
i can do a check on it to see if its rebug or not and apply LV2 mem patch?
 
Yes all rebug cfw have rebug folder in dev flash, lv2mem protection patch is not needed since 4.53, :)


Sent from my iPhone using Tapatalk
 
[MENTION=600]_NzV_[/MENTION]
Is it possible to install the mamba without prx_loader by just poking it in lv2 ?
 
[MENTION=600]_NzV_[/MENTION]
Is it possible to install the mamba without prx_loader by just poking it in lv2 ?

You need to alloc LV2 memory before poking it. If you can alloc LV2 memory without payload so you can do it like this :

-Alloc LV2 mem
-Poke MAMBA to it
-Create a syscall to call the poked content
-Make a call to this syscall to load MAMBA
-Done, you can also remove the syscall pointer you used before its no more needed

After if you want to use my payload but without features of PRX Loader include in it you can build it without, you just need to edit main.c and remove this line "#define PRX_LOADER" (i have updated source code on github for this)
 
Grate work! love to see stuff like this evolve.

Interesting thought pattern. After netiso support of course....lol
The xmb my games menu is nice, refreshing the xml isn't bad, but sometimes you don't want to use the web interface and you don't want to restart, lol.
The video category with UMS does a nice job with the refreshing of content. I'm not sure if it can be replicated to work with netiso/cobra/mamba...but that'd be a great pathway as well. :)
Auto rebuilding XMB menu? hehehe... :)

If only dlna could exploit the games menu.......

but if that were true...that would explain sony pulling it for ps4....just a conspiracy theory idea lol....
 

Trending content

Back
Top