• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help USB Debugging Greyed Out

K

Keith Koonin

Newbie
I was previously able to set USB Debugging , on my Samsung S4, from AT&T, before I upgraded. While I am still able to select Developer Options I am not able to check USB Debugging whether my device is connected to my desktop or not. However, Windows Explorer does show directories on my phone when it is connected through the USB port.
I am running Android 4.4.4

Can anyone tell me how I can get USB debugging working again? Is it possible that AT&T is blocking the USB debugging option?
 
Click on the build number on the phone info tab until it says "something clicks until you become a developer!" then it'll let you.
 
LitrosNub said:
Click on the build number on the phone info tab until it says "something clicks until you become a developer!" then it'll let you.
Click to expand...
Thank you for the response. I already had Developer Options working. However I tried pressing Build Number multiple times as you suggested. The message I received was "No need developer mode already enabled". Therefore I am still stuck with the USB Option under Developer Options greyed out
 
Have you tried enabling it when your not connected to USB? That happend to me before and I needed to disconnect the USB connected to check the box, that might work too.
 
EarlyMon said:
If you turn on mock location will it change the usb debugging option?

Windows Explorer has zero to do with USB debugging btw.
Click to expand...

I tried turning on Mock Locations but that did not help.
I realize that Windows Explorer does not hve anything to do with USB Debugging. I mentioned it to illustrate that I am able to connect the phone to the computer.

Still stuck :(
 
Stupid question but have you placed the slider on the top right of the screen in developer options to "on"?
 
In such a case there'd be no way to turn it off. AT&T is restrictive, so that's hard to imagine.

Grab Terminal Emulator and say

ps | grep adb

Or

find adbd

If the adb daemon is missing all the fiddling in the world with that switch won't help.

If it is there, can you get by with wireless adb?
 
EarlyMon said:
In such a case there'd be no way to turn it off. AT&T is restrictive, so that's hard to imagine.

Grab Terminal Emulator and say

ps | grep adb

Or

find adbd

If the adb daemon is missing all the fiddling in the world with that switch won't help.

If it is there, can you get by with wireless adb?
Click to expand...
Is the handset supposed to be running adb?
 
Keith Koonin said:
I am sorry I do not understand what you mean.
Click to expand...
Here is a screen shot
Screenshot_2015-02-13-20-58-01[1].png
 
Keith Koonin said:
I am sorry I do not understand what you mean.
Click to expand...
My bad - I thought that was a new universal setting with KitKat, could be unique to my phone.

I backtracked and in any case, it doesn't affect mine, so never mind, sorry.

Keith Koonin said:
Is the handset supposed to be running adb?
Click to expand...

When usb debugging is on the adb daemon runs on the phone as a background process - it's what adb on your pc links to.

If it's running anyway (as shown by the ps command saying something about it instead of just returning nothing) you should be good to go.

If it's not, and it's there, it has to be started by hand.

Problem is if you're not rooted already, you probably can't - it often resides at /sbin/adbd depending on the model, but basically, a root-reserved directory in any case.

I wonder if your carrier has done this to hamper rooting. :mad: O.o

Per your first post in the thread, AT&T could have easily removed it.

I assume with a new OTA, you're not rooted?
 
You must log in or register to reply here.
Back
Top Bottom