[Calavera]

So I'm on 3.55 DEX Rogero v1, fat EU 60GB (CECHC04) with my own 80GB HDD in. I have the 22nd july release of Multiman. I've got my root key and everything backed up.

1) Started PS3 > Multiman > Game Backup A (on external) > PS3 reboots to XMB > Booted from XMB no issue.
2) Quit to XMB > Multiman > Game Backup B (on internal) > PS3 reboots to XMB > red blinking light before XMB shows up.
3) Flipped power switch off/on and started up > now YLOD.
4) Unplugged and plugged back power cable > still YLOD.
5) Removed HDD > The PS3 startup sound for 0.5 seconds then blinking red light.
6) Tried another HDD > YLOD.
7) Tried without HDD again > YLOD.

Both these games have worked before but I've never started them after each other previously.

Was this because I never restarted the PS3 between loading the 2 different games from Multiman? Did that cause some issue with lv2 or something? I'm really hoping this is a semibrick or something.

Any help is greatly appriciated.

[parminder_11]

Try getting ps3 into factory service mode ? and reinstalling firmware
************* [ - Post Merged - ] *************
Thats the only thing i can think of apart from attempting a hardware flasher
************* [ - Post Merged - ] *************
Actually after further reading your post I realised that you have a 60gb launch console, they used the most power and had the largest CPU/RSX (90nm) meaning they where most prone to Ylod (i Know this from past experience) So unfortunately your ps3 may be suffering from Ylod and not some lvl2 failure

[Calavera]

Thanks for the input parminder_11.

How would I go about getting tofactory service mode, since the USB drives aren't powered when you have a YLOD? Any ideas?

Honestly I'm not sure what to hope for, reflowing or buying a hardware flasher. Just seems weird to me that I got the error just as Multiman was preparing the game backup and reset the PS3, isn't lv2 involved in that step somehow?

[R3QU13M]

I was analyzing various post about the "Infamous YLOD" and more people are getting them with a jailbroken PS3 phat system thats been running CFW for a while despite the other factors that cause it. I'm beginning to think that certain CFWs are putting stress on the consoles and causes them to overheat .

[zaphod]

if you are a hardcore-gamer -> do not convert to DEX it uses more system ressources (causes more heat so faster YLOD-Brick on the NANDs)

to fix your YLOD -> only possible with hardware flasher... No JIG will work..

always shutdown the dex after using multiman to play a game..

[svenmullet]

This sounds like normal ylod caused by bad solder balls under the RSX. You need to get it reballed. (I wouldn't suggest using a heat gun to reflow. I used to support this concept, but have since changed my mind on it after ruining a CECHA01 by reflowing it too many times)

[Calavera]

All right thanks for the input guys. I actually recieved this unit 2 weeks ago broken from someone else and reflowed it, guys I need to reball just to be sure. 3 quick questions though if you don't mind.

Originally Posted by zaphod to fix your YLOD -> only possible with hardware flasher... No JIG will work.. always shutdown the dex after using multiman to play a game..

1) Let's say this is a brick and I need a flasher, which one would you recommend for my model, or anyone I should avoid? I have backups of the NAND from jaicrab and some other tools.

2) Any way for me to confirm that it is a "classic" YLOD and not a brick? The fact that it did start once for a few seconds tells me that it is, am I right in assuming this?

3) Any tool I can use to extract the game save files from the HDD? I have a 2nd fat PS3 as well (sadly on 4.11 or I would've given this up already)

Again thanks for the input and help, much appriciated!

Cheers

[svenmullet]

Originally Posted by Calavera 2) Any way for me to confirm that it is a "classic" YLOD and not a brick? The fact that it did start once for a few seconds tells me that it is, am I right in assuming this?

You are absolutely correct. While I'm sure it's possible for NAND flash to spontaneously corrupt iteself while playing a game, it's very unlikely. You said yourself, you got it broken and reflowed it; the ylod came back. The only way to save this machine is reball it. Hope this helps

[Calavera]

Hey guys, just wanted to let you know I solved it. In an effort to not be a jerk to some future googler, here's what I did:

Reflowed and it started, ordered everything I need to reball and will soon. Gave me a scare though when it shut down just as multiman reset the PS3 lol.

Again thank you all for your time and feedback.

[parminder_11]

It may be a coincidence that it got ylod as multiman was running your game, also as you say that you reflowed it, it supports that its "classic ylod" as reflows are temporary.