PS3 Help with PS3 Fat

[lugh22]

Hello everyone,

I have a PS3 Fat, model CECHE01, that still have FW 2.35, with what looks like a problem in the NAND memory, or the controller, every time I change some setting I get a RSOD, or I can change but after a reboot returns to the factory default, also unable to create/edit users or install Linux.

I tried to update to several OFW's and CFW's, but fails everytime at 3% with error 8002F14E, after some research I found a Russian forum that pointed to the NAND controller probably being faulty.

So basically I am stuck in OFW 2.35 and every software solution did not work, is there any other option to try being at an OFW this low?

 

[lugh22]

Hello everyone,

After several days researching for an answer I think I found a way to solve my problem, or at least know what's wrong with my PS3, but I still have some questions.

First is about the Factory Service Mode, since my PS3 has the 2.35 OFW, can I safely enter/exit this mode with this version?

 

[Blane]

@lugh22 You can try the following mate:

- Removing the internal battery and then running the update (If you want to change the battery I can send you a spare).
https://www.ifixit.com/Answers/View/54848/Any+info+on+PS3+error+code+8002F14E#:~:text=Error 8002F14E [General Hardware Issue] Problems: It could,Update Flashing of your PS3 if it's looping.

This is the link to locating and changing the battery

https://www.sosav.com/guides/game-consoles/sony/sony-home/playstation-3/battery/#:~:text= Required spare parts 1 Step 1.,console. Then grasp it in order... More

- Maybe your BD drive is not connected properly or the ribbon is damaged. (I have a spare BD drive also).
- Did you try to update your PS3 from recovery or XMB?
- If you ran the update from XMB did you format your HDD afterwards by any chance?
- Can you remove and reconnect your HDD, possible that it's not making full contact.
- In all probability you can't enter FSM without CFW.

"To enter, it is needed setting Offset 0x48C07 on the System Controller EEPROM to value: 0x00 or 0xFE,
at least something beside 0xFF (inactive). This can usually be done via a special hardware logic dongle, or the Factory Service Mode Tool."
FSM mode tool I think is a pkg file that you need to install on a CFW PS3 although rebug CFW generally comes with the tool pre-installed.

If you have a PSP laying around somewhere with CFW on it, you can download FSM homebrew tool. (Think it is called PS3Jig)
It can probably let you enter FSM, but i'm not sure if it actually works, just saw video's of people doing it on YT.

 

[lugh22]

@lugh22 You can try the following mate:

- Removing the internal battery and then running the update (If you want to change the battery I can send you a spare).
https://www.ifixit.com/Answers/View/54848/Any+info+on+PS3+error+code+8002F14E#:~:text=Error 8002F14E [General Hardware Issue] Problems: It could,Update Flashing of your PS3 if it's looping.

This is the link to locating and changing the battery

https://www.sosav.com/guides/game-consoles/sony/sony-home/playstation-3/battery/#:~:text= Required spare parts 1 Step 1.,console. Then grasp it in order... More

- Maybe your BD drive is not connected properly or the tape is damaged. (I have a spare BD drive also).
- Did you try to update your PS3 from recovery or XMB?
- If you ran the update from XMB did you format your HDD afterwards by any chance?
- Can you remove and reconnect your HDD, possible that it's not making full contact.
- In all probability you can't enter FSM without CFW.

"To enter, it is needed setting Offset 0x48C07 on the System Controller EEPROM to value: 0x00 or 0xFE,
at least something beside 0xFF (inactive). This can usually be done via a special hardware logic dongle, or the Factory Service Mode Tool."
FSM mode tool I think is a pkg file that you need to install on a CFW PS3 although rebug CFW generally comes with the tool pre-installed.

If you have a PSP laying around somewhere with CFW on it, you can download FSM homebrew tool. (Think it is called PS3Jig)
It can probably let you enter FSM, but i'm not sure if it actually works, just saw video's of people doing it on YT.

Thanks for the reply Blane,

Already tried to removed the internal battery and still got the same error.
The BD drive is fine, I can play game and watch movies with no problems, also already checked all the cables.
I tried the update from XMB, since I am stuck with OFW 2.35 there is no Recovery Mode, only after OFW 2.50, if I am not wrong.
Also tried with the original 80GB HDD and a 250GB HDD, both still failed.
And finally tried to enter FSM, I have a PSP-3000 with CFW, spent 1 hour trying with no success, the PSP showed the challenge was sent but every time the PS3 booted normally.

 

[Blane]

One more thing, have you also tried to update your PS3 from the update on a BD game disc?

Thanks for the reply Blane,

Already tried to removed the internal battery and still got the same error.
The BD drive is fine, I can play game and watch movies with no problems, also already checked all the cables.
I tried the update from XMB, since I am stuck with OFW 2.35 there is no Recovery Mode, only after OFW 2.50, if I am not wrong.
Also tried with the original 80GB HDD and a 250GB HDD, both still failed.
And finally tried to enter FSM, I have a PSP-3000 with CFW, spent 1 hour trying with no success, the PSP showed the challenge was sent but every time the PS3 booted normally.

@lugh22 No problem. Wow this is a bit of a difficult one. I don't actually know how else you can get the PS3 to update.

Hmm maybe this one can be given to the devs.

 

[Blane]

Although these members have a great knowledge and understanding and they are quite reputable.
@Joonie @pinky @aldostools @bguerville

 

[lugh22]

One more thing, have you also tried to update your PS3 from the update on a BD game disc?


@lugh22 No problem. Wow this is a bit of a difficult one. I don't actually know how else you can get the PS3 to update.

Hmm maybe this one can be given to the devs.

I don't think I tried updating from disc, but I believe the result will be the same.

The main problem is that my PS3 doesn't save anything I change, system setting, video settings, network settings and even tried to register my PSP and other DS3 with no success.

When I try to change some setting it gives me a RSOD, sometimes a BSOD, or doesn't save at all.

Quite sure is a HW problem, probably with the NAND's or the controller, I am trying to find someplace in my town that can at least tell me if it can be fixed or not.

I was going to try myself, but to get all the tools needed is very expensive, at least where I live.

 

[sandungas]

I don't think I tried updating from disc, but I believe the result will be the same.

The main problem is that my PS3 doesn't save anything I change, system setting, video settings, network settings and even tried to register my PSP and other DS3 with no success.

When I try to change some setting it gives me a RSOD, sometimes a BSOD, or doesn't save at all.

Quite sure is a HW problem, probably with the NAND's or the controller, I am trying to find someplace in my town that can at least tell me if it can be fixed or not.

I was going to try myself, but to get all the tools needed is very expensive, at least where I live.

BSOD and the inhability to save setting changes is related with problems in xregistry.sys (located in dev_flash2), RSOD is mostly related with other flash area named VTRM that deals with encryption tasks

Atfter reading your posts this clearly is pointing to damaged NAND chip/s, the straightforward solution that most technicians would try is to replace them. For someone with the proper equipment it doesnt takes much time and is relativelly easy

