Develop Bugs

Terminal Emulator "not found"

I'm trying to use Terminal Emulator and no matter what I try to enter it tells me its not found. I am rooted and it has been given SU rights. I've also tried to uninstall and reinstall but nothing works. Any ideas?

presumedsublime said:
I'm trying to use Terminal Emulator and no matter what I try to enter it tells me its not found. I am rooted and it has been given SU rights. I've also tried to uninstall and reinstall but nothing works. Any ideas?
Click to expand...
Click to collapse
I don't quite understand your issue here. Are you trying to launch Terminal Emulator and get this message?
A few things to try:
1. Clear Terminal Emulator's cache and data, retry.
2. Uninstall, restart, install again, retry.
Alternative route: Install Connectbot and do what you need to do.

I'm trying to get to cd /system/etc/init.d but each time i type it in it says "cd /system/etc/init.d: not found:

presumedsublime said:
I'm trying to get to cd /system/etc/init.d but each time i type it in it says "cd /system/etc/init.d: not found:
Click to expand...
Click to collapse
Just did it on my phone using Connectbot and no issues. I don't know.
Would anyone else like to chime in with assistance?

Okay connect bot worked but now it won't let me run "remount rw". It says "mount: can't find rw in /proc/mounts

Try "mount -o remount,rw /system" or similar
And it could be possible the init.d directory isn't there...
sent from my miui-ified epic

Thanks for your help. I was trying to copy a file to the system/etc/init.d directory through emulator since I've never done it before. Decided to save some time and use Root Explorer.

[Q] Problem with Fix Permissions (line 64: UID readonly variable) [WORK AROUND FOUND]

