Insufficient storage available error - Galaxy S III Q&A, Help & Troubleshooting

This message comes every time I try to install something from the market,
"insufficient storage available "
I try to wipe the cache and the dalvik too but don't seems to work any ideas to fix this?
I have like 7gb of free internal memory and 2gb of free sd card memory so that's not the problem
Galaxy s3
Kernel Siyah 1.5 rc 1
Stock rom I93000XXLFB
Build number IMM76D. I93000XXBLG3
International versión
Sent from my GT-I9300 using xda premium

Are you using tb with lucky Patcher?
《tapatalked from galaxy s3》

John Death said:
This message comes every time I try to install something from the market,
"insufficient storage available "
I try to wipe the cache and the dalvik too but don't seems to work any ideas to fix this?
I have like 7gb of free internal memory and 2gb of free sd card memory so that's not the problem
Galaxy s3
Kernel Siyah 1.5 rc 1
Stock rom I93000XXLFB
Build number IMM76D. I93000XXBLG3
International versión
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
try clearing data and cache from Google Framework services and Google play from application manager..delete your google account..reboot and retry..

No I don't even have lucky patcher just the default tb
Sent from my GT-I9300 using xda premium

zoot1 said:
try clearing data and cache from Google Framework services and Google play from application manager..delete your google account..reboot and retry..
Click to expand...
Click to collapse
Didn't work, still the same error when I try to download even a small app
Sent from my GT-I9300 using xda premium

John Death said:
Didn't work, still the same error when I try to download even a small app
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
try one thing..connect your device to adb..enable usb debugging...type
adb shell
mount
paste what you see..

