My $500 Brick

[hookbill]

I don't use Custom ROMs. Every custom ROM I've seen has issues of some sort or another. I won't say my rooted stock Droid is perfect, but it gives me all the benefits I want from rooting without having somebody's idea of an OS in it.

While I can't comment on whether or not Custom ROM's are responsible for bricking a phone, I can tell you that the bootstraps or Clockwork have an issue. I've tried to go back to stock using recovery and it was a mess. I had to sbf to get back to stock and get my phone working good again.

And one last thing. Bricked is a word that's tossed around a lot. Your phone isn't truly bricked unless you can't turn it on at all.

 

[andyc]

I had a similar problem on my original Droid, around the time I was switching back and forth between the Simply Stunning and the most recent Cyanogen ROMs. While on Cyanogen, I was leaving work and my volume started going up, as if the button was being held down. It kept doing this for about an hour. I got home from work and my phone was frozen on a black screen. Reboot would show the load screen and then revert to the black screen. I couldn't get into bootloader either. Strangely, I hit the thing a few times out of frustration while it was frozen and it started right up :blink:

All was for naught however, since a few days later the "c" on the keyboard acted as if being held down, which on any homescreen immediately opened google search and went "cccccccccc...." as fast as I could delete it. It obviously did the same in any app where text entry was possible, rendering the phone useless. That's pretty much why I upgraded. [/pointless vent]



Summary: I hit my angrily struck my black-screened, seemingly-bricked phone like a disobedient servant and it worked again, a little. Haywire phones are haywire. dancedroid