its in a pastebin link. anyone help with looking at this? i am lost
http://pastebin.com/YQEuL5MS
ok. THINK it is no writing it to the phone. almost like it does not have r/w permissions. anyone have ideas on this as to why??
psycopanther said:
ok. THINK it is no writing it to the phone. almost like it does not have r/w permissions. anyone have ideas on this as to why??
Click to expand...
Click to collapse
is this a correct mount structure?
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p15 on /data type ext4 (ro,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p17 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
~ # ←[6n
boom. pretty sure i know where phone is screwed up.
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p15 on /data type ext4 (ro,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p17 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p14 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
the /dev/block/mmcblk0p15 is set to RO, so when booting up, the phone cannot write the data from /system (which is where rom is stored and used in factory restore) to /data inorder to boot and save everything i do!
cant figure out how to change it though. does ANYBODY know if this is what my problem is. i really need some guru advice here
sorry, but five posts and no one has a clue? everyone over on the android dev threads aint they lol
THIS THREAD IS DONE WITH. IT SHOULD NOW BE LOCKED OR DELETED.
PLEASE see THIS thread for updates on this issue: http://forum.xda-developers.com/showthread.php?p=30386309#post30386309
HI Guys,
I have a peculiar problem, and I hope someone can help solve this:
My phone is a Galaxy 3 (I5801), and I just installed Kyrillos ROM 10.6 on it. I had previously created a 1GB ext4 partition using CWM in my 8Gb card. From Kyrillos' post, I only have to do this much to enable hybrid data2sd, where all the new apps get installed in the sd-ext (1gb) partition on sd card. It seemed to work fine, I removed unwanted launchhers, made backups using Titanium, and plugged the phone to My Linux Mint system.
I copied data to the sd card (6.x gb partition) (and the 1gb ext4 partition was also auto mounted).
I rebooted the phone, and all the newly installed apps (which went to sd-ext) were not visible anymore. I tried to find them, but they were visible as ghosts in the applications list in settings.
I am guessing that the ext4 partition is not getting mounted.
Why is this happening? any ideas? please help!
EDIT:
Here is the output of the "mount" command from terminal emulator
$ export PATH=/data/local/bin:$PATH
$ mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl6 on /system type ext4 (rw,relatime,commit=600,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl7 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=20,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl8 on /cache type rfs (rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/stl4 on /efs type rfs (rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/stl7 on /cache/download type ext4 (rw,nosuid,nodev,noatime,commit=20,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p2 on /sd-ext type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/vold/179:9 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,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)
UPDATE 2:
The problem occurs only when i restart phone after connecting it to Linux Mint (Which Mounts the EXT4 /sd-ext partition. if connected to windows, no problems occur....
Any Ideas?
I have (almost) the same problem. My data2sd isn't working. link2sd desn't see my partition at all. And if I try to use hybrid data2sd I have to use it with either "g3mod config" or KMApp, but then I have this issue with ghost apps.
My phone is i5800, and if I enable BLN in KMApp (which is only for i5801), the apps stay normal, but I get sleep of death issue with screen.
Hello, I have a P5100. I had some problems with the EFS folder, and I think I made a mess.
Before I saw the mount /efs in recovery mount, now disappeared, and when I try to restore the imei with nav_data.bin does not work.
Could someone help me?
I can still see the folder / efs, but looking at the partitions I only see these:
Code:
./adb shell mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard)
I can recreate it? How?
Once rebuilt, I have an old copy of the EFS folder that contain the files:
Code:
FactoryApp
imei
nv_data.bin
redata.bin
wv.keys
bluetooth
nv.log
nv_data.bin.md5
wifi
Could you tell me the exact steps to take to get back the imei correct?
HELP Thank you.
Hi guys,
I've searched and found quite a few adb and terminal emulator commands to view my phone's partitions, but being completely new to all of this (this project is my second time even really using command prompt) it took me a LOT of trial and error on my own before I posted this and I apologize for the n00biness in advance.
My phone setup is an HTC 10 Perfume running 7.0 Nougat (I flashed my phone with some image which allowed it to be rooted), and using the fdisk command on the phone's terminal emulator yielded this:
rootfs on / type rootfs (ro,seclabel,size=1752604k,nr_inodes=438151)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,multiuser,mask=6,gid=1015)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,multiuser,mask=23,gid=9997)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,multiuser,mask=7,gid=9997)
/dev/block/vold/public:179,65 on /mnt/media_rw/4C55-DB29 type texfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,codepage=437,iocharset=utf8,min_prealloc_size=64k,max_prealloc_size=65532800,writeback_boundary=4M,readahead=4M,fail_safe,discard,hidden=show,errors=continue)
/dev/block/vold/public:179,65 on /mnt/secure/asec type texfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,codepage=437,iocharset=utf8,min_prealloc_size=64k,max_prealloc_size=65532800,writeback_boundary=4M,readahead=4M,fail_safe,discard,hidden=show,errors=continue)
/mnt/media_rw/4C55-DB29 on /mnt/runtime/default/4C55-DB29 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,mask=6,gid=1015)
/mnt/media_rw/4C55-DB29 on /mnt/runtime/read/4C55-DB29 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,mask=18,gid=9997)
/mnt/media_rw/4C55-DB29 on /mnt/runtime/write/4C55-DB29 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,mask=18,gid=9997)
none on /config type configfs (rw,relatime)
/dev/block/bootdevice/by-name/slpi on /firmware/slpi type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/system on /system type ext4 (ro,seclabel,noatime,discard,data=ordered)
/dev/block/bootdevice/by-name/devlog on /devlog type ext4 (rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered)
/dev/block/bootdevice/by-name/fataldevlog on /fataldevlog type ext4 (rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered)
/dev/block/bootdevice/by-name/carrier on /carrier type ext4 (rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered)
/dev/block/bootdevice/by-name/cota on /cota type ext4 (rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered)
/dev/block/bootdevice/by-name/apppreload on /preload type ext4 (rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered)
/dev/block/bootdevice/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered)/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,errors=panic,data=ordered)
/dev/block/bootdevice/by-name/dsp on /dsp type ext4 (rw,seclabel,nosuid,nodev,relatime,errors=panic,data=ordered)
/dev/block/bootdevice/by-name/venus on /firmware/venus type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/rfg_3 on /firmware/wsd type vfat (ro,relatime,uid=3012,gid=3012,fmask=0377,dmask=0277,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/radio on /firmware/radio type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/adsp on /firmware/adsp type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,errors=panic,data=ordered)/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,multiuser,mask=7,gid=9997)
/mnt/media_rw/4C55-DB29 on /storage/4C55-DB29 type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,mask=18,gid=9997)
tmpfs on /storage/self type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
Click to expand...
Click to collapse
...Could someone please tell me which one is my userdata partition, or if that's even included in this list? BTW my endgame is to image the partition and open it in some forensics software so I can attempt to recover some deleted data (I believe I actually already copied over the android's entire file system, but none of my forensics software can open that dd file. That's a whole other interesting topic, but I'm not sure if it's too relevant to this forum as much as the forensics ones lol.. maybe I'll make another thread inquiring whether the command I used to do so is valid or not for my goal).