{help needed} cannot find boot/recovery partition - Android Q&A, Help & Troubleshooting

i got the cat /proc/mounts here -
Code:
[email protected]:/ # cat /proc/mounts
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,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/nandi /oem cramfs ro,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal
_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journa
l_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=
ascii,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=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/extsd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.gameinsight.mycountry-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocha
rset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.vividgames.speedwaygp2012-1 vfat ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,i
ocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
can any one tell me from this which is the boot and recovery partition?

anyone please???

michael.the.don said:
i got the cat /proc/mounts here -
can any one tell me from this which is the boot and recovery partition?
Click to expand...
Click to collapse
/proc/mounts only shows currently mounted partitions, and not boot neither recovery are ever mounted. Instead check either /proc/mtd (for NAND) or in the partition table (for MMC, use fdisk).
If NAND, there's no guarantee the boot loader exposes those partitions to the kernel at all, though.

i tried using /proc/mtd but it says file missing.
how to use fdisk?
i tried using /proc/partitions
it gives me-
[email protected]:/ # cat /partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 5992448 nandj
179 0 15674368 mmcblk0
179 1 15670272 mmcblk0p1

michael.the.don said:
i tried using /proc/mtd but it says file missing.
how to use fdisk?
i tried using /proc/partitions
it gives me-
[email protected]:/ # cat /partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 5992448 nandj
179 0 15674368 mmcblk0
179 1 15670272 mmcblk0p1
Click to expand...
Click to collapse
Good enough, now you can start mapping all your partitions. Compare this to the mount list, and mark e.g. nande as data, etc. After a while you'll get a few unknown left, potential candidates for boot and recovery you can examine more carefully.

thanks very much.

michael.the.don said:
thanks very much.
Click to expand...
Click to collapse
I'd guess nandc and nandg, they seems about the right size and not mounted. dd them to a file and examine them if they've got the format mkbootimg produces. Those files should begin with "ANDROID!".
# dd if=/dev/block/nandg of=/sdcard/isthisboot.img

Related

[Q] Need some help with partitions

This is my portion layout:
$ su
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
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,iocharset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
and
$ su
# cat /proc/partitions
major minor #blocks name
137 0 513024 bml0/c
137 1 1536 bml1
137 2 768 bml2
137 3 768 bml3
137 4 17920 bml4
137 5 12800 bml5
137 6 768 bml6
137 7 6144 bml7
137 8 2048 bml8
137 9 10240 bml9
137 10 10240 bml10
137 11 768 bml11
137 12 173568 bml12
137 13 173056 bml13
137 14 102400 bml14
179 0 1955840 mmcblk0
179 1 1955775 mmcblk0p1
138 12 166912 stl12
138 13 166400 stl13
138 14 97280 stl14
#
I am trying to put system and boot.img!
I tried dd if=/dev/block/stl12 of=/sdcard/system.img and it shows a pound at the end I check my sdcard and there is nothing there? Is there something I'm doing wrong?

[Q] How to extract recovery.img from your phone

Hey everyone,
I'm having trouble extracting a recovery.img from my phone. More specific I can't seem to find which file I have to 'dd' to create the img file.
Some commands with the output
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/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
/[email protected] /system ext4 ro,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:97 /mnt/sdcard 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:97 /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 /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:6 /mnt/sdcard2 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
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 85216 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15110144 mmcblk1
179 97 15106048 mmcblk1p1
Code:
[email protected]:/ # cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0000ac40 00002800 "sec_ro"
emmc_p3: 00010740 00100000 "android"
emmc_p4: 00110f40 00100000 "cache"
emmc_p5: 00211740 00500000 "usrdata"
emmc_p6: 00711f40 000299c0 "fat"
Even by running the commands above I'm still not able to determine where I can extract a recovery.img.
Ive been looking around and can't seem to find anything so I hope someone can point me in the right direction.
PS: Phone in question is a Star B92M (chinaphone)
Thanks for the help!
~Whookid
EDIT: I'm looking for a way to do this without SP Flash tool

partitions of sony tablet s

