Rank: Apprentice
Rating: 0%, 0 votes
Northeast Mail Server
postaldaemon@verizon.net
I had the same "white screen" problem as everyone else. The slam method did not work for me (at least not for the force I was willing to apply). But I was successful in disassembling the phone and reseating the display connector. The instructions from Richard Markert are easy to follow. They are here:
http://www.raduque.com/krzr_disassembly/
I would be happy to help anyone with this process. Email: ellery (at) starbus (dot) com. Phone: (five-0-eight) 485 .,.6950.
The hardest part is prying loose the top bezel trim. Try doing that from the very top near the camera. It is not necessary to remove the chin piece or the 4 Torx screws on bottom (battery side)...just the 4 screws beneath the glass top.
The process took me about 30 minutes. Most of my time was spent cleaning out gunk along the seals from 2 years of use and making sure that the display and camera were squeaky clean.
It may be difficult to find a tiny #T5 Torx driver (also called a star driver). I found 5 different models at Home Depot, but they are not with the miscellaneous bits along the aisle of the power tool crib. Those only go down to size 10. Instead, look for the all-in-one tools along the back wall. I purchased a Husky 36 piece precision screwdriver set for only $4.80. For all these bits and extenders, that's a real steal!
In my case, it was also at exactly 2 years since purchasing the Krzr (Verizon K1m CDMA). I usually don't accept conspiracy theories, but I must admit that the circumstantial evidence is quite overwhelming. It seems that no matter how frequently or infrequently the owner flips open the phone, the display connector comes loose just as the service contract expires.
From Verizon's point of view, this isn't good. It not only creates a frustrated customer, but it also makes it likely that a long-term Verizon user (someone who probably won't switch away to another wireless provider) will consume another valuable hardware incentive which costs Verizon $200~300. But from Motorola's POV, it makes perfect sense. Is it possible that the firmware is actually tracking the time and incrementing a register as it sets up the failure? As I said, conspiracy theories really don't stand the test of time. The marketplace is too competitive and too unforgiving. But the corroboration amongst visitors to this forum are downright eerie!