[Mr.Dutch]

Originally Posted by nishat i will post a good picks of my ps3 power connector but could you tell me what u will do with it.I solder the wire to trestate to ground what will happen if i turn it on ps3.

if you turn the ps3 on it won't shut down. (the ps3 will halt on bootup) , but this is mainly used if you have a flasher installed.

btw, i mean the power/eject board connector, it's on the front of the ps3 (right side)

i'm interrested in the hardware part of the ps3.

[nishat]

I dont have the good camera right now i will sure post the pic tomorrow i solder the wire from tristate to grnd and my ps3 turns on but no video and audio i tried to dump also but the same error i m getting what i have to do now

[Mr.Dutch]

maybe @baileyscream or @playerkp420 have some bright ideas.

[baileyscream]

Originally Posted by nishat I dont have the good camera right now i will sure post the pic tomorrow i solder the wire from tristate to grnd and my ps3 turns on but no video and audio i tried to dump also but the same error i m getting what i have to do now

if it was stuck in an update loop then i'd say format the hdd in a pc
but this is a bad update. as the update is checked before its installed then the ps3 must have been turned off during the update.

there is nothing i can think of to fix this.

you could try to ground the tristate then dump, verify then patch as though your going to downgrade and see if it boots (your model wont go to 3.55 so dont install 3.55cfw or 4.30v2cfw)

then if it boots up then re-update to 4.31ofw

[playerkp420]

Originally Posted by baileyscream if it was stuck in an update loop then i'd say format the hdd in a pc but this is a bad update. as the update is checked before its installed then the ps3 must have been turned off during the update. there is nothing i can think of to fix this. you could try to ground the tristate then dump, verify then patch as though your going to downgrade and see if it boots (your model wont go to 3.55 so dont install 3.55cfw or 4.30v2cfw) then if it boots up then re-update to 4.31ofw

How do you know it won't go to 3.55? Did I miss the manufacturing date being posted?

[baileyscream]

Originally Posted by playerkp420 How do you know it won't go to 3.55? Did I miss the manufacturing date being posted?

no
it has to go as an assumption due to not being able to run minvercheck

from wiki:-
these can go to 3.56
CECH-25xx (JTP-001) with 3.56 from factory - datecode 1A (rare)
CECH-25xx (JSD-001) with 3.56 from factory - datecode 1B (common)
CECH-25xx (JTP-001) with 3.56 from factory - datecode 1B (common)

but these go to 3.60
CECH-25xx (JSD-001) with 3.60 from factory - datecode 1B
CECH-25xx (JTP-001) with 3.60 from factory - datecode [N.A.]

even finding out what board is in it wont help knowing what its min ver is

without the ability to run min ver there is going to be a big risk of making things worse

[haz367]

u can notice at the (already known for rlod/ylod > either on flash or hardware for rlod) leds here..that there are more possible brick types, with one its longer holding powerbutton before it goes off, another rlod it goes as soon as hitting the button, here beeps with no led at all? when doing a firmware update..the update loop before could be the HDD for sure..but if did not mess with it..it should not loop, could also be the coreos..correct me if wrong..i think its also caused by corrupt..or how u like to name it...

in this case would buy e3 flasher if NOR, dump the flash, verify if all per console infos are intact and patch it either with "355"(if minverchk is <3.55) else use "430 three musk patches" and do the downgrade

the firmware update atleast cannot cause any "pck" corruption so must be possible to fix with patches..

[playerkp420]

Originally Posted by baileyscream no it has to go as an assumption due to not being able to run minvercheck from wiki:- these can go to 3.56 CECH-25xx (JTP-001) with 3.56 from factory - datecode 1A (rare) CECH-25xx (JSD-001) with 3.56 from factory - datecode 1B (common) CECH-25xx (JTP-001) with 3.56 from factory - datecode 1B (common) but these go to 3.60 CECH-25xx (JSD-001) with 3.60 from factory - datecode 1B CECH-25xx (JTP-001) with 3.60 from factory - datecode [N.A.] even finding out what board is in it wont help knowing what its min ver is without the ability to run min ver there is going to be a big risk of making things worse

But checking the manufacturing date on the bottom of the PS3, will narrow it down a lot.

But yeah, I would do what @haz367 says. If it is 3.56 min, use 3 musk.

[baileyscream]

Originally Posted by playerkp420 But checking the manufacturing date on the bottom of the PS3, will narrow it down a lot. But yeah, I would do what @haz367 says. If it is 3.56 min, use 3 musk.

i dont see how anymore.

now the wiki has changed the "rule"
if you look
JTP-001 boards with both 1A and 1B can be 3.56 but its [NA] for 3.60 so that says "any date code" to me

JSD-001 with 1B (the only date code on this board on 25** model's) can have either 3.56 or 3.60

so to me the date code is no longer a way to tell the min firmware.
************* [ - Post Merged - ] *************

Originally Posted by haz367 u can notice at the (already known for rlod/ylod > either on flash or hardware for rlod) leds here..that there are more possible brick types, with one its longer holding powerbutton before it goes off, another rlod it goes as soon as hitting the button, here beeps with no led at all? when doing a firmware update..the update loop before could be the HDD for sure..but if did not mess with it..it should not loop, could also be the coreos..correct me if wrong..i think its also caused by corrupt..or how u like to name it... in this case would buy e3 flasher if NOR, dump the flash, verify if all per console infos are intact and patch it either with "355"(if minverchk is <3.55) else use "430 three musk patches" and do the downgrade the firmware update atleast cannot cause any "pck" corruption so must be possible to fix with patches..

but if his min version is 3.60 then he cannot goto 3.55 or 4.30cfw
it will make it worse.

if he dumps his nor then his min version is at offset 2F077 & FC0002 i think but its been awhile since i did it this way so i'm not 100%

[haz367]

Originally Posted by baileyscream i dont see how anymore. now the wiki has changed the "rule" if you look JTP-001 boards with both 1A and 1B can be 3.56 but its [NA] for 3.60 so that says "any date code" to me JSD-001 with 1B (the only date code on this board on 25** model's) can have either 3.56 or 3.60 so to me the date code is no longer a way to tell the min firmware.

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