[Q] is this any help? - Flipside General

# cat mtd
dev: size erasesize name
mtd0: 00180000 00020000 "pds"
mtd1: 00060000 00020000 "cid"
mtd2: 000a0000 00020000 "logo"
mtd3: 00060000 00020000 "misc"
mtd4: 00380000 00020000 "boot"
mtd5: 00480000 00020000 "recovery"
mtd6: 008e0000 00020000 "cdrom"
mtd7: 0b860000 00020000 "system"
mtd8: 084c0000 00020000 "cache"
mtd9: 0a120000 00020000 "userdata"
mtd10: 00200000 00020000 "kpanic"
# cat bootinfo
POWERUPREASON : 0x00004000
MBM_VERSION : 0x0000912b
MBM_LOADER_VERSION : 0x0000911a
FLAT_DEV_TREE_ADDRESS : 0xffffffff
BATTERY_STATUS_AT_BOOT : 0x0001
CID_RECOVER_BOOT : 0x00
# cat mounts
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock7 /system/lw yaffs2 ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

# cat cmdline
console=/dev/null rw init=/init ip=off brdrev=P0B androidboot.bootloader=0x0000 mtdparts=omap2-nand.0:1536k @ 2176k(pds),384k @ 4480k(cid),640k @ 6784k(logo),384k(misc),3584k(boot)ro,4608k. @ 15232k(recovery),9088k(cdrom),188800k @ 29312k(system),135936k @ 218496k(cache),164992k(userdata),2m @ 521728k(kpanic) androidboot.mode=reboot mem=498M @ 0x80C00000

Related

[REQUEST] Internal NAND partition setup

Can someone who has performed a temp root post the results of a "mount" and "busybox df -h"? I'd like to see how the internal NAND is partitioned. Thanks!
silow said:
Can someone who has performed a temp root post the results of a "mount" and "busybox df -h"? I'd like to see how the internal NAND is partitioned. Thanks!
Click to expand...
Click to collapse
I posted this in the rooting thread, but here it is again...
Code:
$ su
su
# 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
/dev/block/mmcblk0p26 /system ext3 ro,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=o
rdered 0 0
/dev/block/mmcblk0p28 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=
ordered 0 0
/dev/block/mmcblk0p31 /devlog ext3 rw,nosuid,nodev,relatime,errors=continue,data
=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=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.qualcomm.qx.neocore-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/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/loop9 /system/bin ext2 rw,relatime,errors=continue 0 0
#
Code:
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 186.6M 0 186.6M 0% /dev
/dev/block/mmcblk0p26
391.4M 331.4M 59.9M 85% /system
/dev/block/mmcblk0p27
431.7M 259.3M 172.4M 60% /data
/dev/block/mmcblk0p28
142.2M 18.1M 124.1M 13% /cache
/dev/block/mmcblk0p31
19.9M 4.0M 15.8M 20% /devlog
tmpfs 186.6M 0 186.6M 0% /mnt/asec
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/vold/179:33
7.1G 5.7G 1.4G 80% /mnt/sdcard
/dev/block/vold/179:33
7.1G 5.7G 1.4G 80% /mnt/secure/asec
/dev/block/dm-0 7.1M 5.4M 1.7M 76% /mnt/asec/com.qualcomm.q
x.neocore-1
/dev/block/dm-1 16.2M 14.1M 2.1M 87% /mnt/asec/com.rovio.angr
ybirds-1
/dev/loop9 14.5M 10.2M 3.5M 74% /system/bin
#

[Q] LG G2 D802. Spot the mount list error?

Can anyone post their mount list?
adb shell
mount
here's mine, and I cannot find the error.
I just want to see the difference.
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
debugfs /sys/kernel/debug debugfs 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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Can anyone spot the error?
I assume I mounted something wrong here, so I have only 16GB of storage instead of 32GB.

[Q] LG Optimus L3 E400 ROM Troubleshooting

