hi,
quick question..
i put "setprop service.adb.tcp.port 5555" in file.txt, and save this to /sdcard.
if i run "sh /sdcard/file.txt" from adb shell, on pc, then it works and getprop confirms.
if i run "sh /sdcard/file.txt" from terminal emulator, on phone, it says "could not set property".
can someone explain this behaviour? tahnk you.
in addition, where should you save shell scripts on your phone?
do you guys use shell scripts? can you give examples of what you use them for?
MrPresident said:
hi,
quick question..
i put "setprop service.adb.tcp.port 5555" in file.txt, and save this to /sdcard.
if i run "sh /sdcard/file.txt" from adb shell, on pc, then it works and getprop confirms.
if i run "sh /sdcard/file.txt" from terminal emulator, on phone, it says "could not set property".
can someone explain this behaviour? tahnk you.
in addition, where should you save shell scripts on your phone?
do you guys use shell scripts? can you give examples of what you use them for?
Click to expand...
Click to collapse
Try "su" command first and grant root access to terminal app
minimale_ldz said:
Try "su" command first and grant root access to terminal app
Click to expand...
Click to collapse
thanks for the reply, minimale.
okay. so, as you suggested, it works when i do it as root from the terminal app.
but couple of things.
1) Why can i run it from adbshell without 'su' command. through adb shell it still works as "[email protected]:/ $" instead of "[email protected]:/ #"
2) how come, without 'su', I can access "/sdcard" (as "[email protected]: / $"). but, as root, I have to go through "/data/media/0"
MrPresident said:
thanks for the reply, minimale.
okay. so, as you suggested, it works when i do it as root from the terminal app.
but couple of things.
1) Why can i run it from adbshell without 'su' command. through adb shell it still works as "[email protected]:/ $" instead of "[email protected]:/ #"
2) how come, without 'su', I can access "/sdcard" (as "[email protected]: / $"). but, as root, I have to go through "/data/media/0"
Click to expand...
Click to collapse
I'm glad I helped, but have no idea where the differences between ADB and terminal emulator come from. It's beyond my current knowledge.
minimale_ldz said:
I'm glad I helped, but have no idea where the differences between ADB and terminal emulator come from. It's beyond my current knowledge.
Click to expand...
Click to collapse
no worries. i got what i need.
Related
Okay, so I'm a bit an ADB noob here. I've been trying to push my avatar apk into /system/apps for awhile here but every time i do so, it fails with this error:
/bin/sh: adb: not found
did I set it up wrong somehow?
Oniyuri said:
Okay, so I'm a bit an ADB noob here. I've been trying to push my avatar apk into /system/apps for awhile here but every time i do so, it fails with this error:
/bin/sh: adb: not found
did I set it up wrong somehow?
Click to expand...
Click to collapse
Make sure you are running the adb command from the directory where your adb is located. There is tons of info on this site and google that will give you everything you need to know about using adb. Try typing the error message into search
yeah, i know to change directories already. this error is happening after i'm in the directory.
i basically start out like this:
cd C:\android-sdk-windows\tools
and after that, switch to adb shell
C:\android-sdk-windows\tools> adb shell
i get some characters and then try for a push
"adb push C:\users\myuser\downloads/avatar.apk /system/app
after that, boom! error.
bump
+10char
Oniyuri said:
yeah, i know to change directories already. this error is happening after i'm in the directory.
i basically start out like this:
cd C:\android-sdk-windows\tools
and after that, switch to adb shell
C:\android-sdk-windows\tools> adb shell
i get some characters and then try for a push
"adb push C:\users\myuser\downloads/avatar.apk /system/app
after that, boom! error.
Click to expand...
Click to collapse
You really should be using either the search bar here or google because this information is in abundance. "adb push" should not be run from inside the shell. adb is not recognized by the shell. Do the same thing that you listed above minus the step where you typed "adb shell"
********
Sent from my Paragon RC3 Captivate using the XDA app
Try 'cd C:\android-sdk-windows\platform-tools', not C:\android-sdk-windows\tools.
Better yet, just add that to the environment variable, PATH.
hth
Hello, I am using a Droid Razr Maxx CDMA (XT912). I have Android version 4.2.2. I am using Cyanogen mod 10.1.
I am having problems opening ADB. When I turn my USB Debugging on under my dev. options, connect my device in PTP mode using the terminal emulator commands:
su
setprop persist.sys.usb.config mass_storage
reboot
I run the ADB program and a window comes up for a brief moment then closes. I am unable to open ADB. I have Java.
Thank You!
ADB Troubles Cont'd.
nathanielhall929 said:
Hello, I am using a Droid Razr Maxx CDMA (XT912). I have Android version 4.2.2. I am using Cyanogen mod 10.1.
I am having problems opening ADB. When I turn my USB Debugging on under my dev. options, connect my device in PTP mode using the terminal emulator commands:
su
setprop persist.sys.usb.config mass_storage
reboot
I run the ADB program and a window comes up for a brief moment then closes. I am unable to open ADB. I have Java.
Thank You!
Click to expand...
Click to collapse
Did adb kill-server and adb start-server several times in cmd with no avail. The device serial number shows up under adb devices, but ADB Program will still not open. I've tried to open ADB up in cmd also.
I also tried typing in the terminal emulator:
su
setprop persist.sys.usb.config mass_storage, adb
reboot
Thanks again!
Can someone please help me with this?
I even tried installing the Universal naked drivers and that wouldn't go through.
nathanielhall929 said:
I even tried installing the Universal naked drivers and that wouldn't go through.
Click to expand...
Click to collapse
I copied your command and pasted here. setprop persist.sys.usb.config mass_storage, adb
And what I find is posted here. setprop persist.sys.usb.config mass_storage,adb
And reboot afterwards.
Notice the extra space in your command before adb?
I found this command structure several locations and only one that reports failed has the space.
For ICS it also shows adb shell as in
adb shell setprop persist.sys.usb.config mass_storage,adb
adb reboot
I hope this helps.
Tried it without the space and still not working
tobdaryl said:
I copied your command and pasted here. setprop persist.sys.usb.config mass_storage, adb
And what I find is posted here. setprop persist.sys.usb.config mass_storage,adb
And reboot afterwards.
Notice the extra space in your command before adb?
I found this command structure several locations and only one that reports failed has the space.
For ICS it also shows adb shell as in
adb shell setprop persist.sys.usb.config mass_storage,adb
adb reboot
I hope this helps.
Click to expand...
Click to collapse
I just tried it without the space, rebooted, and nothing
I don't get it
nathanielhall929 said:
I just tried it without the space, rebooted, and nothing
Click to expand...
Click to collapse
The ADB Program just won't open up on this computer. It opens for a second spewing command info then closes. Is it my Java program?
nathanielhall929 said:
I just tried it without the space, rebooted, and nothing
Click to expand...
Click to collapse
Are you getting an error?
This is the other method I see being used but I'll break the command as I believe it should be.
adb shell
su
setprop persist.sys.usb.config mtp,adb
exit
adb reboot
My problem is I know nothing about your unit and I don't know whether it should be mtp or mass_storage. I see people failing with mass_storage are being told to use mtp.
in terminal it shows
su
setprop persist.sys.usb.config mass_storage,adb
reboot
or
su
setprop persist.sys.usb.config mtp,adb
reboot
To retrieve this info I used the top search that says Search All Forums and typed in your command then hit search. You may need to do the same and only go to the threads that suit your situation.
---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------
nathanielhall929 said:
The ADB Program just won't open up on this computer. It opens for a second spewing command info then closes. Is it my Java program?
Click to expand...
Click to collapse
Are you opening cmd and going to the directory with adb and issue your commands or are you trying to click on adb and use it that way?
I'm trying to run it in cmd
I've been trying to fix this for two days now. I'll be back tomorrow.
Figured out
Ok, now I feel like I'm a real noob. I just realized that I was thinking too hard about all of this. Adb doesn't open up in a new window as a regular program would. I thought it did. Oops. Maybe I should have been more thourough in my research. I should have realized that I already opened adb by using the cmd prompt.
This is why my device was recognized under adb devices.
Maybe not...
I still can't figure out how to get this:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/attachment/path-adb/
window to come up.
This is what I'm tring to do
nathanielhall929 said:
I still can't figure out how to get this:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/attachment/path-adb/
window to come up.
Click to expand...
Click to collapse
This is what I am trying to do:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/
Figured out finally!!!
nathanielhall929 said:
This is what I am trying to do:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/
Click to expand...
Click to collapse
I finally figured this out!!!
I want to thank tobdaryl for his time.
Thank you for your time tobdaryl
nathanielhall929 said:
I finally figured this out!!!
I want to thank tobdaryl for his time.
Thank you for your time tobdaryl
Click to expand...
Click to collapse
You are welcome.
Can you help me?
Can you check out this thread.. Maybe you can help me.
http://forum.xda-developers.com/showthread.php?t=2260208
Hello sir! I just wana ask question on how to run commands like this
su -c /system/etc/CrossBreeder/REMOVE_TETHER_BOOST
i've seen this in the Cross Breeder thread. I just wanna try it to reduce the lag on my phone and maybe also to speed it up!
but if i came across with this unexpected problems . i really dont know how to run this commands. so i just wanna ask . how do i run commands like that? THANKS IN ADVANCE
These commands are run via a terminal emulator on your phone. For this command, your phone have to be rooted.
Alternatively, you can use adb shell. To do so, you have to download the android sdk or google for adb for just downloading the relevant part of it, then you have to run adb root to get root privileges (the adb binary can be found under Path/to/Android-SDK/platform-tools) and adb shell to get a root shell. There you have to type in /system/etc/CrossBreeder/REMOVE_TETHER_BOOST (the su -c is not needed there because you already have root privileges).
Okay... So Here Is Whats Up... The Digitizer On My Lg Optimus L9 Is Broken, Cant Touch The Screen Or Anything... But I Would Still Like To Use My Phone, I Can Can View My Screen But Thats All I Can Do,I Wish To Use The Keyboard And Mouse To Control My Screen,I Know This Is Possible Apperantly The Only Way To Do This Is To Access The ADB Shell, Okay,But What The Problem? Well When I Attempt To Gain Access To The ADB Shell... Super SU Gets In The Way, I Cant Grant Access To The ADB Shell Because I Cant Touch The Screen Do To The Broken Digitizer, And I Cant Click It When It Appears On The Display Because I Dont Have Super SU Permision To Use The Controlls Do To Being Denied Access Of The ADB Shell, If You Under Stand My Cicumstances Please Assist Me In Any Way, The Only Stipulation, No Factory Reset! Please And Thank You!
savagemessiah97 said:
Okay... So Here Is Whats Up... The Digitizer On My Lg Optimus L9 Is Broken, Cant Touch The Screen Or Anything... But I Would Still Like To Use My Phone, I Can Can View My Screen But Thats All I Can Do,I Wish To Use The Keyboard And Mouse To Control My Screen,I Know This Is Possible Apperantly The Only Way To Do This Is To Access The ADB Shell, Okay,But What The Problem? Well When I Attempt To Gain Access To The ADB Shell... Super SU Gets In The Way, I Cant Grant Access To The ADB Shell Because I Cant Touch The Screen Do To The Broken Digitizer, And I Cant Click It When It Appears On The Display Because I Dont Have Super SU Permision To Use The Controlls Do To Being Denied Access Of The ADB Shell, If You Under Stand My Cicumstances Please Assist Me In Any Way, The Only Stipulation, No Factory Reset! Please And Thank You!
Click to expand...
Click to collapse
You should still be able to access adb shell at the shell level, what is likely happening is that you are dropping into a root shell and this is causing SuperSU to prompt if you want to allow adb shell to have root access. What are the exact steps you are taking when you go to use adb shell?
shimp208 said:
You should still be able to access adb shell at the shell level, what is likely happening is that you are dropping into a root shell and this is causing SuperSU to prompt if you want to allow adb shell to have root access. What are the exact steps you are taking when you go to use adb shell?
Click to expand...
Click to collapse
I Use Android Screencast Plus Android SDK, Then I Use Command Prompt
.Adb Shell
.Su
At That Point Super Su Is Prompted
savagemessiah97 said:
I Use Android Screencast Plus Android SDK, Then I Use Command Prompt
.Adb Shell
.Su
At That Point Super Su Is Prompted
Click to expand...
Click to collapse
I would recommend try starting adb shell (adb shell command) and not dropping into a root shell then skip the su command. So just do
Code:
adb shell
To start adb shell, and then skip the su command.
shimp208 said:
I would recommend try starting adb shell (adb shell command) and not dropping into a root shell then skip the su command. So just do
Code:
adb shell
To start adb shell, and then skip the su command.
Click to expand...
Click to collapse
If I Skip su The cmd Says Not Permited
Code:
•adb shell
•su
•chmod 777 /data/dalvik-cache
•cd /data/dalvik-cache
•chmod 777 ./
This Is My Attempt, Is There An Alternative
savagemessiah97 said:
If I Skip su The cmd Says Not Permited
Code:
•adb shell
•su
•chmod 777 /data/dalvik-cache
•cd /data/dalvik-cache
•chmod 777 ./
This Is My Attempt, Is There An Alternative
Click to expand...
Click to collapse
Trying using adb shell from the command line, instead of Android Screencast. Also what are you trying to do with the device extract your personnel information?
Any progress with this? I'm in the same situation
Device won't respond to "adb shell wm" even though "wm" exists in /system/bin
I'm trying to change the pixel density on my unrooted RN3P using the "adb shell wm density XXX" command.
I'm running Krexus-CAF ROM.
ADB is set up and working, and I can open a shell on the device.
The problem is that `wm` cannot be found, even though it exists on the device at `/system/bin/wm`. I cannot do this with the "adb shell wm density XXX" command, nor if I open a shell on the device and type "wm density"
The output is:
Code:
~/Library/Android/sdk/platform-tools $ adb shell wm density 400
/system/bin/sh: /system/bin/wm: /bin/sh: No such file or directory
Has anyone had success with this, or can tell me why the "wm" command cannot be found, even though it exists in the directory that the device looks in?
Cheers
DoubleDroz said:
I'm trying to change the pixel density on my unrooted RN3P using the "adb shell wm density XXX" command.
I'm running Krexus-CAF ROM.
ADB is set up and working, and I can open a shell on the device.
The problem is that `wm` cannot be found, even though it exists on the device at `/system/bin/wm`. I cannot do this with the "adb shell wm density XXX" command, nor if I open a shell on the device and type "wm density"
The output is:
Has anyone had success with this, or can tell me why the "wm" command cannot be found, even though it exists in the directory that the device looks in?
Cheers
Click to expand...
Click to collapse
First check for "adb devices". If it doesn't show then check for the drivers. After that set path of adb in windows to default. Try again with debugging enabled.
mehulchirania said:
First check for "adb devices". If it doesn't show then check for the drivers. After that set path of adb in windows to default. Try again with debugging enabled.
Click to expand...
Click to collapse
thank you for taking time out to try help.
i'd just say that your solution isn't what the OP is looking for.
mainly because if you read the post he tried adb shell wm.....
but also tried on the phone inside terminal app typing the command..
i personally don't have a solution but i thought i'd try help you try maybe another suggestion?
for example, i can now go and tell the OP to download and install angry bird or busybox etc but it won't make a difference.
mehulchirania said:
First check for "adb devices". If it doesn't show then check for the drivers. After that set path of adb in windows to default. Try again with debugging enabled.
Click to expand...
Click to collapse
As noted in the question, I can definitely find my device, as I was running the shell on the device with ADB. The problem was that I could not execute `wm`, even though it was listed in the directory.
I ended up switching ROMs, and could use `wm` without issue - I'm not sure what it was about the ROM I was using that meant I couldn't use the files listed.
Oh well.