Related
Some of you are familiar with the adb install command.
Is there an equivalent of it in the terminal emulator?
Hi,
Adb is used from the computer and terminal emulator is used from the phone.
What are you trying to do?
I'm trying to install an app without using astro.
your best choise would be
cd to the location of the apk file and use
adb install appname.apk
or adb install C:\folder\appname.apk
think thats the correct way im not sure how you can install it in the terminal i knwowho to remove it.. but not install :/
Install .apk via Terminal EMulator
1) Place the .apk on the root of your SD card (for simplicity)
2) Type "su"
3) cd into the destination of your .apk (in this case it will be cd /sdcard)
4) Use "install "name of .apk" /"destination"/"name of .apk"
su
cd /sdcard
install com.makemobile.coursepro.apk /system/app/com.makemobile.coursepro.apk
further example:
install "space" com.makemobile.coursepro.apk "space" /system/app/com.makemobile.coursepro.apk
This will install the app on your phone using the Terminal Emulator. The destination location can change as well.
Additional help: http://www.busybox.net/downloads/BusyBox.html
On the flip side, could you uninstall from the ext2 partition this way?
install on/from ext2
not sure...I'll looks into this. I had my apps and data on my sd however, it seemed a little buggy and inconsistant. It may have been due to using original G1 1gb class 2 card.
-let me know if you find out first.
a1t said:
1) Place the .apk on the root of your SD card (for simplicity)
2) Type "su"
3) cd into the destination of your .apk (in this case it will be cd /sdcard)
4) Use "install "name of .apk" /"destination"/"name of .apk"
su
cd /sdcard
install com.makemobile.coursepro.apk /system/app/com.makemobile.coursepro.apk
further example:
install "space" com.makemobile.coursepro.apk "space" /system/app/com.makemobile.coursepro.apk
This will install the app on your phone using the Terminal Emulator. The destination location can change as well.
Additional help: http://www.busybox.net/downloads/BusyBox.html
Click to expand...
Click to collapse
nevermind..........used astro file manager and it worked fine
help
what's 'cd' ? the emulator is already installed on the phone ?
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
MikeMadden said:
what's 'cd' ? the emulator is already installed on the phone ?
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
Click to expand...
Click to collapse
cd is a command, meaning "change directory". Which is used to move your location on the system.
MikeMadden said:
what's 'cd' ? the emulator is already installed on the phone ?
Click to expand...
Click to collapse
cd is a *nix command , it is short for 'change directory' and it... changes directory
MikeMadden said:
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
Click to expand...
Click to collapse
it depends on what the app is
your best bet would be to get an app called 'Astro file manager' from the market
Its quite easy, so I won't go into further detail
Which to be honest is a fair trade
APrinceAmongMen said:
Some of you are familiar with the adb install command.
Is there an equivalent of it in the terminal emulator?
Click to expand...
Click to collapse
Some people have mentioned the `install' command from BusyBox, but this won't quite do what you probably want. To invoke the full Android package installation experience--the complete equivalent of `adb install'--you're looking for `pm install'. It takes the same arguments that `adb install' does, checks signatures, creates the appropriate user accounts, etc. so the package is installed the Android way. You can also use `pm uninstall' to remove a package (and as with `adb install', the "-k" option keeps its data around).
The `am' and `pm' commands are both underdocumented, but can be terribly useful. `am' can issue arbitrary Intents, including some Extra values. `pm' has other features not mentioned here, but which are shown in the help text.
olearyp said:
Some people have mentioned the `install' command from BusyBox, but this won't quite do what you probably want. To invoke the full Android package installation experience--the complete equivalent of `adb install'--you're looking for `pm install'. It takes the same arguments that `adb install' does, checks signatures, creates the appropriate user accounts, etc. so the package is installed the Android way. You can also use `pm uninstall' to remove a package (and as with `adb install', the "-k" option keeps its data around).
The `am' and `pm' commands are both underdocumented, but can be terribly useful. `am' can issue arbitrary Intents, including some Extra values. `pm' has other features not mentioned here, but which are shown in the help text.
Click to expand...
Click to collapse
'pm install' often fails with [INSTALL_FAILED_INSUFFICIENT_STORAGE]
which used to frustrate me no end ..
simple shell script
Code:
am start -a android.intent.action.VIEW -t application/vnd.android.package-archive -d file://$1
just pass the full path e.g
sh /sdcard/installapk.sh /sdcard/theapp.apk
and it pops up the Android Package installer
Firerat said:
'pm install' often fails with [INSTALL_FAILED_INSUFFICIENT_STORAGE]
which used to frustrate me no end ..
Click to expand...
Click to collapse
Interesting. I wonder if that's related to A2SD or a particular implementation, and pm getting confused as a result? Still, I like the idea of sending the VIEW intent to bring up the package installer. Good snippet.
I just cp the files to /system/sd/app/
from Windows Command prompt, and after switching to the folder containing the .apk file, type:
adb install filename.apk
if it is a reinstall:
adb install -r filename.apk
you could also push the file to the app folder. I use this method to push system apk:
adb remount <<<< you have to remount since you're going to mess with a sys folder
adb push filename.apk /system/app
seriously useful thread... especially after for some weird reason certain apps fail to install using the default Android installer. *cough* Radiant *cough*
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Example -
su
cd /sdcard
pm install AstroFileManager.apk
Hope that can help!
rajasyaitan said:
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Hope that can help!
Click to expand...
Click to collapse
This is very helpful, thanks!
rajasyaitan said:
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Example -
su
cd /sdcard
pm install AstroFileManager.apk
Hope that can help!
Click to expand...
Click to collapse
Thanks big time. Installed perfectly although apk won't open...just got to find one that will.
After installing the JH2 ROM and using unleash the beast, I'm getting weird output from the ls command in the adb shell. Apparently, I can't post links or pictures, yet. So, here's a sort of link:
picasaweb. google. com/ lh/ photo/ VQKACQqA9i7u8ZWG3OmRGQ?feat=directlink
I'm getting listings of entries like [1;34mcache [0m
and [0;0mdefault.prop [0m
before each of the square brackets, there is a left-pointing arrow.
What's causing this? It seems to be an expanded version of the directory listing. How do I turn it off?
belyle said:
After installing the JH2 ROM and using unleash the beast, I'm getting weird output from the ls command in the adb shell. Apparently, I can't post links or pictures, yet. So, here's a sort of link:
picasaweb. google. com/ lh/ photo/ VQKACQqA9i7u8ZWG3OmRGQ?feat=directlink
I'm getting listings of entries like [1;34mcache [0m
and [0;0mdefault.prop [0m
before each of the square brackets, there is a left-pointing arrow.
What's causing this? It seems to be an expanded version of the directory listing. How do I turn it off?
Click to expand...
Click to collapse
thats normal...
designgears said:
thats normal...
Click to expand...
Click to collapse
When I was using the original kernel and the one-click root, my adb shell ls was only file names, not the extra stuff. When I use the ls command in terminal emulator on the phone, it's just the file names.
Also, when I grep the output of ls, the output of grep doesn't have the info in the square brackets, just the file name(s) that meet the criterion.
Thats the ls command sending color codes. It looks nice on a terminal that supports it but weird on windows.
To temporary solve it, after adb shell do this:
alias ls='ls --color=never'
It will fix the problem until you exit adb.
Sent from my SAMSUNG-SGH-I897 using XDA App
LGSilva said:
Thats the ls command sending color codes. It looks nice on a terminal that supports it but weird on windows.
To temporary solve it, after adb shell do this:
alias ls='ls --color=never'
It will fix the problem until you exit adb.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
This was it. Thank you very much. I'm not sure why I didn't see the extra info on my other ROM, but there it is.
I don't suppose there's a different terminal/command prompt for windows that would show the colors?
ls -l
will just give you a standard list of files.
ok I have the supernoob question of the day. can you type adb commands via the terminal emulator on the phone, or do you have to be connected to a computer via usb? I downloaded adb wireless, but im thinking that i have to have the sdk set up on my comp first? Im just a little confused as you can tell
The terminal is the equivalent of doing 'adb shell'. You will have to download the android SDK to get the actual adb tool if you want to do push/pull etc. with it.
belyle said:
This was it. Thank you very much. I'm not sure why I didn't see the extra info on my other ROM, but there it is.
I don't suppose there's a different terminal/command prompt for windows that would show the colors?
Click to expand...
Click to collapse
http://code.google.com/p/puttycyg/ this does.
very old post that got bumped to the top. If you didn't try puttycyg and not interested in colors you can try this: http://forum.xda-developers.com/showpost.php?p=8036010&postcount=7
It works for me.
Just curious. I tried to root a Gingerbread emulator with the new Gingerbreak method, but that didn't work.
Typed by Z using the Gingerbread keyboard.
It's rooted by default. What do you want to do?
No it's not, try su-ing in a console.
GaiusM said:
No it's not, try su-ing in a console.
Click to expand...
Click to collapse
Code:
$ adb devices
List of devices attached
emulator-5554 device
$ adb shell
# <-- '#' indicates that I'm root.
# umount /cache <-- only root can do that
# su <-- su works too
#
Do you use "adb shell" or some terminal emulator app?
yes the emulator is already rooted, but it cannot run root-required app, like root explorer.
aldee_s said:
yes the emulator is already rooted, but it cannot run root-required app, like root explorer.
Click to expand...
Click to collapse
Ok, thread can be closed now.
Typed by Z using the Gingerbread keyboard.
Hi, i have ICS for HTC Desire (Bravo), Android 4.0.4 and my problem when i start Terminal Emulator, i type "su" and i get # (superuser permissions) and when i type "adb uninstall package" i get message from terminal "waiting for device" and i dont know what to do
I need to uninstal com.android.vending
Thx for help
t0msk said:
Hi, i have ICS for HTC Desire (Bravo), Android 4.0.4 and my problem when i start Terminal Emulator, i type "su" and i get # (superuser permissions) and when i type "adb uninstall package" i get message from terminal "waiting for device" and i dont know what to do
I need to uninstal com.android.vending
Thx for help
Click to expand...
Click to collapse
This has nothing to do with Terminal Emulator, it's working fine ->
adb stands for android debug bridge, it's meant to be a way to do stuff with your android device from your computer over the "bridge" that is USB. It says "waiting for device" because it needs a USB android device to be connected. As far as I know, even with OTG you can't use adb actually on an android device itself with Terminal Emulator. If all you want to do is uninstall an app, you shouldn't need adb anyway.
Read here.
HTCDreamOn said:
This has nothing to do with Terminal Emulator, it's working fine ->
adb stands for android debug bridge, it's meant to be a way to do stuff with your android device from your computer over the "bridge" that is USB. It says "waiting for device" because it needs a USB android device to be connected. As far as I know, even with OTG you can't use adb actually on an android device itself with Terminal Emulator. If all you want to do is uninstall an app, you shouldn't need adb anyway.
Read here.
Click to expand...
Click to collapse
I tried use adb through cmd in windows but its waiting too (adb through cmd is working only in recovery)
So how can i uninstall system app?
Screenshot is in attachments, i can disable it, but i need to uninstall it, because here is thread: http://forum.xda-developers.com/showthread.php?t=1355660&page=1662
Originally Posted by rfandango View Post
Download: Vending-3.8.15.noupdate.norestrictions.apk - google it - rename to Vending.apk, with root explorer move it to system app and set perm to rw r r...reboot...work like a charm
Unfortunately, this isn't working for me - still no play store, but there's an entry for com.android.vending in Manage Apps with a grey icon (generic app icon with a little SD card in the bottom right corner) and a size of 0.00b. Anyone know what I missed?
Click to expand...
Click to collapse
Edit: Fixed it! Needed to do "adb uninstall com.android.vending" and then reboot. The store is back now.
Click to expand...
Click to collapse
Any idea?
Because i dont have Play Store so i cant do anything
t0msk said:
Any idea?
Because i dont have Play Store so i cant do anything
Click to expand...
Click to collapse
Try run the following in Terminal Emulator:
Code:
pm uninstall com.android.vending
* You must find out the vending apk and delete it first (If the apk exists and is a system app).
codelover said:
Try run the following in Terminal Emulator:
Code:
pm uninstall com.android.vending
* You must find out the vending apk and delete it first (If the apk exists and is a system app).
Click to expand...
Click to collapse
i got "Failure"
I made new screenshot and i found that when i type "adb devices" in Terminal Emulator i get blank page, you can see it in the screenshot
t0msk said:
I made new screenshot and i found that when i type "adb devices" in Terminal Emulator i get blank page, you can see it in the screenshot
Click to expand...
Click to collapse
As mentioned by @HTCDreamOn, adb is for you to run commands from Windows and since you are working with Terminal Emulator you do not need to deal with adb related command.
Also mentioned earlier that you MUST manually delete the apk first before you can uninstall the app if it is a system app.
To do that first find out where the vending apk located. assumed that you have busybox/grep installed, run the following in Terminal Emulator:
pm list packages -f | grep vending
You should get something like this:
package:/system/app/vending.apk=com.android.vending
Click to expand...
Click to collapse
* Actual filename & path may vary depending on device
Now that you know where the apk is, eg: /system, mount the /system rw and delete the vending.apk manually.
Then you can proceed to uninstall using the following command:
pm uninstall com.android.vending
Success :laugh:
Thx!
I dont want to make new thread so my another question is why i cant go to ini.d folder when its exists?
Look at my screenshot
//EDIT: SOLVED
I installed a tempered glass screen protector on my S4 and it messes with the proximity sensor. I contacted the manufacturer and this is what they told me to do:
Thanks for reaching out to us! Any issues with the S4 proximity sensor can be fixed by recalibrating the proximity sensor by issuing the following command:
echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
I entered that command in my TE and I keep getting an error. I can't really tell where there are spaces, where there are possible spaces, etc. Can anyone look at that command and break it down for me? Like:
echo (space)1(space)>(space)/sys/devices/virtual/sensors/proximity_sensor/prox_cal
That is what I tried and no go.
golfinglenn said:
I installed a tempered glass screen protector on my S4 and it messes with the proximity sensor. I contacted the manufacturer and this is what they told me to do:
Thanks for reaching out to us! Any issues with the S4 proximity sensor can be fixed by recalibrating the proximity sensor by issuing the following command:
echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
I entered that command in my TE and I keep getting an error. I can't really tell where there are spaces, where there are possible spaces, etc. Can anyone look at that command and break it down for me? Like:
echo (space)1(space)>(space)/sys/devices/virtual/sensors/proximity_sensor/prox_cal
That is what I tried and no go.
Click to expand...
Click to collapse
What is the error you are receiving in terminal emulator when entering the command? Also you could try entering the command from adb shell. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
shimp208 said:
What is the error you are receiving in terminal emulator when entering the command? Also you could try entering the command from adb shell. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
/system/bin/sh; can't create /sys/devices/virtual..........prox_cal: Permission denied
golfinglenn said:
/system/bin/sh; can't create /sys/devices/virtual..........prox_cal: Permission denied
Click to expand...
Click to collapse
Is your device rooted? Try running the command as the root user which should fix the error.
Sent from my SCH-I535 using xda premium
shimp208 said:
Is your device rooted? Try running the command as the root user which should fix the error.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks for your help. This may be a stupid question, but how do I run the command as the root user? My device is rooted, confirmed with tibu. When I open TE I get the $ sign in the command prompt. Do I need to get that to #, and if so how. I tried to do the same process when I rooted but still didn't work.
Thanks,
Glenn
golfinglenn said:
Thanks for your help. This may be a stupid question, but how do I run the command as the root user? My device is rooted, confirmed with tibu. When I open TE I get the $ sign in the command prompt. Do I need to get that to #, and if so how. I tried to do the same process when I rooted but still didn't work.
Thanks,
Glenn
Click to expand...
Click to collapse
To run the command as root in terminal emulator type the following (Don't actually input the $ and # symbols):
Code:
$ su
#
Entering "su" gives you a root shell from which to run commands from. After you have a root shell in terminal emulator try running the original command you were given.
Sent from my SCH-I535 using xda premium
Okay, I typed su, got the # sign and entered the original code I was given. Hit return and this is what I got:
[email protected]:/ #
How do I know if it calibrated? I broke the tempered glass protector lol trying to "fix" it another way so waiting for another one.
Thanks,
Glenn
golfinglenn said:
Okay, I typed su, got the # sign and entered the original code I was given. Hit return and this is what I got:
[email protected]:/ #
How do I know if it calibrated? I broke the tempered glass protector lol trying to "fix" it another way so waiting for another one.
Thanks,
Glenn
Click to expand...
Click to collapse
If your get a root prompt in terminal after entering the command and not an error message the command was executed successfully and your display should now be calibrated.
Sent from my SCH-I535 using xda premium
Awesome, thank you!!!
Glenn