PS3 PyPS3tools : a suite of python tools for PS3 flash memory dump files

No0bZiLLa said:
[MENTION=29]Joonie[/MENTION], how did you patch it? what was the problem? what caused the downgrader not to work?
Click to expand...

Judging by his original dump provided, the previous owner had REBUG 4.21.2 then updated to PS3ITA 4.50, but then you provided him rogero 3.55 downgrader v2, and he installed it just fine, so his syscon was set with 3.55 coreos, I had to build him 3.55 pup and coreos patch.

OK, firstly I built REBUG 3.55.4 D-REX with all the known patches just to make it booted to XMB. [RSOD, noBD, and noBT], then also swapped his CoreOS with the one from REBUG 3.55.4 D-REX [Dex kernel as default]

So the system booted as debugger mode, without proper display setting, that's why the guy had a black screen, simply pressing power button on boot could've fixed his black screen issue by resetting the display setting.

Anyhow, his system appeared to be fully working.
 
Last edited:
  • Like
Reactions: Zar
Major update of PyPS3checker to v0.5 :

v0.5.0, (29 nov 2016) :
Added CFW and DEX OFW ROS hashs recognition (thanks to baileyscream and all CFW devs).
Added trvk_prg hash check.
Added "Additional information" field (HDD, MAC address...).
Added some colored strings (optional, requires "Colorama" python module).
Plus some additional minor improvements.
Click to expand...

4263b0f5055740a288cd21fa3f9c814b.png


7f208b7a5d184a328219d3890d43d4b6.png


3d6790cd68634d259fd536aa716b4265.png

Many thanks to @baileyscream for the oldest CFW hashs and to @Joonie and @Alexander for their support.

So now the checker should recognize if a "popular" CFW is/has been installed instead of a false "warning" check result with unknown ROS.
However, the hash list is not 100% complete. So, please, if I missed something let me know by opening an issue on my git.

Thanks
 
Last edited:
@littlebalup some of my wierd test https://s.go.ro/yxyahc2z
this is unit made rsx swap possible on most units.
well is a long story just boot without hdd on 8002f2f0 error after modifications were done in syscon(final test folder). it is complex explanation for this. sandungas can explain better then me.
I realy cant remember if error was before there after reball both ,just got image on screen and didnt care to install any fw ,i assumed rest is easy fix.
the only first untouched nor dump ive took is https://s.go.ro/yuac1jip
rest inside are my tests and patched dumps,after i exchanged nor ic from Spansion to Mxic with 3,55 patched it gives special glod=can hear beeps for reset images,can hear beeps for entering recovery,no image on any port.
no rush or requires for fixing this unit ,just experimental testing,ill leave aside and if you think i should test anything ill do and report back.
 
Last edited:
@littlebalup the flash dumps uploaded by vyktor in the previous post belongs to a legendary PS3 (\o/), please take a look at them, i been checking them and pyps3checker reports a warning for trvk_prg1 (unknown hash), also it seems there is some kind of versions/revisions mistmatch
I dont really know why because is tricky to understand how many modifications vyktor made to this console, but let me try to resume it (and please vyktor correct me if im wrong)

The console had a faulty RSX, vyktor replaced it by a 40nm RSX together with the orbis modchip, also the syscon was replaced by a special "F" model (fully flashable)
When the RSX patches was published the orbis chip was removed, and the "F" syscon was replaced back by the factory syscon (patched for the 40nm RSX)
In all this time the console was booting without hdd, and was giving a correct video output... with a warning screen that tells something like "error 8002f2f0"
In wiki is metioned this kind of error happens while installing a PUP... but this is not the case because it doesnt even have an hdd, this detail (and the mistmatching revisions/versions of revoke packages inside flash) made me think maybe it crashed at an intermediate point of a PUP firmware installation, in other words... maybe a incomplete PUP installation is what created an invalid trvk_prg1 ?

While asking vyktor about the flash modifications he made, he mentioned the flash chip was replaced too.. just because he was suspecting it could have some physicall damage inside it (permanently damaged bad blocks, or some shit), but honestly i could not understand well how many things he made to the flash chip and the current state... im assuming he was modifying the flash contents

I suggested vyktor to ask you about it because maybe the problem is something easy for you to find... or maybe you can provide a valid copy of the trvk_prg1 with the matching revision/version
 
Yes sandungas, that is full history, also I'll try another rsx, already desolder it. If this goes in same stage errors I'll let it aside for further experiments and tests. I'll work with time so no rush for this unit.
 
You must log in or register to reply here.

Similar threads

Back
Top