Chrome's remote debugging (USB debugging) not working for Samsung Galaxy S3 running android 4.3

My devices stopped working as Chrome de-activated the now depracated ADB plugin as it's built in dev-tools now.

I downloaded the SDK and followed the instructions at Chrome Developers. How ever I found the instructions served by Alphonso out not to be sufficient and I did it this way on Windows 8:

1. Download Android SDK here ("SDK Tools Only" section) and unzip the content.
2. Run SDK Manager.exe and install Android SDK platform tools
3. Open up the Command prompt (simply by pressing the windows button and type in cmd.exe)
4. Enter the path with ex: cd c:/downloads/sdk/platform-tools
5. Open ADB by typing in adb.exe
6. Run the following command by typing it and pressing enter: adb devices
7. Check if you get the prompt on your device, if you still can't see your phone in Inspect Devices run the following commands one by one (excluding the ") "adb kill-server" "adb start-server" "adb devices"

I had major problems and managed to get it working with these steps. If you still have problems, google the guide Remote Debugging on Android with Chrome and check for the part about drivers. I had problems with my Samsung Galaxy Nexus that needed special drivers to be compatiable with ADB.

Update

If you are using Windows 10 and couldn't find the link to download Android SDK; you may skip #1 and #2. All you need is activate "Android Debug Bridge". Go straight to #3 - #7 after download and execute "platform-tools"(https://developer.android.com/studio/releases/platform-tools.html)

Having attempted to follow Valros.nu's answer, i discovered that the sdk download is now bundeled with androind studio, in an 840MB exe installer.

As all you need for this particular program is the adb program, you can get this in a standalone installer from the xda guys:

http://forum.xda-developers.com/showthread.php?t=2317790

Note that you do not need to type adb.exe, simply type adb devices into the command prompt that is launched after install.

Also, i had to unplug and replug in my samsung s4 to get the remote debugging prompt to appear on the phone

After looking around a little longer I came across this. Apparently, there isn't a solution to this issue yet, but there is a workaround - going back to the legacy workflow.

The legacy workflow did work for me, and the only additional thing I had to do was to go to the platform-tools folder from android SDK download, open a command window here and run command "adb devices". This caused the computer RSA key fingerprint panel to pop on my mobile screen, and after granting permission, the device showed up under Chrome's Inspect page.

Turns out that it was not an issue caused by mobile OS upgrade but by Chrome (I was thrown off by the fact that it worked on my Nexus4 somehow). In the older versions of Chrome there was't a need to download the 500 odd mb Android SDK, as it supported an ADB plugin. But with latest version of Chrome, I guess, going legacy is the only way to go.

I have Samsung Galaxy S3 and it was not showing in the "Remote devices" tab nor in chrome://inspect. The device did show in Windows's Device Manager as GT-I9300, though. What worked for me was:

1. Plug the mobile phone to the front USB port
2. On my phone, click the notification about successful connection
3. Make sure the connection type is Camera (PTP)
4. On my Windows machine, download installer from https://github.com/koush/UniversalAdbDriver
5. Run it :)
6. Open cmd.exe
7. cd "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
8. adb devices
9. Open Chrome in both mobile phone and Windows machine
10. On Windows's machine navigate to chrome://inspect - there, after a while you should see the target phone :)

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: http://www.samsung.com/us/support/downloads/ > Mobile > Phones > Galaxy S > S III > Unlocked > http://www.samsung.com/us/support/owners/product/galaxy-s-iii-unlocked#downloads