[R3QU13M]

Just another new release fighting game that's patched in my speculation for example Tekken Tag Tournament 2. You can forget about all the hype concerning any 4.xx custom firmware unless you're like **** it I can't wait. xD

[capostef]

Yes no need, but multiman is written with this feature. so it will ask you

[TheFrenchy]

Originally Posted by joaorikard Yes, but MM isn't configured to accept fw>3.55, so it askes to change it. If you spoof your cfw, it asks you to change the sfo, correct? So why wouldn't be the same to a new MM-unsuported-CFW? Sent from my iPhone using Tapatalk

if you got 4.21 cfw you got the same possibilities as 3.55 cfw except you can run backups to 4.21 without patching files from lower firmwares.

so :

- IF DoA5 is a 4.21 game or lower no need to patch file.
- IF it's a higher game of 4.21 just patch it for the current cfw you got : "4.21cfw" (of course if there is a way to patch the eboot and make a fix)


so tell me why patch a file to 3.55 if you got 4.21 cfw with the same possibilities ?!
No sence and no reason this is the best proof of a fake cfw4.21

[Amic3r]

Originally Posted by capostef Yes no need, but multiman is written with this feature. so it will ask you

I am sorry are you a silly pants? MULTIMAN asks for it, it's hard coded. You could pull out 31.42 CFW out your arse and it would still ask for it if you wouldn't release new MMan.

[joaorikard]

you can change the sfo to 1.00 if you want to... what matters are the bin/sprx files. MM is configured BY DEFAULT to look at the sfo and IF SFO => 3.60, it asks to change.
It has nothing to do with CFW, OFW, DEX, whatever. It's the app.

If you ask me why did he choose "YES", instead of "NO", in MM - that I cannot answer. Technically it should work either way, if 4.21CFW.

[davidpstone]

they patched DOA5 to 3.55. No fw 3.56+ would ever ask to patch a param to 3.55, read what the title of thread says: 4.21 CFW or DOA 5 Patched for 3.55 CFW

[xxshizoxx]

This is my opinion

I Think this is Fake ! Why ?
When viedeo beginn is the gGock set on 05.44 when he Launching the Multiman.
And when he play the game DOA5 is the Glock on 05.42 !!! Very Strange
And the Multiman say Change the Parm.sfo on 3.55 and when the Team have Realy the new Keys and e way to Jailbreak 4.21 why is the Viedeo so shortly ?

But this is my opinion

[poorguy]

Originally Posted by TheFrenchy if you got 4.21 cfw you got the same possibilities as 3.55 cfw except you can run backups to 4.21 without patching files from lower firmwares. so : - IF DoA5 is a 4.21 game or lower no need to patch file. - IF it's a higher game of 4.21 just patch it for the current cfw you got : "4.21cfw" (of course if there is a way to patch the eboot and make a fix) so tell me why patch a file to 3.55 if you got 4.21 cfw with the same possibilities ?! No sence and no reason this is the best proof of a fake cfw4.21

Mate, calm down a little.. I get what you are implying. However, let me try and explain what the others are trying to say..

Multiman has been coded to bypass the use of spoofers so that it doesn't confuse and "not patch" a PARAM.SFO to 3.55. Therefore, no matter the FW, unless it has been recoded to modify this step it will always change a PARAM.SFO to 3.55 when being played via "a backup".. That's why all the speculation.

[naddel81]

everything in the video is LEGIT except for the time changing thing. this screams FAKE as loud as a youtube video can. so.... very disappointing.

[TheEvolution_PT]

Originally Posted by davidpstone they patched DOA5 to 3.55. No fw 3.56+ would ever ask to patch a param to 3.55, read what the title of thread says: 4.21 CFW or DOA 5 Patched for 3.55 CFW

Dude the people already said that multiman could ask for change the param sfo, cuz multiman has made only for 3.55 and if this cfw 4.21 is true we don't know if the program will ask for change or not it all depends the way that this program as made, im not deank to answer this question so if anyone have any questions regarding this subject just go to the TbCrunch and ask deank cuz is home is there!