What is going on in the phone at this point is the cracked joints have gotten worse, trying to make the phone charge there have been more connections damaged or the already damaged ones are further damaged. A few weeks later you notice the problem has gotten worse so you do some work with google and find instruction to wiggle it, jam stuff up into it, pull the charger off to one side, etc. You likely buy a new charger to see if that fixes it. Here is what happens.Ī couple of the pins crack or break making an intermittent connection with the board, at this point, the charger will still work but you notice some issues occasionally. I have repaired more of these phones than I can count and something that I see over and over is people doing further damage to their device by rigging it up instead of fixing it. The big reason I'm replying to this super old thread is this.
I'm not sure if it affected the whole flow somehow, but at some point I've installed, and later uninstalled the drivers from Samsung: > Mobile > Phones > Galaxy S > S III > Unlocked >
If you are using Windows 10 and couldn't find the link to download Android SDK you may skip #1 and #2. I had problems with my Samsung Galaxy Nexus that needed special drivers to be compatiable with ADB. If you still have problems, google the guide Remote Debugging on Android with Chrome and check for the part about drivers. I had major problems and managed to get it working with these steps.
Download Android SDK here ("SDK Tools Only" section) and unzip the content.How ever I found the instructions served by Alphonso out not to be sufficient and I did it this way on Windows 8: I downloaded the SDK and followed the instructions at Chrome Developers. My devices stopped working as Chrome de-activated the now depracated ADB plugin as it's built in dev-tools now.