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
Related
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
theMaDHakkeR said:
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
Click to expand...
Click to collapse
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Haha! Thank you your a saint! I'm still learning everyday
Thanks again.
Sent from my X10a using XDA App
biktor_gj said:
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Click to expand...
Click to collapse
Simple, amazing solution. Thanks !
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!
Ok so some background, I am running the newest molten and enjoying it thouroughly but just noticed that when i open terminal emulator and type SU to get root access in the terminal it says permission denied and most other commands return same error, i downloaded a differant terminal emulator that checks for the su.bin and it shows no su binary is installed yet when i goto the directory system/bin/ in es file explorer su is indeed there?
Could someone please tell me why none of the terminal emulators are finding the superuser binary? I ve already tried opening superuser app and updating the su binary (it did update and i rebooted after) but it hasnt helped, I also read on other forums that there are multiple su binaries on some phones? could this be the problem and if so where would i find the right binaries?
It just seams odd that terminal emulator would be included in the build if it is completly unusable
su then hit enter
lol, thanks, im not the smartest with linux commands but i know to hit enter.
I tried typing su and hitting enter in 3 differant terminal emulators but keep getting permission denied in all of them
You should get a super user request once you hit enter. Maybe permission was already denied. Try clearing defaults for su.
Sent from my DROID X2 using xda premium
Did you recent apply the 2.3.5 update? When I went from rooted 234 to 235 I lost root privileges even though the superuser app was still there.
Could be your root isnt quite right. What setup do you have. Also try going into your superuser application and see if they are on the not allowed list.
Also should go from a "$" to a "#" sign after you hit enter if su took.
thanks for the ideas, that really narrowed it down, i cleared data for superuser and terminal, reinstalled terminal, still didnt work.....then i realised im a idiot, my keyboards autocap was on and su has to be "su" not "SU"
lol well thanks again for all the help
brilock42 said:
thanks for the ideas, that really narrowed it down, i cleared data for superuser and terminal, reinstalled terminal, still didnt work.....then i realised im a idiot, my keyboards autocap was on and su has to be "su" not "SU"
lol well thanks again for all the help
Click to expand...
Click to collapse
If it is solved then put (solved) in the OP subject line and list what fixed it for you. It can help future users
Pesky case sensitive terminal
Sent from my DROID X2 using xda premium
No SU in SSH
su did not work here as I did use a bad SSH-app.
I now use sshdroid
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