My problem is that when I run the terminal as super user it's can't read sdcard it's give me nothing .
This is the commands
===========================
[email protected]:/ $ su
[email protected]:/ # cd sdcard
[email protected]:/sdcard # ls
[email protected]:/sdcard #
===========================
But without running as super user give me
===========================
[email protected]:/ $ cd sdcard
[email protected]:/sdcard $ ls
Alarms
Android
Application
DCIM
Documents
Download
INDI
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
SMemo
SecretBox
ShareShot
Subtitles
UCDownloads
WhatsApp
comquoordtapatalkxdapreactivity
data
media
viber
[email protected]:/sdcard $
=============================
I've rooted my phone with CF-Auto-Root-Chainfire
Please what is the solution.
Strange behaviour try adb shell then su then ls /sdcard/ or you can try other way rather then /sdcard.. Do ls on root folder there is another mount point of sdcard as well like /dev/sdcard or /block/legacy/0 something like that.. Dont remembered the excact partition name but it is there..
Related
Hello,
I have a Samsung Captivate running the I9000XWJM2 Firmware on the stock kernel with Samset 1.7 ROM installed. Rooted with busybox. I've noticed that intermittently my ADB Shell will just quit. I was tinkering with the userinit.sh hack to a2sd my phone when it stopped giving me any output. Is this a known issue and is there a repair action other than reflashing the phone?
Here is an example:
C:\Program Files (x86)\Android-SDK\tools>adb shell
$ su
su
# ls
ls
# pwd
pwd
/
# busybox --help
busybox --help
# cd /system
cd /system
# pwd
pwd
/system
# ls
ls
# ls -al
ls -al
# mount
mount
# busybox mount
busybox mount
Click to expand...
Click to collapse
Any guidance would be greatly appreciated. I really don't want to rebuild my phone again.
My root had somehow broken. Re-applying the root update.zip seems to have repaired the issue.
Hello,
So I did something stupid. Not sure what, but I managed to get my phone into a state where NO shell commands work other than cd and su.
./adb shell
$ su
# ls
# top
# free
free: not found
# cat
# df
# more
more: not found
# less
less: not found
# busybox
busybox: not found
# sh
# ssh
ssh: not found
# vi
vi: not found
#
The phone is a Motorola MB502 (Charm), rooted using Universal Androot 1.63.
Currently running the stock Telus ROM (don't really have a choice there...)
Any way I can get this working ?
There is a market app that will attempt to install busybox, if you want to try that.
Do you mean
stericson.busybox ?
because I can't seem to find it on the market, and can't use MarketEnabler since my shell is broken.
With a bit of searching I noticed that all the files in /system/bin seem to be 0-byte files. Perhaps someone who has a Charm could post these files?
$adb pull /system/bin/top
$ls -l
total 0
-rw-r--r-- 1 root root 0 2011-01-18 17:25 top
$
I am trying to diagnose my alarm manager service high wakelocks, which i found out thanks to betterbatterystats. I only have my s3 and asus transformer for computers, no windows machine. I am on synergy 1.7 and imoseyon kexec kernel beta 0.1. I read dumping alarm to a text file yoy can diagnose this.
Here is what happens
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # dumpsys alarm > alarmdump.txt
sh: cannot create alarmdump.txt: Read-only file system
1|[email protected]:/ #
Is doing this possible with terminal emulator?
I got it, just got to change to sdcard with cd.. enter then cd sdcard enter
Hopefully someone can point me were to look for this. When ever I turn on my tablet as the the homepage is loading I am getting a notification "Warning logging to file is enabled" I do not remember setting any apps to log but, I could have accidentally hit a button without knowing because the touch is so sensitive.
lartomar2002 said:
Hopefully someone can point me were to look for this. When ever I turn on my tablet as the the homepage is loading I am getting a notification "Warning logging to file is enabled" I do not remember setting any apps to log but, I could have accidentally hit a button without knowing because the touch is so sensitive.
Click to expand...
Click to collapse
You can try the following commands in adb shell or a terminal program:
su
cd /data/dalvik-cache
fgrep -l 'logging to file is enabled' *.dex
_that;to 37778048 said:
You can try the following commands in adb shell or a terminal program:
su
cd /data/dalvik-cache
fgrep -l 'logging to file is enabled' *.dex
Click to expand...
Click to collapse
Here is what was returned using Terminal Emulator:
[email protected]:/ $ su
[email protected]:/ # cd /data/dalvik-cache
[email protected]:/data/dalvik-cache # fgrep -l 'logging to file is enabled' *.dex
[email protected]@[email protected]
[email protected]:/data/dalvik-cache #
Update: Went to the BubbleUpnP app and found the "logging to file" and diabled it. Thanks_that
lartomar2002 said:
Here is what was returned using Terminal Emulator:
Code:
[email protected]:/ $ su
[email protected]:/ # cd /data/dalvik-cache
[email protected]:/data/dalvik-cache # fgrep -l 'logging to file is enabled' *.dex
[email protected]@[email protected]
[email protected]:/data/dalvik-cache #
Click to expand...
Click to collapse
Great, so now you know it's the BubbleUPnP app which produces this message.
$ cd /sdcard
$ ls
...
...
...
$ su
# cd /sdcard
# ls
#
Does anyone have an explanation for this error?
I have android 4.4.2 and a blackview crown.
Thanks for help
@r4c0r,
Try it like this, instead:
Code:
$ su
# ls /sdcard