But... the most important thing at this point is to make some flash dumps, scan them with pyps3checker or/and other dump checker tools
Also... incase you had old flash dumps made years ago, dont delete them !, because most probably the oldest dumps are the best for forensic purposes (they contains the data before it was damaged)

Actually... you should "split" the dumps (either with a hexeditor or a tool) to extract the areas that are really critical (unique per-console, or per-user). The other flash contents doesnt matters

 

[lugh22]

BSOD and the inhability to save setting changes is related with problems in xregistry.sys (located in dev_flash2), RSOD is mostly related with other flash area named VTRM that deals with encryption tasks

Atfter reading your posts this clearly is pointing to damaged NAND chip/s, the straightforward solution that most technicians would try is to replace them. For someone with the proper equipment it doesnt takes much time and is relativelly easy

But... the most important thing at this point is to make some flash dumps, scan them with pyps3checker or/and other dump checker tools
Also... incase you had old flash dumps made years ago, dont delete them !, because most probably the oldest dumps are the best for forensic purposes (they contains the data before it was damaged)

Actually... you should "split" the dumps (either with a hexeditor or a tool) to extract the areas that are really critical (unique per-console, or per-user). The other flash contents doesnt matters

Thanks for the info sandungas.
I tried to find a place that could fix this PS3 but had no luck, the only place willing to try something went straight to reballing lol.
So, I will try to fix myself, I don't have any NAND backup's, just to give more information, I bought this PS3 last month, the previous owner said he bought around 2008, played three or four times than forgot about it, if it's true, which I think it is because I opened the console to clean it and was almost perfect inside, than I believe this problem could be a corrupted NAND, and hopefully not a hardware problem, is that possible?
Also, I noticed the power LED was flickering, now it's off completely, sometimes it lights up than off again, and the network doesn't work anymore, bluethoot is ok, was working fine when I got it, could this be related?
Bad power supply?

 

[sandungas]

Thanks for the info sandungas.
I tried to find a place that could fix this PS3 but had no luck, the only place willing to try something went straight to reballing lol.
So, I will try to fix myself, I don't have any NAND backup's, just to give more information, I bought this PS3 last month, the previous owner said he bought around 2008, played three or four times than forgot about it, if it's true, which I think it is because I opened the console to clean it and was almost perfect inside, than I believe this problem could be a corrupted NAND, and hopefully not a hardware problem, is that possible?
Also, I noticed the power LED was flickering, now it's off completely, sometimes it lights up than off again, and the network doesn't work anymore, bluethoot is ok, was working fine when I got it, could this be related?
Bad power supply?

The NAND corruption uses to be related with bad blocks (phisically damaged). Is not posible to repair them unless we "remap" them to a different block, but im not sure how tricky is to achieve this in a PS3 NAND
I remember there was an app made by judges (the same person that wrote norway and nandway software for teensy flashers) that was able to remap bad blocks, the first versions was private but at some point he released the "fully unlocked" version of the app
I cant help much with that, i dont remember much more details about that process and i dont have experience with it

To me the problems you reported seems to indicate bad blocks in 2 different areas of the NAND, as can be seen in this table
You seem to have problems in dev_flash2 (this causes the BSOD). But also in VTRM (this causes the RSOD)
So it seems you have (at least) 2 bad blocks... or 2 different corrupted areas anyway (as said, im not sure if are bad blocks)

By now the best you could do is some NAND dumps and check them with pyps3checker and see if it detects some problems

 

[lugh22]

Hello everyone,

Took me some time, but I got almost everything needed to make some NAND backups, but I still have some questions.

I will use a teensy 2.0++ with the 360 nand clip, I was reading the wiki about the teensy, and it said that the teensy, with the voltage regulator, cannot supply enough current to power the nand and other components, but looking at the Samsung K9F1G08U0A-PIB0 NAND datasheet, it consumes a maximum of 30 mA, I need to power anything else than the NAND to make a backup, or it is referring to something else?

 

[Blane]

Hello everyone,

Took me some time, but I got almost everything needed to make some NAND backups, but I still have some questions.

I will use a teensy 2.0++ with the 360 nand clip, I was reading the wiki about the teensy, and it said that the teensy, with the voltage regulator, cannot supply enough current to power the nand and other components, but looking at the Samsung K9F1G08U0A-PIB0 NAND datasheet, it consumes a maximum of 30 mA, I need to power anything else than the NAND to make a backup, or it is referring to something else?

Hey dude, check out this https://www.psx-place.com/threads/chapter-ii-hardware-needed-for-ps3-downgrade.336/

And this https://www.psx-place.com/threads/chapter-iii-nor-downgrade-teensy-flasher.838/

@3absiso (Please give us some more advice here)

 

[lugh22]

Thanks for the info Blane.

So, the power supply main purpose is to power the NAND, but looking at the teensy 2.0++ power consumption, running at 8MHz with 3.3V the max current is around 19.7 mA, plus 0.2 mA for the MCP1825 itself and the 30 mA for the NAND gives around 50 mA, which is far lower than the 500 mA MCP1825 max output current.
And using a USB 3.0, with max current at 900 mA, I don't see any problem using the teensy to power the NAND, unless it's needed to power other components.
I'm no expert in electronics so if I am saying something wrong please correct me.

 

[lugh22]

Hello everyone,

Finally I got some dumps from this board, here are the results.

Spoiler

PyPS3checker v0.10.x. Check log.

Checked file : C:\Users\Acer\OneDrive\Documentos\PS3\DUMPS PS3\CECHE01MG\DUMP01\nand.bin


******* Getting flash type *******
Flash type : NAND (full dump, 256MB)


******* Getting SKU identification datas *******
idps =
metldr0 = 0xE8E0
metldr1 = 0x0E8A
bootldr0 = 0x2EF4
bootldr1 = 0x2EF4
bootldrsize = 0x2EF80

Matching SKU : OK
CECHE01 MG (COK-002)
Minimum version 1.00


******* Getting SDK versions *******
ROS0 : 487.000
ROS1 : 235.000


******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : DANGER!
Any bytes from offset 0x0 to offset 0x2EF80 should be less than 0.5%.
0xFF is 50.17%
001.05 bootldr (Top) 0xFF Filled Area : OK


******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK


******* Checking flash_region_table *******
003.01 Flash Region Table Header : DANGER!
At offset : 0x40200
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 01 00 00 00 09 00 00 00 00 00 EB FE 00

003.02 asecure_loader Offset - Length : DANGER!
At offset : 0x40210
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 00 06 00 00 00 00 00 00 04 00 00

003.03 asecure_loader Name : DANGER!
At offset : 0x40220
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 61 73 65 63 75 72 65 5F 6C 6F 61 64 65 72 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.04 eEID Offset - Length : DANGER!
At offset : 0x40240
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 04 06 00 00 00 00 00 00 01 00 00

