[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

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%.









index.php




Credits : Lazor & Manu-_-ModzHD
 

NotWolfy

Member
Feb 8, 2015
17
6
13
United Kingdom
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
 

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

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



 

pizza_dox_9999

Active Poster
Active Member
Jun 9, 2018
225
26
88
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
 

GamerHD27

New Member
May 23, 2019
4
0
1
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
 

Marty83

Member
Aug 28, 2017
8
0
61
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:
 

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]
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • @ QM|T_JinX:
    if im correct yea
  • @ Cr1ms:
    I join in game, but mod dont work
  • @ QM|T_JinX:
    did you check the update number of the menu and the update number from the game ?
  • @ Cr1ms:
    How?
  • @ QM|T_JinX:
    when you downloaded the menu it should have said on what update
  • @ Cr1ms:
    do you have a mod for the latest tbogt update?
  • @ Cr1ms:
    How check version gta ;?
  • @ QM|T_JinX:
    me nah never modded tbogt so not sure on what update it is
  • @ QM|T_JinX:
    best bet is to google gta tbogt mod menu hen bc i cant seem to find anything i can link to you
  • @ QM|T_JinX:
    or change is to look on Youtube but alot of things wont work so it wont be the first thing you find
  • @ QM|T_JinX:
    things ike this
  • @ QM|T_JinX:
    sorry cant be more of help but i hope you will find something
  • Chat Bot:
    flexovh is our newest member. Welcome!
  • Chat Bot:
    188betctcom is our newest member. Welcome!
  • Chat Bot:
    Cr1ms has joined the room.
  • Chat Bot:
    QM|T_JinX has joined the room.
  • Chat Bot:
    pgarcia is our newest member. Welcome!
  • Chat Bot:
    INVICTOR2000 is our newest member. Welcome!
  • Chat Bot:
    Christo has joined the room.
  • Chat Bot:
    CHEESEST is our newest member. Welcome!
  • Chat Bot:
    Christo has joined the room.
  • Chat Bot:
    evwarno12 is our newest member. Welcome!
  • Chat Bot:
    ay0cam is our newest member. Welcome!
  • Chat Bot:
    ay0cam has left the room.
    Chat Bot: ay0cam has left the room.