Latest!! Switch to TWRP 2.1.8 (June 18th 2012)
Anyone else having a problem Fixing Permisshions? And how did you fix it?
I noticed it would take 2 seconds to run, so I decided to go to "Show log"
Here is the log
I:Checking for extendedcommand, file not found...
/sbin/fix_permissions: line 64: UID readonly variable
Done!
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
Tried:
Running from Rom Manager but it always stalls, never the same place and if I run it multiple times back to back it stalls sooner and sooner
touch recovery
re-installing recovery
clearing download in rom manager and re-installing recovery
setting rom manager to delete recovery before installing
Wipe / reset, wipe cache & dalvik, with superwipe 2 times and re-installing
ClockworkMod Recovery v5.0.2.7
Running [ROM] [cwm]-BLACKEDITION FOR THE SGS2 4-10-2012-ICS RC6
A work around has been found! Thanks to RealPariah, so thank him here!
It is not a fix due to the fact that you still will not be able to fix permissions in CWM or Rom Manager but does get the job done of Fixing Permissions!!
1st Do you have the Google android installed?
If not download and install it! http://developer.android.com/sdk/android-4.0.htm
you might need to install the JDK, if you don't have it already.
2nd Your path to adb must not be set or is not correct.
See http://forum.xda-developers.com/show....php?t=1161776
Now you should be ready to use adb!
STOP!
Fixed in this New CWM Recovery or
GOTO THE DEVELOPMENT THREAD!
http://forum.xda-developers.com/showthread.php?t=1604581
Most recent Fix Script / Work Around found here
http://forum.xda-developers.com/showpost.php?p=25023284&postcount=22
Boot in to Recovery
plug USB in to phone and computer
In Recovery Go in to "mounts and storage" and mount /system and /data
On computer open a command line window (windows) [click start] then [run] then type "cmd" to get a command prompt or terminal (Linux or OSX)
Run "ADB devices" and be sure it is not all ? For device number (if it is restart recovery and reseat USB connection and run "adb kill-server" on computer) I had to run terminal as root (admin for best results bit got it to work either way really)
Now type "adb shell" enter
Once that opens and you get ~#
now type cd /sbin
then type
sh fix_permissions -l -r
done correctly, your command prompt should look like the following
C:\Documents and Settings\family>adb shell
~ # cd /sbin
cd /sbin
/sbin # sh fix_permissions -l -r
sh fix_permissions -l -r
fix_permissions 2.04 started at 04-18-2012 02:28:21
Processing (1 of 177): com.google.android.location...
Processing (2 of 177): com.sec.android.app.phoneutil...
Processing (3 of 177): com.android.defcontainer...
Processing (4 of 177): com.sec.phone...
Processing (5 of 177): com.android.contacts...
Processing (6 of 177): com.android.phone...
ORIGIONAL
RealPariah said:
Fix permissions fix found!
Alright after testing fix permissions I found a way to make it run!
Issue: fix permissions won't run from recovery (correctly (it says done in less than 60 secs and stops instantly for me saying completed and while in Android; ROM manager script runs but freezes at random points (same if you open terminal emulator and run it).
Resolution:
You have to have adb on a computer for this
Do you have the Google android installed?
If not download and install it!
[/url]http://developer.android.com/sdk/android-4.0.html
Boot in to Recovery
plug USB in to phone and computer
Go in to mounts and storage and mount /system and /data
On computer open a command line window (windows) or terminal (Linux or OSX)
Run "ADB devices" and be sure it is not all ? For device number (if it is restart recovery and reseat USB connection and run "adb kill-server" on computer) I had to run terminal as root (admin for best results bit got it to work either way really)
Now run "adb shell" after mounting /system and /data
Once that opens and you get ~# run "sh fix_permissions -l -r" just like that (with two separate - don't do -lr or it won't run)
Of it says not found mount /system
If it says something about read only variable you forgot the preceding sh (may need to do "cd /sbin" then "sh fix_permissions" if you still have an issue.
This is only way I can get fix permissions to run (even tried sh fix_permissions -l -r in Android terminal emulator and script manager to no avail)
After fix permissions ran correctly it really helped iron some small performance issues and notably helped.
I hoped that helps!
Sent from my SAMSUNG-SGH-I727 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse

I have the same issue on multiple roms. Both gingerbread and ics. If you find the solution please share. I will do like wise if i find the answer.
Sent from my brain

Seems this one has people stumped.
Mine actually works on juggernaut every time.
Sent from my GT-P7510 using xda premium

jangst123 said:
Seems this one has people stumped.
Mine actually works on juggernaut every time.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yep! Was going to say this. Fix permissions doesn't work on most roms in this section.
Jug and Macnut (based off of jug) are the only two I have had it work on.
Sent from my SGH-T989 using xda premium

I have only experienced this on ICS Roms, on GB roms Permissions work fine for me.

solracarevir said:
I have only experienced this on ICS Roms, on GB roms Permissions work fine for me.
Click to expand...
Click to collapse
Well see this is the problem.... You think it is working but have you checked logs?
Sent from my SGH-T989 using xda premium

Also having the same problem with Fix Permissions instantly finishing, but with the "/sbin/fix_permissions: line 64: UID readonly variable" error in the logs. Trying in ROM Manager also results in in random results each time I try, but never making it all the way through before it just hangs. The furthest I've gotten is 94 of 132.
Also on ICS Blackedition, but still on RC2.

I just tried another ICS rom and I still cant fix permishions. So I tried CM7 and it works fine.
Looks like this is a problem with ICS.
Sent from my SAMSUNG-SGH-T989 using xda premium

Easydoesit ics rom works when fixing permissions in cwm or from manager. Other ics roms don't so far

photrash said:
Easydoesit ics rom works when fixing permissions in cwm or from manager. Other ics roms don't so far
Click to expand...
Click to collapse
What easydoesit ICS rom!?
The only one I see has no ice cream.
Sent from my SAMSUNG-SGH-T989 using xda premium

jangst123 said:
What easydoesit ICS rom!?
The only one I see has no ice cream.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't know but for some reason it's in the general forum and never made it to the development section. Remember to use the autorotation fix since the OP didn't update the ROM yet. http://forum.xda-developers.com/showthread.php?t=1576617
I ran into some weird superuser error...sometimes i lose root access when im trying to delete or change a system file. maybe i gotta wipe data and caches some more and reflash.
The fix permissions work fine for this ROM work fine in CWM and also in ROM manager

photrash said:
I don't know but for some reason it's in the general forum and never made it to the development section. Remember to use the autorotation fix since the OP didn't update the ROM yet. http://forum.xda-developers.com/showthread.php?t=1576617
I ran into some weird superuser error...sometimes i lose root access when im trying to delete or change a system file. maybe i gotta wipe data and caches some more and reflash.
The fix permissions work fine for this ROM work fine in CWM and also in ROM manager
Click to expand...
Click to collapse
I'll check it out later.
But if this is ture I hope a developer takes a look at it and figurers out why fix permishions only works on that ROM and not the other ICS ROMs

jangst123 said:
I'll check it out later.
But if this is ture I hope a developer takes a look at it and figurers out why fix permishions only works on that ROM and not the other ICS ROMs
Click to expand...
Click to collapse
Yeah that and the ORIGINAL leak by racer is the only ics roms that work. I tried all ics t989 roms haha. IM currently running some skyrocket roms and fix permissions isn't working properly in cwm. It's frustrating sometimes because I need it to work haha

RealPariah posted a workaround over in the Blackedition ICS thread that worked for me:
RealPariah said:
Fix permissions fix found!
Alright after testing fix permissions I found a way to make it run!
Issue: fix permissions won't run from recovery (correctly (it says done in less than 60 secs and stops instantly for me saying completed and while in Android; ROM manager script runs but freezes at random points (same if you open terminal emulator and run it).
Resolution:
You have to have adb on a computer for this
Boot in to Recovery
plug USB in to phone and computer
Go in to mounts and storage and mount /system and /data
On computer open a command line window (windows) or terminal (Linux or OSX)
Run "ADB devices" and be sure it is not all ? For device number (if it is restart recovery and reseat USB connection and run "adb kill-server" on computer) I had to run terminal as root (admin for best results bit got it to work either way really)
Now run "adb shell" after mounting /system and /data
Once that opens and you get ~# run "sh fix_permissions -l -r" just like that (with two separate - don't do -lr or it won't run)
Of it says not found mount /system
If it says something about read only variable you forgot the preceding sh (may need to do "cd /sbin" then "sh fix_permissions" if you still have an issue.
This is only way I can get fix permissions to run (even tried sh fix_permissions -l -r in Android terminal emulator and script manager to no avail)
After fix permissions ran correctly it really helped iron some small performance issues and notably helped.
I hoped that helps!
Click to expand...
Click to collapse
I had to do the "cd /sbin" thing before running "sh fix_permissions -l -r" inside the adb shell, but it actually ran without a hitch!

Not quite a solution, but it gets the job done!
You still will not be able to fix perms in CWM or ROM Manager
I had to do the same "cd /sbin" then "sh fix_permissions -l -r" to get it to work
mimicvii said:
RealPariah posted a workaround over in the Blackedition ICS thread that worked for me:
I had to do the "cd /sbin" thing before running "sh fix_permissions -l -r" inside the adb shell, but it actually ran without a hitch!
Click to expand...
Click to collapse

Thank you!! Been going crazy trying to find a solution!

Thanks for this. resolved some issues I had with a specific application force closing on me.

I am under the impression this has to do with the fact that a lot of I727 users, if not all, are having issues mounting /system inside of ICS. Mounting in recovery is fine but it seems that mounting /system inside of ICS works ONCE after flashing a kernel and then never again.

Wow, I'm really stuck. I tried without "SU" but that didn't help. Here is my cmd screen:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
26d7140a device
C:\Adb>adb shell
sh-3.2$ cd /sbin
cd /sbin
sh: cd: /sbin: Permission denied
sh-3.2$ su
su
sh-3.2# cd /sbin
cd /sbin
sh-3.2# sh fix_permissions -l -r
sh fix_permissions -l -r
sh: fix_permissions: No such file or directory
sh-3.2#
Any help or guidance is appreciated!

Give this a try and report back
First download http://www.getyourdroidon.com/shiversftp/fix_permissions.sh
Put it on the root of your sd card and go into terminal emulator.
Type: su and hit enter
Type: sh /sdcard/fix_permissions.sh and hit enter
Type reboot and hit enter
Should be all fixed.

[Q] Can't access /data in android (rooted)

Hi, I've tried SuperSU and SuperUser.
apps and adb shell can't access the /data partition.
it says that I don't have enough permissions ...
with adb shell I can cd to it, but even an "ls" says operation not permitted
I can access it just fine in CWM using adb shell
all other root directory works fine....
Does anybody know what's going on ? did i miss something ? I'm no expert when it comes to this
thanks for your help

kout said:
Hi, I've tried SuperSU and SuperUser.
apps and adb shell can't access the /data partition.
it says that I don't have enough permissions ...
with adb shell I can cd to it, but even an "ls" says operation not permitted
I can access it just fine in CWM using adb shell
all other root directory works fine....
Does anybody know what's going on ? did i miss something ? I'm no expert when it comes to this
thanks for your help
Click to expand...
Click to collapse
After typing adb shell and entering you have to type su and press enter again, then you`ll have the permissions you need

But how come root browser can't access that directory?
And why can I go to /system without having to type su first

kout said:
But how come root browser can't access that directory?
And why can I go to /system without having to type su first
Click to expand...
Click to collapse
How do you mean: root browser/ file manager on the phone to access system date? You have to be rooted to access system data on the phone. What exactly do you want to do?

Weird stuff, it's working with solid explorer, I had tried with rom toolbox browser and some other root browser from the play store and it wouldn't work
Thanks for the "su" tip I forgot you had to be su to access that folder :-S

kout said:
Weird stuff, it's working with solid explorer, I had tried with rom toolbox browser and some other root browser from the play store and it wouldn't work
Thanks for the "su" tip I forgot you had to be su to access that folder :-S
Click to expand...
Click to collapse
Is you`re phone rooted mate? The su command is for adb from your computer!

Of course it's rooted, I do have a bit of experience with that. It's just weird that certain root browser can't access the data partition despite having granted su permission to the app. Anyway its working great with solid explorer now, and with adb I've got the su command
I actually have the voice stuck on the same street in navigation, (known bug) so I had to delete some cached speech data in the data partition
I did it through cwm but I was wondering why it wasn't letting me do it once booted. Anyway thanks

[Q] Nexus 4 - SU not working anymore but binary present

Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...

I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse

it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse

Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums

I9195 Rooted device, but unable to get root access using adb shell su

Hi All,
I did root my device following this procedure by arco68: http://forum.xda-developers.com/showthread.php?t=2364980
Worked perfectly and naming few applications they are ok, like Terminal Emulator, BusyBox, ES File exploree, etc, and ran different root verifiers program which confirmed root status.
But when using adb shell su, I'm unable to get root access as you can see here
Code:
C:\Users\marco\Downloads\Android\adt-bundle-windows-x86_64-20140702\sdk\platform
-tools>adb devices
List of devices attached
08985214 device
C:\Users\marco\Downloads\Android\adt-bundle-windows-x86_64-20140702\sdk\platform
-tools>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $
1|[email protected]:/ $
1|[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009
(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt)
,3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $
It does generate a new prompt adding "1|", and as soon as you execute a comand it returns to the original prompt, but never you have root access
I've been researching across, but unable to find something similar.
All the procedures for permission denied that I have found point to rooting the device which is why I already did.
I have redone the procedure in case something was wrong, but no changes.
Hope somebody knows what is happening
Thanks in advance

Hi,
I had this problem on terminal emulator (same when typing su) on the s4 mini rooted the same way yours is.
It occurred after I installed some apps including some google updates I installed manually - I don't know which of them caused that. But after I had this problem I realised that all apps don't have the root access anymore - SuperSU, RootChecker... And SuperSU didn't gave apps like TerminalEmulator and RootExplorer anymore root access.
This problem has been solved itself after I restarted my phone (because of another reason). And I had my rooted phone again.
So after your problem occurred - did you try another app that needs root access again? Does it have still root access? If no, try restarting too (if you haven't done that already) - maybe it helps you too...