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
Related
Hey guys
One of the things im working on atm, having a bit of trouble trying to get a sysctl.conf I am working on to be loaded at startup
I've managed to generate the file, edit what i want, gotten it into /etc, but therein lies the problem
when i try to run systl -p, it keeps telling me the following:
sysctl: error setting key <insert sysctl key here>: Permission Denied
How can i overcome this? As soon as ive finished the work on this file, I'll be happy to share it with everyone
so no ideas?
Do you have superuser permissions (su, command prompt #) ?
When trying with this:
-p
Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.
Perhaps this helps ?
-e
Use this option to ignore errors about unknown keys.
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Nutterpc said:
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Click to expand...
Click to collapse
Look at your phone to allow Superuser permission after entering su in the terminal or command
Sent from my X10i using XDA App
had a bit more of a fish round the net to see if anyone else ham similar issues
seems i was able to find the eventual root cause of it, was /system/bin/sh was set to secure mode, so i downloaded root explorer and changed the permissions
now the only thing is, how do i actually get the sysctl.conf im working on to be loaded at start, when i turn the phone on?
You might find something useful in this thread:
http://forum.xda-developers.com/showthread.php?t=523707
Trying to wipe battery stats with terminal emulator, get the following:
$ $ rm failed for /data/system/batterystats.bin, no such file or directory
Verified in root explorer that directory is there but not the file. CWm battery stats wipe doesnt work either.
-50 PBJ, UK 2.0 with ec09 radio.
any suggestions on how to wipe the battery stats ? performance has been lacking since the UK upgrade, radio change didnt help.
Two ways: manually wipe in cwm, or download battery calibration from the market. Both do the exact same thing.
Also, from your terminal command, you tried to do it without superuser access. Type "su" first, then hit enter.
Sent from mah Fascinate using XDA Premium App
Thanks, i did try it with su, but it failed to reboot. Just goes back to a prompt, #.
Also tried in cwm, blank response. I do have cwm red if that matters.
Sent from my SCH-I500 using XDA App
The # sign means the next command will be executed with root access, so try your original command again at the # prompt.
Sent from mah Fascinate using XDA Premium App
I experienced that in Terminal Emulator as well. However, it appeared to work fine in CWM.
I just got an update for the Terminal Emulator software and tried again but still get a return to the # prompt with no reboot. It *used* to work just fine - it was just since loading UKB 2.0 -50 PBJ that it didn't.
---------------
Did some Googling --- Try this:
For Terminal
1. open terminal emulator, press menu button, then preferences
2. scroll down to "shell" and changed initial command to read
"export PATH=/system/xbin: $PATH
3. press back button, Terminal will close, reopen terminal
4. type "su" hit return, grant su when promt pops up
5. type "bstats" and hit return
6. phone will reboot.
Found it here.
Yup, I see the same thing........was working fine with the reboot under commavolt, quite working only after the switch to PBJ -50
Tried the instructions above, no reboot. Acts the same as if I copied and pasted the extracted bstats commands like I used to do. ( back to # prompt)
Hi, I've been trying to move all my game data from my internal SD card to my larger external SD card with no joy.
I have used condi's AIO tool to install init.d support, which reported as successful, but when I follow obicom's instructions as listed in POST #43 of this thread http://forum.xda-developers.com/showthread.php?t=1490116&page=5
I repeatedly receive the message "Operation not permitted."
I have used both ADB Shell and Terminal Emulator with the same result.
I'm obviously doing something wrong as other people appear to have had success with these instructions, I just don't know what.
Here's what I've done: (on rooted ICS from condi's AIO tool)
Installed init'd support "successfully"
Moved all data from sdcard/Android/data over to sdcard2/game_data
In ADB Shell/Terminal Emu. entered the following line;
mount -o bind /sdcard2/game_data /sdcard/Android/data
and this is where I get the "Operation not permitted" message.
Any ideas?
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Ahaaa
Awesome! Can't believe it was something so simple, thanks, and thanks for explaining the reason.
I must have somehow totally missed the "su" instruction in the other thread.
Half of my games work, the other just seem to need re-installing which is no big drama.
Again, thanks, it's much appreciated mate.
Script?
agc93 said:
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Click to expand...
Click to collapse
Hi, is there a way I can create a script (or the like) that would do this, and other similar directory changes, at boot?
At present I need to enter these manually each time the tablet starts, which isn't too much of a drama for me but when other people use it they end up downloading the data all over again when they start a game.
Thanks
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
agc93 said:
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
Click to expand...
Click to collapse
Okay thanks, yet again, I'll give it a try today.
Operation not permitted
Hi,i wanted to change my mac address on phone and even with that su command i get "operation not permitted" (my phone is rooted)...even apk named overclock for android could not grant root acces...in root checker my phone is rooted(and i have been rerooting it but still same).AND THERE IS NO FIX ON INTERNET
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
Per this issue, and specifically this comment, I'm trying to grant the BATTERY_STATS permission to GSam Battery Monitor. I've tried the adb command "pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS" but can't get it to work. I've also tried "pm grant com.gsamlabs.bbm android.Manifest.permission.BATTERY_STATS" but the results are the same. Doing it through ConnectBot gives me the following error:
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 10338 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Doing it through adb gives me this:
Bad argument: java.lang.IllegalArgumentException: Unknown package: com.gsamlabs.bbm
This is on a stock Moto Z Play, 7.1.1
kernel:
3.18.31-perf-g757c8d9
[email protected] #1
Build number NPN26.118-22
Are you running the pro version? Then it needs to be com.gsamlabs.bbm.pro
The error is because it can't find a package named com.gsamlabs.bbm, so I would investigate why that's occurring. Either there's a typo (I don't see one) or that's not the correct package name.
ConnectBot won't work because ConnectBot doesn't have superuser permissions. Unless your device is rooted it'll have to be done through adb or using a PC-side program which effectively does the same thing.
Thanks! I think that was it, as adding .pro to the end didn't give an error. But it didn't actually say it was successful, either. It just spit out all the adb usage info like if you just type "adb" with no parameters. Any idea how I know if it worked?
vertigo_2_20 said:
Thanks! I think that was it, as adding .pro to the end didn't give an error. But it didn't actually say it was successful, either. It just spit out all the adb usage info like if you just type "adb" with no parameters. Any idea how I know if it worked?
Click to expand...
Click to collapse
Do the advanced stats in BBM work now? Also, are you on the paid version of BBM? That's the pro version, iirc.
You are typing "adb -d shell pm grant com.gsamlabs.bbm.pro android.permission.BATTERY_STATS", right?
Got busy with other stuff and just now got back to this, but I got it working. The reason I got the output I did before was because I was typing an invalid command, since pm grant isn't one of the commands of adb.exe. I had to type adb shell THEN type the command, and then it worked (and I just noticed you said that, I must have overlooked that when I looked at it before since I was busy). Also, for anyone that might come across this trying to do this, GSam didn't automatically recognize that this was done. I had to go through the steps of having it show me how to do it and at the end of that it worked. One final note, I had to update to the latest SDK for it to work, the version I was using was too old. Thanks again for the help apraetor!
Yea, I had a feeling after re-reading your original post that you were missing the "adb -d shell" portion, glad it's working.
vertigo_2_20 said:
Got busy with other stuff and just now got back to this, but I got it working. The reason I got the output I did before was because I was typing an invalid command, since pm grant isn't one of the commands of adb.exe. I had to type adb shell THEN type the command, and then it worked (and I just noticed you said that, I must have overlooked that when I looked at it before since I was busy). Also, for anyone that might come across this trying to do this, GSam didn't automatically recognize that this was done. I had to go through the steps of having it show me how to do it and at the end of that it worked. One final note, I had to update to the latest SDK for it to work, the version I was using was too old. Thanks again for the help apraetor!
Click to expand...
Click to collapse