I've installed modaco's custom rom (2.6) for a few times; when i use 'adb shell' and try to do a "ls" it gives me the following:
Code:
C:\>adb shell
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# ls
ls
[1;34mapp[0m [1;34mcustomize[0m [1;34mframework[0m [1;34mmedi
a[0m [1;34mxbin[0m
[1;34mbin[0m [1;34metc[0m [1;34mlib[0m [1;34msd[
0m
[0;0mbuild.prop[0m [1;34mfonts[0m [1;34mlost+found[0m [1;34musr[
0m
# ls
ls
[1;34mapp[0m [1;34mcustomize[0m [1;34mframework[0m [1;34mmedi
a[0m [1;34mxbin[0m
[1;34mbin[0m [1;34metc[0m [1;34mlib[0m [1;34msd[
0m
[0;0mbuild.prop[0m [1;34mfonts[0m [1;34mlost+found[0m [1;34musr[
0m
but when I boot into recovery mode it works fine:
Code:
ls
app customize framework media xbin
bin etc lib sd
build.prop fonts lost+found usr
/system # cd
anyone got similar problems?
kazuni said:
I've installed modaco's custom rom (2.6) for a few times; when i use 'adb shell' and try to do a "ls" it gives me the following:
Code:
C:\>adb shell
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# ls
ls
[1;34mapp[0m [1;34mcustomize[0m [1;34mframework[0m [1;34mmedi
a[0m [1;34mxbin[0m
[1;34mbin[0m [1;34metc[0m [1;34mlib[0m [1;34msd[
0m
[0;0mbuild.prop[0m [1;34mfonts[0m [1;34mlost+found[0m [1;34musr[
0m
# ls
ls
[1;34mapp[0m [1;34mcustomize[0m [1;34mframework[0m [1;34mmedi
a[0m [1;34mxbin[0m
[1;34mbin[0m [1;34metc[0m [1;34mlib[0m [1;34msd[
0m
[0;0mbuild.prop[0m [1;34mfonts[0m [1;34mlost+found[0m [1;34musr[
0m
but when I boot into recovery mode it works fine:
Code:
ls
app customize framework media xbin
bin etc lib sd
build.prop fonts lost+found usr
/system # cd
anyone got similar problems?
Click to expand...
Click to collapse
Those are ANSI color codes and they appear because ls thinks you have a terminal that supports it. Paul will probably fix this in an upcoming version.
If you want to get ls to behave normally you can run the following command.
alias ls="ls --color=no"
After that ls should produce normal output.
packetlss said:
Those are ANSI color codes and they appear because ls thinks you have a terminal that supports it. Paul will probably fix this in an upcoming version.
If you want to get ls to behave normally you can run the following command.
alias ls="ls --color=no"
After that ls should produce normal output.
Click to expand...
Click to collapse
Ahh, thanks for the heads up. got it
same for me here, but under ftp (ftpserver) and usb file connection
Hello,
After flashing the most recent TuchMi ROM on my galaxy s3, trying it out and restoring to my nandroid backup of kyanrom I have a TuchMi folder I cannot delete. I have tried ES Fileexplorer and Root Explorer both. There are three zip files in the TuchMi folder that cannot be deleted, tells me file permissions cannot be changed.
That said, the timestamp on the /TuchMi folder is 8 March 1970. I am wondering if this is causing something to fail in deleting or being able to change permissions. I don't know if this is right place to ask this question but I can't ask in the TuchMi thread because I am too new. Anyone have an idea on what I can do to fix this?
Thanks
JMD
rezin44 said:
Hello,
After flashing the most recent TuchMi ROM on my galaxy s3, trying it out and restoring to my nandroid backup of kyanrom I have a TuchMi folder I cannot delete. I have tried ES Fileexplorer and Root Explorer both. There are three zip files in the TuchMi folder that cannot be deleted, tells me file permissions cannot be changed.
That said, the timestamp on the /TuchMi folder is 8 March 1970. I am wondering if this is causing something to fail in deleting or being able to change permissions. I don't know if this is right place to ask this question but I can't ask in the TuchMi thread because I am too new. Anyone have an idea on what I can do to fix this?
Thanks
JMD
Click to expand...
Click to collapse
Run "fix permissions" from recovery, and then try again.
(One of the most common reasons you can't delete something, even as root, is that its file attributes are set to "immutable" (which under linux often means you've been hacked, but no worries here))
Thanks for the quick reply but that didn't seem to fix it. I am at a loss, the folder is only 32meg so I am not too concerned but it is a little annoying. If there's another thing you can think of I'd appreciate it.
Sent from my SGH-I747M using Tapatalk 2
rezin44 said:
Thanks for the quick reply but that didn't seem to fix it. I am at a loss, the folder is only 32meg so I am not too concerned but it is a little annoying. If there's another thing you can think of I'd appreciate it.
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
Nuke it (rm -rf somedir) from an adb shell, so you can see the actual error.
zmore said:
Nuke it (rm -rf somedir) from an adb shell, so you can see the actual error.
Click to expand...
Click to collapse
Here's what it says.
Code:
[email protected]:/ $ cd sdcard
cd sdcard
[email protected]:/sdcard $ ls
ls
Alarms
Albums
Android
Application
DCIM
Download
EVA
Evernote
GOLauncherEX
GoStore
Library
Movies
Music
Notifications
Pictures
PlayerPro
Podcasts
Ringtones
SpeedSoftware
TuchMi
ba-superkeyboard
backups
data
ivona
mdm
media
rootz
svox
temp
[email protected]:/sdcard $ rm -rf TuchMi
rm -rf TuchMi
rm failed for -rf, No such file or directory
255|[email protected]:/sdcard $ rm TuchMi
rm TuchMi
rm failed for TuchMi, Is a directory
255|[email protected]:/sdcard $ cd TuchMi
cd TuchMi
[email protected]:/sdcard/TuchMi $ ls
ls
Stock_SystemUI.zip
Voice_Reinstall.zip
XXBLG1_AndroidGX-MOD_NexusBattery.zip
[email protected]:/sdcard/TuchMi $ rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi $ ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi $
and these are the permissions of the subject directory.
drwxrwxr-x root sdcard_rw 1970-03-08 01:48 TuchMi
Thank you for taking the time to respond to this.
JMD
I had to delete it while plugged into my pc. Was just driving me crazy that I couldn't get rid of it.
Well, I've resigned myself to failure deleting these three files and the folder they're in. I've tried 8 or 9 different file managers. I downloaded and installed adb, learned enough to really screw up my phone, but that didn't work either. I tried deleting them through windows and debian too.
That said, I'm just going to live with things as they are now. In the future when a more mature JB rom comes out I'll try that but my question is this, can I just format (wipe) my sdcard partition and restore the stock at&t/Samsung rom using Odin?
Sent from my SGH-I747M using Tapatalk 2
rezin44 said:
Well, I've resigned myself to failure deleting these three files and the folder they're in. I've tried 8 or 9 different file managers. I downloaded and installed adb, learned enough to really screw up my phone, but that didn't work either. I tried deleting them through windows and debian too.
That said, I'm just going to live with things as they are now. In the future when a more mature JB rom comes out I'll try that but my question is this, can I just format (wipe) my sdcard partition and restore the stock at&t/Samsung rom using Odin?
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
I noticed in your terminal output, that you weren't root (# vs $). "su" to root, and try again.
zmore said:
I noticed in your terminal output, that you weren't root (# vs $). "su" to root, and try again.
Click to expand...
Click to collapse
Yeah, I caught that before you mentioned it yesterday but I thought I'd try it again as this is very new to me and I am using cheat sheets with adb common commands to navigate through this. Here is the output though. Still no bueno..
Code:
drwxrwxr-x root sdcard_rw 1970-03-08 01:48 TuchMi
drwxrwxr-x root sdcard_rw 2012-09-04 08:05 ba-superkeyboard
drwxrwxr-x root sdcard_rw 2012-09-04 09:45 backups
drwxrwxr-x root sdcard_rw 2012-09-05 02:05 clockworkmod
drwxrwxr-x root sdcard_rw 2012-09-03 20:09 data
drwxrwxr-x root sdcard_rw 2012-09-04 14:24 ivona
drwxrwxr-x root sdcard_rw 2012-08-31 09:00 mdm
drwxrwxr-x root sdcard_rw 2012-08-14 17:39 media
drwxrwxr-x root sdcard_rw 2012-09-03 21:31 rootz
drwxrwxr-x root sdcard_rw 2012-09-04 23:14 temp
[email protected]:/sdcard # rm -rf TuchMi
rm -rf TuchMi
rm failed for -rf, No such file or directory
255|[email protected]:/sdcard # cd TuchMi
cd TuchMi
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rezin44 said:
Yeah, I caught that before you mentioned it yesterday but I thought I'd try it again as this is very new to me and I am using cheat sheets with adb common commands to navigate through this. Here is the output though. Still no bueno..
Code:
...snip...
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
Click to expand...
Click to collapse
Weird. As root, you normally only see that for immutable files, so, try:
lsattr foo.zip
and if you see an "i" flag for immutable, do a:
chattr -i file.zip
zmore said:
Weird. As root, you normally only see that for immutable files, so, try:
lsattr foo.zip
and if you see an "i" flag for immutable, do a:
chattr -i file.zip
Click to expand...
Click to collapse
Code:
D:\android-sdk\platform-tools>adb devices
List of devices attached
b41c0497 device
D:\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cd sdcard/TuchMi
cd sdcard/TuchMi
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Ne
usBattery.zip
[email protected]d:/sdcard/TuchMi # lsattr Stock_SystemUI.zip
lsattr Stock_SystemUI.zip
lsattr: reading Stock_SystemUI.zip: Function not implemented
[email protected]:/sdcard/TuchMi # lsattr Voice_Reinstall.zip
lsattr Voice_Reinstall.zip
lsattr: reading Voice_Reinstall.zip: Function not implemented
[email protected]:/sdcard/TuchMi #
It kicked out those "Function not implemented" errors, I did some searching and some of the sites that popped up were fedora and ubuntu and they hinted at maybe I have the wrong file system for lsattr to work? In windows it shows the file system on both sdcards, int and ext, as 'generic hierarchical'.
I have had this issue with a couple of folder where I could NOT delete them on my i777 no matter what/how I tried. The files/folders I had were some that I extracted. Then when I was done with it I couldn't delete it. After I had two folders I couldn't delete as it too was bugging me was I connected up my phone via ums to my PC and transfered everything I wanted/needed from my sdcard (internal unremovable). Then when I had it all backed up I went into recovery and formatted my internal sdcard (I removed my external sdcard first to be safe). Then I booted up phone and saw it was all clean. Then I reconnected to PC and transferred all my needed files/folders back onto phone.
I THINK what happened was somehow it was a corrupted file and caused my issues. Completely wiping my sdcard fixed it though. Good luck to you.
Sent from My SGH-I777 Running Red Reaper Rom
RockRatt said:
I have had this issue with a couple of folder where I could NOT delete them on my i777 no matter what/how I tried. The files/folders I had were some that I extracted. Then when I was done with it I couldn't delete it. After I had two folders I couldn't delete as it too was bugging me was I connected up my phone via ums to my PC and transfered everything I wanted/needed from my sdcard (internal unremovable). Then when I had it all backed up I went into recovery and formatted my internal sdcard (I removed my external sdcard first to be safe). Then I booted up phone and saw it was all clean. Then I reconnected to PC and transferred all my needed files/folders back onto phone.
I THINK what happened was somehow it was a corrupted file and caused my issues. Completely wiping my sdcard fixed it though. Good luck to you.
Sent from My SGH-I777 Running Red Reaper Rom
Click to expand...
Click to collapse
Thanks, Im gonna give this a try
Well, it's beat me. After trying all the above things I still cannot delete the TuchMi folder. I tried formatting the sdcard partition from windows, CWM, and fedora. All three did format and manage to wipe everything from that partition except the TuchMi folder.
All I can say is be wary of that ROM.
Sent from my SGH-I747M using Tapatalk 2
After the Android 4.3 update to build JWR66Y neither the Root Explorer function of ES File Explorer nor the mount command shown below work any more:
>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ #
What happened? How can I make any changes to /system now, short of going through the recovery?
Google search "changelog JWR66V JWR66Y"
a manta sent this.
Hi xda,
i need some help,
i have à h815 with bl unlock, twrp 3.0.0.0, stock V20d, root, xposed but i can not change permission in system partition #strange
root browser, solid explorer, es, can copy or rename in system partition but when i change permission, the operation failed and the system partition past to read-only and unable to remount
same with adb (i use adb insecure) , :
C:\Users\user>adb shell
[email protected]:/ $ su
su
[email protected]:/ # getenforce
getenforce
Enforcing
[email protected]:/ # setenforce permissive
setenforce permissive
[email protected]:/ # getenforce
getenforce
Permissive
[email protected]:/ #
C:\Users\user>adb shell #enable adb insecure (chainfire app)
[email protected]:/ # ls system/media -la
ls system/media -la
drwxr-xr-x root root 2016-01-15 10:28 audio
-rw-r--r-- root root 8979780 2016-01-15 10:28 bootanimationold.zip
drwxr-xr-x root root 2016-01-15 10:28 gallery
drwxr-xr-x root root 2016-01-15 10:28 ims
-rw-r--r-- root root 4281625 2016-01-15 10:28 shutdownanimation.zip
[email protected]:/ # cp sdcard/download/bootanimation.zip system/media/bootanimation.zip
nload/bootanimation.zip system/media/bootanimation.zip <
cp: system/media/bootanimation.zip: Read-only file system
1|[email protected]:/ # mount -o remount rw /system
mount -o remount rw /system
[email protected]:/ # cp sdcard/download/bootanimation.zip system/media/bootanimation.zip
nload/bootanimation.zip system/media/bootanimation.zip <
[email protected]:/ # ls system/media -la
ls system/media -la
drwxr-xr-x root root 2016-01-15 10:28 audio
-rw------- root root 46802200 2016-03-03 14:54 bootanimation.zip
-rw-r--r-- root root 8979780 2016-01-15 10:28 bootanimationold.zip
drwxr-xr-x root root 2016-01-15 10:28 gallery
drwxr-xr-x root root 2016-01-15 10:28 ims
-rw-r--r-- root root 4281625 2016-01-15 10:28 shutdownanimation.zip
[email protected]:/ # chmod 0644 system/media/bootanimation.zip
chmod 0644 system/media/bootanimation.zip
chmod: chmod 'system/media/bootanimation.zip' to 100644: Read-only file system
1|[email protected]:/ # rm system/media/bootanimation.zip
rm system/media/bootanimation.zip
rm ro system/media/bootanimation.zip (y/N):y
y
rm: system/media/bootanimation.zip: Read-only file system
1|[email protected]:/ # mount -o remount rw /system
mount -o remount rw /system
mount: Read-only file system
any idea ?
thanks & sorry for my frenchy english
anybody have a idea ??