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

RELEASE v0.3

Tools are updated to v0.3:

Changelog v0.3, (03 nov 2015)

PyPS3checker:
Fixed bug displaying the whole dump data in console if reversed check fails.
Added alternate conditions to determine if dump is reversed or not.
Various minor wording corrections.
Added one CECHBxx SKU check entry (NAND).
Added none-wifi machines entry in cISD2 check (NOR & NAND).

PyPS3patcher:
Various minor wording corrections.

PyPS3rebuilder:
Various minor wording corrections.
Click to expand...

https://github.com/littlebalup/PyPS3tools
 
Have a ps3 that didn't have a hard drive and when trying to install a new one it asks for 2.70 at least but can't find the update it says. There's something wrong because fw was dumped and validate says ROS0 and ROS1 have bad hashes after multiple same dumps.

Now i tried to take all the console specific areas and hex them into a donor firmware with the same model and mobo model. The dump is of a 4.78 if that matters. When I try to flash to donor it just beeps 3 times at me. Am I doing something wrong? Validator says my donor is good now so not sure.

Guess we are supposed to use this nice tool PyPS3tools for stuff like this, just found it after trying to manually hex.

Would you just run the pyps3rebuilde with the 'perfw' command to copy just the per console stuff? Is that all I should need? I tried that but still got 3 beeps on start up.
 
Last edited:
what model ps3 is this? what firmware version is in original dump?

sounds like it might be converted to debug. look at 2f075 in hex, if it is 82 then you prob flashing a retail firmware to a debug console
warning: dont paste that data here or publicly anywhere.

edit: go ahead and flash original working dump back to the console. tell us what firmware versions are in ros0 and ros1
 
Last edited:
No0bZiLLa said:
what model ps3 is this? what firmware version is in original dump?

sounds like it might be converted to debug. look at 2f075 in hex, if it is 82 then you prob flashing a retail firmware to a debug console
warning: dont paste that data here or publicly anywhere.

edit: go ahead and flash original working dump back to the console. tell us what firmware versions are in ros0 and ros1
Click to expand...

After checking that address you are right about it being a dex firmware originally and my donor being cex.

Here are those versions from the original semi bricked firmware.

ROS0
421.000

ROS1
450.000

EDIT: This is a CECH-20xx (DYN-001) Minimum version 2.70 as well is the donor.
 
flash original dump back, use dex 355 downgrader from recovery, then update to latest dex cfw, preferably rebug :)
then you can go back to cex if you wish, or just stay dex
 
Last edited:
Spoke too soon. 3.55 dex downgrader finished and rebooted to a blank screen. Tried to flash original FW back and just update straight to latest Rebug D-Rex but ps3 says the file is corrupt.

When you said update to 3.55 downgrader through service menu is that different than just what the ps3 boots to where it says 'press start and select to reinstall at least 2.70 fw?'
 
darknezz19 said:
Spoke too soon. 3.55 dex downgrader finished and rebooted to a blank screen. Tried to flash original FW back and just update straight to latest Rebug D-Rex but ps3 says the file is corrupt.

When you said update to 3.55 downgrader through service menu is that different than just what the ps3 boots to where it says 'press start and select to reinstall at least 2.70 fw?'
Click to expand...

im not to sure what the problem is tbh, which pup did you install? maybe @littlebalup or @Joonie can lend you a hand as i am busy as heck this week and dont have alot of time to give. good luck though, looks like that ps3 should be able to be saved :)

EDIT: try a different 3.55 downgrader pup, i know there are a few. give us a link to the one you tried. also, leave flasher connected to system so you can reflash the original valid dump in the case of it not successfully booting ect ect. would be much less painless
 
Last edited:
If console asked for 2.70, seems syscon is in panic. Hash issue. Console was DEX (ps3-ita 4.50) but certainly spoofed as well.
Now you installed downgrader wich is 9.99. But no boot (glod?) And we don't know qa flag status. Not easy.

So, yes first try to install a 3.55 downgrader (from recovery, both time).
If it doesn't work, maybe try the PS3 ita 4.50 DEX spoofed 9.99.
 
littlebalup said:
I agree with the fact that, first, all must be done to have a good dump. Of course. Maybe I didn't warn it clearly, you are right.
The rebuilder is a "last chance" tool for those who writen their flash without to take care they have a good dump. If by some miracles the perconsole datas are not corrupted, they can transfer them to a know valid dump.
It is not "to make it seem "good" or "valid" on a pc", it is to have well formed file tables, headers, vtrm, etc...
Click to expand...

This is a good option to have as a last resort
If I could offer a suggestion though
Could the tool only rebuild the dump if you rename the dump for example
Last resort.bin
And drop it back through the tool
That way no one can say they did not realise they were patching and flashing a bad dump
As they HAVE to rename the dump for it to do this.


Sent from my hand using Tapatalk and magic
 