003.05 eEID Name : DANGER!
At offset : 0x40250
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 65 45 49 44 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.06 cISD Offset - Length : DANGER!
At offset : 0x40270
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 06 00 00 00 00 00 00 00 08 00

003.07 cISD Name : DANGER!
At offset : 0x40280
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 49 53 44 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.08 cCSD Offset - Length : DANGER!
At offset : 0x402A0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 0E 00 00 00 00 00 00 00 08 00

003.09 cCSD Name : DANGER!
At offset : 0x402B0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 43 53 44 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.10 trvk_prg Offset - Length : DANGER!
At offset : 0x402D0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 16 00 00 00 00 00 00 00 20 00

003.11 trvk_prg Name : DANGER!
At offset : 0x402E0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 74 72 76 6B 5F 70 72 67 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.12 trvk_pkg Offset - Length : DANGER!
At offset : 0x40300
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 36 00 00 00 00 00 00 00 20 00

003.13 trvk_pkg Name : DANGER!
At offset : 0x40310
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 74 72 76 6B 5F 70 6B 67 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.14 creserved_0 Offset - Length : DANGER!
At offset : 0x40330
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 56 00 00 00 00 00 00 02 A8 00

003.15 creserved_0 Name : DANGER!
At offset : 0x40340
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 72 65 73 65 72 76 65 64 5F 30 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.16 ros Offset - Length : DANGER!
At offset : 0x40360
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 07 FE 00 00 00 00 00 00 E0 00 00

003.17 ros Name : DANGER!
At offset : 0x40370
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 72 6F 73 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.18 cvtrm Offset - Length : DANGER!
At offset : 0x40390
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 E7 FE 00 00 00 00 00 00 04 00 00

003.19 cvtrm Name : DANGER!
At offset : 0x403A0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 76 74 72 6D 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.20 Flash Region Table 0x00 Filled Area : WARNING!
All bytes from offset 0x403B0 to offset 0x40800 should be 0x00.
Byte at offset 0x403B0 has value : 0xFF
Subsequent bytes in the range may be wrong as well.



******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : DANGER!
Any bytes from offset 0x40840 to offset 0x4F120 should be less than 0.52%.
0xFF is 50.01%
004.08 asecure_loader 0x00 Filled Area : WARNING!
All bytes from offset 0x4F120 to offset 0x6F000 should be 0x00.
Byte at offset 0x4F200 has value : 0xFF
Subsequent bytes in the range may be wrong as well.



******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : DANGER!
At offset : 0x81370
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 80 06 90 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

005.12 EID3 Static0 : DANGER!
At offset : 0x81AA0
Actual data :
> FF FF FF FF
Expected data :
> 00 00 00 01

005.13 EID3 Static1 : DANGER!
At offset : 0x81AA8
Actual data :
> FF FF FF FF
Expected data :
> 00 00 00 00

005.14 EID3 Static2 : DANGER!
At offset : 0x81AB0
Actual data :
> FF FF FF FF
Expected data :
> 00 01 00 D0

005.15 EID5 IDPS0 : DANGER!
At offset : 0x81BD0
Actual data :
> FF FF FF FF FF FF
Expected data (one of the list):
> 00 00 00 01 00 82
> 00 00 00 01 00 83
> 00 00 00 01 00 84
> 00 00 00 01 00 85
> 00 00 00 01 00 86
> 00 00 00 01 00 87
> 00 00 00 01 00 88
> 00 00 00 01 00 89
> 00 00 00 01 00 8A
> 00 00 00 01 00 8B
> 00 00 00 01 00 8C
> 00 00 00 01 00 8E
> 00 00 00 01 00 8F

005.16 EID5 IDPS1 : DANGER!
At offset : 0x81BD6
Actual data :
> FF FF
Expected data (one of the list):
> 00 01
> 00 02
> 00 03
> 00 04
> 00 05
> 00 06
> 00 07
> 00 08
> 00 09
> 00 0A
> 00 0B
> 00 0C
> 00 0D
> 00 0E
> 00 0F
> 00 10
> 00 11
> 00 12
> 00 13
> 00 14

005.17 EID5 Static : DANGER!
At offset : 0x81BE0
Actual data :
> FF FF FF FF
Expected data :
> 00 12 07 30

005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : DANGER!
Any bytes from offset 0x80880 to offset 0x81370 should be less than 1.2%.
0xFF is 49.82%
005.20 eEID Statistics1 : DANGER!
Any bytes from offset 0x81390 to offset 0x825D0 should be less than 1.2%.
0xFF is 46.47%


******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : DANGER!
At offset : 0x90A60
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data (one of the list):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 1F FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 07 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 3F FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00

006.15 cISD 0xFF Filled Area : OK


******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK


******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : WARNING!
Size = 0x2C0
MD5 = 112528EAAC9E58C6DB66B4604F8597DC
Version = (unknown)

008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : WARNING!
Size = 0x2C0
MD5 = 7FC609781B70DFB88203A3B05FB1700A
Version = (unknown)

008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : WARNING!
At offset : 0x94820
Actual data :
> FF FF FF FF
Expected data :
> 53 43 45 00



******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK


******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : WARNING!
At offset : 0xC0020
Actual data :
> 00 00 00 03 00 00 00 09 00 00 00 00 00 4B E5 78
Expected data :
> 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0

009.02 ROS0 Hash : WARNING!
Size = 0x6FFFE0
MD5 = F51BF5B961BBFEC20C3DD3362FE8908C
Version = (unknown)

009.03 ROS1 Header : OK
009.04 ROS1 Hash : WARNING!
Size = 0x6FFFE0
MD5 = B74B94D2CD2CAC7C52E5C6C0D6D3E053
Version = (unknown)



******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : WARNING!
All bytes from offset 0xEFF000 to offset 0xF00000 should be 0x00.
Byte at offset 0xEFF200 has value : 0xFF
Subsequent bytes in the range may be wrong as well.



******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : WARNING!
At offset : 0xE780200
Actual data :
> A6 E2 BF BA BD B2 F4 BC BC A5 EB A1 E8 F3 A8 BD
E7 B5 A6 E2 E0 A9 A3 F2 E3 BD FE E4 F5 A8 F8 A7
F8 AC BD BC A4 F6 FC EF B6 AA FB A8 EE FD EE AA
EF B5 BB A0 E7 EC B4 F2 F4 BE A3 E0 F0 B9 F6 AB
A7 E3 F5 BE AA A5 EE E8 FB AC B0 F1 F5 A5 A8 B4
Expected data :
> 00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 03 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF
00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF

011.04 cell_ext_os_area 0xFF Filled Area 1 : WARNING!
All bytes from offset 0xE780250 to offset 0xE780400 should be 0xFF.
Byte at offset 0xE780250 has value : 0xFD
Subsequent bytes in the range may be wrong as well.