I am rooted (finally) and am trying to flash custom recovery and then ROM to my phone. Whenever I reboot after flashing, my phone starts the reboot process, but never gets past the LG screen (it is not bricked as I can take battery out and reboot it normally after the attempts). It will never actually fully reboot and make the change.
mount | grep system gives me this:
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
and then cat /proc/mounts gives me this:
rootfs / rootfs ro,noatime 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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /drm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p22 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:20 /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
/dev/block/vold/179:20 /mnt/secure/asec 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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/imoblife.toolbox.full-1 vfat ro,dirsync,nosuid,nodev,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/com.s0up.goomanager-1 vfat ro,dirsync,nosuid,nodev,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/com.grindrapp.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.koushikdutta.rommanager-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-4 /mnt/asec/cm.aptoide.pt-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-5 /mnt/asec/de.mkrtchyan.recoverytools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-6 /mnt/asec/com.siriusapplications.quickboot-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-7 /mnt/asec/com.pandora.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-8 /mnt/asec/com.cgollner.flashify-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-9 /mnt/asec/com.jrummy.root.browserfree-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
#
anyone have any insight? is it just that the root filesystem is read only? the help would be greatly appreciated!
wmt9905 said:
I am rooted (finally) and am trying to flash custom recovery and then ROM to my phone. Whenever I reboot after flashing, my phone starts the reboot process, but never gets past the LG screen (it is not bricked as I can take battery out and reboot it normally after the attempts). It will never actually fully reboot and make the change.
mount | grep system gives me this:
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
and then cat /proc/mounts gives me this:
rootfs / rootfs ro,noatime 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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /drm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p22 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:20 /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
/dev/block/vold/179:20 /mnt/secure/asec 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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/imoblife.toolbox.full-1 vfat ro,dirsync,nosuid,nodev,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/com.s0up.goomanager-1 vfat ro,dirsync,nosuid,nodev,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/com.grindrapp.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.koushikdutta.rommanager-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-4 /mnt/asec/cm.aptoide.pt-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-5 /mnt/asec/de.mkrtchyan.recoverytools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-6 /mnt/asec/com.siriusapplications.quickboot-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-7 /mnt/asec/com.pandora.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-8 /mnt/asec/com.cgollner.flashify-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-9 /mnt/asec/com.jrummy.root.browserfree-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
#
anyone have any insight? is it just that the root filesystem is read only? the help would be greatly appreciated!
Click to expand...
Click to collapse
I didn't read your whole post...but i think i can help u...just do kdg first....it will flash firmware to ur l3..so that u can use ur phone again..then root it and then install rom manager from playstore,there u will find an option of flashing recovery to l3...its the most safest method...any problem,pm me:thumbup:
Sent from my LG-E400 using Tapatalk 2
aroop mishra said:
I didn't read your whole post...but i think i can help u...just do kdg first....it will flash firmware to ur l3..so that u can use ur phone again..then root it and then install rom manager from playstore,there u will find an option of flashing recovery to l3...its the most safest method...any problem,pm me:thumbup:
Sent from my LG-E400 using Tapatalk 2
Click to expand...
Click to collapse
I was never not able to use my phone. I've tried ROM Manager to flash. The flashing isn't the problem. It's getting my to hold on to it because it never fully boots after flashing.

Das restore internal storage's symlinks

Hey,
I messed up something when moving from Devil's recovery to TWRP. I had a secondrom installed and backed up my internal storage for safety reasons and restored it after deleting the .secondrom directory.
Now I can access all my files on sdcard and write to it, but when it comes to downloads via Google Chrome, Chrome toasts "no SD card". ES Download Manager gives me "failed to download [...]".
Is there any way to solve this problem? I attached the output of mount in case you need this. I'm on march 10th nightly using devil's kernel on a Note II.
Code:
rootfs / rootfs ro,relatime 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/fs/cgroup/memory cgroup rw,relatime,memory 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p13 /system ext4 ro,seclabel,noatime,nodiratime,user_xattr,barrier=0,data=writeback,discard 0 0
/dev/block/mmcblk0p16 /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,barrier=0,journal_async_commit,data=writeback,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.heku.readingtrainer-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.vito.lux-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p14 /preload ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/dev/block/vold/179:49 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Sent from my GT-N7100 using Tapatalk
Problem solved doing backup, full wipe and reset, and restore with TWRP. I put my sd card's content into an archive and restored it after the hole process.
Sent from my GT-N7100 using Tapatalk

Which of the Many Mount Points is the Internal Storage

I put a new rom on my tablet but I forgot that there were a few pictures I wanted to keep on it. The mount command in a terminal brings up the following. Can anyone tell which is the internal storage. I've already been able to pull off a couple of images with the dd command, but I'm not sure if I'm getting the internal storage or not.
[email protected]:/ $ su
[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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MDM /mnt/modem ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk1p1 /storage/sdcard1 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
internal storage
it looks like /dev/block/mmcblk1p1
but if i'm understanding fuse right the stuff your trying to get back
might be totally boned
this command should pull the whole thing
cat /dev/block/<block> > /mnt/sdcard/<image>.img
hope i got that right and that it helps
bye

Categories

Resources