[Q] Disable USB/Charge Only Mode - Galaxy Tab 2 Q&A, Help & Troubleshooting

For security reasons, I don't want users to be able to connect the tablet to a computer and download its content. Is there anyway to disable USB data transfer? I know that certain Android devices enable a "Charge Only" option when they are connected via USB, but it doesn't seem to exist on the Galaxy Tab 2 10.1. Is there any way to get that setting on the tablet?
Currently I'm working with a GT-P5113 that's been updated to 4.2.2. Any help would be really appreciated.

For anyone who is curious I solved my problem.
First I rooted the tablet using cf auto root. Then I wrote an app that toggled the USB permissions by running a shell command with root privileges. This app also included a service that ran after boot to disable USB (otherwise USB is always re-enabled on reboot).
I would post links to helpful information, but as I am new I am not yet allowed. I'll possibly edit my answer with helpful links when I am permitted.

Related

[Q} WidgetLauncher Root Access

Hi all,
I hope this is not a 'noob' questions, but I googled and got nothing.
I downloaded WidgetLauncher and can't enable the root access to overcome some issues inherent in the AndroidOS. It says Root is either not available or denied.
I am running D2G on stock ROM with root. SU does not ask for permission when I select this option on WL, so how does the program automatically assume I am not/can't use the root feature?
Thanks!
Have you installed busybox? That and superuser can tell you if you ARE rooted. If not, download SuperOneClick to your PC, connect your phone and run it. Make sure you have USB debugging mode on, but do not mount USB as mass storage. Don't hesitate to look for rooting help here or elsewhere (I.E. Droid Forums, Android Central)
Sent from my Droid using XDA App

[Q] How to enable usb tethering through adb and still have adb

I've been searching through the posts but I can't seem to find an answer.
I've found a post suggesting that the following should work: adb shell "echo 1 > /sys/class/usb_composite/rndis/enable"
When I try it, it says that the file/directory doesn't exist.
The post is also about a year old, so I didn't want to reopen an old thread.
Besides how to enable usb tethering through adb, I was wondering if it is possible to still use adb to connect to the phone while usb tethering is enabled. currently when I enable usb tethering through the phone, adb does not detect the phone anymore.
I saw a few posts saying that it is possible but their methods usually involve an app or buying an app. Is there a way to accomplish this without using an app?
Thanks for help
TKH1218 said:
I've been searching through the posts but I can't seem to find an answer.
I've found a post suggesting that the following should work: adb shell "echo 1 > /sys/class/usb_composite/rndis/enable"
When I try it, it says that the file/directory doesn't exist.
The post is also about a year old, so I didn't want to reopen an old thread.
Besides how to enable usb tethering through adb, I was wondering if it is possible to still use adb to connect to the phone while usb tethering is enabled. currently when I enable usb tethering through the phone, adb does not detect the phone anymore.
I saw a few posts saying that it is possible but their methods usually involve an app or buying an app. Is there a way to accomplish this without using an app?
Thanks for help
Click to expand...
Click to collapse
http://stackoverflow.com/questions/16631185/how-to-turn-wifi-on-using-adb-or-any-other-way-when-usb-debugging-is-disabled
do it through changing settings from adb

No MTP or PTP for Rooted Nexus 5?

I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!

how to access the data on a pattern locked phone with a broken and un responsive scrn

I'm trying to access the data on a Galaxy S4 on which the screen is not working at all(no backlight and doesn't respond to touch). the data I mainly require is the contacts.db file. what I have tried sofar: NOTE: USB Debugging is disabled .
1. tried to access the data via USB but cant access the content due to the lock on the phone.
2. tried to access the data with KIES but once again failed to do so due to the lock on the phone.
3. Downloaded the ADB shell and installed the required USB drivers but cant access the phone, when running the command "adb devices" it says no devices found which I think is because the USB Debugging setting on the phone is not enabled.
4. Also tried to sync with the Google account but unfortunately it was not setup to sync contacts with the Google account.
5. Tried to make use of apps such as MoboRobo and Droid Explorer but it does not work due to the USB Debugging that is disabled
Some other suggestions were to get another S4 and connect its screen to the one in question which I'm sure will work but is there no other way to access the data or to somehow remove the pattern lock from the phone? maybe using another platform to gain full access to the phone or anything?