******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : DANGER!
Any bytes from offset 0xF000000 to offset 0xF02EF80 should be less than 0.5%.
0xA0 is 0.98%
0xA1 is 1.00%
0xA2 is 0.94%
0xA3 is 0.96%
0xA4 is 0.97%
0xA5 is 0.96%
0xA6 is 0.96%
0xA7 is 0.98%
0xA8 is 0.98%
0xA9 is 0.96%
0xAA is 0.95%
0xAB is 0.99%
0xAC is 0.99%
0xAD is 0.92%
0xAE is 0.96%
0xAF is 1.00%
0xB0 is 0.97%
0xB1 is 0.96%
0xB2 is 1.01%
0xB3 is 1.02%
0xB4 is 0.94%
0xB5 is 1.01%
0xB6 is 0.96%
0xB7 is 0.97%
0xB8 is 0.95%
0xB9 is 0.93%
0xBA is 0.94%
0xBB is 0.94%
0xBC is 0.95%
0xBD is 0.98%
0xBE is 0.93%
0xBF is 0.96%
0xE0 is 0.96%
0xE1 is 0.98%
0xE2 is 0.96%
0xE3 is 0.98%
0xE4 is 1.00%
0xE5 is 0.97%
0xE6 is 0.99%
0xE7 is 0.97%
0xE8 is 0.94%
0xE9 is 0.99%
0xEA is 0.99%
0xEB is 0.94%
0xEC is 0.98%
0xED is 0.99%
0xEE is 0.99%
0xEF is 0.99%
0xF0 is 1.03%
0xF1 is 0.99%
0xF2 is 1.01%
0xF3 is 0.99%
0xF4 is 0.99%
0xF5 is 1.01%
0xF6 is 0.96%
0xF7 is 0.93%
0xF8 is 1.01%
0xF9 is 0.97%
0xFA is 0.97%
0xFB is 0.98%
0xFC is 1.00%
0xFD is 1.02%
0xFE is 0.98%
0xFF is 1.01%
012.05 bootldr 0xFF Filled Area : DANGER!
All bytes from offset 0xF02EF80 to offset 0xF040000 should be 0xFF.
Byte at offset 0xF02EF80 has value : 0xFE
Subsequent bytes in the range may be wrong as well.



******* Checking datamatches *******
bootldr size : OK
per console nonce : DANGER!
Following datas should be the same :
bootldr0 at offset 0x14 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
bootldr1 at offset 0xF000014 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
metldr at offset 0x40854 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
eid0 at offset 0x80884 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
eid3 at offset 0x81AB4 length 0xC
> FF FF FF FF FF FF FF FF FF FF FF FF
eid5 at offset 0x81BE4 length 0xC
> FF FF FF FF FF FF FF FF FF FF FF FF

bootldr : DANGER!
Following datas should be the same :
bootldr Top at offset 0x0 length 0x40000
(too long to dilplay)
bootldr Bottom at offset 0xF000000 length 0x40000
(too long to dilplay)

metldr size : OK
vtrm header datas : OK
vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEF94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEFE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)



******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : DANGER!
Following data expected at offset 0x40220 :
> 61 73 65 63 75 72 65 5F 6C 6F 61 64 65 72 00 00
No matching data found!

eEID Repetition : DANGER!
Following data expected at offset 0x40250 :
> 65 45 49 44 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

cISD Repetition : DANGER!
Following data expected at offset 0x40280 :
> 63 49 53 44 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

cCSD Repetition : DANGER!
Following data expected at offset 0x402B0 :
> 63 43 53 44 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

trvk_prg Repetition : DANGER!
Following data expected at offset 0x402E0 :
> 74 72 76 6B 5F 70 72 67 00 00 00 00 00 00 00 00
No matching data found!

trvk_pkg Repetition : DANGER!
Following data expected at offset 0x40310 :
> 74 72 76 6B 5F 70 6B 67 00 00 00 00 00 00 00 00
No matching data found!

ros Repetition : DANGER!
Following data expected at offset 0x40370 :
> 72 6F 73 00 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

cvtrm Repetition : DANGER!
Following data expected at offset 0x403A0 :
> 63 76 74 72 6D 00 00 00 00 00 00 00 00 00 00 00
No matching data found!



******* Additional information *******
MAC address :
CID :
eCID :
board_id (part of console S/N) :
kiban_id (board barcode) :



******* Checks completed *******

Total number of checks = 131
Number of dangers = 44
Number of warnings = 11

Following check(s) returned a DANGER!
001.04 bootldr Statistics (Top)
003.01 Flash Region Table Header
003.02 asecure_loader Offset - Length
003.03 asecure_loader Name
003.04 eEID Offset - Length
003.05 eEID Name
003.06 cISD Offset - Length
003.07 cISD Name
003.08 cCSD Offset - Length
003.09 cCSD Name
003.10 trvk_prg Offset - Length
003.11 trvk_prg Name
003.12 trvk_pkg Offset - Length
003.13 trvk_pkg Name
003.14 creserved_0 Offset - Length
003.15 creserved_0 Name
003.16 ros Offset - Length
003.17 ros Name
003.18 cvtrm Offset - Length
003.19 cvtrm Name
004.07 metldr Statistics
005.11 EID2 BlockSize/Padding
005.12 EID3 Static0
005.13 EID3 Static1
005.14 EID3 Static2
005.15 EID5 IDPS0
005.16 EID5 IDPS1
005.17 EID5 Static
005.19 eEID Statistics0
005.20 eEID Statistics1
006.14 cISD2
012.04 bootldr Statistics (Bottom)
012.05 bootldr 0xFF Filled Area
datamatches : per console nonce
datamatches : bootldr
datamatches : vtrm
repcheck : asecure_loader Repetition
repcheck : eEID Repetition
repcheck : cISD Repetition
repcheck : cCSD Repetition
repcheck : trvk_prg Repetition
repcheck : trvk_pkg Repetition
repcheck : ros Repetition
repcheck : cvtrm Repetition

Following check(s) returned a WARNING!
003.20 Flash Region Table 0x00 Filled Area
004.08 asecure_loader 0x00 Filled Area
008.02 trvk_prg0 Hash
008.04 trvk_prg1 Hash
008.07 trvk_pkg1 SCE
009.01 ROS0 Header
009.02 ROS0 Hash
009.04 ROS1 Hash
010.07 cvtrm 0x00 Filled Area
011.03 cell_ext_os_area Break Section
011.04 cell_ext_os_area 0xFF Filled Area 1

All checks done in 3.25 seconds.

Lots of warnings and error, I am doing other dumps to make sure I got valid dumps.
Now, can I restore this NAND with this errors?
And how can I restore this NAND?

 

[bguerville]

Hello everyone,

Finally I got some dumps from this board, here are the results.

Spoiler

PyPS3checker v0.10.x. Check log.

Checked file : C:\Users\Acer\OneDrive\Documentos\PS3\DUMPS PS3\CECHE01MG\DUMP01\nand.bin


******* Getting flash type *******
Flash type : NAND (full dump, 256MB)


