PS3 original dump check warning

L

loren daoust

Forum Noob
I am following a mrmario jailbreak video. Got to the point of checking the original ps3 dump file on the pyps3checker and it has retuned one warning;

******* Checking CELL_EXTNOR_AREA_Region *******
013.01 CELL_EXTNOR_AREA Header : OK
013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 : OK
013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 : OK
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : WARNING!
All bytes from offset 0xF40030 to offset 0xF60000 should be 0x00.
Byte at offset 0xF4C97C has value : 0x10
Subsequent bytes in the range may be wrong as well.

totally out of my element here. I have tried to re-copy from the ps3 and checked again - same result. I have not gone further yet. I cannot seem to find any info on how to fix this or if it needs to be fixed.
 
You may or may not need to post the full log from PyPS3checker. All unique console information is stripped so you don't need to worry about that. @littlebalup is the developer and so is the best person to ask on anything related to PyPS3checker logs.

My @ will send him a notification for this thread and he'll hopefully take a look when he isn't too busy. In the meantime, sit tight as it's better to be safe than sorry. Unfortunately I'm not in a position to advise, but littlebalup I'm sure will be.
 
loren daoust said:
I am following a mrmario jailbreak video. Got to the point of checking the original ps3 dump file on the pyps3checker and it has retuned one warning;

******* Checking CELL_EXTNOR_AREA_Region *******
013.01 CELL_EXTNOR_AREA Header : OK
013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 : OK
013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 : OK
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : WARNING!
All bytes from offset 0xF40030 to offset 0xF60000 should be 0x00.
Byte at offset 0xF4C97C has value : 0x10
Subsequent bytes in the range may be wrong as well.

totally out of my element here. I have tried to re-copy from the ps3 and checked again - same result. I have not gone further yet. I cannot seem to find any info on how to fix this or if it needs to be fixed.
Click to expand...
Post the full pyps3checker log.
 