zoot1 said:
try one thing..connect your device to adb..enable usb debugging...type
adb shell
mount
paste what you see..
Click to expand...
Click to collapse
C:\android-sdk-windows\platform-tools> adb shell
~ # mount
mount
rootfs on / type rootfs (ro,noatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,jour
nal_async_commit,data=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,jour
nal_async_commit,data=ordered)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journa
l_async_commit,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime)
/dev/fuse on /mnt/sdcard type fuse (rw,nosuid,nodev,noatime,user_id=1023,group_i
d=1023,default_permissions,allow_other)
/dev/block/vold/179:49 on /mnt/extSdCard type vfat (rw,dirsync,nosuid,nodev,noex
ec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,c
odepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

John Death said:
C:\android-sdk-windows\platform-tools> adb shell
~ # mount
mount
rootfs on / type rootfs (ro,noatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,jour
nal_async_commit,data=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,jour
nal_async_commit,data=ordered)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,journa
l_async_commit,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime)
/dev/fuse on /mnt/sdcard type fuse (rw,nosuid,nodev,noatime,user_id=1023,group_i
d=1023,default_permissions,allow_other)
/dev/block/vold/179:49 on /mnt/extSdCard type vfat (rw,dirsync,nosuid,nodev,noex
ec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,c
odepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Click to expand...
Click to collapse
Thank's for all the support, i fixed by installing Lucky Patcher and going to troubleshooting> remove fixes and backups.
I guess my brother was playing with apps in the phone install that thing make some changes and the just erase the program... anyway, thank's for the support!

Your mount pints are perfectly okay and the correct permissions are set..i dont know what i can tell you next...
As a last resort, in my opinion, if you dont find any other option download the correct firmware for your region from sammobile.com/checkfus and flash it via odin...
please backup your data before that as you may need to clear data after the flash..

John Death said:
Thank's for all the support, i fixed by installing Lucky Patcher and going to troubleshooting> remove fixes and backups.
I guess my brother was playing with apps in the phone install that thing make some changes and the just erase the program... anyway, thank's for the support!
Click to expand...
Click to collapse
Thanks i had the same problem and it is fixed now using your method.

Apps2SD
I get this message ramdomly when I try to install apps from PlayStore. Found out that because I've set to use my SD card in app2SD app.

Im also getting "out of space" message when trying to install something And im not able to install even Lucky Patcher.
Having some 400MB of free RAM and free phone memory is bit under 10 gigs.My galaxy s 3 is rooted also.Have been searching now for some 24h to fix that problem but nothing helps.

Guys , look in data/app or system/app for a .odex file. delete it,reboot and see if is all ok now.

enigmatyq said:
Guys , look in data/app or system/app for a .odex file. delete it,reboot and see if is all ok now.
Click to expand...
Click to collapse
Sry buddy but i cant find .odex file there
Edited!
Solved my "out of space" issue :laugh: Its located here:
http://forum.xda-developers.com/showthread.php?t=1711552&page=3

Related

Restore efs with root explorer read only error

I instaled root explorer and am trying to replace efs files from backup but i have a problem as can not mount ir as RW it is RO
Is there any way around that?
it looks like only efs folder have this problem
Is your phone rooted?
yes i just checked again if i rooted it and i did
$ cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp: can't create '/efs/nv_data.bin': File exists
$ rm /efs/nv_data.bin
rm /efs/nv_data.bin
rm: remove '/efs/nv_data.bin'? y
y
rm: can't remove '/efs/nv_data.bin': Read-only file system
any help???
i can not get efs to be rw
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/usb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /app-cache type tmpfs (rw,relatime,size=7168k)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data
=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (ro,relatime,barrier=1,data=ordered)
nil on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data
=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/dev/block/vold/179:11 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
#
Did you try to remount /efs in rw (instead of ro) ?
Yes and it remounts it instead of ext4 in ext3 i can delete and edit what i want no permission errors but once i leave hex editor it gets back to ro and all files I deletes reaiires and files i have changed show as unchanged and it gets RO. I feel that i am missinf some linux command to made this changes succesfull.
same problem my efs is read only and i would like to restore my efs, please help
mahatma said:
I instaled root explorer and am trying to replace efs files from backup but i have a problem as can not mount ir as RW it is RO
Is there any way around that?
it looks like only efs folder have this problem
Click to expand...
Click to collapse
Didnt try the app but have a look http://forum.xda-developers.com/showpost.php?p=16512129&postcount=73
Sent from my GT-I9100 using Tapatalk

Online Android Backup **DO BACKUP WHILE YOUR PHONE STILL ON**

ANNOUNCEMENT:
Official version that support most (including our) device has been released. See HERE
Hi All.
Here are the modified version of Online Android Backup from ORIGINAL THREAD. I've changed some codes to make it works for our HTC Legend.
How To Install:
Through CWM
1. Download from attachment onandroidv3.7_cwm.zip
2. Copy it to your sdcard
3. Reboot into recovery
4. Flash the file
Manual
1. Extract onandroid.zip attached and use adb/root explorer to push/copy the file onandroid to your /system/bin
2. change permission to rwxr-xr-x
How To use:
From PC:
1. Open terminal/command prompt
2. type adb shell
- if using CM9, type su to gain root access after step 2.
3. type onandroid
From your phone:
1. open terminal emulator, type su
2. type onandroid
UPDATE:
If you use ogo2's ROM HERE, please download SENSE_fix_tool.zip from attachment and flash it. Mediafire link are HERE
Changes:
12.06.2012: Initial modification from original version
13.06.2012: Power checking corrected
14.06.2012: Added CWM flashable file
20.06.2012: Update v3.7 from original developer. confirm to work in cm9
Changelogs from original developer:
:: Latest onandroid fixes from v3.7
:: Made "dd" not spit results.
:: Added partition detection for boot and recovery partitions.
02.07.2012: Fix for sense ROM
screenshots and file are attached.
Credits:
ameer1234567890 Original Developer
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
vriz27 said:
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
Click to expand...
Click to collapse
Yes, download the file from attachment (onandroid_CWM.zip)
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
smithchipz said:
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
Click to expand...
Click to collapse
Thanks. I just do some simple modification to the original version, praise to ameer1234567890 for the great tools.
Restoring is working fine with me but make sure you check the backup folder after onandroid is finish running and check if all required files is there especially if you do something else during the backup process.
Fix for sense ROM attached in 1st post.
feed3 said:
Fix for sense ROM attached in 1st post.
Click to expand...
Click to collapse
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
alligator_asl said:
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
Click to expand...
Click to collapse
That is due to an issue in XDA (one of the servers crashed). Should be fixed in a couple of days!
Sense fix
Sense fix tool uploaded to mediafire. Link in the post #1.
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Click to expand...
Click to collapse
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
ameer1234567890 said:
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
Click to expand...
Click to collapse
Here is it:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /mnt/asec/sd ext3 rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/nadsoft.physicscheatsheetsfree-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/jwtc.android.chess-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
How did you partition your sdcard? Which app2sd or link2sd version do you use?
Also, post output from below command!
Code:
echo $SD_EXT_DIREECTORY
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
alligator_asl said:
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
Click to expand...
Click to collapse
Thank you for the information. I am working on a fix.
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
Click to expand...
Click to collapse
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
feed3 said:
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
Click to expand...
Click to collapse
I have fixed this in the next version. Shall be releasing soon.
ameer1234567890 said:
I have fixed this in the next version. Shall be releasing soon.
Click to expand...
Click to collapse
Thanks ameer..

[Q] Getting message "Error insufficient storage available" in Play Store

I get this message everytime I try to install anything from Play Store, so any ideas?
Connect your phone through ADB to your computer, type
"adb shell" and then "mount"
Alternatively if you have terminal emulator installed, type "mount" and then Right-button->Send to email
You could maybe install it by removing an app first
Copy-paste the output here
I used Terminal Emulator but Play Store still refuses to work:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
Sry, I should not have typed and talked: wrong command.
Please try again with:
df
If you're rooted and have busybox, please use
busybox df -i
busybox df
The -i will show inode (file/directory) count.
Got this:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ busybox df -i
Filesystem Inodes Used Available Use% Mounted on
tmpfs 99814 339 99475 0% /dev
tmpfs 99814 1 99813 0% /mnt/asec
tmpfs 99814 1 99813 0% /mnt/obb
/dev/block/mmcblk0p9 98304 2410 95894 2% /system
/dev/block/mmcblk0p12
755904 9436 746468 1% /data
/dev/block/mmcblk0p8 65536 15 65521 0% /cache
/dev/block/mmcblk0p3 1280 47 1233 4% /efs
/dev/fuse 755904 9436 746468 1% /mnt/sdcard
/dev/block/vold/179:17
0 0 0 0% /mnt/extSdCard
[email protected]:/ $
Hmm your filesystems look ok, they are barely being used.
Try force-close and deleting the app-data of the market (Google Play). You now should have to accept the ToS again.
Can you edit/move/create files on the internal and external SD card as expected?
Tried that and uninstalled the updates but still not working. The only thing I can think that caused it was using GL to SD to try to move some Gameloft games to external but it refused to work.
Michael_P said:
Tried that and uninstalled the updates but still not working. The only thing I can think that caused it was using GL to SD to try to move some Gameloft games to external but it refused to work.
Click to expand...
Click to collapse
How much free memory do you have?
Sent from my GT-I9300 using xda premium
4.9gb
Here ya go
Ran into this problem before, but I forgot the solution, so I was scouring the inter webs looking for a solution when I came upon this thread. Later on, I remembered the solution, and I thought of this thread again, so here's the answer (if you're rooted, that is):
1. Go to settings, applications, all, and find the play store
2. Wipe cache, then wipe data
3. Reboot to recovery
4. Wipe cache and dalvik cache
5. Reboot
6. Enjoy!
Hope I helped!
------------
If I've somehow helped in any way, gimme some thanks!
Easy way, if rooted, install lucky patcher (search google, then it will remove unused codec)
Sent from my GT-I9300 using xda app-developers app
ascariz said:
Easy way, if rooted, install lucky patcher (search google, then it will remove unused codec)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Install lucky patcher then followed by what?? What do you mean by remove unused codec?
ascariz said:
Easy way, if rooted, install lucky patcher (search google, then it will remove unused codec)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks it worked perfectly!
Bloodlust said:
Install lucky patcher then followed by what?? What do you mean by remove unused codec?
Click to expand...
Click to collapse
It does it automatically as soon as lucky patcher opens.
(Hopefully) better solution
Sorry to dig up an old thread, came up as the first link on Google. The problem seems to stem from corruption caused by glitches or buggy ROMs. Had this issue with early pre-release build of Cyanogen JB for Epic. Delete the odex file associated with the app (showed up in /data/app on my phone, not in the dalvik cache like it should, hence the glitch). If there isn't an odex file associated with the app, well, that's not it, and you might have to wipe after all. Why Android doesn't always clear the odex file, though, I have no idea. Mysteries of the universe and all that.
Solved my problem
ascariz said:
Easy way, if rooted, install lucky patcher (search google, then it will remove unused codec)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
This post solved my that error for me.
Just found this thread on Google and wanted to clear this up-
ascariz said:
Easy way, if rooted, install lucky patcher (search google, then it will remove unused codec)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Bloodlust said:
Install lucky patcher then followed by what?? What do you mean by remove unused codec?
Click to expand...
Click to collapse
Vertron said:
Thanks it worked perfectly!
It does it automatically as soon as lucky patcher opens.
Click to expand...
Click to collapse
He meant to say "it will remove unused ODEX" which is exactly what Lucky Patcher did upon simply opening it up, not having to redownload it again. Just open lucky patcher and it will remove unused ODEX automatically.
I also have this problem.
When i move application, dalvik-cache and cache, it works great.
But after moving data it says insufficient storage available when installing from play store or an third party app.
Please help.
I have 150 mb internel memory, out of which 140 is data, i want to install more apps.

