On stock OTA JB rooted flashed lean kernel but when I type ffc in console emulator it just says no file or directory found. Anyone know whats wrong?
Sent from my SCH-I535 using Tapatalk 2
Did you try and type "su" then enter, then type ffc?
Not sure if you need super user access to turn on fast charge.
Sent through mental telepathy...or my unlocked SGS3
Dunno if it will help, make sure before you type FFC, you type SU, then enter, to grant the terminal super user rights.
If not try the app terminal emulator. I have had issues in the past with different terminal apps, including this one, but found other terminal apps did work for the commands I was having trouble with. Currently terminal emulator always works when I use it for commands.
Related
I'm sure i'm not the only one that has noticed that you can't update terminal emulator with modded firmware, i did a mild look through the searches, and didn't find what i was looking for, is there a means to update this, i've tried takeing it out of white list and then updating, but no go... Not that its a big deal TE works, its just an annoying knawing thing in the back of my mind, knowing there is an update on the market, and i can't have it
Delete the terminal app in terminal by
su
cd /system/app
ls
them find the app that starts with com. something
type rm -> name of the app
update it in market
card13 said:
Delete the terminal app in terminal by
su
cd /system/app
ls
them find the app that starts with com. something
type rm -> name of the app
update it in market
Click to expand...
Click to collapse
gives me a read only error, i have to chmod it first right? have no clue how to do that right now, have to look it up. Thanks for pointing me to the proper file though
It'd probably be best to use adb.exe (available in the android SDK) to remove terminal emulator rather than using terminal emulator.
Also, in order to change anything in the /system partition, you need to remount it as read/write.
With adb this is easy:
Make sure your android has debug mode enabled (which I think is by default in all JF releases)
Hook it up to your computer with the USB cable
Open up a command prompt in windows (or whatever other OS you're using that has the Android SDK) and go to the tools directory in the SDK
Type "adb devices" to make sure adb sees your phone, if it doesn't, well uh...it's not working right, and you'll have to figure out why
Type "adb remount" to remount the /system partition as read-write
Type "adb shell" this will give you shell access to your G1, from there you can delete stuff from the /system partition. I think you might also be able to use "adb uninstall" but I don't know if that works for the /system/app folder.
thanks for the info TM will play with the sdk tools and see what i can do, they have been giving me a headache on linux, but then i haven't played with linux in about 6 years.. its come along way. Thanks again for the info wait 2 secs to reload the image
I've noticed that, too. I don't see a reason why I need to update TE, the one I have works just fine.
here your answer in the link below
this will allow you to remove the terminal and install the new one from market
http://forum.xda-developers.com/showthread.php?p=3287558
Hello,
First off, let me say, this is my first android device. I have some experience with linux and previously owned a rooted Palm Pre.
I have an HTC EVO, and have rooted it (at least I think it's rooted), with a program called unrEVOked. It flashed a NAND called ClockworkMod Recovery (2.5.0.1), and I can get to the shell using the adb shell command when it is in recovery mode.
However, even with the SuperUser app installed, I'm having trouble running sudo or any command at the terminal (on the phone), and the apps appear to also be having trouble executing any commands that are within /sbin/ (such as killall for the Shark capture packet sniffer). This is persistent while in USB Debugging Mode and running adb shell.
I didn't have to interact with the system at all during unrEVOked, including creating a user, which struck me as odd. Also, never set up an SSH server daemon, but that's okay. I'd be a happy guy if 1) I could actually use commands in /sbin/ and programs could also do this. Note that at a terminal, when I run aname, it tells me that I don't have permission. sudo su does the same.
Alright... I can get su root via the adb shell and terminal emulator.
androidpolice com/2010/05/24/that-was-quick-evo-4gs-already-been-rooted/
It still doesn't appear that apps like a file manager, and Shark packet sniffer can get root though; even with granting them SuperUser access. Any ideas?
Any help is appreciated.
Thanks,
Matt
Hi, i'm currently on a donut ROM on my G1, when I type su into terminal emulator, rather then getting prompted to give terminal emulator permissions, it instead just says Permission Denied
How can I give Terminal Emulator SU permissions?
Have you went into the SU app and told it to forget Terminal then tried allowing it again?
Usually does the trick
I am trying to update a few things on my G2 and when I go in to adb shell, the prompt opens at the superuser level (the # prompt). Typing exit exits adb shell, it does not take me to the $ prompt. Any thoughts on how I can get to the $ prompt? It has worked fine in the past.
Thanks
Edit: disregard. It appears that I still have the regular adb shell and SU levels, but both have the # prompt. Still curious if anybody knows what causes that, but it seems to be working as it should.
Some custom roms open to a root shell... if you have a stock rom then idk what's going on
Sent from my Droid using Tapatalk
I actually first noticed it when on CM 6.1, but it was still showing the # prompt when I restored to my rooted stock. But, there still is the difference between $ and #, I just need to make sure I keep track of which one I am really using at the moment.
if you use 2nd-init or custom boot image you will get default #
I apologize for asking this because I'm SURE it's been asked - just finally gave up on my search. I performed "FIRST" and "SECOND" steps but stopped when I read this: "If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE." ... This is where I want to be (I think) yet when i downloaded "Shell Terminal Emulator" and then ran the "su" command - it would never take me to a hash prompt - so it seems (to me) like i REALLY do not have root. Do I need to do more?
ATT JB 4.1.1 Galaxy SIII
Get an app from the play store that checks if you have root or not and use it.
Sent from my SGH-T999 using xda app-developers app
ANSWERED
Thanks Pennycake - I already had two apps indicating that I infact DO have root access - but having a little Solaris background - I wanted to see it on the Command Line.
One word of advise - NEVER get an app from the Playstore called: Shell Terminal Emulator (version 1.0.1) ... BUT instead get: "Android Terminal Emulator" by Palevich - this performed as expected (su changes the prompt to: #).
Thanks Again!