Hello everyone,
I am using CM10.1 on my Samsung Galaxy S i9000. I have a strange problem since I swithed to CM10 about a month ago. If I boot to revocery I can reach, read and write to all partitions including sdcard and internalsd (and data, system etc.) However, If I boot to normal system, the boot screen SGS/Cyanogen mod image lasts on the screen for too long and then system stats.
When system starts, I end up with external sd mounted but not internal sd. If I connect my phone to a computer at this time, computer only sees external sd card, and says "insert disk" when I click internal sd from Explorer. However, when I removed by sdcard from computer, my phone says "preparing sd card" and than mounts internal sd. Now, external sd is unmounted magically. This time I can use internal sd (read, write everything) but external sd card is not mounted. If I go to System -> Storage to mount external sd card, "Insert sdcard to mount" appears, and it can't be mountable.
I also ran mount command before connecting to PC (when external sd was mounted) and after disconnected from PC (this time internal sd was mounted) These are the outputs:
before connecting to pc
Code:
[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/secure tmpfs rw,relatime,mode=700 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/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.chartcross.gpstestplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/kr.aboy.tools-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/dk.logisoft.aircontrolfull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/radiotime.player-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.qo.android.am3-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:25 /storage/sdcard1 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
last lines differ
after connecting to pc
Code:
[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/secure tmpfs rw,relatime,mode=700 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/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.chartcross.gpstestplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/kr.aboy.tools-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/dk.logisoft.aircontrolfull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/radiotime.player-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.qo.android.am3-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:1 /storage/sdcard0 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 /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
How can I fix this? Btw, I can't report this to CM10.1 page because my post count is too low.
If I could'nt write and read to internalsdcard properly on recovery or after disconnecting to pc I'd thought that it was broken on hardware level but this seems like a software issue to me? What do you think?
By using which shell command, I can try to manually mount my internal sdcard, after the phone booted?
If I run these commands manually after turning on my phone, I can mount my internal sd card to /storage/sdcard successfully. However, I can't mount sdcard to multiple locations (such as mnt/sdcard and /sdcard) so programs don't run properly.
Code:
mount -t vfat /dev/block/mmcblk0p1 /storage/sdcard0;
setprop EXTERNAL_STORAGE_STATE mounted;
am broadcast -a android.intent.action.MEDIA_MOUNTED --ez read-only false -d file:///storage/sdcard0;
However if I try to mount vold/179:0 i get the following error:
Code:
[email protected]:/ # mount -t vfat /dev/block/vold/179\:0 /storage/sdcard0;
mount: Device or resource busy
Any thoughts?
What is vold and what is the difference between mounting
/dev/block/vold/179:0 and /dev/block/mmcblk0p1 ?
If both points to internal storage, why can't I mount one, but do mount another?
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
gergefil said:
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
Click to expand...
Click to collapse
Probably, problem is "clockworkmod" folder into external SD card!
When you make backup, you must choise "tar format" instead "dup format"!!
almost there
Man!
That´s exactly my case!! SGS Vibrant T959, with CyanogenMod v10.1.2. I noticed that I was not accessing the internal sdcard. I tried to plug in the computer and enable the usb mass storage but it wouldn´t mount the internal sdcard. Then I rebooted in recovery mode (CWM recovery) and went to mount & storage -> mount sdcard. Rebooted and nothing. Went back to CWM recovery, mounted sdcard, and to browser it I went to 'install zip' just to see. I was able to see my old files.
Then I googled it and found this!
Thank you very much for your hint!
Funny thing is, this happened just after I installed this version (10.1.2). I was using v10.0 and it was just all fine (with 32 Gb external sdcard).
1) I removed it, and boot and there was my internal sdcard with all my files and backups!! ooohoooo
2) plugged my 32 gb sdcard back and it mounted .
3) reboot
4) and my internal SDcard was not mounted again .
So for now, everytime I boot I have to remove my 32gb external sdcard first, and plug it again after boot is finished.
Does anyone know how to def fix it ?!
Thanks!
gergefil said:
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
Click to expand...
Click to collapse
portisheadbr said:
Does anyone know how to def fix it ?! Thanks!
Click to expand...
Click to collapse
just a thought, Android might have issues when the SD card is not formatted using Android. Its advisable to format Sd cards in a PC and after that again in your Android Phone.
Not sure , if this would solve your problem, but worth a try, if its not too difficult to do.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Related
Can someone please provide the output of the "mount" command from a Stock Captivate on Froyo (no lagfix)?
* Connect Captivate via USB
* open up a terminal window
* adb shell
* mount
* copy/paste the entire results (or place in a text file and attach to your response)
Thank you in advance!
-h8
EDIT.....sorry, i just realized this said STOCK froyo....lol. this is andromeda3. derp
Code:
/ $ mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 ro,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 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/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/ $
bump.............
when i go to the shell of my devices, i put mount; and show me this:
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 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/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
what is mi internal and external memory?
thank you for you answers!!!
damn thats confusing lol
what exactly are you looking for ?? What do you want to know about your internal / external memory
im a little confused
Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O
i have the two memorys bricked, internal and external, and when i run the command try to find /dev/block/mmcblk0 to execute the parted /dev/block/mmcblk0 , no exist...
i find the external sd in /dev/block/vold/179:9, but i could find the internal memory! to fixit
blubxd said:
Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O
Click to expand...
Click to collapse
okey the external is /dev/block/vold/179:9
but the internal?!
Can you help mw please??? I send this mesg from my i9000 but i cant use the sd internal and external. Any solution to this?
So I tried to disable Voodoo lagfix (from Voodoo app) and now I'm stuck in the boot screen. Somehow disabling lagfix in CWM isn't working either. I accidentally had my phone corded up to my PC and had internal memory propably mounted while I booted the phone and it tried to convert the filesystem. Not sure if mounting caused the problem.
Being in this situation, is it safe to flash stock rom with .PIT file in Odin while having lagfix enabled? What (I think) I'm trying to ask is does re-partition convert my filesystem back to RFS? If it doesn't work that way, what should I try next? Already backed up all necessary data and ready to wipe. I'm currently on Darky's 10.1 RE and thought about moving on to newer roms, first through stock rom.
I have limited experience in flashing roms. I've read numerous threads and seen one case in which flashing with .PIT file in Odin helped but I wish not to hesitate with this.
Thanks for reading.
EDIT: Here's my /proc/mounts:
Code:
adb shell cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /datadata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
Everytime I plug it to charger, missus Voodoo robot says "convert /data partition".
EDIT 2: Flashed with .PIT + repartition in Odin and the system boots great! It all worked out!
Whenever I try and move an app to the SD card from Manage Applications it says not enough storage space, even though it has plenty of space. Is read/write being disabled in 5.0.1. doing that? Seems likely, just since it's not saying access denied etc figured I'd check if I wasn't hitting some other issue.
Xeddicus said:
Whenever I try and move an app to the SD card from Manage Applications it says not enough storage space
Click to expand...
Click to collapse
if you have a spare SD card i'd copy all the data to Your computer and
try a different SD card
if this does not work you have a bad tablet and need to return it
Ricci
on 5.0.0 not all apps move to sd for me. I dont understand how the 5.0.1 update changes sd cards but it is aparently meant to stop apps writing to the sd card
i can only move apps to SD if its formated vFat (Fat32). (same for anything applied by the Android 5 SD-permission system)
it doesn´t seem to work on exFat, ext3, ext4
DoubleDeepDroid said:
i can only move apps to SD if its formated vFat (Fat32). (same for anything applied by the Android 5 SD-permission system)
it doesn´t seem to work on exFat, ext3, ext4
Click to expand...
Click to collapse
That's weird, how do you know the format of the card once it's inserted into the device? Or do you format fat32 before installing?
ldeveraux said:
That's weird, how do you know the format of the card once it's inserted into the device? Or do you format fat32 before installing?
Click to expand...
Click to collapse
you can check the format with me.kuder.diskinfo app (cannot post link as a new user) for instance.
i format the cards on my workstation.
the Fire (5.0.1) formats cards as exFat as far as i remember,
so you cannot select them in the android 5 write permission choser.
just wondering if anyone has figured out these issues,i want to mount my sdcard as rw ext4 preferably to bypass the filesize limitations of fat filesystem. I have reformatted to ext4 and it says "Unformatted SD Card". but i pushed cancel, and entered...
Code:
[email protected]:/ # mount -rw -t ext4 dev/block/mmcblk1p1 storage/sdcard1/
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=755,uid=1000,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,discard,nodelalloc,errors=panic,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
dev/block/mmcblk1p1 /storage/sdcard1 ext4 rw,seclabel,relatime,data=ordered 0 0
[email protected]:/ # ls storage/sdcard1/
Android
DCIM
LOST.DIR
lost+found
my B&N downloads
(these are my backed up files)
i know i didnt get all the places that the extsdcard is actually mounted to, my apps that are installed on the sdcard wont work!! of course its all the ones i want to work with. And i can still see the files in my file browser.
Hi,
i got this mobile with bricked OS, all what i know is that he stop with working after regular update (it`s not rooted)
Problem is that he turn on with LG logo and that`s all, freeze there...
After couple reboot in some cases he got screen upgrading software and that`s all again..
I successful get recovery console but have only reboot, apply sd card update, wipe data and cache partition.
Also i can access to him via adb shell, but almost all options are permission denied... and that is why i cannot put new ROM in /sdcard folder
Mount looks like this:
Code:
rootfs / rootfs rw 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
/tmp /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk0p1 /system ext2 rw,relatime 0 0
/dev/block/mmcblk0p2 /cache ext3 rw,nodev,noatime,nodiratime,data=ordered 0 0
i tried many options without luck...
Can i get some help?
tnx.