HOSTs file nightmare! Please help

Can anyone help with this...
The phone is called the n7103, It's a chinese phone and the specs can be found here: https://my.dx.com/MyOrders/OrderDetail/130421001070495638
Root: Yes
Version: 4.1
Carrier: Three (UK)
My hosts files are wrong, so I can't connect to the play store and use some apps, my hosts file currently read:
127.0.0.1 localhost
#74.125.93.113 android.clients.google.com
#74.125.93.113 mtalk.google.com
Click to expand...
Click to collapse
I presume this is correct, if not please do correct me.
Now I want to use ADB to send the to the phone, however I can't for the life of me make the system read/write, The reason being I dont know what to mount, so I found the following instructions:
Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts)
Click to expand...
Click to collapse
I have looked in the /proc/mounts file and get the following read out:
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected]_ro /system/secro ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:96 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:6 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:6 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
So basically I get stuck at this part as I don't know what to type:
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 .........
I have looked for other methods including using totalcommander with root to edit hosts file but to no avail.
I can't push the file as the destination is not read write. I have also tried using terminal and chmoding the system folder as 777 but no joy.
There is also an app called "HOSTS EDITOR" however it wont allow me to insert the "#" character.
I am sorry for the very long post, I'd appreciate any help!
Thanks :good:
mount -o remount, rw /system
Click to expand...
Click to collapse
This returns no errors however when i then try the follwing command it fails.
[email protected]:/ # adb push hosts /etc/hosts
adb push hosts /etc/hosts
error: device not found
Click to expand...
Click to collapse
This phone was gently placed in a bin.
Sent from my GT-I9505 using XDA Premium 4 mobile app
adb is a program in your PC, not in Android itself, so this command:
philipkroberts said:
adb push hosts /etc/hosts
Click to expand...
Click to collapse
should be typed outside of the Android shell (type exit after you remount system, then try that command again).

