WSOD Please post here.

[SeRi@lDiE]

I have a few questions to those who had WSOD before...

What was the last thing you did in your 770 before you got a WSOD?

I ask because I was able to replicate twice a WSOD in my 770... the funny thing was that I was able to re flash it from my Linux system and was able to bring it to life...
How did I replicate it?
Simple... I notice that my memory was full and that application manager was locked due to the system not having more space so I went to cli and call on apt-get, apt-get gave me a massage about /var/lock/ been lock from user and apt-get errors left and right "no space available" didn't pay to much attention to the message since I got a bit nervous... I rebooted the device thinking it will fix application manager so I can remove some apps but what I get? I get a WSOD it wouldn't boot it was just a white screen... so I quickly re flash my 770 and I was back in business... Something happen a few hours ago did the same steps and I was back in business with but with firmware 2.1...
So is it an issue with the system getting locked from user and going corrupt with the 2.0 firmware? I want to here from you guys who had this same issue... was the last thing you did? Install a pkg? Run apt-get? Work from root? Did you had R&D enable in your 770?

TIA.

[SeRi@lDiE]

WoW so many wsod in past post and reply .... :)

[ddalex]

Hello,

I think you're confusing WSOD with a boot-lockup due to software causes.

What are you describing resembles a boot sequence that is unable to run due to lack of disk space. The fact that you solve it by reflashing - and freeing some disk space shows it.

The classic WSOD is a hardware defect that damages the LCD at boot time when internal chips get powered up in un unusual way - this is a design problem. Nokia explained to me that the LCD driver should chip (actually a subsystem part of the OMAP chip) should start before LCD comes to life, or else LCD gets damaged. I'm not sure that this is a correct explanation, but seems plausible. The classic WSOD isn't fixed by software upgrade/update - it's a hardware defect.

Cheers,
Alex

[pycage]

Hello,

I think you're confusing WSOD with a boot-lockup due to software causes.

What are you describing resembles a boot sequence that is unable to run due to lack of disk space. The fact that you solve it by reflashing - and freeing some disk space shows it.

The classic WSOD is a hardware defect that damages the LCD at boot time when internal chips get powered up in un unusual way - this is a design problem. Nokia explained to me that the LCD driver should chip (actually a subsystem part of the OMAP chip) should start before LCD comes to life, or else LCD gets damaged. I'm not sure that this is a correct explanation, but seems plausible. The classic WSOD isn't fixed by software upgrade/update - it's a hardware defect.

Cheers,
Alex

So, it's a race condition and can happen on any 770 on a bad day? :(

[ddalex]

Yes, and no. As I understand it, the problem is in a defective chip - not the LCD. The LCD gets burned, and the fix is to replace LCD and hope that the condition doesn't happen again. So some 770s show the condition a lot. some just a couple of times or once, some just not at all - depending on your luck.

I'm having a 770 with WSOD - it's in repair shop now - and I can tell you I'm not planning to reboot that a lot when it comes back. Probably the best idea would be to get rid of it.

[rattis]

When mine died, via white screen of death, I was flashing from the 2005 to the 2006 version. Reflashing did nothing.

[Peter The Plumber]

Mine died in the flashing process. ie Unit successfully flashed and then booted to the WSOD. I sent mine for repair and got the same unit back several weeks later. No problems since, knock on wood. I have to wonder if the screen brightness has anything to do with it. I have two 770's, mine I had set at 50% and the other got set a little brighter. Both units produced in Estonia. I set my screen brightness up a little from 50% since?!?