I've never had to do a battery pull on this phone (had to do a lot on my old MT3G), but I went ahead and pulled the battery and it booted it up by itself and got all the way to the Cyanogenmod slpash screen (didn't get as far as the animation though) before shutting off and doing the vibrate thing again.
I did another battery pull, but only got as far as the Samsung screen (which lasted about 2 seconds which is shorter than it should be I believe) before a horizontal white line flashed on the screen and the phone died and started vibrating every 3 seconds again.
Here's what I've tried so far:
- plugging the phone into a power outlet, both with the battery in and out, either way it skips the Samsung screen altogether and goes straight into vibrating every 3 seconds.
- plugging into the computer - yields the same results as above
- trying to boot into recovery with all possible combinations of battery in/out and pc/outlet (I've tried several different USB cables as well).
I've done plenty of rooting/flashing of nightlies/RCs/Stables on my old MT3G and a friend's OG Droid and have never bricked a device... I've always at least been able to get into recovery. But this wasn't even the result of getting carried away with tinkering, it just happened while driving home (it was just sitting on my lap).
Has anyone seen this happen before? Any tips on what I should do? I obviously voided the warranty the minute I rooted it all those months back, so I'm not sure I can go prostrate myself before a T-mobile rep and beg for forgiveness...
Any advice would be appreciated. Ugh, I really hope it's not permanently bricked.
