With the recent availability of the Android Wear SDK, I thought I should try developing for it, and Android in general. Got some app ideas to try out. So, in short my current ROM does not have the Settings > Developer Options option to get to Enable USB Debuggingso I can connect to my phone via ADB over USB.
My question is two fold.
Assuming I am not blind, and Developer Options really is missing, what am I messing up?
or
Which 4.4.2 build gives me the option for USB debugging and the other developer settings?
galorin said:
With the recent availability of the Android Wear SDK, I thought I should try developing for it, and Android in general. Got some app ideas to try out. So, in short my current ROM does not have the Settings > Developer Options option to get to Enable USB Debuggingso I can connect to my phone via ADB over USB.
My question is two fold.
Assuming I am not blind, and Developer Options really is missing, what am I messing up?
or
Which 4.4.2 build gives me the option for USB debugging and the other developer settings?
Click to expand...
Click to collapse
Go to the settings..About phone...Build number...Tap it 7 times
Thanks for that! I did not know that was what I was supposed to do. All sorted now.
Has anybody used Asus Fonepad 7 for USB debugging on Windows?
Please let me know if it works without trouble.
Or, will Samsung tab 3 be a better choice than Asus Fonepad7 for app development(with usb debugging option)?
tigeronk2 said:
Has anybody used Asus Fonepad 7 for USB debugging on Windows?
Please let me know if it works without trouble.
Or, will Samsung tab 3 be a better choice than Asus Fonepad7 for app development(with usb debugging option)?
Click to expand...
Click to collapse
i just buy a Asus Fonepad 7 K012 as well. and now trying to root it. i found the way to go to development option. it's from settings > about > sofrware information > build name. and it will pop some message that you are the developer now. so back to setting. there will be an option above about it is developer options.
wish this could help.
you should enter settings > about > sofrware information > build name. and it will pop some message that you are the developer now. so back to setting. there will be an option above about it is developer options.
Fanie Yume said:
i just buy a Asus Fonepad 7 K012 as well. and now trying to root it. i found the way to go to development option. it's from settings > about > sofrware information > build name. and it will pop some message that you are the developer now. so back to setting. there will be an option above about it is developer options.
wish this could help.
Click to expand...
Click to collapse
Great :good: i really liked the settings the way they have hidden.
Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!
I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging
jac10000 said:
I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging
Click to expand...
Click to collapse
It does not show up ever, unplugged or plugged in.
Jacobsen Chief said:
It does not show up ever, unplugged or plugged in.
Click to expand...
Click to collapse
Ok try this :
Solution 1 : Have you switche the activate button ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode
jac10000 said:
Ok try this :
Solution 1 : Have you switche the activate button ?
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode
Click to expand...
Click to collapse
None of those things worked... Ive never seen this before. Here is a screenshot
I think it's a bug with lollipop and it seem that the solution is the factory reset
jac10000 said:
I think it's a bug with lollipop and it seem that the solution is the factory reset
Click to expand...
Click to collapse
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?
And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1
jac10000 said:
And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1
Click to expand...
Click to collapse
I tried installing the KDZ though TWRP, but when it failed I decided to go ahead and just update it with the LG Software. I had read other articles on rooting the G3 with Lollipop, so I didn't really worry about re-rooting it until I ran into this problem.
For installing with the KDZ, I extracted Modem, Boot, and System.imgs, but the System.img failed. And yes with KitKat, I could use debugging.
facing the same problem myself, did you ever find a solution? because this is getting really frustrating
Dragontype191 said:
facing the same problem myself, did you ever find a solution? because this is getting really frustrating
Click to expand...
Click to collapse
Update, I made a post over on the US Cellular forums and if anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!
Dragontype191 said:
If anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!
Click to expand...
Click to collapse
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.
To Enable USB Debugging mode that is blocked by Server you have to dissable McAfee Mobile SECURITY
Jacobsen Chief said:
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?
Click to expand...
Click to collapse
Click on revoke USB debugging authorization. Click ok. Turn off developers option on the verg top. Turn it on again and voila you now have an option to put a check on usb debugging. Hope it works for you...
LG G3 Android 5.0 user
Jacobsen Chief said:
Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
PLEASE PLEASE PLEASE READ! This is probably the fix to this problem all because of a stupid built in app that the g3 includes now and it has to do with McAfee Security.
If it worked mark this up for those future people who have issues!!
Okay so i found out what the problem was. I used to own and lg g2 but recently got the g3. Im with sprint fyi...but anyways i was tinkering around with it being 17 and stupid i bricked the phone, so i eventually got it fixed again. Previously my phone was rooted but now it wasnt so then i went back to get developer options activated and usb debugging active as well, however i ran into this problem. This stumped me because i had it rooted before. So then i was thinking what did i give accsess to that i hadnt before that isnt allowing usb debbugging...well it had to be an app since this didnt happen to me before and it had to be an app that i hadnt used before i bricked my phone and then i thought it has to be a built in app since no third party app would have that permission to say something like "disabled by server policy" then i realised okay what does the g3 have that the g2 doesnt have and is built in.....Mcafee security and Lookout! And it made sence because when you check the box for usb debugging you are making your android less secure! So i entered the McAfee app tapped settings ---> and the first option should be "lock down device" TURN THAT OFF! That right there is your culprit now go back to dev options and you can now enable usb debugging again please rate this up so people can see what was going on and how to fix it. No need to reset your phone. Also let me know if this worked. I have got nothing but positive feed back so far.
I am having the same problem and i have an LG Lucky and usb debugging is disabled by server policy and i really dont know what to do but it worked at first then later it got blocked.
help please
PokrTom said:
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.
Click to expand...
Click to collapse
My debugging option is not available. Do I need to have my old sim card in place? It was from at&t. I took it out a while back. Is that why I cannot chose the Debug option? Ive tried everything on this forum.
I had the same issue. It was blocked by mcafee. I had to change it from " locked down mode" to unlocked mode, then turn developer options off and right baxk on. Then i was allowed to turn on usb debugging
Solution
Okay, so I was having the same issue. I contacted LG, Google, and finally AT&T after I tried a lot of the suggested solutions on this post. The AT&T tech support rep helped me research this issue. The issue is that an app on your phone is not allowing you to be able to debug, most likely a security app. I suppose that it thinks by allowing your phone to debug could cause harm to the device. The app that was keeping me from debugging was McAfee, which came pre-installed. When you disable this app, or whichever app is keeping you from debugging, you will then notice that the message 'USB debugging is disabled by server policy' goes away. I hope this helps you all, and happy developing!
God is good!!!
sir can you all help me for this problem? i can't update and fix my g3! ugrrrr !!!1
Dear Community,
I am currently unable to activate the USB debugging mode on my unrooted Samsung Galaxy S9.
I have activated the developer mode.
USB debugging has alywasy been enabled in the past.
Since I wanted to use Helium, I double-checked that it is activated . but it is not.
The option is grayed out and there is a message saying "USB-Edugging mode will start as soon as usb is connected (translated from german)".
No matter waht I tried, nothing worked out.
Can you please help me out?
Best regards
Bacardi Man
I've noticed on older Samsung devices that if OEM Unlock is enabled then that will grey out USB debugging. The fix was to disable OEM unlock and reboot. Of course, if you're waiting on the 7 day thing to root that may reset the timer. I'm not sure about that since root will never be an option on my US version.
Thank you for the hint, but OEM unlock isn't activated and has never been as I am using Secure Folder (Knox).
Any other suggestions?
Bacardi Man said:
Thank you for the hint, but OEM unlock isn't activated and has never been as I am using Secure Folder (Knox).
Any other suggestions?
Click to expand...
Click to collapse
Probably won't help but worth a shot clearing CACHE from recovery
*Detection* said:
Probably won't help but worth a shot clearing CACHE from recovery
Click to expand...
Click to collapse
Good idea, but that did not work out either.
Am I really the only person with that problem?
Bacardi Man said:
Good idea, but that did not work out either.
Am I really the only person with that problem?
Click to expand...
Click to collapse
Could it be because of knox secure folder?
Tel864 said:
Could it be because of knox secure folder?
Click to expand...
Click to collapse
Maybe, but wouldn't that be made official somewhere?
I never red about it.
Maybe too simple but in Developer Options>USB configuration do you have MTP selected?
Tel864 said:
Maybe too simple but in Developer Options>USB configuration do you have MTP selected?
Click to expand...
Click to collapse
Yes, MTP Mode is selected.
Bacardi Man said:
Maybe, but wouldn't that be made official somewhere?
I never red about it.
Click to expand...
Click to collapse
Looks like it is probably KNOX causing it
https://seap.samsung.com/content/why-usb-debugging-mode-disabled-knox
https://seap.samsung.com/forum-topic/can-i-use-usb-debugging-mode-device-running-knox
Solution 3: Use USB debugging mode on a device running KNOX (For Samsung )
By default, My KNOX and KNOX Premium (through CellWe EMM) disables USB debugging on a device when it creates a secure container.
IT admins KNOX Premium (through CellWe EMM) can later enable USB debugging mode through the Admin Portal: Simply select Policies > Mobile > Samsung KNOX Device Settings > Restrictions Settings > Permit USB debugging = Yes. On the device, you need to go to Android Settings, enable Developer options, then enable USB debugging. The exact steps vary depending on your Android version, as described in Using Hardware Devices.
If you are using My KNOX, you cannot enable USB debugging mode while the container is installed. Unfortunately, you have to root your device and uninstall 'My KNOX' (enter Knox, chose Knox settings app -> More Information -> unistall Knox.), then you will be able to turn on USB debugging mode.
https://www.syncios.com/android/fix-usb-debugging-grey-out.html
hey, I cant find developer setting in the phone. I can get into the recovery. can i flash firmware from there without going to developer setting and unlocking. When i connect the wire to phone odin doesn't pick up anything in recovery mode, odin only pick up connection when the phone is turned on.
my question is can i flash a firmware from the recovery mode, there is option to update from sd card, can i not put the firmware in usb and connect it to phone and update?
Getting the Developer Settings to appear is the same on all Android devices.
Go to Settings > About > software information > keep tapping on the Build number item until it tells you that Developer Options have been unlocked. YTou'll them find them in the Settings menu.