[I figure this is a long-shot question. But I'll ask in case experts here have any insight.]
Yesterday I dropped my S9 from roughly chest height onto a concrete floor. It's in a QuadLock case. It landed flat (not on a corner or side) screen side down. It was loud enough, when I picked it up, I wouldn't have been surprised if the glass broke. But it didn't.
The phone worked normally for a couple of hours. Then while sitting on a table it spontaneously attempted a reboot and stayed on the T-Mobile splash screen continuously.
After a bunch of futzing I got into the Android recovery screen and did Wipe Data / Factory reset. I get through phone setup. But as soon as it appears the phone is booted, when I go to use it......it reboots. I then flashed Android 10 using Odin and behavior is the same. The phone gets warm/almost-hot while going through these reboot sequences.
Between the reset and Android 10 flash I did myself I'm kind of figuring what I'm dealing with is not a sw or configuration problem, but rather a hardware issue.
Based on this story - any educated cases if this seems like a hardware problem?
Thanks!
Jim
Yesterday I dropped my S9 from roughly chest height onto a concrete floor. It's in a QuadLock case. It landed flat (not on a corner or side) screen side down. It was loud enough, when I picked it up, I wouldn't have been surprised if the glass broke. But it didn't.
The phone worked normally for a couple of hours. Then while sitting on a table it spontaneously attempted a reboot and stayed on the T-Mobile splash screen continuously.
After a bunch of futzing I got into the Android recovery screen and did Wipe Data / Factory reset. I get through phone setup. But as soon as it appears the phone is booted, when I go to use it......it reboots. I then flashed Android 10 using Odin and behavior is the same. The phone gets warm/almost-hot while going through these reboot sequences.
Between the reset and Android 10 flash I did myself I'm kind of figuring what I'm dealing with is not a sw or configuration problem, but rather a hardware issue.
Based on this story - any educated cases if this seems like a hardware problem?
Thanks!
Jim