[Sprint Samsung Galaxy S III] Hamspiced:
[MENTION=1387708]rishid[/MENTION]gb

what ive had to do in the past to resolve these issues. Ill Copy/Paste the instructions i have used to Install ADB on my past computers but ill also throw links for the origionals at the bottom of the post.

1. Verify Battery is at least 50% charged. I usually do this by turning the phone off and plugging it into the charger, you should be able to see the battery charging up.

2. Install ADB on your computer. I have a mac, and this was kind of a pain in the ass to do at first but ill explain.

Mac-

1. Download the latest Android SDK from Google: Android SDK - http://developer.android.com/sdk/index.html

2. Extract the ZIP file to your desired location

3. To get ADB, you need to install the SDK: Installing the SDK - http://developer.android.com/sdk/installing/index.html

If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and

proceed with the tutorial: ADB - http://esausilva.com/wp-content/plu...silva.com/misc/android/platform-tools-osx.zip

Create an environment variable (Optional) **This is good because once you create the variable you dont have to navigate to the ADB folder every time to use it.

1. Open Terminal

2. Type cd ~ this will take you to your home directory

3. Type touch .profile this will create a hidden file named profile

4. Type open -e .profile this will open the file you just created in TextEdit

In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools

Save file, close TextEdit, Quit Terminal, and Relaunch Terminal

NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB

You are good to go, type in terminal adb devices, this should give you a serial number, which corresponds to your phone. Looks something like this:

List of devices attached

HT99PHF02521 device

NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices

Also make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)

In Android 4.2.x and up Developer Options is hidden, to make it visible, do the following

Tap seven times in Build Number: Settings > About Phone > Build Number

You will get a message saying you have enabled Developer Options or something like that, go back to Settings and you will see Developer Options in there.

PC-

Step 1: Head over to this link to download the latest version of Android SDK. http://developer.android.com/sdk/index.html

Step 2: Extract the contents of the downloaded file to your hard drive. Within the unzipped “sdk” folder, you’ll find another folder labeled ‘platform-tools’. Since we’re interested in only ADB and Fastboot, this is the one that we’re looking for.

Step 3: Move the platform-tools folder to a convenient location on your PC. The root of C: drive is usually a good idea. I also recommend renaming the folder to something easier, like C:\Android-adb.

By this point, ADB is essentially set up, but to use it, you’ll first need to navigate your command prompt window to this Android-adb folder, and then run all ADB commands inside it. Since it’s too much hassle for most users, we’ll add this location to Windows’ System Path Variable, so you can run ADB commands from anywhere.

Step 4: Right-click the Computer icon on your desktop, and go to Properties.

Step 5: Under System Properties, go to the Advanced tab, and click Environment Variables.

Step 6: The system variables are contained within the lower pane. Locate “Path” here, highlight it, and click the Edit button.

Step 7: There will already be a string of locations here; navigate to the very end, and add the following text (assuming that you have chosen C:\Android-adb as the folder; otherwise, enter whatever path you’ve located adb at):

;C:\Android-adb

Click OK, finally.

Your ADB folder is now configured, and you can run both ADB and Fastboot commands from anywhere in command prompt. To verify, connect your Android device to PC with USB Debugging enabled, launch a command prompt window, and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed.

Mac Instructions

http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/

Pc Instructions

http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/

Now that ADB is installed. If you find yourself in a Bootloop, OR you find yourself in a situation where it wont pass by the boot animation, open up terminal or command prompt. Then type Adb Devices, it should recognize your device and list the serial. And from there you can use the command:

Adb Reboot Recovery

From there you can wipe/Factory Restore and then Flash a new rom.

If you cannot reboot recovery but ADB still sees your phone. You can use command ADB shell to open a linux command prompt through your phone to push and pull files. Ive done this to push roms when the phone wouldnt mount properly.

I know this isnt "THAT" thorough, however ADB has litterally saved my ass a BUNCH of times. Id reccomend setting it up if you flash frequently.

Sorry it took me a couple days to respond, i am not on XDA as much as i used to be.