Getting adb shell to work in Ubuntu with my Droid - Motorola Droid and Milestone General

Hello, I recently got Ubuntu installed on my computer. I got the Android SDK set up on it, but I cannot get adb shell to work, everytime I try it this happens:
[email protected]:~$ adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: insufficient permissions for device
Click to expand...
Click to collapse
This never used to happen on windows, does anyone have any idea on how to fix it?

Have you tried running it as root? It tells you in the error message that you've got insufficient permissions...
Sent from my Droid using XDA App

Related

adb question

is there a command in adb shell to remove a whole directory? i tried the rm command and it didnt work
try
Code:
rm -r /dir
you need to delete dirs with explicit recursion.
kendong2 said:
try
Code:
rm -r /dir
you need to delete dirs with explicit recursion.
Click to expand...
Click to collapse
thanks, ill give it a try
If there is nothing in the directory try...
rmdir nameofthedirectory
** sorry double post**
i didnt want to make a new thread for MY adb question, so i decided to post it here for anyone to help me figure it out. Just so you know adb was working fine and ok awhile ago.
Lately with adb ive been getting some weird early adb command errors.
this is the jist of what i get:
((Phone is connected to computer and USB debugging is on))
C:/Androidsdk/tools/adb devices
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
((then i try again))
C:/Androidsdk/tools/adb devices
adb server is out of date. killing...
* daemon started successfully *
list of devices attached
HT99******* device
It used to just give me my device number right after the command, i never used to get that adb server out of date thing. anyone know why i am getting this new line?
happens to me when using eclipse.
I think the ADB server out of date is because ADB has been running for a long time without anything using it.
and how do i fix this do you think?
re download the sdk? or what?
frostrunner said:
and how do i fix this do you think?
re download the sdk? or what?
Click to expand...
Click to collapse
I am having the same issue. I have SDK 1.5 and Eclipse on Win Vista. Anyone how to fix "adb server is out of date. killing..." issue?

ADB Root no longer works

I recently put the final release of Froyo on my Droid, I wanted to remove the apps that come with it so I loaded up Command prompt and the SDK tools. Apon trying to start adb in superuser mode, I got this message:
C:\Users\Chandler Paul\Documents\android-sdk_r06-windows\android-sdk-windows\tools>adb root
* daemon not running. starting it now *
* daemon started successfully *
adbd cannot run as root in production builds
Click to expand...
Click to collapse
Does anyone know what the problem might be? I run Froyo 2.2 FRF84B on P3Droid's 250-1250 MHz kernal (rooted).
Same thing happened to me too. One thing I've been meaning to try, but haven't had time to, was to download the 2.2 SDK from the 'android' app in the 'tools' directory. I'll give it a shot when I'm at my PC and post the results in a bit.
Sent from my Droid using XDA App
209pcs said:
Same thing happened to me too. One thing I've been meaning to try, but haven't had time to, was to download the 2.2 SDK from the 'android' app in the 'tools' directory. I'll give it a shot when I'm at my PC and post the results in a bit.
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Doesn't make a difference, I already tried
stephen730 said:
same here. It was like that when I first rooted BEFORE i flashed to 2.2 froyo. But I was able to do 'adb shell' and su into it.
Click to expand...
Click to collapse
Yeah, but then I can't use adb remount :\

Please Help!

Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
TomCarter21 said:
Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
Click to expand...
Click to collapse
Do the "factory reset". Erasing all data of course...
To try factory reset from recovery menu
1. turn off the phone
2. press vol down + power
3. waiting vibrate 2 times and release button
4. choose wipe data/factory reset
after that re-root again
don't forget setting debugging mode
before root.
Sent from my LG-P880 using xda app-developers app
First step would be to disconnect any other Android device.
Second one, put the phone to Airplane mode, you can do with some patience even with the SystemBackup.apk installed. Switch USB mode to "charging only".
If that doesn't help, you can still do a reset.
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
XperiaPlayer said:
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
Click to expand...
Click to collapse
Sorry @XperiaPlayer but, I don't have the Android SDK installed, and my root goes perfect...
You're sure that matters?
Regards
Shift + right click the folder where the root.bat is located and type adb devices (or adb.exe devices) and paste the output here.

[Q] No OS Installed, Can't access phone on PC

I accidentally deleted my data and it says "No OS installed". When I plug in the phone to the PC and I check devices it only displays "Android Phone" and I cannot access the phone itself from the PC.
How am I suppose to sideload if I cannot access it in the first place? :[
eXileris said:
I accidentally deleted my data and it says "No OS installed". When I plug in the phone to the PC and I check devices it only displays "Android Phone" and I cannot access the phone itself from the PC.
How am I suppose to sideload if I cannot access it in the first place? :[
Click to expand...
Click to collapse
From recovery. Look for adb push or adb sideload commands
SaHiLzZ said:
From recovery. Look for adb push or adb sideload commands
Click to expand...
Click to collapse
I see ADB Sideload in TWRP.
eXileris said:
I see ADB Sideload in TWRP.
Click to expand...
Click to collapse
this is from the AT&T forum, but the procedure is the same:
http://forum.xda-developers.com/showthread.php?t=2318497
you need adb 1.0.31 to use sideload
you can check your adb version with this command:
Code:
adb version
alray said:
this is from the AT&T forum, but the procedure is the same:
http://forum.xda-developers.com/showthread.php?t=2318497
you need adb 1.0.31 to use sideload
you can check your adb version with this command:
Code:
adb version
Click to expand...
Click to collapse
Yeah I have that exact version. However, I just tried to sideload the zip and it gave me an
Code:
* daemon not running. starting it now on port 5037
* daemon started successfully *
error: device not found
What do I do from here?
2137
eXileris said:
Yeah I have that exact version. However, I just tried to sideload the zip and it gave me an
Code:
* daemon not running. starting it now on port 5037
* daemon started successfully *
error: device not found
What do I do from here?
Click to expand...
Click to collapse
Update: Fixed it. Turns out I did not have the HTC drivers installed on my PC. Thank you everyone that replied. :laugh::highfive:

ADB not recognized

Hi, I've tried 4 computers and 3 cable, still, they can't recognize my Xiaomi MI A2. At first, the device appears but as I try a single command it doesn't detect it. After one command i try the ADB devices and nothing appears. I've tried kill and start server but it's the same.
When I get it: * daemon not running; starting now at tcp:5037
* daemon started successfully.
However, after the first command, this happens: no devices/emulators found

Categories

Resources