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).
It is very easy to use (install and use.)
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).
Payload optional and upgradeable.
It is so simple, and requires a PKG (or a backup manager amended) to install the payload after the start of the console.
Choose which is your preferred option! chosen well!