is it possible to use adb from the transformer, to connect to an other adb device? (that would be my phone)
when I connect my phone to the usb port of my tf (on the dock) and then I type adb devices in a shell here is what I get:
[email protected]:/ $ adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ $
I've done it before. Not sure why it isn't working for you. Double check that debugging is enabled on your phone. You also may need to be root to use adb on the TF. Type "su<enter>" to get root in your terminal, then try adb.
If your TF isn't rooted, then you need to do that first.
never mind, I just needed to adb kill-server after getting root
it works now
Related
when i type
adb devices
adb shell
or
adb remount
i get starting daemon
failure to start daemon
please help
i just had the same problem.
i unistalled the phone drivers and i installed htc sync
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
make sure you delete your drivers!
i used USBDeview
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
I've searched a lot, but did not find a solution.
When I connect my HTC Kaiser with Android Ion 1.5 on the top to my Linux box (all UDEV settings are as recommended), the adb utility (launched as root) does not recognize it correctly. It shows a set of questionmarks instead of the device name:
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? device
adb basic commands (pull/push/install/shell) work, though, but DDMS does not work and I can't debug my application when the device is attached.
Does somebody have a solution?
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
it is root
Super Jamie said:
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
Click to expand...
Click to collapse
Like I mentioned in my question - I do run adb as root.
When it's launched not as root, I can not even do "adb shell" and
"adb devices" shows:
"????????????? Permission denied". So, it is root, I assure.
BTW, on my work Windows 2k3 machine I can use ddms, but
"adb devices" still shows some garbage letters instead of the device name.
Sorry for my English, if my explanation is not clear.
OK, I am trying to root my Nexus 4. What follows is a pretty comprehensive description of what I've done but the TL;DR version is that I managed to unlock my nexus4 using fastboot oem unlock -- but now fastboot and adb are very consistently (across different computers and different cables) not picking up my nexus4 anymore. I did check out MTP mounting, and that's successful. It could be that I'm misunderstanding something, but this is getting kind of frustrating. I have been using information from three or four different tutorials here on xda. So anyway, here's the grisly details:
I am running Ubuntu 12.04 (32 bit on my laptop, 64 bit on my desktop).
Now, on the LAPTOP:
Firstly I powered up my N4 (vol down + power) to get the LOCK STATE - locked information. I connected to the laptop via USB port with the cable supplied with the N4.
I went to the adt.../sdk/platform-tools (from unpacking the ADT bundle archive) directory on my laptop.
Code:
[email protected] $ sudo ./fastboot devices
this gave me a string of numbers followed by fastboot in response. [Note that this is the one and only and ever time I sucessfully listed the N4.] So far so good. Then
Code:
[email protected] $ sudo ./fastboot oem unlock
...
Again so far so good. After answering yes to the unlock question on the N4, the N4 now shows LOCKED STATE - unlocked.
Now here is where it got weird. I wanted to start up adb, so
Code:
adb devices
daemon not running, starting on 5037
list of devices attached
... and no devices. Repeated with sudo, no difference (except daemon already running. Huh.
The above is from my written notes. More detail below on the desktop as I've got all this in another window here.
That was yesterday. So then I checked with my desktop today. This is what's on my desktop:
Code:
[email protected]:~$ uname -a
Linux desktop 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:42:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I downloaded the ADT Bundle. (I notice that despite checking the 32 bit on download, it seems to have given me the 64 bit version. Hm...)
Code:
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ ls
aapt aidl dexdump fastboot llvm-rs-cc renderscript
adb api dx lib NOTICE.txt source.properties
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ sudo ./adb devices
List of devices attached
I changed the USB cable and repeated, same results. Is it the N4?
This computer wasn't set up with MTP, so I did that quickly:
Code:
[email protected]:~$ cd /etc/udev/rules.d/
[email protected]:/etc/udev/rules.d$ sudo vi 51-android.rules
[sudo] password for digitalramble:
[email protected]:/etc/udev/rules.d$ more 51-android.rules
# nexus 7
SUBSYSTEM==”usb”, ATTR{idVendor}==”18d1”, ATTR{idProduct}==”4e41”, MODE=”0666”,
OWNER=”digitalramble”
# nexus 4
SUBSYSTEM==”usb”, ATTR{idVendor}==”1004”, MODE=”0666”, OWNER=”digitalramble”
[email protected]:/etc/udev/rules.d$ sudo service udev restart
udev stop/waiting
udev start/running, process 6945
And then installed the mtp software
Code:
[email protected]:~/$ sudo apt-get install mtp-tools mtpfs
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ sudo mkdir /media/nexus4
digit[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ sudo chmod 755 /media/nexus4
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ sudo mtpfs -o allow_other /media/nexus4
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$ ls /media/nexus4
Alarms DCIM Movies Notifications Playlists Ringtones
Android Download Music Pictures Podcasts
[email protected]:~/SDK/adt-bundle-linux-x86_64/sdk/platform-tools$
So I can't figure out why fastboot or adb won't list my N4? I've swapped out computers, cables, everything but the N4 itself. Yet, the N4 is working otherwise normally (it's doing what I expect on the screen, it can be listed via MTP tools. But if fastboot won't see it, how can I proceed with fastboot flash recovery recovery.img, or or fastboot boot boot.img or whatever? I was going to try to play with adb push/pull instead but neither of them are listing the N4 when I check...
Thanks for any ideas...I'm stumped. I've tried to include all the relevant bits of information.
What state is the phone in when you are trying adb? adb only works when youre in the actual OS (or recovery) and fastboot is for bootloader commands.
IINexusII said:
What state is the phone in when you are trying adb? adb only works when youre in the actual OS (or recovery) and fastboot is for bootloader commands.
Click to expand...
Click to collapse
I'm not entirely sure what you mean by "actual OS". I have the N4 plugged in, turned on, MTP media set, on the default home page with the clock and play icons, etc. I've tried to make sure it hasn't timed out or gone to sleep on the fastboot or adb commands.
It doesn't have a sim card. Is that an issue? Should still be functional, I thought.
i meant when you're booted into Android you can use adb. fastboot commands only work when youre in the bootloader
is developer mode / usb debugging enabled?
IINexusII said:
i meant when you're booted into Android you can use adb. fastboot commands only work when youre in the bootloader
is developer mode / usb debugging enabled?
Click to expand...
Click to collapse
Hrm. I may be a pretty seasoned unix admin, but I actually am not up on some of the android based terminology. I literally do not know what you mean by "when you're in the bootloader" or "booted into Android". Can you explain further or point me to something (not a video, please, I'm deaf) that does? Oh -- is that the mode you're in when you power up via VolDown + Power ??
I did enable the usb debugging thing (tapping seven times on the build number) on the N4 (which is JB 4.2.1).
(as dhayman11 pointed out, "unknown sources" is in security settings, not developer options. but no luck anyway, like most of the settings app, it also crashes if you try to set it.)
instead, here is an extremely stupid idea that just came to me.
1. turn on adb wifi debugging
2. sideload your favorite terminal, e.g.
http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk
(ok I lied. you will need your desktop/laptop/phone/whatever, exactly 1 time. step 2 will be skipped forever after that 1 time.)
3. fire up said terminal from the settings->applications menu.
4. (LOL!)
$ adb devices
4a. if the above command shows no devices,
$ adb connect localhost
and proceed to step 5.
4b. if the command shows exactly 1 device, e.g. "emulator-5554", proceed to step 5.
4c. if the command shows more than 1 device (wtf?!) then you will need to specify a device of your choice ("-s somedevice") in every subsequent adb command, e.g.
$ adb -s emulator-5554 <whatever>
$ adb -s localhost:5555 <whatever>
etc.
5. e.g.
$ adb install /sdcard/Download/foobar.apk
$ adb shell
$ adb uninstall -k com.something.somethingelse
etc. etc.
6. profit? profit!
ok here is a slightly-less incoherent form of the senior-moment-reply I posted earlier
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!