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)
Related
I have an eris running Zen-EXP Rev 7. Up until a couple of weeks ago, everything was peachy keen, and SU was working fine. A few weeks ago I decided to try flashing a newer version of SU (the one found here on the xda forums), and made a Nand backup before doing so. After flashing the updated SU, it force closed on me any time I tried to open it, and programs were unable to gain root access. So I restored my Nand backup, but now I'm having a new issue.
Basically, SU (the restored old version) opens fine from the programs menu, and programs I have already granted SU access to (SetCPU, for instance) work just fine. However, any time a new program asks for SU access, SU hangs at a black screen, so I'm unable to give any new programs root access.
Is there an easy way to fix this, or am I going to have to totally wipe/reflash my phone? I tried updating SU in a variety of ways and reflashing the rom WITHOUT a wipe, but none of those attempts fixed the problem.
Thanks.
Did you wipe before restoring your nandroid? And you're positive you flashed the right SU? The one meant for froyo? They always release TWO SU's, one for froyo and one not.
I didn't read the entire first post but make sure you have usb debugging mode turned on... My SU was hanging last week until I rechecked that.
theEastonator said:
I have an eris running Zen-EXP Rev 7. Up until a couple of weeks ago, everything was peachy keen, and SU was working fine. A few weeks ago I decided to try flashing a newer version of SU (the one found here on the xda forums), and made a Nand backup before doing so. After flashing the updated SU, it force closed on me any time I tried to open it, and programs were unable to gain root access. So I restored my Nand backup, but now I'm having a new issue.
Basically, SU (the restored old version) opens fine from the programs menu, and programs I have already granted SU access to (SetCPU, for instance) work just fine. However, any time a new program asks for SU access, SU hangs at a black screen, so I'm unable to give any new programs root access.
Is there an easy way to fix this, or am I going to have to totally wipe/reflash my phone? I tried updating SU in a variety of ways and reflashing the rom WITHOUT a wipe, but none of those attempts fixed the problem.
Thanks.
Click to expand...
Click to collapse
Some versions and ROMs require you to do this before you use anything that needs SU:
Install Android SDK if you haven't already.
Plug in the phone to the computer with USB Debugging on.
Open up a command prompt and navigate to your tools folder.
C:\android-sdk-windows\tools> adb shell
#
# su
(type adb shell, press enter, then type su, and press enter).
Your phone should pop up with the REAL allow/deny screen, without it being all black. Just for the first time.
Hit allow always, and move on.
Then when you want to use Root Explorer or SetCPU or anything that needs root permission, you WON'T just get that hanging black screen. It'll work.
Some ROMs and versions of SuperUser (or maybe something in bin/xbin, I'm not sure?) require you to use the SDK to use ADB shell, to get SU permissions, before you let any other apps get it.
Strange, yes.
Hope that helps.
pkopalek said:
Open up a command prompt and navigate to your tools folder.
C:\android-sdk-windows\tools> adb shell
#
# su
(type adb shell, press enter, then type su, and press enter).
Click to expand...
Click to collapse
The command "adb shell" doesn't work at all for me. In PowerShell, it just hangs at "Running script/selection".
Can you help me?
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
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
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
im having trouble wirh "reboot recovery" command in my terminal/adb shell
when i try to run in terminal, i get "not permitted!"
and "adb shell reboot recovery" returns [1] Segmentation fault reboot recovery
if i try running reboot -f in terminal or adb shell, i get "usage: reboot [-n] [-p] [rebootcommand]"
i've checked /system/bin, and the reboot bin is there
i've checked the permisssions, originally set to rwsr-sr-x
changing them to rwxr-xr-x makes no change
i found several threads with ppl having the same trouble:
http://forum.xda-developers.com/show...postcount=2040
http://forum.xda-developers.com/show....php?t=1280074
http://forum.xda-developers.com/showthread.php?t=935715
the only one i found useful is the 1st one
the only way i got reboot working is by deleting /system/bin/reboot, and using "reboot -f". without the -f switch nothing happens. if i do reboot recovery -f, it only rebots
but what i really want is to reboot into recovery. any idea on how to? i read in first linked post that the problem is in symlinked reboot to busybox, thats why deleting helped somewhat. anyone has an idea on how to get rebooting to recovery in terminal working?
oh, and my rom is rcmix 4.0. i've read that problem is rom related. but i dont want to switch, because it would defeat the purpouse in the first place....
get root permission first
did you try to "su root" first?
t0mas_ said:
im having trouble wirh "reboot recovery" command in my terminal/adb shell
when i try to run in terminal, i get "not permitted!"
and "adb shell reboot recovery" returns [1] Segmentation fault reboot recovery
if i try running reboot -f in terminal or adb shell, i get "usage: reboot [-n] [-p] [rebootcommand]"
i've checked /system/bin, and the reboot bin is there
i've checked the permisssions, originally set to rwsr-sr-x
changing them to rwxr-xr-x makes no change
i found several threads with ppl having the same trouble:
http://forum.xda-developers.com/show...postcount=2040
http://forum.xda-developers.com/show....php?t=1280074
http://forum.xda-developers.com/showthread.php?t=935715
the only one i found useful is the 1st one
the only way i got reboot working is by deleting /system/bin/reboot, and using "reboot -f". without the -f switch nothing happens. if i do reboot recovery -f, it only rebots
but what i really want is to reboot into recovery. any idea on how to? i read in first linked post that the problem is in symlinked reboot to busybox, thats why deleting helped somewhat. anyone has an idea on how to get rebooting to recovery in terminal working?
oh, and my rom is rcmix 4.0. i've read that problem is rom related. but i dont want to switch, because it would defeat the purpouse in the first place....
Click to expand...
Click to collapse
sure i did... there was something strange with the rom i was trying it on, there was several runnymede roms that had the problem