Hi all
I did not expect to have a true man in this embeded system but, is there somewhere ( or thru a free market app..) a list of commands that can be passed in a terminal window...
i've seen that some posts are talking about setInstallLocation...for example
if I try that in a terminal window, seems to be ignored...
I thought that busybox was supposed to give kind of a man...but not been able to install it...
Could someone enlight me a bit
thks in advance
( sorry for approximative english...lol)
I think that is a adb command and not a linux.
For a list of linuxc commands look here: http://ss64.com/bash/
Most of then should work in a terminal emulator.
Sent from my HTC Desire using XDA App
splendid...thks
well now, I know exactly what I am after...it is the list of ADB commands...
I'll go search for !!!
Related
So I 'm getting brave and decided I want to learn more about modding so that means I need to know at least the most basic of ADB commands.
Well I set up the Android SDK several weeks ago and to my best knowledge it was/is working i.e. from the command window (I'm using Win 7 so I use Shift-Right click to access in the Android sdk tools folder) I can type
adb devices
and my phone shows up.
From there I can type
adb shell
Now here is where it gets wonky
I can't use any adb commands or else I'll get an
"adb: not found" error
I can use the -ls command and a2sdcheck commands without any issues. I can even use the reboot and reboot recovery commands ONCE I don't use ADB in front of it.
So simple commands such as adb push/pull is off limits.
I have also tried in recovery mode but the same thing happens.
I'm sure I'm just missing something small but this is turning out to be really frustrating
And yes I do connect with Charge Only and USB debugging is checked.
Thanks in advance for any help
Sent from my PC36100 using XDA App
I could be wrong, but once you type adb shell I think you have to grant it Super user permission from the phone.
I just read the the SU log and didn't see a request resembling anything from adb or my computer. I also didn't notice a prompt to do so but wasn't really paying attention. I need to check on that but if someone else can clarify or tell me how to grant access that would be great. Thx for the response
Sent from my PC36100 using XDA App
Reconnected my phone and typed adb shell and there was no prompt for SU permissions. I'm thinking this may not be applicable or else you wouldn't be able to connect adb in recovery mode right?
Sent from my PC36100 using XDA App
Here is a tut on using adb. ADB Basics
I clicked on your link and it's taking me to a scanning app. Is that correct?
Nvm got it now
Sent from my PC36100 using XDA App
No it should take you to a thread here in XDA about ADB basics. That's where it takes me. Here try this: http://forum.xda-developers.com/showthread.php?t=694250
I found it in the development section in one of the stickies called
HTC EVO helpful/popular threads (Look here First!)
Babysitting my daughter right now so can't really read that link. I'm pretty sure I've read it before though.
Sent from my PC36100 using XDA App
Ok sorry I couldn't be more help. I am sure you are missing something very small because it sounds to me like it should be working. Make sure you have the right adb driver installed.
Moved to Q&A. This isn't development
Thx pulsar for the move. Sorry about that.
Housry thx for all your input.
I did read that link before and there was a link that confirmed that my ADB is set up correctly.
At the very first cmd prompt I can do adb devices and see my phone.
Then I can type adb shell and I get the # prompt
From there I can't issue anymore adb commands or else I get "adb: not found" error
I can issue reboot or reboot recovery commands BUT without adb in front of it and my phone will respond accordingly.
I can use the ls commands and search the subdirectories. Pushboot even works when I need to change my bootanimations. All this leads me to believe that adb is indeed set up correctly including the drivers so why doesn't the other adb commands work?!
This is really frustrating because I can't even begin to experiment with ADB if I can't get the most basic commands to function.
I know it's probably something small I'm missing and I hope someone will be able to point me in the right directions. Thanks again
Who knows, maybe this is a good thing. I might be able to get in all kind of trouble with my phone otherwise.
Wow on a whim I switched out the USB cable and now everything is working great. Geez.
Sent from my PC36100 using XDA App
ok, you are making a simple yet solvable mistake:
once you type adb shell, you are inside the phone's linux terminal. of course, your phone doesnt have adb in it. a shell is a great tool, and is used very, very often to diagnose problems, make stuff, incorperate stuff, test stuff. if you are in a shell, just type
exit
to get back out. then your adb commands should work.
So I just set up ADB (I THINK) can someone tell me if I did it correctly or not? When I typed in "adb devices" on the cmd thing a bunch of stuff popped up. After watching a video the guy said type "adb shell" for to test to see if it works and I got a msg saying "adb server is out of date. killing... *daemon started successfully"
So is my ADB set up properly so I can now begin rooting??
I dont recommend ADB try using this method.
http://forum.xda-developers.com/showthread.php?t=928160
Sent from my HTC Vision using XDA Premium App
what's wrong with ADB??
I would at least have it set up in case you need it before you root. It might save you from bricking (it has for me).
It doesn't sound set up correctly. When I run adb devices, it says the serial number, nothing else.
Sinistah_ said:
what's wrong with ADB??
Click to expand...
Click to collapse
ADB isn't required to root, and if you're having troubles and have no other need for the SDK or ADB, it can be a lot of unnecessary work.
for awhile it said it was incorrect or sumthin when I'd type "adb devices" into the cmd. Then when I messed with the path a bit and when I typed "adb devices" again, all this stuff popped up. Then I did the "adb shell" and that last thing popped up. What should I do??
martonikaj said:
ADB isn't required to root, and if you're having troubles and have no other need for the SDK or ADB, it can be a lot of unnecessary work.
Click to expand...
Click to collapse
so with this said, can I still use the method shown on wiki to root or do I have to do it the way with Visionary/Gfree??
Sinistah_ said:
so with this said, can I still use the method shown on wiki to root or do I have to do it the way with Visionary/Gfree??
Click to expand...
Click to collapse
I rooted my MyTouch4G with visionary/gfree/terminal emulator. No adb required but its a lifesaver if your phone can't boot!
well now I'm confused on what to do... Do I continue trying to fix this ADB problem or do I just do this other method everyones mentioning.
Sinistah_ said:
well now I'm confused on what to do... Do I continue trying to fix this ADB problem or do I just do this other method everyones mentioning.
Click to expand...
Click to collapse
They really aren't as separate of methods as you think. Every command you enter in ADB can be done by manually moving files into the proper locations, and executing commands via the Terminal Emulator app in the Market instead of the command window (via ADB) on your computer.
So when using the wiki instructions, instead of using cmd commands I use terminal emulator instead??
Sent from my T-Mobile G2 using XDA App
How am I supposed to do the first step on the wiki guide without abd??? I don't get it.
Sent from my T-Mobile G2 using XDA App
ok i want to know if anyone else has this, if so is there a way for my to turn it off or something, when i do adb shell it gives extra stuff like numbers and other stuff if doesnt just give me listing of files
to understand better look at picture
Those are the linux shell colour codes... for colouful text
unfortunately the windows cmd shell can't handle these.
This thread should hopefully sort you out.
HTH
thanks ! but this jus happen soon as i updated the stupid SDK,as well is there a Permanent fix for this for Windows cmd, instead my getting another terminal shell
so i gave that a try and all im getting is
not found
So does the link help or not?
Does this work for you ls --color=never
i knew that command for a temp color off but to have it fully off while in adb shell you have to do alias ls-'ls --color=never'
this is still a temp fix not a permanent one, i was hoping to find one but so far there is non other than using a different type of cmd prompt/terminal that supports it
Try what is mentioned in post 2 of that thread.
once you've done that, instead of typing ls
you would type ll (which just executes ls with the no color flag)
I just found this thread which may be of interest too.
Its an app called ansicon which will enable coloured output on a windows shell.
Just downloaded & tried it out... it works!
waydownsouth said:
Try what is mentioned in post 2 of that thread.
once you've done that, instead of typing ls
you would type ll (which just executes ls with the no color flag)
Click to expand...
Click to collapse
i did and i got
"not Found"
edit
Ok so i did the ansicon way, what i did was downloaded the right setup for my laptop X64
i placed it in my program files
then i ran ansicon.exe and terminal pop up
after that i did this in it
ansicon.exe -i
after i closed it and open regular cmd pmpt and did adb shell and BAM no more wacky characters shows colors in regualr cmd thnks and sweet
hi my htc desire keeps restarting when i flash any gingerbread miui rom i have tired data2ext and a2sd and have wiped and also formated my sdcard and stil have same problem with both but it works fine with all other roms and the froyo version of miui. please help
What hboot are you using and how did you root your phone?
Sent from my HTC Desire using xda premium
hi im using normal hboot-0.93.0001 i used unrevoked to root my phone i am not really a noob i have flashed and rooted many phones but for some strange reason all other roms including miui froyo work on my phone but gingerbread miui wont it loads up to the home screen and then just reboots ive tried data2et version and a2sd version and same thing happens with both versions.i have also tried using diffrent recoverys amon-ra,clockwork etc and still get the same problem.
You need to understand what is going on under the hood.. Getting an adb logcat is the way to go..
Code:
Windows>Start>Run
echo "null" > log.txt
start log.txt
adb logcat > log.txt
Use Notepad++ to associate with the txt file and reload the file every couple of seconds while keeping the cmd shell in the background.. See what's happening just before it reboots. It could be anything from a bad script to a bad module
Have you tried gingerbread 2.8, its simple and a very plain ROM, I have had issues with miui roms with my desire, if that doesn't work I will keep looking my self, sorry I'm not very insightful, you have an odd problem.
Sent from my HTC Pyramid using xda premium
Nice one Droidzone, I will have to try that also.
Sent from my HTC Pyramid using xda premium
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
casanova786 said:
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
Click to expand...
Click to collapse
Once you open a command line prompt in the folder where adb is installed (or anywhere else, if the file adb.exe is in your Windows path variable-Dont worry about that if you dont know), you can directly type each line of the commands starting from step 2.
Before that, install Notepad+, and associate .txt file to open with it by default..
By the way, you have to start typing those commands directly after rebooting from recovery after installing the Rom..
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.also i typed the commands u gave me once in adb and it says "the process cannot access the file because it is being used by another process."
casanova786 said:
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.
Click to expand...
Click to collapse
Hmm.. I seem to be offering more Windows support than Android!
I meant Notepad+. Hold Shift, rightclick any text file, Choose Open with Notepad+ as default. You can go to your adb folder like you normally do and then type each line I posted and hit Enter after each time. You can also make a batch file with all those commands (search Google for that if you dont know how)
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
casanova786 said:
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
Click to expand...
Click to collapse
Hmm yes, that can happen if you have more than one adb.exe process running in the background because you exited it by closing the command shell with the close button instead of typing
Code:
exit
after done with it.
Use Ctrl+Alt+Del or Process Explorer to terminate the background adb.exe processes
Hi, I don't have this really clear.
BusyBox is needed for terminal emulator. Now... I guess that in that terminal you enter commands, but, what commands? Do you guys have a list or at list some examples to know if it is like a pc: regedit, or cmd>ipconfig ...
And what is the use of Busybox besides a base to the terminal emulator?
Thanks
Arturofm2 said:
Hi, I don't have this really clear.
BusyBox is needed for terminal emulator. Now... I guess that in that terminal you enter commands, but, what commands? Do you guys have a list or at list some examples to know if it is like a pc: regedit, or cmd>ipconfig ...
And what is the use of Busybox besides a base to the terminal emulator?
Thanks
Click to expand...
Click to collapse
Ok so I may be off on these... but this is my current understanding anyway (and please correct me folks if I'm wrong) -
- Busybox is a binary that contains within it a number of functions more commonly seen in linux environments (the "toolbox" android stock roms come with is rather limited in this sense)
- This "busybox" binary, when installed, makes it so you can do a number of the common-to-linux-terminal-environment commands you would have available to you if you were running some flavor of a linux distro - things like cp, mkdir, chmod, etc.
The commands are then accessible via something like terminal emulator (by its own name it's basically emulating a linux terminal environment) and are essentially the same as what you would have on any basic linux distribution, though sometimes they won't have all the extended functionality (via flags and what not) that you would normally see.
Hope that helps
dwitherell said:
Ok so I may be off on these... but this is my current understanding anyway (and please correct me folks if I'm wrong) -
- Busybox is a binary that contains within it a number of functions more commonly seen in linux environments (the "toolbox" android stock roms come with is rather limited in this sense)
- This "busybox" binary, when installed, makes it so you can do a number of the common-to-linux-terminal-environment commands you would have available to you if you were running some flavor of a linux distro - things like cp, mkdir, chmod, etc.
The commands are then accessible via something like terminal emulator (by its own name it's basically emulating a linux terminal environment) and are essentially the same as what you would have on any basic linux distribution, though sometimes they won't have all the extended functionality (via flags and what not) that you would normally see.
Hope that helps
Click to expand...
Click to collapse
Thanks dwitherell, I also found this: http://forum.xda-developers.com/showthread.php?p=31500912, I thought it was something else, but I think I won't need it because most apps do this with a graphical environment.
If you want to know the list of commands/applets simply browse to
/system/xbin from the terminal emulator and run ls command to list all installed applets.
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
If you want to know the list of commands/applets simply browse to
/system/xbin from the terminal emulator and run ls command to list all installed applets.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Just typing busybox will list them all out as well
Please help correct these errors