[na0339]

Hey all. I have a NAND system that I got downgraded back to 3.55. I didn't realize that I couldn't install kmeaw 3.55 right after the downgrade due to the checks, and I got a YLOD as a result.

The strange thing is, after multiple tries, I am sometimes (though seldomly) able to boot into the system. When I check the FW, it reads 3.55 (no CFW). I'm wondering if there's a way to salvage the system without having to ship it and pay to get it flashed again. I tried installing the Rogero 3.5 CFW one of the times I got it up and running, but the system reset about 80% of the way through the install and then the YLOD returned. Any thoughts? Thanks!

[baileyscream]

Originally Posted by na0339 Hey all. I have a NAND system that I got downgraded back to 3.55. I didn't realize that I couldn't install kmeaw 3.55 right after the downgrade due to the checks, and I got a YLOD as a result. The strange thing is, after multiple tries, I am sometimes (though seldomly) able to boot into the system. When I check the FW, it reads 3.55 (no CFW). I'm wondering if there's a way to salvage the system without having to ship it and pay to get it flashed again. I tried installing the Rogero 3.5 CFW one of the times I got it up and running, but the system reset about 80% of the way through the install and then the YLOD returned. Any thoughts? Thanks!

strange that it "sometimes" boots
are you sure its a de-hash fail that you have?
its sounds more like a true ylod that you have may just need to re-flow to solve this.

but if it is a de-hash fail that you have then you should just need to send it back to who downgraded it for you to get it de-hashed.

when you recived it back did it have genuine firmware on (did it boot with ps3 on screen)
or was it rogero's cfw? (did it boot with rogero on screen?)

[na0339]

Originally Posted by baileyscream are you sure its a de-hash fail that you have?

I'm not, but based on the forums I've been reading, it seemed like I was a perfect candidate for it. I (naively) tried installing kmeaw twice after the I got it shipped back to me and both times it YLOD'd right at the end of the update process. Same thing after I tried Rogero, though after that I've been too frustrated to try to get it to boot again, so who knows if that's even possible anymore.

Originally Posted by baileyscream when you recived it back did it have genuine firmware on (did it boot with ps3 on screen) or was it rogero's cfw? (did it boot with rogero on screen?)

Genuine firmware boot.
************* [ - Post Merged - ] *************

Originally Posted by baileyscream are you sure its a de-hash fail that you have?

I contacted the guy that did the downgrade for me and he said that he dehashed with the reFSM method. I also did a md5 checksum on my PUP to verify I was using an unmodified file, and that was fine. So I guess I was mistaken that it was me trying to install kmeaw. I don't know anything about hardware failures and YLOD -- if it's just a solder problem, is it odd that it always fails at the same time (whenever I try to update)?

[baileyscream]

Originally Posted by na0339 I'm not, but based on the forums I've been reading, it seemed like I was a perfect candidate for it. I (naively) tried installing kmeaw twice after the I got it shipped back to me and both times it YLOD'd right at the end of the update process. Same thing after I tried Rogero, though after that I've been too frustrated to try to get it to boot again, so who knows if that's even possible anymore. Genuine firmware boot. ************* [ - Post Merged - ] ************* I contacted the guy that did the downgrade for me and he said that he dehashed with the reFSM method. I also did a md5 checksum on my PUP to verify I was using an unmodified file, and that was fine. So I guess I was mistaken that it was me trying to install kmeaw. I don't know anything about hardware failures and YLOD -- if it's just a solder problem, is it odd that it always fails at the same time (whenever I try to update)?

yes its odd
if its de-hash fail then it shouldnt boot.
it should turn on then beep & flash yellow or red then turn off with the red light blinking constantly untill you unplug the ps3.

you shouldnt be-able to boot it to put any firmware on this is why its called a "soft brick"

ylod can happen at the same spot.
ie when cool the solder is touching but when the ps3 warms up it breaks the solder creating the ylod.

[Freesty]

i have problem on slim ps3 with installing any fw after downgrade, it came on 37% and then power off and brick on every fw, after this i remarried bd with 3.55 remarried mode and from then everything was good.

[baileyscream]

Originally Posted by Freesty i have problem on slim ps3 with installing any fw after downgrade, it came on 37% and then power off and brick on every fw, after this i remarried bd with 3.55 remarried mode and from then everything was good.

can you post a link to the remarry firmware for the o/p to try with his.
i doubt this is the problem but i wont hurt to try

[Freesty]

http://www.mediafire.com/?fx8n72n2e2q94vq

and you need to download ofw 3.30 http://www.ps3devwiki.com/files/firm...0/PS3UPDAT.PUP
and i still cant believe why i have this problem but...