Mamba Loader (+AutoLoader)

yeah, i edited my other comment, but the problem i was having is it would freeze almost right after i selected system update in recovery. swapped hdd, installed newest cfw and then put the other drive back in and reinstalled the same cfw as on the spare drive.
 
No0bZiLLa said:
the problem i was having is it would freeze almost right after i selected system update in recovery.
Click to expand...
btw, that is a major problem of this core stuff, which i first encountered with old ccapi versions. if anything goes wrong this always happens in recovery.
 
I dun goof'd and installed the Mamba Loader version from the first post in this thread, which is obviously outdated. My CFW is probably 6-8 months old, so not the latest but not so outdated to be outright compatible.
When I installed I directly enabled the Mamba Loader autostart on boot and now when loading the main screen the screen freezes and controller stops responding... I also have to turn off the console by the back power switch because the power button won't respond.

Any ideas on how to disable the Mamba Loader from booting when you can't finish boot?

Firmware is CEX Ferrox, exact version is unknown but 6-8 months old.

PS. Reading from previous diagnoses in this thread, I don't have a device connected to the USB ports.
 
Last edited:
hopugop said:
I dun goof'd and installed the Mamba Loader version from the first post in this thread, which is obviosly outdated. My CFW is probably 6-8 months old, so not the latest but not so outdated. When I installed I directly enabled the autostart on boot and now when loading the main screen the screen freezes and controller stops responding... I also have to turn off the console by the back power switch because the power button won't respond. Any ideas on how to disable the Mamba Loader from booting when you can't finish boot?

Firmware is CEX Ferrox.
Click to expand...
Easily done with the flag method.
Use a USB stick formatted in fat32. With your PC, create a folder named "core_flags" on the stick, in it create a dummy file (an empty txt file made with Notepad without extension will do!) named "failsafe". Use lower case only.
The path should look like this:
Code: 
x:\core_flags\failsafe
Plug the USB stick in a usb port of the ps3 then turn the console on.
Now you can uninstall Mamba + Autoloader if you wish.

You can also use the "mamba_off" flag instead of "failsafe", in this case, Mamba is disabled but the plugins like webman still get loaded with prx loader.

Download the most recent Mamba+Autoloader pkg (v3.1.4) from http://store.brewology.com/ahomebrew.php?brewid=287.
Take the opportunity to read the provided information in the Release Notes Tab. [emoji6]
And before installing the autoloader, you should always try running Mamba from the XMB icon first to make sure everything is fine!
After launching Mamba, run multiMAN, if it opens as mmCM, it means Mamba is working, you can mount a game for further confirmation.
If all is well, you can finally install the Autoloader. And if ever you experience more problems, you now know how to disable the autoloader with the core_flags flag system... [emoji6]
 
Last edited:
bguerville said:
Easily done with the flag method.
Use a USB stick formatted in fat32. With your PC, create a folder named "core_flags" on the stick, in it create a dummy file (an empty txt file made with Notepad without extension will do!) named "failsafe". Use lower case only.
The path should look like this:
Code: 
x:\core_flags\failsafe
Plug the USB stick in a usb port of the ps3 then turn the console on.
Now you can uninstall Mamba + Autoloader if you wish.

You can also use the "mamba_off" flag instead of "failsafe", in this case, Mamba is disabled but the plugins like webman still get loaded with prx loader.

Download the most recent one (v3.1.4) from http://store.brewology.com/ahomebrew.php?brewid=287.
Take the opportunity to read the provided information in the Release Notes Tab. [emoji6]
And before installing the autoloader, test running Mamba from the XMB icon to make sure everything is fine!
Click to expand...

It worked! I had to retry several times but in the end I got everything right! Thanks a lot for your help and I'll surely read on and be more careful :)
 
Last edited by a moderator:
arfgh said:
is it possible an update to use it on current 4.90 CFW ?
i used this a lot in 4.84... but...
Click to expand...
Since it's introduction in Rebug 4.84.2, all Cobra in later firmware versions include the nocfw_kernel_plugin payload. That is a direct replacement for Mamba loader.

That payload allows to load a kernel plugin like Mamba just indicating the path of the mamba file in /dev_hdd0/boot_plugins_kernel_nocobra.txt

The unique requirements are that Cobra should be disabled and a valid Mamba payload must exist in the path of the txt.

If you enter to Recovery menu the txt is deleted. This is a failsafe measure to prevent semi-brick your console in case of defects in the kernel payload.
 
aldostools said:
Since it's introduction in Rebug 4.84.2, all Cobra in later firmware versions include the nocfw_kernel_plugin payload. That is a direct replacement for Mamba loader.

That payload allows to load a kernel plugin like Mamba just indicating the path of the mamba file in /dev_hdd0/boot_plugins_kernel_nocobra.txt

The unique requirements are that Cobra should be disabled and a valid Mamba payload must exist in the path of the txt.