******* Getting SKU identification datas *******
idps =
metldr0 = 0xE8E0
metldr1 = 0x0E8A
bootldr0 = 0x2EF4
bootldr1 = 0x2EF4
bootldrsize = 0x2EF80

Matching SKU : OK
CECHE01 MG (COK-002)
Minimum version 1.00


******* Getting SDK versions *******
ROS0 : 487.000
ROS1 : 235.000


******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : DANGER!
Any bytes from offset 0x0 to offset 0x2EF80 should be less than 0.5%.
0xFF is 50.17%
001.05 bootldr (Top) 0xFF Filled Area : OK


******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK


******* Checking flash_region_table *******
003.01 Flash Region Table Header : DANGER!
At offset : 0x40200
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 01 00 00 00 09 00 00 00 00 00 EB FE 00

003.02 asecure_loader Offset - Length : DANGER!
At offset : 0x40210
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 00 06 00 00 00 00 00 00 04 00 00

003.03 asecure_loader Name : DANGER!
At offset : 0x40220
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 61 73 65 63 75 72 65 5F 6C 6F 61 64 65 72 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.04 eEID Offset - Length : DANGER!
At offset : 0x40240
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 04 06 00 00 00 00 00 00 01 00 00

003.05 eEID Name : DANGER!
At offset : 0x40250
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 65 45 49 44 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.06 cISD Offset - Length : DANGER!
At offset : 0x40270
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 06 00 00 00 00 00 00 00 08 00

003.07 cISD Name : DANGER!
At offset : 0x40280
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 49 53 44 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.08 cCSD Offset - Length : DANGER!
At offset : 0x402A0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 0E 00 00 00 00 00 00 00 08 00

003.09 cCSD Name : DANGER!
At offset : 0x402B0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 43 53 44 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.10 trvk_prg Offset - Length : DANGER!
At offset : 0x402D0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 16 00 00 00 00 00 00 00 20 00

003.11 trvk_prg Name : DANGER!
At offset : 0x402E0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 74 72 76 6B 5F 70 72 67 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.12 trvk_pkg Offset - Length : DANGER!
At offset : 0x40300
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 36 00 00 00 00 00 00 00 20 00

003.13 trvk_pkg Name : DANGER!
At offset : 0x40310
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 74 72 76 6B 5F 70 6B 67 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.14 creserved_0 Offset - Length : DANGER!
At offset : 0x40330
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 05 56 00 00 00 00 00 00 02 A8 00

003.15 creserved_0 Name : DANGER!
At offset : 0x40340
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 72 65 73 65 72 76 65 64 5F 30 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.16 ros Offset - Length : DANGER!
At offset : 0x40360
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 07 FE 00 00 00 00 00 00 E0 00 00

003.17 ros Name : DANGER!
At offset : 0x40370
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 72 6F 73 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.18 cvtrm Offset - Length : DANGER!
At offset : 0x40390
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 00 00 00 00 E7 FE 00 00 00 00 00 00 04 00 00

003.19 cvtrm Name : DANGER!
At offset : 0x403A0
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 63 76 74 72 6D 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

003.20 Flash Region Table 0x00 Filled Area : WARNING!
All bytes from offset 0x403B0 to offset 0x40800 should be 0x00.
Byte at offset 0x403B0 has value : 0xFF
Subsequent bytes in the range may be wrong as well.



******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : DANGER!
Any bytes from offset 0x40840 to offset 0x4F120 should be less than 0.52%.
0xFF is 50.01%
004.08 asecure_loader 0x00 Filled Area : WARNING!
All bytes from offset 0x4F120 to offset 0x6F000 should be 0x00.
Byte at offset 0x4F200 has value : 0xFF
Subsequent bytes in the range may be wrong as well.



******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : DANGER!
At offset : 0x81370
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data :
> 00 80 06 90 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

005.12 EID3 Static0 : DANGER!
At offset : 0x81AA0
Actual data :
> FF FF FF FF
Expected data :
> 00 00 00 01

005.13 EID3 Static1 : DANGER!
At offset : 0x81AA8
Actual data :
> FF FF FF FF
Expected data :
> 00 00 00 00

005.14 EID3 Static2 : DANGER!
At offset : 0x81AB0
Actual data :
> FF FF FF FF
Expected data :
> 00 01 00 D0

005.15 EID5 IDPS0 : DANGER!
At offset : 0x81BD0
Actual data :
> FF FF FF FF FF FF
Expected data (one of the list):
> 00 00 00 01 00 82
> 00 00 00 01 00 83
> 00 00 00 01 00 84
> 00 00 00 01 00 85
> 00 00 00 01 00 86
> 00 00 00 01 00 87
> 00 00 00 01 00 88
> 00 00 00 01 00 89
> 00 00 00 01 00 8A
> 00 00 00 01 00 8B
> 00 00 00 01 00 8C
> 00 00 00 01 00 8E
> 00 00 00 01 00 8F

005.16 EID5 IDPS1 : DANGER!
At offset : 0x81BD6
Actual data :
> FF FF
Expected data (one of the list):
> 00 01
> 00 02
> 00 03
> 00 04
> 00 05
> 00 06
> 00 07
> 00 08
> 00 09
> 00 0A
> 00 0B
> 00 0C
> 00 0D
> 00 0E
> 00 0F
> 00 10
> 00 11
> 00 12
> 00 13
> 00 14

005.17 EID5 Static : DANGER!
At offset : 0x81BE0
Actual data :
> FF FF FF FF
Expected data :
> 00 12 07 30

005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : DANGER!
Any bytes from offset 0x80880 to offset 0x81370 should be less than 1.2%.
0xFF is 49.82%
005.20 eEID Statistics1 : DANGER!
Any bytes from offset 0x81390 to offset 0x825D0 should be less than 1.2%.
0xFF is 46.47%


******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : DANGER!
At offset : 0x90A60
Actual data :
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Expected data (one of the list):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 1F FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 07 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 3F FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00

006.15 cISD 0xFF Filled Area : OK


******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK


******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : WARNING!
Size = 0x2C0
MD5 = 112528EAAC9E58C6DB66B4604F8597DC
Version = (unknown)

008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : WARNING!
Size = 0x2C0
MD5 = 7FC609781B70DFB88203A3B05FB1700A
Version = (unknown)

008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : WARNING!
At offset : 0x94820
Actual data :
> FF FF FF FF
Expected data :
> 53 43 45 00



******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK


******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : WARNING!
At offset : 0xC0020
Actual data :
> 00 00 00 03 00 00 00 09 00 00 00 00 00 4B E5 78
Expected data :
> 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0

009.02 ROS0 Hash : WARNING!
Size = 0x6FFFE0
MD5 = F51BF5B961BBFEC20C3DD3362FE8908C
Version = (unknown)

009.03 ROS1 Header : OK
009.04 ROS1 Hash : WARNING!
Size = 0x6FFFE0
MD5 = B74B94D2CD2CAC7C52E5C6C0D6D3E053
Version = (unknown)



