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

No0bZiLLa said:
@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
Click to expand...

Now we don't know wich ROS is active in syscon. It certainly switched when he tryed 3.55 downgrader. Maybe why he get a corrupted data error.
So, First of all I think it would be nice to fill both ROS of the dump with a clean DEX CoreOS. Latest Rebug D-REX as exemple. Then flash patched dump and try a 3.55 downgrader again.
 
[MENTION=11]No0bZiLLa[/MENTION] that one gives 'data is corrupt' message as well. I have noticed the error message has change from 8002f2c5 to o8002f225 and one time it was something else as well. I think reseatting the bdrom ribbon caused this but not sure.

Tried to reflash original fw again with tristate tied to ground this time, same results on trying to update.

Would it be possible to use a dex fw donor(4.78?) and and then use PyPS3rebuilder to create a new fw to flash? Would that work if the fw is spoofed on this original?
 
littlebalup said:
Now we don't know wich ROS is active in syscon. It certainly switched when he tryed 3.55 downgrader. Maybe why he get a corrupted data error.
So, First of all I think it would be nice to fill both ROS of the dump with a clean DEX CoreOS. Latest Rebug D-REX as exemple. Then flash patched dump and try a 3.55 downgrader again.
Click to expand...

littlebalp, I don't have a cech-2001 with mobo dyn-001 around currently too get a dex donor dump from. Would it be possible to use an cech-2501x for the dex donor?

If not does anyone here have one they could compile for me if I send them my dump?
 
darknezz19 said:
littlebalp, I don't have a cech-2001 with mobo dyn-001 around currently too get a dex donor dump from. Would it be possible to use an cech-2501x for the dex donor?

If not does anyone here have one they could compile for me if I send them my dump?
Click to expand...

Just send me your dumps and I will patch them for you.
 
[MENTION=29]Joonie[/MENTION], don't see a way to PM you here. Just sent you a friend request, will I be able to PM you once we are friends?
 
Sending PM now.

EDIT: [MENTION=29]Joonie[/MENTION] still don't see an option to send a PM. Maybe you can send me one and I can reply?
 
Last edited:
darknezz19 said:
Corrupt data. Guess it's time to just throw the towel in on this, thanks for helping anyway everyone.
Click to expand...

There is a one thing that bothers me. I'll send you couple more stuff

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...


I totally missed this, your syscon is already on 3.55, so patching dumps with 4.XX coreOS won't help at all.

check your mail now
 
Last edited:
[MENTION=29]Joonie[/MENTION], how did you patch it? what was the problem? what caused the downgrader not to work?
 
[MENTION=11]No0bZiLLa[/MENTION] when i got the new pup Joonie provided to install(not sure exactly which it was) the ps3 booted to a blank screen again. This time though I tried to boot again with a second beep and xmb loaded. May or may not have tried to boot after a second beep with the first downgrader install, don't think I did though.
 
honestly, even if you had gotten it working, i was expecting it to boot into rsod... but glad it worked out for you :)
 
You must log in or register to reply here.

Similar threads

Back
Top