[baileyscream]

Originally Posted by monu1232009 ok sir bailey

these are no good. do you have anymore anywhere?

[haz367]

the bkpps32 haha never seen that bfore 80mb files..lol...

for bkpps3 although it is same console = identical metldr files it is bad..empty bootloader_0(bad clipping) and empty ros1 but noticed in ros0 a firmware of "40400000"
a downgrader.pup maybe like 425to355.pup used here?, anyway it shows 4.40...with those firmwares it ask for that in recovery when u install 355 right

for bkpps30 and bkpps31.bin(4.25OFW old - 355 CFW? installed)
well only cvtrm(BD stuff??!!) is different but from the same console and should be used for restoring if "no hardware" failures

this "cvtrm" stuff diff doesn't prevent to unbrick the ps3, maybe for nands/bd playback? not sure there..cvtrm is something with BD drive seen it it my own backups..can't really say there tho..

both dumps(30/31)can be used if u ask me and are valid per console stuff, patch the dumps with 355coreos/three musk patches 4.30) and restore?! not saying it works but if firmware on flash is corrupt, with this it overwrites and do the normal 355 downgrade steps

it's this console

0B
CECH-25xx (JSD-001) with 3.56 from factory - datecode 0D
CECH-25xx (JTP-001) with 3.56 from factory - datecode 1A 
E9 60 	0E 92 	2F570 	2F 53 	2F 53 	OK

goodluck on fix

[monu1232009]

Originally Posted by haz367 the bkpps32 haha never seen that bfore 80mb files..lol... for bkpps3 although it is same console = identical metldr files it is bad..empty bootloader_0(bad clipping) and empty ros1 but noticed in ros0 a firmware of "40400000" a downgrader.pup maybe like 425to355.pup used here?, anyway it shows 4.40...with those firmwares it ask for that in recovery when u install 355 right for bkpps30 and bkpps31.bin(4.25OFW old - 355 CFW? installed) well only cvtrm(BD stuff??!!) is different but from the same console and should be used for restoring if "no hardware" failures this "cvtrm" stuff diff doesn't prevent to unbrick the ps3, maybe for nands/bd playback? not sure there..cvtrm is something with BD drive seen it it my own backups..can't really say there tho.. both dumps(30/31)can be used if u ask me and are valid per console stuff, patch the dumps with 355coreos/three musk patches 4.30) and restore?! not saying it works but if firmware on flash is corrupt, with this it overwrites and do the normal 355 downgrade steps it's this console 0B CECH-25xx (JSD-001) with 3.56 from factory - datecode 0D CECH-25xx (JTP-001) with 3.56 from factory - datecode 1A E9 60 0E 92 2F570 2F 53 2F 53 OK goodluck on fix

thank you so much to bring me a hope...

i did not understand about this patch {355coreos/three musk patches 4.30).
will you please patch it for me {bkps31.bin}.

and i have also 16mb bkps32.bin should i post its link?

please help me.

[haz367]

let's assume the norflash is corrupt, then with patched backups it can be fixed/overwritten>downgrade, anyway "weird dumps" tho and not knowing for real what happend there + knowing the firmware versions and the strange 80mb extracted "bkpps32.bin" is that one somehow compiled by urself?? or something...

here are patched backups for 355 and 4.30(the 4.30>E3 only? u have to lookup howto that one!)
patched on both bkpps30.bin and bkpps31.bin, because "cvtrm" is only different on them, this should not prevent unbricking, then again what it does..beats me

first go for the "355" way ofcourse, the 4.30 should also work anyway did that one for the fun , both are correctly patched for E3 flasher use and ofcourse USE AT UR OWN RISK, don't come crying..lol...goodluck

http://rghost.net/42132245

[Mr.Dutch]

Originally Posted by haz367 both are correctly patched for E3 flasher use and ofcourse USE AT UR OWN RISK, don't come crying..lol...goodluck

so he should use the e3 flasher? i know he later on used e3 linker instead...

don't want anymore confusion.

[baileyscream]

Originally Posted by monu1232009 thank you so much to bring me a hope... i did not understand about this patch {355coreos/three musk patches 4.30). will you please patch it for me {bkps31.bin}. and i have also 16mb bkps32.bin should i post its link? please help me.

there is a hell of alot more wrong than what haz has pointed out.
all your dumps have at 1 point or another bad sections
i am mapping them all down.
hopefully i can take good sections from each dump (not the bkpps3 as thats worse than seeing my grans dump)
i'm about 2/3rds way through these dumps so DO NOT DO ANYTHING untill i have finnished.
if you do then sod it i'm out of this thread.
i said i would be a while so be paitiant. this is what got you in this situation in the first place.

and did you say a few posts back that you have ANOTHER dump?
i said i want ALL your dumps
upload it if there is another

************* [ - Post Merged - ] *************

Originally Posted by Mr.Dutch so he should use the e3 flasher? i know he later on used e3 linker instead... don't want anymore confusion.

the E3 flasher is the actual device
the E3 linker is to solder wires to the ps3 test points
the E3 clip clips onto the NOR chip

you will get the hang of all this soon bud

[haz367]

ah..ok..my bad if he's using e3linker/52?wires, bad wire?

