I have an Samsung Epic 4G Touch, stock rooted ICS 4.0.4, with Clockwork mod. I have developed a strange problem with my data having dates in the future. Where I first noticed this was in Titanium Backup, where sorting the apps by 'data freshness' results in numerous apps having a data changed' date up to a month in the future of the current date. I contacted Titanium Backup tech support regarding this, and did some checking based on what they told me. What I discovered is that all the apps that have a future data date have a lib file in the data/data/'app'/lib folder that seems to have a modified date with a YEAR (2012) in place of a TIME.
I have only been able to see this YEAR by going into ADB SHELL and doing a BUSYBOX LS -AL listing of the directory. Here is an example of what I see for two apps:
[email protected]:/ # busybox ls -al /data/data/com.opera.browser/lib
busybox ls -al /data/data/com.opera.browser/lib
/data/data/com.opera.browser/lib:
drwxr-xr-x 2 system system 4096 Aug 14 19:29 .
drwxr-xr-x 9 app_126 app_126 4096 Aug 14 19:29 ..
-rwxr-xr-x 1 system system 9824 Aug 20 2012 libOS14.so
-rwxr-xr-x 1 system system 9740 Aug 20 2012 libOS14fallback.so
-rwxr-xr-x 1 system system 9824 Aug 20 2012 libOS15.so
-rwxr-xr-x 1 system system 9740 Aug 20 2012 libOS15fallback.so
-rwxr-xr-x 1 system system 4948 Aug 20 2012 libOS4.so
-rwxr-xr-x 1 system system 9284 Aug 20 2012 libOS7.so
-rwxr-xr-x 1 system system 13492 Aug 20 2012 libOS8.so
-rwxr-xr-x 1 system system 9664 Aug 20 2012 libOS9.so
-rwxr-xr-x 1 system system 9568 Aug 20 2012 libOS9fallback.so
-rwxr-xr-x 1 system system 1257444 Aug 20 2012 libbream.so
-rwxr-xr-x 1 system system 9478860 Aug 20 2012 libopera.so
[email protected]:/ # busybox ls -al /data/data/com.adobe.reader/lib
busybox ls -al /data/data/com.adobe.reader/lib
/data/data/com.adobe.reader/lib:
drwxr-xr-x 2 system system 4096 Aug 14 19:30 .
drwxr-xr-x 6 app_351 app_351 4096 Aug 14 19:30 ..
-rwxr-xr-x 1 system system 3931800 Aug 25 2012 libAdobeReader.so
If I check the properties of the files that have a year instead of a time in ES Explorer, it shows the same incorrect date and time that Titanium Backup shows for the app data, it does not show the 2012 year as above.
The app with the 'earliest' incorrect data date is Opera Mobile, which is about 5-10 seconds ahead of the actual time (date is correct), I don't know if that indicates this problem somehow originates with that app. When I update an app, it generally now gets its data listed a one month in the future, so this problem is ongoing, and I first noticed it about a month ago. I made no major changes that I know of that would have caused something like this (though I actually have no idea what would cause something like this!).
Titanium support has asked if the date set in my phone could have been incorrect when these apps were installed and has since been corrected. I know of no reason this would have been the case, but I do know that the date and time are correct on my phone now but apps continue to update with the wrong date, so I don't think that could have been what caused this?
Anyone have any idea what is going on and how I can fix it? I am no Android expert, just trying to learn, and a lot of the stuff I have already said is over my head, so please don't assume that I know something... Thanks!
So what does "busybox date" claims the year is?
"ls" only outputs the year when it's significant, e.g. not the current.
kuisma said:
So what does "busybox date" claims the year is?
"ls" only outputs the year when it's significant, e.g. not the current.
Click to expand...
Click to collapse
[email protected]:/ # busybox date
busybox date
Wed Aug 22 02:38:38 PDT 2012
[email protected]:/ # busybox ls -al /data/data/com.adobe.reader/lib
busybox ls -al /data/data/com.adobe.reader/lib
drwxr-xr-x 2 system system 4096 Aug 20 21:50 .
drwxr-xr-x 5 app_31 app_31 4096 Aug 20 21:51 ..
-rwxr-xr-x 1 system system 3931800 Aug 25 2012 libAdobeReader.so
"Busybox date" reports the date and time correctly. Ran the ls command right after the date command and it still shows the file with a year and a wrong date?
I've tried uninstalling Adobe Reader, clearing cache and Dalvik cache, reinstalling Adobe Reader, still has same incorrect date.
Anybody have any ideas on this? Please. :banghead:
Related
I've seem many threads about it, but couldn't really find a solution.
I just pulled out my sdcard to do some updates in my rom (I was running Th3Bill's miui v4).
I've copied a couple of .zips to try, and when I inserted back, my I /sdcard wasn't mounting.
I've tried to format in windows (fast and normal mode); I've putted this very same card in my tabled (xoom2 me) and it was working fine.
I've tried to run format /sdcard in cwm. same error mounting;
I went to advance > show log:
CWM-based Recovery v5.0.2.7-atrix5
Error mounting /sdcard!
ro.bootloader=unknown
ro.hardware=olympus
ro.revision=33776
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand. file not found...
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
W:failed to mount /dev/block/mmcblk1 (No such file or directory)
Error mounting /sdcard!
I've tried some stuff on adb (someone mentioned it, not sure what it means):
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ln -n -s /data/media /sdcar
d
ln: /sdcard/media: File exists
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ls -a -l
drwxr-xr-x 21 root root 0 Aug 7 02:15 .
drwxr-xr-x 21 root root 0 Aug 7 02:15 ..
drwxr-xr-x 2 root root 0 Aug 7 02:15 boot
drwxrwx--x 5 system cache 4096 Aug 7 01:43 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Aug 7 02:15 datadata
-rw-r--r-- 1 root root 3875 Jan 1 1970 default.prop
drwxr-xr-x 9 root root 3260 Aug 7 02:15 dev
drwxr-xr-x 2 root root 0 Aug 7 02:15 emmc
drwxr-xr-x 2 root root 0 Aug 7 02:15 etc
-rwxr-x--- 1 root root 94404 Jan 1 1970 init
-rwxr-x--- 1 root root 783 Jan 1 1970 init.rc
drwxr-xr-x 2 root root 0 Aug 7 02:15 osh
drwxr-xr-x 2 root root 0 Aug 7 02:15 pds
drwxr-xr-x 2 root root 0 Aug 7 02:15 preinstall
dr-xr-xr-x 95 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Sep 5 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Aug 7 02:15 sd-ext
drwxr-xr-x 2 root root 0 Aug 7 02:16 sdcard
drwxr-xr-x 14 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Aug 7 02:15 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 9731 Jan 1 1970 ueventd.olympus.rc
-rw-r--r-- 1 root root 4078 Jan 1 1970 ueventd.rc
What do I need to do?
Maybe is there some pins not working in my phone? Because I've tried another micro sd and got same error!
Thanks in advance!
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
ravilov said:
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
Click to expand...
Click to collapse
Well, Actually those commands weren't trying to fix it, and I know what ls does, I wasn't much sure about how ln works, but I know that it wouldn't damage my stuff.
I just checked some stuff here, it seems to be a hardware issue indeed, when I put my nail under the card, it reads! Unfortunately I can't claim warranty. I bought this phone used, via ebay, like and year ago, from a seller in USA (I'm in Brazil). I'll try to arrange some workaround (maybe some paper under it might work,...) and hope it works properly.
hello, I need some assistance regarding a strange characters when using ADB commands from MSDOS window.
In my tablet that is running Android ICS 4.0.4, and is rooted, I replaced most of the commands that TOOLBOX was assign to issue in /system/bin. I replaced them with BUSYBOX commands, and everything works fine from the standpoint of the tablet.
But somehow I started to get some weird characters when using the LS command in ADB shell from a PC. so it happened right away after the replacement.
So I did a listing of the root files and folders in the tablet form my PC with the command:
adb shell ls -la /
and this is what I got:
C:\Windows\system32>adb shell ls -la /
total 285
drwxr-xr-x 16 root root 0 Sep 12 11:59 ←[1;34m.←[0m
drwxr-xr-x 16 root root 0 Sep 12 11:59 ←[1;34m..←[0m
drwxr-xr-x 3 root root 0 Sep 12 11:59 ←[1;34macct←[0m
drwxrwx--- 4 system cache 4096 Sep 12 13:01 ←[1;34mcache←[0m
dr-x------ 2 root root 0 Sep 12 11:59 ←[1;34mconfig←[0m
lrwxrwxrwx 1 root root 17 Sep 12 11:59 ←[1;36md←[0m -> ←[1;34m/sys/kernel/debug←[0m
drwxrwx--x 25 system system 4096 Sep 6 23:22 ←[1;34mdata←[0m
-rw-r--r-- 1 root root 89 Dec 31 1969 ←[0;0mdefault.prop←[0m
drwxr-xr-x 12 root root 14240 Sep 12 12:09 ←[1;34mdev←[0m
lrwxrwxrwx 1 root root 11 Sep 12 11:59 ←[1;36metc←[0m -> ←[1;34m/system/etc←[0m
drwxrwxrwx 3 root root 16384 Dec 31 1969 ←[1;34mfirmware←[0m
-rwxr-x--- 1 root root 98736 Dec 31 1969 ←[1;32minit←[0m
-rwxr-x--- 1 root root 2344 Dec 31 1969 ←[1;32minit.goldfish.rc←[0m
-rwxr-x--- 1 root root 15813 Dec 31 1969 ←[1;32minit.qcom.rc←[0m
-rwxr-x--- 1 root root 11014 Dec 31 1969 ←[1;32minit.qcom.sh←[0m
-rwxr-x--- 1 root root 30858 Dec 31 1969 ←[1;32minit.qcom.usb.rc←[0m
-rwxr-x--- 1 root root 8786 Dec 31 1969 ←[1;32minit.qcom.usb.sh←[0m
-rwxr-x--- 1 root root 19420 Dec 31 1969 ←[1;32minit.rc←[0m
-rwxr-x--- 1 root root 3491 Dec 31 1969 ←[1;32minit.target.rc←[0m
-rwxr-x--- 1 root root 12760 Dec 31 1969 ←[1;32minitlogo.rle←[0m
drwxrwxr-x 6 root system 0 Sep 12 11:59 ←[1;34mmnt←[0m
drwxrwx--x 4 system system 1024 Jul 19 22:25 ←[1;34mpersist←[0m
dr-xr-xr-x 900 root root 0 Dec 31 1969 ←[1;34mproc←[0m
drwx------ 2 root root 0 Jun 27 05:47 ←[1;34mroot←[0m
drwxr-x--- 2 root root 0 Dec 31 1969 ←[1;34msbin←[0m
lrwxrwxrwx 1 root root 11 Sep 12 11:59 ←[1;36msdcard←[0m -> ←[1;34m/mnt/sdcard←[0m
drwxr-xr-x 12 root root 0 Sep 12 11:59 ←[1;34msys←[0m
drwxr-xr-x 14 root root 4096 Sep 6 23:20 ←[1;34msystem←[0m
drwxr-xr-x 5 root root 4096 Jul 19 22:25 ←[1;34mtombstones←[0m
-rw-r--r-- 1 root root 272 Dec 31 1969 ←[0;0mueventd.goldfish.rc←[0m
-rw-r--r-- 1 root root 8338 Dec 31 1969 ←[0;0mueventd.rc←[0m
lrwxrwxrwx 1 root root 14 Sep 12 11:59 ←[1;36mvendor←[0m -> ←[1;34m/system/vendor←[0m
But from the tablet when I issue the command ls -la / i get the normal listing but in shows in COLOR, so I''m guessing that <-[1;36m in ADB represents a color ([0,0m for white, [1;34m for dark blue, etc), but how do I go to show color listing in ADB shell in my PC ?
Before when TOOLBOX was handing the LS command there was not color in the listing, but now with BUSYBOX handling the LS command I get nice different colors for files/folders/scripts, etc.
Any way I can fix this from the standpoint of the Widows PC MSDOS window with ADB shell listing files with LS in also in color ???
much appreciated, regards.
UPDATE:
I found out that I can list with ADB shell without those strange characters (in other words with NO COLOR) with the following command:
adb shell ls -la --color=never /
but it would be nice not to have to type --color=never every time I want a listing and better find a way to list it with color from PC in MSDOS window.
you can use a utility like ansicon, which allows msdos command windows to interpret the colour codes. You could add this to windows startup if you want, or use some replacement command line utility that can automatically run an app on startup.
flshg said:
you can use a utility like ansicon, which allows msdos command windows to interpret the colour codes. You could add this to windows startup if you want, or use some replacement command line utility that can automatically run an app on startup.
Click to expand...
Click to collapse
thanks a bunch, it worked just great!
Hello,
I can't delete some files on my device (Samsung Galaxy Note 2 LTE [t0lte]]) running CyanogenMod 10.1 using RootExplorer (or similar file manager).
So I tried with adb (in CM10.1, ClockworkMod & TeamWin recovery), but received error messages:
Code:
/data/media/0/DCIM/.thumbnails # rm 1375815201990.jpg
rm: can't remove '1375815201990.jpg': Operation not permitted
/data/media/0/DCIM/.thumbnails # chmod 777 1375815201990.jpg
chmod: 1375815201990.jpg: Operation not permitted
/data/media/0/DCIM/.thumbnails # chown root:root 1375815201990.jpg
chown: 1375815201990.jpg: Operation not permitted
I think there is something wrong with the permissions, here are the directory listings:
Code:
/data/data/com.amazon.venezia.wech/app_resources/configurationTwo/assets/css/amazon-phoenix/compositions # ls -lisah
202883 4 drwx------ 2 u0_a145 u0_a145 4.0K Aug 14 20:03 .
202882 4 drwx------ 3 u0_a145 u0_a145 4.0K Aug 8 03:43 ..
203719 24 ---S-wxr-t 1 u0_a1355 u0_a2315 1.8G Oct 11 2024 amazon-phoenix-xlarge-landscape-xhdpi.css
Code:
/data/lost+found # ls -lisah
10333 4 --wsrwSr-x 1 u22097_a u4253_a5 12.0K Jan 27 1988 #10333
10436 4 -r-------T 1 u22097_a u12935_a 254.5M May 14 1984 #10436
104567 8 ----r-Srwx 1 u37071_a u21823_a 36.0K Mar 5 1951 #104567
104571 36 d-w-rws--T 2 u18849_a u29364_a 36.0K Jan 10 1956 #104571
104687 8 ---S--x-w- 1 u38084_a u38537_a 28.0K Feb 16 1986 #104687
104696 8 --w--wsrwT 1 u8912_a4 u20250_a 36.0K Jun 12 1929 #104696
104832 36 d---r-sr-T 2 u8902_a5 u4062_a1 36.0K Sep 23 1929 #104832
...and_many_more...
Code:
/data/media/0/DCIM/.thumbnails # ls -lisah
243488 156 drwxrwxrwx 2 media_rw media_rw 152.0K Aug 15 11:29 .
97358 4 drwxrwxrwx 3 media_rw media_rw 4.0K Aug 16 08:32 ..
248825 32 -r---ws-wx 1 all_a153 u0_a2320 712.5M Aug 19 1994 1375815201990.jpg
BTW: /data/media/0 is the internal sd-card of my device.
How can I delete theses files?
all files gone, have to rebuild my phone
Stiegi said:
How can I delete theses files?
Click to expand...
Click to collapse
I didn't find a smart way (no "xattr", or "chflags", ... on android available) to clean the files off from my disk, so I rebuild my phone:
copied all files from /data/media/0/ to my linux,
wiped all local partitions (ecxept my external sdcard) in TWRP (but the bad files are still there)
found another menu in TWRP and formated the /data/... (now the unusable files & folders are gone. I think the /data-wipe in TWRP uses "rm -fR *" on /data.)
installed the latest CM10.1 + gapps,
booted the phone,
google restored my apps,
TitaniumBackup restored the appdata,
and finally I copied the files from my linux back to /data/media/0/
So after a day of extreme backup-/restore-/delete-/copy-ing I'm back on the track
I've create a directory /storage/sdcard2 and mounted it as follows:
mkdir sdcard2
chmod 771 /storage/sdcard2
chgrp 1015 /storage/sdcard2
So it has looks like:
drwxrwx--x 3 root sdcard_rw 60 Feb 12 20:17 sdcard2
Now the external storage looks like:
drwxrwx--x 19 root sdcard_rw 32768 Dec 31 1969 DE52-F3E6
So they match exactly, but for some reason while most apps (non-root) can see and view /storage/DE52-F3E6 nothing but root apps can see /storage/sdcard2 (if I su* others can see it in a console but not access it). In Android (CM12) 5.1, this worked fine, in (CM13) 6.0.1 I'm going crazy. I thought it might be namespace separation in Super SU, but that does not appear to be the case it is as if there is another block that only allows root to see non-standard directories (or files) since creating a file in /storage has the exact same issue.
How do I fix this as it makes using 6.0.1 useless as I can not manually mount my secondary partition on the SD Sard and get access to the data on it (except as root).
su - u_10034
127|[email protected]:/storage # su - u0_a334
[email protected]:/storage $ ls -al
drwxr-xr-x 6 root root 140 Feb 12 20:06 .
drwxr-xr-x 28 root root 0 Feb 12 19:59 ..
drwxrwx--x 19 root sdcard_rw 32768 Dec 31 1969 DE52-F3E6
drwx--x--x 5 root sdcard_rw 4096 Dec 31 2014 emulated
drwxrwx--x 3 root sdcard_rw 60 Feb 12 20:17 sdcard2
drwxr-xr-x 2 root root 60 Aug 2 2015 self
[email protected]:/storage $
At a minimum I want to at be able to access the sdcard2 directory same as I can access DE52-F3E6 the permissions match, but the SE (ls -n) setting differ, but I can not find what setting I need to use there to allow the same access as DE52-F3E6 since DE52-F3E6 is a device and sdcard2 is a directory.
Thanks,
ERIC
I'm trying to flash lineageOS on my Moto Z/XT1650 however it aborts with 'E2001: Failed to update vendor image.' and leaves the system in an unbootable state (which i have then to fix by restoring the stock image from backups) After having a closer look the error seems to originate from the updater script when it tries to patch the vendor/oem partition (/dev/block/bootdevice/by-name/oem or /dev/block/sdc9) because the partition is readonly.
Code:
block_image_update("/dev/block/bootdevice/by-name/oem", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
I also failed to mount the partition rw via adb shell.
Code:
~ # mount -w /dev/block/sdc9 /oem
~ # ls -al /oem
drwxr-xr-x 6 root root 4096 Jan 1 1970 .
drwxrwxrwt 31 root root 1040 Jul 26 09:25 ..
drwxr-xr-x 6 root root 4096 Sep 25 2018 app
drwxr-xr-x 6 root root 4096 Sep 25 2018 etc
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 146 Sep 25 2018 oem.prop
drwxr-xr-x 4 root root 4096 Sep 25 2018 priv-app
~ # touch /oem/test
touch: /oem/test: Read-only file system
How do i make the partition rw so that twrp/lineage installer can patch it?
Never mind, i found the solution: Booting directly into twrp causes these issues. Flash the twrp/recovery image and boot into recovery mode instead