darknezz19 said:
Spoke too soon. 3.55 dex downgrader finished and rebooted to a blank screen. Tried to flash original FW back and just update straight to latest Rebug D-Rex but ps3 says the file is corrupt.

When you said update to 3.55 downgrader through service menu is that different than just what the ps3 boots to where it says 'press start and select to reinstall at least 2.70 fw?'
Click to expand...

You can just trigger FSM while on 3.55 Dex downgrader then install the official DEX 3.55 fw.
 
littlebalup said:
Yes, you need python 2.
And no, I'll not make an exe. Goal is to have multi-OS simple scripts.
But it is not a big deal to install python on Windows. If you use a Teensy, you should have it.
Click to expand...

It Should work on a Raspberry Pi as well? Since it's python code, Raspberry Pi's <3 Python. Might take a minute longer (4 cores at 1ghz OC + 1gb Ram) but plus programmable GPIO's for Send/Receive Data. And couldn't you bypass the Teensy as well with just a RPi. I think the Teensy has the Same GPIO's

Could Process the NOR/NAND and Flash all in the same device, right?

PS Sorry a little late to the post :)
here's a link to some research https://www.raspberrypi.org/forums/viewtopic.php?f=44&t=16775
 
Last edited:
baileyscream said:
This is a good option to have as a last resort
Click to expand...

my main point was just that if you are not able to dump correctly, then you wont be able to write correctly. this tool is great as long as you know what your doing but can also be the demise of some poor noobs console if perconsole isnt correct. if you cant dump data correctly from any section in the flash, you ass better resolder/reseat before doing anything ;0

but like i said it is a very nice tool to have, especially if your still into downgrading mass consoles for people. i got slap burnt out on it myself lol.

i know i came off as an ******* about this tool a while ago in my earlier posts, and i apologize. i meant no disrespect to the developer [MENTION=48]littlebalup[/MENTION] he is very knowledgeable and has helped out around the scene many times. it takes alot of time and patience to script something together and make sure it works and alot of people wouldnt have even attempted it
 
Last edited:
littlebalup said:
If console asked for 2.70, seems syscon is in panic. Hash issue. Console was DEX (ps3-ita 4.50) but certainly spoofed as well.
Now you installed downgrader wich is 9.99. But no boot (glod?) And we don't know qa flag status. Not easy.

So, yes first try to install a 3.55 downgrader (from recovery, both time).
If it doesn't work, maybe try the PS3 ita 4.50 DEX spoofed 9.99.
Click to expand...

Hi littlebalu. I'm not sure what the symptoms of GLOD are but the system boots up with a green light and shows a blank lit up screen on the tv. When you say try to install the downgrader 'from recovery' is that different than the screen it asks for 2.70 with an formatted hard drive in the system?

Joonie said:
You can just trigger FSM while on 3.55 Dex downgrader then install the official DEX 3.55 fw.
Click to expand...

Joonie can I still get into FSM menu with the downgrader firmware booting a a blank lit up screen like it is? If so can I get into it without a dangle?
 
darknezz19 said:
Hi littlebalu. I'm not sure what the symptoms of GLOD are but the system boots up with a green light and shows a blank lit up screen on the tv. When you say try to install the downgrader 'from recovery' is that different than the screen it asks for 2.70 with an formatted hard drive in the system?



Joonie can I still get into FSM menu with the downgrader firmware booting a a blank lit up screen like it is? If so can I get into it without a dangle?
Click to expand...

If you don't have any dongle then you can also use rebug toolbox while on 3.55 dex cfw

Try entering recovery mode first though

Sent from my iPhone using Tapatalk
 
Last edited:
Alight so after I flashed the original firmware back the recovery menu now tells me now that all the update pups I try have 'corrupted data' with error code 8002f2c5. Did something get changed from the first dex downgrader I tried?

Petty sue this is the dex 3.55 downgrader I used.
3.55downgradePUP
 
darknezz19 said:
Alight so after I flashed the original firmware back the recovery menu now tells me now that all the update pups I try have 'corrupted data' with error code 8002f2c5. Did something get changed from the first dex downgrader I tried?

Petty sue this is the dex 3.55 downgrader I used.
3.55downgradePUP
Click to expand...

How did you flash your original firmware back? You meant you installed the FW? or you flashed your NOR FLASH dump via E3 Flasher?

I'm confused.
 
@Joonie the console had no hdd. he slapped one in it and then without knowing it, he tried flashing a repaired cex dump to a dex target id. after we figured out he did that, i told him to flash the original dump back and then use a dex 3.55 downgrader and got glod.... now he has flashed back the original dump and it is telling him corrupt data when installing pup.
@darknezz19 which pups have you tried to install? please give us links to the source threads. also make sure there is no disc in disc drive.

EDIT: see if this will work. its rogero 3.55 dex downgrader v2 : link
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top