i saw "bkpps3.bin and assumed the "E3flasher/clip" instead, the bkpps3.bin works on linker&clip ofcourse ..with "e3linker"is there a bad sector? from a bad wire/cold solder or something...can't help there

the dumps "per console info" atleast is intact, and as euss always pointed out and it works, if the NOR flash firmwares are corrupt, just patch ofw, whatever dump with 355coreos and do the usual downgrade

the dumps are correclty patched, no harm there, he could try with e3clip if he still have it, anyway goodluck there

Originally Posted by Mr.Dutch so he should use the e3 flasher? i know he later on used e3 linker instead... don't want anymore confusion.

[monu1232009]

Originally Posted by baileyscream there is a hell of alot more wrong than what haz has pointed out. all your dumps have at 1 point or another bad sections i am mapping them all down. hopefully i can take good sections from each dump (not the bkpps3 as thats worse than seeing my grans dump) i'm about 2/3rds way through these dumps so DO NOT DO ANYTHING untill i have finnished. if you do then sod it i'm out of this thread. i said i would be a while so be paitiant. this is what got you in this situation in the first place. and did you say a few posts back that you have ANOTHER dump? i said i want ALL your dumps upload it if there is another ************* [ - Post Merged - ] ************* the E3 flasher is the actual device the E3 linker is to solder wires to the ps3 test points the E3 clip clips onto the NOR chip you will get the hang of all this soon bud

please trust me i will not do anything to my console untill you tell me sir bailey even it takes a week or month .

i am asking to sir haz367 for my 16mb bkpps32.bin because he said he has bkpps32.bin of 60mb . is that ok i dont have any new dumps i have only 4 and i already post it. please understand my broken english.

[playerkp420]

@baileyscream

I have this dump from him. I keep looking through it, and I must be missing something. But I believe it is valid.

If I had dumped it while doing a console, I would believe it would work for downgrade or unbrick.

[baileyscream]

damn!!!!!! bloody deleted it all instead of saving it!!!!

this is a quick check. i did have what was wrong and a propper comparison but this will have to do.

click to open

bkpps30.bin

DEADBEEF FACEOFF headder at offset 10
IFI at offset 200
table at 400 - 600 is correct
FACEOFF FACEOFF headder at offset f00010 .............bad everything is doubbled up here!!!!!
(but good on bkpps31)

asecure_loader (folder)
> metldr: size E9 60 correct for CECH-25xx (JSD-001) & CECH-25xx (JTP-001) boards

ros0 (folder)
> aim_spu_module.self
> creserved_0
> default.spp
> emer_init.self
> eurus_fw.bin: *****differences******
> hdd_copy.self
> lv0
> lv0.2
> lv1.self
> lv2_kernal.self*****differences*****
> manu_info_spu_module.self
> mc_iso_spu_module.self
> me_iso_for_ps2emu.self
> me_iso_spu_module.self
> pkg.srvk
> prog.srvk
> sb_iso_spu_module.self
> sc_iso.self******differences******
> sdk_version
> spp_verifier.self
> spu_pkg_rvk_verifier.self
> spu_token_processor.self
> spu_utoken_processor.self
> sv_iso_for_ps2emu.self
> sv_iso_spu_module.self*****differences*****

ros1 (folder)
> aim_spu_module.self
> appldr
> creserved_0
> default.spp
> emer_init.self
> eurus_fw.bin
> hdd_copy.self
> isoldr
> lv0
> lv1.self*****differences******
> lv1ldr
> lv2_kernel.self*****differences*****
> lv2ldr
> manu_info_spu_module.self*****differences*****
> mc_iso_spu_module.self
> me_iso_spu_module.self
> sb_iso_spu_module.self*****differences*****
> sc_iso.self
> sdk_version
> spp_verifier.self
> spu_pkg_rvk_verifier.self
> spu_token_processor.self
> spu_utoken_processor.self
> sv_iso_spu_module.self

bootloader_0: size 2F570 & 2F 53 at 02 & 12 correct for CECH-25xx (JSD-001) & CECH-25xx (JTP-001)boards

cCSD same as bkpps31 (perconsole data but full mostly by FF FF FF etc)

cISD: same as bkpps31 (includes perconsole data) and part of your serial number that can be checked xx-2745934-xxxxxxx-chech-2xxx (if i have figured it out right)

cvtrm 40000 in lenth.88.02% is FF filed. but has different data compaired to bkpps31

eEID: same as bkpps31 (includes encripted per console data)

trvk_pkg0 SCE headder present and same as bkpps31

trvk_pkg1 SCE headder present and same as bkpps31

trvk_prg0 SCE headder present and same as bkpps31

trvk_prg1 SCE headder present and same as bkpps31

@monu1232009 can you flash the bkpps31 onto your ps3 twice then empty your sd card and make a new dump
re-name that dump "linker" or something.
then can you connect your nor clip and dump again (you dont need to de-solder the linker) and rename this one "clip1"

then upload them please.

i am still thinking a wire is not connected propperly OR there are just difficult segments on the NOR chip that are being a pain to write to / read from (this is why i say to flash the dump to ps3 twice)

@playerkp420 thanks for the dump.
its the same as the bkpps31 that he uploaded in this thread.
but it was good to get a hold of it.