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

Question

Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2) I am unable to use Chrome\'s remote debugging for android (more details here).

I have the deve

Answer 1

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

Answer 2

Those who updated their device to Android 4.2 Jelly Bean or higher or having a 4.2 JB or higher android powered device, will not found the Developers Options in Settings menu. The Developers Options hide by default on 4.2 jelly bean and later android versions. Follow the below steps to Unhide Developers Options.

1. Go to Settings>>About (On most Android Smartphone and tablet) OR

Go to Settings>> More/General tab>> About (On Samsung Galaxy S3, Galaxy S4, Galaxy Note 8.0, Galaxy Tab 3 and other galaxy Smartphone and tablet having Android 4.2/4.3 Jelly Bean) OR

Go to Settings>> General>> About (On Samsung Galaxy Note 2, Galaxy Note 3 and some other Galaxy devices having Android 4.3 Jelly Bean or 4.4 KitKat) OR

Go to Settings> About> Software Information> More (On HTC One or other HTC devices having Android 4.2 Jelly Bean or higher) 2. Now Scroll onto Build Number and tap it 7 times repeatedly. A message will appear saying that u are now a developer.

1. Just return to the previous menu to see developer option.

Credit to www.androidofficer.com

Answer 3

I know this is an older question, but I thought I would also post my solution:

• Update your Chrome on your phone and on your PC.
• Even if it says you have the latest driver for your device inside Device Manager, you may need an alternative. Google latest Samsung drivers and try updating your drivers.

Answer 4

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)

Answer 5

For me the solution was to download the Android SDK and launch adb devices which started the adb daemon.

Answer 6

In case it helps anyone I will post what worked for me.

I had to plug my S3 into a direct USB port of my PC for it to prompt me to accept the RSA signature. I had my S3 plugged into a hub before then.

Now the S3 is detected when using both the direct USB port of the PC and via the hub.

NOTE - You may need to also run adb devices from the command line to get your S3 to re-request permission.

D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
9283759342847566        unauthorized

...accept signature on phone...

D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
9283759342847566        device