PS3 PS3DumpChecker

littlebalup said:
Build 485 released with support of 4.76 firmware:
Thanks [MENTION=56]Alexander[/MENTION] ;)
Click to expand...

Thank you for new release!
Just downgrading an old cechh console and have strange cSid Semistatic2 region 56 00 56 00 86 00
is it ok and you will update hashes?
Dumps was taken three times and all equals
cechh.png
 
olegt said:
Thank you for new release!
Just downgrading an old cechh console and have strange cSid Semistatic2 region 56 00 56 00 86 00
is it ok and you will update hashes?
Dumps was taken three times and all equals
View attachment 3833
Click to expand...

This is not a hash.
Your data (swapped) is "00 56 00 56 00 86" which is not yet known/referenced in the wiki : Talk:Flash:Individual System Data - cISD - PS3 Developer wiki
That's why it returned a "bad". So, it sounds to be a false bad. If your are confident, patch and flash as is and let me know if everything is OK. Then I'll update wiki and PSDumpChecker accordingly.

Thanks.
 
All goes successfully!
Console is flashed by FERROX 4.76
Then downgrade to Rogero 3.55, then install HABIB 4.75 COBRA
But now have strange things:
System Update menu in XMB don't have "Network Update" or "Storage update".
Even if console disconnected from internet and no disk of usb-flash inserted it shows:
Checking system update...
And then "Update 4.76 found"
Very strange...

UPD:
After
Restore File System (Recovery)
Rebuild Database (Recovery)
and Restore to factory defaults (Recovery)
all menus have returned
 
Last edited:
olegt said:
All goes successfully!
Console is flashed by FERROX 4.76
Then downgrade to Rogero 3.55, then install HABIB 4.75 COBRA
But now have strange things:
System Update menu in XMB don't have "Network Update" or "Storage update".
Even if console disconnected from internet and no disk of usb-flash inserted it shows:
Checking system update...
And then "Update 4.76 found"
Very strange...

UPD:
After
Restore File System (Recovery)
Rebuild Database (Recovery)
and Restore to factory defaults (Recovery)
all menus have returned
Click to expand...

Thanks for the report.
Please, I need your SKUidentity data. Like this : Screenshot by Lightshot
 
First of all, thanks for this tool. I've only just started downgrading slims (done 4 so far) and this has been invaluable.

Next, a question. I usually do not update the OFW before grabbing it with the E3 flasher and instead just load the correct patch with the package you released earlier in this thread. I select the correct one for the version that is installed. No problem.
This one I have now has 4.75 but the tool (latest version) has 4.76 built in and 4.75 was not in the old patches package.
The real question is, can I patch a 4.75 dump with patcher 4.76 or am I supposed to first update to 4.76 and then dump it/patch it?

I still have 484 here for now, with 4.75 patch built in, so I'm safe for now. Just curious what the correct procedure is.

Thanks!
 
Turranius said:
First of all, thanks for this tool. I've only just started downgrading slims (done 4 so far) and this has been invaluable.

Next, a question. I usually do not update the OFW before grabbing it with the E3 flasher and instead just load the correct patch with the package you released earlier in this thread. I select the correct one for the version that is installed. No problem.
This one I have now has 4.75 but the tool (latest version) has 4.76 built in and 4.75 was not in the old patches package.
The real question is, can I patch a 4.75 dump with patcher 4.76 or am I supposed to first update to 4.76 and then dump it/patch it?

I still have 484 here for now, with 4.75 patch built in, so I'm safe for now. Just curious what the correct procedure is.

Thanks!
Click to expand...

You can patch ofw 4.76 with a 4.75 patch or ofw 4.75 with a 4.76 patch. The only thing, the console will not boot to XMB but will ask to re-install firmware (means CFW).
So the only value added to use a patch corresponding to your firmware version is to boot to XMB after the flash.

If you want the 4.75 standalone patch, it still available on github history : https://github.com/Swizzy/PS3DumpCh...6b406565/src/PS3DumpChecker/Patches/patch.bin
Rename it as you want.
 
Dear littlebalup
First of all wanna say Thanks for GUI to NANDway.py
Its really saves my time!

Now have a new challenge for you )) "No matching SKU model found!"
CECHB07 with unknown SKUidentity and strange cISD2
Need your help!

SKU.png

cISD2.png
 
Last edited:
olegt said:
Dear littlebalup
First of all wanna say Thanks for GUI to NANDway.py
Its really saves my time!

Now have a new challenge for you )) "No matching SKU model found!"
CECHB07 with unknown SKUidentity and strange cISD2
Need your help!

View attachment 4147

View attachment 4146
Click to expand...

For cisd2 check, you have 00000000... due to the fact you have a cechb (so, without wifi card) : Flash:Individual System Data - cISD - PS3 Developer wiki
So it's a false "bad". I don't know why this entry is missing in our checks... I'll correct it asap.

About sku, it return false because your idps target ID (0x02) for à cechb does not match meldr/bootldr size data per this table : Validating flash dumps - PS3 Developer wiki
But it match cok-001 board anyway (cechA). So values are not wrong. Wiki is incomplete or your console has been refurbished.

Conclusion : I'm 99.99% sure your dump is valid. You can go ahead.
Please, confirm your flash goes well once you'll do it. On my side I'll update wiki and checks asap.

Thanks for your feedback ;)
 
littlebalup said:
Conclusion : I'm 99.99% sure your dump is valid. You can go ahead.
Please, confirm your flash goes well once you'll do it. On my side I'll update wiki and checks asap.
Thanks for your feedback ;)
Click to expand...

Thanks for answer! Will try today and let you know.
 
olegt said:
hello dear littlebalup!
Have a new quiz for you )))
Just read cech2008b. 4 similar readings. Same errors in CELL_EXTNOR_AREA 00 Filled areas
Is it OK? or something wrong?

View attachment 4412
Click to expand...

I have not access to your attachment...
Anyway, it depend of what kind of data is in this area instead of the 0x00. Open your dump with hex editor, go to the offset of this check and take a screenshot for us.
 
Success!
At my own risk flash this patched dump back to CECH2008b with 320Gb Toshiba and all goes perfect!
 
You must log in or register to reply here.

Similar threads

Back
Top