[Voting] Waninkoko Custom Firmware 3.55 v2

[STRATEGIZER]

On Teknoconsolas, Waninkoko has given the community the option to vote on 2 different version his new v2 CFW. Here's the the option's & I quote..

Having found the bug in CFW (caused by a tool of fail0verflow team), I am finalizing the publication of the v2 of my CFW.


Update: My favorite is the second option, although it may be less stable. The second option is easier to update (and any payload error is easily correctable). But the first option has the pros of being, theoretically, more stable, and be easier (but with the backups that make up the payload manager, the truth is that the second option would be just as easy).


Currently you can perform two types of CFW:

- Type 1:

A payload integrated with CFW (like my previous CFW).

Advantages:
It is very easy to use (install and use.)
"Greater stability?

Inconveniences:
The payload is not updatable, requiring post a new CFW (PKG with a more or less be updated on a temporary basis of style CFW Kmeaw).
The payload is always present and running, with all that that entails.


- Type 2:

A CFW to peek / poke and a few more tools (Kmeaw style).

Advantages:
Total security.
Payload optional and upgradeable.

Inconveniences:
It is so simple, and requires a PKG (or a backup manager amended) to install the payload after the start of the console.
"Reduced stability?


Choose which is your preferred option! chosen well!

So Which do you prefer ?

[mikerock98]

Type 1 with a hermes intergraded payload instead of PL3 which i think is where the very few freezes with waninkoko CFW come from

[TitaniumL]

Agreed. Get rid of PL3 please.

If you or anyone here are a member there please quote us on this. Hopefully he'll try working with hermes.

[STRATEGIZER]

TBH I would like to have Type 1 because of the stability & from using his first CFW, I know that a all in one is the best way forward. Only bad thing is that if there's problems or a new payload come's out for it, We have to wait for him to fix or implement the payload into the v2 CFW (If he would even do that for us )

Im not to sure about Type 2 because isnt that the same as Kmeaw's & Wutang's ? Pointless making a Type 2 because we might as well wait for a new payload to come out & use it on either Kmeaw's & Wutang's.. Poinless having another pointless CFW....

[Omnomnom]

I voted for type 1, purely out of stability. It seems as if plenty of people using the patch package are having constant issues.

[strictlyfocused]

I voted for type 2 since syscall36 can still be implemented this way.

[AlexDC22]

like the rest have said, whats the point of type 2? might as well stay with kmeaw then lol...go wanin, do your thing, and please make it compatible with my 256 nand so i can use your cfw champ

[Chaz36]

I kinda like it already the way it is now, this cfw is so much stabler then kmeaw.

I will go for option 1.

[[C*]]

Just release both.

I voted for type 1, since not having to do the extra step of RAM patching is cool.

[STRATEGIZER]

57 out of 1261 (Signed up members) have only voted... This maybe the best CFW released to date (IMO).

Vote or Die