Anonymous CFW 4.85 [Discussion]

@kozarovv @sandungas @STLcardsWS @lmn7 @DeViL303 i think problem is fixed ,i extract stage2 from spy cfw and i see that the hashes have not been updated (i mean with hashcal) i open stage2 in hex and compare the hashes in cobra source modulespatch.h and search them in HxD its kind of those hashs are static in last cobra i think

i restore back those instead of the one i calculate using Evilnat's Hashcal and compile stage2 again and seems like PS2 ISO are now readble and yellow icon instead of Unsupported Disc and playble and new clean CFW is comin ...

Capture d’écran (4700).png

Capture d’écran (4701).png

Capture d’écran (4702).png

Capture d’écran (4703).png

20191004_173339.jpg

20191004_173352.jpg

20191004_180658.jpg

20191004_180722.jpg

20191004_180724.jpg
 
Last edited:
Louay said:
those hashs are static in last cobra i think
Click to expand...

The module hashes have been static in cobra for a while now. Only needs changing if there is changes to the modules that cobra dynamically patches are significant enough to effect the hashcalc. As there have been no real significant changes in them the hashes can remain static. Or if you add some kind of new major patch to one of the modules yourself then it may need updating depending on what it is... ( This is my understanding of it as I see it and also after reading a post on it a while back by @bguerville )

This is why I asked if you changed anything else in the stage2, you also confirmed 100% what I found when you showed them screenshots of the hashcalc's you were using in your modules.h cobra source.... but I wasn't just going to give you the solution...

I gave you the bump in the right direction by mentioning the stage2.bin..... releasing a CFW means you should be able to find the problem and fix it yourself mostly and you seemed to go straight to the source of the issue.... nice one... :)

I made quite a few mistakes myself when first making a CFW but now I can simply just get on with it when a new OFW update is pushed by S@ny. I just don't have the time to release mine for people to use then be able to provide the kind of user support that should come with a CFW release, maybe in the future but right now no really free time to do anything PS3 related.

Nice one in finding what was wrong and correcting it..... don't forget to add the patched emu files and emu stage 2s this time when packing the pup this time....:-p And make sure to test ALL game formats properly> PS1, PS2 ISO and classic, PSPISO, PSP mini , PS3 ISO and JB format.
 
Cypher_CG89 said:
The module hashes have been static in cobra for a while now. Only needs changing if there is changes to the modules that cobra dynamically patches are significant enough to effect the hashcalc. As there have been no real significant changes in them the hashes can remain static. Or if you add some kind of new major patch to one of the modules yourself then it may need updating depending on what it is... ( This is my understanding of it as I see it and also after reading a post on it a while back by @bguerville )

This is why I asked if you changed anything else in the stage2, you also confirmed 100% what I found when you showed them screenshots of the hashcalc's you were using in your modules.h cobra source.... but I wasn't just going to give you the solution...

I gave you the bump in the right direction by mentioning the stage2.bin..... releasing a CFW means you should be able to find the problem and fix it yourself mostly and you seemed to go straight to the source of the issue.... nice one... :)

I made quite a few mistakes myself when first making a CFW but now I can simply just get on with it when a new OFW update is pushed by S@ny. I just don't have the time to release mine for people to use then be able to provide the kind of user support that should come with a CFW release, maybe in the future but right now no really free time to do anything PS3 related.

Nice one in finding what was wrong and correcting it..... don't forget to add the patched emu files and emu stage 2s this time when packing the pup this time....:-p And make sure to test ALL game formats properly> PS1, PS2 ISO and classic, PSPISO, PSP mini , PS3 ISO and JB format.
Click to expand...
sb00 said:
Nice! I'll give it another go when you release the new version.
Click to expand...
Thank you guys you just push me to go further :love heart:
 
Last edited:
Louay said:
i have made one :)

but to go from there and do as i have done before (updating the hashes) will lead to same error
Click to expand...
What, if you start with with a good CEX base CFW if will lead to errors? :) That makes no sense. Obviously don't do as you have done before... :)

Why dont you try to make a standard CEX CFW without any errors and release it for testing.
 
@Louay i second that! (when you got time). i look foward to using bgtoolset to rejailbreak my slim but a pup is much easier.
 
fpoker102 said:
Thank you Sir for the cfw but i need all the version of 4.85 cfw by louay Anonymous
Click to expand...
Screenshot_20230625_223655_YouTube.jpg


That is what I gave you man. This is Louay's 4.85 CFW you asked for. He removed the link to the first one as was a much older Cobra 8.01 and had some stuff that didn't work right. You can get the link directly from his YouTube channel but it is the link I posted and screenshot to prove it. So this is what you asked for bud.
 
You must log in or register to reply here.

Similar threads

Back
Top