******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : WARNING!
All bytes from offset 0xEFF000 to offset 0xF00000 should be 0x00.
Byte at offset 0xEFF200 has value : 0xFF
Subsequent bytes in the range may be wrong as well.



******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : WARNING!
At offset : 0xE780200
Actual data :
> A6 E2 BF BA BD B2 F4 BC BC A5 EB A1 E8 F3 A8 BD
E7 B5 A6 E2 E0 A9 A3 F2 E3 BD FE E4 F5 A8 F8 A7
F8 AC BD BC A4 F6 FC EF B6 AA FB A8 EE FD EE AA
EF B5 BB A0 E7 EC B4 F2 F4 BE A3 E0 F0 B9 F6 AB
A7 E3 F5 BE AA A5 EE E8 FB AC B0 F1 F5 A5 A8 B4
Expected data :
> 00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 03 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF
00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF

011.04 cell_ext_os_area 0xFF Filled Area 1 : WARNING!
All bytes from offset 0xE780250 to offset 0xE780400 should be 0xFF.
Byte at offset 0xE780250 has value : 0xFD
Subsequent bytes in the range may be wrong as well.



******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : DANGER!
Any bytes from offset 0xF000000 to offset 0xF02EF80 should be less than 0.5%.
0xA0 is 0.98%
0xA1 is 1.00%
0xA2 is 0.94%
0xA3 is 0.96%
0xA4 is 0.97%
0xA5 is 0.96%
0xA6 is 0.96%
0xA7 is 0.98%
0xA8 is 0.98%
[emoji767] is 0.96%
0xAA is 0.95%
0xAB is 0.99%
0xAC is 0.99%
0xAD is 0.92%
[emoji768] is 0.96%
0xAF is 1.00%
0xB0 is 0.97%
0xB1 is 0.96%
0xB2 is 1.01%
0xB3 is 1.02%
0xB4 is 0.94%
0xB5 is 1.01%
0xB6 is 0.96%
0xB7 is 0.97%
0xB8 is 0.95%
0xB9 is 0.93%
0xBA is 0.94%
0xBB is 0.94%
0xBC is 0.95%
0xBD is 0.98%
0xBE is 0.93%
0xBF is 0.96%
0xE0 is 0.96%
0xE1 is 0.98%
0xE2 is 0.96%
0xE3 is 0.98%
0xE4 is 1.00%
0xE5 is 0.97%
0xE6 is 0.99%
0xE7 is 0.97%
0xE8 is 0.94%
0xE9 is 0.99%
0xEA is 0.99%
0xEB is 0.94%
0xEC is 0.98%
0xED is 0.99%
0xEE is 0.99%
0xEF is 0.99%
0xF0 is 1.03%
0xF1 is 0.99%
0xF2 is 1.01%
0xF3 is 0.99%
0xF4 is 0.99%
0xF5 is 1.01%
0xF6 is 0.96%
0xF7 is 0.93%
0xF8 is 1.01%
0xF9 is 0.97%
0xFA is 0.97%
0xFB is 0.98%
0xFC is 1.00%
0xFD is 1.02%
0xFE is 0.98%
0xFF is 1.01%
012.05 bootldr 0xFF Filled Area : DANGER!
All bytes from offset 0xF02EF80 to offset 0xF040000 should be 0xFF.
Byte at offset 0xF02EF80 has value : 0xFE
Subsequent bytes in the range may be wrong as well.



******* Checking datamatches *******
bootldr size : OK
per console nonce : DANGER!
Following datas should be the same :
bootldr0 at offset 0x14 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
bootldr1 at offset 0xF000014 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
metldr at offset 0x40854 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
eid0 at offset 0x80884 length 0xC
> 1F 9D 86 61 B0 8E 62 01 49 D4 0A 9F
eid3 at offset 0x81AB4 length 0xC
> FF FF FF FF FF FF FF FF FF FF FF FF
eid5 at offset 0x81BE4 length 0xC
> FF FF FF FF FF FF FF FF FF FF FF FF

bootldr : DANGER!
Following datas should be the same :
bootldr Top at offset 0x0 length 0x40000
(too long to dilplay)
bootldr Bottom at offset 0xF000000 length 0x40000
(too long to dilplay)

metldr size : OK
vtrm header datas : OK
vtrm : DANGER!
Following datas should be the same :
repetitions seq. 1 at offset 0xEF94C0 length 0x14, repeted 0x417 time
(too long to dilplay)
repetitions seq. 2 at offset 0xEFE6A0 length 0x14, repeted 0x78 time
(too long to dilplay)



******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : DANGER!
Following data expected at offset 0x40220 :
> 61 73 65 63 75 72 65 5F 6C 6F 61 64 65 72 00 00
No matching data found!

eEID Repetition : DANGER!
Following data expected at offset 0x40250 :
> 65 45 49 44 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

cISD Repetition : DANGER!
Following data expected at offset 0x40280 :
> 63 49 53 44 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

cCSD Repetition : DANGER!
Following data expected at offset 0x402B0 :
> 63 43 53 44 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

trvk_prg Repetition : DANGER!
Following data expected at offset 0x402E0 :
> 74 72 76 6B 5F 70 72 67 00 00 00 00 00 00 00 00
No matching data found!

trvk_pkg Repetition : DANGER!
Following data expected at offset 0x40310 :
> 74 72 76 6B 5F 70 6B 67 00 00 00 00 00 00 00 00
No matching data found!

ros Repetition : DANGER!
Following data expected at offset 0x40370 :
> 72 6F 73 00 00 00 00 00 00 00 00 00 00 00 00 00
No matching data found!

cvtrm Repetition : DANGER!
Following data expected at offset 0x403A0 :
> 63 76 74 72 6D 00 00 00 00 00 00 00 00 00 00 00
No matching data found!



******* Additional information *******
MAC address :
CID :
eCID :
board_id (part of console S/N) :
kiban_id (board barcode) :



******* Checks completed *******

Total number of checks = 131
Number of dangers = 44
Number of warnings = 11

Following check(s) returned a DANGER!
001.04 bootldr Statistics (Top)
003.01 Flash Region Table Header
003.02 asecure_loader Offset - Length
003.03 asecure_loader Name
003.04 eEID Offset - Length
003.05 eEID Name
003.06 cISD Offset - Length
003.07 cISD Name
003.08 cCSD Offset - Length
003.09 cCSD Name
003.10 trvk_prg Offset - Length
003.11 trvk_prg Name
003.12 trvk_pkg Offset - Length
003.13 trvk_pkg Name
003.14 creserved_0 Offset - Length
003.15 creserved_0 Name
003.16 ros Offset - Length
003.17 ros Name
003.18 cvtrm Offset - Length
003.19 cvtrm Name
004.07 metldr Statistics
005.11 EID2 BlockSize/Padding
005.12 EID3 Static0
005.13 EID3 Static1
005.14 EID3 Static2
005.15 EID5 IDPS0
005.16 EID5 IDPS1
005.17 EID5 Static
005.19 eEID Statistics0
005.20 eEID Statistics1
006.14 cISD2
012.04 bootldr Statistics (Bottom)
012.05 bootldr 0xFF Filled Area
datamatches : per console nonce
datamatches : bootldr
datamatches : vtrm
repcheck : asecure_loader Repetition
repcheck : eEID Repetition
repcheck : cISD Repetition
repcheck : cCSD Repetition
repcheck : trvk_prg Repetition
repcheck : trvk_pkg Repetition
repcheck : ros Repetition
repcheck : cvtrm Repetition