PyPS3checker v0.11.x. Check log.
Checked file : C:\Users\loren\Desktop\PyPS3checker-standalone-package_2021-22-11_215328\dump_original.hex
******* Getting flash type *******
Flash type : NOR
Reversed : NO
******* Getting SKU identification datas *******
idps = 0x09
metldr0 = 0xE890
metldr1 = 0x0E85
metldrkey = 0xBC78B8F02879A81184A0DA74
bootldr0 = 0x2F13
bootldr1 = 0x2F13
bootldrsize = 0x2F170
Matching SKU : OK
CECH-20xxx (DYN-001)
Minimum version 2.70
******* Getting SDK versions *******
ROS0 : 487.000
ROS1 : 488.000
******* Checking first_region_header *******
001.01 First Region Header 0x00 Filled Area 0 : OK
001.02 First Region Header Magic : OK
001.03 First Region Header 0x00 Filled Area 1 : OK
******* Checking flash_format *******
002.01 Flash Format String : OK
002.02 Flash Format Version : OK
002.03 Flash Format 0xFF Filled Area : 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_prg0 Offset - Length : OK
003.11 trvk_prg0 Name : OK
003.12 trvk_prg1 Offset - Length : OK
003.13 trvk_prg1 Name : OK
003.14 trvk_pkg0 Offset - Length : OK
003.15 trvk_pkg0 Name : OK
003.16 trvk_pkg1 Offset - Length : OK
003.17 trvk_pkg1 Name : OK
003.18 ros0 Offset - Length : OK
003.19 ros0 Name : OK
003.20 ros1 Offset - Length : OK
003.21 ros1 Name : OK
003.22 cvtrm Offset - Length : OK
003.23 cvtrm Name : OK
003.24 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.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : OK
Size = 0x2E0
MD5 = E537DE954DCF25D4DE961DF44549BAF7
Version = 3.50 (from PUP)
008.02 trvk_prg0 0xFF filled area : OK
008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.04 trvk_prg1 0xFF filled area : OK
008.05 trvk_pkg0 SCE : OK
008.06 trvk_pkg0 0xFF filled area : OK
008.07 trvk_pkg1 SCE : OK
008.08 trvk_pkg1 0xFF filled area : OK
******* Checking CoreOS_region *******
009.01 ROS0 Header : OK
009.02 ROS0 Hash : OK
Size = 0x6FFFE0
MD5 = 8F4A63DC20F1EB54168478C814DF80C1
Version = 4.87 CEX/SEX OFW/HFW
009.03 ROS0 unused 0xFF Filled Area : OK
009.04 ROS1 Header : OK
009.05 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = 36A0D80FB18E9D6FD7635217D59FA726
Version = 4.88 CEX/SEX OFW/HFW
009.06 ROS1 unused 0xFF Filled Area : OK
******* Checking cvtrm_region *******
010.01 Pre cvtrm 0xFF Filled Area : OK
010.02 cvtrm0 Header : OK
010.03 cvtrm0 0xFF Filled Area : OK
010.04 vtrm0 Magic : OK
010.05 vtrm0 Reserved Entries : OK
010.07 cvtrm1 Header : OK
010.08 cvtrm1 0xFF Filled Area : OK
010.09 vtrm1 Magic : OK
010.10 vtrm1 Reserved Entries : OK
******* Checking Second_Region_Header *******
011.01 Second Region Header 0x00 Filled Area 0 : OK
011.02 Second Region Header Magic : OK
011.03 Second Region Header Count : OK
011.04 Second Region Header 0x00 Filled Area 1 : OK
011.05 Second Region Unknown Block 0 : OK
011.06 Second Region Header 0x00 Filled Area 2 : OK
011.07 Second Region Unknown Block 1 : OK
011.08 Second Region Header 0x00 Filled Area 3 : OK
******* Checking Unreferenced_Area *******
012.01 unreferenced area 0xFF Filled : OK
******* Checking CELL_EXTNOR_AREA_Region *******
013.01 CELL_EXTNOR_AREA Header : OK
013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 : OK
013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 : OK
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : WARNING!
All bytes from offset 0xF40030 to offset 0xF60000 should be 0x00.
Byte at offset 0xF4C97C has value : 0x10
Subsequent bytes in the range may be wrong as well.
013.05 CELL_EXTNOR_AREA 0x00 Filled Area 3 : OK
013.06 CELL_EXTNOR_AREA 0xFF Filled Area 0 : OK
013.07 CELL_EXTNOR_AREA 0x00 Filled Area 5 : OK
013.08 CELL_EXTNOR_AREA 0x00 Filled Area 6 : OK
013.09 CELL_EXTNOR_AREA 0xFF Filled Area 1 : OK
******* Checking bootldr_region *******
014.01 bootldr0 : OK
014.02 bootldr1 : OK
014.03 bootldr Rev key : OK
014.04 bootldr Statistics : OK
014.05 bootldr 0xFF Filled Area : OK
******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
CELL_EXTNOR_AREA Hash1 : OK
CELL_EXTNOR_AREA Hash2 : OK
metldr size : OK
vtrm0 : OK
vtrm1 : OK
******* Checking repetitions *******
Header Magic0 Repetitions : OK
asecure_loader Repetitions : OK
eEID Repetitions : OK
cISD Repetitions : OK
cCSD Repetitions : OK
trvk_prg0 Repetitions : OK
trvk_prg1 Repetitions : OK
trvk_pkg0 Repetitions : OK
trvk_pkg1 Repetitions : OK
ros0 Repetitions : OK
ros1 Repetitions : OK
cvtrm Repetitions : OK
******* Additional information *******
HDD : TOSHIBA MK2555GSX H 9926SCBBS
MAC address : 00:24:8D:9D:15:56
CID : 0x00010071D548
eCID : 01DF00E7C01057181304E24200000000
board_id (part of console S/N) : 27453905
kiban_id (board barcode) : 3HG13605148D
******* Checks completed *******
Total number of checks = 155
Number of dangers = 0
Number of warnings = 1
Following check(s) returned a WARNING!
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2
All checks done in 4.72 seconds.
----------------------------------------------------------------------------
| IMPORTANT NOTICE ! |
| Checks of late CECH-25xxx, CECH-3xxxx and CECH-4xxxx consoles dumps still |
| under development and may return false results. If you feel it's the case, |
| please post your *.checklog.txt in a new issue on my github repository: |
| https://github.com/littlebalup/PyPS3tools/issues |
| Thanks! It will help me a lot to improve that tool ;) |
----------------------------------------------------------------------------
 
