[PS3] NOR/NAND Statistic Beta

  • 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.
Manu_ModzHD

Manu_ModzHD

Member
Jun 1, 2015
59
107
28
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%.




[HIDE]https://mega.co.nz/#!bddVRTCb!xKubpe96gUX8Ue2h28jvBfEaYUpd2Jx8SVwjHxGKFos[/HIDE]




index.php




Credits : Lazor & Manu-_-ModzHD​
 
NotWolfy

NotWolfy

Member
Feb 8, 2015
17
6
13
United Kingdom
Manu_ModzHD said:
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​
Click to expand...
 
D

Dabit

New Member
Apr 4, 2017
2
0
1
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 ???
 
viMax

viMax

Active Poster
Active Member
Aug 11, 2016
313
34
88
Ok

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



​
 
P

pizza_dox_9999

Active Poster
Active Member
Jun 9, 2018
225
26
88
Manu_ModzHD said:
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​
Click to expand...
thanks
 
G

GamerHD27

New Member
May 23, 2019
4
0
1
Manu_ModzHD said:
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​
Click to expand...
gracias
 
Marty83

Marty83

Member
Aug 28, 2017
8
0
61
Manu_ModzHD said:
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​
Click to expand...
:xD::xD::xD::xD::xD::xD:
 
P

polanco1

Member
Jul 19, 2015
1
0
61
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]
 
You must log in or register to reply here.
General chit-chat
Help Users
    Chat Bot: Christo has joined the room.
    Top Bottom