PS3 PS3DumpChecker

Updated to build 479 with new settings organisation and stuffs : http://i.imgur.com/F2mK4fn.png

Plus some minor fixes & changes:

Build 479 2015-01-23:
- Added: embedded ROS patch version now displayed in settings.
- Added: new button to restore default values of settings (clear registry then restart the application).
- Improved: settings form, some tooltips...
- Fixed: now "Restore ROS header" option is disabled if internal patcher is not used.
- Fixed: cvtrm Header static check (NAND)
Click to expand...
 
Build 484 released with replacement of the embedded noFSM patch by a 4.75 patch made out of FERROX 4.75 CEX 1.00 CoreOS files (repacked). Many thanks to [MENTION=56]Alexander[/MENTION].

See first post for details.

For those who would like to update the Rogero's autopatcher or any other patcher, the patch is available to Swizzy's git repo here : [noparse]https://github.com/Swizzy/PS3DumpChecker/raw/master/src/PS3DumpChecker/Patches/patch.bin[/noparse]
MD5: FB00F805C27130579A6FE2A2489A66A7
 
Last edited:
hey littlebalup

first, thanks for all you do! I appreciate it !

so I have this issue that I think may be a problem with the patcher embedded in build 484. I contacted swizzy and he told me to get with you...

I am working with a 4.75 ofw system and had 3 successful dumps ...They all checked out fine. so i patched the last dump and the bkpps3 file now was bkpps3_patched , I changed the name to just bkpps3. Then I ran it through the dumpchecker again ...but normally when a file is patched in the corner of the gui where it says "pre-patched" it always says yes when its a patched file. But on build 484 it doesn't. it just asks again "do you want to patch the image" which it isn't supposed to if the image is patched. I made triple sure by patching one of the other dumps and same thing happen

so I decided to upload the patched dump into the ps. Then on my flasher, the first light was blinking, the next 3 were off and then all the rest were blinking ..meaning it couldn't read the file, or the micro card wasn't sitting right or a problem with the file ..etc

very luckily I was able to install the original bios. and I turned off the ps then on and did 3 more dumps all checked fine. without moving anything I patched one of them and same thing happened all over again as above. the flasher blinked, the ps was able to turn on and i had to flash the original bios again and nothing blinks and it all works like normal

so the problem isnt my flasher because it dumps and uploads the original bios just fine.

so to eliminate other possible issues on my end .....I have different builds of this dumpchecker and I save all the bios and patched bios of every ps I downgrade. So I took a patched bios of a 4.66 system. When I ran it through build 484 guess what... it DIDN:T ask me if I wanted to patch it and in the upper right corner it now had a YES next to "pre patched" . I did this same process for a patched bios of 4.55 and 4.70 systems and it checked out ok too!

But these 3 patched bios obviously were done with different version patchers not this build 484. So the problem definitely is something patcher related . when you patch 4.75 ofw bios with it , it won't do it correctly. but if you check any other patched ones that were patched using other builds or other patchers , then it will show the patch bio as good and not ask if I want to patch them again which it shouldn't and in the pre patch box it will say yes

so basically I can't downgrade my 4.75 ofw because the bios patched with build 484 are not being accepted by the flasher...but all others are.

Thanks in advance for any assistance
 
Last edited:
Zoilus said:
hey littlebalup

first, thanks for all you do! I appreciate it !

so I have this issue that I think may be a problem with the patcher embedded in build 484. I contacted swizzy and he told me to get with you...

I am working with a 4.75 ofw system and had 3 successful dumps ...They all checked out fine. so i patched the last dump and the bkpps3 file now was bkpps3_patched , I changed the name to just bkpps3. Then I ran it through the dumpchecker again ...but normally when a file is patched in the corner of the gui where it says "pre-patched" it always says yes when its a patched file. But on build 484 it doesn't. it just asks again "do you want to patch the image" which it isn't supposed to if the image is patched. I made triple sure by patching one of the other dumps and same thing happen

so I decided to upload the patched dump into the ps. Then on my flasher, the first light was blinking, the next 3 were off and then all the rest were blinking ..meaning it couldn't read the file, or the micro card wasn't sitting right or a problem with the file ..etc

very luckily I was able to install the original bios. and I turned off the ps then on and did 3 more dumps all checked fine. without moving anything I patched one of them and same thing happened all over again as above. the flasher blinked, the ps was able to turn on and i had to flash the original bios again and nothing blinks and it all works like normal

so the problem isnt my flasher because it dumps and uploads the original bios just fine.

so to eliminate other possible issues on my end .....I have different builds of this dumpchecker and I save all the bios and patched bios of every ps I downgrade. So I took a patched bios of a 4.66 system. When I ran it through build 484 guess what... it DIDN:T ask me if I wanted to patch it and in the upper right corner it now had a YES next to "pre patched" . I did this same process for a patched bios of 4.55 and 4.70 systems and it checked out ok too!