bguerville said:
That is fine, no need for any other file for the time being.

I don't think this warning is a problem given the dump region in question (CELL_EXTNOR_AREA is the OtherOS region of the NOR if I remember correctly) HOWEVER you should wait for @littlebalup to give you his opinion, he has a lot more experience with dump analysis.
Click to expand...

There is no oos region on NOR flash (it's in vflash).
CELL_EXTNOR_AREA is mainly where crl/drl hash are stored. https://www.psdevwiki.com/ps3/Flash:CELL_EXTNOR_AREA

The warning reported here looks like an artifact in an unused area between crl1 and drl1 hash. It would be interesting to look with an hex editor at 0xF4C97C if it's an isolated byte or not.
It happens sometime to find artifacts in unused areas.
That said crl/drl hashes are repeated and this is checked OK by the checker. So it shouldn't be an issue.
 
littlebalup said:
There is no oos region on NOR flash (it's in vflash).
CELL_EXTNOR_AREA is mainly where crl/drl hash are stored. https://www.psdevwiki.com/ps3/Flash:CELL_EXTNOR_AREA

The warning reported here looks like an artifact in an unused area between crl1 and drl1 hash. It would be interesting to look with an hex editor at 0xF4C97C if it's an isolated byte or not.
It happens sometime to find artifacts in unused areas.
That said crl/drl hashes are repeated and this is checked OK by the checker. So it shouldn't be an issue.
Click to expand...
Thanks, failing memory, getting old is a terrible thing lol, I edited my post to avoid confusion..
 
littlebalup said:
There is no oos region on NOR flash (it's in vflash).
CELL_EXTNOR_AREA is mainly where crl/drl hash are stored. https://www.psdevwiki.com/ps3/Flash:CELL_EXTNOR_AREA

The warning reported here looks like an artifact in an unused area between crl1 and drl1 hash. It would be interesting to look with an hex editor at 0xF4C97C if it's an isolated byte or not.
It happens sometime to find artifacts in unused areas.
That said crl/drl hashes are repeated and this is checked OK by the checker. So it shouldn't be an issue.
Click to expand...
dose this error mean I cant downgrade? I at CFW 4.88.2 Evilnat Cobra 8.3 and be trying to see if i can go 4.85 for rebug dex
before it has 6 error but now down to 1, but i guess it fix by replace big HDD to small 1tb to 500 gb.
Need help, but i would love to learn how to fix them. CECHG01 1.90 version
Matching SKU : WARNING!
No matching SKU found!
 
DrSoul2495 said:
dose this error mean I cant downgrade? I at CFW 4.88.2 Evilnat Cobra 8.3 and be trying to see if i can go 4.85 for rebug dex
before it has 6 error but now down to 1, but i guess it fix by replace big HDD to small 1tb to 500 gb.
Need help, but i would love to learn how to fix them. CECHG01 1.90 version
Matching SKU : WARNING!
No matching SKU found!
Click to expand...
That is probably a refurbished console. (Updated metldr not matching regular cechg). Need to look at the customer id (CID) at the end of the log.
 
littlebalup said:
It starts with 0x0FFF so it's refurbished and explains the warning. It has no incidence.
Click to expand...
I know it a refurbished i look into your dump checker which is awesome BTW No joke, but i wanna to downgrade to 4.85 so i can get into dex on my fat ps3, but i cant for some reason, maybe because of that error? if you can guide me to downgrade, that would be awesome too. PM me.
 
Last edited:
DrSoul2495 said:
I know it a refurbished i look into your dump check which is awesome BTW No joke, but i wanna to downgrade to 4.85 so i can get into dex on my fat ps3, but i cant for some reason, maybe because of that error? if you can guide me to downgrade, that would be awesome too. PM me.
Click to expand...
We dont know whats that byte/s, if we assume is garbage from repair service we are assuming also the console is ignoring it
If we assume is some kind of special settings they used in repair service it would mean that is right

One way or the other is not a problem, what you could do right now to try to enlight this mistery a bit is to take a look at the dump in a hexeditor, basically you need to check at offset 0xF4C97C (where you are going to find the byte 0x10) and tell us how looks the bytes that comes next
That area was supposed to be filled with zeroes, but pyps3checker stopped checking it when it found the 0x10 at offset 0xF4C97C so we dont know if is an isolated byte or if there is more data after it (different than zeroes)
For a full check you need to look up to offset 0xF60000

Btw @littlebalup you could allow the tool to continue reading the area (even after finding bytes different than zero) and count them, then display the counter in the log, this way:
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : WARNING!
All bytes from offset 0xF40030 to offset 0xF60000 should be 0x00.
Byte at offset 0xF4C97C has value : 0x10
Total bytes different than zero : 0x27
Click to expand...
In other words, you show the offset of the first byte that differs in the same way is made actually, and a counter of the others that comes after it, intended to give an small hint of how much data differs
Displaying a list of all the bytes that differs with his offsets is overkill, so this intermediate solution is not so bad, is an small improvement over the actual info
 
sandungas said:
We dont know whats that byte/s, if we assume is garbage from repair service we are assuming also the console is ignoring it
If we assume is some kind of special settings they used in repair service it would mean that is right

One way or the other is not a problem, what you could do right now to try to enlight this mistery a bit is to take a look at the dump in a hexeditor, basically you need to check at offset 0xF4C97C (where you are going to find the byte 0x10) and tell us how looks the bytes that comes next
That area was supposed to be filled with zeroes, but pyps3checker stopped checking it when it found the 0x10 at offset 0xF4C97C so we dont know if is an isolated byte or if there is more data after it (different than zeroes)
For a full check you need to look up to offset 0xF60000

Btw @littlebalup you could allow the tool to continue reading the area (even after finding bytes different than zero) and count them, then display the counter in the log, this way:

In other words, you show the offset of the first byte that differs in the same way is made actually, and a counter of the others that comes after it, intended to give an small hint of how much data differs
Displaying a list of all the bytes that differs with his offsets is overkill, so this intermediate solution is not so bad, is an small improvement over the actual info
Click to expand...
That's good idea. I'll take a look.
 
DrSoul2495 said:
I know it a refurbished i look into your dump checker which is awesome BTW No joke, but i wanna to downgrade to 4.85 so i can get into dex on my fat ps3, but i cant for some reason, maybe because of that error? if you can guide me to downgrade, that would be awesome too. PM me.
Click to expand...

To downgrade you need to set the QA flag.
 
DrSoul2495 said:
I did Toggle QA flag, and still not work
Click to expand...
What does not work?

Toggle QA to enable it, reboot the console, install Rebug REX 4.84.2 & convert to DEX with the Rebug Toolbox.
That should work just fine unless there is a problem with your console.
 
bguerville said:
What does not work?

Toggle QA to enable it, reboot the console, install Rebug REX 4.84.2 & convert to DEX with the Rebug Toolbox.
That should work just fine unless there is a problem with your console.
Click to expand...
I had 4.81 rebug dex pup, not rex, that why it giving me a problem. My bad lol :witless:
 
You must log in or register to reply here.

Similar threads

Back
Top