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
Related
the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.
Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.
I have the same problem... working on it now...
I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.
It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Thank you dagentooboy!
Can someone explain this for this not so savvy person?
chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.
Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.
yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.
Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..
check too make sure your Android isnt listed under usb mass storage devices in device manager.
Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.
my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this
Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
I posted this question over on Phandroids but this forum seems perhaps more appropriate. My Lenovo laptop running XP sees my phone just fine (Samsung Gravity Smart SGH-T589) and I'm able to transfer files to/from the phone. However, adb doesn't seem to be able to see it. A search about this problem turns up solution suggestions that mostly involve drivers, but my Samsung driver is up to date and clearly working (or else the phone wouldn't show up to Windows and I wouldn't be able to transfer files). My phone is rooted, which also makes it obvious that my laptop can talk to it just fine -- I used OneClick to root it last week using the same computer.
I'm using the DOS prompt (cmd) to run adb, and adb works fine. It simply doesn't see any devices. Here's an actual text transcript:
===============================
C:\Android\adt\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Android\adt\sdk\platform-tools>adb shell
error: device not found
C:\Android\adt\sdk\platform-tools>
===============================
Any ideas? I'm pretty new to this, so perhaps I'm missing something really simple. I hope so anyway!
--
Craig
Sunnyvale, California
Make sure that USB debuggin is enabled on your device. (This option should be changed only while device is disconnected from USB).
Also, try to restart adb server by killing it from the device manager.
Thanks for the suggestions. I had indeed already done both of those things. USB debug must be enabled to do file transfers, so I already knew it was definitely on. I still cycled it off/on anyway to make sure. And I did both kill-server and start-server commands as part of my checkout to assure myself that adb was in fact working correctly. I had Windows task manager up as well so I could watch adb disappear and reappear with those commands.
--
Craig
Sunnyvale, California
Hmmm... Try to reboot both your computer and device.
Have you tried to connect other devices to ADB? May be there is a problem with ADB installation?
Phone and laptop have both been rebooted many times. I also tried it with the phone in charge-only mode because that's what One Click Root required, but nothing changed. I also tried using all of the different USB ports on my laptop and tried two different USB cables, although that was silly because the phone is obviously talking to the laptop via USB. It shows up in file explorer, and I am able to transfer files using Windows drag and drop.
I'm afraid I have only one device, my recently rooted Samsung Gravity Smart phone, so I can't try it out on anything else.
I'm not sure how the adb installation could be at fault since the commands work as long as they don't involve the USB port. And I know that it MUST be possible to shell to the phone with what's already on this computer because One Click did it. I tried running the adb commands from the One Click Root > ADB directory just in case something about that particular install of adb was different, but I got exactly the same result.
It seems to me that I must be failing to do some setup step that an experienced Android developer might know about. I've never done anything like this before, so I wouldn't have even known about downloading the Android sdk if it weren't for forums like this! I sure appreciate the community of knowledgeable people here, who are clearly willing to help newbies like me.
If there are any software tools that anyone can suggest using to help me figure out what's going on, please let me know.
EDIT: Is there something that I need to load on my phone before adb will work? It occurs to me that OneClick might push something to the phone when it does the root, then delete it when the task is complete. I tried using QTadb, which is an adb GUI, and got the same result: no devices seen on the port even though Windows sees my phone and can talk to it via USB.
--
Craig
Sunnyvale, California
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.
Hi
Has anyone tried the XDA Navigation gestures app on the Nokia 7 Plus? If so can you guide me through the process that involves granting permission via adb. I did follow the steps as mentioned, but I am not seeing the desired results.
Thanks
I tried that too. I got "permission denied" or something like that.
yes, i use it without problem, with "8.1 June" and also "P DP2rev2"... for grand use exactly adb command what app show, if you have any problem then i think is with non functional adb and/or with badly rewrite adb command, try post output from terminal/command_prompt after you second try it
btw: you have enabled USB Debuging in Developer Settings on phone right?
edit: info about installing adb is here
I had a problem using the ADB. It kept saying "adb" wasnt a correct command. But I figured out that I had to type ".\adb" to make it work
Using it here without any major issues except sometimes a bit laggy