Bugjaeger Mobile ADB App Running Directly on Android Phone - What Features?

I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: https://play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - user should be able to execute fastboot commands
Thanks
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
SaadatM said:
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
Click to expand...
Click to collapse
Not sure if I understand what you mean with "local terminal". .. Do you mean a shell spawned from regular app running on your phone?
The point of the app is to perform some privileged tasks that cannot be performed by regular apps on non-rooted phone.
You should be able to perform these tasks without the need to install ADB on your PC, or even without having a pc currently at your hands(e.g., if you're on-the-go).
Additionally, you should be able to perform a lot of these tasks with a couple of taps (instead of typing shell commands).
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
crunchybutternut said:
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
Click to expand...
Click to collapse
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
bugjaeger said:
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
Click to expand...
Click to collapse
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
Click to expand...
Click to collapse
If you made adbd listen on specific port before(adb tcpip 5555), then yes, you can issue adb commands from the app to the same device running the app.
bugjaeger said:
If you made adbd listen on specific port before(adb tcpip 5555), than yes, you can issue adb commands from the app to the same device running the app.
Click to expand...
Click to collapse
I believe you'd need root to do that though, right?
crunchybutternut said:
I believe you'd need root to do that though, right?
Click to expand...
Click to collapse
No, I don't think you need root. I used it a lot on my non-rooted Nexus 5x and once on an old Asus Zenfone during testing and it was working as expected.
That's great . I was just wondering if there was something like this already out there. Thanks for your efforts and I hope you are prosperous.
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I've added the possibility to copy apps/APKs between phones
Thanks
Click to expand...
Click to collapse
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
lodk said:
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
Click to expand...
Click to collapse
So you tried to connect your phone (with Bugjaeger installed) to you wife's phone via USB OTG cable? And the phone with Bugjaeger app doesn't detect any ADB device connection (or other dialogs pop up)? Did I understand this correctly?
You might need to temporarily disable the other protocols that Android offers via USB so that there are no other dialogs popping up (on your wife's phone). On my Nexus with Android 8, I can go to Connected devices -> USB and switch it to only "Charge this device" (so PTP or the other stuff is disabled).
In case there is some other app doing stuff with ADB USB devices, you might also need to change your defaults so that Bugjaeger can handle ADB USB devices.
Then you also need to make sure that Developer options are enabled on your wife's phone (and USB debugging of course).
Once you successfully connected and authorized the phone, you should do the following
- In Bugjaeger app switch to Packages tab and click on Add button top right (the button with the plus sign). Then you should pick the package disabler APK. This should install the package to your wife's phone
- Switch back to Commands tab (first tab) and either click on plus button in top right or shell into the device with the floating action button ("<>").
You can then activate the device owner with something like this
Code:
dpm set-device-owner disabler.package.name/.DisablerAdminReceiver
*Note that I don't prefix the command with "adb shell" here
When activating device owner you also need to make sure that there are no other accounts configured on your wifes phone (e.g. google account) because otherwise it probably won't work.
You can also check my blog post where I describe how to activate device owner with Bugjaeger in more detail (at the end of the blog post)
https://sisik.eu/blog/android/dev-admin/set-dev-owner
Hope that helps
going to give this a try thanks will post later with results,
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Crisal said:
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Click to expand...
Click to collapse
Hi,
Unfortunately, I don't think my app can help you in this case.
Hi, thanks for the reply. Do you know a way to help me?
please help me!!
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - for now the user can dump bootloader info
Thanks
Click to expand...
Click to collapse
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
I don't have any wear os watch at my hands right now and I can't test it at the moment. Is the APK compatible with the watch? If you're able to establish an adb connection between Bugjaeger and the watch, try to check the "Packages" tab in Bugjaeger app. There's a "+" button in the top toolbar, which allows you to select apk for installing on the target device.
The official docs are showing how to establish ADB connection with the watch - https://developer.android.com/training/wearables/apps/debugging
In Bugjaeger you then need to tap the connect button (plug with a plus sign in top toolbar), type in the IP address of the device, and tap on connect button. Both devices should be connected to the same WiFi network to make this work.
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
lindser112 said:
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
Click to expand...
Click to collapse
Perfect :laugh:

Categories

Resources