[Q] OpenVPN Eclair 2.1 SGS I9000 **What is wrong?** - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi all,
I'm still working trying to work my openvpn:
Link related to thread:
http://forum.xda-developers.com/showpost.php?p=8347800&postcount=3
http://code.google.com/p/android-openvpn-installer/issues/detail?id=2
Now, some info about my config:
# mount
mount
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Check load of tun.ko
#lsmod
tun 11088 0 - Live 0xbf203000
Path to busybox:
# which busybox
/system/xbin/busybox
Path to Openvpn:
# which openvpn
/system/xbin/openvpn
Links for openvpn due harcode
# busybox ls -la /system/xbin/bb
total 8
drwxrwxrwx 1 0 0 0 Oct 20 03:17 .
drwxr-xr-x 1 0 2000 0 Oct 20 03:18 ..
lrwsrwsrwt 1 0 0 60 Oct 20 03:14 ifconfig -> /system/xbin/ifconfig
lrwsrwsrwt 1 0 0 56 Oct 20 03:17 route -> /system/xbin/route
# busybox ls -la /system/xbin/ifconfig
busybox ls -la /system/xbin/ifconfig
lrwsrwsrwt 1 0 0 60 Oct 20 07:19 ←[1;36m/system/xbin/ifconfig←[0m -> ←[1;32m/system/xbin/busybo←[0m
# busybox ls -la /system/xbin/route
busybox ls -la /system/xbin/route
lrwsrwsrwt 1 0 0 60 Oct 20 07:19 ←[1;36m/system/xbin/route←[0m -> ←[1;32m/system/xbin/busybox←[0m
Path to tun.ko module
# busybox ls -la /system/lib/modules
busybox ls -la /system/lib/modules
total 152
drwxrwxrwx 1 0 0 0 Oct 20 07:19 ←[1;34m.←[0m
drwxr-xr-x 1 0 0 0 Oct 20 02:19 ←[1;34m..←[0m
-rwxrwxrwx 1 0 0 154447 Oct 20 12:19 ←[1;32mtun.ko←[0m
Busybox Version:
# busybox
busybox
BusyBox v1.17.1 (2010-08-12 23:44:34 CDT) multi-call binary.
Openvpn Version based on first link
# openvpn
openvpn
OpenVPN 2.1_rc15 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] built on Jan 21 2010
Now, my openvpn connect, but cant get ip address , i mean, on GUI interface of openvpn after connect, still like "connected to mydomain.com as"..
if a try to launch via terminal (adb shell) after write "openvpn --config <path to my *.ovpn config file>, freeze the screen and nothins happens...
This is the final phase for each connection, looking on my logfile:
Wed Oct 20 09:13:40 2010 TLS: Initial packet from XXX.XXX.XXX.XXX:YYY, sid=caddb5cd 96066b25
Wed Oct 20 09:13:43 2010 VERIFY OK: depth=1, /C=CO/ST=CU/L=Bogota/O=Favernet/CN=NASVPN/[email protected]
Wed Oct 20 09:13:43 2010 VERIFY OK: depth=0, /C=CO/ST=CU/O=Favernet/CN=FavernetVPN/[email protected]
Wed Oct 20 09:13:56 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 20 09:13:56 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 20 09:13:56 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 20 09:13:56 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 20 09:13:56 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Oct 20 09:13:56 2010 [FavernetVPN] Peer Connection Initiated with XXX.XXX.XXX.XXX:YYY
Wed Oct 20 09:13:57 2010 Initialization Sequence Completed
I'm not good with this, but i don't know what else need verification..any suggestions?

http://forum.xda-developers.com/showthread.php?t=729531 >> This is a DEVELOPMENT section, not GENERAL. Do NOT post questions here!
try here: http://forum.xda-developers.com/forumdisplay.php?f=748

Moved to Q&A as not development

Related

Which blocks are present in our SGA`s FW?

Does anyone have information about which blocks are present in our SGA?
For example: bml5 - it's core(?), stl12 - this system, stl13 - data and so on.
I would like to know them all.
I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed
Does anyone have information about which blocks are present in gt-s5830i?
problem partitions
I have a problem with these corrupt partitions I have them and I can not restore a backup
ketut.kumajaya said:
I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed
Click to expand...
Click to collapse
how to get information like you? I used the two commands cat /proc/partitions" and "cat /proc/mounts
results
Code:
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 1954816 mmcblk0
179 1 1954751 mmcblk0p1
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 186624 bml13
137 14 29696 bml14
137 15 6144 bml15
138 12 214784 stl12
138 13 179968 stl13
138 14 25856 stl14
138 15 2304 stl15
254 0 2110 dm-0
#
Code:
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
0 0
/dev/stl15 /secure rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,io
charset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=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.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
please help me to get the information you thankssssss:good:
please help me .................................................
Try running this:
ls -al /dev/block/platform/msm_sdcc.1/by-name
That works on my GS3, on AT&T....
~Ibrahim~

CM10 - Issue with /data partiton

After installing the latest CM10 Nightly 20121002 it would appear that the /datadata partition is back however my apps are still trying to install themselves to /data which has been reduced to ~80MB and as a result I get a messsage soon after the market restore begins that space is low.
I went back to CM10-20120919 and I have 422MB available in the /data partition as expected.
I tried to post to the CM10 Nightly thread but I'm still less than 10 posts old on XDA, I posted the partition layout in 20121002 on the Cyanogen forums, can't post links, too noobish for XDA yet again.
Is this expected behaviour in CM10? Do we now how to put everything on the SD card?
Hi,
I'm on CM10 1002 and I have 1G free in /data (and 472M used). In /datadata I have 218M free and 203M used.
All my apps are on the phone, i didn't moved anything on sd card.
I think it was something wrong with your install, you should try flashing it again.
Aviatoru said:
Hi,
I'm on CM10 1002 and I have 1G free in /data (and 472M used). In /datadata I have 218M free and 203M used.
All my apps are on the phone, i didn't moved anything on sd card.
I think it was something wrong with your install, you should try flashing it again.
Click to expand...
Click to collapse
I have downloaded the latest nightly 20121003 and I still have the same issue.
Here is what I see in ADB:
1|[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 184M 48K 184M 4096
/mnt/asec 184M 0K 184M 4096
/mnt/obb 184M 0K 184M 4096
/cache 17M 2M 14M 4096
/radio 16M 15M 760K 4096
/datadata 422M 17M 404M 4096
/system 393M 229M 164M 4096
/data 81M 46M 35M 4096
/efs 12M 5M 6M 4096
/storage/sdcard1 7G 822M 6G 32768
/storage/sdcard0 14G 11G 3G 8192
/mnt/secure/asec 14G 11G 3G 8192
[email protected]:/ # mount
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/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,n
omblk_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/vold/179:9 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch:angel:
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
Everything checks out except the /data LV, it's only been created as 81MB!
Something has gone wrong in LVM:
--- Volume group ---
VG Name lvpool
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 484.00 MiB
PE Size 4.00 MiB
Total PE 121
Alloc PE / Size 121 / 484.00 MiB
Free PE / Size 0 / 0
VG UUID buUfFr-wHCP-0WaI-theX-LYHJ-WIB3-CvBIW0
--- Logical volume ---
LV Path /dev/lvpool/system
LV Name system
VG Name lvpool
LV UUID KyabDe-sf7A-eVsT-S0ay-XenC-Yvyk-QuStAC
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 400.00 MiB
Current LE 100
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/lvpool/userdata
LV Name userdata
VG Name lvpool
LV UUID zIQCKS-O3sA-QqJa-6FCb-dw0A-mvSV-5nAcH0
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 84.00 MiB
Current LE 21
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
[EDIT]
Partition list on mmcblk0
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16005464064 bytes
255 heads, 63 sectors/track, 1945 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1868 15004678+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 1869 1931 500173 83 Linux
/dev/block/mmcblk0p3 1931 1946 125453 82 Linux swap
Anybody know how to fix this?
infecticide said:
I have downloaded the latest nightly 20121003 and I still have the same issue.
Here is what I see in ADB:
1|[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 184M 48K 184M 4096
/mnt/asec 184M 0K 184M 4096
/mnt/obb 184M 0K 184M 4096
/cache 17M 2M 14M 4096
/radio 16M 15M 760K 4096
/datadata 422M 17M 404M 4096
/system 393M 229M 164M 4096
/data 81M 46M 35M 4096
/efs 12M 5M 6M 4096
/storage/sdcard1 7G 822M 6G 32768
/storage/sdcard0 14G 11G 3G 8192
/mnt/secure/asec 14G 11G 3G 8192
[email protected]:/ # mount
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/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,n
omblk_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/vold/179:9 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch:angel:
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
Everything checks out except the /data LV, it's only been created as 81MB!
Something has gone wrong in LVM:
--- Volume group ---
VG Name lvpool
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 484.00 MiB
PE Size 4.00 MiB
Total PE 121
Alloc PE / Size 121 / 484.00 MiB
Free PE / Size 0 / 0
VG UUID buUfFr-wHCP-0WaI-theX-LYHJ-WIB3-CvBIW0
--- Logical volume ---
LV Path /dev/lvpool/system
LV Name system
VG Name lvpool
LV UUID KyabDe-sf7A-eVsT-S0ay-XenC-Yvyk-QuStAC
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 400.00 MiB
Current LE 100
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/lvpool/userdata
LV Name userdata
VG Name lvpool
LV UUID zIQCKS-O3sA-QqJa-6FCb-dw0A-mvSV-5nAcH0
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 84.00 MiB
Current LE 21
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
[EDIT]
Partition list on mmcblk0
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16005464064 bytes
255 heads, 63 sectors/track, 1945 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1868 15004678+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 1869 1931 500173 83 Linux
/dev/block/mmcblk0p3 1931 1946 125453 82 Linux swap
Anybody know how to fix this?
Click to expand...
Click to collapse
So I think I found the problem and, possibly, the solution.
I noticed on my internal SD card that there is a swap parititon that wasn't being used, as confirmed by 'free' in ADB. Swap shouldn't be there so I deleted it Reflashed, hoping it would recreate the internal partitioning to right size. Nope, same issue.
Deleted the linux partition (mmcblk0p2) hoping that during the reflash it would recreate it. Nope, almost bricked the phone until I discovered that ADB is available in recovery.
Re-created said partition with remaining space, I now have ~360MB of "internal storage". So it would appear that the internal card is partitioned wrong.
Could the helpful person from before, go into ADB shell and run fdisk -l /dev/block/mmcblk0 and post the results so I can see what I should have for unit numbers?
Thanks!

How can I (we) contribute to dev, rooting, roms, etc?

I apologize if this is a newbie question, but now that my kindle fire 2 updated itself to 10.2.3, I have lost root. I've also noticed that no roms or bootloader workaround has been done for the kindle fire 2.
So my question is: if I have some experience with linux systems (although maybe not with android specifically), how can I get started contributing to the rom community? I ask this in the context of kindle fire 2 of course.
I found a few docs like this: dubdubdub sourceconference dot com slash publications/bos12pubs/android-modding-source.pdf
I noticed that /data is now under group perm rwx :system , and maybe there's an existing path towards getting system group perm from standard adb shell
Code:
127|[email protected]:/sys $ mount
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/platform/omap/omap_hsmmc.1/by-name/system /system ext4 ro,relatime,ba
rrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4 rw,nosuid,node
v,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4 rw,nosuid,nodev,
noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /efs ext4 rw,relatime,barrier=
1,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,d
efault_permissions,allow_other 0 0
[email protected]:/sys $ ls -al /
ls -al /
drwxr-xr-x root root 2012-12-06 10:04 acct
drwxrwx--- system cache 2012-12-06 12:23 cache
dr-x------ root root 2012-12-06 10:04 config
lrwxrwxrwx root root 2012-12-06 10:04 d -> /sys/kernel/debug
drwxrwx--x system system 2012-12-05 11:54 data
-rw-r--r-- root root 89 1969-12-31 18:00 default.prop
drwxr-xr-x root root 2012-12-06 10:04 dev
drwxr-xr-x root root 2012-11-22 01:59 efs
lrwxrwxrwx root root 2012-12-06 10:04 etc -> /system/etc
-rwxr-x--- root root 98608 1969-12-31 18:00 init
-rwxr-x--- root root 2344 1969-12-31 18:00 init.goldfish.rc
-rwxr-x--- root root 9053 1969-12-31 18:00 init.omap4blazeboard.rc
-rwxr-x--- root root 4204 1969-12-31 18:00 init.omap4blazeboard.usb.
rc
-rwxr-x--- root root 17463 1969-12-31 18:00 init.rc
lrwxrwxrwx root root 2012-12-06 10:04 misc -> /dev/block/platfo
rm/omap/omap_hsmmc.1/by-name/misc
drwxrwxr-x root system 2012-12-06 10:04 mnt
dr-xr-xr-x root root 1969-12-31 18:00 proc
drwx------ root root 2012-11-28 01:23 root
drwxr-x--- root root 1969-12-31 18:00 sbin
lrwxrwxrwx root root 2012-12-06 10:04 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-12-06 10:04 sys
drwxr-xr-x root root 2012-12-06 06:33 system
-rw-r--r-- root root 272 1969-12-31 18:00 ueventd.goldfish.rc
-rw-r--r-- root root 1289 1969-12-31 18:00 ueventd.omap4blazeboard.r
c
-rw-r--r-- root root 4267 1969-12-31 18:00 ueventd.rc
lrwxrwxrwx root root 2012-12-06 10:04 vendor -> /system/vendor
re: contributing, and not moaning..
..respect to you, Sir, refreshing attitude - guess you can best help by doing..
for my own part, currently have a 'half-root' KF2, root read / ftp access, Google Music (only thing I need personally) etc. all working fine under 10.2.3, I cannot change folder permissions (/data, etc.) at all tho, either under adb or ftp (does ftp chmod work *at all*? on Fire? - I have zero android/Fire experience, unfortunately), any and all further ideas appreciated tho..
either that, or I guess we just wait on the 10.2.3 Youtube crack walkthrough
My impression so far is there are three categories of workaround for root:
file permissions exploits, which take advantage of log writing or other scripts that already have root, and hijack them to modify system perms (e.g. the qemu root method)
bootloader over-writing (e.g. cwm). KF2 uses a locked bootloader unlike KF1, but KF2 ("otter2" builds) share a lot of similarity with the kindle HD, and that bootloader has reportedly been successfully worked around by some people.
other exploits, e.g. the typical modifying of binary assembly files or overflow bugs that are totally outside of my purview
any others?
If there was a repository of ideas for #1, perhaps we can see if there's crossover of another vendor exploit with KF2.
Also, I'd love links that outline the boot, recovery, and OTA scripts for KF2
Ideas for trying #2 without bricking would be nice too

[HoWTO] [FINDING MOUNT POINTS] [SAMSUNG] [NAUTILUS]

Hello buddies..
From the concept SHARING IS CARING, I am going to share with you how to get the mount points of a samsung device.
So let's start!!
Needed tools:
1)Any Linux distro that supports Nautilus scripts
2)Willing of learning and some patience and cold nerves!
First off Download This : CLICK ME!
Set-Up:
Now Open Your Home Folder.
1) Copy The Downloaded File then Press Ctrl+H .
2) Now open .gnome2 . Now open nautilus-scripts.
3) Paste the downloaded File There.
4) Open Terminal Using Ctrl+Alt+T
5) Paste This Into Terminal And Hit Enter.
Code:
chmod a+x ~/.gnome2/nautilus-scripts/Mount-Points
Now To Use This Script to find the mount points.
1) Ensure You Have ADB Working
2) Connect Your Phone with USB Debugging On
3) Now Open HOME Folder
4) Right-Click And Scroll To Scripts.
5) Now Select "Mount-Points"
6) Check in You Home Dir To See mounts.txt
Thats It!! Have Fun Making ROMS!!
Wtf
Isnt it easier to just tell em to adb shell cat /proc/mounts and adb shell cat /proc/partitions :silly:
This way some will learn a bit since this is xda university section and not the i want likes for every post section ^^
Hi mate.
I can get some Mount points later if you still need them, what Linux distro is recommended? And how easy is to to use a n7100 ROM after the mount points have been found??
Sent from my GT-N7105 using Tapatalk 2
Robbie Hood said:
Wtf
Isnt it easier to just tell em to adb shell cat /proc/mounts and adb shell cat /proc/partitions :silly:
This way some will learn a bit since this is xda university section and not the i want likes for every post section ^^
Click to expand...
Click to collapse
Hmm...but those commands don't show me the logical location (aka mount points):
Code:
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/mounts
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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.urbandroid.sleep.full.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.quoord.tapatalkpro.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.boatbrowser.license.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.vito.lux-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.distractionware.superhexagon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.asksven.betterbatterystats-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/gov.whitehouse-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.tyenee.android.googlecontactformatter-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/org.mots.haxsync-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/vold/179:97 /storage/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
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 9387 loop1
7 2 2111 loop2
7 3 3150 loop3
7 4 66591 loop4
7 6 5229 loop6
7 7 3150 loop7
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 15557120 mmcblk1p1
254 0 2110 dm-0
254 1 9387 dm-1
254 2 2110 dm-2
254 3 3150 dm-3
254 4 66591 dm-4
254 6 5229 dm-6
254 7 3150 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 3150 loop9
254 9 3150 dm-9
I know mmcblk0p18 is recovery from another guide I read, but how did they figure that out? Are these Nautilus scripts the easiest way, then?
EDIT: this command works! ls -al /dev/block/platform/msm_sdcc.1/by-name
ikjadoon said:
Hmm...but those commands don't show me the logical location (aka mount points):
Code:
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/mounts
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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.urbandroid.sleep.full.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.quoord.tapatalkpro.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.boatbrowser.license.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.vito.lux-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.distractionware.superhexagon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.asksven.betterbatterystats-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/gov.whitehouse-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.tyenee.android.googlecontactformatter-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/org.mots.haxsync-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/vold/179:97 /storage/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
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 9387 loop1
7 2 2111 loop2
7 3 3150 loop3
7 4 66591 loop4
7 6 5229 loop6
7 7 3150 loop7
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 15557120 mmcblk1p1
254 0 2110 dm-0
254 1 9387 dm-1
254 2 2110 dm-2
254 3 3150 dm-3
254 4 66591 dm-4
254 6 5229 dm-6
254 7 3150 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 3150 loop9
254 9 3150 dm-9
I know mmcblk0p18 is recovery from another guide I read, but how did they figure that out? Are these Nautilus scripts the easiest way, then?
EDIT: this command works! ls -al /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
Actually, the first command - cat /proc/mounts gives you the mount points. The first column is the device, the second column is the mount point, the third column is the file system type, the fourth column is how it is mounted, i.e. ro (read-only) or rw (read-write) and so on. The second command gives the partition table. You may be able to look at other files, like fstab or recovery.fstab to see where other things are.
sidneyk said:
Actually, the first command - cat /proc/mounts gives you the mount points. The first column is the device, the second column is the mount point, the third column is the file system type, the fourth column is how it is mounted, i.e. ro (read-only) or rw (read-write) and so on. The second command gives the partition table. You may be able to look at other files, like fstab or recovery.fstab to see where other things are.
Click to expand...
Click to collapse
Do a adb pull yourphone/proc/mounts
Sent from my GT-P7300 using xda premium
mithun46 said:
Do a adb pull yourphone/proc/mounts
Sent from my GT-P7300 using xda premium
Click to expand...
Click to collapse
OK, here is from my SGH-T769 under Android:
Code:
[email protected]:~$ adb shell cat /proc/mounts
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/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/vold/179:33 /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
/dev/block/vold/179:28 /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:28 /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
/dev/block/dm-1 /mnt/asec/com.gsn.android.casino-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.phantomefx.standalone.mermaidspearl-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.phantomefx.standalone.robinhood-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.chartcross.gpstest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.androidwasabi.livewallpaper.raindrop-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/air.com.slotgalaxy-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.farproc.wifi.analyzer-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/air.com.playtika.slotomania-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.iudesk.android.photo.editor-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/com.eamobile.life_na_wf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.google.android.apps.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/org.zwanoo.android.speedtest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.phantomefx.standalone.theheist-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.joeykrim.rootcheckp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-15 /mnt/asec/com.androidwasabi.livewallpaper.dandelion-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-16 /mnt/asec/com.phantomefx.indianspirit_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-17 /mnt/asec/com.zumobi.msnbc-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-18 /mnt/asec/com.slots-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-19 /mnt/asec/com.anddoes.launcher.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-20 /mnt/asec/com.bvalosek.cpuspy.realgpp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-21 /mnt/asec/com.pokiemagic.KalahariSunFree-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-22 /mnt/asec/com.mw.slotsroyale-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-23 /mnt/asec/com.phantomefx.leprecoin_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-24 /mnt/asec/air.com.Slot-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-25 /mnt/asec/com.audioaddict.sky-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-26 /mnt/asec/com.fishsticksgames.SlotsJourney-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-27 /mnt/asec/com.quoord.tapatalkxda.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-28 /mnt/asec/com.mxtech.videoplayer.ad-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-29 /mnt/asec/mobi.mgeek.TunnyBrowser-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-30 /mnt/asec/com.phantomefx.aztecsun_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-31 /mnt/asec/com.natenai.virtualhorseracing3d-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-32 /mnt/asec/com.eamobile.monopoly_full_azn-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-33 /mnt/asec/com.phantomefx.balloonblitz-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-34 /mnt/asec/com.jrummy.liberty.toolboxpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-35 /mnt/asec/com.ziplinegames.slotstycoon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-36 /mnt/asec/com.google.zxing.client.android-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-37 /mnt/asec/com.phantomefx.bovinebling_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-38 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-39 /mnt/asec/com.phantomefx.tunzamunny-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-40 /mnt/asec/com.hotrod.reference.spiritofseventysix-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-41 /mnt/asec/com.phantomefx.standalone.spiritwolf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
And here is the contents of /etc/recovery.fstab from the CWM recovery ramdisk:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p22
/efs ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p25
/system ext4 /dev/block/mmcblk0p24
/cache ext4 /dev/block/mmcblk0p26
/emmc vfat /dev/block/mmcblk0p28
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2
And here is the contents of /fstab.qcom back in the normal Android OS:
Code:
[email protected]:/ # cat /fstab.qcom
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p24 /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p26 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p21 /efs ext4 nosuid,nodev,barrier=1 wait.check
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
This, of course, applies to my phone, Samsung Galaxy S Blaze 4G SGH-T769 with custom CWM recovery and custom PACman JB 4.1.2 ROM. You should be able to see the same things on your phone, especially if rooted, and can see where the friendly names of the familiar mount points are at and how it was figured out. There are also other mounts being executed in some of the other startup files. One thing of note, is that the recovery system and Android system may, and probably do, use different mount points and even different mount names for internal storage and external sdcard. For example, in recovery, the internal storage is /emmc and /sdcard and /sd-ext are the external sdcard. Under Android, /sdcard can refer to at least a part of internal storage. Under Android 4.1+ the external card is /storage/sdcard1 and the internal is also /storage/sdcard0. Some of the devices are given multiple mount points (or at least symlinks) with different names pointing to the same device. Confusing as hell, but that's the way it is.
sidneyk said:
OK, here is from my SGH-T769 under Android:
Code:
[email protected]:~$ adb shell cat /proc/mounts
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/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/vold/179:33 /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
/dev/block/vold/179:28 /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:28 /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
/dev/block/dm-1 /mnt/asec/com.gsn.android.casino-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.phantomefx.standalone.mermaidspearl-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.phantomefx.standalone.robinhood-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.chartcross.gpstest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.androidwasabi.livewallpaper.raindrop-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/air.com.slotgalaxy-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.farproc.wifi.analyzer-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/air.com.playtika.slotomania-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.iudesk.android.photo.editor-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/com.eamobile.life_na_wf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.google.android.apps.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/org.zwanoo.android.speedtest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.phantomefx.standalone.theheist-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.joeykrim.rootcheckp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-15 /mnt/asec/com.androidwasabi.livewallpaper.dandelion-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-16 /mnt/asec/com.phantomefx.indianspirit_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-17 /mnt/asec/com.zumobi.msnbc-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-18 /mnt/asec/com.slots-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-19 /mnt/asec/com.anddoes.launcher.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-20 /mnt/asec/com.bvalosek.cpuspy.realgpp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-21 /mnt/asec/com.pokiemagic.KalahariSunFree-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-22 /mnt/asec/com.mw.slotsroyale-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-23 /mnt/asec/com.phantomefx.leprecoin_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-24 /mnt/asec/air.com.Slot-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-25 /mnt/asec/com.audioaddict.sky-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-26 /mnt/asec/com.fishsticksgames.SlotsJourney-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-27 /mnt/asec/com.quoord.tapatalkxda.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-28 /mnt/asec/com.mxtech.videoplayer.ad-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-29 /mnt/asec/mobi.mgeek.TunnyBrowser-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-30 /mnt/asec/com.phantomefx.aztecsun_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-31 /mnt/asec/com.natenai.virtualhorseracing3d-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-32 /mnt/asec/com.eamobile.monopoly_full_azn-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-33 /mnt/asec/com.phantomefx.balloonblitz-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-34 /mnt/asec/com.jrummy.liberty.toolboxpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-35 /mnt/asec/com.ziplinegames.slotstycoon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-36 /mnt/asec/com.google.zxing.client.android-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-37 /mnt/asec/com.phantomefx.bovinebling_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-38 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-39 /mnt/asec/com.phantomefx.tunzamunny-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-40 /mnt/asec/com.hotrod.reference.spiritofseventysix-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-41 /mnt/asec/com.phantomefx.standalone.spiritwolf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
And here is the contents of /etc/recovery.fstab from the CWM recovery ramdisk:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p22
/efs ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p25
/system ext4 /dev/block/mmcblk0p24
/cache ext4 /dev/block/mmcblk0p26
/emmc vfat /dev/block/mmcblk0p28
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2
And here is the contents of /fstab.qcom back in the normal Android OS:
Code:
[email protected]:/ # cat /fstab.qcom
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p24 /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p26 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p21 /efs ext4 nosuid,nodev,barrier=1 wait.check
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
This, of course, applies to my phone, Samsung Galaxy S Blaze 4G SGH-T769 with custom CWM recovery and custom PACman JB 4.1.2 ROM. You should be able to see the same things on your phone, especially if rooted, and can see where the friendly names of the familiar mount points are at and how it was figured out. There are also other mounts being executed in some of the other startup files. One thing of note, is that the recovery system and Android system may, and probably do, use different mount points and even different mount names for internal storage and external sdcard. For example, in recovery, the internal storage is /emmc and /sdcard and /sd-ext are the external sdcard. Under Android, /sdcard can refer to at least a part of internal storage. Under Android 4.1+ the external card is /storage/sdcard1 and the internal is also /storage/sdcard0. Some of the devices are given multiple mount points (or at least symlinks) with different names pointing to the same device. Confusing as hell, but that's the way it is.
Click to expand...
Click to collapse
U r right
Sent from my GT-P7300 using xda premium
Since this is xda university to share info with new xda members, here is a summary on how to get mounting points without rooting or extracting recovery.img.
The different procedures only needs to have adb shell or terminal emulator.. I will explain using adb shell through pc.
After establishing adb connection to your device, you can choose any of the following procedures to get your mounting points:
#1
Code:
adb shell
cat /proc/mounts
This will give you info about device, the mount point, the file system type, and how it is mounted. (see post #4)
Limitation: This method, however, will not give you all mounting points.!!!
#2
Code:
adb shell
cat /proc/partitions
This is more neat, it will give you info about ALL dev blocks and their names (not the familiar name!), and block size
Limitation: Needs from you to figure out which block belong to which partition name.!!
{
"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"
}
#3
Code:
adb shell
ls -al /dev/block/platform/[B][COLOR="Blue"]dw_mmc[/COLOR][/B]/by-name
This one is the command that I like on non-rooted device..! It will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc) :laugh:
This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).
How?
- In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).
- Go to "/dev/block/platform/" folder
- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.
N.B: If you check post #4, it was "msm_sdcc.1", so it depends totally on which device you have.!
- At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)
- Now open adb shell and put the command..
If anyone knows any other method for NON-ROOTED devices, please share.
Cheers
Why not use adb shell,then just type mount > /sdcard/mounts.txt and use adb pull to get it?
通过我的 SM-N9200 上的 Tapatalk发言

4.3 System Dump?

Anyone mind pulling the 4.3 System Dump?
adb shell
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
exit
adb pull /sdcard/system.img
unlocked, rooted then was deleting some google apps and bloatware and now I can't get past the splash screen. Fastboot works and detects device so Im not bricked yet.
US 4.3 Sku by the way
schmeggy929 said:
US 4.3 Sku by the way
Click to expand...
Click to collapse
Ow, as I said I can do it in about 2 hours.. but I've the ww edition...
And if I remember correctly it is partition 4 not 1 (mmcblk0p4)
menollo said:
Ow, as I said I can do it in about 2 hours.. but I've the ww edition...
And if I remember correctly it is partition 4 not 1 (mmcblk0p4)
Click to expand...
Click to collapse
ok thanks I will update the thread, will the WW sku boot on a US version?
mmcblk01 used to be system on the TF700T...
Have they changed it to mmcblk04 on the TF701T?
04 was the staging partition
sbdags said:
mmcblk01 used to be system on the TF700T...
Have they changed it to mmcblk04 on the TF701T?
04 was the staging partition
Click to expand...
Click to collapse
Im not sure, still stuck on the asus splash screen. I originally thought it was mmcblk01.
Anyone wanna help a brotha out? mmcblk01 and mmcblk04, I'll fastboot both lol
Sent from my HTCONE using Tapatalk
[email protected]:/ $ mount
rootfs / rootfs ro,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/sdhci-tegra.3/by-name/ADF /ADF ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/PER /persist ext4 ro,seclabel,relatime,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,errors=panic,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=755,gid=1000 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=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]:/ $ ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2013-11-16 20:54 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-11-16 20:54 APD -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-11-16 20:54 APP -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-11-16 20:54 CAC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-11-16 20:54 CRA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-11-16 20:54 DTB -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-11-16 20:54 EKS -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-11-16 20:54 LNX -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-11-16 20:54 MDA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-11-16 20:54 MSC -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-11-16 20:54 PER -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-11-16 20:54 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-11-16 20:54 UDA -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-11-16 20:54 USP -> /dev/block/mmcblk0p9
menollo said:
[email protected]:/ $ mount
rootfs / rootfs ro,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/sdhci-tegra.3/by-name/ADF /ADF ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/PER /persist ext4 ro,seclabel,relatime,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,errors=panic,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=755,gid=1000 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=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]:/ $ ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2013-11-16 20:54 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-11-16 20:54 APD -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-11-16 20:54 APP -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-11-16 20:54 CAC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-11-16 20:54 CRA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-11-16 20:54 DTB -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-11-16 20:54 EKS -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-11-16 20:54 LNX -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-11-16 20:54 MDA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-11-16 20:54 MSC -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-11-16 20:54 PER -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-11-16 20:54 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-11-16 20:54 UDA -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-11-16 20:54 USP -> /dev/block/mmcblk0p9
Click to expand...
Click to collapse
First off thank you for taking the time to do this. I never created a image file, so im a clueless with what im supposed to do with this text.
menollo said:
[email protected]:/ $ mount
rootfs / rootfs ro,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/sdhci-tegra.3/by-name/ADF /ADF ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/PER /persist ext4 ro,seclabel,relatime,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,errors=panic,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=755,gid=1000 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=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]:/ $ ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2013-11-16 20:54 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-11-16 20:54 APD -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-11-16 20:54 APP -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-11-16 20:54 CAC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-11-16 20:54 CRA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-11-16 20:54 DTB -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-11-16 20:54 EKS -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-11-16 20:54 LNX -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-11-16 20:54 MDA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-11-16 20:54 MSC -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-11-16 20:54 PER -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-11-16 20:54 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-11-16 20:54 UDA -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-11-16 20:54 USP -> /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Thanks for confirming. Most blocks got moved for the tegra4.
Ok So I solved my little soft bricked problem. I flashed the asus firmware for 4.2.2 (10.14.1.47) and reflash CWM. Restore my backup(thank god I made a backup!). All is good. Loaded the newest firmware(10.26.1.7) and back up on 4.3.
I wasn't as smart to create a backup image of my tablet ^^
Anyway, I'm running a WW-version of this tablet, already upgraded to 4.3.
Is anyone capable of pulling a system.img off a 4.3 WW TF701?
It would be greatly appreciated.
Thanks in advance.

Categories

Resources