Following check(s) returned a WARNING!
003.20 Flash Region Table 0x00 Filled Area
004.08 asecure_loader 0x00 Filled Area
008.02 trvk_prg0 Hash
008.04 trvk_prg1 Hash
008.07 trvk_pkg1 SCE
009.01 ROS0 Header
009.02 ROS0 Hash
009.04 ROS1 Hash
010.07 cvtrm 0x00 Filled Area
011.03 cell_ext_os_area Break Section
011.04 cell_ext_os_area 0xFF Filled Area 1

All checks done in 3.25 seconds.

Lots of warnings and error, I am doing other dumps to make sure I got valid dumps.
Now, can I restore this NAND with this errors?
And how can I restore this NAND?

From the logs you posted, it appears your dumps are invalid.
Roughly speaking, you cannot use an invalid dump as a base for NOR/NAND restoration unless the corruption is strictly limited to CoreOS regions.
Corrupted CoreOS regions can be fixed by applying a no-fsm patch on the dump for instance.
But any other corruption would either require manual fixes (that requires skills & knowledge) or be unfixable (per console unique data).
You need to be 100% sure that your dumps are completely valid. 1 or 2 warnings can be ok, it depends, but dozens of errors won't do. You can see in the logs that much of the data is just 0xFF bytes.

 

[lugh22]

Took another dump and this looks better

Spoiler

PyPS3checker v0.10.x. Check log.

Checked file : C:\Users\Acer\OneDrive\Documentos\PS3\DUMPS PS3\CECHE01MG\DUMP02\nand.bin


******* Getting flash type *******
Flash type : NAND (full dump, 256MB)


******* Getting SKU identification datas *******
idps =
metldr0 = 0xE8E0
metldr1 = 0x0E8A
bootldr0 = 0x2EF4
bootldr1 = 0x2EF4
bootldrsize = 0x2EF80

Matching SKU : OK
CECHE01 MG (COK-002)
Minimum version 1.00


******* Getting SDK versions *******
ROS0 : 487.000
ROS1 : 235.000


******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : OK
001.05 bootldr (Top) 0xFF Filled Area : OK


******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK


******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg Offset - Length : OK
003.11 trvk_prg Name : OK
003.12 trvk_pkg Offset - Length : OK
003.13 trvk_pkg Name : OK
003.14 creserved_0 Offset - Length : OK
003.15 creserved_0 Name : OK
003.16 ros Offset - Length : OK
003.17 ros Name : OK
003.18 cvtrm Offset - Length : OK
003.19 cvtrm Name : OK
003.20 Flash Region Table 0x00 Filled Area : OK


******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK


******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK


******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK


******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK


******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : WARNING!
Size = 0x2C0
MD5 = E339EB916D7DD86CE497F9AD42ADB9E9
Version = (unknown)

008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2C0
MD5 = 02AEEBC058B53653B0D9F96E61BB8F70
Version = 2.35 (from PUP)

008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : WARNING!
At offset : 0x94820
Actual data :
> FF FF FF FF
Expected data :
> 53 43 45 00



******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK


******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : WARNING!
At offset : 0xC0020
Actual data :
> 00 00 00 03 00 00 00 09 00 00 00 00 00 4B E5 78
Expected data :
> 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0

009.02 ROS0 Hash : WARNING!
Size = 0x6FFFE0
MD5 = 6B6BD5CCEBC41C19364F6F228867512F
Version = (unknown)

009.03 ROS1 Header : OK
009.04 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = 8E90D6483CCB71AA78780AAF43CC42F8
Version = 2.35 CEX/SEX OFW



******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : OK


******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : OK
011.04 cell_ext_os_area 0xFF Filled Area 1 : OK


******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : OK
012.05 bootldr 0xFF Filled Area : OK


******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
bootldr : OK
metldr size : OK
vtrm header datas : OK
vtrm : OK


******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : OK
eEID Repetition : OK
cISD Repetition : OK
cCSD Repetition : OK
trvk_prg Repetition : OK
trvk_pkg Repetition : OK
ros Repetition : OK
cvtrm Repetition : OK


******* Additional information *******
MAC address :
CID :
eCID :
board_id (part of console S/N) :
kiban_id (board barcode) :


******* Checks completed *******

Total number of checks = 131
Number of dangers = 0
Number of warnings = 4

Following check(s) returned a WARNING!
008.02 trvk_prg0 Hash
008.07 trvk_pkg1 SCE
009.01 ROS0 Header
009.02 ROS0 Hash

All checks done in 3.30 seconds.

The ROS0 could make sense give me a warning since I tried to update several times and all failed at 4%.

 

[bguerville]

Took another dump and this looks better

Spoiler

PyPS3checker v0.10.x. Check log.

Checked file : C:\Users\Acer\OneDrive\Documentos\PS3\DUMPS PS3\CECHE01MG\DUMP02\nand.bin


******* Getting flash type *******
Flash type : NAND (full dump, 256MB)


******* Getting SKU identification datas *******
idps =
metldr0 = 0xE8E0
metldr1 = 0x0E8A
bootldr0 = 0x2EF4
bootldr1 = 0x2EF4
bootldrsize = 0x2EF80

Matching SKU : OK
CECHE01 MG (COK-002)
Minimum version 1.00


******* Getting SDK versions *******
ROS0 : 487.000
ROS1 : 235.000


******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : OK
001.05 bootldr (Top) 0xFF Filled Area : OK


******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK


******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg Offset - Length : OK
003.11 trvk_prg Name : OK
003.12 trvk_pkg Offset - Length : OK
003.13 trvk_pkg Name : OK
003.14 creserved_0 Offset - Length : OK
003.15 creserved_0 Name : OK
003.16 ros Offset - Length : OK
003.17 ros Name : OK
003.18 cvtrm Offset - Length : OK
003.19 cvtrm Name : OK
003.20 Flash Region Table 0x00 Filled Area : OK


******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK


******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK


******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK


******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK


******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : WARNING!
Size = 0x2C0
MD5 = E339EB916D7DD86CE497F9AD42ADB9E9
Version = (unknown)

008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2C0
MD5 = 02AEEBC058B53653B0D9F96E61BB8F70
Version = 2.35 (from PUP)

