PS3 CECHA00 - Questions about black screen in PS2

Hello! I'm also experiencing this issue. Got my CECHA01 Frankenstein'd with a 40nm RSX and also got a black screen when trying to play PS2 discs. Got another 40nm RSX to see if that would fix things but I still have the same issue. Black screen but I can't access the menu to go back to the XMB. Gonna replace the EE+GS and see if that will work. If not, I suspect the bridge chip or Southbridge. I will let you guys know if the EE+GS replacement is successful! Let me know if you guys have had similar symptoms and if you were able to resolve the issue.
 
RedOverlord said:
Hello guys, joining the thread sadly.

I built a CECHA00 yesterday with a 40nm super slim RSX, CELL delid, and NEC/TOKIN replaced.

I would add pics but its asking me for a picture link instead of a local file so I guess I cant.

same issue basically, when I first tested it it would launch the ps2 title to the main menu but would lock up, right now it usually only wants to boot if I reset the game. after a few moments it would also lock up.

I didnt have this issue with the previous frankenstein console I made.

im going to be investigating this board later.
Click to expand...

Hi, @RedOverlord

Since it's been a while, did you get any further about this? I've tried to contact the person who was starting doing REBALLING and such but he just went missing. So no luck for replacing EE/GS from me (no experience and I don't have the equipment...).

Kalulo24 said:
Hello! I'm also experiencing this issue. Got my CECHA01 Frankenstein'd with a 40nm RSX and also got a black screen when trying to play PS2 discs. Got another 40nm RSX to see if that would fix things but I still have the same issue. Black screen but I can't access the menu to go back to the XMB. Gonna replace the EE+GS and see if that will work. If not, I suspect the bridge chip or Southbridge. I will let you guys know if the EE+GS replacement is successful! Let me know if you guys have had similar symptoms and if you were able to resolve the issue.
Click to expand...

Hi @Kalulo24

A pleasure to see you here.

About the info you're asking for, the thread is all I've got, nothing else, as I replied to RedOverlord, the person who was starting to do reballing and such, just disappeared, he doesn't even answer to DMs... Wish I could expand this thread with more information.

Hope you'll have success replacing the chip and if you need something else, just ask to see if anybody or me can help!

Best regards!
 
Last edited by a moderator:
Red is in the Netherlands I think. Just so you're aware. You're waisting your time and money paying someone to replace eegs and bridge chip. Like I said previously, the odds of it being those chips are slim to none. Use the money you were thinking of spending on the bga work and just buy another console where the PS2 actually works.
 
Hello, I dont seem to have gotten any DM's.

I just havent gotten around to try things to fix this. plenty of people tried multiple things to fix it and nobody knows why this happens.
 
Haven't replaced the EE+GS yet but I just wanted to say that if it isn't an issue with the EE+GS, I think it could also be the southbridge since it seems like it plays a part in the communication with the PS2 hardware and the rest of the PS3. But at the same time, everything else seems to work fine aside from PS2 so I might be wrong.

THEORETICALLY if it is an issue with the southbridge. Would it be possible to swap the southbridge chip with another one or is it married to the board? And if it is married to the board is there a way to re-marry another one? On top of that would it also cause my inability to bring up the menu, since I see that some people can still bring it up to return to the XMB.

I'm not just gonna blindly replace components on the board except for the EE+GS and that it. I'm just thinking of scenarios that could cause this phenomenon. So if you have anything to add or any corrections please don't hesitate to reply.
 
SB is not married to the board. If you have a rework station and time to kill, then it can't hurt to just try swapping stuff. If you're paying someone to do this work, don't even bother. There's some people that will gladly take your money, knowing it won't solve the issue. If this is a Franky, check the resistor mod. Especially around r2002. That resistor plays a part in PS2 as well. I've accidentally added a 49ohm resistor on cok002 boards and it causes no PS2. On cok001 boards the original resistor should be there. If you want to strictly stick to rip Felix's advice, a 47kohm resistor should be installed for "stability".
 
Last edited:
luvbuckets said:
SB is not married to the board. If you have a rework station and time to kill, then it can't hurt to just try swapping stuff. If you're paying someone to do this work, don't even bother. There's some people that will gladly take your money, knowing it won't solve the issue. If this is a Franky, check the resistor mod. Especially around r2002. That resistor plays a part in PS2 as well. I've accidentally added a 49ohm resistor on cok002 boards and it causes no PS2. On cok001 boards the original resistor should be there. If you want to strictly stick to rip Felix's advice, a 47kohm resistor should be installed for "stability".
Click to expand...

Thanks for the advice regarding the resistor mod! I'll definitely keep that in mind for when I have time to go back to it.
 
I see that some mentioned that ps2_emu.self could be having an issue. Does this mean that there are some configuration files related to PS2 backwards compatibility on the nand that could get corrupted? If so, is it possible to resolve this simply by rebuilding database, doing a system restore, or reinstalling OFW? Is there a way to check if there's something wrong with the part of the firmware that's responsible for the operation of the PS2 hardware? Of course this won't apply to all cases on no ps2.
 
I've seen one person fix a nops2 by pulling the nand chips, patching them and then reflashing. Reinstalling firmware seems like it might accomplish the same thing. You could give that a shot. The thing about nops2 is there's no one fix all solution. As far as I know there's no "PS2 uart" or way to officially troubleshoot it. You could try patching into the SB uart and eegs uart. Not sure how much that will tell you though. Because there's no one fix or way to really troubleshoot it. You kind of have to just swap stuff and see what happens.
 
Last edited:
So, EE+GS replacement did not work but at least that is crossed off the list of potential causes (FOR ME). How would I go forward with reinstalling OFW if it is a ps2_emu issue. Would simply updating my PS3 resolve any issues or corrupted data/files in my PS3's nand? Or is it more deeper than that. I think it could be a software issue since the menu does not come up when pressing the PS button. But that is most likely wishful thinking on my end because I just want a quick and easy solution.

The worst possible scenario I could think of causing this is a damaged internal trace but I'm hoping that isn't the case since the board was properly secured and not moved or bent during the process of the 40nm RSX swap.
 
I believe the bridge chip has been known to fix no menu/sync nops2. Like I said earlier, if you're paying someone to do this work, you're waisting your money.
 
Last edited:
luvbuckets said:
I believe the bridge chip has been known to fix no menu/sync nops2. Like I said earlier, if you're paying someone to do this work, you're waisting your money.
Click to expand...
In that case I'll just try reinstalling system firmware before doing anything else board wise. Forgot to mention that my PS3 is unmodded as well. I'll also try to get a complete dump of my nand as well just in case. You think reading from the EE+GS and southbridge would help point me in the right direction?
 
Hello I also have the same issue on my CECHB00. When I got it the PS2 mode was working (tested in GT4). I then sent the console to get a 40nm RSX installed (in hindsight I should´ve left it as is with a 90nm) and the technician told me that the PS2 mode doesn´t work and that this is more of a luck thing than anything. I´ll check the resistors used for the resistor mod. In my case the menu doesn´t pop up. I´ll also try to run an ISO straight from the HDD (to rule out the BlueRay Drive having an almost dead laser).
 
Nos 40s are hard to come by. If you have a true nos 40 on it, you may be better off harvesting it and using it on another board. As I said earlier, 9/10 times it's not worth troubleshooting no PS2 issues.
 
I would harvest it and use it on one of my CECHC04s with a 90nm RSX, but I don´t have any reballing tools or experience and I don´t really want to spend the money to get it remounted. I already have a Sony 65nm Frankie CECHC04 which I´ll be using. I´ll just do basic stuff like check resistors, try a different drive, nothing to complicated. In the worst case scenario I´ll keep it as a decoration piece.
 
Frish said:
Hello I also have the same issue on my CECHB00. When I got it the PS2 mode was working (tested in GT4). I then sent the console to get a 40nm RSX installed (in hindsight I should´ve left it as is with a 90nm) and the technician told me that the PS2 mode doesn´t work and that this is more of a luck thing than anything. I´ll check the resistors used for the resistor mod. In my case the menu doesn´t pop up. I´ll also try to run an ISO straight from the HDD (to rule out the BlueRay Drive having an almost dead laser).
Click to expand...

Let me know if the resistor mod on your PS3 is normal. We both seem to be having the same type of NoPs2 issue (black screen, can't bring up the menu). Well, on the surface it's the same, we both might have different causes.
 
I'm sure if it was something simple like the resistor mod, Viktor would of seen it. A botched resistor mod usually yields a glod. I believe it's r2002 that might have something to do with nops2. Sony officially populated that pad with a 47kohm resistor on their Franky's. Most people leave the original resistor. Several people have tried using a 47kohm resistor and it makes no difference
 
I'm an idiot for telling you guys this so late but I left out a pretty important piece of context. Before the first 40nm RSX was replaced, the menu was able to be brought up. After replacing it with another 40nm RSX, it gave a black screen unable to bring up the menu. Ugh, I feel pretty stupid right now but at least this is another clue.
 
You must log in or register to reply here.

Similar threads

Back
Top