note:this is a study log,i'am not sure if blow is all right:cyclops:
Code:
major minor #blocks dev format name mount note
179 1 2048 mmcblk0p1 ext2 CF /configs
179 2 393216 mmcblk0p2 ext4 A0 /system system.img flash here
179 3 393216 mmcblk0p3 ext4 A1 /system backup system?
179 4 524288 mmcblk0p4 ext4 CC /cache
179 5 2048 mmcblk0p5 ???? MC /misc can't mount
179 6 49152 mmcblk0p6 ???? UP /staging hidden.img flash here
179 7 1024 mmcblk0p7 ???? BF /blflags can't mount
179 8 393216 mmcblk0p8 ext4 DP /datapp manel mount
179 9 16384 mmcblk0p9 ext4 LG /log
179 10 4194304 mmcblk0p10 ext4 UA /data
179 11 9368576 mmcblk0p11 vfat SC /sdcard
here mmcblk0 is first mmc-block device,that is inner storage
mmcblk0p1 is first partition of mmcblk0
block size is 1 KB,so block count 2048 means size is 2MB
there are 2 system partition(p2,p3),p2 is main system partition,if something wrong with p2,system will use p3 for backup.
my tablet first boot will stop at sony logo(use p2),2nd boot will ok(use p3)
if i flash ics,it will flash to p2,and can't use in forst boot,but after wipe,it will back to 3.2.1 again,then next boot to ics....
??system rember what system used in blflag(p7)+0xC.
(in updater-script read_index("/blflags") and code in update-binary)
if the byte is 0,use p2,else use p3,my is 1
content of p7:all zero but 0x03C -- 0x1FB is 0xFF,and
Code:
0x0C:1
0x14:1
0x1fC:0xD2A7AA14
0x1000:BL_VERSION_INFO\0
0x1010:_BL\0 0x00000008
0x1020:_RM\0 0x0000001E
0x1030:_LX\0 0x07334EFF
0x1040:_E1\0 0x00000009
a wipe data will format partition:
data,cache,log,staging
when flash rom,system.img flash to p2 or p3,hidden.img flash to p6
condi's double flash roms flash both to p2 and p3
some cmd:
get partion list
Code:
cat /proc/partitions
p3,p6,p8 is only use in update-script,but you can mout it by cmd
Code:
mount -t ext4 /dev/block/mmcblk0p3 /dir-name
p5,p7,format is unknow,mount fail,but you can dump it's data by cmd
Code:
cat /dev/block/mmcblk0p3 /some-name.bin
or
Code:
dd if=/dev/block/mmcblk0p3 of=/some-name.bin
in theory,you can restore partition by dd cmd,but it's very dangers!
you can check what system you use by cmd mount
Code:
# mount
mount
rootfs / rootfs rw,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
/dev/block/mmcblk0p1 /configs ext2 ro,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
[COLOR="Red"]/dev/block/mmcblk0p3 /system ext4 rw,relatime,barrier=1,data=ordered 0 0[/COLOR]
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0
0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatim
e,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remoun
t-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-
ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=rem
ount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
View attachment partitions.7z
Have anyone treis to flip this blaflags partition flag which tells which partition to reboot from? It could allow more versatile flashing...
According to Chainfire's floating performance monitor application the Disk I/O is mmcblk0.
Sent from my Nexus 4 using xda app-developers app
Where is the kernel? In the system partition, because i can´t see a boot partition in your list...
Partitionator said:
Where is the kernel? In the system partition, because i can´t see a boot partition in your list...
Click to expand...
Click to collapse
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery
lopezk38 said:
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery
Click to expand...
Click to collapse
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..
;45311156 said:
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..
Click to expand...
Click to collapse
Robin, we need you to join the Sony Tablet Bootloader Discussion on Google Hangouts, can you PM me with your email with the subject "STBD"?
Sent from my Nexus 4 using Tapatalk 4

Custom Recovery

I have romdumped my device after searching everwhere and finally found the files. It is very different from the general files and i am confused.
These are the files shown in partitions
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd
93 32 1048576 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 2071552 nandi
179 0 1931264 mmcblk0
179 1 1927164 mmcblk0p1
And mount Points
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 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
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:64 /mnt/sdcard 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 /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Could you please tell mw how to make a custom recovery for my device.
Device Touchmate M-tab... Basically unherd of and no support anywhere. So please help me.
I had found a recovery builder (clockwork mod builder) but dont know how to use it. And i am confused abt the recovery.fstab.
Thankyou

[Q] Dump Lenovo B8080 boot.img/recovery.img

I'm trying to dump the boot.img in the hopes of porting CWM and, eventually, CM11 to the Lenovo B8080, better known as the Lenovo Yoga 10 HD+. But I'm at a loss how to extract the boot.img.
I've been following this guide here: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device and am stuck at trying to extract my boot.img as the binary is missing. All I get is
Code:
$ dump_image boot /storage/sdcard1/boot.img
dump_image: not found
I've also tried using romdump but the binary that I found won't run on the b8080, wrong architecture.
Lastly, I tried
Code:
$ cat /proc/mtd
as recommended in this guide: http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
but that also doesn't work as there is no "/proc/mtd".
What I do have is the following output:
Code:
$ cat /proc/partitions
major minor #blocks name
7 0 17703 loop0
179 0 15267840 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 32 mmcblk0p5
179 6 768 mmcblk0p6
179 7 768 mmcblk0p7
179 8 500 mmcblk0p8
179 9 500 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 500 mmcblk0p11
179 12 500 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 10240 mmcblk0p16
179 17 1572864 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 131072 mmcblk0p19
179 20 204800 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 1536 mmcblk0p23
179 24 1 mmcblk0p24
179 25 8 mmcblk0p25
179 26 12646383 mmcblk0p26
179 32 4096 mmcblk0rpmb
254 0 17703 dm-0
179 64 31166976 mmcblk1
179 65 31162880 mmcblk1p1
and
Code:
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=962644k,nr_inodes=182058,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 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
/dev/faccc /fac ext4 rw,seclabel,nodev,noatime,nodiratime,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=755,gid=1000 0 0
tmpfs /mnt/asec2 tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,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,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/lesw /lesw ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,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/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/[0]com.sketchbook-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:65 /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:65 /mnt/secure/asec2 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
Does anybody know how to proceed from here? Thanks!
In case anybody else is wondering, I found this wonderfully useful post that solves this problem:
http://forum.xda-developers.com/showpost.php?p=45564277&postcount=4
In case anybody is interested, here's the repository I'm working on:
https://github.com/zyrill/android_device_LENOVO_B8080
I am extremely interested! Nice work
Anny update ?

Categories

Resources