simply digit "adb hell" instead of "adb shell"...
It just brought up the help screens for me, just like it does for anything else it doesn't understand. Did you get something different?
There's adb lolcat too
on android sdk for linux this print first lines of adb shell with a red style.... it's all...
Related
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.
First off, I'm fairly new to the Droid X and this is my second android phone(the first was an Eris which should be kinda obvious). I am rooted but, for whatever reason, I cannot run the adb remount command from the prompt. I can run other commands like adb shell bootanimation which runs my boot animation and when i enter in adb shell it returns a $. $ does mean rooted, correct?
Also, when i try to run the sdk manager i get the "java not found in your your path" The weird thing is that it is in the path. So i'm getting frustrated now and I know it is probably something simple that i am overlooking.
If anyone can help out, I would greatly appreciate the help.
DroidEris1981 said:
First off, I'm fairly new to the Droid X and this is my second android phone(the first was an Eris which should be kinda obvious). I am rooted but, for whatever reason, I cannot run the adb remount command from the prompt. I can run other commands like adb shell bootanimation which runs my boot animation and when i enter in adb shell it returns a $. $ does mean rooted, correct?
Also, when i try to run the sdk manager i get the "java not found in your your path" The weird thing is that it is in the path. So i'm getting frustrated now and I know it is probably something simple that i am overlooking.
If anyone can help out, I would greatly appreciate the help.
Click to expand...
Click to collapse
$ does not mean rooted. from that prompt you can enter 'su' and you should get an '#' and then you are using root.
However, by default, the ADB daemon is not running with root privileges. Thus when you try to ADB remount it gets denied.
You need to run a 'Root Elevated' adb daemon. Or you can manually remount the /system partition from adb shell.
Why does the Droid X Recovery Bootstrap start on boot?
As mentioned above, it needs to log that your phone booted successfully and recovery mode is not necessary. It also replaces your "adb daemon" with one that has root permissions, allowing for easier usage of the adb command.
Click to expand...
Click to collapse
I know that if you install/run DroidX Bootstrapper (which installs the ClockworkMod Recovery) it also sets up a root elevated ADB daemon. You will need to reboot after installing before this takes effect.
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
- the app does not give you a root option - it only guides you what to do
- have you followed all steps ?
adb shell chmod 777 /data/local/tmp
adb install BurritoRoot3.apk
<go open the app now>
adb shell /data/local/tmp/BurritoRoot3.bin --root
adb shell /data/local/tmp/BurritoRoot3.bin --install
maybe you have to do the adb commands with ./ in front (eg ./adb whatever)
t4nn3d1n said:
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
Click to expand...
Click to collapse
You have to make sure that you do this command:
adb shell chmod 777 /data/local/tmp
Otherwise it will not make a "BurritoRoot3.bin" file, which means no root.
Install the BurritoRoot3.apk on your kindle, and go into the app.
After that is finished, input:
adb shell /data/local/tmp/BurritoRoot3.bin --root
Then:
adb shell /data/local/tmp/BurritoRoot3.bin --install
I found http://forum.xda-developers.com/showthread.php?t=1410223 which has that chmod command in it. Naturally I found that thread 10 minutes after I posted and was so dumbstruck with myself that I didn't post a reply to my own post.
The device is rooted now and I installed the Alpha Release of MIUI 4.0.? and naturally a few things don't work. Trying again with MIUI's 2.3 stable release (don't know the version number off the top of my head)
Thanks for the quick reply and looking out
So I'm in my platform-tools directory in the terminal, and here is how my commands go
./adb devices
returns List of devices attached
015d18ad5a27fe04 device
so then I go
./adb reboot bootloader
and my Nexus reboots into the bootloader. And then I enter
./adb devices
And there is no device listed. When I type in
./fastboot oem lock
it returns
<waiting for device>
and it hangs here until I control-c out. Am I missing something? I really hope it's not a syntax error
any help would be appreciated. Also, please note that I am in Ubuntu 12.04 on a native installation, so it isn't a driver issue
Silly question, but did you sudo?
thebobp said:
Silly question, but did you sudo?
Click to expand...
Click to collapse
As a matter of fact, I didn't :crying: I had to kill the server and when I did I left su. That's even more humiliating than a syntax error :crying: thanks for the help
Running with instructions here:
http://wiki.cyanogenmod.org/wiki/HTC_Glacier:_Full_Update_Guide#Rooting_the_HTC_Glacier
but after going into adb shell and running:
adb push busybox /data/local/tmp/
I'm getting a "permission denied" error for any adb for that or any adb command I throw at it.
I do notice that my adb shell starts with $ instead of # but not sure what step I'm missing. Any help would be greatly appreciated. Trying to breath new life in this thing and don't have any account/market setup on it - so if I can do the rooting through this it'll be easier for me otherwise I'll go ahead and setup another G-account to do it that way if I have to :\
Try executing "adb shell mkdir /data/local/tmp" and try again.
If doesn't work - try changing all /data/local/tmp references to /data/local
thanks for the feedback Jack_R1
Unfortunately that's a no go... same error even with that
Then you're doing something wrong. Follow the guides EXACTLY. Don't do stuff that's not written, do the stuff that's written EXACTLY as it's written, verify that you're starting where the guides expect you to and have all the prerequisites, and it'll work. Your phone isn't different from any other phone, and if something that works for million others doesn't work for you - then you're doing something wrong.
For example, nobody asked you to get into ADB shell to run these commands you're running. You can't run "adb" while being inside ADB shell. Read the guide PROPERLY.
Jack_R1 said:
Then you're doing something wrong. Follow the guides EXACTLY. Don't do stuff that's not written, do the stuff that's written EXACTLY as it's written, verify that you're starting where the guides expect you to and have all the prerequisites, and it'll work. Your phone isn't different from any other phone, and if something that works for million others doesn't work for you - then you're doing something wrong.
For example, nobody asked you to get into ADB shell to run these commands you're running. You can't run "adb" while being inside ADB shell. Read the guide PROPERLY.
Click to expand...
Click to collapse
Thanks,
I did try to follow things to the T but diverted away from doing things -exactly- since starting with "adb push busybox /data/local/tmp/" command I keep getting a "cannot stat 'busybox': No such file or directory"
So in reality.. .THAT was my main issue which is leading to me trying other stuff such as the "adb shell" and not getting # (since I'm pushing files to gain root)
Turns out I'm now able to get "adb push" working on my files since.. I hate myself for it being this simple... I just had to "CD" into my /platform-tools folder since command prompt started in my documents folder by default thus it was looking there for my files
Welp, thanks for the help anyway. Seen this question lingering around in Google Search and hope this helps out someone else :good: