My SM910T was working fine, and suddenly the screen froze for a few seconds, then blanked.
From that point on, the phone has done nothing but a brief vibration.
After a battery pull, starting up with 1) normal power switch 2) download startup 3) recovery startup 4) inserting USB cable
all result in the same: A short delay, a brief buzz from the vibration, which may repeat again every few seconds. The screen remains black.
When connected to a Windows computer with USB, the phone is enumerated. It shows up as these devices:
ADB does not work. The command "adb devices" returns the null list (List of devices attached)- it does not see any device attached.
Windows sees the phones internal file system as an MTP drive, and shows the file structure, but the files are not accessible.
ODIN sees there is a phone attached (it says <ID:0/004> Added!!)
What mode or state is the phone in, and what should be done to restore normal operation?
From that point on, the phone has done nothing but a brief vibration.
After a battery pull, starting up with 1) normal power switch 2) download startup 3) recovery startup 4) inserting USB cable
all result in the same: A short delay, a brief buzz from the vibration, which may repeat again every few seconds. The screen remains black.
When connected to a Windows computer with USB, the phone is enumerated. It shows up as these devices:
- SAMSUNG_Android SAMSUNG Mobile USB Component,
- trtlemo
- Port #0004 SAMSUNG Android ADB Interface.
ADB does not work. The command "adb devices" returns the null list (List of devices attached)- it does not see any device attached.
Windows sees the phones internal file system as an MTP drive, and shows the file structure, but the files are not accessible.
ODIN sees there is a phone attached (it says <ID:0/004> Added!!)
What mode or state is the phone in, and what should be done to restore normal operation?
from xda-developers http://ift.tt/1RAw8Bf
via IFTTT
No comments:
Post a Comment