• Hello Guest! Welcome to ConsoleCrunch, to help support our site check out the premium upgrades HERE! to get exclusive access to our hidden content.
  • Unable to load portions of the website...
    If you use an ad blocker addon, you should disable it because it interferes with several elements of the site and blocks more than just adverts.
  • Read Rules Before Posting Post Virus Scans with every program.

[PS3] NOR/NAND Statistic Beta

Manu_ModzHD

Member
beta1dz9x.jpg


Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.









index.php




Credits : Lazor & Manu-_-ModzHD
 
beta1dz9x.jpg


Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.





***Hidden content cannot be quoted.***[/URL]




index.php




Credits : Lazor & Manu-_-ModzHD
 
i registered and it still wont let me get the link im trying to get the dump stastics checker for my nor dump can u help me ???
 

beta1dz9x.jpg



Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.






***Hidden content cannot be quoted.***





index.php









Credits : Lazor & Manu-_-ModzHD



 
beta1dz9x.jpg


Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.





***Hidden content cannot be quoted.***




index.php




Credits : Lazor & Manu-_-ModzHD
thanks
 
beta1dz9x.jpg


Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.





***Hidden content cannot be quoted.***




index.php




Credits : Lazor & Manu-_-ModzHD
gracias
 
beta1dz9x.jpg


Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.





***Hidden content cannot be quoted.***




index.php




Credits : Lazor & Manu-_-ModzHD
:xD::xD::xD::xD::xD::xD:
 
thanks gracias
gracias
beta1dz9x.jpg


Features:

NOR/NAND statistics
NOR/NAND patching
NOR/NAND byte swapping
NOR/NAND infos
NOR/NAND validation
NOR/NAND extraction
DATECODE check


This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

Always patching 3.55 is recommended to see if the patched statistic is right/green.

ckp_management_ID values have to be equel as well as per_console_nonce.
(should be stated in error.log if not)

There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.


For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.


It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.





***Hidden content cannot be quoted.***




index.php


gracias111

Credits : Lazor & Manu-_-ModzHD
[/QUOTE]
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • Chat Bot:
    QM|T_JinX has joined the room.
  • Chat Bot:
    killa2! is our newest member. Welcome!
  • Chat Bot:
    Christo has joined the room.
  • Chat Bot:
    xperttechy is our newest member. Welcome!
  • Chat Bot:
    burhanpc is our newest member. Welcome!
  • Chat Bot:
    jerpator is our newest member. Welcome!
  • Chat Bot:
    kazuma18 is our newest member. Welcome!
  • Chat Bot:
    kazuma18 has posted a new reply in the thread "Console ID #8660".
  • Chat Bot:
    Blazed420999 is our newest member. Welcome!
  • Chat Bot:
    charlles is our newest member. Welcome!
  • Chat Bot:
    charlles has posted a new reply in the thread "Console ID #8660".
  • Chat Bot:
    CFWMODDINGCEX is our newest member. Welcome!
  • Chat Bot:
    Yote1234 is our newest member. Welcome!
  • Chat Bot:
    QM|T_JinX has joined the room.
  • Chat Bot:
    Christo has joined the room.
  • Chat Bot:
    Mariglen is our newest member. Welcome!
  • Chat Bot:
    QM|T_JinX has joined the room.
  • Chat Bot:
    WxRRioR_ is our newest member. Welcome!
  • Chat Bot:
    QM|T_JinX has joined the room.
  • Chat Bot:
    QM|T_JinX has joined the room.
  • Chat Bot:
    Pinauz is our newest member. Welcome!
  • Chat Bot:
    派森寒树 is our newest member. Welcome!
  • Chat Bot:
    派森寒树 has left the room.
  • Chat Bot:
    ahagai is our newest member. Welcome!
  • Chat Bot:
    QM|T_JinX has joined the room.
      Chat Bot: QM|T_JinX has joined the room.
      Back
      Top