Post: [Release] PS3 NOR/NAND Statistic (Beta)
Options
04-18-2013, 08:46 AM
#1
SonyBlack
League Champion
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%.
Keep in mind this is only beta.
Download
You must login or register to view this content.
You must login or register to view this content.
Source
You must login or register to view this content.
The following 5 users say thank you to SonyBlack for this useful post:
04-18-2013, 04:56 PM
#3
Mango_Knife
In my man cave
Originally posted by SONY
You must login or register to view this content.
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%.
Keep in mind this is only beta.
Download
You must login or register to view this content.
You must login or register to view this content.
Source
You must login or register to view this content.
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%.
Keep in mind this is only beta.
Download
You must login or register to view this content.
You must login or register to view this content.
Source
You must login or register to view this content.
What this tool acctualy doing like what it can help me?
04-19-2013, 10:57 PM
#4
Pseudo_Soldier
< ^ > < ^ >
OMFG, I was just wondering if there was a tool that did this and here this comes out! I forgot to label my DEX/CEX backups correctly, now I can check them! :happycry:
04-20-2013, 10:59 AM
#5
NOT_A_CLUE
Gym leader
Originally posted by SONY
You must login or register to view this content.
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%.
Keep in mind this is only beta.
Download
You must login or register to view this content.
You must login or register to view this content.
Source
You must login or register to view this content.
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%.
Keep in mind this is only beta.
Download
You must login or register to view this content.
You must login or register to view this content.
Source
You must login or register to view this content.
sorry for this random question but i hear you're the guy to speak to about cfw n stuff.
i installed PS3ITA installed the loader and tried to sign in and all i get is the error 8002A224
i re-installed rebug to see if i was console banned because everybody says it's a banned console id but it let me sign in straight away,
have you any idea what i could be doing wrong?
i would prefer to use PS3ITA and if you could help i'd be extremely grateful.
04-20-2013, 02:48 PM
#6
SonyBlack
League Champion
Originally posted by CLUE
sorry for this random question but i hear you're the guy to speak to about cfw n stuff.
i installed PS3ITA installed the loader and tried to sign in and all i get is the error 8002A224
i re-installed rebug to see if i was console banned because everybody says it's a banned console id but it let me sign in straight away,
have you any idea what i could be doing wrong?
i would prefer to use PS3ITA and if you could help i'd be extremely grateful.
i installed PS3ITA installed the loader and tried to sign in and all i get is the error 8002A224
i re-installed rebug to see if i was console banned because everybody says it's a banned console id but it let me sign in straight away,
have you any idea what i could be doing wrong?
i would prefer to use PS3ITA and if you could help i'd be extremely grateful.
sorry dude..the only 1 cfw i dont use is ps3ita..really sorry but i cant help you on any quastions about ps3ita..i use all other ones...venix..mirala..sdk..but not ps3ita..
sorry..but i think maybe you dont chance your targetid or np enviroment..
04-20-2013, 03:43 PM
#7
NOT_A_CLUE
Gym leader
Originally posted by SONY
sorry dude..the only 1 cfw i dont use is ps3ita..really sorry but i cant help you on any quastions about ps3ita..i use all other ones...venix..mirala..sdk..but not ps3ita.. sorry..but i think maybe you dont chance your targetid or np enviroment..
sorry..but i think maybe you dont chance your targetid or np enviroment..
sorry mate I should of come back and edited my post riggs fixed it for me I just needed my real consoleid plus 32 0s after it in a .txt on a usb then I patched my psid with psidpatch and I was able to sign in fine.
thanks for replying anyway
04-20-2013, 04:40 PM
#8
Pseudo_Soldier
< ^ > < ^ >
Originally posted by CLUE
sorry mate I should of come back and edited my post riggs fixed it for me I just needed my real consoleid plus 32 0s after it in a .txt on a usb then I patched my psid with psidpatch and I was able to sign in fine.
thanks for replying anyway
thanks for replying anyway
You need to spoof your IDPS to CEX, DEX consoles/firmware cannot connect to CEX servers without spoofing first. Never dealt with the loaders myself but here is how I do it....
1) Download the "Rebug Toolbox v2.01.02" and install it.
2) Open the app, go to the right-most column and scroll to the very last option. Spoof the IDPS target to CEX.
3) Close the app after you have done this and sign in.
Note: You will have to do this everytime before you log in so maybe there is a loader option available.
2) Open the app, go to the right-most column and scroll to the very last option. Spoof the IDPS target to CEX.
3) Close the app after you have done this and sign in.
Note: You will have to do this everytime before you log in so maybe there is a loader option available.
Nevermind, you fixed it yourself!
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
