Reball Failure, System Will Not Stay On
 

Hello Everyone,

First I want to thank everyone on this site for all of their help and great guides. Without them I would not have been able to get as far as I have. I'm hoping that once again you guys can help me get past the latest hurdle in getting this PS3 system working.

:questionmark:The Original Problem:
After downgrading to 3.55 I noticed that was getting scrambled video and that the system would sometime freeze. After this happened a couple of times the PS3 would then turn on and stay on but not display any video (symptoms of the dreaded GLOD.) This past symptom mixed with the scrambled video led me to believe that the PS3 needed a reball on the GPU.

I went ahead and sent it to ps3specialist's reball service on ebay. The service tech said the reball was a success and was able to see dead points on the GPU that the service should have fixed.

:dontknow:The New Problem:
The tech now says that the PS3 turns on and then immediately turns off (1 to 2 second delay) and does not produce any error beeps. He claims that he has "seen this issue before" and has not been able to fix it. He did a reball on the southbridge to attempt to fix it but that has made no difference.

Did this guy just screw up my motherboard with too much heat from the reball? Is there anything I can do to attempt to fix this?

Any help or suggestions would be greatly appreciated. :flowers::flowers::flowers:


Some History:
-System is a CECH-2501A that was downgraded using @baileyscream 's guide using an E3 Linker (not clip.)
-Was able to successfully downgrade to 3.55 and then upgraded to Rogero's 4.30.
-I have three dumps that I have personally verified and one that was verified using the forum here.
-I removed the linker from the motherboard and all excess solder has been cleaned up.

it turns off without any light right? , and it's always a 25xx serie , at least that's what i think,
some say the cpu need to be reballed but i just don't know....

so before it turned on but had artfacts / no picture.

had a re-ball now it shuts off.

i'd say solder is touching or he lifted some pads on the gpu

or

didnt use a propper jig and the board warped and now the gpu needs a re-ball.

either way he said it was a success so something happened after that point.

so your just waiting for a fully working ps3 to be returned.

somehow i'm affraid he allready have the ps3 back ;)

i missed this. thanks @Mr.Dutch

yes send it back

tell them it needs putting back to a working condition as they sait it was a success so it should have been returned working.

Just get your money back pal take the hit on the console my best guess is they reflowed it and not reballed it

You do need CPU reballing


Sent from my iPhone 5 using Tapatalk

Yeah, that's the crap part about it- every thread on this site and others that I've seen don't have any particular answers to the question. It does appear that this is becoming more and more of an issue- I just wish we could figure out why!
************* [ - Post Merged - ] *************
Do you mean that the CPU needs a reball or that the GPU needs to get a second reball? He said that the particular reball was a success in that he could see there were problems with the connections that should have been fixed.

Have you see instances of this before where a CPU reball has fixed this issue?

The tech still has the unit but has just asked for the transaction to be canceled and for a refund to be issued. The thing that sucks is that he got the system with an error that has been fixable and left it with one that isn't. I'm wondering if I can get him to attempt a CPU reball before he sends it back. WHo knows.

the cpu does not need reballing or even touching for that matter
it is very rare for the ps3 cpu to go

the problem is the rsx (gpu) he guy obviously reflowed it then it worked and now its gone fully glod = bad rsx if a reball dont fix it then it needs a new rsx.

reflowed with a heatgun for sure ghetto style

That is interesting. Does anyone know of anybody that provides an rsx replacement service? Does anyone else think a faulty GPU could be to blame?