[Touch Pro2, Tilt 2 Windows Mobile General] jennifaerie:
I had thought I was one of the many SOD sufferers out there, but I'm not 100% sure now based on the symptoms that are happening with my phone versus others, so I wanted to create a new thread and just let you know what happened to me (and what is occurring right now).

I ordered my TP2 the day it was released through T-Mobile. I'd gone two or three weeks without having any issues. I didn't really install too many CABs on there (with the exception of updating Bing, mobile Netflix, Astraware Solitaire, the battery increment fix, and TouchLockPro).

I put the phone on the charger one night, and the next morning, I clicked the Power button to unlock it. It vibrated, indicating it was powering on (versus just unlocking). I thought, Okay, no big deal. Maybe I shut it off by accident.

The next day, it was off the charger, and I clicked on the Power button to unlock, and it wouldn't turn on at all. (This is where my issue seems to differ from the SOD sufferers... their phones are making noise and actually functioning, but their screens are black, so they can't really do anything with the phone until they reset.)

I panicked, but shoved the phone back on the charger. Thought maybe the battery was dead (though I knew the last I looked at it, it was at 82%). Nothing happened. The light did not light up to indicate it was charging or fully charged.

I took the phone off the charger and pressed the Power button again. The red light flickered off and on, but nothing.

I plugged it back into the charger. Kept pressing the power button. Nothing. Then suddenly it turned on. It worked fine.

This happened maybe one more time before I left for vacation two weeks ago. The phone seemed to work just fine until about two days into my vacation. Then that started happening again.

But this time, it was worse. The phone would turn back on, and as soon as it got to the passcode screen to log into the phone, it would shut off. Sometimes, it'd let me get two numbers in, but most of the time, I couldn't even get one digit in before it shut off.

This would happen about six times in a row, and then the phone would just flat out not turn on for an hour or so.

As the vacation wore on (it was tiring, as our itinerary was on our phone, so there were times we didn't know where we needed to be because I couldn't get the phone on... I had a hard copy in the room, but that would mean having to travel back to the room to get it, losing an hour or two, so it wasn't worth it), it started to get worse. More times of getting to the passcode screen. More times of it shutting off before I could enter the number. Then it got to the point where I couldn't turn it on for four or five hours at a time.

No matter what I tried, the phone continued to "die". Everything that seemed to work turned out to be a coincidence.

What I tried:

1. Reset button.

2. Pulling the battery out.

3. Pulling the SD out.

4. Pulling the SIM out. (Would boot up the phone sans SIM. Then put it back in and boot it up again. I THOUGHT this worked, as I went from last Wednesday to yesterday with it working, but alas, it occurred again, even without the SIM in).

5. There were times I even squeezed the phone a certain way because it seemed like the phone responded more when I held it tighter.

6. I was wary that something I installed (like TouchLockPro) was causing the problem, so I upgraded to latest version, still occurred, then removed.

7. Believe me, there was a ridiculous number of OTHER bizarre things I tried (not including a TP2 voodoo doll), but I'm too embarrassed to mention those!

Outside of formatting the phone, I had exhausted all of the possibilities. I even logged on here while I was away to find out if anything had changed with SOD, and it seemed like nothing new occurred.

I had had it when the problem started again yesterday, so I went to a local T-Mobile retailer. Imagine their surprise! The battery was swapped out, and that didn't change anything. Removed the SIM, removed the SD, it occurred over and over again (which was great! I was actually able to prove the issue).

The man I showed it to called Support, and Support was dumbfounded too, so T-Mobile is replacing the phone. I should have it in a few days.

After all that, the phone came back last night. I know it'll die sooner or later, so it's best I'm getting a new one.

I think I probably would have been fine about this experience except it occurred while I was on vacation. Like I said, it had our itinerary. It was our gateway to the pets at home (texts, emails, pictures). It was really our only connection to the outside world. Granted, when you're on vacation, you don't want that, but I definitely want to know our pets are still alive! I also like to know where I'm supposed to eat! It was definitely a black cloud over our trip. (Thank you, though, to xda-developers, for keeping me sane when I DID have access!)

I am still pretty sure it's hardware, based on everything I've done, read, and seen over the past couple weeks. I was hesitant about setting up the phone the way I have it now, but I need to prove to myself that it's faulty hardware first before blaming applications.

But I wanted to share my story (albeit long) with everyone out there. People may be having the same issue but don't want to post, so if you are, you're not alone!