[Q]can't paste files on some partition like /data , /system and /ext_sdcard

this is weird , i try to copy some files from my internal SDcard to the external Sdcard by using Root Explorer
it keep says "the paste operation failed. it may be that there was not enough free space on the target file system "
but serious , i have 20 GB left in my external Sdcard ... and the file was only 8 MB ..
weird thing is that it happens sometime and sometimes it doesn't happen.
sometimes on /data partition , sometimes /system , like i try to replace boot animation or such .
i tried few ROMs all happens on me as well.
i tried to creat a empty text files .txt , and write something in it and it can be saved. so it just get me confused what's going on :crying:
Using any scripts?
Permissions correct?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
you should remove some apps from system folder because there is a limited space for apps in this folder
you can check it :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alfares43 said:
you should remove some apps from system folder because there is a limited space for apps in this folder
Click to expand...
Click to collapse
...and /data? /extSdCard?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
...and /data? /extSdCard?
Click to expand...
Click to collapse
I faced the same problem before in system folder
and solved it by removing some apps
i have no idea what to do for the other folders .. :silly:
Do you get the same issue if you try doing it with terminal emulator or adb? I wonder if it is some setting on root explorer that maybe limits file size or something. If you use another file explorer program do you have the same problem?
rootSU said:
Using any scripts?
Permissions correct?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Sdcard doesn't have permissions ...
alfares43 said:
you should remove some apps from system folder because there is a limited space for apps in this folder
you can check it :
Click to expand...
Click to collapse
1.5 GB left in system and 5 GB in data.. so no really the case ...
wangdaning said:
Do you get the same issue if you try doing it with terminal emulator or adb? I wonder if it is some setting on root explorer that maybe limits file size or something. If you use another file explorer program do you have the same problem?
Click to expand...
Click to collapse
I didn't try ADB, but when I failed to move around the internal and external sdcard, I can manually copy it into PC and then paste it back in...
In other words, I can access (delete, paste or such) from my PC but can't do it with Root Explorer
Sent from my GT-I9300 using xda premium
qtwrk said:
Sdcard doesn't have permissions ...
Click to expand...
Click to collapse
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
rootSU said:
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
Click to expand...
Click to collapse
This was why I say no permission...
I more think about media scan? But seems highly unlikely.
If it is not mounted or permission error ... then why I was able to create empty text files and write save it? this operation does write on it, doesn't it?
Sent from my GT-I9300 using xda premium
Try other root explorers then....
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
Click to expand...
Click to collapse
Code:
[email protected]:/ $ mount
rootfs on / type rootfs (ro,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime)
proc on /proc type proc (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
sysfs on /sys type sysfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=600)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpu)
tmpfs on /storage type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
none on /acct type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=775,gid=1000)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (ro,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,commit=100,barrier=1,data=ordered,noauto_da_alloc,discard)
tmpfs on /system/lib/modules type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,barrier=1,journal_async_commit,data=writeback,noauto_da_alloc,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=777,gid=1000)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ $
I can't read this... m a little help please?
Sent from my GT-I9300 using xda premium
qtwrk said:
Code:
[email protected]:/ $ mount
rootfs on / type rootfs (ro,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime)
proc on /proc type proc (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
sysfs on /sys type sysfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=600)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpu)
tmpfs on /storage type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
none on /acct type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=775,gid=1000)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (ro,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,commit=100,barrier=1,data=ordered,noauto_da_alloc,discard)
tmpfs on /system/lib/modules type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,barrier=1,journal_async_commit,data=writeback,noauto_da_alloc,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=777,gid=1000)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ $
I can't read this... m a little help please?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
This is the line you want:
Code:
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Which is normal for an AOSP ROM.
A touchwiz ROM would look like....
Code:
vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Anyway, you ruled something out there (if you ran this when you got the error)
rootSU said:
This is the line you want:
Code:
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Which is normal for an AOSP ROM.
A touchwiz ROM would look like....
Code:
vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Anyway, you ruled something out there (if you ran this when you got the error)
Click to expand...
Click to collapse
Yeah... last time it shows error at beginning, and after I reboot it once and now it says error after the paste is completed, with refresh I can see the file in place and md5 checks identical.
That was the line when I got error...
I'm gonna try other files manager...
Sent from my GT-I9300 using xda premium
qtwrk said:
Yeah... last time it shows error at beginning, and after I reboot it once and now it says error after the paste is completed, with refresh I can see the file in place and md5 checks identical.
That was the line when I got error...
I'm gonna try other files manager...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
es file explorer> menu> root explorer on> grant.... then again menu> click root explorer> mount r/w and enable write permissions and you can copy/cut/paste data anywhere. this is what i always do.
:good:

Categories

Resources