But these 3 patched bios obviously were done with different version patchers not this build 484. So the problem definitely is something patcher related . when you patch 4.75 ofw bios with it , it won't do it correctly. but if you check any other patched ones that were patched using other builds or other patchers , then it will show the patch bio as good and not ask if I want to patch them again which it shouldn't and in the pre patch box it will say yes

so basically I can't downgrade my 4.75 ofw because the bios patched with build 484 are not being accepted by the flasher...but all others are.

Thanks in advance for any assistance
Click to expand...

Hi,
I missed a tag into the hashlist xml file. PS3DumpChecker patched your dump but the patched ROS hash is not recognize as "patched" (you can see your dump is patched looking at the ROS hash).
Anyway, it has been fixed some days ago ( [noparse]https://github.com/Swizzy/PS3DumpChecker/commit/45a202e00dd7ed4167da52eb23f3ef566b406565[/noparse] ).
I didn't made a new build just for that. You simply need to update the hashlist from the software, like this :

4OhBLke.png


My apologize for the disturbance. :embarrassed:
 
Last edited by a moderator:
littlebalup said:
Hi,
I missed a tag into the hashlist xml file. PS3DumpChecker patched your dump but the patched ROS hash is not recognize as "patched" (you can see your dump is patched looking at the ROS hash).
Anyway, it has been fixed some days ago ( [noparse]https://github.com/Swizzy/PS3DumpChecker/commit/45a202e00dd7ed4167da52eb23f3ef566b406565[/noparse] ).
I didn't made a new build just for that. You simply need to update the hashlist from the software, like this :

4OhBLke.png


My apologize for the disturbance. :embarrassed:
Click to expand...

wasn't it part of your instructions to update your stuff (hashlisht, cfg file, latest build) to the latest before checking dumps?
I can't remember if it was part of your instructions or part of my common sense, lol.
 
Last edited by a moderator:
thanks for the reply Littlebalup .... and don't worry about it your fine

but that's the hashlist i'm using. just to make sure I did your steps and it says I have the newest/current one already. Still having the same problem. It will show that the 4.75 bios have been patched but it won't say yes in the corner...but worse is that the nor flasher doesn't accept the 4.75 patch. On that same ps using the same flasher I can install the factory 4.75 ofw bios with no issue ..

so then to test it out, I patched the factory 4.75 bios with 4.70 darkjiros patcher, the flasher won't install those either. it seems that the flasher has some kind of safe guard so that only "like" bios of the same firmware number can be installed.

And for years I've always done it that way ...so 4.55 ofw would get 4.55 patched bios...4.70 gets 4.70 never any issues

and I just did another 4.70 system using 481 dump checker and darkjiros nor nand patcher and as usual everything worked smooth as butter. But this other ps on 4.75 ofw won't take anything that was patched with this 484 build . I just don't get it.


so I decided to upload the patched dump into the 4.75 ps again. Then on my flasher, the first light was blinking, the next 3 were off and then all the rest were blinking ..meaning it couldn't read the file, or the micro card wasn't sitting right or a problem with the file ..etc

the ps still turnes on and boots up so I decided to do a dump of this corrupted patched bios done with the 484 build ...in the nor inspector the ros 0 line had a bunch of jibberish characters in the ROS 1 line it was 4.75. and in the status tab half the things were red. But the flasher is connected correctly .

when I ran the dumpchecker 2 checks failed.

Lines:
009.02 ROS0 hash
009.03 ROS0 version

without moving or touching the flasher I was able to install the original bios as normal with no issue. I turned off the ps then on and did 3 more dumps all checked fine. im doing the same thing i've done for over 150 ps3's , I honestly doubt the problem is my end. The flasher works for 4.70 and below systems, the micro card is brand new, nothing has changed on my pc's. the only thing that has changed is going from build 481 to 484.

any ideas?

thanks again
 
When you are changing name you are adding .bin extension? If yes then try don't do this. Just leave name bkpps3
 
Zoilus said:
thanks for the reply Littlebalup .... and don't worry about it your fine

but that's the hashlist i'm using. just to make sure I did your steps and it says I have the newest/current one already. Still having the same problem. It will show that the 4.75 bios have been patched but it won't say yes in the corner...but worse is that the nor flasher doesn't accept the 4.75 patch. On that same ps using the same flasher I can install the factory 4.75 ofw bios with no issue ..

so then to test it out, I patched the factory 4.75 bios with 4.70 darkjiros patcher, the flasher won't install those either. it seems that the flasher has some kind of safe guard so that only "like" bios of the same firmware number can be installed.

And for years I've always done it that way ...so 4.55 ofw would get 4.55 patched bios...4.70 gets 4.70 never any issues

and I just did another 4.70 system using 481 dump checker and darkjiros nor nand patcher and as usual everything worked smooth as butter. But this other ps on 4.75 ofw won't take anything that was patched with this 484 build . I just don't get it.


so I decided to upload the patched dump into the 4.75 ps again. Then on my flasher, the first light was blinking, the next 3 were off and then all the rest were blinking ..meaning it couldn't read the file, or the micro card wasn't sitting right or a problem with the file ..etc

the ps still turnes on and boots up so I decided to do a dump of this corrupted patched bios done with the 484 build ...in the nor inspector the ros 0 line had a bunch of jibberish characters in the ROS 1 line it was 4.75. and in the status tab half the things were red. But the flasher is connected correctly .

when I ran the dumpchecker 2 checks failed.

Lines:
009.02 ROS0 hash
009.03 ROS0 version

without moving or touching the flasher I was able to install the original bios as normal with no issue. I turned off the ps then on and did 3 more dumps all checked fine. im doing the same thing i've done for over 150 ps3's , I honestly doubt the problem is my end. The flasher works for 4.70 and below systems, the micro card is brand new, nothing has changed on my pc's. the only thing that has changed is going from build 481 to 484.

any ideas?

thanks again
Click to expand...

Issue with PS3dumpchecker is totally independent of the issue you may have with your flasher. Even if patch is wrong (and it is not the case), your flasher should patch the image. So you have issues with your SD card or your dump name or size. So, folow [MENTION=118]kozarovv[/MENTION] tip or do this: Bad Request to show file extentions.
Then ensure your file is not bkpps3.bin.bin

Concerning your PS3DumpChecker issue, if you have the latest hashlist and still have "No" into "Pre-Patched" box, ensure "Enable hash check" option is checked:
3CUpj6Z.png
 
Last edited:
im going to do a thorough check of my flasher, change the ribbon ..etc just to double check

I have another 2501 series model I just got and its on 4.66 so Im going to try the downgrade with the same equipment and see what happens. the other 2 i did were 2001A's . but since the one im having problems with is a 2501A on 4.75 and this one is on 4.66 then I should have a good chance to eliminate a couple of things from the equation

I will let you know
 
@kozarov, Również witam! (Welcome also!)
Yes, I have tried this app PyPS3tools few day ago and in my opinion its less userfiendly for me, but anyway also good app.
 
Hey Littlebalup... I FINALLY figured out the issue! It took forever for my new E3 flashers to get here. After extensive testing I narrowed down the exact problem...and yeah it was my end!

The top part of the Flasher where the ribbon goes connected to, was worn out. At least one or more of the prongs inside of that little port are worn out. I have 2 new flashers and a total of 5 ribbons (3 new) and did all kinds of tests until it was clear that was issue!

After doing about 150 ps3's I just took it for granted that it couldn't be the flasher ...all that disconnecting/connecting of ribbons obviously wore it out. But the issue was the flasher communicating with the ps and it would happen even with new ribbons but with the new flashers everything was like butter again!

So thanks for your help and maybe that info can help someone else who comes across that problem similar or the same as mine. I apologize for doubting your work man!!!!! The only tiny issue is that The dump checker still doesn't show 4.75 dumps that have been patched as "patched" in the upper right corner and asks to patch them again, but that isn't a big deal as they are indeed patched and work freakin great!

thanks again man for the speedy attention and concern you showed to help me out!
 
Zoilus said:
Hey Littlebalup... I FINALLY figured out the issue! It took forever for my new E3 flashers to get here. After extensive testing I narrowed down the exact problem...and yeah it was my end!

The top part of the Flasher where the ribbon goes connected to, was worn out. At least one or more of the prongs inside of that little port are worn out. I have 2 new flashers and a total of 5 ribbons (3 new) and did all kinds of tests until it was clear that was issue!

After doing about 150 ps3's I just took it for granted that it couldn't be the flasher ...all that disconnecting/connecting of ribbons obviously wore it out. But the issue was the flasher communicating with the ps and it would happen even with new ribbons but with the new flashers everything was like butter again!

So thanks for your help and maybe that info can help someone else who comes across that problem similar or the same as mine. I apologize for doubting your work man!!!!! The only tiny issue is that The dump checker still doesn't show 4.75 dumps that have been patched as "patched" in the upper right corner and asks to patch them again, but that isn't a big deal as they are indeed patched and work freakin great!

thanks again man for the speedy attention and concern you showed to help me out!
Click to expand...

Thanks for the report :)

For the small issue you mentionned, please,refer to this post : http://www.psx-place.com/forum/downgrading/ps3dumpchecker-255-post17142.html#post17142
That will solve it for sure.
 
Build 485 released with support of 4.76 firmware:

Build 485 2015-09-06:
  • Changed: The embedded 4.75 patch replaced by a 4.76 patch build from the FERROX 4.76 CEX custom firmware CoreOS.
  • Added: OFW and Patched 4.76 ROS hashs.
Click to expand...

Thanks [MENTION=56]Alexander[/MENTION] ;)
 
You must log in or register to reply here.

Similar threads

Back
Top