Timeline for Galaxy S3 is stuck at Samsung logo splash screen and won’t charge
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2016 at 1:09 | comment | added | Mohammad Haseeb | If you ever enabled "USB Debugging" in the Developer options, you can look at the ADB logs and see what's going on with your phone using a USB cable and the adb logcat. My hunch is that of Alex's i.e. "sudden death". It happened to my phone some years ago. | |
| Jun 6, 2016 at 23:18 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 24, 2015 at 5:12 | answer | added | See-Sharp | timeline score: 0 | |
| Mar 6, 2015 at 14:39 | answer | added | Noumenon | timeline score: 0 | |
| Feb 13, 2014 at 16:26 | answer | added | user53634 | timeline score: 0 | |
| Oct 8, 2013 at 14:11 | answer | added | user5506 | timeline score: 1 | |
| Sep 22, 2013 at 11:54 | comment | added | Izzy | Giving it to service might also be a variant, at least if it's still under warranty. I know it's rooted, which voids that in most countries; but at least here in EU they make a difference (EU law says rooting doesn't void "implied warranty", which any manufacturer must ensure). | |
| Sep 22, 2013 at 4:44 | comment | added | Troubleshooter76 | Thanks for your help, but I have given up trying to soft unbrick my phone. I’ve tried to enter recovery mode, to no avail. However, I can get into download mode and I've already tried many unbricking procedures using ODIN, but none of them have worked. I'm deciding whether I'll replace the main motherboard or not. I'll keep up posting. | |
| Sep 15, 2013 at 12:16 | history | tweeted | twitter.com/#!/StackAndroid/status/379217108225490944 | ||
| Sep 15, 2013 at 11:19 | comment | added | Izzy |
I don't know Samsung devices well enough, but AFAIR they also offer a "download mode". As you obvioulsy cannot even reach "recovery mode", maybe there's a chance to get there and see whether the device becomes visible to adb devices. If so, there might be a chance to "wipe" it from there, or using some of the Samsung-specific tools like Odin or Heimdall.
|
|
| Sep 15, 2013 at 5:59 | review | First posts | |||
| Sep 15, 2013 at 7:17 | |||||
| Sep 15, 2013 at 5:41 | history | asked | Troubleshooter76 | CC BY-SA 3.0 |