Which blocks are present in our SGA`s FW? - Galaxy Ace S5830 Q&A, Help & Troubleshooting

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~

Related

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 change the first picture at boot?

Hi,
after some flash to fix my bootloop, see other thread, my I8190 is still alive
BUT..
After Power On i see a I9100 Samsung Galaxy II Logo instead I8190!
How can i fix that and how does it happend?
bootsamsung.qmg and bootsamsungloop.qmg replaced but still the same problem.
Ahh, the problem is http://forum.xda-developers.com/showpost.php?p=35104908&postcount=4
can anyone make a dd of a Galaxy S III mini, please?
youpiyo said:
Hi,
I did a wrong manipulation by trying to modify the .lfs partition on my infuse rogers phone.
I would need the original param.lfs from a ROGERS Infuse Phone
Here the command line to have it
adb shell
$ su
# dd if=/dev/block/???? of=/sdcard/param.lfs bs=4096
or you can use terminal emulator if you prefer (remove adb shell).
The param.lfs will be in your internal sd card.
The phone need to be rooted though.
Click to expand...
Click to collapse
which one is the param Partition?
mmcblk0 None 7456,00 NA
mmcblk0p1 None 0,12 NA
mmcblk0p2 None 0,38 NA
mmcblk0p3 None 1,00 NA
mmcblk0p4 None 1,00 NA
mmcblk0p5 None 0,50 NA
mmcblk0p6 None 0,50 NA
mmcblk0p7 None 0,50 NA
mmcblk0p8 None 0,50 NA
mmcblk0p9 /storage/extSdCard 7612,0 5594,2
mmcblk0p10 None 1,00 NA
mmcblk0p11 /efs 15,7 4,5
mmcblk0p12 /modemfs 15,7 4,4
mmcblk0p13 None 16,00 NA
mmcblk0p14 None 50,00 NA
mmcblk0p15 None 0,06 NA
mmcblk0p16 None 14,00 NA
mmcblk0p17 None 2,00 NA
mmcblk0p18 None 2,00 NA
mmcblk0p19 /mnt/.lfs 0,0 0,0
mmcblk0p20 None 16,00 NA
mmcblk0p21 None 16,00 NA
mmcblk0p22 /system 1151,6 826,5
mmcblk0p23 /cache 826,8 14,0
mmcblk0p24 /preload 315,0 64,2
mmcblk0p25 /data 4754,1 3369,8
mmcblk0boot1 None 2,00 NA
mmcblk0boot0 None 2,00 NA
mmcblk1 None 7620,00 NA
mmcblk1p1 /storage/extSdCard 7612,0 5594,2
partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 7802880 mmcblk1
179 97 7798784 mmcblk1p1
mounts
rootfs / rootfs rw 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
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 rw,relatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 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/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
Enjoy
thx, but there is no picture at boot. it´s gray
strange..
this is the original param of s3 mini dump from my phone.
if it's not work i dont know what you can do.
did you tried to flash full firmware?
The Bootlogos are inside.
There must be a paramater to select the right one.
This script show you all Images
script.sh param.lfs
#!/bin/bash
# filename: extract-jpg.sh
starts=(`grep -Pabo $'\xFF\xD8' $1 | cut -f 1 -d :`)
ends=(`grep -Pabo $'\xFF\xD9' $1 | cut -f 1 -d :`)
for (( i = 0 ; i < ${#starts[@]} ; i++ )); do
end=$((ends[$i] + 2))
count=$((end - starts[$i]))
echo "-I- Extracting ${starts[$i]}.jpg"
dd if=$1 bs=1 skip=${starts[$i]} count=$count > ${starts[$i]}.jpg
done
i dont know what it means, but if the pictures of logo they are inside the param.tar that i upload i dont know why isn't working.
First try: Odin 3.x sucks.
Secound try: 1.85 works! Big Thx
Happy to hear.
---------- Post added at 03:35 PM ---------- Previous post was at 03:25 PM ----------
p.s.
i tried now flash cf-root of galaxy s iii to check, the phone got soft bricked.
right after i flashed this file that i made, in odin 3.04 and it fix the logo.
I think recovery mode was fact from this flash..
try to go to recovery mode by command
Code:
adb reboot recovery
for me the phone stuck on the first boot.
thats why if you will try to flash full firmware, after flash done the phone will stuck again until you flash any other file (like param).
the reason for this is because cache.img include in the firmware and after odin flash this img it will reboot phone automaticly to recovery mode, then the phone stuck because recovery mode was fact..
basicly it means we wnot can do factory reset from the settings.

[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发言

[Q] Edify_defs file for kitchen

Can anyone provide me a link with edify_defs p880 file for dsixda's kitchen ?
i started to cooking stock rom(v20a i want to create a good rom like OMEGA rom from s3/s4) so now i can't flash it wihout this file :|
for example:
Lg Optimus 2X edify_defs file
# LG Optimus 2X
change_mnt=yes
fix_boot=yes
param1=ext3
param2=EMMC
sys_mnt=\/dev\/block\/mmcblk0p1
cache_mnt=\/dev\/block\/mmcblk0p2
boot_mnt=\/dev\/block\/mmcblk0p5
data_mnt=\/dev\/block\/mmcblk0p8
sdcard_mnt=\/dev\/block\/mmcblk0p9
So i need This device mount points
Seriously anyone ? nobody help me ?
Maby try a edify_defs file from the htc one x? The phone have almost the same hardware then the 4x hd! Make first a backup before you try it, or try it from another lg phone, it have alsmost the same software
Sent from my LG-P880 using xda app-developers app
noppoer2 said:
Maby try a edify_defs file from the htc one x? The phone have almost the same hardware then the 4x hd! Make first a backup before you try it, or try it from another lg phone, it have alsmost the same software
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Sorry but even if is the same hardware, any software is not the same, every device use another mounting point.
Why not just take apart another custom ROM build and get the information from there?
SimonTS said:
Why not just take apart another custom ROM build and get the information from there?
Click to expand...
Click to collapse
from META-INF ?
but how?
Allex42HD said:
Seriously anyone ? nobody help me ?
Click to expand...
Click to collapse
So we don't have developers ? Seriously nobody help me with that problem ?
Allex42HD said:
So we don't have developers ? Seriously nobody help me with that problem ?
Click to expand...
Click to collapse
Im not a developer. Wouldn't it work to do a
Code:
cat /proc/mounts
cat /proc/partitions
cat \proc/self/mountinfo
on the device to get the information you need?
Here's the output from my phone running Magic v2
Code:
2|[email protected]:/proc $ cat 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
debugfs /sys/kernel/debug debugfs 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/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,resuid=1000,errors=continue,user_xattr,acl,barrier=0,nodelalloc,nomblk_io_submit,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 ro,nosuid,nodev,noatime,user_xattr,acl,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.asksven.betterbatterystats-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/radiotime.player-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/eu.chainfire.perfmon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.ttxapps.dropsync.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.quoord.tapatalkpro.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.teslacoilsw.launcher.prime-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.joeykrim.rootcheckp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/cloudtv.hdwidgets-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.enterprisingapps.android.enterpriseping-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.riteshsahu.SMSBackupRestorePro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/com.quoord.tapatalkHD-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/vold/179:49 /storage/external_SD 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
[email protected]:/proc $ cat partitions
major minor #blocks name
7 0 5229 loop0
7 1 16664 loop1
7 2 2111 loop2
7 3 2111 loop3
7 4 9387 loop4
7 5 2111 loop5
7 6 2111 loop6
7 7 42651 loop7
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31164416 mmcblk1p1
254 0 5229 dm-0
254 1 16663 dm-1
254 2 2110 dm-2
254 3 2110 dm-3
254 4 9387 dm-4
254 5 2110 dm-5
254 6 2110 dm-6
254 7 42651 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 3150 loop9
254 9 3150 dm-9
7 10 20822 loop10
254 10 20821 dm-10
[email protected]:/proc/self $ cat mountinfo
1 1 0:1 / / ro,relatime - rootfs rootfs ro
11 1 0:11 / /dev rw,nosuid,relatime - tmpfs tmpfs rw,mode=755
12 11 0:9 / /dev/pts rw,relatime - devpts devpts rw,mode=600
13 1 0:3 / /proc rw,relatime - proc proc rw
14 1 0:12 / /sys rw,relatime - sysfs sysfs rw
15 14 0:5 / /sys/kernel/debug rw,relatime - debugfs debugfs rw
16 1 0:13 / /acct rw,relatime - cgroup none rw,cpuacct
17 1 0:14 / /mnt/asec rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
18 1 0:15 / /mnt/obb rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
19 11 0:16 / /dev/cpuctl rw,relatime - cgroup none rw,cpu
20 1 179:3 / /system ro,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP ro,user_xattr,acl,barrier=0,data=ordered
21 1 179:8 / /data rw,nosuid,nodev,noatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA rw,resuid=1000,errors=continue,user_xattr,acl,barrier=0,nodelalloc,nomblk_io_submit,data=ordered,noauto_da_alloc
22 1 179:4 / /cache rw,nosuid,nodev,noatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC ro,user_xattr,acl,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc
23 1 179:12 / /cal rw,nosuid,nodev,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAL rw,user_xattr,acl,barrier=0,data=ordered
24 1 179:9 / /persist-lg rw,nosuid,nodev,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/DRM rw,user_xattr,acl,barrier=0,data=ordered
25 1 179:10 / /mpt rw,nosuid,nodev,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/MLT rw,user_xattr,acl,barrier=0,data=ordered
26 1 0:17 / /storage/sdcard0 rw,nos
Allex42HD said:
So we don't have developers ? Seriously nobody help me with that problem ?
Click to expand...
Click to collapse
Developers (and honestly, everybody) expect that you at least reply and try to understand what you have been told.
You just created another thread for the same question. Wouldn't it have been easier to just bump that thread? Also, you got the answer there, but you didn't even try to test it. What do you expect then? Nobody will help if you don't care about the answers.
Adam77Root said:
Developers (and honestly, everybody) expect that you at least reply and try to understand what you have been told.
You just created another thread for the same question. Wouldn't it have been easier to just bump that thread? Also, you got the answer there, but you didn't even try to test it. What do you expect then? Nobody will help if you don't care about the answers.
Click to expand...
Click to collapse
yea yea i'm sorry but i'm desperate i want to create a stock based rom and i can't wihout this, htc one x file don't work for 4x hd because he has another software branded
anyone ?
Allex42HD said:
yea yea i'm sorry but i'm desperate i want to create a stock based rom and i can't wihout this, htc one x file don't work for 4x hd because he has another software branded
Click to expand...
Click to collapse
soo..... ? anyone :crying:

Help - accidentally deleted system, userdata, and radios partitions on my Nexus 6

When Magisk Manager put my Nexus 6 (AOSP 7.1.1) into an endless bootloop, I fired up ADB, went into TWRP, and tried to set thing right.
It only kinda worked. My phone would boot to the desktop, but all kinds of things just weren't right. (For instance, I couldn't use the rectangle icon to bring up a list of windows. It just didn't do anything, period.)
After wrestling with it for 6 hours or so, I finally accepted the fact that I was going to have to reinstall the OS, and redo all my customizations. Unfortunately, instead of doing a factory reset from the bootloader, I chose to wipe the system, radio, and userdata partitions from the wipe menu in TWRP.
Yes, it was stupid of me. I was tired, frustrated, angry at the broken Magisk Manager update, and badly sleep-deprived (the latter is due to a chronic medical condition, and is now, unfortunately, my default state).
Of course, TWRP warned me it would wipe my OS - but I assumed that meant it would wipe the contents of those partitions. Instead, it deleted the partitions themselves.
I can boot the phone to the bootloader, and TWRP is still present in the recovery partition, but I can't get it to install the OS from a zipfile (I have a USB-OTG cardreader, which it can see), because THE NECESSARY PARTITIONS ARE GONE, so it errors out. The same thing happens with partition image files from within the factory zip (which I also extracted to the sdcard from which I tried to install the zip).
Although I have developer options enabled, and I long ago unlocked the bootloader, ADB doesn't work (even to sideload files, despite my having started the TWRP sideload daemon). It does see the device in sideload mode, but it doesn't actually copy any files. Nor does it see the phone when I list devices. (Windows 10 reports that it doesn't recognize the USB-connected device, btw.) Naturally, fastboot doesn't work, either, apparently for the same reason.
So, somehow I need to recreate the system, userdata, cache, and radio partitions in order to install the factory zip, and get my phone to return from its undead state. The thing is, despite obvious evidence to the contrary, I'm not entirely stupid. I do not know how to create and name the necessary partitions, nor do I know what sizes they should be - and I'm unwilling to experiment with terminal commands until I'm certain I understand both things well enough to proceed.
If someone who knows what they're talking about would be kind enough to supply me with the above information, or to point me at existing resources that:
a. explain in detail how to use the terminal to create, size, and name the missing partitions (in stepwise fashion, if possible), and
b. supply me with the sizes of the partitions in question EXACTLY as whatever tool I have to use needs them to be specified,
I would be exceedingly grateful.
Thanks in advance for any help you can render.
If you go to recovery -> advanced -> terminal and enter the command "mount" do you get anything like the following?
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1507196k,nr_inodes=172748,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,size=1507196k,nr_inodes=172748)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
If you go to recovery -> advanced -> terminal and enter the command "mount" do you get anything like the following?
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1507196k,nr_inodes=172748,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,size=1507196k,nr_inodes=172748)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
What I get is identical to the above, EXCEPT the last two lines. They read as follows:
Code:
/dev/block/dm-0 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/dm-0 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
As you can see, the difference in both cases is "dm-0" in place of the volume designator.
As I said, those partitions are missing. The mount menu in TWRP won't allow them to be selected, and my attempts to flash the factory zip from an sdcard via USB-OTG fail with error messages indicating the partitions don't exist, so the images didn't flash. (This also happens when I attempt to flash the individual images.)
So, again, it's extremely clear to me that I need to create those partitions - and the radio and cache partitions - before I have any possibility of flashing a working OS, whether it's the factory shamu one, or a third-party firmware like Revolution/Remix.
BTW - Thank you for your substantive response. I very much appreciate your willingness to help!
Best regards,
Thom Stark
Click to expand...
Click to collapse
Try listing the partition table with this command:
fdisk -l /dev/block/mmcblk0
I’m going to information dump here for you. This is all of the relevant information from my device. Maybe it will help you recover.
I’m not sure enough of my knowledge to give you any suggestions on fixing this, but if all else fails, android stack exchange might be a resource.
Good Luck!
Code:
fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 42 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 256 229631 112M 0700 modem
2 229632 262399 16.0M 0700 metadata
3 262400 263167 384K 0700 sbl1
4 263424 263535 57344 0700 sdi
5 263936 263967 16384 0700 sec
6 263968 264031 32768 0700 ddr
7 264192 266239 1024K 0700 aboot
8 267192 267703 256K 0700 rpm
9 268192 269215 512K 0700 utags
10 269216 270215 500K 0700 tz
11 270216 278527 4156K 0700 padA
12 278528 279295 384K 0700 sbl1bak
13 279552 281599 1024K 0700 abootBackup
14 282552 283063 256K 0700 rpmBackup
15 283552 284575 512K 0700 utagsBackup
16 284576 285575 500K 0700 tzBackup
17 285576 285583 4096 0700 versions
18 285696 286719 512K 0700 frp
19 286720 288767 1024K 0700 mdm1m9kefs1
20 288768 290815 1024K 0700 mdm1m9kefs2
21 290816 292863 1024K 0700 mdm1m9kefs3
22 292864 294911 1024K 0700 padB
23 294912 327679 16.0M 0700 sp
24 327680 360447 16.0M 0700 keystore
25 360448 364543 2048K 0700 logs
26 364544 430079 32.0M 0700 persist
27 430080 430591 256K 0700 mdm1hob
28 430592 430655 32768 0700 mdm1dhob
29 430656 430911 128K 0700 cid
30 430912 447295 8192K 0700 logo
31 447296 449343 1024K 0700 misc
32 449344 454399 2528K 0700 padD
33 454400 454401 1024 0700 mdm1m9kefsc
34 454402 454417 8192 0700 ssd
35 454656 487455 16.0M 0700 recovery
36 487680 505855 9088K 0700 kpan
37 505856 538623 16.0M 0700 boot
38 538624 1062911 256M 0700 cache
39 1062912 1193983 64.0M 0700 oem
40 1193984 1196031 1024K 0700 padC
41 1196032 5390335 2048M 0700 system
42 5390336 61005567 26.5G 0700 userdata
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1510044 504 1509540 1% /dev
/dev/block/platform/msm_sdcc.1/by-name/system 2031440 1485728 529328 74% /system
tmpfs 1510044 0 1510044 0% /system/xbin
/sbin/.core/block/loop08 60400 1772 57320 3% /system/xbin/mcs
tmpfs 1510044 0 1510044 0% /mnt
/dev/block/platform/msm_sdcc.1/by-name/cache 253920 316 248364 1% /cache
/dev/block/platform/msm_sdcc.1/by-name/modem 78756 78696 0 100% /firmware
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 744 743 0 100% /fsg
/dev/block/platform/msm_sdcc.1/by-name/userdata 27240188 13256268 13967536 49% /data
tmpfs 1510044 448 1509596 1% /sbin
/data/media 27240188 13256268 13967536 49% /storage/emulated
Code:
cat /proc/mounts
rootfs / rootfs ro,seclabel 0 0 tmpfs /dev tmpfs
rw,seclabel,nosuid,relatime,size=1510044k,nr_inodes=160860,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0 none /dev/memcg
cgroup rw,relatime,memory 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0
0 none /dev/cpuset cgroup
rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/bfqio cgroup rw,relatime,bfqio 0 0 adb /dev/usb-ffs/adb
functionfs rw,relatime 0 0 proc /proc proc
rw,relatime,gid=3009,hidepid=2 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,seclabel,relatime 0 0 pstore /sys/fs/pstore
pstore rw,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4
ro,seclabel,relatime,data=ordered 0 0 tmpfs /system/xbin tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860 0 0
/sbin/.core/block/loop08 /system/xbin/mcs ext4
rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/7z ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/anrd ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/bash ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/cpustats ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dhdutil ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dnschk ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dumpcache
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/htop ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/httpurl ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/ioshark_bench
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/ksminfo ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/latencytop
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/librank ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/micro_bench
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system
/system/xbin/micro_bench_static ext4 ro,seclabel,relatime,data=ordered 0
0 /dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/mmc_utils
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/nano ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/pigz ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/powertop ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/procmem ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/procrank ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/puncture_fs
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/rawbu ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/rsync ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/runconuid
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system
/system/xbin/sane_schedstat ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/showmap ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/showslab ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/simpleperf
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/strace ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/taskstats
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/tcpdump ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/unrar ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/vim ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/zip ext4
ro,seclabel,relatime,data=ordered 0 0 /sbin/.core/block/loop08
/system/etc/hosts ext4 rw,seclabel,relatime,data=ordered 0 0 none /acct
cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0 /data/media /mnt/runtime/default/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid
0 0 /data/media /mnt/runtime/read/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid
0 0 /data/media /mnt/runtime/write/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid
0 0 none /config configfs rw,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4
rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4
ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4
rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4
ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 tmpfs /sbin tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /sbin/.core/mirror/system
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /sbin/.core/mirror/bin
ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 /sbin/.core/block/loop08 /sbin/.core/img ext4
rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata
/sbin/.core/db-0/magisk.db ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 tmpfs /storage tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0 /data/media /storage/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid
0 0 tmpfs /storage/self tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
7 64 65536 loop64
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
total 0
drwxr-xr-x 2 root root 880 1970-01-21 18:47 .
drwxr-xr-x 4 root root 960 1970-01-21 18:47 ..
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 system -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 versions -> /dev/block/mmcblk0p17
Have you tried to download the factory image and flash from bootloader. The flash all script.
camcory said:
Have you tried to download the factory image and flash from bootloader. The flash all script.
Click to expand...
Click to collapse
He said that he can't make the PC recognize the device in Fastboot or ADB after the accident.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Thank you, ktmom.
ktmom said:
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Thank you for the data dump, ktmom. I very much appreciate it.
Sorry it took so long for me to reply. I've been unwell.
(BTW - I like your .sig a lot. I wish more of us had Mr. Picciolini's attitude ... )
Best regards,
Thom Stark

Categories

Resources