Hey all,
I'm hoping I'm in the right area to post this question. If I am not, if you could direct me to where I should post it I would appreciate it.
Anyway, here is my question: How does one go about changing the shell that su uses? I am using Android Terminal Emulator and while I have changed the default shell command line to ash, I am unable to figure out how to change the shell used when going into superuser mode. The default terminal is missing my most used feature (command recall) and I'd like to get it back.
If you could help me out, I would greatly appreciate it.
Know I'll catch some heat for this but would really like an answer so bumping the thread
Related
So I feel like a total Noob, which i am, but I cannot get this new Kernel to work for me. I do the following steps:
1) Open Terminal Emulator (install it from market if you don't have it).
2) Type "su" (without quotes) and hit enter.
3) Type "speedtweak.sh" (without quotes) and hit enter.
When I type in and I get speadtweak.sh and i get Speedtweak.sh not found... what in the world am I doing wrong?
when terminal boots up I get:
$ export PATH=/data/local/bin:$PATH
$
when your terminal boots up-
$ export PATH=/data/local/bin:$PATH
$
-- You need remember ALWAYS lower sensitive case characters
type su hit return
it will come up #
then
type speedtweak.sh hit return
There you will access the dialog output from speedtweak.sh.
Good luck
You have to install BusyBox. If you haven't it'll show up as "not found".
Having same issue. Busybox is installed even tried using adb shell. Any advice?
Did you install the kernel through Rom Manager or through Recovery? If it was through Rom Manager it could have been a bad flash.
Also, you can try this
I found this thread through google, searching for "speedtweak.sh not found." I dislike necroposting but I tried various suggestions found on multiple websites and none of them worked for me. I kept getting the same error code. Hopefully this will help someone else with the same issue. I don't know much about Linux/Unix so I am always extremely methodical about typing in commands precisely as they're posted, double-checking each step so I'm certain I did everything correctly.
I finally solved the issue for me by entering in the following in Terminal Emulator.
su
/sbin/speedtweak.sh
Typing in the full path for the speedtweak script worked for me. Perhaps someone with more experience can explain why that was necessary. Were we working in DOS, I'd know to add C:/sbin/ to the autoexec.bat path line... :silly:
Terminal emulator from the market had something changed in the last update so for some reason now you have to manually enter it or change the path in the settings.
Sent from my ADR6400L using Tapatalk 2
Hey all,
I would just like to say I am new to this whole thing, and HAVE searched the forums, and found this link to be most helpful:
http://forum.xda-developers.com/showpost.php?p=12029729&postcount=12
I am merely trying to install the new swype beta, I am currently trying to uninstall my current version of swype, now I have done the majority of the steps the only thing I am having trouble doing is giving the phone read/write access
as when I try: mkdir /mnt/sdcard/swype_backup I get an error because it's a read-only file system.
I am using ADB; the first line of the post I linked to says to enable R/W access if you're using Root Explorer... but I am not, so how can I accomplish this through adb?
Am I missing something glaringly obvious?
Thanks for your time and patience
Edit: I believe adb is working to the extent it should... after I type in adb shell I do infact get a '#' before each line.
It's all fixed, re-did gladroot and now everything worked perfectly, not sure exactly why it wasn't before
thanks anyways!
Hello everybody,
I am looking for a simple way of starting a predefined shell command from the homescreen.
I assume that this is not a built-in feature of Android, but I am pretty sure that I'm not the only in need of that feature. I look forward to hearing about any app recommendations or other hints that could help me accomplish this.
If you're wondering what I need that for: I would like to be able (un)mount a partition on my sdcard, without having to start the terminal emulator manually and to enter the same commands over and over again.
I know about GScript:
http://forum.xda-developers.com/showthread.php?t=486486&page=21
However, it's still in alpha status and as far as I understand it, it brings its own shell and in general much more features than I need.
Thank you,
David
Hey all,
I'm hoping I'm in the right area to post this question. If I am not, if you could direct me to where I should post it I would appreciate it.
Anyway, here is my question: How does one go about changing the shell that su uses? I am using Android Terminal Emulator and while I have changed the default shell command line to ash, I am unable to figure out how to change the shell used when going into superuser mode. The default terminal is missing my most used feature (command recall) and I'd like to get it back.
If you could help me out, I would greatly appreciate it.
No one? Really?
gumbyx84 said:
No one? Really?
Click to expand...
Click to collapse
Well, if you were to use "/system/xbin/su -c /system/xbin/bash" in Cyanogenmod then it would give you bash shell as root. So, if you change the path to bash to ash on your ROM then you can have ash shell as root.
Hi everyone,
I am having a general conundrum that is really setting me back. My device(s) are my HTC One (rooted) and and CS968 (rooted) mini-pc. I've tried the following on both devices and always get the same thing. I don't think its device specific:
I am trying to install an APK. When I go into Terminal Emulator and get su permissions, I type in the following command "pm install /sdcard/directory/of/apk/target.apk" and it works, success, the apk is installed.
If I write a .sh script with the EXACT same syntax, I always get the infamous "INSTALL_FAILED_INVALID_URI" error. I cannot for the life of me figure out why.
Yes, I have searched every corner of this forum and google for solutions to this problem. They all end with the conclusion that you need to re-flash your rom (???) which seems very improbable to me. What makes my case different is that, like I said, the command works just fine when manually entered into Terminal Emulator, but when executed from a script, is when I get this bizzare error. I am at my wits end.
If anyone could shine some light on this for me I would greatly appreciate it.
Thank you