I have many super user apps running but tried to go into terminal emulator to run oc dameon in viper rom 2.2 and it say su: not found. Can anyone tell me how to fix the problem? Thanks!
Deleted by poster
Okay I figured it out. Not sure what or why? I installed busy box and then reinstalled terminal emulator. Now it works.
Related
Hey guys I'm trying to flash Amon RA v 1.8 on my phone, put it in the root of my sdcard opened terminal emulator and typed su, but it said 'permission denied'
my phone is rooted, i have superuser permissions under my apps, i was able to use set cpu, i dont understand whats wrong, suggestions?
Sounds like you may be rooted but not Nand unlocked. You should give more information as to what method you did to achieve root, what hboot, etc...
one person told me the same and that i needed the PC36IMG zip file and that i would be good. my method of rooting was installing the hboot drivers and then using unrevoked.
i booted in recovery with clockwork and did a NAND backup assuming then that NAND was unlocked lol but i guess not so i tried doing some research into the NAND unlocking and i have no idea what this adb shell thing is, is this the problem though with flashing amon RA?
Try giving terminal emulator su permission. Tap supermissions apk and enable terminal emulator.
if you mean go to the superuser permission app and check whats allowed/denied terminal emulator isnt there, only wifi tethering set cpu and titanium backup are there
R1pTheJacka said:
if you mean go to the superuser permission app and check whats allowed/denied terminal emulator isnt there, only wifi tethering set cpu and titanium backup are there
Click to expand...
Click to collapse
In terminal emulator settings check start as root, then restart it, and then when supermissions prompts you give terminal emulator root privilege.
there's no setting like that in terminal emulator, i do have another app called 'better terminal emulator', checked those settings and it had the setting you were talking about, but even when i checked that, superuser permissions didnt ask me to allow/deny better terminal emulator
R1pTheJacka said:
there's no setting like that in terminal emulator, i do have another app called 'better terminal emulator', checked those settings and it had the setting you were talking about, but even when i checked that, superuser permissions didnt ask me to allow/deny better terminal emulator
Click to expand...
Click to collapse
Within Better terminal emulator, try the su command.
I used better terminal emulator (bte) to install Amon_Ra's 1.8 and it is in the super user permission white list.
Hi there,
i'm actually trying to do the wimax backup found here:
http://forum.xda-developers.com/showthread.php?t=887900
I went through all of this trouble trying to install busybox until I found out that Titanium backup already installed 1.16 on my phone. However I can't seem to find where it was installed to and the,
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
command isn't working. Any thoughts? Sorry if this is the wrong spot to post. I'm still getting the hang of this forum.
I have the same problem. I think I'm getting this error in the terminal emulator because I don't have the system Busybox installed, just Titanium's app busybox, which is apparently different?. When I try to run Busybox installer, it errors saying I'm possibly not nand unlocked... I used UR3 and UR forever, and can confirm that I am S-Off. Doesn't S-Off = nand-unlock?
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
topdawgn8 said:
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
Click to expand...
Click to collapse
greyopaque said:
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
Click to expand...
Click to collapse
you should be able to run find without a hitch. I have had issues running a find while executing a remove, but find had always worked...
try remounting the system:
Code:
su
remount rw
find -iname "*busybox*"
Edit: I just ran find with only SU. What rom and kernel are you running? The only two things I can think of are:
1: The dev removed it from the rom
2: User error-- ensure the commands are lower case, there is a space where appropriate (denoted by ">")
Code:
find>-iname>"*busybox*"
The busy box that tb installs doesn't have all the commands. I had to install from the market to get all the commands.
Sent from my PC36100 using XDA App
its in system/bin most of the time but can be in different spots
Usually you can find busybox in /system/xbin
OMG... I feel stupid... I had install location set for SDCard. That's why busybox installer was failing. I changed it back to auto, and installed busybox, and now everything is working!
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
That's exactly what I did. Thanx!
gpz1100 said:
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
Click to expand...
Click to collapse
Hello Friends,
I am using DHD since last few weeks, i have downgraded it to 1.32 and can use superuser access. But now i have been facing new problem. i am not able to reboot using terminal emulator. is there anything missing? I was adding new font to my system fonts, but at the end of it we requires to reboot it, its simply said "not permitted!"
can anyone please help me in this regards!
Thanks in advance.
Are you on a custom rom?
I had a quick look in leedroid with root explorer and it seems the permissions are incorrect for /system/bin/reboot.
rwsr-xr-x where it should be rwxr-xr-x
-----
Someone Swyped my idea.
Using Unity 1.29,have checked my permissions on /system/bin/ reboot -rwxr-xr-x root shell,busybox is also good tried
$ su
#reboot
and get "not permitted"
I know i could just use the buttons but would like to be able to do it from the terminal,checked on a nandroid backup of CM7.03 and the command works from terminal,anybody any ideas how to get it working? Its got me completely stumpted!!!!!!!!!!!!!
also happens to me with Revolution HD
Try from the terminal
$su
#reboot -f
BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
Try it and see how you go
Hi there!
I'm trying to root Ziio 7 unit I got for a review for PurePC.pl, and so far so good I installed SuperUser app and su and busybox binaries. Now using terminal I can su without any problems. But the thing is, SU only seems to be working in terminal emulator. I've tried using some apps that should use root like ShootMe and ScreenshotIt, SetCPU and they just doesn't work.
ShootMe says "Starting Server failed", plus info that i need to have root access and enabled access to lower graphics (whatever it is).
ScreenshotIt just doesn't work without any information why, and SetCPU FC's after selecting profile. Although it gets me a nice SuperUser dialog, but that's as far as it goes, cause it crashes right after that.
Am I missing something to have a complete root? Interesting thing is that on this device, preferred PATH for executable binaries is /data/busybox/, and not a usual /system/bin. Interestingly, my su binaries refused to work from /data/busybox directory, so I moved them to /system/bin. Rest of the utilities and such are still in /data/busybox, but I don't know if this information is important in any way Have I missed something along the way? Please help. Cheers.
OK, I know why su gave me permission denied when running from /data/busybox. The /data partition was mounted with nosuid. But still the applications such as ShootMe won't work.
I waiting for. If who has a good new. Please tell me to private message.
Have you made any progress on this bagienny?
Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.
Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).
Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse
goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse
Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.