008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : WARNING!
At offset : 0x94820
Actual data :
> FF FF FF FF
Expected data :
> 53 43 45 00



******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK


******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : WARNING!
At offset : 0xC0020
Actual data :
> 00 00 00 03 00 00 00 09 00 00 00 00 00 4B E5 78
Expected data :
> 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0

009.02 ROS0 Hash : WARNING!
Size = 0x6FFFE0
MD5 = 6B6BD5CCEBC41C19364F6F228867512F
Version = (unknown)

009.03 ROS1 Header : OK
009.04 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = 8E90D6483CCB71AA78780AAF43CC42F8
Version = 2.35 CEX/SEX OFW



******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : OK


******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : OK
011.04 cell_ext_os_area 0xFF Filled Area 1 : OK


******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : OK
012.05 bootldr 0xFF Filled Area : OK


******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
bootldr : OK
metldr size : OK
vtrm header datas : OK
vtrm : OK


******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : OK
eEID Repetition : OK
cISD Repetition : OK
cCSD Repetition : OK
trvk_prg Repetition : OK
trvk_pkg Repetition : OK
ros Repetition : OK
cvtrm Repetition : OK


******* Additional information *******
MAC address :
CID :
eCID :
board_id (part of console S/N) :
kiban_id (board barcode) :


******* Checks completed *******

Total number of checks = 131
Number of dangers = 0
Number of warnings = 4

Following check(s) returned a WARNING!
008.02 trvk_prg0 Hash
008.07 trvk_pkg1 SCE
009.01 ROS0 Header
009.02 ROS0 Hash

All checks done in 3.30 seconds.

The ROS0 could make sense give me a warning since I tried to update several times and all failed at 4%.

That's more like it...
@littlebalup
What do you think?

To be sure, you should try to make say 2 more dumps that are identical to this one.
Use either a binary comparison app or simply a md5/sha checksum utility & compare the dump hashes.

 

[lugh22]

That's more like it...
@littlebalup
What do you think?

To be sure, you should try to make say 2 more dumps that are identical to this one.
Use either a binary comparison app or simply a md5/sha checksum utility & compare the dump hashes.

I was able to get 3 identical dumps from NAND0, but from NAND1 every time there is some differences in the dump, also this NAND have 84 bad blocks.

Checking after every dump I get the same warnings

Spoiler

PyPS3checker v0.10.x. Check log.

Checked file : C:\Users\Acer\Desktop\DUMP04\nand.bin


******* Getting flash type *******
Flash type : NAND (full dump, 256MB)


******* Getting SKU identification datas *******
idps = 0x03
metldr0 = 0xE8E0
metldr1 = 0x0E8A
bootldr0 = 0x2EF4
bootldr1 = 0x2EF4
bootldrsize = 0x2EF80

Matching SKU : OK
CECHE01 MG (COK-002)
Minimum version 1.00


******* Getting SDK versions *******
ROS0 : 487.000
ROS1 : 235.000


******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : OK
001.05 bootldr (Top) 0xFF Filled Area : OK


******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK


******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg Offset - Length : OK
003.11 trvk_prg Name : OK
003.12 trvk_pkg Offset - Length : OK
003.13 trvk_pkg Name : OK
003.14 creserved_0 Offset - Length : OK
003.15 creserved_0 Name : OK
003.16 ros Offset - Length : OK
003.17 ros Name : OK
003.18 cvtrm Offset - Length : OK
003.19 cvtrm Name : OK
003.20 Flash Region Table 0x00 Filled Area : OK


******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK


******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK


******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK


******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK


******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : WARNING!
Size = 0x2C0
MD5 = E339EB916D7DD86CE497F9AD42ADB9E9
Version = (unknown)

008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2C0
MD5 = 02AEEBC058B53653B0D9F96E61BB8F70
Version = 2.35 (from PUP)

008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : WARNING!
At offset : 0x94820
Actual data :
> FF FF FF FF
Expected data :
> 53 43 45 00



******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK


******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : WARNING!
At offset : 0xC0020
Actual data :
> 00 00 00 03 00 00 00 09 00 00 00 00 00 4B E5 78
Expected data :
> 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0

009.02 ROS0 Hash : WARNING!
Size = 0x6FFFE0
MD5 = 6B6BD5CCEBC41C19364F6F228867512F
Version = (unknown)

009.03 ROS1 Header : OK
009.04 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = 8E90D6483CCB71AA78780AAF43CC42F8
Version = 2.35 CEX/SEX OFW



******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : OK


******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : OK
011.04 cell_ext_os_area 0xFF Filled Area 1 : OK


******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : OK
012.05 bootldr 0xFF Filled Area : OK


******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
bootldr : OK
metldr size : OK
vtrm header datas : OK
vtrm : OK


******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : OK
eEID Repetition : OK
cISD Repetition : OK
cCSD Repetition : OK
trvk_prg Repetition : OK
trvk_pkg Repetition : OK
ros Repetition : OK
cvtrm Repetition : OK


******* Additional information *******
MAC address :
CID :
eCID :
board_id (part of console S/N) :
kiban_id (board barcode) :



******* Checks completed *******

Total number of checks = 131
Number of dangers = 0
Number of warnings = 4

Following check(s) returned a WARNING!
008.02 trvk_prg0 Hash
008.07 trvk_pkg1 SCE
009.01 ROS0 Header
009.02 ROS0 Hash

All checks done in 3.94 seconds.

I checked all the bad blocks, and they are not mapped, so fixing the tvrk_prg0 and trvk_pkg1 can solve the problem with RSOD/BSOD and other erros with this PS3?

 

[bguerville]

If you keep getting identical dumps & you are sure that the hardware flasher is reading every NAND sector correctly:

The ros0 warnings can probably be ignored if the active ROS is ros1.
Same for trvk_prg0.

But the trvk_pkg1 warning (0xffffffff detected instead of 0x53434500 expected) looks to me like corruption that needs fixed.

Before going ahead with any changes, you may wanna wait for littlebalup or someone else with similar experience in dump analysis to confirm, your setup is based on old 2.35 firmware, there might be specifities I am not familiar with.

 

[lugh22]

If you keep getting identical dumps & you are sure that the hardware flasher is reading every NAND sector correctly:

The ros0 warnings can probably be ignored if the active ROS is ros1.
Same for trvk_prg0.

But the trvk_pkg1 warning (0xffffffff detected instead of 0x53434500 expected) looks to me like corruption that needs fixed.

Before going ahead with any changes, you may wanna wait for littlebalup or someone else with similar experience in dump analysis to confirm, your setup is based on old 2.35 firmware, there might be specifities I am not familiar with.

Thanks for the help @bguerville

The active ROS is ros1, every update attempt fails at 4%, OFW, CFW with noBD, noBT, RSODFix, nothing works, so still stuck with OFW 2.35.

Also I am a bit worried about the quantity of bad blocks in NAND1, 1 or 2 is normal, but 84?