Yes you have add hash to rebug cfw..
Also you need remove that 4_81DEX from:
elif defined(FIRMWARE_4_81) || defined(FIRMWARE_4_81DEX)
And add 4_81DEX symbols separately.
Take 4.78CEX/DEX as example, the symbols to 4.81 are totally mess (as my engrish)
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...
Yes maybe the problem is the version of gcc.. i use gcc 4.1.1..
EDIT:
@Zar in the makefile replace the CFLAGS -O2 with -Os, that make the payload smaller and seems fix the problem..
Thanks! Yes the md5 probably always changed, the important is the size, i only want see if the problem is in the enviroment of Zar or something in the source..
I use linux (make_all.sh)
I never use windows to compile the mamba source.. maybe something is wrong in that .bat.. i don't know..
Maybe you can ask to @Joonie
Have you tried to compile only the payload 4.75 from console?
@Zar mmm.. i think you're right, my compiled payload differs in size..
your (24 october) = 88 256 md5 :70847be57d29b36e287e008cbc92d2f1
my (24 october) = 86 304 md5: 33379af4b4d793e81e592f9c2a2675c8
Try if my compiled payloads works..
Are you in dex or cex?
EDIT:
Nevermind.. i've tested now one psp game on 4.75.3 rebug (lv2 dex/cex and vsh dex/cex) and it works.. so i think we can exclude "the bad offset"
Have you tried set BUILD_TYPE to debug and get the debug log with socat?
I've not updated yet the payload mamba in the funny autoloader..
You need compile the mamba payload and add it to autoloader..
The old payload had problem with the cfw rebug: https://github.com/Ps3itaTeam/MAMBA/commit/3dcd37bd570790ecfe81fc7426e00b8dc19aee84
If that not work then the problem...
That because mamba v3.10 not has yet the support to 4.80.
Mamba v3.10 work great with the autoloader (new_core), the problem is with the backup manager..