[Bigbones87]

@Smart60 I mean make sure the e3 ribbon cable is seated good on the ps3 nor, and make sure the other end of the ribbon is clipped to the e3 flasher board good. In other words, make sure both ends or seated good. If you can get the e3 ribbon seated good, then you can get a new bios dump from the console. As long as the per console data is there, we can fix it. First things first, get the clip seated properly to get it doing a bios dump. Then we can check the bios dump for validity and then patch it, then you can flash it back to the console, as long as it contains the per console data. Then you won't have to worry about the back up you deleted. Good luck and post back after you get the e3 backing up your bios.

[Smart60]

yeah... understood sir.

[Bigbones87]

@Smart60 you don't have to call me sir, I am only trying to help. I am not trying to boss you around or anything. If i seem like i am being rude or you dont like what i am saying, then tell me and I will leave it alone. I do remember you telling another user that his ps3 was done for and I told you not to tell people their Ps3 is trash unless you have the knowledge to back it up. Most things are fixable with the right knowledge and equipment. Anyway, let me know if you get a bios dump and I can help you further.

[Smart60]

Do not take it seriously... man. i just was excited, and i'm really sorry if you don't like what i'm calling you. actually i praise the people that always can help me out and whatever i call them..I love...sir..etc so don't misunderstand me bigbones.

we are a beginner and you're a senior, plz we need you.

[D Dush]

When you install a cfw over a downgrade cfw, you soft brick or semi brick.

Hi, I think I have one of these & hope someone can help. I actually downgraded a PS3 Slim(Cech2002A) successfully a few months back for a friend from 3.70 to 3.55CFW. Since then he has put TB CFW then decided to go back to 3.55 CFW(went OFW 1st I'm led to believe but not 100% on that).

Anyway, now when u turn it on you get no video/audio & it stays on for aboout 8 seconds, LED goes yellow then beeps 3 times & flashes red until you press the power button again, to go to solid red.

I only now read about the de-hash which I dont think I did during the downgrade(months ago), so I',m guessing this is why its now bricked/semi-bricked? so kinda feel responsible for the brick.

What is the best course of action to un-brick the ps3? I'm hoping not having to resolder the progskeet & reflash. Was hoping for a USB method if it exists at all.I also have backups of his NOR/downgrade.bin if that helps.

BTW, I have tried to get it into FSM via dongle but the ps3 just shuts down as mentioned above.
Appreciate any help.

[D Dush]

Someone?Anyone?

[marcin888888]

do u have bios backup of this ps3?if no u can trash it

[sbmotoracer]

What cfw did you put him when you originally downgraded?

if its one where the lv1 check is removed then thats why it worked the first time.

Since you still have his original ps3 dumps, then your going to have to reatch the progskeet and dehash his system.

Originally Posted by D Dush Hi, I think I have one of these & hope someone can help. I actually downgraded a PS3 Slim(Cech2002A) successfully a few months back for a friend from 3.70 to 3.55CFW. Since then he has put TB CFW then decided to go back to 3.55 CFW(went OFW 1st I'm led to believe but not 100% on that). Anyway, now when u turn it on you get no video/audio & it stays on for aboout 8 seconds, LED goes yellow then beeps 3 times & flashes red until you press the power button again, to go to solid red. I only now read about the de-hash which I dont think I did during the downgrade(months ago), so I',m guessing this is why its now bricked/semi-bricked? so kinda feel responsible for the brick. What is the best course of action to un-brick the ps3? I'm hoping not having to resolder the progskeet & reflash. Was hoping for a USB method if it exists at all.I also have backups of his NOR/downgrade.bin if that helps. BTW, I have tried to get it into FSM via dongle but the ps3 just shuts down as mentioned above. Appreciate any help.

[D Dush]

I initially put KMEAW 3.55 No-check & all worked ok, but I guess he has put the standard KMEAW fw afterwards & hence why its bricked.

So no easier method than hooking up the Progskeet again?....damm!
Thanks for the replies.

[D Dush]

Apologies for bumping this thread again but thought it appropriate here.

I have finally got around to attaching the progskeet with the original wiring from the 1st(successful) downgrade so wiring/position of progskeet etc is in identical position as to what worked 1st time around(as well as using same version of Winskeet(WinSkeet40000_111004),preset to Spansion P90. The only difference now is I need to use an external power source(3.3V) to power my NOR & progskeet(via R7 closed/switched) as the ps3 is bricked & wont stay on long enough. Doing this method gives me 100% verification errors,even at 4bytes write. have tried following things with same result:
-Powering Progskeet only via USB
- Using this method(http://www.ps3devwiki.com/wiki/Talk:...st_safe_method)
- different Halt times(5-10sec)
-Thicker gnd & VCC wire
- varying VCC from 3.3V - 3.4V
My questions are:
1)Am I doing something obvisouly wrong?
2) Is the Halt procedure required if powering NOR via external power supply?
3) I am using my good 'downgrade.bin'(from previous succesful flash) to flash..should I not be doing this 1st?
4)Is there any other way to know verify will fail as I'm writing at 8bytes which takes 1hr just to find out it fails each time.

Thanks for any help.