If you enter to Recovery menu the txt is deleted. This is a failsafe measure to prevent semi-brick your console in case of defects in the kernel payload.
Click to expand...

Aldo, the reason of my request is that i am on CFW HABIB 4.84.2 working in mamba mode, since in cobra mode i had lot of problems with corrupt savegames. And also by the way i like a lot to use the iris manager fork Play Manager v1.12 becase the fan threshold settings on it including also very helful 5 profiles. Also the interval to show the system temperatures via select + L2. Can i request those settings in your irisman ?

I have seen so far you irisman is missing those interesting features... but the problem with Play Manager is that is only prepared to work until CFW 4.86, and also, in mamba mode is unable to load itself, for that reason i needed Mamba PRX loader...
 
arfgh said:
Aldo, the reason of my request is that i am on CFW HABIB 4.84.2 working in mamba mode, since in cobra mode i had lot of problems with corrupt savegames. And also by the way i like a lot to use the iris manager fork Play Manager v1.12 becase the fan threshold settings on it including also very helful 5 profiles. Also the interval to show the system temperatures via select + L2. Can i request those settings in your irisman ?

I have seen so far you irisman is missing those interesting features... but the problem with Play Manager is that is only prepared to work until CFW 4.86, and also, in mamba mode is unable to load itself, for that reason i needed Mamba PRX loader...
Click to expand...

Play Manager is a fork of the original Iris Manager with minimum changes to the original code.

On the other had, IRISMAN has massive changes and improvements. As far as I know almost all the features in Iris Manager are present in IRISMAN, maybe using different buttons.

In regards to your request, currently I'm not adding new features to IRISMAN. Only fixes for critical bugs or to support new firmware versions. The project is open source and anyone interested can submit a PR on Github. I'll be glad to add them always that the changes are not superfluous.

BTW CFW 4.84.3 Starbuged introduced the nocfw kernel payload feature that I commented previously.
https://www.psx-place.com/threads/4-84-3-starbuged-w-cobra-8-01-new-update-in-from-habib.23057/
 
aldostools said:
Play Manager is a fork of the original Iris Manager with minimum changes to the original code.

On the other had, IRISMAN has massive changes and improvements. As far as I know almost all the features in Iris Manager are present in IRISMAN, maybe using different buttons.

In regards to your request, currently I'm not adding new features to IRISMAN. Only fixes for critical bugs or to support new firmware versions. The project is open source and anyone interested can submit a PR on Github. I'll be glad to add them always that the changes are not superfluous.

BTW CFW 4.84.3 Starbuged introduced the nocfw kernel payload feature that I commented previously.
https://www.psx-place.com/threads/4-84-3-starbuged-w-cobra-8-01-new-update-in-from-habib.23057/
Click to expand...

and do you know that when using select + L2 in your irisman the all notifications will be threw with no delay in between ? i have seen that in 4.89 version. Even knowing that, you wont fix it ? i have to insist that none of the iris manager forks i have tested, all of them, have the required features like Play Manager offer, that means usable.
 
Last edited:
arfgh said:
and do you know that when using select + L2 in your irisman the all notifications will be threw with no delay in between ? i have seen that in 4.89 version. Even knowing that, you wont fix it ? i have to insist that none of the iris manager forks i have tested, all of them, have the required features like Play Manager offer, that means usable.
Click to expand...

Play Manager is open source too. With very basic knowledge of C it is possible to update it to support 4.90.
I haven't tested, but I guess it could 4.90 could work since LV2 kernel it has the same offsets of 4.80.

The latest source code available is Play Manager 1.11
https://www.mediafire.com/file/grwgpwb436zkna8/playmanager-src-v1.11.7z/file

To make it work on 4.83-4.89, I think you just need to change the line 165 in source\payload_475\payload_475.c to:
if(toc == 0x800000000034FBB0ULL && peekq(0x80000000002FCB68ULL) >= 0x323031372F30382FULL)
 
Last edited:
aldostools said:
Play Manager is open source too. With very basic knowledge of C it is possible to update it to support 4.90.
I haven't tested, but I guess it could 4.90 could work since LV2 kernel it has the same offsets of 4.80.

The latest source code available is Play Manager 1.11
https://www.mediafire.com/file/grwgpwb436zkna8/playmanager-src-v1.11.7z/file

To make it work on 4.83-4.89, I think you just need to change the line 165 in source\payload_475\payload_475.c to:
if(toc == 0x800000000034FBB0ULL && peekq(0x80000000002FCB68ULL) >= 0x323031372F30382FULL)
Click to expand...
yes, i know. The author never shared last version source.
Anyways you should test these features i am pointing and compare to your irisman, and then say if will be bad to have same in irisman...
I hope that you reconsider it, since the 5 profiles, and the configured delay of notifications is A MUST HAVE.
 
You must log in or register to reply here.

Similar threads

Back
Top