[baileyscream]

Originally Posted by haz367 hey baileyscream, think euss never updated that part > JSD-001/2504-1a/3.50minverchk, although i passed it to him after asking him "howto" make sure = dump/verify for metldr revision.. but that one..must be one of the latest "hackable" ones = cech2504B - Datacode 1A - JSD-001 - minverchk 3.50 for the 3.60 not sure there..arent those "metlldr2" anyway?! without knowing..he should "dump and verify" for metldr 1 or 2.. but there excist 25xx - jsd-001 with datacode 1A

yes
good point on the metldr2
that will be the ideal and quick and correct way to go here.

and the date codes used to be more clear then they are now i'm sure they were??

[haz367]

yes 3.60 = metldr 2 right..so dump and check the offset for magic or no magic..
nvm..the rest...

[playerkp420]

Without the date code, we don't know if it is even 1A or 1B. I have many CECH-25xx that are date code 0C min. praxis 3.40 or date code 0D min. praxis 3.50.

[haz367]

edited my previous post..mixed TargetID withdatacode...anuway

without the datacode? its on the box..back for phats..botton for slims

he can check here and be 99% correct on wich ps3 it is..datacode wise..
http://www.ps3devwiki.com/wiki/Date_Codes

this list shows the 1A datacode and its actual praxis:

1A 	January, February, March / 2011 	Sometimes 	3.56, 3.60 	3.55 or 3.56

this one also has a 3.50 actual praxis - JSD001

[playerkp420]

I think you guys are making this way to confusing. I don't understand why you are assuming it is date code 1a or 1b?

I just reread the thread, and no where did the OP say he even tried to run min ver check. Let alone not be able to run it.

This brick is most likely from a bad update. The download was corrupted, so the firmware tried to install was corrupted.

@nishat can you please confirm your manufacturing date? It is on the black sticker on the bottom of the PS3.

If it is not metldr 2, it can be fixed with a flasher.

[nishat]

My ps3 model no is 2508A and the date code 0D

[playerkp420]

Originally Posted by nishat My ps3 model no is 2508A and the date code 0D

Thank you. So we can squash the metldr 2 and date code talk. Your PS3 is capable of going to 3.55.

I believe your PS3 installed a corrupt firmware update. Or was shut off during an update, and is what caused the brick.

You may be able to fix it with a hardware flasher. Or pay someone with a flasher to fix it for you.

Unless there is another issue that we don't know about.
But since you were installing an update when this happened, I bet it is a bad flash.

[nishat]

I have E3 flasher so i can repair it with it i tried to dump but it give me an error that that some ps3 did not work properly check that the ps3 is working fine it may be that nor flasher did not seated properly.

[Dartban214]

Originally Posted by playerkp420 Thank you. So we can squash the metldr 2 and date code talk. Your PS3 is capable of going to 3.55. I believe your PS3 installed a corrupt firmware update. Or was shut off during an update, and is what caused the brick. You may be able to fix it with a hardware flasher. Or pay someone with a flasher to fix it for you. Unless there is another issue that we don't know about. But since you were installing an update when this happened, I bet it is a bad flash.

I was going to say it may be a bad flash.

But if it was a bad flash wouldn't it be near impossible to fix? I mean of course there are ways to try(Doesn't hurt) but it's slim.

If he can get a NOR dump that's awsome but if this is a brick than there's basically no way he can fix unless he can patch IF IF he's lucky. Well that or if he get's someone elses dump.

[nishat]

So i can say that i did not seated the nor flasher properly i will try it again and let u all know.
************* [ - Post Merged - ] *************
Did i have to format the hdd before dumping the bkpp3
************* [ - Post Merged - ] *************
Did i have to format the hdd before dumping the bkpp3